From 5336b9a35cf36d47f16ab64bbc2cfca9ca06cfa6 Mon Sep 17 00:00:00 2001 From: Vanessa Yuen <6842965+vanessayuenn@users.noreply.github.com> Date: Tue, 2 Feb 2021 20:56:26 +0100 Subject: [PATCH] translations batch (#17637) * New Crowdin translations by Github Action * fix frontmatter errors in translation * fix release notes * revert broken translation to main Co-authored-by: Crowdin Bot --- .../actions/creating-actions/about-actions.md | 7 +- .../creating-a-composite-run-steps-action.md | 8 +- .../creating-a-docker-container-action.md | 36 +- .../creating-a-javascript-action.md | 3 + .../dockerfile-support-for-github-actions.md | 9 +- .../metadata-syntax-for-github-actions.md | 4 +- .../setting-exit-codes-for-actions.md | 2 + .../about-packaging-with-github-actions.md | 4 +- .../guides/about-service-containers.md | 9 +- .../building-and-testing-java-with-ant.md | 10 +- .../building-and-testing-java-with-gradle.md | 29 +- .../building-and-testing-java-with-maven.md | 12 +- .../guides/building-and-testing-net.md | 6 +- .../guides/building-and-testing-nodejs.md | 26 +- .../guides/building-and-testing-powershell.md | 3 + .../guides/building-and-testing-python.md | 67 +-- .../guides/building-and-testing-ruby.md | 16 +- ...hing-dependencies-to-speed-up-workflows.md | 12 +- .../creating-postgresql-service-containers.md | 17 +- .../creating-redis-service-containers.md | 17 +- ...ing-to-amazon-elastic-container-service.md | 5 + .../guides/deploying-to-azure-app-service.md | 5 + .../deploying-to-google-kubernetes-engine.md | 5 + .../de-DE/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 10 +- .../publishing-java-packages-with-gradle.md | 17 +- .../publishing-java-packages-with-maven.md | 15 +- .../guides/publishing-nodejs-packages.md | 19 +- .../storing-workflow-data-as-artifacts.md | 8 +- .../about-self-hosted-runners.md | 2 +- ...a-proxy-server-with-self-hosted-runners.md | 2 +- ...using-self-hosted-runners-in-a-workflow.md | 11 +- translations/de-DE/content/actions/index.md | 17 +- .../essential-features-of-github-actions.md | 4 +- .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 8 +- .../managing-complex-workflows.md | 2 + ...-from-azure-pipelines-to-github-actions.md | 153 +++--- ...grating-from-circleci-to-github-actions.md | 85 +-- ...ting-from-gitlab-cicd-to-github-actions.md | 43 +- ...igrating-from-jenkins-to-github-actions.md | 174 +++---- ...rating-from-travis-ci-to-github-actions.md | 75 +-- .../security-hardening-for-github-actions.md | 8 +- .../adding-a-workflow-status-badge.md | 8 +- .../manually-running-a-workflow.md | 2 +- .../de-DE/content/actions/quickstart.md | 3 + ...nd-expression-syntax-for-github-actions.md | 43 +- .../reference/environment-variables.md | 22 +- .../workflow-commands-for-github-actions.md | 20 +- .../workflow-syntax-for-github-actions.md | 23 +- .../configuration/command-line-utilities.md | 16 +- .../configuring-email-for-notifications.md | 8 +- ...-availability-replication-for-a-cluster.md | 2 +- .../evacuating-a-cluster-node.md | 10 + .../initializing-the-cluster.md | 2 +- ...manually-syncing-actions-from-githubcom.md | 2 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../de-DE/content/admin/overview/index.md | 1 + ...managing-your-github-enterprise-license.md | 24 +- .../creating-a-pre-receive-hook-script.md | 43 +- .../admin/user-management/audited-actions.md | 4 +- .../migrating-to-internal-repositories.md | 4 +- .../user-management/viewing-push-logs.md | 9 +- .../managing-tags.md | 11 + .../creating-a-github-app-from-a-manifest.md | 4 +- .../creating-ci-tests-with-the-checks-api.md | 10 +- ...nces-between-github-apps-and-oauth-apps.md | 3 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 8 + .../developers/github-marketplace/index.md | 7 +- .../requirements-for-listing-an-app.md | 11 +- .../setting-pricing-plans-for-your-listing.md | 8 +- ...submitting-your-listing-for-publication.md | 30 +- .../developers/overview/secret-scanning.md | 77 ++- .../de-DE/content/discussions/index.md | 4 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../de-DE/content/education/guides.md | 10 +- translations/de-DE/content/education/index.md | 12 +- .../basics-of-setting-up-github-classroom.md | 2 +- .../create-a-group-assignment.md | 2 +- ...n-assignment-from-a-template-repository.md | 2 - .../create-an-individual-assignment.md | 2 +- .../index.md | 1 - .../teach-with-github-classroom.md | 3 + ...fications-for-pushes-to-your-repository.md | 4 +- .../changing-the-default-branch.md | 2 +- .../renaming-a-branch.md | 13 + ...authentication-with-saml-single-sign-on.md | 14 +- ...moving-sensitive-data-from-a-repository.md | 4 +- .../blocking-a-user-from-your-organization.md | 3 +- ...cking-a-user-from-your-personal-account.md | 6 +- ...ngle-issue-template-for-your-repository.md | 2 +- ...a-merge-conflict-using-the-command-line.md | 16 +- .../working-with-pre-receive-hooks.md | 2 +- .../about-github-marketplace.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 10 +- ...ode-scanning-alerts-for-your-repository.md | 2 + ...-codeql-code-scanning-in-your-ci-system.md | 2 + .../sarif-support-for-code-scanning.md | 6 +- .../uploading-a-sarif-file-to-github.md | 2 + .../about-github-advanced-security.md | 2 +- .../git-and-github-learning-resources.md | 10 +- .../git-cheatsheet.md | 2 +- .../githubs-products.md | 1 + ...roject-to-github-using-the-command-line.md | 18 +- .../navigating-code-on-github.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 2 + .../publishing-a-security-advisory.md | 12 + .../configuring-notifications.md | 3 +- ...sferring-an-issue-to-another-repository.md | 2 +- .../about-email-notifications.md | 3 +- .../searching-issues-and-pull-requests.md | 3 +- .../index.md | 4 +- ...ithub-pages-sites-for-your-organization.md | 30 ++ .../permission-levels-for-an-organization.md | 181 +++---- ...y-permission-levels-for-an-organization.md | 206 ++++---- ...-management-for-your-enterprise-account.md | 16 +- ...dio-subscription-with-github-enterprise.md | 4 +- .../managing-your-profile-readme.md | 2 + ...on-levels-for-a-user-account-repository.md | 19 +- .../types-of-emails-github-sends.md | 13 +- .../github-additional-product-terms.md | 2 +- .../site-policy/github-and-trade-controls.md | 25 +- .../github-subprocessors-and-cookies.md | 46 +- ...delines-for-legal-requests-of-user-data.md | 9 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../about-github-pages-and-jekyll.md | 4 +- .../about-github-pages.md | 22 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...he-visibility-of-your-github-pages-site.md | 27 + ...tom-404-page-for-your-github-pages-site.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 11 +- .../creating-a-github-pages-site.md | 7 +- .../github/working-with-github-pages/index.md | 1 + ...yll-build-errors-for-github-pages-sites.md | 2 +- .../unpublishing-a-github-pages-site.md | 2 +- .../basic-writing-and-formatting-syntax.md | 16 +- .../organizing-information-with-tables.md | 10 +- .../graphql/guides/introduction-to-graphql.md | 38 +- ...n-github-insights-and-github-enterprise.md | 2 +- .../installing-github-insights.md | 1 + ...ache-maven-for-use-with-github-packages.md | 10 +- ...guring-npm-for-use-with-github-packages.md | 6 +- ...g-rubygems-for-use-with-github-packages.md | 6 +- translations/de-DE/content/packages/index.md | 11 +- .../manage-packages/deleting-a-package.md | 4 +- .../de-DE/content/rest/overview/libraries.md | 4 + .../permissions-required-for-github-apps.md | 11 +- .../de-DE/data/glossaries/external.yml | 6 +- .../de-DE/data/learning-tracks/README.md | 3 + .../de-DE/data/learning-tracks/actions.yml | 7 + .../de-DE/data/release-notes/2-20/18.yml | 2 +- .../de-DE/data/release-notes/2-21/9.yml | 2 +- .../de-DE/data/release-notes/2-22/1.yml | 2 +- .../de-DE/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../de-DE/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../ssh-into-instance.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../github-actions/actions-billing.md | 2 +- .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../reseller-ask-to-become-billing-manager.md | 2 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../de-DE/data/reusables/pages/visit-site.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- ...ut-user-provisioning-enterprise-account.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../pull_request_webhook_properties.md | 6 +- translations/de-DE/data/ui.yml | 12 +- translations/de-DE/data/variables/product.yml | 1 + .../actions/creating-actions/about-actions.md | 9 +- .../creating-a-composite-run-steps-action.md | 8 +- .../creating-a-docker-container-action.md | 36 +- .../creating-a-javascript-action.md | 3 + .../dockerfile-support-for-github-actions.md | 7 +- .../metadata-syntax-for-github-actions.md | 489 +++++++++--------- .../setting-exit-codes-for-actions.md | 2 + .../guides/about-continuous-integration.md | 7 +- .../about-packaging-with-github-actions.md | 6 +- .../guides/about-service-containers.md | 11 +- .../building-and-testing-java-with-ant.md | 10 +- .../building-and-testing-java-with-gradle.md | 29 +- .../building-and-testing-java-with-maven.md | 12 +- .../guides/building-and-testing-net.md | 4 +- .../guides/building-and-testing-nodejs.md | 26 +- .../guides/building-and-testing-powershell.md | 3 + .../guides/building-and-testing-python.md | 67 +-- .../guides/building-and-testing-ruby.md | 16 +- ...hing-dependencies-to-speed-up-workflows.md | 12 +- .../creating-postgresql-service-containers.md | 17 +- .../creating-redis-service-containers.md | 17 +- ...ing-to-amazon-elastic-container-service.md | 5 + .../guides/deploying-to-azure-app-service.md | 5 + .../deploying-to-google-kubernetes-engine.md | 5 + .../es-ES/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 10 +- .../publishing-java-packages-with-gradle.md | 17 +- .../publishing-java-packages-with-maven.md | 15 +- .../guides/publishing-nodejs-packages.md | 19 +- ...us-integration-using-workflow-templates.md | 5 +- .../storing-workflow-data-as-artifacts.md | 10 +- .../about-self-hosted-runners.md | 116 ++--- .../adding-self-hosted-runners.md | 47 +- ...ess-to-self-hosted-runners-using-groups.md | 4 +- ...and-troubleshooting-self-hosted-runners.md | 84 +-- ...a-proxy-server-with-self-hosted-runners.md | 2 +- ...using-self-hosted-runners-in-a-workflow.md | 11 +- translations/es-ES/content/actions/index.md | 30 +- .../essential-features-of-github-actions.md | 4 +- .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 8 +- .../managing-complex-workflows.md | 2 + ...-from-azure-pipelines-to-github-actions.md | 155 +++--- ...grating-from-circleci-to-github-actions.md | 83 +-- ...ting-from-gitlab-cicd-to-github-actions.md | 43 +- ...igrating-from-jenkins-to-github-actions.md | 174 +++---- ...rating-from-travis-ci-to-github-actions.md | 75 +-- .../security-hardening-for-github-actions.md | 12 +- .../adding-a-workflow-status-badge.md | 8 +- .../manually-running-a-workflow.md | 29 +- .../es-ES/content/actions/quickstart.md | 84 +-- .../reference/authentication-in-a-workflow.md | 4 +- ...nd-expression-syntax-for-github-actions.md | 43 +- .../reference/environment-variables.md | 22 +- .../events-that-trigger-workflows.md | 8 +- ...pecifications-for-github-hosted-runners.md | 2 +- ...usage-limits-billing-and-administration.md | 2 +- .../workflow-commands-for-github-actions.md | 22 +- .../workflow-syntax-for-github-actions.md | 23 +- ...d-access-management-for-your-enterprise.md | 2 +- ...or-users-outside-your-identity-provider.md | 2 +- ...-your-github-enterprise-server-instance.md | 2 +- ...rovisioning-with-your-identity-provider.md | 4 +- ...identity-and-access-for-your-enterprise.md | 4 +- .../content/admin/authentication/using-cas.md | 2 +- .../admin/authentication/using-ldap.md | 2 +- .../admin/authentication/using-saml.md | 147 +++--- .../about-enterprise-configuration.md | 2 +- .../configuration/command-line-utilities.md | 16 +- .../configuring-advanced-security-features.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 2 +- .../configuring-email-for-notifications.md | 12 +- ...guring-github-pages-for-your-enterprise.md | 2 +- .../configuring-network-settings.md | 2 +- .../configuring-your-enterprise.md | 4 +- ...-github-enterprise-server-and-githubcom.md | 2 +- ...rise-server-and-github-enterprise-cloud.md | 2 +- .../configuration/site-admin-dashboard.md | 235 ++++----- .../about-geo-replication.md | 2 +- .../about-high-availability-configuration.md | 2 +- .../configuring-clustering.md | 2 +- ...-availability-replication-for-a-cluster.md | 2 +- .../configuring-high-availability.md | 2 +- .../creating-a-high-availability-replica.md | 2 +- ...een-clustering-and-high-availability-ha.md | 2 +- .../evacuating-a-cluster-node.md | 10 + .../initializing-the-cluster.md | 2 +- ...ng-a-failover-to-your-replica-appliance.md | 2 +- ...ng-from-github-enterprise-1110x-to-2123.md | 93 ++-- .../monitoring-your-appliance.md | 2 +- .../recommended-alert-thresholds.md | 24 +- ...-virtual-machine-and-physical-resources.md | 2 +- .../upgrading-github-enterprise-server.md | 2 +- .../about-github-enterprise-support.md | 1 - .../about-support-for-advanced-security.md | 6 +- .../admin/enterprise-support/overview.md | 2 +- .../providing-data-to-github-support.md | 2 +- .../reaching-github-support.md | 6 +- .../receiving-help-from-github-support.md | 2 +- .../enterprise-support/submitting-a-ticket.md | 2 +- ...anced-configuration-and-troubleshooting.md | 2 +- ...ub-actions-for-github-enterprise-server.md | 2 +- ...naging-access-to-actions-from-githubcom.md | 2 +- ...manually-syncing-actions-from-githubcom.md | 2 +- ...talling-github-enterprise-server-on-aws.md | 2 +- ...lling-github-enterprise-server-on-azure.md | 2 +- ...erprise-server-on-google-cloud-platform.md | 2 +- ...thub-enterprise-server-on-openstack-kvm.md | 2 +- ...ling-github-enterprise-server-on-vmware.md | 2 +- ...g-github-enterprise-server-on-xenserver.md | 2 +- ...-up-a-github-enterprise-server-instance.md | 2 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../about-upgrades-to-new-releases.md | 6 +- .../es-ES/content/admin/overview/index.md | 1 + ...managing-your-github-enterprise-license.md | 28 +- .../content/admin/overview/system-overview.md | 2 +- ...e-ecosystem-support-for-your-enterprise.md | 26 +- .../enabling-github-packages-with-aws.md | 26 +- ...github-packages-with-azure-blob-storage.md | 12 +- .../enabling-github-packages-with-minio.md | 36 +- ...ith-github-packages-for-your-enterprise.md | 30 +- ...inio-storage-bucket-for-github-packages.md | 6 +- .../creating-a-pre-receive-hook-script.md | 47 +- .../enforcing-policies-for-your-enterprise.md | 2 +- ...enforcing-policy-with-pre-receive-hooks.md | 2 +- .../es-ES/content/admin/release-notes.md | 4 +- .../admin/user-management/audited-actions.md | 44 +- .../auditing-users-across-your-enterprise.md | 4 +- ...-large-file-storage-for-your-enterprise.md | 2 +- ...izing-user-messages-for-your-enterprise.md | 42 +- ...rom-third-party-version-control-systems.md | 2 +- ...naging-organizations-in-your-enterprise.md | 2 +- ...anaging-repositories-in-your-enterprise.md | 4 +- .../managing-users-in-your-enterprise.md | 4 +- ...rating-data-to-and-from-your-enterprise.md | 2 +- .../migrating-data-to-your-enterprise.md | 14 +- .../migrating-to-internal-repositories.md | 6 +- .../monitoring-activity-in-your-enterprise.md | 2 +- ...ring-to-migrate-data-to-your-enterprise.md | 16 +- ...ctor-authentication-for-an-organization.md | 2 +- .../searching-the-audit-log.md | 2 +- .../suspending-and-unsuspending-users.md | 2 +- .../user-management/viewing-push-logs.md | 9 +- .../adding-and-cloning-repositories.md | 2 +- ...nging-a-remotes-url-from-github-desktop.md | 4 +- .../creating-an-issue-or-pull-request.md | 2 +- ...ur-local-repository-in-sync-with-github.md | 2 +- .../making-changes-in-a-branch.md | 2 +- .../managing-branches.md | 2 +- .../managing-tags.md | 11 + .../pushing-changes-to-github.md | 2 +- .../viewing-the-branch-history.md | 2 +- ...pository-on-github-or-github-enterprise.md | 2 +- .../about-connections-to-github.md | 2 +- ...t-large-file-storage-and-github-desktop.md | 2 +- .../authenticating-to-github.md | 2 +- ...figuring-and-customizing-github-desktop.md | 2 +- .../configuring-basic-settings.md | 2 +- .../configuring-git-for-github-desktop.md | 2 +- ...r-first-repository-using-github-desktop.md | 2 +- .../getting-started-with-github-desktop.md | 2 +- ...ng-and-authenticating-to-github-desktop.md | 2 +- .../overview.md | 2 +- .../developers/apps/authorizing-oauth-apps.md | 12 +- .../developers/apps/building-github-apps.md | 2 +- .../developers/apps/building-oauth-apps.md | 2 +- .../creating-a-github-app-from-a-manifest.md | 10 +- ...ating-a-github-app-using-url-parameters.md | 32 +- .../creating-ci-tests-with-the-checks-api.md | 12 +- ...nces-between-github-apps-and-oauth-apps.md | 5 +- .../apps/getting-started-with-apps.md | 2 +- .../es-ES/content/developers/apps/guides.md | 2 +- ...g-and-authorizing-users-for-github-apps.md | 8 +- .../developers/apps/managing-github-apps.md | 2 +- .../developers/apps/managing-oauth-apps.md | 2 +- .../developers/apps/scopes-for-oauth-apps.md | 60 +-- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../creating-apps-for-github-marketplace.md | 2 +- .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 9 + .../developers/github-marketplace/index.md | 7 +- .../listing-an-app-on-github-marketplace.md | 2 +- .../receiving-payment-for-app-purchases.md | 8 +- .../requirements-for-listing-an-app.md | 11 +- .../selling-your-app-on-github-marketplace.md | 2 +- .../setting-pricing-plans-for-your-listing.md | 8 +- ...submitting-your-listing-for-publication.md | 30 +- ...-the-github-marketplace-api-in-your-app.md | 2 +- .../viewing-transactions-for-your-listing.md | 2 +- ...k-events-for-the-github-marketplace-api.md | 10 +- .../developers/overview/secret-scanning.md | 77 ++- .../developers/webhooks-and-events/events.md | 2 +- .../webhooks-and-events/github-event-types.md | 4 +- .../webhooks-and-events/issue-event-types.md | 26 +- .../webhook-events-and-payloads.md | 38 +- .../webhooks-and-events/webhooks.md | 2 +- .../about-discussions.md | 2 +- ...ting-with-maintainers-using-discussions.md | 2 +- ...s-for-community-conversations-on-github.md | 2 +- ...iscussions-across-multiple-repositories.md | 2 +- .../es-ES/content/discussions/index.md | 18 +- .../es-ES/content/discussions/quickstart.md | 2 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../es-ES/content/education/guides.md | 56 +- translations/es-ES/content/education/index.md | 38 +- ...g-makecode-arcade-with-github-classroom.md | 2 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../basics-of-setting-up-github-classroom.md | 4 +- .../create-a-group-assignment.md | 4 +- ...n-assignment-from-a-template-repository.md | 4 +- .../create-an-individual-assignment.md | 4 +- .../get-started-with-github-classroom.md | 4 +- .../glossary.md | 2 +- .../index.md | 1 - .../integrate-github-classroom-with-an-ide.md | 4 +- ...ate-github-classroom-with-an-online-ide.md | 2 +- .../learn-with-github-classroom.md | 4 +- .../leave-feedback-with-pull-requests.md | 2 +- .../manage-classrooms.md | 2 +- .../teach-with-github-classroom.md | 9 +- .../use-autograding.md | 2 +- .../view-autograding-results.md | 2 +- .../es-ES/content/education/quickstart.md | 4 +- .../about-dependabot-version-updates.md | 4 +- ...fications-for-pushes-to-your-repository.md | 6 +- .../about-merge-methods-on-github.md | 2 +- .../about-protected-branches.md | 80 +-- .../about-secret-scanning.md | 30 +- .../about-securing-your-repository.md | 10 +- ...for-release-forms-with-query-parameters.md | 8 +- .../changing-the-default-branch.md | 4 +- ...guration-options-for-dependency-updates.md | 8 +- ...ring-commit-squashing-for-pull-requests.md | 2 +- .../configuring-pull-request-merges.md | 2 +- ...g-secret-scanning-for-your-repositories.md | 30 +- ...zing-how-changed-files-appear-on-github.md | 2 +- ...ining-the-mergeability-of-pull-requests.md | 2 +- ...nd-restoring-branches-in-a-pull-request.md | 2 +- ...ing-a-sponsor-button-in-your-repository.md | 2 +- ...ing-github-discussions-for-a-repository.md | 2 +- ...your-actions-up-to-date-with-dependabot.md | 2 +- ...your-dependencies-updated-automatically.md | 2 +- .../managing-a-branch-protection-rule.md | 54 +- .../managing-alerts-from-secret-scanning.md | 2 +- .../managing-branches-in-your-repository.md | 2 +- .../managing-repository-settings.md | 2 +- ...d-analysis-settings-for-your-repository.md | 16 +- ...d-people-with-access-to-your-repository.md | 2 +- ...ging-the-automatic-deletion-of-branches.md | 2 +- ...-the-forking-policy-for-your-repository.md | 2 +- .../releasing-projects-on-github.md | 2 +- .../renaming-a-branch.md | 33 +- .../restoring-a-deleted-repository.md | 2 +- .../securing-your-repository.md | 2 +- .../setting-repository-visibility.md | 12 +- .../troubleshooting-required-status-checks.md | 10 +- .../viewing-branches-in-your-repository.md | 2 +- ...deployment-activity-for-your-repository.md | 2 +- ...wing-your-repositorys-releases-and-tags.md | 2 +- .../about-anonymized-image-urls.md | 2 +- ...authentication-with-saml-single-sign-on.md | 16 +- .../about-commit-signature-verification.md | 4 +- .../about-githubs-ip-addresses.md | 2 +- .../authenticating-to-github/about-ssh.md | 2 +- ...-github-using-two-factor-authentication.md | 2 +- ...ng-a-new-gpg-key-to-your-github-account.md | 2 +- ...ng-a-new-ssh-key-to-your-github-account.md | 8 +- .../associating-an-email-with-your-gpg-key.md | 2 +- ...authenticating-with-saml-single-sign-on.md | 2 +- ...-token-for-use-with-saml-single-sign-on.md | 2 +- ...sh-key-for-use-with-saml-single-sign-on.md | 2 +- .../authorizing-oauth-apps.md | 2 +- ...delivery-methods-for-your-mobile-device.md | 2 +- .../checking-for-existing-gpg-keys.md | 2 +- ...t-and-tag-signature-verification-status.md | 2 +- ...-factor-authentication-recovery-methods.md | 2 +- .../configuring-two-factor-authentication.md | 2 +- .../connecting-to-github-with-ssh.md | 2 +- ...s-where-sms-authentication-is-supported.md | 2 +- .../creating-a-personal-access-token.md | 2 +- .../creating-a-strong-password.md | 2 +- ...uthentication-for-your-personal-account.md | 2 +- .../error-bad-file-number.md | 2 +- .../error-ssh-add-illegal-option----k.md | 2 +- .../generating-a-new-gpg-key.md | 2 +- ...-ssh-key-and-adding-it-to-the-ssh-agent.md | 2 +- .../keeping-your-account-and-data-secure.md | 2 +- .../managing-commit-signature-verification.md | 2 +- ...ccount-if-you-lose-your-2fa-credentials.md | 2 +- ...moving-sensitive-data-from-a-repository.md | 6 +- ...wing-your-authorized-applications-oauth.md | 2 +- .../reviewing-your-authorized-integrations.md | 2 +- .../reviewing-your-security-log.md | 342 ++++++------ ...ount-with-two-factor-authentication-2fa.md | 2 +- .../signing-commits.md | 2 +- .../authenticating-to-github/signing-tags.md | 2 +- .../authenticating-to-github/sudo-mode.md | 2 +- .../telling-git-about-your-signing-key.md | 2 +- .../testing-your-ssh-connection.md | 36 +- ...eshooting-commit-signature-verification.md | 2 +- .../troubleshooting-ssh.md | 2 +- .../updating-an-expired-gpg-key.md | 2 +- ...-verified-email-address-in-your-gpg-key.md | 2 +- ...-and-managing-your-active-saml-sessions.md | 2 +- .../working-with-ssh-key-passphrases.md | 2 +- ...out-community-management-and-moderation.md | 2 +- ...munity-profiles-for-public-repositories.md | 2 +- .../about-team-discussions.md | 2 +- .../about-wikis.md | 2 +- .../accessing-a-projects-community-profile.md | 2 +- ...dding-a-code-of-conduct-to-your-project.md | 2 +- .../adding-a-license-to-a-repository.md | 2 +- .../blocking-a-user-from-your-organization.md | 5 +- ...cking-a-user-from-your-personal-account.md | 8 +- .../changing-access-permissions-for-wikis.md | 2 +- .../collaborating-with-your-team.md | 2 +- ...ing-issue-templates-for-your-repository.md | 2 +- ...ll-request-template-for-your-repository.md | 2 +- .../creating-a-team-discussion.md | 2 +- .../disabling-wikis.md | 2 +- .../documenting-your-project-with-wikis.md | 4 +- .../editing-or-deleting-a-team-discussion.md | 2 +- ...ntributions-to-your-project-with-labels.md | 2 +- ...iting-interactions-in-your-organization.md | 2 +- ...imiting-interactions-in-your-repository.md | 2 +- .../locking-conversations.md | 2 +- .../maintaining-your-safety-on-github.md | 2 +- ...-abuse-in-your-organizations-repository.md | 2 +- ...ontent-in-your-organizations-repository.md | 2 +- ...ngle-issue-template-for-your-repository.md | 4 +- .../moderating-comments-and-conversations.md | 2 +- .../pinning-a-team-discussion.md | 2 +- .../reporting-abuse-or-spam.md | 2 +- ...-guidelines-for-repository-contributors.md | 2 +- ...-your-project-for-healthy-contributions.md | 4 +- .../tracking-changes-in-a-comment.md | 2 +- ...nblocking-a-user-from-your-organization.md | 2 +- ...cking-a-user-from-your-personal-account.md | 2 +- ...courage-useful-issues-and-pull-requests.md | 2 +- ...-who-are-blocked-from-your-organization.md | 2 +- ...ouve-blocked-from-your-personal-account.md | 2 +- .../about-branches.md | 4 +- .../about-collaborative-development-models.md | 2 +- ...out-comparing-branches-in-pull-requests.md | 2 +- .../about-conversations-on-github.md | 2 +- .../about-forks.md | 2 +- .../about-merge-conflicts.md | 2 +- .../about-pull-request-merges.md | 2 +- .../about-pull-request-reviews.md | 4 +- .../about-pull-requests.md | 2 +- .../addressing-merge-conflicts.md | 2 +- ...pull-request-branch-created-from-a-fork.md | 2 +- ...ng-a-pull-request-with-required-reviews.md | 4 +- ...nging-the-base-branch-of-a-pull-request.md | 2 +- .../changing-the-stage-of-a-pull-request.md | 2 +- ...repositories-with-code-quality-features.md | 2 +- .../commenting-on-a-pull-request.md | 2 +- .../creating-a-pull-request-from-a-fork.md | 4 +- .../creating-a-pull-request.md | 2 +- ...eleting-branches-within-your-repository.md | 2 +- .../dismissing-a-pull-request-review.md | 4 +- .../filtering-files-in-a-pull-request.md | 2 +- ...methods-and-functions-in-a-pull-request.md | 2 +- .../github-flow.md | 2 +- ...corporating-changes-from-a-pull-request.md | 2 +- ...rporating-feedback-in-your-pull-request.md | 2 +- .../merging-a-pull-request.md | 4 +- .../overview.md | 2 +- ...changes-to-your-work-with-pull-requests.md | 2 +- .../requesting-a-pull-request-review.md | 2 +- .../resolving-a-merge-conflict-on-github.md | 2 +- ...a-merge-conflict-using-the-command-line.md | 18 +- .../reviewing-changes-in-pull-requests.md | 2 +- ...ng-dependency-changes-in-a-pull-request.md | 2 +- ...wing-proposed-changes-in-a-pull-request.md | 4 +- .../viewing-a-pull-request-review.md | 2 +- ...sitory-is-deleted-or-changes-visibility.md | 2 +- .../working-with-forks.md | 2 +- .../working-with-pre-receive-hooks.md | 2 +- .../about-commits.md | 2 +- .../changing-a-commit-message.md | 2 +- .../commit-branch-and-tag-labels.md | 2 +- ...sts-on-github-but-not-in-my-local-clone.md | 2 +- .../comparing-commits.md | 2 +- ...g-a-commit-on-behalf-of-an-organization.md | 4 +- ...creating-a-commit-with-multiple-authors.md | 2 +- .../creating-and-editing-commits.md | 2 +- .../differences-between-commit-views.md | 2 +- .../troubleshooting-commits.md | 2 +- .../viewing-and-comparing-commits.md | 2 +- ...are-my-commits-linked-to-the-wrong-user.md | 2 +- .../about-archiving-repositories.md | 2 +- .../about-code-owners.md | 2 +- .../about-readmes.md | 2 +- .../about-repositories.md | 4 +- .../archiving-a-github-repository.md | 2 +- .../archiving-repositories.md | 2 +- .../backing-up-a-repository.md | 2 +- .../cloning-a-repository-from-github.md | 2 +- .../cloning-a-repository.md | 2 +- .../creating-a-new-repository.md | 2 +- .../creating-a-repository-on-github.md | 2 +- .../licensing-a-repository.md | 2 +- .../about-github-marketplace.md | 4 +- .../exploring-integrations.md | 6 +- .../installing-an-app-in-your-organization.md | 2 +- ...talling-an-app-in-your-personal-account.md | 2 +- ...d-installing-apps-in-github-marketplace.md | 2 +- .../about-codespaces.md | 2 +- ...configuring-codespaces-for-your-project.md | 4 +- ...ging-access-and-security-for-codespaces.md | 28 +- ...naging-encrypted-secrets-for-codespaces.md | 40 +- ...anaging-gpg-verification-for-codespaces.md | 12 +- ...rsonalizing-codespaces-for-your-account.md | 4 +- .../getting-started-with-the-api.md | 2 +- .../git-automation-with-oauth-tokens.md | 2 +- .../about-code-scanning.md | 35 +- .../about-integration-with-code-scanning.md | 2 +- ...our-code-for-vulnerabilities-and-errors.md | 2 +- .../configuring-code-scanning.md | 172 +++--- ...-codeql-code-scanning-in-your-ci-system.md | 12 +- ...enabling-code-scanning-for-a-repository.md | 110 ++-- .../integrating-with-code-scanning.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 4 +- ...-codeql-code-scanning-in-your-ci-system.md | 16 +- .../sarif-support-for-code-scanning.md | 162 +++--- .../troubleshooting-the-codeql-workflow.md | 8 +- .../uploading-a-sarif-file-to-github.md | 8 +- ...e-scanning-with-your-existing-ci-system.md | 2 +- .../about-github-jobs.md | 2 +- .../about-github-advanced-security.md | 40 +- .../access-permissions-on-github.md | 2 +- .../exploring-projects-on-github.md | 2 +- .../faq-about-changes-to-githubs-plans.md | 6 +- ...-to-contribute-to-open-source-on-github.md | 2 +- .../following-people.md | 2 +- .../git-and-github-learning-resources.md | 12 +- .../git-cheatsheet.md | 2 +- .../github-for-mobile.md | 22 +- .../github-glossary.md | 2 +- .../githubs-products.md | 7 +- .../keyboard-shortcuts.md | 16 +- .../learning-about-github.md | 2 +- .../getting-started-with-github/quickstart.md | 2 +- .../saving-repositories-with-stars.md | 2 +- ...g-up-a-trial-of-github-enterprise-cloud.md | 2 +- ...-up-a-trial-of-github-enterprise-server.md | 2 +- .../signing-up-for-github.md | 2 +- .../types-of-github-accounts.md | 2 +- .../using-github.md | 2 +- .../verifying-your-email-address.md | 2 +- .../about-github-importer.md | 2 +- ...roject-to-github-using-the-command-line.md | 8 +- ...rting-a-repository-with-github-importer.md | 2 +- .../importing-source-code-to-github.md | 2 +- .../source-code-migration-tools.md | 2 +- .../support-for-subversion-clients.md | 2 +- ...author-attribution-with-github-importer.md | 2 +- ...-differences-between-subversion-and-git.md | 2 +- .../working-with-subversion-on-github.md | 2 +- .../3d-file-viewer.md | 2 +- ...-to-a-repository-using-the-command-line.md | 2 +- .../creating-new-files.md | 2 +- .../deleting-files-in-a-repository.md | 24 +- ...iting-files-in-another-users-repository.md | 2 +- .../editing-files-in-your-repository.md | 2 +- .../getting-permanent-links-to-files.md | 2 +- .../managing-files-on-github.md | 2 +- .../managing-files-using-the-command-line.md | 2 +- ...o-a-new-location-using-the-command-line.md | 2 +- .../navigating-code-on-github.md | 4 +- .../renaming-a-file-using-the-command-line.md | 2 +- .../rendering-csv-and-tsv-data.md | 2 +- ...g-with-jupyter-notebook-files-on-github.md | 2 +- .../working-with-non-code-files.md | 2 +- .../about-git-large-file-storage.md | 2 +- .../about-storage-and-bandwidth-usage.md | 2 +- ...llaboration-with-git-large-file-storage.md | 2 +- .../configuring-git-large-file-storage.md | 2 +- .../installing-git-large-file-storage.md | 2 +- ...ur-repository-to-git-large-file-storage.md | 2 +- ...oving-files-from-git-large-file-storage.md | 2 +- .../versioning-large-files.md | 2 +- .../working-with-large-files.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 4 +- .../about-dependabot-security-updates.md | 6 +- ...g-a-collaborator-to-a-security-advisory.md | 2 +- ...ng-a-security-policy-to-your-repository.md | 2 +- ...ilities-in-the-github-advisory-database.md | 8 +- ...ork-to-resolve-a-security-vulnerability.md | 2 +- ...configuring-dependabot-security-updates.md | 8 +- ...tifications-for-vulnerable-dependencies.md | 44 +- .../editing-a-security-advisory.md | 2 +- ...ecurity-vulnerabilities-in-your-project.md | 2 +- ...abilities-in-your-projects-dependencies.md | 2 +- ...rmission-levels-for-security-advisories.md | 2 +- .../publishing-a-security-advisory.md | 14 +- ...a-collaborator-from-a-security-advisory.md | 2 +- .../troubleshooting-dependabot-errors.md | 8 +- ...he-detection-of-vulnerable-dependencies.md | 2 +- ...nerable-dependencies-in-your-repository.md | 2 +- .../withdrawing-a-security-advisory.md | 2 +- .../about-notifications.md | 4 +- .../configuring-notifications.md | 13 +- .../managing-notifications-from-your-inbox.md | 48 +- ...ng-subscriptions-for-activity-on-github.md | 2 +- .../managing-your-subscriptions.md | 2 +- .../setting-up-notifications.md | 2 +- .../viewing-and-triaging-notifications.md | 2 +- ...and-pull-requests-with-query-parameters.md | 8 +- .../about-automation-for-project-boards.md | 2 +- .../about-milestones.md | 2 +- .../about-project-boards.md | 2 +- .../about-task-lists.md | 2 +- ...es-and-pull-requests-to-a-project-board.md | 2 +- .../adding-notes-to-a-project-board.md | 2 +- ...and-pull-requests-to-other-github-users.md | 2 +- ...ilestones-with-issues-and-pull-requests.md | 2 +- .../changing-project-board-visibility.md | 8 +- .../closing-a-project-board.md | 2 +- ...nfiguring-automation-for-project-boards.md | 2 +- ...ting-a-permanent-link-to-a-code-snippet.md | 2 +- .../creating-a-project-board.md | 4 +- .../creating-an-issue.md | 2 +- ...milestones-for-issues-and-pull-requests.md | 2 +- .../deleting-a-project-board.md | 2 +- .../deleting-an-issue.md | 2 +- ...ing-project-boards-in-your-organization.md | 2 +- .../editing-a-project-board.md | 2 +- .../filtering-cards-on-a-project-board.md | 2 +- ...g-issues-and-pull-requests-by-assignees.md | 2 +- ...ring-issues-and-pull-requests-by-labels.md | 2 +- ...g-issues-and-pull-requests-by-milestone.md | 2 +- .../filtering-issues-and-pull-requests.md | 2 +- ...iltering-pull-requests-by-review-status.md | 2 +- .../finding-information-in-a-repository.md | 2 +- .../linking-a-pull-request-to-an-issue.md | 4 +- ...linking-a-repository-to-a-project-board.md | 2 +- .../managing-labels.md | 4 +- .../managing-project-boards.md | 2 +- ...your-work-with-issues-and-pull-requests.md | 2 +- .../opening-an-issue-from-a-comment.md | 2 +- .../opening-an-issue-from-code.md | 2 +- .../reopening-a-closed-project-board.md | 2 +- .../sharing-filters.md | 2 +- .../sorting-issues-and-pull-requests.md | 2 +- ...e-progress-of-your-work-with-milestones.md | 2 +- ...ogress-of-your-work-with-project-boards.md | 2 +- ...sferring-an-issue-to-another-repository.md | 4 +- ...arch-to-filter-issues-and-pull-requests.md | 2 +- ...ng-all-of-your-issues-and-pull-requests.md | 2 +- .../viewing-your-milestones-progress.md | 2 +- .../about-email-notifications.md | 5 +- .../about-notifications.md | 2 +- .../about-web-notifications.md | 2 +- .../accessing-your-notifications.md | 2 +- ...-delivery-method-for-your-notifications.md | 2 +- .../getting-started-with-notifications.md | 2 +- ...listing-the-repositories-youre-watching.md | 2 +- .../managing-your-notifications.md | 2 +- .../marking-notifications-as-read.md | 2 +- .../saving-notifications-for-later.md | 2 +- ...to-and-unsubscribing-from-notifications.md | 2 +- ...nd-unwatching-releases-for-a-repository.md | 2 +- .../watching-and-unwatching-repositories.md | 2 +- ...atching-and-unwatching-team-discussions.md | 2 +- .../about-searching-on-github.md | 2 +- .../finding-files-on-github.md | 2 +- ...etting-started-with-searching-on-github.md | 2 +- .../searching-code.md | 2 +- .../searching-commits.md | 10 +- .../searching-discussions.md | 2 +- .../searching-for-repositories.md | 2 +- .../searching-github-marketplace.md | 2 +- .../searching-in-forks.md | 2 +- .../searching-issues-and-pull-requests.md | 5 +- .../searching-on-github.md | 2 +- .../searching-topics.md | 2 +- .../searching-users.md | 2 +- .../searching-wikis.md | 2 +- .../sorting-search-results.md | 2 +- .../troubleshooting-search-queries.md | 2 +- ...bout-billing-for-git-large-file-storage.md | 2 +- .../about-billing-for-github-marketplace.md | 2 +- .../about-billing-for-github-packages.md | 4 +- .../about-billing-for-github-sponsors.md | 2 +- .../about-billing-on-github.md | 2 +- ...organizations-for-procurement-companies.md | 2 +- .../about-per-user-pricing.md | 2 +- ...r-an-organization-on-behalf-of-a-client.md | 2 +- ...unted-subscriptions-for-github-accounts.md | 22 +- ...lling-plan-for-a-github-marketplace-app.md | 2 +- .../downgrading-your-github-subscription.md | 2 +- ...-downgrading-affect-the-billing-process.md | 2 +- ...ging-billing-for-git-large-file-storage.md | 2 +- .../managing-billing-for-github-actions.md | 2 +- ...ing-billing-for-github-marketplace-apps.md | 2 +- .../managing-billing-for-github-packages.md | 2 +- .../managing-billing-for-github-sponsors.md | 2 +- ...anaging-billing-for-your-github-account.md | 2 +- .../managing-your-github-billing-settings.md | 2 +- ...organizations-for-procurement-companies.md | 2 +- .../upgrading-git-large-file-storage.md | 2 +- .../upgrading-your-github-subscription.md | 2 +- ...ng-pending-changes-to-your-subscription.md | 2 +- ...ewing-your-git-large-file-storage-usage.md | 2 +- ...ing-your-subscriptions-and-billing-date.md | 2 +- ...ess-management-with-saml-single-sign-on.md | 4 +- .../about-oauth-app-access-restrictions.md | 2 +- .../about-scim.md | 4 +- .../about-teams.md | 2 +- ...-authentication-and-saml-single-sign-on.md | 2 +- ...f-your-identity-provider-is-unavailable.md | 2 +- ...ithub-app-managers-in-your-organization.md | 2 +- .../adding-organization-members-to-a-team.md | 2 +- ...rs-to-repositories-in-your-organization.md | 2 +- .../adding-people-to-your-organization.md | 2 +- ...roving-oauth-apps-for-your-organization.md | 2 +- ...tside-collaborator-in-your-organization.md | 2 +- ...an-invitation-to-join-your-organization.md | 2 +- ...laborating-with-groups-in-organizations.md | 2 +- ...saml-single-sign-on-and-scim-using-okta.md | 2 +- ...-identity-provider-to-your-organization.md | 2 +- ...ation-member-to-an-outside-collaborator.md | 2 +- ...-collaborator-to-an-organization-member.md | 2 +- ...reating-a-new-organization-from-scratch.md | 2 +- .../creating-a-team.md | 2 +- ...ions-saml-single-sign-on-recovery-codes.md | 2 +- ...ml-single-sign-on-for-your-organization.md | 2 +- ...ml-single-sign-on-for-your-organization.md | 2 +- ...r-organization-with-saml-single-sign-on.md | 2 +- .../index.md | 2 +- ...ra-with-your-organization-project-board.md | 2 +- ...nviting-users-to-join-your-organization.md | 2 +- .../keeping-your-organization-secure.md | 2 +- ...-project-board-for-organization-members.md | 2 +- ...aging-access-to-your-organizations-apps.md | 2 +- ...ss-to-your-organizations-project-boards.md | 2 +- ...cess-to-your-organizations-repositories.md | 2 +- ...access-to-an-organization-project-board.md | 2 +- ...ls-access-to-an-organization-repository.md | 2 +- ...rvice-accounts-with-saml-single-sign-on.md | 2 +- ...s-for-repositories-in-your-organization.md | 2 +- ...n-for-repositories-in-your-organization.md | 2 +- ...cess-to-your-organizations-repositories.md | 2 +- ...anaging-membership-in-your-organization.md | 2 +- .../managing-organization-settings.md | 2 +- ...-access-to-your-organization-with-roles.md | 2 +- ...ml-single-sign-on-for-your-organization.md | 2 +- ...heduled-reminders-for-your-organization.md | 2 +- ...aging-scheduled-reminders-for-your-team.md | 2 +- ...analysis-settings-for-your-organization.md | 32 +- ...am-access-to-an-organization-repository.md | 2 +- ...e-for-repositories-in-your-organization.md | 2 +- ...he-forking-policy-for-your-organization.md | 2 +- ...ithub-pages-sites-for-your-organization.md | 30 ++ ...rom-accounts-your-organization-sponsors.md | 4 +- ...ng-to-improved-organization-permissions.md | 2 +- ...-a-team-in-your-organizations-hierarchy.md | 2 +- .../organizing-members-into-teams.md | 2 +- .../permission-levels-for-an-organization.md | 183 +++---- ...aml-single-sign-on-in-your-organization.md | 2 +- ...t-board-permissions-for-an-organization.md | 4 +- ...ng-a-former-member-of-your-organization.md | 2 +- ...emoving-a-member-from-your-organization.md | 2 +- ...borator-from-an-organization-repository.md | 2 +- ...hub-app-managers-from-your-organization.md | 2 +- .../renaming-an-organization.md | 2 +- ...y-permission-levels-for-an-organization.md | 208 ++++---- .../requesting-to-add-a-child-team.md | 2 +- ...questing-to-add-or-change-a-parent-team.md | 2 +- ...tor-authentication-in-your-organization.md | 2 +- ...cting-access-to-your-organizations-data.md | 2 +- ...visibility-changes-in-your-organization.md | 2 +- ...ing-the-audit-log-for-your-organization.md | 137 ++--- ...ng-base-permissions-for-an-organization.md | 2 +- ...-a-team-with-an-identity-provider-group.md | 18 +- ...ading-to-the-corporate-terms-of-service.md | 2 +- ...embers-saml-access-to-your-organization.md | 2 +- .../viewing-insights-for-your-organization.md | 2 +- ...s-in-your-organization-have-2fa-enabled.md | 2 +- ...-management-for-your-enterprise-account.md | 34 +- ...rganizations-in-your-enterprise-account.md | 6 +- ...-management-for-your-enterprise-account.md | 4 +- ...rganizations-in-your-enterprise-account.md | 14 +- ...ity-settings-in-your-enterprise-account.md | 4 +- ...dio-subscription-with-github-enterprise.md | 14 +- ...rganizations-in-your-enterprise-account.md | 2 +- ...rganizations-in-your-enterprise-account.md | 10 +- ...rganizations-in-your-enterprise-account.md | 2 +- .../managing-users-in-your-enterprise.md | 2 +- .../managing-your-enterprise-account.md | 2 +- .../roles-in-an-enterprise.md | 2 +- ...rganizations-in-your-enterprise-account.md | 2 +- ...-a-users-saml-access-to-your-enterprise.md | 2 +- .../viewing-people-in-your-enterprise.md | 2 +- ...n-and-usage-for-your-enterprise-account.md | 2 +- .../about-your-organizations-profile.md | 2 +- .../about-your-profile.md | 2 +- .../customizing-your-profile.md | 2 +- ...ing-contribution-graphs-on-your-profile.md | 2 +- .../managing-your-profile-readme.md | 4 +- .../personalizing-your-profile.md | 2 +- .../pinning-items-to-your-profile.md | 2 +- ...r-private-contributions-on-your-profile.md | 2 +- .../viewing-contributions-on-your-profile.md | 4 +- ...tributions-not-showing-up-on-my-profile.md | 6 +- .../about-organization-membership.md | 2 +- .../about-your-personal-dashboard.md | 2 +- ...an-email-address-to-your-github-account.md | 2 +- ...that-expose-your-personal-email-address.md | 2 +- .../changing-your-github-username.md | 2 +- .../changing-your-primary-email-address.md | 2 +- .../converting-a-user-into-an-organization.md | 2 +- ...rating-jira-with-your-personal-projects.md | 2 +- ...-collaborators-to-a-personal-repository.md | 2 +- ...ng-access-to-your-personal-repositories.md | 2 +- .../managing-email-preferences.md | 2 +- .../managing-marketing-emails-from-github.md | 2 +- ...analysis-settings-for-your-user-account.md | 2 +- ...fault-branch-name-for-your-repositories.md | 2 +- .../managing-user-account-settings.md | 2 +- ...naging-your-membership-in-organizations.md | 2 +- .../managing-your-scheduled-reminders.md | 2 +- .../managing-your-theme-settings.md | 4 +- .../merging-multiple-user-accounts.md | 2 +- ...on-levels-for-a-user-account-repository.md | 21 +- ...on-levels-for-user-owned-project-boards.md | 6 +- ...membering-your-github-username-or-email.md | 2 +- ...collaborator-from-a-personal-repository.md | 2 +- ...ng-organization-approval-for-oauth-apps.md | 2 +- .../setting-a-backup-email-address.md | 2 +- .../types-of-emails-github-sends.md | 13 +- .../github-acceptable-use-policies.md | 2 +- .../github-additional-product-terms.md | 2 +- .../site-policy/github-and-trade-controls.md | 51 +- ...ub-bug-bounty-program-legal-safe-harbor.md | 2 +- .../github-corporate-terms-of-service.md | 36 +- .../github/site-policy/github-event-terms.md | 2 +- .../github-gifts-and-entertainment-policy.md | 4 +- .../github-marketplace-developer-agreement.md | 14 +- ...ource-applications-terms-and-conditions.md | 4 +- .../site-policy/github-pre-release-program.md | 2 +- .../site-policy/github-privacy-statement.md | 50 +- .../github-registered-developer-agreement.md | 2 +- .../github-research-program-terms.md | 2 +- .../github-sponsors-additional-terms.md | 4 +- .../github-subprocessors-and-cookies.md | 100 ++-- .../site-policy/github-terms-of-service.md | 2 +- ...out-the-california-consumer-privacy-act.md | 2 +- ...ide-to-submitting-a-dmca-counter-notice.md | 11 +- ...de-to-submitting-a-dmca-takedown-notice.md | 2 +- ...delines-for-legal-requests-of-user-data.md | 11 +- ...b-sponsors-for-open-source-contributors.md | 2 +- .../about-github-sponsors.md | 2 +- .../managing-your-sponsorship.md | 2 +- .../overview.md | 2 +- ...ng-sponsorships-through-github-sponsors.md | 2 +- ...p-github-sponsors-for-your-organization.md | 2 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../sponsoring-open-source-contributors.md | 2 +- .../tax-information-for-github-sponsors.md | 2 +- .../viewing-your-sponsors-and-sponsorships.md | 4 +- ...se-settings-for-your-private-repository.md | 2 +- ...hive-program-for-your-public-repository.md | 2 +- .../github/using-git/about-git-rebase.md | 10 +- .../using-git/about-git-subtree-merges.md | 2 +- .../github/using-git/adding-a-remote.md | 2 +- .../caching-your-github-credentials-in-git.md | 2 +- .../using-git/changing-a-remotes-url.md | 2 +- .../configuring-git-to-handle-line-endings.md | 2 +- ...etting-changes-from-a-remote-repository.md | 2 +- .../getting-started-with-git-and-github.md | 2 +- .../github/using-git/learning-about-git.md | 2 +- .../using-git/managing-remote-repositories.md | 2 +- .../pushing-commits-to-a-remote-repository.md | 2 +- .../github/using-git/removing-a-remote.md | 2 +- .../github/using-git/renaming-a-remote.md | 2 +- .../using-git/setting-your-username-in-git.md | 2 +- ...ing-credentials-from-the-macos-keychain.md | 2 +- .../using-git/using-advanced-git-commands.md | 2 +- .../using-git/using-common-git-commands.md | 2 +- .../using-git-rebase-on-the-command-line.md | 2 +- .../which-remote-url-should-i-use.md | 2 +- ...hy-is-git-always-asking-for-my-password.md | 2 +- .../about-repository-graphs.md | 2 +- .../about-the-dependency-graph.md | 91 ++-- .../accessing-basic-repository-data.md | 2 +- ...lyzing-changes-to-a-repositorys-content.md | 2 +- ...loring-the-dependencies-of-a-repository.md | 18 +- ...anding-connections-between-repositories.md | 2 +- ...nd-deletions-to-content-in-a-repository.md | 2 +- .../about-custom-domains-and-github-pages.md | 2 +- .../about-github-pages-and-jekyll.md | 4 +- .../about-github-pages.md | 24 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 4 +- ...ithub-pages-site-with-the-theme-chooser.md | 2 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...he-visibility-of-your-github-pages-site.md | 27 + ...ustom-domain-for-your-github-pages-site.md | 2 +- ...tom-404-page-for-your-github-pages-site.md | 4 +- ...reating-a-github-pages-site-with-jekyll.md | 5 +- .../creating-a-github-pages-site.md | 9 +- .../getting-started-with-github-pages.md | 2 +- .../github/working-with-github-pages/index.md | 3 +- ...ustom-domain-for-your-github-pages-site.md | 2 +- ...for-your-github-pages-site-using-jekyll.md | 2 +- ...ting-up-a-github-pages-site-with-jekyll.md | 2 +- ...r-github-pages-site-locally-with-jekyll.md | 2 +- ...yll-build-errors-for-github-pages-sites.md | 2 +- .../unpublishing-a-github-pages-site.md | 2 +- .../using-submodules-with-github-pages.md | 2 +- ...ium-support-for-github-enterprise-cloud.md | 2 +- .../about-github-support.md | 4 +- .../github-marketplace-support.md | 2 +- .../submitting-a-ticket.md | 2 +- .../writing-on-github/about-saved-replies.md | 2 +- .../about-writing-and-formatting-on-github.md | 2 +- .../autolinked-references-and-urls.md | 2 +- .../basic-writing-and-formatting-syntax.md | 20 +- .../creating-a-saved-reply.md | 2 +- .../creating-and-highlighting-code-blocks.md | 2 +- .../writing-on-github/creating-gists.md | 14 +- .../editing-a-saved-reply.md | 2 +- .../editing-and-sharing-content-with-gists.md | 2 +- .../forking-and-cloning-gists.md | 2 +- ...d-with-writing-and-formatting-on-github.md | 2 +- .../organizing-information-with-tables.md | 12 +- .../writing-on-github/using-saved-replies.md | 2 +- .../working-with-advanced-formatting.md | 2 +- .../working-with-saved-replies.md | 2 +- .../guides/forming-calls-with-graphql.md | 2 +- .../graphql/guides/introduction-to-graphql.md | 38 +- .../guides/managing-enterprise-accounts.md | 2 +- .../viewing-key-metrics-and-reports.md | 2 +- .../about-data-in-github-insights.md | 2 +- .../about-github-insights.md | 2 +- .../configuring-github-insights.md | 2 +- ...n-github-insights-and-github-enterprise.md | 2 +- ...installing-and-updating-github-insights.md | 2 +- .../installing-github-insights.md | 3 +- .../managing-data-in-github-insights.md | 2 +- .../guides/about-github-container-registry.md | 99 ++-- ...ache-maven-for-use-with-github-packages.md | 12 +- ...ing-docker-for-use-with-github-packages.md | 4 +- ...dotnet-cli-for-use-with-github-packages.md | 12 +- ...ing-gradle-for-use-with-github-packages.md | 2 +- ...guring-npm-for-use-with-github-packages.md | 16 +- ...g-rubygems-for-use-with-github-packages.md | 8 +- .../container-guides-for-github-packages.md | 2 +- .../guides/deleting-a-container-image.md | 32 +- ...ckage-client-guides-for-github-packages.md | 2 +- ...ing-github-packages-with-github-actions.md | 35 +- translations/es-ES/content/packages/index.md | 20 +- .../about-github-packages.md | 164 +++--- .../manage-packages/deleting-a-package.md | 4 +- .../manage-packages/viewing-packages.md | 4 +- .../es-ES/content/packages/quickstart.md | 2 +- translations/es-ES/content/rest/index.md | 2 +- .../es-ES/content/rest/overview/libraries.md | 6 +- .../content/rest/overview/media-types.md | 2 +- .../overview/resources-in-the-rest-api.md | 18 +- .../es-ES/content/rest/reference/activity.md | 8 +- .../es-ES/content/rest/reference/checks.md | 2 +- .../rest/reference/enterprise-admin.md | 248 ++++----- .../es-ES/content/rest/reference/git.md | 2 +- .../content/rest/reference/interactions.md | 2 +- .../content/rest/reference/migrations.md | 2 +- .../es-ES/content/rest/reference/orgs.md | 2 +- .../permissions-required-for-github-apps.md | 11 +- .../es-ES/content/rest/reference/pulls.md | 2 +- .../es-ES/content/rest/reference/repos.md | 2 +- .../es-ES/content/rest/reference/search.md | 4 +- .../es-ES/data/glossaries/candidates.yml | 196 +++---- .../es-ES/data/glossaries/external.yml | 352 ++++++------- .../es-ES/data/glossaries/internal.yml | 252 ++++----- .../es-ES/data/learning-tracks/README.md | 3 + .../es-ES/data/learning-tracks/actions.yml | 23 +- translations/es-ES/data/products.yml | 2 +- .../es-ES/data/release-notes/2-20/11.yml | 3 +- .../es-ES/data/release-notes/2-20/12.yml | 3 +- .../es-ES/data/release-notes/2-20/15.yml | Bin 4546 -> 5369 bytes .../es-ES/data/release-notes/2-20/16.yml | 5 +- .../es-ES/data/release-notes/2-20/17.yml | 3 +- .../es-ES/data/release-notes/2-20/18.yml | 5 +- .../es-ES/data/release-notes/2-20/5.yml | 3 +- .../es-ES/data/release-notes/2-20/7.yml | 3 +- .../es-ES/data/release-notes/2-21/0.yml | 7 +- .../es-ES/data/release-notes/2-21/2.yml | 3 +- .../es-ES/data/release-notes/2-21/3.yml | 5 +- .../es-ES/data/release-notes/2-21/6.yml | Bin 5014 -> 5795 bytes .../es-ES/data/release-notes/2-21/7.yml | 5 +- .../es-ES/data/release-notes/2-21/8.yml | 3 +- .../es-ES/data/release-notes/2-21/9.yml | 5 +- .../es-ES/data/release-notes/2-22/0.yml | 123 ++--- .../es-ES/data/release-notes/2-22/1.yml | 29 +- .../es-ES/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../es-ES/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../actions/actions-use-policy-settings.md | 2 +- .../actions/allow-specific-actions-intro.md | 2 +- .../actions/enterprise-actions-permissions.md | 6 +- .../data/reusables/actions/enterprise-beta.md | 2 +- .../actions/enterprise-common-prereqs.md | 2 +- .../actions/enterprise-enable-checkbox.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../actions/enterprise-http-proxy.md | 2 +- .../actions/enterprise-limit-actions-use.md | 2 +- .../enterprise-postinstall-nextsteps.md | 2 +- .../actions/enterprise-s3-permission.md | 2 +- .../actions/enterprise-s3-support-warning.md | 2 +- .../actions/enterprise-self-signed-cert.md | 2 +- .../actions/enterprise-storage-ha-backups.md | 2 +- .../actions/workflow-template-overview.md | 2 +- .../note-org-enable-uses-seats.md | 2 +- .../audit_log/exported-log-keys-and-values.md | 2 +- .../audit_log/keys-and-example-values.md | 2 +- .../data/reusables/code-scanning/beta.md | 2 +- .../false-positive-fix-codeql.md | 2 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../community/interaction-limits-duration.md | 2 +- .../interaction-limits-restrictions.md | 2 +- .../community/set-interaction-limit.md | 2 +- .../community/types-of-interaction-limits.md | 8 +- .../dependabot/private-dependencies-note.md | 2 +- .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../pages-policies-save.md | 2 +- .../enterprise-accounts/pages-tab.md | 2 +- .../user-provisioning-release-stage.md | 2 +- .../enterprise-managed/about-billing.md | 2 +- .../hardware-considerations-all-platforms.md | 10 +- .../hardware-rec-table.md | 8 +- .../ssh-into-instance.md | 2 +- .../enterprise_management_console/actions.md | 2 +- .../advanced-security-license.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../about-ssh-access.md | 2 +- .../about-the-management-console.md | 2 +- .../about-the-site-admin-dashboard.md | 2 +- .../message-preview-save.md | 2 +- .../repository-search.md | 2 +- .../search-user-or-org.md | 2 +- .../search-user.md | 2 +- .../gated-features/actions-shared.md | 2 +- .../reusables/gated-features/code-scanning.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../gated-features/protected-branches.md | 2 +- .../gated-features/repository-insights.md | 2 +- .../data/reusables/gated-features/saml-sso.md | 2 +- .../ssh-certificate-authorities.md | 2 +- .../cannot-convert-public-gists-to-secret.md | 2 +- .../github-actions/actions-billing.md | 2 +- .../disabling-github-actions.md | 2 +- .../enabled-local-github-actions.md | 2 +- .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- ...ed-runner-configure-runner-group-access.md | 2 +- ...-runner-management-permissions-required.md | 2 +- ...-runner-navigate-to-repo-org-enterprise.md | 4 +- .../self-hosted-runner-public-repo-access.md | 2 +- .../using-context-or-environment-variables.md | 10 +- .../data/reusables/github-ae/about-billing.md | 2 +- .../github-ae/github-ae-enables-you.md | 2 +- .../github-insights/contributors-tab.md | 2 +- .../revoking-identity-team-sync.md | 2 +- .../team-sync-confirm.md | 2 +- .../interactions/interactions-detail.md | 2 +- .../issue-event-common-properties.md | 2 +- .../can-include-lfs-objects-archives.md | 2 +- .../reusables/large_files/rejected_pushes.md | 2 +- .../large_files/storage_assets_location.md | 4 +- .../marketplace/downgrade-marketplace-only.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../data/reusables/mobile/about-mobile.md | 2 +- .../reusables/mobile/ghes-release-phase.md | 2 +- .../mobile/push-notifications-on-ghes.md | 2 +- ...nerable-dependency-notification-options.md | 18 +- .../organizations/can-require-ssh-cert.md | 2 +- .../organizations/click-codespaces.md | 2 +- .../reseller-ask-to-become-billing-manager.md | 2 +- .../organizations/team-synchronization.md | 2 +- .../package_registry/authenticate-packages.md | 12 +- .../enable-enterprise-github-packages.md | 2 +- ...ext-steps-for-packages-enterprise-setup.md | 4 +- .../packages-cluster-support.md | 2 +- .../packages-ghes-release-stage.md | 2 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../es-ES/data/reusables/pages/visit-site.md | 2 +- .../project-management/choose-visibility.md | 2 +- .../project-board-visibility.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- .../required-reviews-for-prs-summary.md | 2 +- .../repositories/branch-rules-example.md | 2 +- .../reusables/repositories/reaction_list.md | 2 +- .../repositories/return-to-source-diff.md | 4 +- .../review-policy-overlapping-commits.md | 2 +- ...quash-and-rebase-linear-commit-hisitory.md | 2 +- .../repositories/workflow-notifications.md | 2 +- ...ut-user-provisioning-enterprise-account.md | 2 +- .../reusables/saml/dotcom-saml-explanation.md | 2 +- .../secret-scanning/about-secret-scanning.md | 2 +- .../data/reusables/secret-scanning/beta.md | 2 +- .../partner-secret-list-private-repo.md | 140 ++--- .../partner-secret-list-public-repo.md | 138 ++--- .../data/reusables/support/ghae-priorities.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../codespaces-secret-repository-access.md | 2 +- .../user_settings/codespaces-secret-value.md | 2 +- .../reusables/user_settings/codespaces-tab.md | 2 +- .../webhooks/check_run_properties.md | 4 +- .../webhooks/check_suite_properties.md | 2 +- .../code_scanning_alert_event_properties.md | 2 +- .../webhooks/commit_comment_properties.md | 8 +- .../reusables/webhooks/create_properties.md | 2 +- .../webhooks/deploy_key_properties.md | 2 +- .../reusables/webhooks/fork_properties.md | 2 +- .../webhooks/membership_properties.md | 12 +- .../webhooks/milestone_properties.md | 4 +- .../reusables/webhooks/package_properties.md | 2 +- .../webhooks/project_card_properties.md | 4 +- .../webhooks/project_column_properties.md | 4 +- .../reusables/webhooks/project_properties.md | 4 +- .../pull_request_review_properties.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../webhooks/repository_import_properties.md | 2 +- ...pository_vulnerability_alert_properties.md | 2 +- .../secret_scanning_alert_event_properties.md | 2 +- translations/es-ES/data/ui.yml | 28 +- .../data/variables/action_code_examples.yml | 42 +- .../es-ES/data/variables/enterprise.yml | 2 +- translations/es-ES/data/variables/gists.yml | 6 +- translations/es-ES/data/variables/product.yml | 19 +- .../actions/creating-actions/about-actions.md | 7 +- .../creating-a-composite-run-steps-action.md | 12 +- .../creating-a-docker-container-action.md | 40 +- .../creating-a-javascript-action.md | 7 +- .../dockerfile-support-for-github-actions.md | 11 +- .../metadata-syntax-for-github-actions.md | 2 +- .../setting-exit-codes-for-actions.md | 2 + .../guides/about-continuous-integration.md | 3 + .../about-packaging-with-github-actions.md | 4 +- .../guides/about-service-containers.md | 11 +- .../building-and-testing-java-with-ant.md | 14 +- .../building-and-testing-java-with-gradle.md | 33 +- .../building-and-testing-java-with-maven.md | 16 +- .../guides/building-and-testing-net.md | 4 +- .../guides/building-and-testing-nodejs.md | 28 +- .../guides/building-and-testing-powershell.md | 59 ++- .../guides/building-and-testing-python.md | 83 +-- .../guides/building-and-testing-ruby.md | 84 ++- ...hing-dependencies-to-speed-up-workflows.md | 22 +- .../creating-postgresql-service-containers.md | 19 +- .../creating-redis-service-containers.md | 19 +- ...ing-to-amazon-elastic-container-service.md | 81 +-- .../guides/deploying-to-azure-app-service.md | 61 ++- .../deploying-to-google-kubernetes-engine.md | 75 +-- .../ja-JP/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 16 +- .../publishing-java-packages-with-gradle.md | 19 +- .../publishing-java-packages-with-maven.md | 19 +- .../guides/publishing-nodejs-packages.md | 43 +- ...us-integration-using-workflow-templates.md | 5 +- .../storing-workflow-data-as-artifacts.md | 36 +- .../about-self-hosted-runners.md | 10 +- .../adding-self-hosted-runners.md | 22 +- ...-hosted-runner-application-as-a-service.md | 6 +- ...ess-to-self-hosted-runners-using-groups.md | 12 +- .../removing-self-hosted-runners.md | 6 +- ...a-proxy-server-with-self-hosted-runners.md | 4 +- .../using-labels-with-self-hosted-runners.md | 4 +- ...using-self-hosted-runners-in-a-workflow.md | 15 +- translations/ja-JP/content/actions/index.md | 33 +- .../essential-features-of-github-actions.md | 14 +- .../finding-and-customizing-actions.md | 12 +- .../introduction-to-github-actions.md | 28 +- .../managing-complex-workflows.md | 12 +- ...-from-azure-pipelines-to-github-actions.md | 189 +++---- ...grating-from-circleci-to-github-actions.md | 99 ++-- ...ting-from-gitlab-cicd-to-github-actions.md | 71 +-- ...igrating-from-jenkins-to-github-actions.md | 176 +++---- ...rating-from-travis-ci-to-github-actions.md | 193 +++---- .../security-hardening-for-github-actions.md | 90 ++-- ...haring-workflows-with-your-organization.md | 4 +- .../adding-a-workflow-status-badge.md | 8 +- .../canceling-a-workflow.md | 4 +- .../disabling-and-enabling-a-workflow.md | 6 +- .../downloading-workflow-artifacts.md | 10 +- .../actions/managing-workflow-runs/index.md | 2 +- .../manually-running-a-workflow.md | 6 +- .../re-running-a-workflow.md | 2 +- .../removing-workflow-artifacts.md | 23 +- .../reviewing-deployments.md | 24 +- .../using-the-visualization-graph.md | 8 +- .../using-workflow-run-logs.md | 15 +- .../viewing-job-execution-time.md | 2 +- .../ja-JP/content/actions/quickstart.md | 69 +-- .../reference/authentication-in-a-workflow.md | 8 +- ...nd-expression-syntax-for-github-actions.md | 99 ++-- .../actions/reference/encrypted-secrets.md | 32 +- .../reference/environment-variables.md | 42 +- .../content/actions/reference/environments.md | 54 +- .../events-that-trigger-workflows.md | 18 +- .../ja-JP/content/actions/reference/index.md | 6 +- ...pecifications-for-github-hosted-runners.md | 12 +- ...usage-limits-billing-and-administration.md | 14 +- .../workflow-commands-for-github-actions.md | 36 +- .../workflow-syntax-for-github-actions.md | 113 ++-- ...d-access-management-for-your-enterprise.md | 18 +- .../changing-authentication-methods.md | 2 +- ...ning-for-your-enterprise-using-azure-ad.md | 30 +- ...rovisioning-with-your-identity-provider.md | 4 +- ...saml-single-sign-on-for-your-enterprise.md | 66 +-- ...g-user-provisioning-for-your-enterprise.md | 62 +-- .../content/admin/authentication/index.md | 2 +- ...identity-and-access-for-your-enterprise.md | 6 +- .../content/admin/authentication/using-cas.md | 2 +- .../configuration/command-line-utilities.md | 16 +- .../configuration/configuring-applications.md | 2 +- .../configuring-email-for-notifications.md | 8 +- .../about-geo-replication.md | 2 +- .../configuring-collectd.md | 2 +- ...-availability-replication-for-a-cluster.md | 4 +- .../evacuating-a-cluster-node.md | 10 + .../initializing-the-cluster.md | 2 +- ...ng-a-failover-to-your-replica-appliance.md | 6 +- .../removing-a-high-availability-replica.md | 2 +- .../upgrade-requirements.md | 2 +- .../upgrading-github-enterprise-server.md | 2 +- .../about-github-enterprise-support.md | 41 +- .../about-support-for-advanced-security.md | 2 +- .../preparing-to-submit-a-ticket.md | 4 +- .../providing-data-to-github-support.md | 14 +- .../reaching-github-support.md | 4 +- .../receiving-help-from-github-support.md | 2 +- .../enterprise-support/submitting-a-ticket.md | 14 +- ...ing-actions-on-github-enterprise-server.md | 12 +- ...anced-configuration-and-troubleshooting.md | 4 +- ...rise-server-with-github-actions-enabled.md | 24 +- ...-githubcom-actions-using-github-connect.md | 2 +- ...ub-actions-for-github-enterprise-server.md | 4 +- ...g-github-actions-with-amazon-s3-storage.md | 20 +- ...-github-actions-with-azure-blob-storage.md | 20 +- ...ions-with-minio-gateway-for-nas-storage.md | 24 +- ...ub-actions-policies-for-your-enterprise.md | 2 +- ...ub-actions-for-github-enterprise-server.md | 42 +- .../high-availability-for-github-actions.md | 24 +- ...manually-syncing-actions-from-githubcom.md | 8 +- ...-hosted-runners-without-internet-access.md | 4 +- ...ting-github-actions-for-your-enterprise.md | 92 ++-- .../using-a-staging-environment.md | 18 +- translations/ja-JP/content/admin/index.md | 2 +- ...talling-github-enterprise-server-on-aws.md | 4 +- ...lling-github-enterprise-server-on-azure.md | 14 +- ...erprise-server-on-google-cloud-platform.md | 4 +- ...ing-github-enterprise-server-on-hyper-v.md | 6 +- ...thub-enterprise-server-on-openstack-kvm.md | 4 +- ...ling-github-enterprise-server-on-vmware.md | 4 +- ...g-github-enterprise-server-on-xenserver.md | 4 +- .../setting-up-a-staging-instance.md | 2 +- .../overview/about-enterprise-accounts.md | 18 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../about-the-github-enterprise-api.md | 10 +- .../about-upgrades-to-new-releases.md | 24 +- .../ja-JP/content/admin/overview/index.md | 3 +- .../managing-billing-for-your-enterprise.md | 34 +- ...managing-your-github-enterprise-license.md | 28 +- .../content/admin/overview/system-overview.md | 4 +- .../creating-a-pre-receive-hook-script.md | 43 +- ...-management-policies-in-your-enterprise.md | 32 +- .../ja-JP/content/admin/release-notes.md | 2 +- .../user-management/activity-dashboard.md | 6 +- .../admin/user-management/audit-logging.md | 10 +- .../admin/user-management/audited-actions.md | 171 +++--- .../auditing-users-across-your-enterprise.md | 18 +- .../best-practices-for-user-security.md | 4 +- ...-large-file-storage-for-your-enterprise.md | 8 +- ...-visibility-for-organization-membership.md | 4 +- ...bling-git-ssh-access-on-your-enterprise.md | 6 +- .../content/admin/user-management/index.md | 2 +- .../migrating-to-internal-repositories.md | 4 +- .../user-management/viewing-push-logs.md | 9 +- .../managing-tags.md | 11 + .../creating-a-github-app-from-a-manifest.md | 4 +- .../creating-ci-tests-with-the-checks-api.md | 10 +- ...nces-between-github-apps-and-oauth-apps.md | 3 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 8 + .../developers/github-marketplace/index.md | 7 +- .../requirements-for-listing-an-app.md | 11 +- .../setting-pricing-plans-for-your-listing.md | 10 +- ...submitting-your-listing-for-publication.md | 30 +- .../developers/overview/secret-scanning.md | 77 ++- .../ja-JP/content/discussions/index.md | 8 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../ja-JP/content/education/guides.md | 10 +- translations/ja-JP/content/education/index.md | 12 +- .../basics-of-setting-up-github-classroom.md | 2 +- ...g-management-system-to-github-classroom.md | 4 +- .../create-a-group-assignment.md | 2 +- ...n-assignment-from-a-template-repository.md | 2 - .../create-an-individual-assignment.md | 2 +- .../index.md | 1 - .../teach-with-github-classroom.md | 3 + .../changing-the-default-branch.md | 2 +- .../renaming-a-branch.md | 13 + ...moving-sensitive-data-from-a-repository.md | 4 +- .../blocking-a-user-from-your-organization.md | 3 +- ...cking-a-user-from-your-personal-account.md | 6 +- ...ngle-issue-template-for-your-repository.md | 2 +- ...a-merge-conflict-using-the-command-line.md | 16 +- .../working-with-pre-receive-hooks.md | 2 +- .../about-github-marketplace.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 10 +- ...ode-scanning-alerts-for-your-repository.md | 2 + ...-codeql-code-scanning-in-your-ci-system.md | 2 + .../sarif-support-for-code-scanning.md | 6 +- .../uploading-a-sarif-file-to-github.md | 2 + .../about-github-advanced-security.md | 32 +- .../git-and-github-learning-resources.md | 12 +- .../git-cheatsheet.md | 2 +- .../github-for-mobile.md | 10 +- .../githubs-products.md | 1 + .../keyboard-shortcuts.md | 6 +- ...roject-to-github-using-the-command-line.md | 18 +- .../navigating-code-on-github.md | 2 +- .../publishing-a-security-advisory.md | 12 + ...sferring-an-issue-to-another-repository.md | 2 +- .../about-email-notifications.md | 3 +- .../searching-issues-and-pull-requests.md | 3 +- ...unted-subscriptions-for-github-accounts.md | 4 +- .../index.md | 2 +- ...ithub-pages-sites-for-your-organization.md | 30 ++ .../permission-levels-for-an-organization.md | 181 +++---- ...y-permission-levels-for-an-organization.md | 206 ++++---- ...ing-the-audit-log-for-your-organization.md | 93 ++-- ...-management-for-your-enterprise-account.md | 18 +- ...dio-subscription-with-github-enterprise.md | 4 +- .../managing-your-profile-readme.md | 2 + ...on-levels-for-a-user-account-repository.md | 19 +- .../types-of-emails-github-sends.md | 13 +- .../github-additional-product-terms.md | 2 +- .../site-policy/github-and-trade-controls.md | 25 +- .../github-subprocessors-and-cookies.md | 46 +- ...delines-for-legal-requests-of-user-data.md | 9 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../about-github-pages-and-jekyll.md | 4 +- .../about-github-pages.md | 24 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...he-visibility-of-your-github-pages-site.md | 27 + ...tom-404-page-for-your-github-pages-site.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 5 +- .../creating-a-github-pages-site.md | 7 +- .../github/working-with-github-pages/index.md | 1 + ...yll-build-errors-for-github-pages-sites.md | 2 +- .../unpublishing-a-github-pages-site.md | 2 +- .../basic-writing-and-formatting-syntax.md | 16 +- .../organizing-information-with-tables.md | 10 +- translations/ja-JP/content/graphql/README.md | 2 +- .../graphql/guides/introduction-to-graphql.md | 38 +- .../guides/managing-enterprise-accounts.md | 2 +- .../graphql/overview/resource-limitations.md | 2 +- ...n-github-insights-and-github-enterprise.md | 2 +- .../installing-github-insights.md | 1 + ...ache-maven-for-use-with-github-packages.md | 10 +- ...guring-npm-for-use-with-github-packages.md | 6 +- ...g-rubygems-for-use-with-github-packages.md | 6 +- translations/ja-JP/content/packages/index.md | 11 +- .../manage-packages/deleting-a-package.md | 4 +- .../ja-JP/content/packages/quickstart.md | 2 +- .../ja-JP/content/rest/overview/libraries.md | 4 + .../permissions-required-for-github-apps.md | 11 +- .../ja-JP/data/glossaries/external.yml | 6 +- .../ja-JP/data/learning-tracks/README.md | 3 + .../ja-JP/data/learning-tracks/actions.yml | 7 + .../ja-JP/data/release-notes/2-20/0.yml | 72 +-- .../ja-JP/data/release-notes/2-20/1.yml | 30 +- .../ja-JP/data/release-notes/2-20/10.yml | 30 +- .../ja-JP/data/release-notes/2-20/11.yml | 26 +- .../ja-JP/data/release-notes/2-20/12.yml | 20 +- .../ja-JP/data/release-notes/2-20/13.yml | 32 +- .../ja-JP/data/release-notes/2-20/14.yml | 16 +- .../ja-JP/data/release-notes/2-20/16.yml | 16 +- .../ja-JP/data/release-notes/2-20/17.yml | 16 +- .../ja-JP/data/release-notes/2-20/18.yml | 38 +- .../ja-JP/data/release-notes/2-20/19.yml | 16 +- .../ja-JP/data/release-notes/2-20/2.yml | 42 +- .../ja-JP/data/release-notes/2-20/20.yml | 20 +- .../ja-JP/data/release-notes/2-20/21.yml | 18 +- .../ja-JP/data/release-notes/2-20/22.yml | 28 +- .../ja-JP/data/release-notes/2-20/23.yml | 16 +- .../ja-JP/data/release-notes/2-20/3.yml | 20 +- .../ja-JP/data/release-notes/2-20/4.yml | 26 +- .../ja-JP/data/release-notes/2-20/5.yml | 28 +- .../ja-JP/data/release-notes/2-20/6.yml | 40 +- .../ja-JP/data/release-notes/2-20/7.yml | 30 +- .../ja-JP/data/release-notes/2-20/8.yml | 28 +- .../ja-JP/data/release-notes/2-20/9.yml | 22 +- .../ja-JP/data/release-notes/2-21/0.yml | 86 +-- .../ja-JP/data/release-notes/2-21/1.yml | 2 +- .../ja-JP/data/release-notes/2-21/10.yml | 2 +- .../ja-JP/data/release-notes/2-21/11.yml | 2 +- .../ja-JP/data/release-notes/2-21/12.yml | 2 +- .../ja-JP/data/release-notes/2-21/13.yml | 2 +- .../ja-JP/data/release-notes/2-21/14.yml | 2 +- .../ja-JP/data/release-notes/2-21/2.yml | 2 +- .../ja-JP/data/release-notes/2-21/3.yml | 2 +- .../ja-JP/data/release-notes/2-21/4.yml | 2 +- .../ja-JP/data/release-notes/2-21/5.yml | 2 +- .../ja-JP/data/release-notes/2-21/7.yml | 2 +- .../ja-JP/data/release-notes/2-21/8.yml | 2 +- .../ja-JP/data/release-notes/2-21/9.yml | 4 +- .../ja-JP/data/release-notes/2-22/1.yml | 2 +- .../ja-JP/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../ja-JP/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../actions/enterprise-limit-actions-use.md | 2 +- .../actions/enterprise-marketplace-actions.md | 2 +- .../classroom/guide-create-new-classroom.md | 2 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../ssh-into-instance.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../github-actions/actions-billing.md | 2 +- .../artifact-log-retention-statement.md | 2 +- .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../reseller-ask-to-become-billing-manager.md | 2 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../ja-JP/data/reusables/pages/visit-site.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- .../navigate-to-job-superlinter.md | 2 +- ...ut-user-provisioning-enterprise-account.md | 2 +- ...tact-support-if-your-idp-is-unavailable.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../pull_request_webhook_properties.md | 6 +- translations/ja-JP/data/ui.yml | 12 +- translations/ja-JP/data/variables/product.yml | 1 + .../actions/creating-actions/about-actions.md | 7 +- .../creating-a-composite-run-steps-action.md | 10 +- .../creating-a-docker-container-action.md | 40 +- .../creating-a-javascript-action.md | 5 +- .../dockerfile-support-for-github-actions.md | 9 +- .../setting-exit-codes-for-actions.md | 2 + .../guides/about-continuous-integration.md | 5 +- .../about-packaging-with-github-actions.md | 4 +- .../guides/about-service-containers.md | 9 +- .../building-and-testing-java-with-ant.md | 12 +- .../building-and-testing-java-with-gradle.md | 31 +- .../building-and-testing-java-with-maven.md | 14 +- .../guides/building-and-testing-net.md | 4 +- .../guides/building-and-testing-nodejs.md | 28 +- .../guides/building-and-testing-powershell.md | 5 +- .../guides/building-and-testing-python.md | 69 +-- .../guides/building-and-testing-ruby.md | 18 +- ...hing-dependencies-to-speed-up-workflows.md | 14 +- .../creating-postgresql-service-containers.md | 19 +- .../creating-redis-service-containers.md | 19 +- ...ing-to-amazon-elastic-container-service.md | 5 + .../guides/deploying-to-azure-app-service.md | 5 + .../deploying-to-google-kubernetes-engine.md | 5 + .../ko-KR/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 12 +- .../publishing-java-packages-with-gradle.md | 19 +- .../publishing-java-packages-with-maven.md | 17 +- .../guides/publishing-nodejs-packages.md | 21 +- ...us-integration-using-workflow-templates.md | 5 +- .../storing-workflow-data-as-artifacts.md | 10 +- ...a-proxy-server-with-self-hosted-runners.md | 4 +- ...using-self-hosted-runners-in-a-workflow.md | 13 +- translations/ko-KR/content/actions/index.md | 17 +- .../essential-features-of-github-actions.md | 4 +- .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 8 +- .../managing-complex-workflows.md | 2 + ...-from-azure-pipelines-to-github-actions.md | 155 +++--- ...grating-from-circleci-to-github-actions.md | 85 +-- ...ting-from-gitlab-cicd-to-github-actions.md | 45 +- ...igrating-from-jenkins-to-github-actions.md | 176 +++---- ...rating-from-travis-ci-to-github-actions.md | 77 +-- .../security-hardening-for-github-actions.md | 8 +- .../adding-a-workflow-status-badge.md | 8 +- .../manually-running-a-workflow.md | 2 +- .../ko-KR/content/actions/quickstart.md | 3 + ...nd-expression-syntax-for-github-actions.md | 43 +- .../reference/environment-variables.md | 22 +- .../workflow-commands-for-github-actions.md | 20 +- .../workflow-syntax-for-github-actions.md | 23 +- .../configuration/command-line-utilities.md | 16 +- .../configuring-email-for-notifications.md | 8 +- ...-availability-replication-for-a-cluster.md | 2 +- .../evacuating-a-cluster-node.md | 10 + .../initializing-the-cluster.md | 2 +- .../about-github-enterprise-support.md | 1 - ...manually-syncing-actions-from-githubcom.md | 2 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../ko-KR/content/admin/overview/index.md | 1 + ...managing-your-github-enterprise-license.md | 24 +- .../creating-a-pre-receive-hook-script.md | 43 +- .../admin/user-management/audited-actions.md | 4 +- .../migrating-to-internal-repositories.md | 4 +- .../user-management/viewing-push-logs.md | 9 +- .../managing-tags.md | 11 + .../creating-a-github-app-from-a-manifest.md | 4 +- .../creating-ci-tests-with-the-checks-api.md | 10 +- ...nces-between-github-apps-and-oauth-apps.md | 3 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 8 + .../developers/github-marketplace/index.md | 7 +- .../requirements-for-listing-an-app.md | 11 +- .../setting-pricing-plans-for-your-listing.md | 8 +- ...submitting-your-listing-for-publication.md | 30 +- .../developers/overview/secret-scanning.md | 77 ++- .../ko-KR/content/discussions/index.md | 4 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../ko-KR/content/education/guides.md | 10 +- translations/ko-KR/content/education/index.md | 12 +- .../basics-of-setting-up-github-classroom.md | 2 +- .../create-a-group-assignment.md | 2 +- ...n-assignment-from-a-template-repository.md | 2 - .../create-an-individual-assignment.md | 2 +- .../index.md | 1 - .../teach-with-github-classroom.md | 3 + ...fications-for-pushes-to-your-repository.md | 4 +- .../changing-the-default-branch.md | 2 +- .../renaming-a-branch.md | 13 + ...authentication-with-saml-single-sign-on.md | 14 +- ...moving-sensitive-data-from-a-repository.md | 4 +- .../blocking-a-user-from-your-organization.md | 3 +- ...cking-a-user-from-your-personal-account.md | 6 +- ...ngle-issue-template-for-your-repository.md | 2 +- ...a-merge-conflict-using-the-command-line.md | 16 +- .../working-with-pre-receive-hooks.md | 2 +- .../about-github-marketplace.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 10 +- ...ode-scanning-alerts-for-your-repository.md | 2 + ...-codeql-code-scanning-in-your-ci-system.md | 2 + .../sarif-support-for-code-scanning.md | 6 +- .../uploading-a-sarif-file-to-github.md | 2 + .../about-github-advanced-security.md | 2 +- .../git-and-github-learning-resources.md | 10 +- .../git-cheatsheet.md | 2 +- .../githubs-products.md | 1 + .../keyboard-shortcuts.md | 6 +- ...roject-to-github-using-the-command-line.md | 6 +- .../navigating-code-on-github.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 2 + .../publishing-a-security-advisory.md | 12 + .../configuring-notifications.md | 3 +- ...sferring-an-issue-to-another-repository.md | 2 +- .../about-email-notifications.md | 3 +- .../searching-issues-and-pull-requests.md | 3 +- ...unted-subscriptions-for-github-accounts.md | 4 +- .../index.md | 2 +- ...ithub-pages-sites-for-your-organization.md | 30 ++ .../permission-levels-for-an-organization.md | 181 +++---- ...y-permission-levels-for-an-organization.md | 206 ++++---- ...ing-the-audit-log-for-your-organization.md | 75 +-- ...-management-for-your-enterprise-account.md | 16 +- ...dio-subscription-with-github-enterprise.md | 4 +- .../managing-your-profile-readme.md | 2 + ...on-levels-for-a-user-account-repository.md | 19 +- .../types-of-emails-github-sends.md | 13 +- .../github-additional-product-terms.md | 2 +- .../site-policy/github-and-trade-controls.md | 25 +- .../github-subprocessors-and-cookies.md | 46 +- ...delines-for-legal-requests-of-user-data.md | 9 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../about-github-pages-and-jekyll.md | 4 +- .../about-github-pages.md | 16 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...he-visibility-of-your-github-pages-site.md | 27 + ...tom-404-page-for-your-github-pages-site.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 5 +- .../creating-a-github-pages-site.md | 7 +- .../github/working-with-github-pages/index.md | 1 + ...yll-build-errors-for-github-pages-sites.md | 2 +- .../unpublishing-a-github-pages-site.md | 2 +- .../basic-writing-and-formatting-syntax.md | 16 +- .../organizing-information-with-tables.md | 10 +- .../graphql/guides/introduction-to-graphql.md | 38 +- ...n-github-insights-and-github-enterprise.md | 2 +- .../installing-github-insights.md | 1 + ...ache-maven-for-use-with-github-packages.md | 10 +- ...guring-npm-for-use-with-github-packages.md | 6 +- ...g-rubygems-for-use-with-github-packages.md | 6 +- translations/ko-KR/content/packages/index.md | 11 +- .../manage-packages/deleting-a-package.md | 4 +- .../ko-KR/content/rest/overview/libraries.md | 4 + .../permissions-required-for-github-apps.md | 11 +- .../ko-KR/data/glossaries/external.yml | 6 +- .../ko-KR/data/learning-tracks/README.md | 3 + .../ko-KR/data/learning-tracks/actions.yml | 7 + .../ko-KR/data/release-notes/2-20/18.yml | 2 +- .../ko-KR/data/release-notes/2-21/9.yml | 2 +- .../ko-KR/data/release-notes/2-22/1.yml | 2 +- .../ko-KR/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../ko-KR/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../ssh-into-instance.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../github-actions/actions-billing.md | 2 +- .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../reseller-ask-to-become-billing-manager.md | 2 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../ko-KR/data/reusables/pages/visit-site.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- ...ut-user-provisioning-enterprise-account.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../pull_request_webhook_properties.md | 6 +- translations/ko-KR/data/ui.yml | 12 +- translations/ko-KR/data/variables/product.yml | 1 + .../actions/creating-actions/about-actions.md | 7 +- .../creating-a-composite-run-steps-action.md | 8 +- .../creating-a-docker-container-action.md | 36 +- .../creating-a-javascript-action.md | 3 + .../dockerfile-support-for-github-actions.md | 9 +- .../metadata-syntax-for-github-actions.md | 2 +- .../setting-exit-codes-for-actions.md | 2 + .../guides/about-continuous-integration.md | 5 +- .../about-packaging-with-github-actions.md | 4 +- .../guides/about-service-containers.md | 9 +- .../building-and-testing-java-with-ant.md | 10 +- .../building-and-testing-java-with-gradle.md | 29 +- .../building-and-testing-java-with-maven.md | 12 +- .../guides/building-and-testing-net.md | 4 +- .../guides/building-and-testing-nodejs.md | 47 +- .../guides/building-and-testing-powershell.md | 3 + .../guides/building-and-testing-python.md | 67 +-- .../guides/building-and-testing-ruby.md | 16 +- ...hing-dependencies-to-speed-up-workflows.md | 12 +- .../creating-postgresql-service-containers.md | 17 +- .../creating-redis-service-containers.md | 17 +- ...ing-to-amazon-elastic-container-service.md | 5 + .../guides/deploying-to-azure-app-service.md | 5 + .../deploying-to-google-kubernetes-engine.md | 5 + .../pt-BR/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 13 +- .../publishing-java-packages-with-gradle.md | 17 +- .../publishing-java-packages-with-maven.md | 15 +- .../guides/publishing-nodejs-packages.md | 71 ++- ...us-integration-using-workflow-templates.md | 3 + .../storing-workflow-data-as-artifacts.md | 8 +- .../about-self-hosted-runners.md | 2 +- ...a-proxy-server-with-self-hosted-runners.md | 2 +- ...using-self-hosted-runners-in-a-workflow.md | 11 +- translations/pt-BR/content/actions/index.md | 17 +- .../essential-features-of-github-actions.md | 4 +- .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 8 +- .../managing-complex-workflows.md | 76 +-- ...-from-azure-pipelines-to-github-actions.md | 195 +++---- ...grating-from-circleci-to-github-actions.md | 127 ++--- ...ting-from-gitlab-cicd-to-github-actions.md | 43 +- ...igrating-from-jenkins-to-github-actions.md | 174 +++---- ...rating-from-travis-ci-to-github-actions.md | 79 +-- .../security-hardening-for-github-actions.md | 10 +- ...haring-workflows-with-your-organization.md | 9 +- .../adding-a-workflow-status-badge.md | 8 +- .../manually-running-a-workflow.md | 2 +- .../pt-BR/content/actions/quickstart.md | 19 +- ...nd-expression-syntax-for-github-actions.md | 76 ++- .../reference/environment-variables.md | 32 +- .../events-that-trigger-workflows.md | 5 +- ...pecifications-for-github-hosted-runners.md | 39 +- .../workflow-commands-for-github-actions.md | 24 +- .../configuration/command-line-utilities.md | 29 +- ...onfiguring-an-outbound-web-proxy-server.md | 4 +- .../configuring-backups-on-your-appliance.md | 8 + ...guring-code-scanning-for-your-appliance.md | 33 +- .../configuring-email-for-notifications.md | 8 +- ...ring-secret-scanning-for-your-appliance.md | 6 +- .../enabling-subdomain-isolation.md | 37 +- .../content/admin/configuration/index.md | 2 + ...g-github-for-mobile-for-your-enterprise.md | 2 +- .../enterprise-management/about-clustering.md | 2 + ...-availability-replication-for-a-cluster.md | 2 +- .../evacuating-a-cluster-node.md | 10 + .../admin/enterprise-management/index.md | 1 - .../initializing-the-cluster.md | 2 +- .../removing-a-high-availability-replica.md | 8 + .../upgrading-github-enterprise-server.md | 6 + .../about-github-enterprise-support.md | 1 - .../providing-data-to-github-support.md | 2 + ...-githubcom-actions-using-github-connect.md | 3 +- ...g-github-actions-with-amazon-s3-storage.md | 4 +- ...-github-actions-with-azure-blob-storage.md | 12 +- ...ions-with-minio-gateway-for-nas-storage.md | 6 +- ...ub-actions-policies-for-your-enterprise.md | 1 - .../high-availability-for-github-actions.md | 2 +- .../content/admin/github-actions/index.md | 19 +- ...manually-syncing-actions-from-githubcom.md | 6 +- ...ting-github-actions-for-your-enterprise.md | 76 +-- .../using-a-staging-environment.md | 18 +- ...talling-github-enterprise-server-on-aws.md | 3 +- ...lling-github-enterprise-server-on-azure.md | 6 +- ...erprise-server-on-google-cloud-platform.md | 3 +- ...ing-github-enterprise-server-on-hyper-v.md | 3 +- ...thub-enterprise-server-on-openstack-kvm.md | 3 +- ...ling-github-enterprise-server-on-vmware.md | 3 +- ...g-github-enterprise-server-on-xenserver.md | 3 +- .../setting-up-a-staging-instance.md | 6 + .../overview/about-enterprise-accounts.md | 6 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../about-upgrades-to-new-releases.md | 24 +- .../pt-BR/content/admin/overview/index.md | 2 + ...managing-your-github-enterprise-license.md | 24 +- .../enabling-github-packages-with-aws.md | 26 +- ...github-packages-with-azure-blob-storage.md | 12 +- .../enabling-github-packages-with-minio.md | 36 +- ...ith-github-packages-for-your-enterprise.md | 30 +- .../pt-BR/content/admin/packages/index.md | 12 +- ...inio-storage-bucket-for-github-packages.md | 6 +- .../creating-a-pre-receive-hook-script.md | 43 +- ...-management-policies-in-your-enterprise.md | 8 +- .../admin/user-management/audited-actions.md | 54 +- ...izing-user-messages-for-your-enterprise.md | 59 ++- .../migrating-to-internal-repositories.md | 4 +- .../user-management/viewing-push-logs.md | 9 +- .../managing-tags.md | 11 + .../developers/apps/authorizing-oauth-apps.md | 16 +- .../creating-a-github-app-from-a-manifest.md | 4 +- ...ating-a-github-app-using-url-parameters.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 12 +- ...nces-between-github-apps-and-oauth-apps.md | 5 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../developers/apps/scopes-for-oauth-apps.md | 60 +-- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 8 + .../developers/github-marketplace/index.md | 7 +- .../receiving-payment-for-app-purchases.md | 8 +- .../requirements-for-listing-an-app.md | 11 +- .../setting-pricing-plans-for-your-listing.md | 8 +- ...submitting-your-listing-for-publication.md | 30 +- .../viewing-transactions-for-your-listing.md | 2 +- .../developers/overview/secret-scanning.md | 77 ++- .../pt-BR/content/discussions/index.md | 4 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../pt-BR/content/education/guides.md | 10 +- translations/pt-BR/content/education/index.md | 34 +- .../basics-of-setting-up-github-classroom.md | 2 +- .../create-a-group-assignment.md | 2 +- ...n-assignment-from-a-template-repository.md | 2 - .../create-an-individual-assignment.md | 2 +- .../index.md | 1 - .../manage-classrooms.md | 2 +- .../teach-with-github-classroom.md | 3 + .../about-dependabot-version-updates.md | 4 + ...fications-for-pushes-to-your-repository.md | 4 +- .../about-merge-methods-on-github.md | 2 +- .../about-releases.md | 2 +- .../about-secret-scanning.md | 111 +--- .../about-securing-your-repository.md | 20 +- .../changing-the-default-branch.md | 8 +- ...g-secret-scanning-for-your-repositories.md | 28 +- .../administering-a-repository/index.md | 18 +- .../managing-a-branch-protection-rule.md | 54 +- .../managing-alerts-from-secret-scanning.md | 19 +- ...-objects-in-archives-of-your-repository.md | 4 +- .../managing-releases-in-a-repository.md | 2 +- ...d-analysis-settings-for-your-repository.md | 41 +- .../renaming-a-branch.md | 33 +- .../setting-repository-visibility.md | 93 ++-- .../troubleshooting-required-status-checks.md | 10 +- ...authentication-with-saml-single-sign-on.md | 14 +- .../about-commit-signature-verification.md | 6 +- .../keeping-your-account-and-data-secure.md | 4 +- ...moving-sensitive-data-from-a-repository.md | 4 +- .../reviewing-your-security-log.md | 38 +- .../testing-your-ssh-connection.md | 2 +- .../working-with-ssh-key-passphrases.md | 11 +- .../blocking-a-user-from-your-organization.md | 3 +- ...cking-a-user-from-your-personal-account.md | 6 +- ...ngle-issue-template-for-your-repository.md | 2 +- .../about-branches.md | 2 +- .../about-pull-request-reviews.md | 5 +- ...ng-a-pull-request-with-required-reviews.md | 5 +- ...pull-request-branch-created-from-a-fork.md | 2 +- .../creating-a-pull-request-from-a-fork.md | 2 +- .../dismissing-a-pull-request-review.md | 4 +- .../github-flow.md | 2 +- .../merging-a-pull-request.md | 2 +- ...a-merge-conflict-using-the-command-line.md | 16 +- ...ng-dependency-changes-in-a-pull-request.md | 6 +- ...wing-proposed-changes-in-a-pull-request.md | 8 +- .../working-with-pre-receive-hooks.md | 2 +- ...g-a-commit-on-behalf-of-an-organization.md | 12 +- ...creating-a-commit-with-multiple-authors.md | 12 +- .../about-code-owners.md | 2 +- .../about-readmes.md | 4 +- .../about-repositories.md | 4 +- .../licensing-a-repository.md | 2 +- .../about-github-marketplace.md | 2 +- .../about-codespaces.md | 2 + .../index.md | 3 + ...ging-access-and-security-for-codespaces.md | 28 +- ...naging-encrypted-secrets-for-codespaces.md | 40 +- ...anaging-gpg-verification-for-codespaces.md | 12 +- ...rsonalizing-codespaces-for-your-account.md | 1 + ...-codeql-code-scanning-in-your-ci-system.md | 10 +- ...enabling-code-scanning-for-a-repository.md | 5 +- ...ode-scanning-alerts-for-your-repository.md | 2 + ...-codeql-code-scanning-in-your-ci-system.md | 19 +- .../sarif-support-for-code-scanning.md | 8 +- ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 1 + .../troubleshooting-the-codeql-workflow.md | 63 ++- .../uploading-a-sarif-file-to-github.md | 4 + .../about-github-advanced-security.md | 40 +- .../git-and-github-learning-resources.md | 10 +- .../git-cheatsheet.md | 2 +- .../github-for-mobile.md | 39 +- .../githubs-products.md | 114 ++-- .../getting-started-with-github/index.md | 1 + .../keyboard-shortcuts.md | 6 +- ...roject-to-github-using-the-command-line.md | 6 +- .../deleting-files-in-a-repository.md | 24 +- .../managing-files-in-a-repository/index.md | 2 +- .../navigating-code-on-github.md | 2 +- .../about-storage-and-bandwidth-usage.md | 2 +- .../configuring-git-large-file-storage.md | 2 +- .../about-dependabot-security-updates.md | 4 + .../about-managing-vulnerable-dependencies.md | 2 +- ...configuring-dependabot-security-updates.md | 10 +- ...tifications-for-vulnerable-dependencies.md | 2 +- .../publishing-a-security-advisory.md | 12 + .../troubleshooting-dependabot-errors.md | 8 +- .../about-notifications.md | 10 +- .../configuring-notifications.md | 27 +- .../managing-notifications-from-your-inbox.md | 87 +++- .../managing-your-subscriptions.md | 4 +- .../viewing-your-subscriptions.md | 2 +- .../changing-project-board-visibility.md | 11 +- .../copying-a-project-board.md | 2 +- .../creating-a-project-board.md | 2 + ...iltering-pull-requests-by-review-status.md | 2 +- ...sferring-an-issue-to-another-repository.md | 33 +- ...arch-to-filter-issues-and-pull-requests.md | 2 +- .../about-email-notifications.md | 3 +- .../searching-commits.md | 2 +- .../searching-discussions.md | 52 +- .../searching-issues-and-pull-requests.md | 3 +- ...unted-subscriptions-for-github-accounts.md | 4 +- ...ess-management-with-saml-single-sign-on.md | 8 +- .../about-scim.md | 2 +- .../index.md | 3 +- ...analysis-settings-for-your-organization.md | 77 ++- ...ithub-pages-sites-for-your-organization.md | 30 ++ .../permission-levels-for-an-organization.md | 181 +++---- ...t-board-permissions-for-an-organization.md | 2 +- ...y-permission-levels-for-an-organization.md | 75 ++- ...-a-team-with-an-identity-provider-group.md | 15 +- ...embers-saml-access-to-your-organization.md | 2 + ...-management-for-your-enterprise-account.md | 34 +- ...rganizations-in-your-enterprise-account.md | 6 +- ...-management-for-your-enterprise-account.md | 4 +- ...-for-your-enterprise-account-using-okta.md | 2 +- ...rganizations-in-your-enterprise-account.md | 14 +- ...ity-settings-in-your-enterprise-account.md | 95 +--- .../index.md | 8 +- ...dio-subscription-with-github-enterprise.md | 14 +- ...rganizations-in-your-enterprise-account.md | 10 +- ...rganizations-in-your-enterprise-account.md | 2 +- ...-a-users-saml-access-to-your-enterprise.md | 2 + ...n-and-usage-for-your-enterprise-account.md | 4 +- .../managing-your-profile-readme.md | 2 + ...roubleshooting-commits-on-your-timeline.md | 20 +- ...tributions-not-showing-up-on-my-profile.md | 4 +- ...on-levels-for-user-owned-project-boards.md | 4 +- .../types-of-emails-github-sends.md | 13 +- .../github-additional-product-terms.md | 18 +- .../site-policy/github-and-trade-controls.md | 50 +- ...ub-bug-bounty-program-legal-safe-harbor.md | 2 +- .../site-policy/github-privacy-statement.md | 46 +- .../github-subprocessors-and-cookies.md | 49 +- ...delines-for-legal-requests-of-user-data.md | 9 +- .../pt-BR/content/github/site-policy/index.md | 10 - .../changing-your-sponsorship-tiers.md | 2 +- .../sponsoring-an-open-source-contributor.md | 36 +- .../viewing-your-sponsors-and-sponsorships.md | 8 +- ...se-settings-for-your-private-repository.md | 2 +- .../github/using-git/adding-a-remote.md | 2 +- .../using-git-rebase-on-the-command-line.md | 6 +- .../which-remote-url-should-i-use.md | 2 +- ...loring-the-dependencies-of-a-repository.md | 14 +- .../about-github-pages-and-jekyll.md | 4 +- .../about-github-pages.md | 18 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...-to-your-github-pages-site-using-jekyll.md | 2 + ...he-visibility-of-your-github-pages-site.md | 27 + ...shing-source-for-your-github-pages-site.md | 2 +- ...tom-404-page-for-your-github-pages-site.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 5 +- .../creating-a-github-pages-site.md | 7 +- .../github/working-with-github-pages/index.md | 1 + ...ustom-domain-for-your-github-pages-site.md | 2 +- ...yll-build-errors-for-github-pages-sites.md | 154 +++--- .../unpublishing-a-github-pages-site.md | 2 +- .../about-github-support.md | 4 +- .../forking-and-cloning-gists.md | 2 +- .../organizing-information-with-tables.md | 10 +- translations/pt-BR/content/graphql/README.md | 10 +- .../guides/forming-calls-with-graphql.md | 1 + .../graphql/guides/introduction-to-graphql.md | 38 +- .../guides/migrating-from-rest-to-graphql.md | 14 +- .../graphql/guides/using-global-node-ids.md | 8 +- .../graphql/overview/resource-limitations.md | 8 +- ...n-github-insights-and-github-enterprise.md | 4 +- .../installing-github-insights.md | 1 + .../guides/about-github-container-registry.md | 8 +- ...ache-maven-for-use-with-github-packages.md | 10 +- ...ing-docker-for-use-with-github-packages.md | 67 ++- ...guring-npm-for-use-with-github-packages.md | 16 +- ...g-rubygems-for-use-with-github-packages.md | 6 +- ...cting-a-repository-to-a-container-image.md | 4 +- .../container-guides-for-github-packages.md | 6 +- .../guides/deleting-a-container-image.md | 32 +- .../pt-BR/content/packages/guides/index.md | 2 +- ...ckage-client-guides-for-github-packages.md | 6 +- ...ing-github-packages-with-github-actions.md | 264 +++++++++- translations/pt-BR/content/packages/index.md | 20 +- .../about-github-packages.md | 17 +- .../core-concepts-for-github-packages.md | 2 +- .../packages/learn-github-packages/index.md | 6 +- .../manage-packages/deleting-a-package.md | 6 +- .../content/packages/manage-packages/index.md | 4 +- .../pt-BR/content/packages/quickstart.md | 44 +- translations/pt-BR/content/rest/README.md | 10 +- .../rest/guides/basics-of-authentication.md | 2 +- .../rest/guides/delivering-deployments.md | 2 +- .../rest/guides/rendering-data-as-graphs.md | 4 +- .../rest/guides/working-with-comments.md | 6 +- .../content/rest/overview/api-previews.md | 11 - .../pt-BR/content/rest/overview/libraries.md | 38 +- .../content/rest/overview/media-types.md | 9 +- .../rest/overview/openapi-description.md | 26 +- .../overview/other-authentication-methods.md | 14 +- .../overview/resources-in-the-rest-api.md | 436 +++++++--------- .../content/rest/overview/troubleshooting.md | 22 +- .../content/rest/reference/code-scanning.md | 1 + .../pt-BR/content/rest/reference/gists.md | 26 +- .../content/rest/reference/interactions.md | 20 +- .../pt-BR/content/rest/reference/orgs.md | 2 +- .../permissions-required-for-github-apps.md | 13 +- .../pt-BR/content/rest/reference/repos.md | 218 ++++---- .../pt-BR/content/rest/reference/search.md | 8 +- .../content/rest/reference/secret-scanning.md | 2 +- .../pt-BR/content/rest/reference/teams.md | 2 +- .../pt-BR/content/rest/reference/users.md | 2 +- .../pt-BR/data/glossaries/external.yml | 14 +- .../pt-BR/data/glossaries/internal.yml | 4 +- .../pt-BR/data/learning-tracks/README.md | 3 + .../pt-BR/data/learning-tracks/actions.yml | 23 +- .../pt-BR/data/release-notes/2-20/0.yml | 71 ++- .../pt-BR/data/release-notes/2-20/1.yml | 29 +- .../pt-BR/data/release-notes/2-20/10.yml | 29 +- .../pt-BR/data/release-notes/2-20/11.yml | 25 +- .../pt-BR/data/release-notes/2-20/12.yml | 19 +- .../pt-BR/data/release-notes/2-20/13.yml | 31 +- .../pt-BR/data/release-notes/2-20/14.yml | 15 +- .../pt-BR/data/release-notes/2-20/16.yml | 15 +- .../pt-BR/data/release-notes/2-20/17.yml | 15 +- .../pt-BR/data/release-notes/2-20/18.yml | 37 +- .../pt-BR/data/release-notes/2-20/19.yml | 15 +- .../pt-BR/data/release-notes/2-20/2.yml | 41 +- .../pt-BR/data/release-notes/2-20/20.yml | 19 +- .../pt-BR/data/release-notes/2-20/21.yml | 17 +- .../pt-BR/data/release-notes/2-20/22.yml | 27 +- .../pt-BR/data/release-notes/2-20/23.yml | 15 +- .../pt-BR/data/release-notes/2-20/3.yml | 19 +- .../pt-BR/data/release-notes/2-20/4.yml | 25 +- .../pt-BR/data/release-notes/2-20/5.yml | 27 +- .../pt-BR/data/release-notes/2-20/6.yml | 39 +- .../pt-BR/data/release-notes/2-20/7.yml | 29 +- .../pt-BR/data/release-notes/2-20/8.yml | 27 +- .../pt-BR/data/release-notes/2-20/9.yml | 21 +- .../pt-BR/data/release-notes/2-21/0.yml | 33 +- .../pt-BR/data/release-notes/2-21/1.yml | 25 +- .../pt-BR/data/release-notes/2-21/10.yml | 15 +- .../pt-BR/data/release-notes/2-21/11.yml | 23 +- .../pt-BR/data/release-notes/2-21/12.yml | 19 +- .../pt-BR/data/release-notes/2-21/13.yml | 27 +- .../pt-BR/data/release-notes/2-21/14.yml | 15 +- .../pt-BR/data/release-notes/2-21/2.yml | 25 +- .../pt-BR/data/release-notes/2-21/3.yml | 19 +- .../pt-BR/data/release-notes/2-21/4.yml | 27 +- .../pt-BR/data/release-notes/2-21/5.yml | 17 +- .../pt-BR/data/release-notes/2-21/7.yml | 15 +- .../pt-BR/data/release-notes/2-21/8.yml | 17 +- .../pt-BR/data/release-notes/2-21/9.yml | 41 +- .../pt-BR/data/release-notes/2-22/0.yml | 135 +++-- .../pt-BR/data/release-notes/2-22/1.yml | 79 ++- .../pt-BR/data/release-notes/2-22/2.yml | 21 +- .../pt-BR/data/release-notes/2-22/3.yml | 29 +- .../pt-BR/data/release-notes/2-22/4.yml | 23 +- .../pt-BR/data/release-notes/2-22/5.yml | 33 +- .../pt-BR/data/release-notes/2-22/6.yml | 15 +- .../pt-BR/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../pt-BR/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../actions/enterprise-actions-permissions.md | 13 +- .../data/reusables/actions/enterprise-beta.md | 2 +- .../data/reusables/code-scanning/beta.md | 4 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../dependabot/private-dependencies-note.md | 4 +- .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../enterprise-administrators.md | 2 +- .../user-provisioning-release-stage.md | 2 +- .../hardware-considerations-all-platforms.md | 15 +- .../hardware-rec-table.md | 27 +- .../ssh-into-instance.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../reusables/gated-features/code-scanning.md | 2 +- .../reusables/gated-features/environments.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../gated-features/protected-branches.md | 2 +- .../gated-features/secret-scanning.md | 2 +- .../cannot-convert-public-gists-to-secret.md | 2 +- .../github-actions/actions-billing.md | 2 +- .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- .../team-sync-azure-permissions.md | 2 +- .../team-sync-confirm.md | 2 +- .../can-include-lfs-objects-archives.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../organizations/can-require-ssh-cert.md | 2 +- .../reseller-ask-to-become-billing-manager.md | 2 +- .../organizations/team-synchronization.md | 2 +- .../packages-ghes-release-stage.md | 4 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../pt-BR/data/reusables/pages/visit-site.md | 2 +- .../data/reusables/profile/profile-readme.md | 2 +- .../project-board-visibility.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- .../required-checks-must-pass-to-merge.md | 2 +- .../required-reviews-for-prs-summary.md | 4 +- .../repositories/branch-rules-example.md | 2 +- .../repositories/dependency-review.md | 2 +- .../reusables/repositories/relative-links.md | 2 +- .../review-policy-overlapping-commits.md | 2 +- .../reusables/repositories/section-links.md | 2 +- .../repositories/workflow-notifications.md | 2 + ...ut-user-provisioning-enterprise-account.md | 2 +- .../reusables/saml/dotcom-saml-explanation.md | 2 +- .../you-must-periodically-authenticate.md | 2 +- .../data/reusables/secret-scanning/beta.md | 5 +- ...nalysis-features-are-enabled-by-default.md | 2 + .../sponsors/sponsorship-dashboard.md | 2 +- .../data/reusables/support/ghae-priorities.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../pull_request_webhook_properties.md | 6 +- translations/pt-BR/data/ui.yml | 24 +- .../data/variables/action_code_examples.yml | 4 +- translations/pt-BR/data/variables/gists.yml | 6 +- translations/pt-BR/data/variables/product.yml | 2 + .../data/variables/release_candidate.yml | 2 +- .../actions/creating-actions/about-actions.md | 7 +- .../creating-a-composite-run-steps-action.md | 10 +- .../creating-a-docker-container-action.md | 40 +- .../creating-a-javascript-action.md | 5 +- .../dockerfile-support-for-github-actions.md | 9 +- .../setting-exit-codes-for-actions.md | 2 + .../guides/about-continuous-integration.md | 5 +- .../about-packaging-with-github-actions.md | 4 +- .../guides/about-service-containers.md | 9 +- .../building-and-testing-java-with-ant.md | 12 +- .../building-and-testing-java-with-gradle.md | 31 +- .../building-and-testing-java-with-maven.md | 14 +- .../guides/building-and-testing-net.md | 4 +- .../guides/building-and-testing-nodejs.md | 28 +- .../guides/building-and-testing-powershell.md | 5 +- .../guides/building-and-testing-python.md | 69 +-- .../guides/building-and-testing-ruby.md | 18 +- ...hing-dependencies-to-speed-up-workflows.md | 14 +- .../creating-postgresql-service-containers.md | 19 +- .../creating-redis-service-containers.md | 19 +- ...ing-to-amazon-elastic-container-service.md | 5 + .../guides/deploying-to-azure-app-service.md | 5 + .../deploying-to-google-kubernetes-engine.md | 5 + .../ru-RU/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 12 +- .../publishing-java-packages-with-gradle.md | 19 +- .../publishing-java-packages-with-maven.md | 17 +- .../guides/publishing-nodejs-packages.md | 21 +- ...us-integration-using-workflow-templates.md | 5 +- .../storing-workflow-data-as-artifacts.md | 10 +- ...a-proxy-server-with-self-hosted-runners.md | 4 +- ...using-self-hosted-runners-in-a-workflow.md | 13 +- translations/ru-RU/content/actions/index.md | 17 +- .../essential-features-of-github-actions.md | 4 +- .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 8 +- .../managing-complex-workflows.md | 2 + ...-from-azure-pipelines-to-github-actions.md | 155 +++--- ...grating-from-circleci-to-github-actions.md | 85 +-- ...ting-from-gitlab-cicd-to-github-actions.md | 45 +- ...igrating-from-jenkins-to-github-actions.md | 176 +++---- ...rating-from-travis-ci-to-github-actions.md | 77 +-- .../security-hardening-for-github-actions.md | 8 +- .../adding-a-workflow-status-badge.md | 8 +- .../manually-running-a-workflow.md | 2 +- .../ru-RU/content/actions/quickstart.md | 3 + ...nd-expression-syntax-for-github-actions.md | 43 +- .../reference/environment-variables.md | 22 +- .../workflow-commands-for-github-actions.md | 20 +- .../workflow-syntax-for-github-actions.md | 23 +- .../configuration/command-line-utilities.md | 16 +- .../configuring-email-for-notifications.md | 8 +- ...-availability-replication-for-a-cluster.md | 2 +- .../evacuating-a-cluster-node.md | 10 + .../initializing-the-cluster.md | 2 +- .../about-github-enterprise-support.md | 1 - ...manually-syncing-actions-from-githubcom.md | 2 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../ru-RU/content/admin/overview/index.md | 1 + ...managing-your-github-enterprise-license.md | 24 +- .../creating-a-pre-receive-hook-script.md | 43 +- .../admin/user-management/audited-actions.md | 4 +- .../migrating-to-internal-repositories.md | 4 +- .../user-management/viewing-push-logs.md | 9 +- .../managing-tags.md | 11 + .../creating-a-github-app-from-a-manifest.md | 4 +- .../creating-ci-tests-with-the-checks-api.md | 10 +- ...nces-between-github-apps-and-oauth-apps.md | 3 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 8 + .../developers/github-marketplace/index.md | 7 +- .../requirements-for-listing-an-app.md | 11 +- .../setting-pricing-plans-for-your-listing.md | 8 +- ...submitting-your-listing-for-publication.md | 30 +- .../developers/overview/secret-scanning.md | 77 ++- .../ru-RU/content/discussions/index.md | 4 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../ru-RU/content/education/guides.md | 10 +- translations/ru-RU/content/education/index.md | 12 +- .../basics-of-setting-up-github-classroom.md | 2 +- .../create-a-group-assignment.md | 2 +- ...n-assignment-from-a-template-repository.md | 2 - .../create-an-individual-assignment.md | 2 +- .../index.md | 1 - .../teach-with-github-classroom.md | 3 + ...fications-for-pushes-to-your-repository.md | 4 +- .../changing-the-default-branch.md | 2 +- .../renaming-a-branch.md | 13 + ...authentication-with-saml-single-sign-on.md | 14 +- ...moving-sensitive-data-from-a-repository.md | 4 +- .../blocking-a-user-from-your-organization.md | 3 +- ...cking-a-user-from-your-personal-account.md | 6 +- ...ngle-issue-template-for-your-repository.md | 2 +- ...a-merge-conflict-using-the-command-line.md | 16 +- .../working-with-pre-receive-hooks.md | 2 +- .../about-github-marketplace.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 10 +- ...ode-scanning-alerts-for-your-repository.md | 2 + ...-codeql-code-scanning-in-your-ci-system.md | 2 + .../sarif-support-for-code-scanning.md | 6 +- .../uploading-a-sarif-file-to-github.md | 2 + .../about-github-advanced-security.md | 2 +- .../git-and-github-learning-resources.md | 10 +- .../git-cheatsheet.md | 2 +- .../githubs-products.md | 1 + .../keyboard-shortcuts.md | 6 +- ...roject-to-github-using-the-command-line.md | 6 +- .../navigating-code-on-github.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 2 + .../publishing-a-security-advisory.md | 12 + .../configuring-notifications.md | 3 +- ...sferring-an-issue-to-another-repository.md | 2 +- .../about-email-notifications.md | 3 +- .../searching-issues-and-pull-requests.md | 3 +- ...unted-subscriptions-for-github-accounts.md | 4 +- .../index.md | 2 +- ...ithub-pages-sites-for-your-organization.md | 30 ++ .../permission-levels-for-an-organization.md | 181 +++---- ...y-permission-levels-for-an-organization.md | 206 ++++---- ...ing-the-audit-log-for-your-organization.md | 75 +-- ...-management-for-your-enterprise-account.md | 16 +- ...dio-subscription-with-github-enterprise.md | 4 +- .../managing-your-profile-readme.md | 2 + ...on-levels-for-a-user-account-repository.md | 19 +- .../types-of-emails-github-sends.md | 13 +- .../github-additional-product-terms.md | 2 +- .../site-policy/github-and-trade-controls.md | 25 +- .../github-subprocessors-and-cookies.md | 46 +- ...delines-for-legal-requests-of-user-data.md | 9 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../about-github-pages-and-jekyll.md | 4 +- .../about-github-pages.md | 16 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...he-visibility-of-your-github-pages-site.md | 27 + ...tom-404-page-for-your-github-pages-site.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 5 +- .../creating-a-github-pages-site.md | 7 +- .../github/working-with-github-pages/index.md | 1 + ...yll-build-errors-for-github-pages-sites.md | 2 +- .../unpublishing-a-github-pages-site.md | 2 +- .../basic-writing-and-formatting-syntax.md | 16 +- .../organizing-information-with-tables.md | 10 +- .../graphql/guides/introduction-to-graphql.md | 38 +- ...n-github-insights-and-github-enterprise.md | 2 +- .../installing-github-insights.md | 1 + ...ache-maven-for-use-with-github-packages.md | 10 +- ...guring-npm-for-use-with-github-packages.md | 6 +- ...g-rubygems-for-use-with-github-packages.md | 6 +- translations/ru-RU/content/packages/index.md | 11 +- .../manage-packages/deleting-a-package.md | 4 +- .../ru-RU/content/rest/overview/libraries.md | 4 + .../permissions-required-for-github-apps.md | 11 +- .../ru-RU/data/glossaries/external.yml | 6 +- .../ru-RU/data/learning-tracks/README.md | 3 + .../ru-RU/data/learning-tracks/actions.yml | 7 + .../ru-RU/data/release-notes/2-20/18.yml | 2 +- .../ru-RU/data/release-notes/2-21/9.yml | 2 +- .../ru-RU/data/release-notes/2-22/1.yml | 2 +- .../ru-RU/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../ru-RU/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../ssh-into-instance.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../github-actions/actions-billing.md | 2 +- .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../reseller-ask-to-become-billing-manager.md | 2 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../ru-RU/data/reusables/pages/visit-site.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- ...ut-user-provisioning-enterprise-account.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../pull_request_webhook_properties.md | 6 +- translations/ru-RU/data/ui.yml | 12 +- translations/ru-RU/data/variables/product.yml | 1 + .../actions/creating-actions/about-actions.md | 5 +- .../creating-a-composite-run-steps-action.md | 6 +- .../creating-a-docker-container-action.md | 40 +- .../creating-a-javascript-action.md | 7 +- .../dockerfile-support-for-github-actions.md | 11 +- .../metadata-syntax-for-github-actions.md | 2 +- .../setting-exit-codes-for-actions.md | 2 + .../guides/about-continuous-integration.md | 3 + .../about-packaging-with-github-actions.md | 2 + .../guides/about-service-containers.md | 7 +- .../building-and-testing-java-with-ant.md | 12 +- .../building-and-testing-java-with-gradle.md | 31 +- .../building-and-testing-java-with-maven.md | 14 +- .../guides/building-and-testing-net.md | 4 +- .../guides/building-and-testing-nodejs.md | 28 +- .../guides/building-and-testing-powershell.md | 5 +- .../guides/building-and-testing-python.md | 69 +-- .../guides/building-and-testing-ruby.md | 18 +- ...hing-dependencies-to-speed-up-workflows.md | 16 +- .../creating-postgresql-service-containers.md | 19 +- .../creating-redis-service-containers.md | 19 +- ...ing-to-amazon-elastic-container-service.md | 5 + .../guides/deploying-to-azure-app-service.md | 5 + .../deploying-to-google-kubernetes-engine.md | 5 + .../zh-CN/content/actions/guides/index.md | 37 ++ .../guides/publishing-docker-images.md | 12 +- .../publishing-java-packages-with-gradle.md | 19 +- .../publishing-java-packages-with-maven.md | 17 +- .../guides/publishing-nodejs-packages.md | 25 +- ...us-integration-using-workflow-templates.md | 5 +- .../storing-workflow-data-as-artifacts.md | 10 +- ...-hosted-runner-application-as-a-service.md | 2 +- ...ess-to-self-hosted-runners-using-groups.md | 2 +- .../removing-self-hosted-runners.md | 2 +- ...a-proxy-server-with-self-hosted-runners.md | 4 +- .../using-labels-with-self-hosted-runners.md | 2 +- ...using-self-hosted-runners-in-a-workflow.md | 15 +- translations/zh-CN/content/actions/index.md | 17 +- .../essential-features-of-github-actions.md | 2 + .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 6 +- .../managing-complex-workflows.md | 2 + ...grating-from-circleci-to-github-actions.md | 87 ++-- ...ting-from-gitlab-cicd-to-github-actions.md | 45 +- ...igrating-from-jenkins-to-github-actions.md | 176 +++---- ...rating-from-travis-ci-to-github-actions.md | 77 +-- .../security-hardening-for-github-actions.md | 8 +- .../adding-a-workflow-status-badge.md | 8 +- .../manually-running-a-workflow.md | 2 +- .../zh-CN/content/actions/quickstart.md | 3 + ...nd-expression-syntax-for-github-actions.md | 43 +- .../reference/environment-variables.md | 22 +- .../workflow-commands-for-github-actions.md | 20 +- .../workflow-syntax-for-github-actions.md | 41 +- .../configuration/command-line-utilities.md | 16 +- .../configuring-email-for-notifications.md | 8 +- ...-availability-replication-for-a-cluster.md | 2 +- .../evacuating-a-cluster-node.md | 10 + .../initializing-the-cluster.md | 2 +- .../about-github-enterprise-support.md | 1 - ...manually-syncing-actions-from-githubcom.md | 2 +- .../content/admin/overview/about-github-ae.md | 46 ++ .../zh-CN/content/admin/overview/index.md | 1 + ...managing-your-github-enterprise-license.md | 24 +- .../creating-a-pre-receive-hook-script.md | 43 +- .../admin/user-management/audited-actions.md | 4 +- .../migrating-to-internal-repositories.md | 4 +- .../user-management/viewing-push-logs.md | 9 +- .../managing-tags.md | 11 + .../developers/apps/authorizing-oauth-apps.md | 2 +- .../creating-a-github-app-from-a-manifest.md | 4 +- .../creating-ci-tests-with-the-checks-api.md | 12 +- ...nces-between-github-apps-and-oauth-apps.md | 3 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- .../developers/apps/scopes-for-oauth-apps.md | 60 +-- .../about-github-marketplace.md | 26 +- .../about-marketplace-badges.md | 43 ++ ...sher-verification-for-your-organization.md | 32 ++ .../drafting-a-listing-for-your-app.md | 2 +- .../github-marketplace-overview.md | 8 + .../developers/github-marketplace/index.md | 7 +- .../receiving-payment-for-app-purchases.md | 8 +- .../requirements-for-listing-an-app.md | 11 +- .../setting-pricing-plans-for-your-listing.md | 10 +- ...submitting-your-listing-for-publication.md | 30 +- .../viewing-transactions-for-your-listing.md | 2 +- .../developers/overview/secret-scanning.md | 77 ++- .../zh-CN/content/discussions/index.md | 4 +- .../about-campus-advisors.md | 18 + .../about-campus-experts.md | 12 + ...education-for-educators-and-researchers.md | 32 ++ .../about-github-education-for-students.md | 22 + .../about-github-education.md | 24 + .../apply-for-a-student-developer-pack.md | 54 ++ ...-for-an-educator-or-researcher-discount.md | 58 +++ .../index.md | 26 + ...-github-at-your-educational-institution.md | 12 + .../use-github-for-your-schoolwork.md | 12 + ...e-github-in-your-classroom-and-research.md | 12 + ...n-for-a-student-developer-pack-approved.md | 68 +++ ...ducator-or-researcher-discount-approved.md | 46 ++ .../zh-CN/content/education/guides.md | 10 +- translations/zh-CN/content/education/index.md | 12 +- .../basics-of-setting-up-github-classroom.md | 2 +- .../create-a-group-assignment.md | 2 +- ...n-assignment-from-a-template-repository.md | 2 - .../create-an-individual-assignment.md | 2 +- .../index.md | 1 - .../manage-classrooms.md | 2 +- .../teach-with-github-classroom.md | 3 + ...fications-for-pushes-to-your-repository.md | 4 +- .../changing-the-default-branch.md | 2 +- .../renaming-a-branch.md | 13 + ...moving-sensitive-data-from-a-repository.md | 4 +- .../blocking-a-user-from-your-organization.md | 3 +- ...cking-a-user-from-your-personal-account.md | 6 +- ...ngle-issue-template-for-your-repository.md | 2 +- .../automatically-merging-a-pull-request.md | 34 +- ...a-merge-conflict-using-the-command-line.md | 16 +- .../working-with-pre-receive-hooks.md | 2 +- .../about-github-marketplace.md | 2 +- ...ging-access-and-security-for-codespaces.md | 28 +- ...naging-encrypted-secrets-for-codespaces.md | 40 +- ...anaging-gpg-verification-for-codespaces.md | 12 +- ...-codeql-code-scanning-in-your-ci-system.md | 10 +- ...ode-scanning-alerts-for-your-repository.md | 2 + ...-codeql-code-scanning-in-your-ci-system.md | 2 + .../sarif-support-for-code-scanning.md | 6 +- .../uploading-a-sarif-file-to-github.md | 2 + .../about-github-advanced-security.md | 40 +- .../git-and-github-learning-resources.md | 12 +- .../git-cheatsheet.md | 2 +- .../githubs-products.md | 1 + .../keyboard-shortcuts.md | 6 +- ...roject-to-github-using-the-command-line.md | 6 +- .../deleting-files-in-a-repository.md | 24 +- .../navigating-code-on-github.md | 2 +- .../about-managing-vulnerable-dependencies.md | 12 +- .../publishing-a-security-advisory.md | 12 + .../configuring-notifications.md | 3 +- ...sferring-an-issue-to-another-repository.md | 2 +- .../about-email-notifications.md | 3 +- .../searching-issues-and-pull-requests.md | 3 +- .../index.md | 2 +- ...ithub-pages-sites-for-your-organization.md | 32 ++ ...rom-accounts-your-organization-sponsors.md | 14 +- .../permission-levels-for-an-organization.md | 181 +++---- ...y-permission-levels-for-an-organization.md | 206 ++++---- ...ail-notifications-to-an-approved-domain.md | 2 +- .../verifying-your-organizations-domain.md | 2 +- ...-management-for-your-enterprise-account.md | 34 +- ...rganizations-in-your-enterprise-account.md | 6 +- ...-management-for-your-enterprise-account.md | 4 +- ...rganizations-in-your-enterprise-account.md | 14 +- ...dio-subscription-with-github-enterprise.md | 4 +- ...rganizations-in-your-enterprise-account.md | 10 +- ...-enterprise-account-to-approved-domains.md | 16 +- ...rifying-your-enterprise-accounts-domain.md | 24 +- .../managing-your-profile-readme.md | 2 + ...on-levels-for-a-user-account-repository.md | 45 +- .../types-of-emails-github-sends.md | 13 +- .../github-additional-product-terms.md | 2 +- .../site-policy/github-and-trade-controls.md | 25 +- .../github-subprocessors-and-cookies.md | 44 +- ...delines-for-legal-requests-of-user-data.md | 9 +- ...uting-sponsorships-to-your-organization.md | 16 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../about-github-pages-and-jekyll.md | 4 +- ...yll-build-errors-for-github-pages-sites.md | 4 +- ...-to-your-github-pages-site-using-jekyll.md | 2 +- ...he-visibility-of-your-github-pages-site.md | 27 + ...tom-404-page-for-your-github-pages-site.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 5 +- .../creating-a-github-pages-site.md | 7 +- .../github/working-with-github-pages/index.md | 1 + ...yll-build-errors-for-github-pages-sites.md | 2 +- .../unpublishing-a-github-pages-site.md | 2 +- .../basic-writing-and-formatting-syntax.md | 16 +- .../organizing-information-with-tables.md | 10 +- .../graphql/guides/introduction-to-graphql.md | 38 +- ...n-github-insights-and-github-enterprise.md | 2 +- .../installing-github-insights.md | 1 + ...ache-maven-for-use-with-github-packages.md | 10 +- ...ing-docker-for-use-with-github-packages.md | 2 +- ...dotnet-cli-for-use-with-github-packages.md | 10 +- ...guring-npm-for-use-with-github-packages.md | 10 +- translations/zh-CN/content/packages/index.md | 11 +- .../about-github-packages.md | 6 +- .../manage-packages/deleting-a-package.md | 4 +- .../zh-CN/content/rest/overview/libraries.md | 4 + .../permissions-required-for-github-apps.md | 11 +- .../zh-CN/data/glossaries/external.yml | 6 +- .../zh-CN/data/learning-tracks/README.md | 3 + .../zh-CN/data/learning-tracks/actions.yml | 7 + .../zh-CN/data/release-notes/2-20/18.yml | 4 +- .../zh-CN/data/release-notes/2-21/9.yml | 4 +- .../zh-CN/data/release-notes/2-22/1.yml | 4 +- .../zh-CN/data/release-notes/3-0/0-rc1.yml | 145 ++++++ .../zh-CN/data/release-notes/3-0/0-rc2.yml | 25 + .../reusables/actions/actions-not-verified.md | 2 +- .../actions/actions-use-policy-settings.md | 2 +- .../actions/allow-specific-actions-intro.md | 2 +- .../deprecating_auth_with_query_parameters.md | 4 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 5 + .../community/interaction-limits-duration.md | 2 +- .../interaction-limits-restrictions.md | 2 +- .../community/set-interaction-limit.md | 2 +- .../community/types-of-interaction-limits.md | 6 +- .../dependabot/private-dependencies-note.md | 4 +- .../dependabot/supported-package-managers.md | 59 +-- .../data/reusables/desktop/delete-tag.md | 4 + .../education/about-github-education-link.md | 2 +- .../reusables/education/apply-for-team.md | 2 +- .../enterprise-administrators.md | 2 +- .../enterprise-accounts/pages-tab.md | 2 +- .../enterprise-managed/about-billing.md | 2 +- .../ssh-into-instance.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../about-ssh-access.md | 2 +- .../about-the-management-console.md | 2 +- .../about-the-site-admin-dashboard.md | 2 +- .../reusables/gated-features/private-pages.md | 1 + .../github-actions/java-jvm-architecture.md | 2 +- .../github-actions/macos-runner-preview.md | 2 +- .../data/reusables/github-ae/about-billing.md | 2 +- .../github-ae/github-ae-enables-you.md | 2 +- .../reusables/marketplace/launch-with-free.md | 2 +- .../custom-notifications-beta.md | 2 +- ...nerable-dependency-notification-options.md | 2 +- .../feature-preview-for-container-registry.md | 2 +- .../pages/about-private-publishing.md | 1 + .../data/reusables/pages/choose-visibility.md | 1 + .../org-owners-can-restrict-pages-creation.md | 7 + .../pages/private_pages_are_public_warning.md | 6 +- .../pages/twenty-minutes-to-publish.md | 1 + .../zh-CN/data/reusables/pages/visit-site.md | 2 +- .../project-board-visibility.md | 2 +- .../pull_requests/re-request-review.md | 2 +- .../pull_requests/rebase_and_merge_summary.md | 2 +- .../required-reviews-for-prs-summary.md | 2 +- .../administrators-can-disable-issues.md | 2 +- .../repositories/branch-rules-example.md | 2 +- .../review-policy-overlapping-commits.md | 2 +- ...quash-and-rebase-linear-commit-hisitory.md | 2 +- .../repositories/workflow-notifications.md | 2 +- ...ut-user-provisioning-enterprise-account.md | 2 +- ...ae-enable-saml-sso-during-bootstrapping.md | 2 +- .../data/reusables/saml/ae-uses-saml-sso.md | 2 +- .../assert-the-administrator-attribute.md | 2 +- ...tact-support-if-your-idp-is-unavailable.md | 2 +- .../reusables/saml/create-a-machine-user.md | 2 +- .../reusables/saml/dotcom-saml-explanation.md | 2 +- .../you-must-periodically-authenticate.md | 2 +- .../scim/after-you-configure-saml.md | 2 +- .../data/reusables/scim/supported-idps.md | 2 +- .../reusables/secret-scanning/api-beta.md | 2 +- .../data/reusables/secret-scanning/beta.md | 2 +- .../data/reusables/support/ghae-priorities.md | 12 +- .../government-response-times-may-vary.md | 2 +- .../user-settings/edit_marketplace_listing.md | 2 +- .../pull_request_webhook_properties.md | 6 +- .../secret_scanning_alert_event_properties.md | 8 +- .../secret_scanning_alert_event_short_desc.md | 2 +- translations/zh-CN/data/ui.yml | 12 +- .../data/variables/action_code_examples.yml | 170 +++--- .../discussions_community_examples.yml | 20 +- translations/zh-CN/data/variables/product.yml | 1 + 2731 files changed, 24684 insertions(+), 15460 deletions(-) create mode 100644 translations/de-DE/content/admin/overview/about-github-ae.md create mode 100644 translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/de-DE/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/de-DE/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/de-DE/data/learning-tracks/README.md create mode 100644 translations/de-DE/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/de-DE/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/de-DE/data/reusables/desktop/delete-tag.md create mode 100644 translations/de-DE/data/reusables/gated-features/private-pages.md create mode 100644 translations/de-DE/data/reusables/pages/about-private-publishing.md create mode 100644 translations/de-DE/data/reusables/pages/choose-visibility.md create mode 100644 translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md create mode 100644 translations/es-ES/content/admin/overview/about-github-ae.md create mode 100644 translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/es-ES/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/es-ES/data/learning-tracks/README.md create mode 100644 translations/es-ES/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/es-ES/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/es-ES/data/reusables/desktop/delete-tag.md create mode 100644 translations/es-ES/data/reusables/gated-features/private-pages.md create mode 100644 translations/es-ES/data/reusables/pages/about-private-publishing.md create mode 100644 translations/es-ES/data/reusables/pages/choose-visibility.md create mode 100644 translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md create mode 100644 translations/ja-JP/content/admin/overview/about-github-ae.md create mode 100644 translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/ja-JP/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/ja-JP/data/learning-tracks/README.md create mode 100644 translations/ja-JP/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/ja-JP/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/ja-JP/data/reusables/desktop/delete-tag.md create mode 100644 translations/ja-JP/data/reusables/gated-features/private-pages.md create mode 100644 translations/ja-JP/data/reusables/pages/about-private-publishing.md create mode 100644 translations/ja-JP/data/reusables/pages/choose-visibility.md create mode 100644 translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md create mode 100644 translations/ko-KR/content/admin/overview/about-github-ae.md create mode 100644 translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/ko-KR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/ko-KR/data/learning-tracks/README.md create mode 100644 translations/ko-KR/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/ko-KR/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/ko-KR/data/reusables/desktop/delete-tag.md create mode 100644 translations/ko-KR/data/reusables/gated-features/private-pages.md create mode 100644 translations/ko-KR/data/reusables/pages/about-private-publishing.md create mode 100644 translations/ko-KR/data/reusables/pages/choose-visibility.md create mode 100644 translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/ko-KR/data/reusables/pages/twenty-minutes-to-publish.md create mode 100644 translations/pt-BR/content/admin/overview/about-github-ae.md create mode 100644 translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/pt-BR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/pt-BR/data/learning-tracks/README.md create mode 100644 translations/pt-BR/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/pt-BR/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/pt-BR/data/reusables/desktop/delete-tag.md create mode 100644 translations/pt-BR/data/reusables/gated-features/private-pages.md create mode 100644 translations/pt-BR/data/reusables/pages/about-private-publishing.md create mode 100644 translations/pt-BR/data/reusables/pages/choose-visibility.md create mode 100644 translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md create mode 100644 translations/ru-RU/content/admin/overview/about-github-ae.md create mode 100644 translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/ru-RU/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/ru-RU/data/learning-tracks/README.md create mode 100644 translations/ru-RU/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/ru-RU/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/ru-RU/data/reusables/desktop/delete-tag.md create mode 100644 translations/ru-RU/data/reusables/gated-features/private-pages.md create mode 100644 translations/ru-RU/data/reusables/pages/about-private-publishing.md create mode 100644 translations/ru-RU/data/reusables/pages/choose-visibility.md create mode 100644 translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/ru-RU/data/reusables/pages/twenty-minutes-to-publish.md create mode 100644 translations/zh-CN/content/admin/overview/about-github-ae.md create mode 100644 translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md create mode 100644 translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md create mode 100644 translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md create mode 100644 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md create mode 100644 translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md create mode 100644 translations/zh-CN/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md create mode 100644 translations/zh-CN/data/learning-tracks/README.md create mode 100644 translations/zh-CN/data/release-notes/3-0/0-rc1.yml create mode 100644 translations/zh-CN/data/release-notes/3-0/0-rc2.yml create mode 100644 translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md create mode 100644 translations/zh-CN/data/reusables/desktop/delete-tag.md create mode 100644 translations/zh-CN/data/reusables/gated-features/private-pages.md create mode 100644 translations/zh-CN/data/reusables/pages/about-private-publishing.md create mode 100644 translations/zh-CN/data/reusables/pages/choose-visibility.md create mode 100644 translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md create mode 100644 translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md diff --git a/translations/de-DE/content/actions/creating-actions/about-actions.md b/translations/de-DE/content/actions/creating-actions/about-actions.md index 5290b4c566..f990a6d337 100644 --- a/translations/de-DE/content/actions/creating-actions/about-actions.md +++ b/translations/de-DE/content/actions/creating-actions/about-actions.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Action development + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ Schritte: #### Verwenden des SHA eines Commits für die Releaseverwaltung -Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation. +Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value.{% else %}Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation.{% endif %} ```yaml Schritte: diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md index f9ba9a461b..8088c0ff21 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Action development' --- {% data reusables.actions.enterprise-beta %} @@ -65,12 +67,12 @@ Before you begin, you'll create a {% data variables.product.product_name %} repo required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -122,7 +124,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md index d3404b356b..1bb4d31c61 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Action development' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ Erstellen Sie zunächst ein GitHub-Repository. 1. Gehe in Deinem Terminal zum Verzeichnisse Deines neuen Repositorys. - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ Erstellen Sie zunächst ein GitHub-Repository. Erstelle im neuen Verzeichnis `hello-world-docker-action` eine neue `Dockerfile`-Datei. Weitere Informationen findest Du unter „[Dockerfile-Support für {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)“. **Dockerfile** -```dockerfile +```dockerfile{:copy} # Container-Image, das Deinen Code ausführt FROM alpine:3.10 @@ -65,7 +68,7 @@ Erstellen Sie eine neue `action.yml`-Datei im von Ihnen oben erstellten Verzeich {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ Als Nächstes ruft das Skript die aktuelle Zeit ab und legt sie als eine Ausgabe 1. Erstelle eine neue `entrypoint.sh`-Datei im Verzeichnis `hello-world-docker-action`. -1. Mache Deine Datei `entrypoint.sh` ausführbar: - - ```shell - chmod +x entrypoint.sh - ``` - 1. Füge Deiner Datei `entrypoint.sh` den folgenden Code hinzu. **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" time=$(date) echo "::set-output name=time::$time" ``` - Wenn `entrypoint.sh` ohne Fehler durchläuft, wird der Status der Aktion auf `success` (erfolgreich) festgelegt. Du kannst auch explizit Exit-Codes im Code Deiner Aktion festlegen, um einen Status der Aktion anzugeben. Weitere Informationen findest Du unter "[Exit Codes für Aktionen setzen](/actions/creating-actions/setting-exit-codes-for-actions)." +1. Make your `entrypoint.sh` file executable by running the following command on your system. + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### Eine README erstellen Sie können eine README-Datei erstellen, um Person dahingehend zu informieren, wie sie Ihre Aktion verwenden sollen. Eine README ist am hilfreichsten, wenn Sie vorhaben, Ihre Aktion öffentlich freizugeben. Zudem eignet sie sich dafür, Sie oder Ihr Team dahingehend zu erinnern, wie die Aktion verwendet wird. @@ -130,7 +132,7 @@ Erstelle in Deinem Verzeichnis `hello-world-docker-action` eine Datei `README.md - Ein Beispiel für die Verwendung Deiner Aktion in einem Workflow. **README.md** -```markdown +```markdown{:copy} # Docker-Aktion „Hello world“ Diese Aktion gibt „Hello World“ oder „Hello“ + den Namen einer Person aus, die im Protokoll gegrüßt werden soll. @@ -160,7 +162,7 @@ Committen Sie in Ihrem Terminal Ihre Dateien `action.yml`, `entrypoint.sh`, `Doc Es hat sich bewährt, auch ein Versions-Tag für Releases Deiner Aktion hinzuzufügen. Weitere Informationen zur Versionierung Deiner Aktion findest Du unter "[Informationen zu Aktionen](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)." -```shell +```shell{:copy} git add action.yml entrypoint.sh Dockerfile README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1 @@ -175,11 +177,11 @@ Nun sind Sie bereit, Ihre Aktion in einem Workflow zu testen. Wenn eine Aktion i #### Beispiel mit einer öffentlichen Aktion -Der folgende Workflow-Code verwendet die fertiggestellte Aktion „hello world“ im öffentlichen Repository [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Kopiere den folgenden Workflow-Beispielcode in eine Datei `.github/workflows/main.yml`. Ersetze jedoch `actions/hello-world-docker-action` durch Deinen Repository- und Aktionsnamen. Darüber hinaus können Sie die Eingabe `who-to-greet` durch Ihren Namen ersetzen. +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. Kopiere den folgenden Workflow-Beispielcode in eine Datei `.github/workflows/main.yml`. Ersetze jedoch `actions/hello-world-docker-action` durch Deinen Repository- und Aktionsnamen. Darüber hinaus können Sie die Eingabe `who-to-greet` durch Ihren Namen ersetzen. {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### Beispiel mit einer privaten Aktion -Kopieren Sie den folgenden Workflow-Beispielcode im Repository Ihrer Aktion in eine `.github/workflows/main.yml`-Datei. Darüber hinaus können Sie die Eingabe `who-to-greet` durch Ihren Namen ersetzen. +Kopieren Sie den folgenden Workflow-Beispielcode im Repository Ihrer Aktion in eine `.github/workflows/main.yml`-Datei. Darüber hinaus können Sie die Eingabe `who-to-greet` durch Ihren Namen ersetzen. {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} zu: [push] Jobs: diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md index 022e09d529..58c7d5abe3 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Action development' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md index d6a1619189..d0870d2b28 100644 --- a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,7 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} @@ -48,20 +48,21 @@ Für die Docker-Anweisung `ENTRYPOINT` gibt es sowohl eine _shell_-Form als auch Wenn Du Deinen Container so konfigurierst, dass er die _exec_-Form der Anweisung `ENTRYPOINT` verwendet, können die in der Metadaten-Datei der Aktion konfigurierten `args` (Argumente) nicht in einer Kommando-Shell genutzt werden. Wenn die `Args` der Aktion eine Umgebungsvariable enthalten, wird die Variable nicht ersetzt. Wenn Du zum Beispiel das folgende _exec_-Format verwendest, wird nicht der in `$GITHUB_SHA` gespeicherte Wert ausgegeben, sondern stattdessen „`$GITHUB_SHA`“. -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` Wenn Du Variablensubstitution willst, verwende entweder die _Shell_-Form oder führe direkt eine Shell aus. Zum Beispiel kannst Du mit dem folgenden _exec_-Format eine Shell ausführen, um den Wert auszugeben, der in der Umgebungsvariable `GITHUB_SHA` gespeichert ist. -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` Um `args` aus der Metadaten-Datei der Aktion an einen Docker Container zu übergeben, der die _exec_-Form im `ENTRYPOINT` verwendet, empfehlen wir, ein Shell-Skript namens `entrypoint.sh` zu erstellen und dieses von der `ENTRYPOINT`-Anweisung aus anrufen: ##### Beispiel *Dockerfile* -``` + +```dockerfile # Container image that runs your code FROM debian:9.5-slim diff --git a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 7066aa27b0..f0a07b0b9e 100644 --- a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -1,7 +1,7 @@ --- title: Metadaten-Syntax für GitHub-Aktionen shortTitle: Metadaten-Syntax -intro: Du kannst Aktionen erstellen, um Aufgaben in Ihrem Repository zu erledigen. Für Aktionen ist eine Metadaten-Datei erforderlich, welche die YAML-Syntax verwendet. +intro: 'Du kannst Aktionen erstellen, um Aufgaben in Ihrem Repository zu erledigen. Für Aktionen ist eine Metadaten-Datei erforderlich, welche die YAML-Syntax verwendet.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/metadata-syntax-for-github-actions @@ -11,7 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md index bfc443e25e..4d2b68b590 100644 --- a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,11 +41,13 @@ Weitere Informationen finden Sie unter „[Eine JavaScript-Aktion erstellen](/ar Wenn Sie eine Docker-Container-Aktion erstellen, können Sie einen Fehler-Exit-Code im `entrypoint.sh`-Skript festlegen. Ein Beispiel: +{% raw %} ``` if ; then echo "Game over!" exit 1 fi ``` +{% endraw %} Weitere Informationen finden Sie unter „[Eine Docker-Container-Aktion erstellen](/articles/creating-a-docker-container-action)“. diff --git a/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md b/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md index 0a74fc42ed..07c2dc004a 100644 --- a/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Pakete erstellen --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/about-service-containers.md b/translations/de-DE/content/actions/guides/about-service-containers.md index ec29114eef..30c3fc7f86 100644 --- a/translations/de-DE/content/actions/guides/about-service-containers.md +++ b/translations/de-DE/content/actions/guides/about-service-containers.md @@ -8,7 +8,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ Du kannst das Schlüsselwort `Services` verwenden, um Service-Container zu erste Dieses Beispiel erstellt einen Dienst namens `redis` in einem Job namens `container-job`. Der Docker-Host in diesem Beispiel ist der Container `node:10.18-jessie`. {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -89,7 +92,7 @@ Wenn Du den Port des Docker-Hosts angibst, aber nicht den des Containers, dann w Dieses Beispiel ordnet den Port 6379 des Service-Containers `redis` dem Port 6379 des Docker-Hosts zu. {% raw %} -```yaml +```yaml{:copy} name: Redis Service Example on: push diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md index 0ba1f17391..080a09218c 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-ant.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Um schnell loszulegen, kannst Du beim Erstellen eines neuen Workflows die vorkon Du kannst auch manuell diesen Workflow hinzufügen, indem Du eine neue Datei im Verzeichnis `.github/workflows` Deines Reporitorys erstellst. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ Der Starter-Workflow führt das in der Datei _build.xml_ angegebene „default t Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder ein anderes Ziel auszuführen möchtest, kannst Du dies angeben. Vielleicht möchtest Du beispielsweise das Ziel `jar` ausführen, das in Deiner Datei _build-ci.xml_ konfiguriert ist. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ Nachdem sowohl Build erfolgreich war und Deine Tests bestanden hat, wirst Du die Ant erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `build/jar`. Du kannst den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md index 3d713bc131..8dc6ce8aaa 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-gradle.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Um schnell loszulegen, kannst Du beim Erstellen eines neuen Workflows die vorkon Du kannst auch manuell diesen Workflow hinzufügen, indem Du eine neue Datei im Verzeichnis `.github/workflows` Deines Reporitorys erstellst. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ Der Starter-Workflow führt standardmäßig den Task `build` aus. In der Standar Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder einen anderen Task auszuführen möchtest, kannst Du dies angeben. Vielleicht möchtest Du beispielsweise den Task `package` ausführen, der in Deiner Datei _ci.gradle_ konfiguriert ist. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Nach einem erfolgreichen Lauf wird Dein lokaler Paket-Cache von Gradle in der Aktions-Infrastruktur auf GitHub gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Paket-Repositories heruntergeladen werden müssen. Weitere Informationen findest Du unter „Caching-Abhängigkeiten zur Beschleunigung von Workflows“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. + # Restoring these files from a GitHub Actions cache might cause problems for future builds. + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -Dieser Workflow speichert den Inhalt Deines lokalen Gradle-Package-Caches im Verzeichnis `.gradle/caches` des Home-Verzeichnisses auf dem Runner. Der Cache-Schlüssel wird der gehashte Inhalt der Gradle-Build-Dateien sein, so dass Änderungen an ihnen den Cache ungültig machen. +This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache. ### Workflow-Daten als Artefakte paketieren @@ -122,7 +135,7 @@ Nachdem sowohl Build erfolgreich war und Deine Tests bestanden hat, wirst Du die Gradle erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `build/libs`. Du kannst den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md b/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md index 25029c9c1a..eff8ccd6f3 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-java-with-maven.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Um schnell loszulegen, kannst Du beim Erstellen eines neuen Workflows die vorkon Du kannst auch manuell diesen Workflow hinzufügen, indem Du eine neue Datei im Verzeichnis `.github/workflows` Deines Reporitorys erstellst. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ Der Starter-Workflow führt standardmäßig das „target“ (Ziel) `package` au Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder ein anderes Ziel auszuführen möchtest, kannst Du dies angeben. Vielleicht möchtest Du beispielsweise das Ziel `verify` ausführen, das in Deiner Datei _pom-ci.xml_ konfiguriert ist. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Nach einem erfolgreichen Lauf wird Dein lokales Maven-Repository in der Aktions-Infrastruktur auf GitHub gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Maven-Repositories heruntergeladen werden müssen. Weitere Informationen findest Du unter „Caching-Abhängigkeiten zur Beschleunigung von Workflows“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -122,7 +126,7 @@ Nachdem sowohl Build erfolgreich war und Deine Tests bestanden hat, wirst Du die Maven erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `target`. Um diese als Artefakte hochzuladen, kannst du sie in ein neues Verzeichnis kopieren, welches Artefakte zum Hochladen enthält. Zum Beispiel kannst Du ein Verzeichnis namens `staging` erstellen. Dann kannst Du den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/de-DE/content/actions/guides/building-and-testing-net.md b/translations/de-DE/content/actions/guides/building-and-testing-net.md index 763ac81bed..3d9911625b 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-net.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. -The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action. #### Using multiple .NET versions @@ -125,7 +125,7 @@ steps: You can cache NuGet 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 example, the YAML below installs the `Newtonsoft` package. -For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." +Weitere Informationen findest Du unter „[Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern](/actions/guides/caching-dependencies-to-speed-up-workflows)“. {% raw %} ```yaml diff --git a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md index fa5b29c599..8d388edcea 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md @@ -9,6 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} @@ -77,7 +81,7 @@ The template includes a matrix strategy that builds and tests your code with fou Jeder Job in der Matrix kann mithilfe des `Matrix`-Kontexts auf den im Array `node-version` definierten Wert zugreifen. Die Aktion `setup-node` verwendet den Kontext als Eingabe für `node-version`. Die Aktion `setup-node` konfiguriert jeden Job mit einer anderen Node.js-Version bevor sie den Code baut und testet. Weitere Informationen zu Matrix-Strategien und Kontexten findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)“ und „[Kontext- und Ausdruckssyntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. {% raw %} -```yaml +```yaml{:copy} strategy: matrix: node-version: [10.x, 12.x, 14.x, 15.x] @@ -93,7 +97,7 @@ steps: Alternativ kannnst Du auch mit genauen Node.js-Versionen bauen und testen. -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -102,7 +106,7 @@ strategy: Oder Du kannst auch mithilfe einer einzelnen Version von Node.js bauen und testen. {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -136,7 +140,7 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can Dieses Beispiel installiert die Abhängigkeiten, die in der Datei *package.json* definiert sind. Weitere Informationen findest Du unter [`npm install`](https://docs.npmjs.com/cli/install). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -150,7 +154,7 @@ steps: Du kannst mithilfe `npm ci` die Versionen in der Datei *package-lock.json* oder *npm-shrinkwrap.json* installieren und Aktualisierungen der Sperrdatei verhindern. `npm ci` zu verwenden ist gewöhnlich schneller als `npm install` laufen zu lassen. Weitere Informationen findest Du unter [`npm ci`](https://docs.npmjs.com/cli/ci.html) und „[Einführung in `npm ci` für schnellere und zuverlässigere Builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)“. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -166,7 +170,7 @@ steps: Dieses Beispiel installiert die Abhängigkeiten, die in der Datei *package.json* definiert sind. Weitere Informationen findest Du unter [`Yarn-Installation`](https://yarnpkg.com/en/docs/cli/install). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -179,7 +183,7 @@ steps: Alternativ kannst Du `--frozen-lockfile` übergeben, um die Versionen in der Datei *yarn.lock* zu installieren und Aktualisierungen der Datei *yarn.lock* zu verhindern. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -201,7 +205,7 @@ Im folgenden Beispiel enthält das Geheimnis `NPM_TOKEN` den npm-Authentifizieru Bevor Du Abhängigkeiten installierst, verwende die Aktion `setup-node`, um die Datei *.npmrc* zu erstellen. Die Aktion hat zwei Eingabeparameter. Der Parameter `node-version` legt die Version von Node.js fest und der Parameter `registry-url` bestimmt die Standard-Registry. Wenn Deine Paket-Registry Geltungsbereiche verwendet, musst Du den Parameter `scope` verwenden. Weitere Informationen findest Du unter [`npm-scope`](https://docs.npmjs.com/misc/scope). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -220,7 +224,7 @@ steps: Das obige Beispiel erzeugt eine *.npmrc* Datei mit folgendem Inhalt: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -231,7 +235,7 @@ always-auth=true When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. Weitere Informationen findest Du unter „Caching-Abhängigkeiten zur Beschleunigung von Workflows“ und der [Aktion `cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -256,7 +260,7 @@ steps: Du kannst die gleichen Befehle verwenden, die Du auch lokal verwendest, um Deinen Code zu erstellen und zu testen. Wenn Du beispielsweise `npm run build` ausführst, um die in Deinem *package.json* definierten Build-Schritte zu durchlaufen, und `npm test`, um Deine Testsuite laufen zu lassen, dann fügst Di diese Befehle in Deine Workflow-Datei ein. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md index 2e398c4b81..a00b552d6e 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md @@ -8,6 +8,9 @@ versions: authors: - potatoqualitee type: 'tutorial' +topics: + - 'CI' + - 'Powershell' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/building-and-testing-python.md b/translations/de-DE/content/actions/guides/building-and-testing-python.md index f8f785f490..f0ea1f23c3 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-python.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-python.md @@ -8,6 +8,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Du solltest ein grundlegendes Verständnis von Python, PyPy und pip haben. Weite Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -94,7 +97,7 @@ Wenn Du einen selbst gehosteten Runner verwendest, kannst Du den Runner so konfi #### Mehrere Python-Versionen verwenden {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -126,7 +129,7 @@ jobs: Du kannst eine bestimmte Version von Python konfigurieren, For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. Dieses Beispiel verwendet das neueste Minor Release von Python 3. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -158,7 +161,7 @@ Wenn du eine Version von Python angibst, die nicht verfügbar ist, schlägt `set Du kannst in Deinem Workflow auch das Schlüsselwort `exclude` verwenden, wenn Du eine bestimmte Konfiguration von Python nicht laufen lassen möchtest. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)“. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -196,7 +199,7 @@ Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist der Pake When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Weitere Informationen findest Du unter „Abhängigkeiten zur Beschleunigung von Workflows im Cache zwischenspeichern“. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -213,7 +216,7 @@ steps: Nach dem Update von `pip` werden üblicherweise im nächsten Schritt die Abhängigkeiten aus *requirements.txt* installiert. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -234,7 +237,7 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can 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). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Setup Python @@ -271,7 +274,7 @@ Du kannst die gleichen Befehle verwenden, die Du auch lokal verwendest, um Deine 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -295,7 +298,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -318,7 +321,7 @@ steps: 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 +```yaml{:copy} name: Python package on: [push] @@ -352,7 +355,7 @@ You can upload artifacts to view after a workflow completes. Zum Beispiel kann e 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 +```yaml{:copy} name: Python package on: [push] @@ -365,26 +368,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} ``` {% endraw %} @@ -395,7 +398,7 @@ You can configure your workflow to publish your Python package to any package re You can store any access tokens or credentials needed to publish your package using secrets. The following example creates and publishes a package to PyPI using `twine` and `dist`. Weitere Informationen findest Du unter "[Verschlüsselte Geheimnisse erstellen und verwenden](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". {% raw %} -```yaml +```yaml{:copy} name: Upload Python Package on: diff --git a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md index 92c0146bc6..6f4c3b4c62 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md @@ -6,6 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Ruby' --- {% data reusables.actions.enterprise-beta %} @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -63,7 +63,7 @@ jobs: The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index aa8068a207..d5d929d677 100644 --- a/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -10,6 +10,8 @@ redirect_from: versions: free-pro-team: '*' type: 'tutorial' +topics: + - 'Workflows' --- ### Informationen zum Zwischenspeichern von Workflow-Abhängigkeiten @@ -68,7 +70,7 @@ Weitere Informationen findest Du unter [`Aktionen/Cache`](https://github.com/act Dieses Beispiel erzeugt einen neuen Cache, wenn sich die Pakete in `package-lock.json` ändern oder wenn das Betriebssystem des Runners wechselt. Das folgende Beispiel verwendet Kontexte und Ausdrücke, um einen Schlüssel zu erzeugen, der eine Kennung des Runner-Betriebssystems und einen SHA-256-Hash der Datei `package-lock.json` enthält. {% raw %} -```yaml +```yaml{:copy} name: Caching mit npm on: push @@ -124,14 +126,14 @@ Ein Cache-Key (Cache-Schlüssel) kann Kontexte, Funktionen, Literale und Operato Wenn Du zum Erstellen eines `key`s Ausdrücke verwendest, kannst Du automatisch einen neuen Cache zu erstellen, sobald sich die Abhängigkeiten geändert haben. Zum Beispiel kannst Du einen `key` mittels eines Ausdrucks erstellen, der den Hash-Code einer npm-Datei `package-lock.json` errechnet. {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %} wertet den Ausdruck aus `hash "package-lock.json"` um daraus den endgültigen `key` abzuleiten. -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ Du kannst eine Liste der `restore-keys` angeben, die verwendet werden sollen, we #### Beispiel für die Verwendung mehrerer Restore-Keys {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | Der Runner bewertet die Ausdrücke, die sich in folgende `restore-keys` auflösen lassen: {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md b/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md index dd87337ef7..98209d14b8 100644 --- a/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md @@ -10,6 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Es kann Dir auch helfen, YAML, die Syntax für {% data variables.product.prodnam {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL service example on: push @@ -94,7 +97,7 @@ jobs: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} jobs: # Label des Container-Jobs container-job: @@ -124,7 +127,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI-Tests starten - name: Check out repository code @@ -159,7 +162,7 @@ Wenn Du einen Job direkt auf der Runner-Maschine ausführst, musst Du die Ports {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL Service Example on: push @@ -220,7 +223,7 @@ jobs: Der Workflow ordnet Port 5432 des PostgreSQL-Service-Containers dem Docker-Host zu. Weitere Informationen über das Schlüsselwort `ports` findest Du unter "[Informationen über Service-Container](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)." -```yaml +```yaml{:copy} jobs: # Label des Runner-Jobs runner-job: @@ -251,7 +254,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI-Tests starten - name: Check out repository code @@ -287,7 +290,7 @@ Du kannst *client.js* anpassen, um alle PostgreSQL-Vorgänge einzuschließen, di {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/de-DE/content/actions/guides/creating-redis-service-containers.md b/translations/de-DE/content/actions/guides/creating-redis-service-containers.md index e121a41e5f..6a1aa16d0f 100644 --- a/translations/de-DE/content/actions/guides/creating-redis-service-containers.md +++ b/translations/de-DE/content/actions/guides/creating-redis-service-containers.md @@ -10,6 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Es kannst Dir helfen, wenn Du ein grundlegendes Verständnis von YAML, der Synta {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -91,7 +94,7 @@ jobs: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} jobs: # Label des Container-Jobs container-job: @@ -118,7 +121,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI tests gestartet werden - name: Check out repository code @@ -152,7 +155,7 @@ Wenn Du einen Job direkt auf der Runner-Maschine ausführst, musst Du die Ports {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis runner example on: push @@ -210,7 +213,7 @@ jobs: Der Workflow ordnet Port 6379 des Redis-Service-Containers dem Docker-Host zu. Weitere Informationen über das Schlüsselwort `ports` findest Du unter "[Informationen über Service-Container](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)." -```yaml +```yaml{:copy} jobs: # Label des Runner-Jobs runner-job: @@ -238,7 +241,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI tests gestartet werden - name: Check out repository code @@ -274,7 +277,7 @@ Du kannst *client.js* anpassen, um alle Redis-Operationen abzudecken, die Dein W {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // Erzeugt einen neuen Redis-Client diff --git a/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md index dd137836d4..4c992cb81a 100644 --- a/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/deploying-to-azure-app-service.md b/translations/de-DE/content/actions/guides/deploying-to-azure-app-service.md index 86dfb41e3b..388d5b708d 100644 --- a/translations/de-DE/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/de-DE/content/actions/guides/deploying-to-azure-app-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Azure App Service' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/de-DE/content/actions/guides/deploying-to-google-kubernetes-engine.md index c2f0870656..ff85e4bbed 100644 --- a/translations/de-DE/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/de-DE/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/index.md b/translations/de-DE/content/actions/guides/index.md index c432c2ebb3..1c61a50a7c 100644 --- a/translations/de-DE/content/actions/guides/index.md +++ b/translations/de-DE/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/de-DE/content/actions/guides/publishing-docker-images.md b/translations/de-DE/content/actions/guides/publishing-docker-images.md index c987e76b81..9c8569174f 100644 --- a/translations/de-DE/content/actions/guides/publishing-docker-images.md +++ b/translations/de-DE/content/actions/guides/publishing-docker-images.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Pakete erstellen' + - 'Publishing' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -55,7 +59,7 @@ Um zum „Docker Hub“ zu pushen, benötigst Du ein Benutzerkonto auf „Docker * `repository`: Dein „Docker Hub“-Repository im Format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -93,7 +97,7 @@ Die für {% data variables.product.prodname_registry %} erforderlichen `build-pu * `repository`: Muss im Format `OWNER/REPOSITORY/IMAGE_NAME` gesetzt werden. Beispiel: Für ein Bild namens `octo-image` auf {% data variables.product.prodname_dotcom %} unter `http://github. om/octo-org/octo-repo` sollte die Option `repository` auf `octo-org/octo-repo/octo-image` gesetzt werden. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -126,7 +130,7 @@ In einem einzigen Workflow kannst Du Dein Docker-Image in mehreren Registries ve Der folgende Beispiel-Workflow verwendet die Schritte der `build-push-action` aus den vorherigen Abschnitten („[Veröffentlichung von Bildern auf ‚Docker Hub‘](#publishing-images-to-docker-hub)“ und „[Veröffentlichung von Bildern in {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)“), um einen einzigen Workflow zu erstellen, der in beide Registries pusht. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: diff --git a/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md index 9b36a08e0c..f2b4dd58ac 100644 --- a/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md @@ -8,6 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Pakete erstellen' + - 'Publishing' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ Jedes Mal, wenn Du ein neues Release erstellst, kannst Du einen Workflow anstoß Du kannst ein neues Maven-Repository im Block `publishing` Deiner Datei _build.gradle_ definieren, das auf Dein Paket-Repository verweist. Wenn Du zum Beispiel über das OSSRH-Hosting-Projekt in das „Maven Central Repository“ deployst, kann Deine _build.gradle_ ein Repository mit dem Namen `"OSSRH"` bestimmen. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -67,7 +72,7 @@ Im Deploy-Schritt musst Du Umgebungsvariablen für den Benutzernamen und das Pas {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -105,7 +110,7 @@ Der `GITHUB_TOKEN` existiert standardmäßig in Deinem Repository und hat Lese- Wenn beispielsweise Deine Organisation „octocat“ und Dein Repository „hello-world“ heißt, sieht die {% data variables.product.prodname_registry %}-Konfiguration in _build.gradle_ so ähnlich wie im folgenden Beispiel aus. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -126,7 +131,7 @@ publishing { Mit dieser Konfiguration kannst Du einen Workflow erstellen, der mithilfe des Befehls `gradle publish` Dein Paket im „Maven Central Repository“ veröffentlicht. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -162,7 +167,7 @@ Wenn Du beispielsweise über das OSSRH-Hosting-Projekt in das Central Repository Wenn Deine Organisation „octocat“ und Dein Repository „hello-world“ heißt, sieht die {% data variables.product.prodname_registry %}-Konfiguration in _build.gradle_ so ähnlich wie im folgenden Beispiel aus. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -191,7 +196,7 @@ publishing { Mit dieser Konfiguration kannst Du einen Workflow erstellen, der mithilfe des Befehls `gradle publish` Dein Paket sowohl im „Maven Central Repository“ als auch in der {% data variables.product.prodname_registry %} veröffentlicht. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md b/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md index 5eb7aa29d7..c3947f6ea7 100644 --- a/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md @@ -8,6 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Pakete erstellen' + - 'Publishing' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +52,7 @@ In diesem Workflow kannst Du die Aktion `setup-java` verwenden. Diese Aktion ins Wenn Du zum Beispiel über das OSSRH-Hosting-Projekt ins „Maven Central Repository“ deployst, kann Deine _pom.xml_ ein Distributions-Management-Repository mit `ossrh` als `id` angeben. {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ Im Deploy-Schritt musst Du die Umgebungsvariablen auf den Benutzernamen setzen, {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ Für ein Maven-basiertes Projekt kannst Du diese Einstellungen nutzen, indem Du Wenn beispielsweise Deine Organisation „octocat“ und Dein Repository „hello-world“ heißt, sieht die {% data variables.product.prodname_registry %}-Konfiguration in _pom.xml_ so ähnlich wie im folgenden Beispiel aus. {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ Wenn beispielsweise Deine Organisation „octocat“ und Dein Repository „hell Mit dieser Konfiguration kannst Du einen Workflow erstellen, der Dein Paket in der {% data variables.product.prodname_registry %} veröffentlicht, indem Du die automatisch generierte _settings.xml_ verwendest. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ Du kannst Deine Pakete sowohl im Maven Central Repository als auch in der {% dat Stelle sicher, dass Deine Datei _pom.xml_ ein Distributionsmanagement-Repository sowohl für Dein {% data variables.product.prodname_dotcom %}-Repository als auch Deinen „Maven Central Repository“-Provider enthält. Wenn Du z.B. über das Hosting-Projekt OSSRH in das Central Repository deployst, solltest Du es vielleicht in einem Distributionsverwaltungs-Repository mit `ossrh` als `id` angeben, und Du solltest {% data variables.product.prodname_registry %} in einem Distributionsverwaltungs-Repository mit `github` als `id` setzen. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md index 4eb37d6e8b..17d3c480d7 100644 --- a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md @@ -9,6 +9,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Pakete erstellen' + - 'Publishing' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} @@ -54,7 +59,7 @@ Wenn Du ein Paket veröffentlichst, das einen Präfix für den „scope“ (Gelt Dieses Beispiel speichert das Geheimnis `NPM_TOKEN` in der Umgebungsvariablen `NODE_AUTH_TOKEN`. Wenn die Aktion `setup-node` eine Datei *.npmrc* erzeugt, referenziert sie das Token aus der Umgebungsvariable `NODE_AUTH_TOKEN`. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -78,7 +83,7 @@ jobs: Im obigen Beispiel erzeugt die Aktion `setup-node` auf dem Runner eine Datei *.npmrc* mit folgendem Inhalt: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -114,7 +119,7 @@ If you want to publish your package to a different repository, you must use a pe Dieses Beispiel speichert das Geheimnis `GITHUB_TOKEN` in der Umgebungsvariablen `NODE_AUTH_TOKEN`. Wenn die Aktion `setup-node` eine Datei *.npmrc* erzeugt, referenziert sie das Token aus der Umgebungsvariable `NODE_AUTH_TOKEN`. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -140,7 +145,7 @@ jobs: Die Aktion `setup-node` erzeugt eine Datei *.npmrc* auf dem Runner. Wenn Du für die Aktion `setup-node` die Eingabe `scope` verwendest, enthält die Datei *.npmrc* das Präfix „scope“. Standardmäßig legt die Aktion `setup-node` den „Scope“ (Geltungsbereich) in der Datei *.npmrc* auf das Konto fest, das diese Workflow-Datei enthält. -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -151,7 +156,7 @@ always-auth=true Wenn Du den Paketmanager „Yarn“ verwendest, kannst Du mit Yarn Pakete installieren und veröffentlichen. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -167,7 +172,7 @@ jobs: node-version: '12.x' registry-url: 'https://registry.npmjs.org' # Defaults to the user or organization that owns the workflow file - scope: '@octocat' + scope: '@octocat' - run: yarn - run: yarn publish env: @@ -196,7 +201,7 @@ Wenn Du für die Aktion `setup-node` die Eingabe `scope` verwendest, erstellt di Dieser Workflow ruft die Aktion `setup-node` zweimal auf. Jedes Mal, wenn die Aktion `setup-node` ausgeführt wird, überschreibt sie die Datei *.npmrc*. Die Datei *.npmrc* referenziert den Token, mit dem Du authentifizierte Operationen in der Paket-Registry durchführen kannst, durch die Umgebungsvariable `NODE_AUTH_TOKEN`. Der Workflow setzt die Umgebungsvariable `NODE_AUTH_TOKEN` jedes Mal, wenn der Befehl `npm publish` ausgeführt wird; zuerst mit einem Token zum Veröffentlichen auf npm (`NPM_TOKEN`) und dann mit einem Token zum Veröffentlichen in der {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`). {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: diff --git a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md index 5f55719cb2..3d2c7d7bbb 100644 --- a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -12,6 +12,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} @@ -79,7 +81,7 @@ In diesem Beispiel wird gezeigt, wie Sie einen Workflow für ein Node.js-Projekt Der Workflow lädt die Produktionsartefakte in das `dist` Verzeichnis, schließt jedoch alle Markdowndateien aus. Es lädt auch die `code-coverage.html` Bericht als ein weiteres Artefakt. -```yaml +```yaml{:copy} Name: Node CI on: [push] @@ -114,7 +116,7 @@ jobs: 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' uses: actions/upload-artifact@v2 with: @@ -183,7 +185,7 @@ Auftrag 3 zeigt das im vorherigen Auftrag hochgeladene Ergebnis an: Die vollständige, in diesem Workflow-Beispiel durchgeführte mathematische Operation lautet `(3 + 7) x 9 = 90`. -```yaml +```yaml{:copy} name: Daten zwischen Jobs teilen: [push] diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 2e52517e81..75da4a3e35 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index d4a3eaaa3f..58bd9c548a 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -38,7 +38,7 @@ Wenn es nicht praktikabel ist, Umgebungsvariablen zu setzen, kannst Du die Proxy Eine beispielhafte Proxy-Konfiguration mittels _.env_ ist unten dargestellt: -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 2d324d5f3f..c849f67dae 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -64,8 +64,11 @@ Diese Labels funktionieren kumulativ, so dass die Labels eines selbst-gehosteten ### Routing precedence for self-hosted runners -If you use both repository-level and organization-level runners, {% data variables.product.prodname_dotcom %} follows an order of precedence when routing jobs to self-hosted runners: +When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels: -1. The job's `runs-on` labels are processed. {% data variables.product.prodname_dotcom %} then attempts to locate a runner that matches the label requirements: -2. The job is sent to a repository-level runner that matches the job labels. If no repository-level runner is available (either busy, offline, or no matching labels): -3. The job is sent to an organization-level runner that matches the job labels. If no organization-level runner is available, the job request fails with an error. +1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}. +2. The job is then sent to the first matching runner that is online and idle. + - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners. + - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners. + - If there are no matching runners at any level, the job will fail. + - If the job remains queued for more than 24 hours, the job will fail. diff --git a/translations/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md index a9c1273bc9..b05b8d6733 100644 --- a/translations/de-DE/content/actions/index.md +++ b/translations/de-DE/content/actions/index.md @@ -10,21 +10,22 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: + - + title: Environments, environment protection rules and environment secrets (beta) + date: '2020-12-15' + href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ - title: Workflow visualization date: '2020-12-08' @@ -33,10 +34,6 @@ changelog: title: Removing set-env and add-path commands on November 16 date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Ubuntu-latest workflows will use Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ @@ -73,7 +70,7 @@ versions: {% render 'code-example-card' for actionsCodeExamples as example %} - +
{% octicon "search" width="24" %}
diff --git a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md index dc998f2abf..6f9befb78b 100644 --- a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,7 +5,9 @@ intro: '{% data variables.product.prodname_actions %} are designed to help you b versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md index 5014f26491..35f77a4cf2 100644 --- a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} @@ -68,7 +70,7 @@ Schritte: #### Using SHAs -If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. This example targets an action's SHA: +If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA: ```yaml Schritte: diff --git a/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md index 12d906bf92..77a17c56d1 100644 --- a/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -9,7 +9,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -147,7 +149,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s ``` - Groups together all the steps that run in the check-bats-version job. Each line nested under this section is a separate action. + 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. @@ -180,7 +182,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s ``` - 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. + 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. diff --git a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md index fa4f83f75e..9ac1159626 100644 --- a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 7b7a59aac1..6c53150015 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Azure-Pipelines' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -62,16 +67,16 @@ Azure-Pipelines {% raw %} ```yaml jobs: -- job: scripts - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in the default shell" - - bash: echo "This step runs in bash" - - pwsh: Write-Host "This step runs in PowerShell Core" - - task: PowerShell@2 - inputs: - script: Write-Host "This step runs in PowerShell" + - job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" ``` {% endraw %} @@ -82,13 +87,13 @@ jobs: scripts: runs-on: windows-latest steps: - - run: echo "This step runs in the default shell" - - run: echo "This step runs in bash" - shell: bash - - run: Write-Host "This step runs in PowerShell Core" - shell: pwsh - - run: Write-Host "This step runs in PowerShell" - shell: powershell + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell ``` {% endraw %} @@ -123,11 +128,11 @@ Azure-Pipelines {% raw %} ```yaml jobs: -- job: run_command - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in CMD on Windows by default" + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} @@ -138,9 +143,9 @@ jobs: run_command: runs-on: windows-latest steps: - - run: echo "This step runs in PowerShell on Windows by default" - - run: echo "This step runs in CMD on Windows explicitly" - shell: cmd + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %} @@ -171,12 +176,12 @@ Azure-Pipelines {% raw %} ```yaml jobs: -- job: conditional - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This step runs with str equals 'ABC' and num equals 123" - condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) + - job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) ``` {% endraw %} @@ -187,8 +192,8 @@ jobs: conditional: runs-on: ubuntu-latest steps: - - run: echo "This step runs with str equals 'ABC' and num equals 123" - if: ${{ env.str == 'ABC' && env.num == 123 }} + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %} @@ -217,29 +222,29 @@ Azure-Pipelines {% raw %} ```yaml jobs: -- job: initial - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This job will be run first." -job: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout2." -job: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout1." -job: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - steps: - - script: echo "This job will run after fanout1 and fanout2 have finished." + - job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." + - job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." + - job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." + - job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -250,22 +255,22 @@ jobs: initial: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." fanout1: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout2." + - run: echo "This job will run after the initial job, in parallel with fanout2." fanout2: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout1." + - run: echo "This job will run after the initial job, in parallel with fanout1." fanin: runs-on: ubuntu-latest needs: [fanout1, fanout2] steps: - - run: echo "This job will run after fanout1 and fanout2 have finished." + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -294,15 +299,15 @@ Azure-Pipelines {% raw %} ```yaml jobs: -- job: run_python - pool: - vmImage: 'ubuntu-latest' - steps: - - task: UsePythonVersion@0 - inputs: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} @@ -313,11 +318,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 0a43eadf82..94ac77c65e 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CircleCI' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -258,24 +263,24 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 - # einen Gesundheitscheck zufuegen + - 5432:5432 + # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - # Diese Docker-Datei Setzt USER auf circleci statt dem Standardbenutzer, daher muessen wir die Datei-Berechtigungen fuer dieses Image aktualisieren, um auf GH-Aktionen arbeiten zu koennen. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem - - name: Setup file system permissions - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} @@ -412,35 +417,35 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - - uses: actions/checkout@v2 - - name: Setup Ruby - uses: eregon/use-ruby-action@master - with: - ruby-version: ${{ matrix.ruby }} - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: vendor/bundle - key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - name: Install postgres headers - run: sudo apt-get install libpq-dev - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake - - name: Install appraisal - run: bundle exec appraisal install - - name: Run appraisal - run: bundle exec appraisal rake + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %} diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 038f98e77d..15b189a387 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -5,6 +5,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'GitLab' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,12 +340,12 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} @@ -371,7 +376,7 @@ GitLab CI/CD script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -424,12 +429,12 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js tags: - docker ``` diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index d94f5ca274..58f1e92cbc 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Jenkins' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ Mit Jenkins kannst Du Builds an einen einzelnen Build-Agenten senden oder sie ü Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. Die folgende Tabelle vergleicht, wie das Konzept für verteilte Builds sowohl bei Jenkins als auch bei {% data variables.product.prodname_actions %} umgesetzt ist. | Jenkins | {% data variables.product.prodname_actions %} -| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`Agenten`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`Runner`](/actions/learn-github-actions/introduction-to-github-actions#runners)
[`selbst-gehostete Runner`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`Agenten`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
[`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### Sektionen verwenden, um Pipelines zu organisieren @@ -51,7 +56,6 @@ Jenkins teilt seine Deklarative Pipelines in mehrere Sektionen auf. Similarly, { | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### Anweisungen verwenden Jenkins verwendet Anweisungen um _Deklarative Pipelines_ zu verwalten. Diese Anweisungen definieren die Merkmale Deines Workflows und die Art und weise, wie dieser ausgeführt wird. Die folgende Tabelle zeigt, wie diese Anweisungen den Konzepten innerhalb von {% data variables.product.prodname_actions %} entsprechen. @@ -69,7 +73,6 @@ Jenkins verwendet Anweisungen um _Deklarative Pipelines_ zu verwalten. Diese Anw | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### Sequenzielle „Stages“ (Phasen) verwenden #### Parallele Verarbeitungvon Jobs @@ -114,23 +117,23 @@ Jenkins-Pipeline - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +``` @@ -150,25 +153,24 @@ Jenkins-Pipeline - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +``` @@ -188,30 +190,28 @@ Jenkins-Pipeline - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +``` @@ -231,26 +231,27 @@ Jenkins-Pipeline - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - name: demo-workflow - on: - push: - jobs: - test: - runs-on: ${{ matrix.os }} - strategy: - fail-fast: false - matrix: - os: [macos-latest, ubuntu-latest] - steps: - - uses: actions/checkout@v1 - - uses: actions/setup-node@v1 - with: - node-version: 12 - - run: npm install -g bats - - run: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index a88b435055..12f4fc0e89 100644 --- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Travis CI' + - 'Migration' + - 'CI' + - 'CD' --- ### Einführung @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -155,9 +160,9 @@ git: {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %} @@ -207,10 +212,10 @@ When working with different languages in {% data variables.product.prodname_acti Ein Beispiel: ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` ### Error handling in {% data variables.product.prodname_actions %} @@ -275,11 +280,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} @@ -345,20 +350,20 @@ Travis CI - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +``` @@ -378,24 +383,24 @@ Travis CI {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %} diff --git a/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 53a5a74c03..a0854e1ab0 100644 --- a/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Sicherheit --- {% data reusables.actions.enterprise-beta %} @@ -54,11 +56,13 @@ This means that a compromise of a single action within a workflow can be very si Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail. {% endwarning %} + {% endif %} * **Audit the source code of the action** @@ -140,4 +144,4 @@ The following tables describe the {% data variables.product.prodname_actions %} | `action:org.runner_group_removed` | Triggered when an organization admin removes a self-hosted runner group. | | `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | | `action:org.runner_group_runners_added` | Triggered when an organization admin [adds 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). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | diff --git a/translations/de-DE/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/de-DE/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index a708a029aa..887a65cdc6 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///Workflows//badge.svg In diesem Markdown-Beispiel wird ein Status-Badge für einen Workflow mit dem Namen "Greet Everyone" hinzugefügt. Die `owner` des Repositorys sind die `Aktionen` Organisation, und der name `REPOSITORY` ist `hello-world`. -``` +```markdown ! [Beispiel-Workflowname] (https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ In diesem Markdown-Beispiel wird ein Status-Badge für einen Workflow mit dem Na In diesem Markdown-Beispiel wird ein Status-Badge für einen Workflow mit dem Dateipfad `.github/workflows/main.yml`hinzugefügt. Die `owner` des Repositorys sind die `Aktionen` Organisation, und der name `REPOSITORY` ist `hello-world`. -``` +```markdown ! [Beispiel Workflowdateipfad] (https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ In diesem Markdown-Beispiel wird ein Status-Badge für einen Workflow mit dem Da In diesem Markdown-Beispiel wird ein Status-Badge für eine Verzweigung mit dem Namen `Feature-1-`hinzugefügt. -``` +```markdown ! [Beispiel-Zweigparameter] (https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ In diesem Markdown-Beispiel wird ein Status-Badge für eine Verzweigung mit dem In diesem Markdown-Beispiel wird ein Badge hinzugefügt, das den Status von Workflowausführungen anzeigt, die durch das `pull_request` -Ereignis ausgelöst werden. -``` +```markdown ! [Beispielereignisparameter] (https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md index b4323a2e0f..9dbdc56d21 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -18,7 +18,7 @@ To run a workflow manually, the workflow must be configured to run on the `workf To trigger the `workflow_dispatch` event on {% data variables.product.prodname_dotcom %}, your workflow must be in the default branch. Führen Sie die folgenden Schritte aus, um eine Workflowausführung manuell auszulösen. -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md index 5aa7046bab..04b6952aad 100644 --- a/translations/de-DE/content/actions/quickstart.md +++ b/translations/de-DE/content/actions/quickstart.md @@ -7,6 +7,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md index ea04f4ed54..95322f5003 100644 --- a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -186,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -348,7 +348,7 @@ Der Wert für `array` kann ein Array oder ein String sein. Alle Werte im `array` `join(github.event.issue.labels.*.name, ', ')` kann „Bug, Hilfe gesucht“ zurückgeben -#### toJson +#### toJSON `toJSON(value)` @@ -358,13 +358,13 @@ Gibt eine Pretty-Print-JSON-Darstellung von `value` zurück. Diese Funktion hilf `toJSON(job)` kann `{ "status": "Success" }` zurückgeben. -#### fromJson +#### fromJSON `fromJSON(value)` -Gibt ein JSON-Objekt für `value` zurück. Mit dieser Funktion kannst Du ein JSON-Objekt als ausgewerteten Ausdruck bereitstellen. +Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string. -##### Beispiel +##### Example returning a JSON object Dieser Workflow legt eine JSON-Matrix in einem Job fest und übergibt sie mittels einer Ausgabe und `fromJSON` an den nächsten Job. @@ -384,12 +384,33 @@ jobs: needs: job1 runs-on: ubuntu-latest strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} steps: - run: build ``` {% endraw %} +##### Example returning a JSON data type + +This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer. + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... +``` +{% endraw %} + #### hashFiles `hashFiles(path)` diff --git a/translations/de-DE/content/actions/reference/environment-variables.md b/translations/de-DE/content/actions/reference/environment-variables.md index 6c4e302fd9..c63bdaeade 100644 --- a/translations/de-DE/content/actions/reference/environment-variables.md +++ b/translations/de-DE/content/actions/reference/environment-variables.md @@ -21,15 +21,25 @@ versions: Um benutzerdefinierte Umgebungsvariablen festzulegen, musst Du die Variablen in der Workflow-Datei angeben. 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. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“. ```yaml -steps: - - name: Hello world - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +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. + +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 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV` environment file{% else %} `set-env` workflow command{% endif %} to set an environment variable that the following steps in a workflow can use. The {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}environment file{% else %} `set-env` command{% endif %} can be used directly by an action or as a shell command in a workflow file using the `run` keyword. Weitere Informationen findest Du unter „[Workflow-Befehle für {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)“. ### Standard-Umgebungsvariablen diff --git a/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md b/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md index 519cc8d08d..3696d67e0b 100644 --- a/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md @@ -257,7 +257,7 @@ During the execution of a workflow, the runner generates temporary files that ca **Warning:** 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 ``` @@ -272,11 +272,19 @@ Erstellt oder aktualisiert eine Umgebungsvariable für alle Aktionen, die als n #### Beispiel -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` - -Running `$action_state` in a future step will now return `yellow` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} #### Multiline strings @@ -291,7 +299,7 @@ For multiline strings, you may use a delimiter with the following syntax. ##### Beispiel 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 id: step_one diff --git a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md index 03fbfb9cd4..b76f689a7b 100644 --- a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ Name des Workflows. {% data variables.product.prodname_dotcom %} zeigt die Namen ### `on` -**Erforderlich** Name des Ereignisses auf {% data variables.product.prodname_dotcom %}, das den Workflow auslöst. Sie können einen `string` für ein einzelnes Ereignis, ein `array` mit Ereignissen, ein `array` mit Ereignis-`types` oder eine Ereigniskonfigurations-`map` festlegen, mit der ein Workflow geplant oder die Ausführung eines Workflows auf bestimmte Dateien, Tags oder Branch-Änderungen beschränkt wird. Eine Liste der verfügbaren Ereignisse finden Sie unter „[Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows)“. +**Required**. The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. Sie können einen `string` für ein einzelnes Ereignis, ein `array` mit Ereignissen, ein `array` mit Ereignis-`types` oder eine Ereigniskonfigurations-`map` festlegen, mit der ein Workflow geplant oder die Ausführung eines Workflows auf bestimmte Dateien, Tags oder Branch-Änderungen beschränkt wird. Eine Liste der verfügbaren Ereignisse finden Sie unter „[Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows)“. {% data reusables.github-actions.actions-on-examples %} @@ -286,7 +286,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al ### `jobs..runs-on` -**Erforderlich** Typ der Maschine, auf der der Job ausgeführt wird. Die Maschine kann entweder ein {% data variables.product.prodname_dotcom %}-gehosteter oder ein selbst-gehosteter Runner sein. +**Required**. The type of machine to run the job on. Die Maschine kann entweder ein {% data variables.product.prodname_dotcom %}-gehosteter oder ein selbst-gehosteter Runner sein. {% data reusables.actions.enterprise-github-hosted-runners %} @@ -299,6 +299,7 @@ Verfügbare Arten von {% data variables.product.prodname_dotcom %}-gehostete Run {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} ##### Beispiel @@ -518,7 +519,7 @@ Aktionen sind entweder JavaScript-Dateien oder Docker-Container. Bei Docker-Cont ```yaml steps: # Reference a specific commit - - uses: actions/setup-node@74bc508 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e # Reference the major version of a release - uses: actions/setup-node@v1 # Reference a minor version of a release @@ -700,12 +701,24 @@ steps: Mit `command […options] {0} [..more_options]` können Sie einen Vorlagen-String für den `shell`-Wert festlegen. {% data variables.product.prodname_dotcom %} interpretiert das erste Wort im String, nach dem ein „Whitespace“ (Zwischenraum-Zeichen) steht, als Befehl, und der Dateiname für das temporäre Skript wird in `{0}` eingefügt. +Ein Beispiel: + +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +The command used, `perl` in this example, must be installed on the runner. 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)." + #### Exit-Codes und Voreinstellung für Fehleraktionen Für integrierte Shell-Schlüsselwörter gelten die folgenden Standards, die durch auf {% data variables.product.prodname_dotcom %} gehostete Runner ausgeführt werden. Beachte diese Richtlinien beim Ausführen von Shell-Skripts. - `bash`/`sh`: - - Fail-Fast-Verhalten mit `set -e o pipefail`: Standard für `bash` und integrierte `shell`. Dies ist außerdem der Standard, wenn Du eine Option für eine Plattform außer Windows angibst. + - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. Dies ist außerdem der Standard, wenn Du eine Option für eine Plattform außer Windows angibst. - Wenn Du auf Fail-Fast verzichtest und stattdessen die volle Kontrolle übernehmen möchtest, stelle einen Vorlagen-String für die Shell-Optionen bereit. Beispiel: `bash {0}`. - sh-ähnliche Shells liefern beim Beenden als ihren eigenen Exit-Code den Exit-Code des letzten Befehls, der im Skript ausgeführt wurde. Dies ist auch das Standardverhalten für Aktionen. Der Runner meldet den Status des Schritts gemäß diesem Exit-Code als Fehler/Erfolg. @@ -1186,7 +1199,7 @@ Weitere Informationen zur Syntax für Branch-, Tag- und Pfadfilter finden Sie un | `'**'` | Abgleich mit allen Branch- und Tag-Namen. Dies ist das Standardverhalten, wenn Sie keinen `branches`- oder `tags`-Filter angeben. | `all/the/branches`

`every/tag` | | `'*feature'` | Das Zeichen `*` ist ein Sonderzeichen in YAML. Wenn ein Muster mit `*` beginnen soll, sind Anführungszeichen erforderlich. | `mona-feature`

`feature`

`ver-10-feature` | | `v2*` | Abgleich mit Branch- und Tag-Namen, die mit `v2` beginnen. | `v2`

`v2.0`

`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Abgleich mit allen semantischen Versions-Tags mit der Hauptversion 1 oder 2. | `v1.10.1`

`v2.0.0` | +| `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` | #### Muster für den Abgleich von Dateinamen diff --git a/translations/de-DE/content/admin/configuration/command-line-utilities.md b/translations/de-DE/content/admin/configuration/command-line-utilities.md index 3a1ac0f2c2..32d7172d3b 100644 --- a/translations/de-DE/content/admin/configuration/command-line-utilities.md +++ b/translations/de-DE/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` Dadurch können Sie den UUID Ihres Knotens in `cluster.conf` ermitteln. -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -545,8 +545,8 @@ ghe-dpages status ``` Um einen {% data variables.product.prodname_pages %}-Speicherdienst zu evakuieren, bevor ein Cluster-Knoten evakuiert wird: -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -571,16 +571,16 @@ ghe-spokes route Um Speicherdienste auf einem Cluster-Knoten zu evakuieren: -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage Mit diesem Dienstprogramm können Sie alle Speicherdienste evakuieren, bevor Sie einen Clusterknoten evakuieren. -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md b/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md index 7c37675b31..2d5a74ab3d 100644 --- a/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ For more information about contacting support, see "[About {% data variables.con - Wählen Sie im Dropdownmenü **Authentication** (Authentifizierung) den von Ihrem SMTP-Server verwendeten Verschlüsselungstyp aus. - Geben Sie im Feld **No-reply email address** („no-reply“-E-Mail-Adresse) die E-Mail-Adresse ein, die für alle Benachrichtigungs-E-Mails in den Feldern „From“ (Von) und „To“ (An) verwendet werden soll. - {% note %} - - **Hinweis:** Wenn Sie das Kontrollkästchen **Send from author** (Über Autor senden) im E-Mail-Webhook **Services** (Dienste) in einem Repository aktivieren, werden ausgehende E-Mails für dieses Repository über den Autor und nicht über die „no-reply“-E-Mail-Adresse gesendet. Weitere Informationen findest Du unter "[Informationen zu E-Mail-Benachrichtigungen für Pushes in Dein Repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)." - - {% endnote %} - 6. Wenn Sie alle eingehenden E-Mails verwerfen möchten, die an die „no-reply“-E-Mail-Adresse adressiert sind, sollten Sie **Discard email addressed to the no-reply email address** (An die „no-reply“-E-Mail-Adresse adressierte E-Mails verwerfen) aktivieren. ![Kontrollkästchen zum Verwerfen der an die „no-reply“-E-Mail-Adresse adressierten E-Mails](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. Wählen Sie unter **Support** (Unterstützung) einen Linktyp aus, um Ihren Benutzern zusätzliche Unterstützung zu bieten: - **Email** (E-Mail): Eine interne E-Mail-Adresse. @@ -155,7 +149,7 @@ Sie werden feststellen, dass `metroplex` die eingehende Nachricht empfängt, sie #### Ihre DNS-Einstellungen verifizieren -Damit eingehende E-Mails ordnungsgemäß verarbeitet werden, müssen Sie eine gültigen A-Datensatz (oder CNAME) und einen MX-Datensatz konfigurieren. Weitere Informationen finden Sie unter „[DNS- und Firewalleinstellungen zum Zulassen eingehender E-Mails konfigurieren](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)“. +Damit eingehende E-Mails ordnungsgemäß verarbeitet werden, müssen Sie eine gültigen A-Datensatz (oder CNAME) und einen MX-Datensatz konfigurieren. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." #### Einstellungen der Firewall oder der AWS-Sicherheitsgruppe überprüfen diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index a031528928..4b77e36abc 100644 --- a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -10,7 +10,7 @@ versions: ### About high availability replication for clusters -You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests without data loss. +You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage. In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests. diff --git a/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md index ef47d1f606..6b29151f91 100644 --- a/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ Wenn Sie einen Knoten offline nehmen, der Datendienste aufweist (wie Git, Pages ghe-spokes evac-status ``` Für {% data variables.product.prodname_pages %} + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} Für Storage ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ Wenn Sie einen Knoten offline nehmen, der Datendienste aufweist (wie Git, Pages 3. Nach Abschluss des Kopiervorgangs können Sie den Speicherdienst evakuieren. Führen Sie einen der folgenden Befehle aus: Für Git + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} Für {% data variables.product.prodname_pages %} + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} Nehmen Sie für Storage den Knoten offline. + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} Evakuieren Sie anschließend + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md b/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md index bbcafccd47..e86a7e5f7e 100644 --- a/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ Die Namen der Knoten können beliebige gültige Hostnamen sein. Die Namen werden Geben Sie den ersten Clusterknoten an, den Sie als den MySQL-Master über `mysql-server` und `mysql-master` konfiguriert haben. -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 3f21952063..80418a4783 100644 --- a/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -63,7 +63,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac * 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 on your enterprise instance, 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/docker-build-push-action@v1 ``` diff --git a/translations/de-DE/content/admin/overview/about-github-ae.md b/translations/de-DE/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..bad0c51fe9 --- /dev/null +++ b/translations/de-DE/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: About GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} is the most secure and compliant way to use {% data variables.product.prodname_dotcom %}.' +versions: + github-ae: '*' +--- + +### Informationen zu {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase developer velocity, automate entire workflows, secure your code, and collaborate in developers’ favorite tool. + +{% data variables.product.prodname_ghe_managed %} provides your organization with all the power of [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). With {% data variables.product.prodname_ghe_managed %}, you can also meet security and compliance goals with a suite of features and certifications that put you in control. + +### A highly available and planet-scale cloud + +{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. + +### Data residency + +All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region. + +### Encryption on your terms + +All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." + +### Isolated accounts + +All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." + +### Restricted network access + +Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." + +### Commercial and government environments + +{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization. + +### Premium Plus support + +Premium Plus support is available for all {% data variables.product.prodname_ghe_managed %} customers, to ensure you have the fastest and most personal support experience. A dedicated Account Manager will work with you to help you get the most out of {% data variables.product.prodname_dotcom %}. Our support team will resolve issues any time of day, in the shortest possible time. + +### Informationen zur Abrechnung für {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.about-billing %} For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." \ No newline at end of file diff --git a/translations/de-DE/content/admin/overview/index.md b/translations/de-DE/content/admin/overview/index.md index fd42df580f..18670dc5a8 100644 --- a/translations/de-DE/content/admin/overview/index.md +++ b/translations/de-DE/content/admin/overview/index.md @@ -12,6 +12,7 @@ Weitere Informationen zu oder zum Kauf von {% data variables.product.prodname_en ### Inhaltsverzeichnis +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} diff --git a/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md b/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md index 90dc19dfbd..2c79131491 100644 --- a/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ Wenn Du Benutzerlizenzen erneuern oder zu {% data variables.product.prodname_ent {% data reusables.enterprise-accounts.license-tab %} 12. Klicken Sie unter „Quick links“ (Schnellzugriff) auf **Update license** (Lizenz aktualisieren). ![Lizenz-Link aktualisieren](/assets/images/enterprise/business-accounts/update-license-link.png) 13. Klicke zum Auswählen Deiner Lizenz auf **Lizenzdatei** oder ziehe Deine Lizenzdatei auf **Lizenzdatei**. ![Lizenzdatei hochladen](/assets/images/enterprise/management-console/upload-license.png) -14. Klicke **Upload**. ![Upgrade-Start](/assets/images/enterprise/management-console/begin-upload.png) +14. Klicke **Upload**. ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %} ### Lizenznutzung anzeigen @@ -70,3 +72,23 @@ Auf {% data variables.product.prodname_ghe_server %} können Sie eine JSON-Datei {% data reusables.enterprise-accounts.license-tab %} 10. Klicke unter "Enterprise Server-Instanzen" auf **Servernutzung hinzufügen**. ![Link zum Hochladen der GitHub Enterprise Server-Nutzung](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. Laden Sie die JSON-Datei hoch, die Sie von {% data variables.product.prodname_ghe_server %} heruntergeladen haben.![„Drag and drop or select a file to upload“ (Hochzuladende Datei per Drag-and-Drop auswählen oder suchen)](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### Problemlösungen + +In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Restart the services for Git authentication and the HTTP server. + + {% warning %} + + **Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again. + +{% endif %} diff --git a/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md index e06b832e5f..045c0fb96b 100644 --- a/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -58,7 +58,8 @@ Außerhalb der `stdin` bereitgestellten Werte sind zusätzliche Variablen vorhan | $GITHUB_VIA | Die zum Erstellen des ref-Werts verwendete Methode.
**Mögliche Werte:**
- `auto-merge deployment api`
- `blob edit`
- `branch merge api`
- `branches page delete button`
- `git refs create api`
- `git refs delete api`
- `git refs update api`
- `merge api`
- `pull request branch delete button`
- `pull request branch undo button`
- `pull request merge api`
- `pull request merge button`
- `pull request revert button`
- `releases delete button`
- `stafftools branch restore`
- `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | Die Anzahl der Push-Optionen, die vom Client gesendet wurden. Weitere Informationen zu den Push-Optionen finden Sie unter „[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)“ in der Git-Dokumentation. | | $GIT_PUSH_OPTION_N | N entspricht hierbei einer ab 0 beginnenden Ganzzahl. Diese Variable enthält den String der vom Client gesendeten Push-Option. Die erste gesendete Option wird in GIT_PUSH_OPTION_0 gespeichert. Die zweite gesendete Option wird in GIT_PUSH_OPTION_1 gespeichert usw. Weitere Informationen zu den Push-Optionen finden Sie unter „[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)“ in der Git-Dokumentation. |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. |{% endif %} +| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. +{% endif %} ### Berechtigungen festlegen und einen Pre-Receive-Hook per Push-Vorgang an {% data variables.product.prodname_ghe_server %} übertragen @@ -93,30 +94,30 @@ Sie können ein Pre-Receive-Hook-Skript lokal testen, bevor Sie es auf Ihrer {% 2. Erstellen Sie eine Datei namens `Dockerfile.dev`, die Folgendes enthält: - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. Erstellen Sie ein Pre-Receive-Testskript namens `always_reject.sh`. Dieses Beispielskript lehnt alle Push-Vorgänge ab, was zum Sperren eines Repositorys nützlich ist: + 3. Erstellen Sie ein Pre-Receive-Testskript namens `always_reject.sh`. Dieses Beispielskript lehnt alle Push-Vorgänge ab, was zum Sperren eines Repositorys nützlich ist: - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 diff --git a/translations/de-DE/content/admin/user-management/audited-actions.md b/translations/de-DE/content/admin/user-management/audited-actions.md index aa50b69ea7..b21e5b9f54 100644 --- a/translations/de-DE/content/admin/user-management/audited-actions.md +++ b/translations/de-DE/content/admin/user-management/audited-actions.md @@ -80,7 +80,7 @@ versions: | Name | Beschreibung | | ------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | -| `repo.archive` | Ein Repository wurde archiviert. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)." | +| `repo.archived` | Ein Repository wurde archiviert. 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` | Einem Repository wurde ein Mitarbeiter hinzugefügt. | | `repo.config` | Ein Websiteadministrator hat erzwungene Push-Vorgänge blockiert. Weitere Informationen finden Sie unter „[Erzwungene Push-Vorgänge an ein Repository blockieren](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)“. | | `repo.create` | Ein Repository wurde erstellt. | @@ -89,7 +89,7 @@ versions: | `repo.rename` | Ein Repository wurde umbenannt. | | `repo.transfer` | Ein Benutzer hat eine Anfrage akzeptiert, ein übertragenes Repository zu empfangen. | | `repo.transfer_start` | Ein Benutzer hat eine Anfrage gesendet, ein Repository an einen anderen Benutzer oder an eine andere Organisation zu übertragen. | -| `repo.unarchive` | Die Archivierung eines Repositorys wurde aufgehoben. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% if enterpriseServerVersions contains currentVersion %} +| `repo.unarchived` | Die Archivierung eines Repositorys wurde aufgehoben. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% if enterpriseServerVersions contains currentVersion %} | `repo.config.disable_anonymous_git_access` | Anonymous Git read access is disabled for a repository. Weitere Informationen finden Sie unter „[Anonymen Git-Lesezugriff für ein Repository aktivieren](/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. Weitere Informationen finden Sie unter „[Anonymen Git-Lesezugriff für ein Repository aktivieren](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)“. | | `repo.config.lock_anonymous_git_access` | Die Einstellung für den anonymen Git-Lesezugriff eines Repositorys ist gesperrt, wodurch Repository-Administratoren daran gehindert werden, diese Einstellung zu ändern (zu aktivieren oder zu deaktivieren). Weitere Informationen finden Sie unter „[Änderung des anonymen Git-Lesezugriffs durch Benutzer verhindern](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)“. | diff --git a/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md b/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md index d7fb887ad4..3d2425fdf9 100644 --- a/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,11 +33,11 @@ Wenn Du den private Modus nicht aktiviert hast, hat das Migrationsskript keine A 1. Stellen Sie eine Verbindung zur Verwaltungsshell her. Weitere Informationen findest Du unter "[Auf die administrative Shell (SSH) zugreifen](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)." 2. Navigiere zum Verzeichnis `/data/github/current`. - ``` + ```shell cd /data/github/current ``` 3. Führe den Migrationsbefehl aus. - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` diff --git a/translations/de-DE/content/admin/user-management/viewing-push-logs.md b/translations/de-DE/content/admin/user-management/viewing-push-logs.md index ecc3902479..d9b2d1d5b9 100644 --- a/translations/de-DE/content/admin/user-management/viewing-push-logs.md +++ b/translations/de-DE/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ Push-Protokolleinträge zeigen: ### Push-Protokolle eines Repositorys anzeigen +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. 1. Navigieren Sie zu einem Repository. -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. In the upper-right corner of the repository's page, click +{% octicon "rocket" aria-label="The rocket ship" %}. + ![Raumschiffsymbol für den Zugriff auf die Einstellungen des Websiteadministrators](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. Klicken Sie auf der linken Seitenleiste auf **Push Log** (Push-Protokoll). ![Registerkarte „Push log“ (Push-Protokoll)](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### Push-Protokolle eines Repositorys an der Befehlszeile anzeigen -1. Stellen Sie eine SSH-Verbindung zu Ihrer Appliance her. Weitere Informationen finden Sie unter „[Auf die Verwaltungsshell (SSH) zugreifen](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)“. -2. Öffnen Sie im entsprechenden Git-Repository die Auditprotokolldatei: +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Öffnen Sie im entsprechenden Git-Repository die Auditprotokolldatei: ```shell ghe-repo owner/repository -c "less audit_log" ``` diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index c452b39751..9b1d2bb3cd 100644 --- a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ versions: ![Ein Tag in der Historie anzeigen](/assets/images/help/desktop/viewing-tags-in-history.png) 3. Alle dem Commit zugeordneten Tags sind in den Metadaten dieses Commits sichtbar. ![Ein Tag im Commit anzeigen](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### Deleting tags + +{% note %} + +**Note**: You can only delete tags associated with commits that have not yet been pushed. + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md index e19b3edd2e..bdc94c3ee7 100644 --- a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -80,7 +80,7 @@ The `hook_attributes` object has the following key: This example uses a form on a web page with a button that triggers the `POST` request for a user account: -``` +```html
Create a GitHub App Manifest:
@@ -111,7 +111,7 @@ This example uses a form on a web page with a button that triggers the `POST` re ``` This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. -``` +```html Create a GitHub App Manifest:
diff --git a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 74fe373fda..33c4c3b441 100644 --- a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -435,7 +435,7 @@ The code above gets the full repository name and the head SHA of the commit from ### Schritt 2.3. Running RuboCop -Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). +Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) for details and an example of the JSON format. +The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. Because this code stores the RuboCop results in a `@report` variable, it can safely remove the checkout of the repository. This code also parses the JSON so you can easily access the keys and values in your GitHub App using the `@output` variable. @@ -588,7 +588,7 @@ This code limits the total number of annotations to 50. But you can modify this When the `offense_count` is zero, the CI test is a `success`. If there are errors, this code sets the conclusion to `neutral` in order to prevent strictly enforcing errors from code linters. But you can change the conclusion to `failure` if you would like to ensure that the check suite fails when there are linting errors. -When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. +When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. This code also iterates through each error in the `offenses` array and collects the location of the offense and error message. After extracting the information needed, the code creates an annotation for each error and stores it in the `annotations` array. Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same. @@ -718,13 +718,13 @@ If the annotations are related to a file already included in the PR, the annotat If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button. -The RuboCop tool [offers](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. +The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set. In order to commit files, Git must know which [username](/articles/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. Ein Beispiel: -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 4b48f0dd57..54a6c2f416 100644 --- a/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ An _authorized_ OAuth App has access to all of the user's or organization owner' | Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. | | Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |{% endif %} +| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. +{% endif %} ### Requesting permission levels for resources diff --git a/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index d294e3c1d3..6a56ef04db 100644 --- a/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -89,7 +89,7 @@ Expiring user tokens are currently part of the user-to-server token expiration b 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 the beta for expiring user-to-server access tokens. -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", diff --git a/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md b/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md index 47019fdbe0..40cdc7e4dc 100644 --- a/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ To learn about publishing {% data variables.product.prodname_actions %} in {% da ### Apps -Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." +Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. + +To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments. + +To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)." + +#### New to apps? If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." +#### GitHub Apps vs. OAuth Apps + {% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." -If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. - -### Publishing an app to {% data variables.product.prodname_marketplace %} +### Publishing an app to {% data variables.product.prodname_marketplace %} overview When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: @@ -38,13 +46,9 @@ When you have finished creating your app, you can share it with other users by p 1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." - 1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." - -An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." ### Seeing how your app is performing @@ -52,3 +56,7 @@ You can access metrics and transactions for your listing. Weitere Informationen - "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" - "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" + +### Contacting Support + +If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. diff --git a/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md b/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..eb26c0030a --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: About marketplace badges +intro: 'Learn about the badges that you may see for some apps and actions listings on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### For GitHub Apps + +Apps with the {% octicon "verified" aria-label="The verified badge" %}, are owned by an organization that has: +- Confirmed their domain +- Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization +- Required two-factor authentication for their organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)“. + +![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +To learn how you can add this badge to your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### For GitHub actions + +Actions with the {% octicon "verified" aria-label="The verified badge" %}, or verified creator badge, indicate that {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization. + +![Verified creator badge for GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +For information on how to publish a GitHub action to {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." + +### About the previous verification process for apps + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**Note:** The new publisher verification process for apps replaces the previous process where individual apps were verified. The new publisher verification process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..8131b7bf11 --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Applying for publisher verification for your organization +intro: 'To offer paid plans for your app or to include a marketplace badge in your app listing, you must complete the publisher verification process for your organization.' +versions: + free-pro-team: '*' +--- + +Publisher verification ensures that {% data variables.product.prodname_dotcom %} has a way to contact you, that you've enabled two-factor authentication for your organization, and that your organization's domain has been verified. + +Once your organization has been verified, you can publish paid plans for your app. For information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)." + +### Requesting publisher verification + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. Klicke auf der linken Seitenleiste auf **Developer settings** (Entwicklereinstellungen). ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) +1. Under "Publisher Verification", complete the information in the checklist: + - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. + - Ensure that Two-factor authentication is enabled for your organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)“. + - Submit a verified domain. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + + ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) + +1. Click **Request Verification**. {% data variables.product.company_short %} will review your details and let you know once your publisher verification is complete. + +### Weiterführende Informationen + +For information about the process of publishing apps, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)." diff --git a/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 52c2c64dc9..033802f582 100644 --- a/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ Once you've created a {% data variables.product.prodname_marketplace %} draft li ### Submitting your app -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. ### Removing a {% data variables.product.prodname_marketplace %} listing diff --git a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview.md b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..5b8799f9d9 --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,8 @@ +--- +title: GitHub Marketplace Overview +intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/developers/github-marketplace/index.md b/translations/de-DE/content/developers/github-marketplace/index.md index 612c9ed17c..ba99540576 100644 --- a/translations/de-DE/content/developers/github-marketplace/index.md +++ b/translations/de-DE/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md index a6c8b87456..4bcccd4e00 100644 --- a/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ To protect your customers, we recommend that you also follow security best pract ### Requirements for paid apps -In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transfering ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: - {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. - {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. - All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. -- Publishing organizations must have a verified domain and must enable two-factor authentication. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)“. -When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} diff --git a/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 9ab919817d..52f91dd1ab 100644 --- a/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,11 +19,13 @@ versions: ### About setting pricing plans -If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." -{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." +To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." +If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. + +![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png) ### About saving pricing plans diff --git a/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md index b25c4580ae..6b338d826b 100644 --- a/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: Submitting your listing for publication -intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +intro: 'To finish your app listing submission, you can request a review by an onboarding expert.' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +Once your app listing meets the {% data variables.product.prodname_marketplace %} requirements, you can submit your app. For an overview of the app listing requirements, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +1. In the top left of the app listing page, click **Overview**. For information on finding your app listing page, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + ![Overview option for the marketplace draft listing](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) +2. To submit your your completed app listing, click **Request review**. -{% data reusables.marketplace.launch-with-free %} + !["Publish your app to Marketplace" checklist with submission button at the bottom](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -After you submit your listing for review, an onboarding expert will reach out to you with additional information. - -For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." - -### Prerequisites for publishing with verification - -Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." - -If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. - -### Transferring an app to an organization before you submit - -You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: - -1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" - -1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" +An onboarding expert will reach out to you with additional information. diff --git a/translations/de-DE/content/developers/overview/secret-scanning.md b/translations/de-DE/content/developers/overview/secret-scanning.md index 0744a72c4e..81c16008a3 100644 --- a/translations/de-DE/content/developers/overview/secret-scanning.md +++ b/translations/de-DE/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: Secret scanning intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. Secret scanning happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our secret scanning. +{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}. When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice. -When a match of your secret format is found in a private repository configured for secret scanning, then repository admins are alerted and can view and manage the secret scanning results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from secret scanning](/github/administering-a-repository/managing-alerts-from-secret-scanning)". +When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning)." {% note %} -**Note:** Secret scanning for private repositories is currently in beta. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. {% endnote %} -This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the secret scanning program. +This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. -### The secret scanning process +### The {% data variables.product.prodname_secret_scanning %} process -##### How secret scanning works in a public repository +##### How {% data variables.product.prodname_secret_scanning %} works in a public repository -The following diagram summarizes the secret scanning process for public repositories, with any matches sent to a service provider's verify endpoint. +The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint. -![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "Secret scanning flow") +![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow") -### Joining the secret scanning program on {% data variables.product.prodname_dotcom %} +### Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %} 1. Contact {% data variables.product.prodname_dotcom %} to get the process started. 1. Identify the relevant secrets you want to scan for and create regular expressions to capture them. -1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the secret scanning message payload. +1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the {% data variables.product.prodname_secret_scanning %} message payload. 1. Implement signature verification in your secret alert service. 1. Implement secret revocation and user notification in your secret alert service. +1. Provide feedback for false positives (optional). #### Contact {% data variables.product.prodname_dotcom %} to get the process started -To get the enrollment process started, email secret-scanning@github.com. +To get the enrollment process started, email secret-scanning@github.com. -You will receive details on the secret scanning program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. +You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. #### Identify your secrets and create regular expressions -To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the secret scanning program: +To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program: * A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later. * A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives. * The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type. -Send this information to secret-scanning@github.com. +Send this information to secret-scanning@github.com. #### Create a secret alert service @@ -61,7 +62,7 @@ Create a public, internet accessible HTTP endpoint at the URL you provided to us ##### Example POST sent to your endpoint -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ You can retrieve the {% data variables.product.prodname_dotcom %} secret scannin Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set. **Sample message sent to verify endpoint** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -315,4 +316,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### Implement secret revocation and user notification in your secret alert service -For secret scanning in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. +For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. + +#### Provide feedback for false positives + +We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at secret-scanning@github.com. + +When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats. + +You can send us the raw token: + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256: + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +A few important points: +- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both. +- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm. +- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed. + +{% note %} + +**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at secret-scanning@github.com. + +{% endnote %} + diff --git a/translations/de-DE/content/discussions/index.md b/translations/de-DE/content/discussions/index.md index 66dca4f270..429f32ddbd 100644 --- a/translations/de-DE/content/discussions/index.md +++ b/translations/de-DE/content/discussions/index.md @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -43,7 +43,7 @@ versions: {% render 'discussions-community-card' for discussionsCommunityExamples as example %}
{% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
{% octicon "search" width="24" %}
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..5712d78d81 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +title: Informationen zu Campus Advisors +intro: 'Lernen Sie als Instrukteur oder Mentor, {% data variables.product.prodname_dotcom %} an Ihrer Einrichtung mit Campus Advisors-Schulungen und -Support zu verwenden.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-advisors + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Professoren, Lehrer und Mentoren können die Onlineschulungen von Campus Advisors nutzen, um den Umgang mit Git und {% data variables.product.prodname_dotcom %} sowie Best Practices für das Unterrichten von Studenten mit {% data variables.product.prodname_dotcom %} zu erlernen. Weitere Informationen findest Du unter „[Campus Advisors](https://education.github.com/teachers/advisors).“ + +{% note %} + +**Hinweis:** Als Kursleiter kannst Du keine {% data variables.product.prodname_dotcom %}-Konten für Deine Studenten erstellen. Studenten müssen ihre eigenen {% data variables.product.prodname_dotcom %}-Konten erstellen. + +{% endnote %} diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..7a9e68fc4d --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: Informationen zu Campus Experts +intro: 'Erwirb Dir als Student mit Campus Experts-Schulungen für {% data variables.product.prodname_dotcom %} die notwendigen Fähigkeiten, um die Technologie-Community an Deiner Bildungseinrichtung sowie ein realistisches Portfolio aufzubauen.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +Erlernen von Fähigkeiten in den Bereichen öffentliches Reden, technisches Schreiben, Community Leadership und Softwareentwicklung als Campus Experts für {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Campus Experts](https://education.github.com/students/experts).“ diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..3a6823404c --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: Informationen über GitHub Education für Lehrer und Forscher +intro: '{% data variables.product.prodname_education %} bietet eine Vielzahl von Tools, mit denen Lehrer und Forscher innerhalb und außerhalb des Unterrichts effektiver arbeiten können.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} für Lehrer + +Die Werkzeuge und Dienste von {% data variables.product.prodname_education %} für Lehrer aller Bildungsebenen ermöglichen Dir Folgendes: + - Verwende [{% data variables.product.prodname_classroom %}](https://classroom.github.com), um Code zu verteilen, Schülern und Studenten Feedback zu geben und Aufgaben auf {% data variables.product.prodname_dotcom %} einzusammeln. + - Tritt unserer [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) bei, um mit Deinen Kollegen aus der ganzen Welt über aktuelle Trends in der technologischen Bildung zu diskutieren. + - Greife auf unsere [Open-Source-Lehrpläne](https://education.github.community/t/open-source-lesson-plans/1591) zum Unterrichten von Git und {% data variables.product.prodname_dotcom %} zu und passe diese an. + - [Fordere eine {% data variables.product.prodname_dotcom %}-Tasche](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) mit Lehrmaterialien und Aufmerksamkeiten für Deine Schüler und Studenten an. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} für Forscher + +Die Werkzeuge und Dienste von {% data variables.product.prodname_education %} für Forscher ermöglichen Dir Folgendes: + - Arbeite weltweit auf {% data variables.product.prodname_dotcom %} mit anderen Personen gemeinsam an Deiner Forschungsarbeit. + - [Erfahre](https://education.github.com/stories), wie akademische Einrichtungen auf der ganzen Welt {% data variables.product.prodname_dotcom %} für ihre Forschung verwenden. + {% data reusables.education.apply-for-team %} + +### Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_education %} für Schüler und Studenten](/articles/about-github-education-for-students)“ diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..992f08d186 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: Informationen zu GitHub Education für Schüler und Studenten +intro: '{% data variables.product.prodname_education %} bietet Schülern und Studenten praktische Erfahrung mit kostenlosem Zugriff auf verschiedene Entwicklertools von Partnern von {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Die Verwendung von {% data variables.product.prodname_dotcom %} für Ihre Projektarbeiten ist ein praktischer Weg, um mit anderen zusammenzuarbeiten und ein Portfolio aufzubauen, das Ihre praktische Erfahrung zeigt. + +{% data reusables.education.about-github-education-link %} + +Jeder mit einem {% data variables.product.prodname_dotcom %}-Konto kann unbegrenzt in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_free_user %} zusammenarbeiten. Als Schüler oder Student können Sie auch das {% data variables.product.prodname_student_pack %} beantragen, das kostenlosen Zugriff auf Tools und Dienste bietet, die von professionellen Entwicklern verwendet werden. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +Wenn Sie Mitglied in einem FIRST Robotics Club sind, kann Ihr Lehrer einen Rabatt beantragen, damit Ihr Team mit {% data variables.product.prodname_team %} zusammenarbeiten kann, wodurch eine unbegrenzte Anzahl von Benutzern und privaten Repositorys kostenlos genutzt werden kann. For more information, see "[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)." + +### Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_education %} für Lehrer und Forscher](/articles/about-github-education-for-educators-and-researchers)“ diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..6f659dca01 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: Informationen zu GitHub Education +intro: '{% data variables.product.prodname_education %} bietet ein spezielles kostenloses Produkt für Bildungseinrichtungen, die {% data variables.product.prodname_dotcom %} optimal für ihre Community nutzen möchten und den spezifischen Programmanforderungen zustimmen.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +Wenn Ihre Schule bestimmte Anforderungen erfüllt, kann Ihre weiterführende Schule, Ihre Universität oder Ihr Schülercamp {% data variables.product.prodname_education %} und damit das Beste von {% data variables.product.prodname_dotcom %} kostenlos nutzen, einschließlich +- {% data variables.product.prodname_ghe_cloud %} und/oder {% data variables.product.prodname_ghe_server %}, +- Lehrerschulung zur Beherrschung von Git und {% data variables.product.prodname_dotcom %} mit unserem Campus Advisors-Programm, +- automatisierter Zugriff auf die Premiumfunktionen von {% data variables.product.prodname_education %}, wie z. B. das {% data variables.product.prodname_student_pack %}, +- Schulungen für Schüler und Studenten mit dem Campus Experts-Programm zur Entwicklung von Leadership und technischer Kompetenz. + +Weitere Informationen findest Du auf der [offiziellen {% data variables.product.prodname_education %}-Seite](https://education.github.com/partners/schools). + +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)." + +Weitere Informationen zu Schulungsprogrammen für Schüler, Studenten und Lehrer findest Du unter „[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)“ und „[Campus Advisors](https://education.github.com/teachers/advisors).“ + +Wenn Sie Schüler, Student oder Lehrkraft sind und Ihre Einrichtung nicht mit {% data variables.product.prodname_dotcom %} als {% data variables.product.prodname_education %}-Einrichtung kooperiert, können Sie trotzdem individuell Rabatte für die Nutzung von {% data variables.product.prodname_dotcom %} beantragen. For more information, see "[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)" or "[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/)." diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..4f5f29e9be --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: Apply for a student developer pack +intro: 'Studenten können das {% data variables.product.prodname_student_pack %} beantragen, das Angebote und Vorteile von {% data variables.product.prodname_dotcom %}-Partnern umfasst.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Anforderungen + +Damit Du ein {% data variables.product.prodname_student_pack %} nutzen kannst, musst Du: +- Derzeit als Schüler oder Student in einer Einrichtung eingeschrieben sein, die einen Abschluss oder ein Diplom verleiht, beispielsweise ein Gymnasium, eine weiterführende Schule, eine Hochschule, eine Universität, eine Heimschule oder eine ähnliche Bildungseinrichtung, +- Eine überprüfbare E-Mail-Adresse einer Hochschule besitzen oder Dokumente hochladen, die Deinen aktuellen Status als Student bestätigen +- Ein [{% data variables.product.prodname_dotcom %}-Benutzerkonto](/articles/signing-up-for-a-new-github-account) besitzen, +- Mindestens 13 Jahre alt sein + +Documents that prove your current student status include a picture of your school ID with current enrollment date, class schedule, transcript, and affiliation or enrollment verification letter. + +Während Deiner Zeit als Student wirst Du möglicherweise dazu aufgefordert, in regelmäßigen Abständen Deinen aktuellen akademischen Status zu bestätigen. + +{% note %} + +**Hinweis:** Du kannst akademische Rabatte nicht von einem Konto zu einem anderen übertragen. Wenn Du den Rabatt auf mehrere Konten anwenden möchtest, kannst Du Deine Benutzerkonten [zusammenführen](/articles/merging-multiple-user-accounts) und das resultierende Konto [umbenennen](/articles/changing-your-github-username), falls gewünscht. + +{% endnote %} + +Weitere Informationen zum Verlängerung Ihres {% data variables.product.prodname_student_pack %}s finden Sie unter „[Ablauf und Verlängerungen](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)“. + +### Ein {% data variables.product.prodname_student_pack %} beantragen + +{% data reusables.education.benefits-page %} +3. Wähle unter „Which best describes your academic status?“ (Was beschreibt Deinen akademischen Status am besten?) **Student** aus. ![Akademischen Status auswählen](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Ablauf und Verlängerungen + +Wenn Ihr Zugriff auf das {% data variables.product.prodname_student_pack %} abgelaufen ist, können Sie ihn erneut beantragen, sofern Sie die Voraussetzungen weiterhin erfüllen. Einige unserer Partnerangebote können jedoch nicht verlängert werden. Die meisten zeitlich begrenzten Angebote unserer Partner beginnen unmittelbar nachdem Du sie eingerichtet hast. Weitere Informationen findest Du auf der [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)-Seite. + +Angaben dazu, wann Ihr kostenloser Zugriff auf das {% data variables.product.prodname_student_pack %} abläuft, finden Sie in den [Abrechnungseinstellungen](https://github.com/settings/billing) Ihres Kontos. + +### Weiterführende Informationen + +- „[Warum wurde mein Antrag für das {% data variables.product.prodname_student_pack %}s abgelehnt?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)“ +- „[Für ein neues {% data variables.product.prodname_dotcom %}-Konto anmelden](/articles/signing-up-for-a-new-github-account)“ +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..87cc91370f --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: Apply for an educator or researcher discount +intro: 'Wenn Sie ein Lehrer oder Forscher sind, können Sie beantragen, {% data variables.product.prodname_team %} kostenlos für das Konto Ihrer Organisation zu erhalten.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### Informationen zu Lehrer- und Forscherrabatten + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Einen Lehrer- oder Forscherrabatt beantragen + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Ein Upgrade Deiner Organisation durchführen + +Nachdem Dein Antrag für einen Lehrer- oder Forscherrabatt genehmigt wurde, kannst Du die von Dir mit Deiner Lerngemeinschaft benutzte Organisation auf {% data variables.product.prodname_team %} hochstufen, was die kostenlose Nutzung von unbegrenzten Benutzern und privaten Repositorys erlaubt. Du kannst eine vorhandene Organisation hochstufen oder eine neue Organisation für das Hochstufen erstellen. + +#### Hochstufen einer vorhandenen Organisation + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Hochstufen einer neuen Organisation + +{% data reusables.education.upgrade-page %} +1. Klicke auf {% octicon "plus" aria-label="The plus symbol" %} **Create an organization** (Erstelle eine Organisation). ![Schaltfläche „Create an organization“ (Eine Organisation erstellen)](/assets/images/help/education/create-org-button.png) +3. Lies die Informationen, dann klicke auf **Create organization** (Organisation erstellen). ![Schaltfläche „Create organization“ (Organisation erstellen)](/assets/images/help/education/create-organization-button.png) +4. Klicke unter "Choose your plan" (Wähle Deinen Plan), auf **Choose {% data variables.product.prodname_free_team %}** (Wähle Produkt). +5. Folge den Anweisungen, um Deine Organisation zu erstellen. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Weiterführende Informationen + +- „[Warum wurde mein Antrag eines Lehrer- oder Forscherrabatts nicht genehmigt?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)“ +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %}-Videos](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..8294d8dbaf --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Erkunden +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Inhaltsverzeichnis + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..469ccdcb03 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub at your educational institution +intro: 'Maximieren Sie die Vorteile der Nutzung von {% data variables.product.prodname_dotcom %} in Ihrer Einrichtung für Ihre Studenten, Instrukteure und IT-Mitarbeiter mit {% data variables.product.prodname_education %} und unseren verschiedenen Schulungsprogrammen für Studenten und Instrukteure.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..369692a2aa --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub for your schoolwork +intro: 'Schüler und Studenten können {% data variables.product.prodname_dotcom %} verwenden, um an Schulprojekten zusammenzuarbeiten und erste praktische Erfahrung aufzubauen.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..3b0a35e885 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub in your classroom and research +intro: 'Lehrer oder Forscher können {% data variables.product.prodname_dotcom %} für die Zusammenarbeit im Klassenraum, in der Studenten- oder Forschungsgruppe usw. verwenden.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..232cb1f7f6 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +title: Warum wurde mein Antrag für das Studentenentwicklungspaket abgelehnt? +intro: 'Lies die generellen Gründe, weshalb Anträge für das {% data variables.product.prodname_student_pack %} nicht genehmigt werden, und Tipps, um die erneute Bewerbung erfolgreich zu gestalten.' +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tipp:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unklare Dokumente zur akademischen Zugehörigkeit + +Wenn anhand des von Dir hochgeladenen Bildes Dein aktueller akademischer Status nicht eindeutig identifiziert werden kann, fordern wir einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse mit einer nicht verifizierten Domäne verwenden + +Wenn Deine akademische E-Mail-Adresse eine nicht verifizierte Domäne aufweist, fordern wir einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse von einer Bildungseinrichtung mit lockeren E-Mail-Richtlinien verwenden + +Wenn Deine Bildungseinrichtung E-Mail-Adressen vor der bezahlten Studentenregistrierung ausstellt, fordern wir einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +Bei anderen Fragen oder Bedenken zur Domäne der Bildungseinrichtung solltest Du das IT-Personal Deiner Bildungseinrichtung bitten, uns zu kontaktieren. + +### Akademische E-Mail-Adresse wird bereits verwendet + +Wenn Deine akademische E-Mail-Adresse bereits verwendet wurde, um ein {% data variables.product.prodname_student_pack %} für ein anderes {% data variables.product.prodname_dotcom %}-Konto anzufordern, kannst Du die akademische E-Mail-Adresse bis zum Ablauf des entsprechenden Rabatts nicht erneut verwenden, um Dich erfolgreich für ein anderes {% data variables.product.prodname_student_pack %} zu bewerben. + +{% note %} + +**Hinweis:** Es verstößt gegen die {% data variables.product.prodname_dotcom %}-[Nutzungsbedingungen](/articles/github-terms-of-service/#3-account-requirements), mehr als ein persönliches Konto zu verwenden. + +{% endnote %} + +Falls Du über mehrere persönliche Konten verfügst, musst Du Deine Konten zusammenführen. Um den Rabatt zu erhalten, solltest Du das Konto beibehalten, für das der Rabatt gewährt wurde. Du kannst das beibehaltene Konto umbenennen und Deinen Beitragsverlauf beibehalten. Füge dem beibehaltenen Konto dazu alle Deine E-Mail-Adressen hinzu. + +Weitere Informationen findest Du unter: +- „[Mehrere Benutzerkonten zusammenführen](/articles/merging-multiple-user-accounts)“ +- „[Deinen {% data variables.product.prodname_dotcom %}-Benutzernamen ändern](/articles/changing-your-github-username)“ +- „[E-Mail-Adresse zu Deinem {% data variables.product.prodname_dotcom %}-Konto hinzufügen](/articles/adding-an-email-address-to-your-github-account)“ + +### Nicht berechtigter Studentenstatus + +Du bist nicht für ein {% data variables.product.prodname_student_pack %} berechtigt, falls: +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- Du weniger als 13 Jahre alt bist. + +Dein Kursleiter kann weiterhin einen {% data variables.product.prodname_education %}-Rabatt für die Nutzung in der Ausbildung beantragen. Wenn Du ein Student an einer Codierschule oder in einem Schülercamp bist, hast Du Anspruch auf ein {% data variables.product.prodname_student_pack %}, wenn Deine Bildungseinrichtung dem [{% data variables.product.prodname_dotcom %}-Campus-Programm](https://education.github.com/schools) beitritt. + +### Weiterführende Informationen + +- „[Ein Studentenentwicklungspaket beantragen](/articles/applying-for-a-student-developer-pack)“ +- "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..30b353acbd --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: Warum wurde mein Antrag auf einen Lehrer- oder Forscherrabatt nicht genehmigt? +intro: Lies die generellen Gründe durch, weshalb Bewerbungen für einen Lehrer- oder Forscherrabatt nicht genehmigt werden, und die Tipps, um die erneute Bewerbung erfolgreich zu gestalten. +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tipp:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unklare Zugehörigkeitsnachweisdokumente + +Falls das von Dir hochgeladene Bild Deine aktuelle Beschäftigung an einer Schule oder Universität nicht zweifelsfrei belegt, musst Du Dich erneut bewerben und ein anderes Bild Deiner Fakultäts-ID oder einen Beschäftigungsnachweis mit eindeutigen Informationen hochladen. + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse mit einer nicht verifizierten Domäne verwenden + +Wenn Deine akademische E-Mail-Adresse eine nicht verifizierte Domäne aufweist, fordern wir allenfalls einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse von einer Bildungseinrichtung mit lockeren E-Mail-Richtlinien verwenden + +Falls Alumni und pensionierte Lehrkörper Deiner Bildungseinrichtung lebenslang auf die von Deiner Bildungseinrichtung ausgestellten E-Mail-Adressen zugreifen können, fordern wir allenfalls einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +Bei anderen Fragen oder Bedenken zur Domäne der Bildungseinrichtung solltest Du das IT-Personal Deiner Bildungseinrichtung bitten, uns zu kontaktieren. + +### Nichtstudent beantragt das Studentenentwicklungspaket + +Lehrer und Forscher sind nicht berechtigt für die Partnerangebote, die im Lieferumfang von [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) enthalten sind. Stelle bei der erneuten Bewerbung sicher, dass Du **Faculty** (Universitätsmitglied) auswählst, um Deinen akademischen Status zu beschreiben. + +### Weiterführende Informationen + +- "[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)" diff --git a/translations/de-DE/content/education/guides.md b/translations/de-DE/content/education/guides.md index 45263ae4da..25190558b4 100644 --- a/translations/de-DE/content/education/guides.md +++ b/translations/de-DE/content/education/guides.md @@ -12,8 +12,8 @@ Teachers, students, and researchers can use tools from {% data variables.product - [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) -- [Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) +- [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) ### Run a software development course with {% data variables.product.company_short %} @@ -32,7 +32,7 @@ Administer a classroom, assign and review work from your students, and teach the Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. - [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/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [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) @@ -41,5 +41,5 @@ Incorporate {% data variables.product.prodname_dotcom %} into your education, an 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) -- [Informationen zu Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) -- [Informationen zu Campus Advisors](/education/teach-and-learn-with-github-education/about-campus-advisors) +- [Informationen zu Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) +- [Informationen zu Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) diff --git a/translations/de-DE/content/education/index.md b/translations/de-DE/content/education/index.md index c3827df288..782c20b772 100644 --- a/translations/de-DE/content/education/index.md +++ b/translations/de-DE/content/education/index.md @@ -6,16 +6,16 @@ introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom @@ -41,5 +41,5 @@ versions: free-pro-team: '*' --- - + diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 5454736d9c..cc9c99d30c 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ For more information about teaching with {% data variables.product.prodname_clas ### Weiterführende Informationen -- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" +- "[Explore the benefits of teaching and learning with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 5bc887c1c7..100fe09c4c 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -140,6 +140,6 @@ You can see the teams that are working on or have submitted an assignment in the ### Weiterführende Informationen -- "[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)" +- "[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/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index 76cef7d653..07bf385d07 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,8 +11,6 @@ You can use a template repository on {% data variables.product.product_name %} a To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." - ### Weiterführende Informationen - "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index b44f0c64fa..86b12722ba 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -120,5 +120,5 @@ You can see whether a student has joined the classroom and accepted or submitted ### Weiterführende Informationen -- "[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)" +- "[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/de-DE/content/education/manage-coursework-with-github-classroom/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md index 72fbf280b2..4a63ac0379 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 6e051e9d2d..e5dbcf02c1 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -4,5 +4,8 @@ intro: Learn how to set up your classroom and assignments. mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index d3413b7003..4bdfdf5b9a 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -33,8 +33,8 @@ Du kannst E-Mail-Benachrichtigungen filtern, die Du für Pushes an ein Repositor {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 5. Gib bis zu zwei E-Mail-Adressen (getrennt durch Leerzeichen) ein, an die Du Benachrichtigungen senden möchtest. Wenn Du E-Mails an mehr als zwei Konten senden möchtest, legst Du eine der E-Mail-Adressen als Gruppen-E-Mail-Adresse fest. ![Textfeld für die E-Mail-Adresse](/assets/images/help/settings/email_services_addresses.png) -6. Wenn Du Deinen eigenen Server verwendest, kannst Du die Integrität von E-Mails über das Token **Secret** (Geheim) überprüfen. Dieses Token wird mit der E-Mail als `Approved`-Header (Genehmigt) gesendet. Wenn der `Approved`-Header (Genehmigt) mit dem von Dir gesendeten Token übereinstimmt, kannst Du darauf vertrauen, dass die E-Mail von {% data variables.product.product_name %} stammt. ![Textfeld für das E-Mail-Geheimnis](/assets/images/help/settings/email_services_token.png) -7. Klicke auf **Save settings** (Einstellungen speichern). ![Schaltfläche „Save settings“ (Einstellungen speichern)](/assets/images/help/settings/save_notification_settings.png) +1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}. ![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png) +7. Click **Setup notifications**. ![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png) ### Weiterführende Informationen {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} diff --git a/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md b/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md index 4b70f591e8..9eb1a20f92 100644 --- a/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,7 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." diff --git a/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md b/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md index 0748625b6b..8dcd7efdd5 100644 --- a/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md @@ -4,6 +4,7 @@ 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: free-pro-team: '*' + enterprise-server: '>=3.1' --- ### About renaming branches @@ -19,3 +20,15 @@ If you rename a branch, {% data variables.product.prodname_dotcom %} will automa 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) + +### Updating a local clone after a branch name changes + +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. + +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 +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index bd983209f9..99dbdb8918 100644 --- a/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Informationen zur Authentifizierung mit SAML Single-Sign-On -intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' +intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on @@ -9,6 +9,8 @@ versions: github-ae: '*' --- +### About authentication with SAML SSO + {% if currentVersion == "github-ae@latest" %} SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. @@ -31,13 +33,17 @@ Wenn Du Dich kürzlich mit der SAML IdP Deiner Organisation in Deinem Browser au {% data reusables.saml.you-must-periodically-authenticate %} -Um die API oder Git in der Befehlszeile für den Zugriff auf geschützte Inhalte in einer Organisation mit SAML SSO zu verwenden, musst Du ein autorisiertes persönliches Zugriffstoken über HTTPS oder einen autorisierten SSH-Schlüssel verwenden. {% data variables.product.prodname_oauth_app %}-Zugriffstoken sind standardmäßig autorisiert. +Um die API oder Git in der Befehlszeile für den Zugriff auf geschützte Inhalte in einer Organisation mit SAML SSO zu verwenden, musst Du ein autorisiertes persönliches Zugriffstoken über HTTPS oder einen autorisierten SSH-Schlüssel verwenden. Wenn Du kein persönliches Zugriffstoken oder keinen SSH-Schlüssel hast, kannst Du ein persönliches Zugriffstoken für die Befehlszeile erstellen oder einen neuen SSH-Schlüssel generieren. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -Um ein neues oder vorhandenes persönliches Zugriffstoken oder einen SSH-Schlüssel in einer Organisation zu verwenden, die SAML SSO erzwingt, musst Du das Token autorisieren oder den SSH-Schlüssel für die Verwendung bei einer SAML SSO-Organisation autorisieren. Weitere Informationen findest Du unter „[Autorisieren eines persönlichen Zugriffstokens für die Benutzung mit SAML Single Sign-On](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" oder „[Autorisieren eines SSH-Schlüssels für die Benutzung mit SAML Single Sign-On](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. Weitere Informationen findest Du unter „[Autorisieren eines persönlichen Zugriffstokens für die Benutzung mit SAML Single Sign-On](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" oder „[Autorisieren eines SSH-Schlüssels für die Benutzung mit SAML Single Sign-On](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -Du musst eine aktive SAML-Sitzung haben, wenn Du eine {% data variables.product.prodname_oauth_app %} autorisierst. +### About {% data variables.product.prodname_oauth_apps %} and SAML SSO + +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO. + +After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). {% endif %} diff --git a/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index e9ed19699e..a5d6868ae2 100644 --- a/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ In diesem Artikel erfährst Du, wie Du Commits mit vertraulichen Daten für alle #### Benutze BFG -[BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) ist ein von der Open-Source-Community entwickeltes und verwaltetes Tool. Für das Löschen unerwünschter Daten ist es eine schnellere und einfachere Alternative zum Befehl `git filter-branch`. Um beispielsweise Deine Datei mit vertraulichen Daten zu entfernen und Deinen letzten Commit unberührt zu lassen, führe folgenden Befehl aus: +[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) ist ein von der Open-Source-Community entwickeltes und verwaltetes Tool. Für das Löschen unerwünschter Daten ist es eine schnellere und einfachere Alternative zum Befehl `git filter-branch`. Um beispielsweise Deine Datei mit vertraulichen Daten zu entfernen und Deinen letzten Commit unberührt zu lassen, führe folgenden Befehl aus: ```shell $ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA @@ -46,7 +46,7 @@ After the sensitive data is removed, you must force push your changes to {% data $ git push --force ``` -Ausführliche Informationen zum Download und zur Verwendung von [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) findest Du in seiner Dokumentation. +Ausführliche Informationen zum Download und zur Verwendung von [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) findest Du in seiner Dokumentation. #### Mit „filter-branch“ diff --git a/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index 1095a94e72..e6028004e5 100644 --- a/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ Wenn Du einen Benutzer blockierst, kannst Du auswählen, ob er dauerhaft oder f {% tip %} -**Tipp:** Wenn Du einen Benutzer wegen einer hitzigen Unterhaltung blockierst, empfiehlt es sich möglicherweise, [die Unterhaltung zu schließen](/articles/locking-conversations), sodass nur Mitarbeiter kommentieren können. +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. (siehe „[Unterhaltungen sperren](/github/building-a-strong-community/locking-conversations)“) {% endtip %} Wenn Du einen Benutzer für Deine Organisation blockieren: - beobachtet der Benutzer die Repositorys Deiner Organisation nicht mehr - werden die Sternmarkierungen und Issue-Zuweisungen des Benutzers von Deinen Repositorys entfernt -- The user's forks of your organization's repositories are deleted - The user's votes on discussions or comments in your organization's repositories are deleted - wird der Benutzer als Mitarbeiter aus den Repositorys Deiner Organisation entfernt - The user's contributions to your organization's repositories are no longer counted as contributions for them diff --git a/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 2fce8debe1..9160c8698f 100644 --- a/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/de-DE/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### Informationen zum Blockieren von Benutzern -Du kannst einen Benutzer in Deinen Kontoeinstellungen oder über das Profil des Benutzers blockieren. {% data variables.product.prodname_dotcom %} wird dem Benutzer nicht mitteilen, wenn Du ihn blockierst. Wenn Du vermeiden möchtest, am selben Projekt mitzuwirken wie ein von Dir blockierter Benutzer, kannst Du bei Repositorys, zu denen der blockierte Benutzer in der Vergangenheit beigetragen hat, [Warnungen anzeigen lassen](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings). You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content. +Du kannst einen Benutzer in Deinen Kontoeinstellungen oder über das Profil des Benutzers blockieren. {% data variables.product.prodname_dotcom %} wird dem Benutzer nicht mitteilen, wenn Du ihn blockierst. If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see "[Blocking a user in your account settings](#blocking-a-user-in-your-account-settings)." You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content. {% tip %} -**Tipp:** Wenn Du einen Benutzer wegen einer hitzigen Unterhaltung blockierst, empfiehlt es sich möglicherweise, [die Unterhaltung zu schließen](/articles/locking-conversations), sodass nur Mitarbeiter kommentieren können. +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. (siehe „[Unterhaltungen sperren](/github/building-a-strong-community/locking-conversations)“) {% endtip %} @@ -22,8 +22,6 @@ Wenn Du einen Benutzer blockierst: - The user stops watching and unpins your repositories - The user is not able to join any organizations you are an owner of - werden die Sternmarkierungen und Issue-Zuweisungen des Benutzers von Deinen Repositorys entfernt -- The user's forks of your repositories are deleted -- You delete any forks of the user's repositories - The user's votes on discussions or comments in your repositories are deleted - Wird er als Mitarbeiter von Deinen Repositorys entfernt - The user's contributions to your repositories are no longer counted as contributions for them diff --git a/translations/de-DE/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/de-DE/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 8123d58187..92b4defe04 100644 --- a/translations/de-DE/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/de-DE/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ Du kannst YAML-Titelei zu jeder Issuevorlage hinzufügen, um den Issuetitel vora Hier ist ein Beispiel für eine YAML-Titelei. -``` +```yaml --- name: Issue verfolgen about: Benutzer diese Vorlage zum verfolgen neuer Funktionen. diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index 86bb4e44f0..9df3d01b6c 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ Ein Beispiel: Du und eine andere Person haben die gleichen Zeilen der Datei _sty 4. Öffne Deinen bevorzugten Texteditor, beispielsweise [Atom](https://atom.io/), und navigiere zu der Datei mit den Mergekonflikten. 5. Um in der Datei an den Anfang des Mergekonflikts zu gelangen, durchsuche die Datei nach dem Konflikthinweis `<<<<<<<`. Wenn Du die Datei in Deinem Texteditor öffnest, siehst Du die Änderungen im Head- oder Basis-Branch nach der Zeile `<<<<<<< HEAD`. Danach siehst Du `=======`, was Deine Änderungen von den Änderungen im anderen Branch abtrennt. Danach folgt `>>>>>>> BRANCH-NAME`. In diesem Beispiel gab eine Person im Basis- oder Head-Branch „open an issue“ ein, eine andere Person im Vergleichs-Branch (`branch-a`) hingegen „ask your question in IRC“. - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In diesem Beispiel werden beide Änderungen in den Merge übernommen: ```shell diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 409373a00a..1018eaf5a8 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ Pre-Receive-Hooks führen Tests für an ein Repository übertragenen Code durch, Falls Dein Push nicht akzeptiert wird, wird eine Fehlermeldung zum fehlgeschlagenen Pre-Receive-Hook angezeigt. -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md index dd51c26ffa..bd4c9569c9 100644 --- a/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,7 +19,7 @@ You can discover, browse, and install apps and actions created by others on {% d {% data reusables.actions.actions-not-verified %} -Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Ein Tool auf {% data variables.product.prodname_marketplace %} erstellen und veröffentlichen diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index fbbf119fb7..d2288c0735 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ To integrate {% data variables.product.prodname_code_scanning %} into your CI sy In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -39,7 +39,7 @@ The {% data variables.product.prodname_codeql_runner %} automatically detects an To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are `cpp`, `csharp`, `go`, `java`, `javascript`, and `python`. -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -55,7 +55,7 @@ If you also are using a configuration file for custom settings, and you are also In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. -``` +```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 ``` @@ -68,7 +68,7 @@ The configuration file is a YAML file. It uses syntax similar to the workflow sy Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. -``` +```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml ``` @@ -84,7 +84,7 @@ For many common build systems, the {% data variables.product.prodname_codeql_run The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. -``` +```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 8deaec4e36..81c7f84190 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ You can set up {% data variables.product.prodname_code_scanning %} to check the 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### About alerts details 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 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. diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 43b0e6fa7d..2d92e06f15 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -93,6 +93,8 @@ You can configure where the {% data variables.product.prodname_codeql_runner %} To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Basic example This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 2a8acbc0b4..f4c782d9b7 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -40,6 +40,8 @@ If you upload a SARIF file without fingerprint data using the `/code-scanning/sa If your SARIF file doesn't include `partialFingerprints`, the `partialFingerprints` field will be calculated when you upload the SARIF file using {% data variables.product.prodname_actions %}. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### Supported SARIF output file properties If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}. @@ -82,6 +84,8 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr #### `result` object +{% data reusables.code-scanning.upload-sarif-alert-limit %} + | Name | Beschreibung | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | @@ -89,7 +93,7 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | | `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | | `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | -| `locations[]` | **Required.** The set of locations where the result was detected. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | | `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | | `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | | `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index dcbfce7282..bd63f29378 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -39,6 +39,8 @@ The `upload-sarif` action can be configured to run when the `push` and `schedule If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Example workflow for SARIF files generated outside of a repository You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository. diff --git a/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md index 8508638714..8e3f5b0994 100644 --- a/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/de-DE/content/github/getting-started-with-github/about-github-advanced-security.md @@ -10,7 +10,7 @@ versions: {% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." For information about permission requirements for actions related to security features, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." ### About {% data variables.product.prodname_advanced_security %} features diff --git a/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md index 12f894aba4..5a7e7b5f51 100644 --- a/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ Mache Dich mit Git vertraut: Besuche die [offizielle Git-Projekt-Website](https: {% endif %} -Lernen Sie {% data variables.product.product_name %} mithilfe unserer [Bootcamp](/categories/bootcamp/)-Artikel besser kennen. Eine Prozesseinführung findest Du unter [{% data variables.product.prodname_dotcom %}-Ablauf](https://guides.github.com/introduction/flow). In unseren [Übersichtsleitfäden](https://guides.github.com) stellen wir Dir Schritt für Schritt die grundlegenden Konzepte vor. +Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. Eine Prozesseinführung findest Du unter [{% data variables.product.prodname_dotcom %}-Ablauf](https://guides.github.com/introduction/flow). In unseren [Übersichtsleitfäden](https://guides.github.com) stellen wir Dir Schritt für Schritt die grundlegenden Konzepte vor. {% data reusables.support.ask-and-answer-forum %} #### Branches, Forks und Pull Requests -Lerne mit einem interaktiven Tool alles über [Branches bei Git](http://learngitbranching.js.org/). Informieren Sie sich über [Forks](/articles/about-forks), [Pull Requests](/articles/using-pull-requests) und [die Verwendung von Pull Requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) auf {% data variables.product.prodname_dotcom %}. - -Außerdem stehen Ihnen Kurzanleitungen zur [Befehlszeile](https://hub.github.com) sowie [Checklisten, Merkzettel etc.](https://services.github.com/on-demand/resources) zu {% data variables.product.prodname_dotcom %} zur Verfügung. +Lerne mit einem interaktiven Tool alles über [Branches bei Git](http://learngitbranching.js.org/). Informieren Sie sich über [Forks](/articles/about-forks), [Pull Requests](/articles/using-pull-requests) und [die Verwendung von Pull Requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) auf {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). #### Reinschauen @@ -41,9 +39,9 @@ Auf unserem {% data variables.product.prodname_dotcom %} [YouTube-Kanal „GitHu ### Schulungen -#### Kostenlose Kurse +#### Free courses -{% data variables.product.product_name %} bietet eine Reihe von interaktiven [On-Demand-Schulungskursen](https://services.github.com/on-demand/), darunter {% data variables.product.prodname_dotcom %} 101: [Introduction](https://services.github.com/on-demand/intro-to-github/) (Einführung), {% data variables.product.prodname_dotcom %} 102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop) (GitHub Desktop) und {% data variables.product.prodname_dotcom %} 103: [Command Line](https://services.github.com/on-demand/github-cli) (Befehlszeile). +{% 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 %}. #### Webbasierte Lernprogramme von {% data variables.product.prodname_dotcom %} diff --git a/translations/de-DE/content/github/getting-started-with-github/git-cheatsheet.md b/translations/de-DE/content/github/getting-started-with-github/git-cheatsheet.md index 43934b7ce4..c9f8bbab43 100644 --- a/translations/de-DE/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/de-DE/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -Alle verfügbaren Git-Befehle auf einmal zu lernen ist eine Herausforderung. Halte als Referenz einen unserer [Git-Merkzettel](https://services.github.com/on-demand/resources/cheatsheets/) bereit. Der Merkzettel zur Git-Verwendung liegt in mehreren Sprachen vor. Weitere Informationen findest Du auf der [Ressourcen-Seite auf der GitHub Dienste-Website](https://services.github.com/on-demand/resources/). +Alle verfügbaren Git-Befehle auf einmal zu lernen ist eine Herausforderung. Our cheat sheets provide a quick reference for the commands you'll use most often: see "[Git Cheat Sheets](https://training.github.com/)." The "Using Git" cheat sheet is available in several languages. Darüber hinaus findest Du auf unserer Seite [Git- und GitHub-Lerninhalte](/articles/git-and-github-learning-resources/) zahlreiche Links zu Leitfäden, Videos und anderen Ressourcen. diff --git a/translations/de-DE/content/github/getting-started-with-github/githubs-products.md b/translations/de-DE/content/github/getting-started-with-github/githubs-products.md index 189af98ef4..579124dbb4 100644 --- a/translations/de-DE/content/github/getting-started-with-github/githubs-products.md +++ b/translations/de-DE/content/github/getting-started-with-github/githubs-products.md @@ -85,6 +85,7 @@ Zusätzlich zu den mit {% data variables.product.prodname_team %} verfügbaren F - {% data variables.contact.enterprise_support %}. Weitere Informationen findest Du unter „{% data variables.product.prodname_ghe_cloud %}-Support“ und „{% data variables.product.prodname_ghe_cloud %}-Nachtrag.“ - 50.000 {% data variables.product.prodname_actions %}-Minuten - 50 GB {% data variables.product.prodname_registry %}-Speicher +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime - Die Option, die Richtlinien und Abrechnungen für mehrere {% data variables.product.prodname_dotcom_the_website %}-Organisationen mit Enterprise-Konto zentral zu verwalten. Weitere Informationen findest Du unter "About enterprise accounts" (Über Enterprise-Konten). diff --git a/translations/de-DE/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/de-DE/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 470d627842..181b4c19e0 100644 --- a/translations/de-DE/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/de-DE/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,10 +45,10 @@ versions: 7. Klicken Sie oben auf der Seite zur Schnelleinrichtung Ihres {% data variables.product.product_name %}-Repositorys auf {% octicon "clippy" aria-label="The copy to clipboard icon" %}, um die URL des Remote-Repositorys zu kopieren. ![Feld zum Kopieren der Remote-Repository-URL](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. [Füge in Terminal die URL für das Remote-Repository hinzu](/articles/adding-a-remote), an das Dein lokales Repository per Push übergeben werden soll. ```shell - $ git remote add origin remote repository URL - # setzt die neue Remote-Repository URL + $ git remote add origin <REMOTE_URL> + # Sets the new remote $ git remote -v - # Verifiziert die neue Remote-Repository URL + # Verifies the new remote URL ``` 9. [Übergib die Änderungen](/articles/pushing-commits-to-a-remote-repository/) in Deinem lokalen Repository per Push an {% data variables.product.product_location %}. ```shell @@ -83,10 +83,10 @@ versions: 7. Klicken Sie oben auf der Seite zur Schnelleinrichtung Ihres {% data variables.product.product_name %}-Repositorys auf {% octicon "clippy" aria-label="The copy to clipboard icon" %}, um die URL des Remote-Repositorys zu kopieren. ![Feld zum Kopieren der Remote-Repository-URL](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. Gib in der Eingabeaufforderung [die URL für das Remote-Repository](/articles/adding-a-remote) ein, an das Dein lokales Repository per Push übergeben werden soll. ```shell - $ git remote add origin remote repository URL - # setzt die neue Remote-Repository URL + $ git remote add origin <REMOTE_URL> + # Sets the new remote $ git remote -v - # Verifiziert die neue Remote-Repository URL + # Verifies the new remote URL ``` 9. [Übergib die Änderungen](/articles/pushing-commits-to-a-remote-repository/) in Deinem lokalen Repository per Push an {% data variables.product.product_location %}. ```shell @@ -121,10 +121,10 @@ versions: 7. Klicken Sie oben auf der Seite zur Schnelleinrichtung Ihres {% data variables.product.product_name %}-Repositorys auf {% octicon "clippy" aria-label="The copy to clipboard icon" %}, um die URL des Remote-Repositorys zu kopieren. ![Feld zum Kopieren der Remote-Repository-URL](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. [Füge in Terminal die URL für das Remote-Repository hinzu](/articles/adding-a-remote), an das Dein lokales Repository per Push übergeben werden soll. ```shell - $ git remote add origin remote repository URL - # setzt die neue Remote-Repository URL + $ git remote add origin <REMOTE_URL> + # Sets the new remote $ git remote -v - # Verifiziert die neue Remote-Repository URL + # Verifies the new remote URL ``` 9. [Übergib die Änderungen](/articles/pushing-commits-to-a-remote-repository/) in Deinem lokalen Repository per Push an {% data variables.product.product_location %}. ```shell diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md index bede1c05f5..37c11ac96d 100644 --- a/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### Über Code-Navigation auf {% data variables.product.prodname_dotcom %} -Code-Navigationsfunktionen verwenden die [Semantik](https://github.com/github/semantic) der Open-Source-Bibliothek. Die folgenden Sprachen werden unterstützt: +Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). Die folgenden Sprachen werden unterstützt: - C# - CodeQL - Go diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 81d619cc6e..27416ac984 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -47,6 +47,8 @@ For a list of the ecosystems that {% data variables.product.product_name %} can 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." + {% 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 %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/de-DE/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index 006093078e..0006efe52b 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ Wenn Du einen Sicherheitshinweis veröffentlichst, informierst Du Deine Communit Bevor Du einen Sicherheitshinweis veröffentlichst, kannst Du privat mit anderen zusammenarbeiten, um die Sicherheitslücke in einem temporären privaten Fork zu beheben. Weitere Informationen findest Du unter „[In einem temporären privaten Fork zusammenarbeiten, um eine Sicherheitslücke zu beheben](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability).“ +{% warning %} + +**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to. + +We recommend you take the following steps in these different situations: + +- If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready. +- If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication. +- If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue. + +{% endwarning %} + When you publish a draft advisory from a public repository, everyone is able to see: - The current version of the advisory data. diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 858887a8c5..2456952b0d 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -133,7 +133,8 @@ E-Mail-Benachrichtigungen von {% data variables.product.product_name %} enthalte | `To`-Feld | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | `Cc`-Adresse | {% data variables.product.product_name %} fügt Sie zu `Cc` hinzu, wenn Sie eine Unterhaltung abonniert haben. Die zweite E-Mail-Adresse in `Cc` entspricht dem Benachrichtigungsgrund. Das Suffix für diese Benachrichtigungsgründe lautet {% data variables.notifications.cc_address %}. Zu den möglichen Benachrichtigungsgründen gehören folgende:
  • `assign`: Dir wurde ein Issue oder Pull Request zugewiesen.
  • `author`: Du hast einen Issue oder Pull Request erstellt.
  • `comment`: Du hast einen Issue oder Pull Request kommentiert.
  • `manual`: Ein Issue oder Pull Request, den Du manuell abonniert hast, wurde aktualisiert.
  • `mention`: Du wurdest in einem Issue oder Pull Request erwähnt.
  • `push`: Jemand hat einen Commit für einen Pull Request erstellt, den Du abonniert hast.
  • `review_requested`: Du oder ein Team, dem Du angehörst, wurdest/wurde gebeten, einen Review für einen Pull Request durchzuführen.
    • {% if currentVersion != "github-ae@latest" %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} hat eine Schwachstelle in einem Repository erkannt, für das Du Sicherheitswarnungen erhältst.
    • {% endif %}
  • `state_change`: Ein Issue oder Pull Request, den Du abonniert hast, wurde entweder geschlossen oder geöffnet.
  • `subscribed`: Es gab eine Aktualisierung in einem Repository, das Du beobachtest.
  • `team_mention`: Ein Team, dem Du angehörst, wurde in einem Issue oder Pull Request erwähnt.
  • `your_activity`: Du hast einen Issue oder Pull Request geöffnet, kommentiert oder geschlossen.
| | `mailing list`-Feld | In diesem Feld werden der Name des Repositorys und sein Inhaber identifiziert. Das Format dieser Adresse lautet immer `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `X-GitHub-Severity`-Feld | {% data reusables.repositories.security-alerts-x-github-severity %} Die möglichen Schweregrade sind:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | |{% endif %} +| `X-GitHub-Severity`-Feld | {% data reusables.repositories.security-alerts-x-github-severity %} Die möglichen Schweregrade sind:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | +{% endif %} ### Wähle Deine Benachrichtigungseinstellungen diff --git a/translations/de-DE/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/de-DE/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 32fe48320e..7264d95af3 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: Für die Übertragung eines offenen Issues in ein anderes Repository benötigst Du Schreibberechtigung sowohl für das Repository, aus dem der Issue stammt, wie auch für das Repository, in das der Issue übertragen wird. Weitere Informationen finden Sie unter„[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“. -You can only transfer issues between repositories owned by the same user or organization account.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} +Du kannst Issues nur zwischen Repositorys übertragen, die demselben Benutzer- oder Organisationskonto angehören. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} Wenn Du einen Issue überträgst, bleiben seine Kommentare und Bearbeiter erhalten. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. Weitere Informationen findest Du unter „[Informationen zu Projektboards](/articles/about-project-boards).“ diff --git a/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index 0928cb3591..1a505b1d27 100644 --- a/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,7 +25,8 @@ E-Mail-Benachrichtigungen von {% data variables.product.product_name %} enthalte | `To`-Feld | Dieses Feld ist direkt mit dem Thread verknüpft. Wenn Du auf die E-Mail antwortest, fügst Du der Unterhaltung einen neuen Kommentar hinzu. | | `Cc`-Adresse | {% data variables.product.product_name %} fügt Sie zu `Cc` hinzu, wenn Sie eine Unterhaltung abonniert haben. Die zweite E-Mail-Adresse in `Cc` entspricht dem Benachrichtigungsgrund. Das Suffix für diese Benachrichtigungsgründe lautet {% data variables.notifications.cc_address %}. Zu den möglichen Benachrichtigungsgründen gehören folgende:
  • `assign`: Dir wurde ein Issue oder Pull Request zugewiesen.
  • `author`: Du hast einen Issue oder Pull Request erstellt.
  • `comment`: Du hast einen Issue oder Pull Request kommentiert.
  • `manual`: Ein Issue oder Pull Request, den Du manuell abonniert hast, wurde aktualisiert.
  • `mention`: Du wurdest in einem Issue oder Pull Request erwähnt.
  • `push`: Jemand hat einen Commit für einen Pull Request erstellt, den Du abonniert hast.
  • `review_requested`: Du oder ein Team, dem Du angehörst, wurdest/wurde gebeten, einen Review für einen Pull Request durchzuführen.
  • `security_alert`: {% data variables.product.prodname_dotcom %} hat eine Schwachstelle in einem Repository erkannt, für das Du Sicherheitswarnungen erhältst.
  • `state_change`: Ein Issue oder Pull Request, den Du abonniert hast, wurde entweder geschlossen oder geöffnet.
  • `subscribed`: Es gab eine Aktualisierung in einem Repository, das Du beobachtest.
  • `team_mention`: Ein Team, dem Du angehörst, wurde in einem Issue oder Pull Request erwähnt.
  • `your_activity`: Du hast einen Issue oder Pull Request geöffnet, kommentiert oder geschlossen.
| | `mailing list`-Feld | In diesem Feld werden der Name des Repositorys und sein Inhaber identifiziert. Das Format dieser Adresse lautet immer `..{% data variables.command_line.backticks %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| `X-GitHub-Severity`-Feld | {% data reusables.repositories.security-alerts-x-github-severity %} Die möglichen Schweregrade sind:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | |{% endif %} +| `X-GitHub-Severity`-Feld | {% data reusables.repositories.security-alerts-x-github-severity %} Die möglichen Schweregrade sind:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | +{% endif %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 20b559c982..aab6d7b348 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ Du kannst Deine Ergebnisse auf Issues einschränken, die mit einem Pull-Request | `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) findet offene Issues im `desktop/desktop`-Repository, die mit einer schließenden Referenz zu einem Pull Request verknüpft sind. | | `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) findet geschlossene Pull Requests im `desktop/desktop`-Repository, die zu einem Issue verknüpft waren, den der Pull Request möglicherweise geschlossen hat. | | `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) findet offene Issues im `desktop/desktop`-Repository, die nicht mit einer schließenden Referenz zu einem Pull Request verknüpft sind. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) findet offene Pull Requests im `desktop/desktop`-Repository, die nicht zu einem Issue verknüpft sind, die der Pull Request möglicherweise schließen kann. |{% endif %} +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) findet offene Pull Requests im `desktop/desktop`-Repository, die nicht zu einem Issue verknüpft sind, die der Pull Request möglicherweise schließen kann. +{% endif %} ### Suche nach Kennzeichnung diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md index 6130f88b2c..0e29ac2828 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} @@ -121,7 +121,7 @@ versions: {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} {% link_in_list /connecting-your-identity-provider-to-your-organization %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-using-okta %} + {% link_in_list /connecting-your-identity-provider-to-your-organization %} {% link_in_list /enabling-and-testing-saml-single-sign-on-for-your-organization %} {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..975641a8fe --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses +{% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/unpublishing-a-github-pages-site)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Klicke auf **Save** (Speichern). + +### Weiterführende Informationen + +- „[Informationen zum {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)“ diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index ee0343d47e..3dde9c5aa8 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late {% if currentVersion == "free-pro-team@latest" %} -| Aktion in der Organisation | Inhaber | Mitglieder | Abrechnungsmanager | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:----------:|:--------------------------------------------------:| -| Repositorys erstellen (siehe „[Repository-Erstellung in Deiner Organisation einschränken](/articles/restricting-repository-creation-in-your-organization)“) | **X** | **X** | | -| Abrechnungsinformationen anzeigen und bearbeiten | **X** | | **X** | -| Personen zum Beitritt zur Organisation einladen | **X** | | | -| Einladungen zum Beitritt zur Organisation bearbeiten und zurückziehen | **X** | | | -| Mitglied aus der Organisation entfernen | **X** | | | -| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | | -| Benutzer zu **allen Teams** hinzufügen oder wieder entfernen | **X** | | | -| Organisationsmitglieder zu *Team-Betreuern* ernennen | **X** | | | -| Code-Review-Zuweisungen konfigurieren (Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | | | -| Geplante Erinnerungen setzen (Weitere Informationen findest Du unter „[Geplante Erinnerungen für Pull-Requests verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | -| Mitarbeiter zu **allen Repositorys** hinzufügen | **X** | | | -| Auf das Auditprotokoll der Organisation zugreifen | **X** | | | -| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | | -| Die Domänen der Organisation überprüfen (siehe „[Domänen Deiner Organisation überprüfen](/articles/verifying-your-organization-s-domain)“) | **X** | | | -| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | -| **Alle Teams** löschen | **X** | | | -| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | | -| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | | -| [Teams in der Hierarchie einer Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Projektboards erstellen (siehe „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“) | **X** | **X** | | -| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | | -| Ein sichtbares Team @erwähnen | **X** | **X** | | -| Kann *Team-Beteuern* werden | **X** | **X** | | -| Einblicke für die Organisation anzeigen (siehe „[Einblicke für Ihre Organisation anzeigen ](/articles/viewing-insights-for-your-organization)“) | **X** | **X** | | -| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | **X** | | -| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | | | -| Teamdiskussionen in **allen Teams** bearbeiten und löschen (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments)“) | **X** | | | -| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | | -| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} -| Die Anzeige von Einblicken zu den Abhängigkeiten einer Organisation verwalten (siehe „[Die Sichtbarkeit der Einblicke zu den Abhängigkeiten Ihrer Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“) | **X** | | |{% endif %} -| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“) | **X** | | | -| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | -| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | -| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | -| [SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on) aktivieren und erzwingen | **X** | | | -| [Den SAML-Zugriff eines Benutzers auf Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | -| Die SSH-Zertifizierungsstellen einer Organisation verwalten (siehe „[SSH-Zertifizierungsstellen Ihrer Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities)“) | **X** | | | -| Repositorys übertragen | **X** | | | -| {% data variables.product.prodname_marketplace %}-Apps erwerben, installieren, kündigen und ihre Abrechnung verwalten | **X** | | | -| Apps auf {% data variables.product.prodname_marketplace %} aufführen | **X** | | |{% if currentVersion != "github-ae@latest" %} -| 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** | | | -| 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** | | |{% endif %} -| [Die Forking-Richtlinie verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Aktivitäten in öffentlichen Repositorys in einer Organisation einschränken](/articles/limiting-interactions-in-your-organization) | **X** | | | -| Lesen von (pull), Schreiben zu (push) und Kopieren von (clone) *allen Repositorys* der Organisation | **X** | | | -| Organisationsmitglieder in [externe Mitarbeiter](#outside-collaborators) umwandeln | **X** | | | -| [Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Eine Liste der Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | | | -| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | | | -| Enable team synchronization (see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" for details) | **X** | | | +| Aktion in der Organisation | Inhaber | Mitglieder | Abrechnungsmanager | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:----------:|:------------------:| +| Repositorys erstellen (siehe „[Repository-Erstellung in Deiner Organisation einschränken](/articles/restricting-repository-creation-in-your-organization)“) | **X** | **X** | | +| Abrechnungsinformationen anzeigen und bearbeiten | **X** | | **X** | +| Personen zum Beitritt zur Organisation einladen | **X** | | | +| Einladungen zum Beitritt zur Organisation bearbeiten und zurückziehen | **X** | | | +| Mitglied aus der Organisation entfernen | **X** | | | +| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | | +| Benutzer zu **allen Teams** hinzufügen oder wieder entfernen | **X** | | | +| Organisationsmitglieder zu *Team-Betreuern* ernennen | **X** | | | +| Code-Review-Zuweisungen konfigurieren (Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Geplante Erinnerungen setzen (Weitere Informationen findest Du unter „[Geplante Erinnerungen für Pull-Requests verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Mitarbeiter zu **allen Repositorys** hinzufügen | **X** | | | +| Auf das Auditprotokoll der Organisation zugreifen | **X** | | | +| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | | +| Die Domänen der Organisation überprüfen (siehe „[Domänen Deiner Organisation überprüfen](/articles/verifying-your-organization-s-domain)“) | **X** | | | +| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | +| **Alle Teams** löschen | **X** | | | +| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | | +| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | | +| [Teams in der Hierarchie einer Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Projektboards erstellen (siehe „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“) | **X** | **X** | | +| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | | +| Ein sichtbares Team @erwähnen | **X** | **X** | | +| Kann *Team-Beteuern* werden | **X** | **X** | | +| Einblicke für die Organisation anzeigen (siehe „[Einblicke für Ihre Organisation anzeigen ](/articles/viewing-insights-for-your-organization)“) | **X** | **X** | | +| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | **X** | | +| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | | | +| Teamdiskussionen in **allen Teams** bearbeiten und löschen (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments)“) | **X** | | | +| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | | +| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | | +| Die Anzeige von Einblicken zu den Abhängigkeiten einer Organisation verwalten (siehe „[Die Sichtbarkeit der Einblicke zu den Abhängigkeiten Ihrer Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“) | **X** | | | +| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“) | **X** | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/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](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | +| [SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on) aktivieren und erzwingen | **X** | | | +| [Den SAML-Zugriff eines Benutzers auf Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Die SSH-Zertifizierungsstellen einer Organisation verwalten (siehe „[SSH-Zertifizierungsstellen Ihrer Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities)“) | **X** | | | +| Repositorys übertragen | **X** | | | +| {% data variables.product.prodname_marketplace %}-Apps erwerben, installieren, kündigen und ihre Abrechnung verwalten | **X** | | | +| Apps auf {% data variables.product.prodname_marketplace %} aufführen | **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** | | | +| 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** | | | +| [Die Forking-Richtlinie verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Aktivitäten in öffentlichen Repositorys in einer Organisation einschränken](/articles/limiting-interactions-in-your-organization) | **X** | | | +| Lesen von (pull), Schreiben zu (push) und Kopieren von (clone) *allen Repositorys* der Organisation | **X** | | | +| Organisationsmitglieder in [externe Mitarbeiter](#outside-collaborators) umwandeln | **X** | | | +| [Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Eine Liste der Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | | | +| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | | | +| Enable team synchronization (see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" for details) | **X** | | | {% else %} -| Aktion in der Organisation | Inhaber | Mitglieder | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:---------------------------------------------------------------------------------------------------:| -| Personen zum Beitritt zur Organisation einladen | **X** | | -| Einladungen zum Beitritt zur Organisation bearbeiten und zurückziehen | **X** | | -| Mitglied aus der Organisation entfernen | **X** | | | -| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | | -| Benutzer zu **allen Teams** hinzufügen oder wieder entfernen | **X** | | -| Organisationsmitglieder zu *Team-Betreuern* ernennen | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Code-Review-Zuweisungen konfigurieren (Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} -| Mitarbeiter zu **allen Repositorys** hinzufügen | **X** | | -| Auf das Auditprotokoll der Organisation zugreifen | **X** | | -| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | | -| **Alle Teams** löschen | **X** | | -| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | -| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | -| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | -| Ein sichtbares Team @erwähnen | **X** | **X** | -| Kann *Team-Beteuern* werden | **X** | **X** | -| Repositorys übertragen | **X** | | -| Die SSH-Zertifizierungsstellen einer Organisation verwalten (siehe „[SSH-Zertifizierungsstellen Ihrer Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities)“) | **X** | | -| Projektboards erstellen (siehe „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“) | **X** | **X** | | -| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | **X** | | -| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | | | -| Teamdiskussionen in **allen Teams** bearbeiten und löschen (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments)“) | **X** | | | -| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | **X** | -| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | | -| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“) | **X** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | |{% endif %} -| [Teams in der Hierarchie einer Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Lesen von (pull), Schreiben zu (push) und Kopieren von (clone) *allen Repositorys* der Organisation | **X** | | -| Organisationsmitglieder in [externe Mitarbeiter](#outside-collaborators) umwandeln | **X** | | -| [Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Eine Liste der Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | |{% endif %} +| Aktion in der Organisation | Inhaber | Mitglieder | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:------------------------------------------------------------------------------------------------:| +| Personen zum Beitritt zur Organisation einladen | **X** | | +| Einladungen zum Beitritt zur Organisation bearbeiten und zurückziehen | **X** | | +| Mitglied aus der Organisation entfernen | **X** | | | +| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | | +| Benutzer zu **allen Teams** hinzufügen oder wieder entfernen | **X** | | +| Organisationsmitglieder zu *Team-Betreuern* ernennen | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Code-Review-Zuweisungen konfigurieren (Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Mitarbeiter zu **allen Repositorys** hinzufügen | **X** | | +| Auf das Auditprotokoll der Organisation zugreifen | **X** | | +| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | | +| **Alle Teams** löschen | **X** | | +| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | +| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | +| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | +| Ein sichtbares Team @erwähnen | **X** | **X** | +| Kann *Team-Beteuern* werden | **X** | **X** | +| Repositorys übertragen | **X** | | +| Die SSH-Zertifizierungsstellen einer Organisation verwalten (siehe „[SSH-Zertifizierungsstellen Ihrer Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities)“) | **X** | | +| Projektboards erstellen (siehe „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“) | **X** | **X** | | +| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | **X** | | +| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/articles/managing-disruptive-comments)) | **X** | | | +| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | **X** | +| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | | +| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“) | **X** | | |{% if currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | +{% endif %} +| [Teams in der Hierarchie einer Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Lesen von (pull), Schreiben zu (push) und Kopieren von (clone) *allen Repositorys* der Organisation | **X** | | +| Organisationsmitglieder in [externe Mitarbeiter](#outside-collaborators) umwandeln | **X** | | +| [Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Eine Liste der Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | +{% endif %} {% endif %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 7701ea1ecd..7a3a3f3ca8 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: Berechtigungsebenen für die Repositorys einer Organisation intro: 'Den Zugriff auf die einzelnen Repositorys Deiner Organisation kannst Du durch granulare Berechtigungsebenen anpassen. Auf diese Weise kannst Du Deinen Benutzern Zugriff auf genau die Funktionen und Aufgaben gewähren, die sie tatsächlich benötigen.' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,95 +43,124 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben {% endwarning %} ### Repository-Zugriff der einzelnen Berechtigungsebenen +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} -| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| -| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | -| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | -| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** | -| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** | -| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** | -| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** | -| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** | -| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** | -| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** | -| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Bearbeiten von Wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Melden von Missbrauch oder Spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %} -| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** | -| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** | -| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** | -| [Ausblenden der Kommentare beliebiger Benutzer](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Blockieren von Unterhaltungen](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** | -| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** | -| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** | -| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** | -| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** | -| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Pakete löschen](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** | -| Aktivieren von Projektboards | | | | **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** | -| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** | -| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Interaktionen in einem Repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** |{% endif %} -| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** | -| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** | -| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** | -| Ein Repository zu einem Team hinzufügen (siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** | -| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** | -| Ändern der Einstellungen eines Repositorys | | | | | **X** | -| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** | -| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** | -| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** | -| [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** | -| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [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 %} -| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/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** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %} +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} +| +{% endif %} +| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | +| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | +| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** | +| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** | +| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** | +| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** | +| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** | +| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** | +| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** | +| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Bearbeiten von Wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Melden von Missbrauch oder Spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} +| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** | +| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** | +| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** | +| [Ausblenden der Kommentare beliebiger Benutzer](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Blockieren von Unterhaltungen](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** | +| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** | +| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** | +| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +{% endif %} +| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** | +| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** | +| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Pakete löschen](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** | +| Aktivieren von Projektboards | | | | **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** | +| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** | +| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Interaktionen in einem Repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** +{% endif %} +| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** | +| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** | +| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** | +| Ein Repository zu einem Team hinzufügen (siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** | +| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** | +| Ändern der Einstellungen eines Repositorys | | | | | **X** | +| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** | +| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} +| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/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** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_advanced_security %} features. + +| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** | +| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** | +| [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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** | +| [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 %} +{% endif %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index f8e9441c10..63c954cdef 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -20,12 +20,12 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. -| IdP | SAML | User provisioning | Team synchronization | -| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | User provisioning | Team synchronization | +| -------------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index db737dff12..8c5a799e95 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -33,7 +33,9 @@ Weitere Informationen zu {% data variables.product.prodname_enterprise %} finden To use the {% data variables.product.prodname_enterprise %} portion of the license, the 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 %}. -Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an 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. +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. + +While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 023714da6b..0fadec8542 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ GitHub will display your profile README on your profile page if all of the follo The generated README file is pre-populated with a template to give you some inspiration for your profile README. ![README file with pre-populated template](/assets/images/help/repository/personal-repository-readme-template.png) +For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](http://www.emoji-cheat-sheet.com/)." + ### Removing a profile README The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply: diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 16d6ee1e10..b4c0187e13 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,20 +30,23 @@ Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository. | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | | „[Mitarbeiter in ein persönliches Repository einladen](/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" +{% endif %} | Einen Pull Request auf einem geschützten Branch zusammenführen, selbst ohne genehmigende Reviews | „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches)“ | | Das Repository löschen | „[Repository löschen](/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)" |{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} -| Pakete löschen | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| Pakete löschen | "[Deleting a package](/github/managing-packages-with-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)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | Receive | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/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 %} +| 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 %} | Codeinhaber für das Repository definieren | „[Informationen zu Codeinhabern](/github/creating-cloning-and-archiving-repositories/about-code-owners)“ | | Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Sicherheitshinweise erstellen | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | @@ -64,8 +67,9 @@ Collaborators can also perform the following actions. | Aktion | Weitere Informationen | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/github/building-a-strong-community/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)" | @@ -79,7 +83,8 @@ Collaborators can also perform the following actions. | Create and edit a wiki for the repository | „[Informationen zu Wikis](/github/building-a-strong-community/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" +{% endif %} | sich selbst als Mitarbeiter aus dem Repository entfernen | „[Dich selbst aus dem Repository eines Mitarbeiters entfernen](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)“ | ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md index cdfee96023..dc036e3007 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -1,6 +1,6 @@ --- title: Arten der von GitHub versendeten E-Mails -intro: 'Sie können von {% data variables.product.product_name %} verschiedene Arten von E-Mails erhalten, unter anderem Benachrichtigungen, Kontoinformationen und Marketingkommunikation.' +intro: 'There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, customer research invitations, and marketing communications.' redirect_from: - /articles/types-of-emails-github-sends versions: @@ -25,6 +25,17 @@ Auch kannst Du die Art der E-Mail-Aktualisierungen festlegen, die Du zu Unterhal Falls Du ein Upgrade auf bezahlte Produkte oder Funktionen durchgeführt hast, erhältst Du an die primäre E-Mail-Adresse Deines Kontos Abrechnungsquittungen. Weitere Informationen findest Du unter „[E-Mail-Adresse für die Abrechnung festlegen](/articles/setting-your-billing-email).“ +### Customer research emails + +{% data variables.product.product_name %} occasionally seeks customers to participate in research sessions to help us build a better GitHub. These are conducted remotely, open to customers worldwide, and may include: + +- Feedback surveys +- Research interviews +- Usability testing sessions +- Previewing early prototypes or concepts + +These emails are infrequent and you can choose whether or not to participate. If you're interested in additional opportunities to participate in research sessions, you may add yourself to the GitHub Customer Research Panel. For more information, see "[GitHub Customer Experience Research](https://cxr.github.com)." + ### Marketing-E-Mails {% data variables.product.product_name %} versendet gelegentlich auch E-Mails mit folgenden Arten von Marketingkommunikation: diff --git a/translations/de-DE/content/github/site-policy/github-additional-product-terms.md b/translations/de-DE/content/github/site-policy/github-additional-product-terms.md index 496257fdb2..8f15165d24 100644 --- a/translations/de-DE/content/github/site-policy/github-additional-product-terms.md +++ b/translations/de-DE/content/github/site-policy/github-additional-product-terms.md @@ -55,7 +55,7 @@ Actions and any elements of the Actions service may not be used in violation of - 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 - jegliche weiteren Aktivitäten ohne Bezug zu Produktion, Tests, Bereitstellung oder Veröffentlichung des Software-Projekts, das mit dem Repository verknüpft ist, in dem GitHub Actions verwendet werden. -Um Verstöße gegen diese Einschränkungen und Missbrauch von GitHub Actions zu verhindern, kann GitHub Ihre Verwendung von GitHub Actions überwachen. Der Missbrauch von GitHub Actions kann zur Kündigung von Aufträgen oder zu Beschränkungen Ihrer Möglichkeiten bei der Nutzung von GitHub Actions führen. +Um Verstöße gegen diese Einschränkungen und Missbrauch von GitHub Actions zu verhindern, kann GitHub Ihre Verwendung von GitHub Actions überwachen. 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. #### b. Verwendung von Packages GitHub Packages is billed on a usage basis. The [Packages documentation](/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). diff --git a/translations/de-DE/content/github/site-policy/github-and-trade-controls.md b/translations/de-DE/content/github/site-policy/github-and-trade-controls.md index 10ae8accf4..787459dd13 100644 --- a/translations/de-DE/content/github/site-policy/github-and-trade-controls.md +++ b/translations/de-DE/content/github/site-policy/github-and-trade-controls.md @@ -27,7 +27,9 @@ Die Benutzer sind dafür verantwortlich, sicherzustellen, dass die Inhalte, die GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Darüber hinaus dürfen Benutzer GitHub.com nicht für oder im Namen solcher Parteien nutzen, einschließlich der Regierungen von sanktionierten Ländern. Des Weiteren darf GitHub.com nicht für Zwecke verwendet werden, die nach den geltenden Exportkontrollgesetzen verboten sind, einschließlich verbotener Endnutzungen, die in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) beschrieben sind. +GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. Des Weiteren darf GitHub.com nicht für Zwecke verwendet werden, die nach den geltenden Exportkontrollgesetzen verboten sind, einschließlich verbotener Endnutzungen, die in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) beschrieben sind. #### GitHub Enterprise Server @@ -41,13 +43,13 @@ GitHub Enterprise Server darf nicht in Länder, die in der Ländergruppe E:1 in #### On which countries and territories are U.S. government sanctions applied? -Krim, Kuba, Iran, Nordkorea und Syrien. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. +Krim, Kuba, Iran, Nordkorea und Syrien. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. #### Wie stellt GitHub sicher, dass Personen, die nicht in den sanktionierten Ländern und Gebieten leben bzw. professionelle Verbindungen zu den sanktionierten Ländern und Gebieten haben, immer noch Zugang oder die Möglichkeit haben, Berufung einzulegen? In dem seltenen Fall, dass ein Konto unbeabsichtigt oder irrtümlich betroffen ist, haben wir ein Berufungsverfahren, um solche Fälle zu klären. -Wenn ein einzelner Benutzer oder der Administrator einer Organisation der Meinung ist, fälschlicherweise mit einem Flag gekennzeichnet worden zu sein, dann hat dieser Benutzer die Möglichkeit, gegen die Kennzeichnung Einspruch zu erheben, indem er GitHub Verifizierungsinformationen zur Verfügung stellt. Wenn GitHub hinreichende Informationen erhält, um zu verifizieren, dass der Benutzer oder die Organisation nicht mit einer von den USA sanktionierten oder anderweitig durch US-Wirtschaftssanktionen eingeschränkten Region verbunden ist, wird das Flag entfernt. economic sanctions, then the flag will be removed. Bitte beachten Sie hierzu das [Antragsformular für Einsprüche zu Einzelpersonenkonten](https://airtable.com/shrGBcceazKIoz6pY) und das [Antragsformular für Einsprüche zu Organisationskonten](https://airtable.com/shrB2je5RBkqLEt5D). +Wenn ein einzelner Benutzer oder der Administrator einer Organisation der Meinung ist, fälschlicherweise mit einem Flag gekennzeichnet worden zu sein, dann hat dieser Benutzer die Möglichkeit, gegen die Kennzeichnung Einspruch zu erheben, indem er GitHub Verifizierungsinformationen zur Verfügung stellt. If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction for which we do not have a license or otherwise restricted by U.S. economic sanctions, then the flag will be removed. Bitte beachten Sie hierzu das [Antragsformular für Einsprüche zu Einzelpersonenkonten](https://airtable.com/shrGBcceazKIoz6pY) und das [Antragsformular für Einsprüche zu Organisationskonten](https://airtable.com/shrB2je5RBkqLEt5D). #### Haben Reisen in diese Regionen irgendwelche Auswirkungen? @@ -55,13 +57,17 @@ Reisen in diese Regionen können sich auf Ihren Kontostatus auswirken, aber die #### Was ist verfügbar und nicht verfügbar? -GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. -GitHub hat sich verpflichtet, Entwicklern mit Einzelpersonen- und Organisationskonten in von den USA sanktionierten Regionen weiterhin kostenlose öffentliche Repository-Dienste anzubieten. Dazu gehören der eingeschränkte Zugriff zu kostenlosen Diensten, wie z. B. öffentliche Repositorys für Open-Source-Projekte (und zugehörige öffentliche Seiten), öffentliche Gists und zugeteilte kostenlose Aktionsminuten, nur für die persönliche Kommunikation und nicht für kommerzielle Zwecke. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in Syria and Crimea. Dazu gehören der eingeschränkte Zugriff zu kostenlosen Diensten, wie z. B. öffentliche Repositorys für Open-Source-Projekte (und zugehörige öffentliche Seiten), öffentliche Gists und zugeteilte kostenlose Aktionsminuten, nur für die persönliche Kommunikation und nicht für kommerzielle Zwecke. For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. +GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. + +GitHub services are not available to developers located or otherwise resident in North Korea. #### Wie definieren Sie diese spezifischen Benutzer? @@ -89,8 +95,13 @@ For example, a developer in Iran may sign up for a Free or Pro plan for their in Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. +If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. #### Will Iranian GitHub users be able to use paid services under the license? Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. + +#### Can you clarify availability of GitHub to Cuban developers? + +GitHub cloud services, both free and paid, are generally available to developers located in Cuba. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. diff --git a/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md index 25cbc9fbb5..4a979e7944 100644 --- a/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **January 6, 2021** +Effective date: **January 29, 2021** GitHub bietet viel Transparenz darüber, wie wir Ihre Daten verwenden, wie wir Ihre Daten sammeln und mit wem wir Ihre Daten teilen. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -18,28 +18,26 @@ GitHub bietet viel Transparenz darüber, wie wir Ihre Daten verwenden, wie wir I Wenn wir Ihre Daten an Unterauftragsverarbeiter, wie z. B. unsere Anbieter und Dienstleister, weitergeben, bleiben wir für diese verantwortlich. Wir legen großen Wert darauf, Ihr Vertrauen zu erhalten, wenn wir neue Anbieter hinzuziehen, und wir verlangen von allen Anbietern, dass sie mit uns Datenschutzvereinbarungen abschließen, die deren Verarbeitung von personenbezogenen Benutzerdaten (wie in der [Datenschutzerklärung](/articles/github-privacy-statement/) definiert) einschränken. -| Name des Unterauftragsverarbeiters | Beschreibung der Verarbeitung | Ort der Verarbeitung | Corporate Location | -|:---------------------------------- |:----------------------------------------------------- |:------------------------------ |:------------------------------ | -| Automattic | Hosting-Dienst | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| AWS Amazon | Daten-Hosting | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Braintree (PayPal) | Kreditkarten-Zahlungsabwicklung | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Clearbit | Marketing-Datenanreicherungsservice | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Discourse | Community-Forum-Softwareanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Eloqua | Automatisierung von Marketingkampagnen | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Google Apps | Interne Unternehmensinfrastruktur | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Google Analytics | Analytics and performance | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| MailChimp | Kunden-Ticketing-E-Mail Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Mailgun | Transaktions-Mail-Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Microsoft | Microsoft Services | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Monday.com | Plattform für Teamkollaboration und Projektmanagement | Vereinigte Staaten von Amerika | Israel | -| Nexmo | SMS-Benachrichtigungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Salesforce.com | Customer Relations-Management | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Sendgrid | Transaktions-Mail-Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Sentry.io | Application monitoring provider | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Stripe | Zahlungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Twilio | SMS-Benachrichtigungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Zendesk | Kundensupport-Ticketing-System | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | -| Zuora | Unternehmens-Abrechnungssystem | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Name des Unterauftragsverarbeiters | Beschreibung der Verarbeitung | Ort der Verarbeitung | Corporate Location | +|:---------------------------------- |:--------------------------------------------------------------- |:------------------------------ |:------------------------------ | +| Automattic | Hosting-Dienst | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| AWS Amazon | Daten-Hosting | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Braintree (PayPal) | Kreditkarten-Zahlungsabwicklung | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Clearbit | Marketing-Datenanreicherungsservice | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Discourse | Community-Forum-Softwareanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Eloqua | Automatisierung von Marketingkampagnen | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Google Apps | Interne Unternehmensinfrastruktur | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| MailChimp | Kunden-Ticketing-E-Mail Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Mailgun | Transaktions-Mail-Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Microsoft | Microsoft Services | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Monday.com | Plattform für Teamkollaboration und Projektmanagement | Vereinigte Staaten von Amerika | Israel | +| Nexmo | SMS-Benachrichtigungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Salesforce.com | Customer Relations-Management | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Sentry.io | Application monitoring provider | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Stripe | Zahlungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Zendesk | Kundensupport-Ticketing-System | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | +| Zuora | Unternehmens-Abrechnungssystem | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | Wenn wir einen neuen Unterauftragsverarbeiter einsetzen, der die personenbezogenen Daten unserer Benutzer verarbeitet, oder einen Unterauftragsverarbeiter entfernen oder die Verwendung eines Unterauftragsverarbeiter ändern, werden wir diese Seite aktualisieren. Wenn Sie Fragen oder Bedenken zu einem neuen Unterauftragsverarbeiter haben, helfen wir Ihnen gerne weiter. Bitte kontaktieren Sie uns über {% data variables.contact.contact_privacy %}. @@ -47,7 +45,7 @@ Wenn wir einen neuen Unterauftragsverarbeiter einsetzen, der die personenbezogen GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. -Since the number and names of cookies may change,the table below may be updated from time to time. +Since the number and names of cookies may change, the table below may be updated from time to time. | Service Provider | Cookie Name | Beschreibung | Expiration* | |:---------------- |:------------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------- | diff --git a/translations/de-DE/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/de-DE/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 945e931bd3..1b94714150 100644 --- a/translations/de-DE/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/de-DE/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ Bitte beachten Sie, dass die verfügbaren Informationen von Fall zu Fall variier ### Kostenerstattung -Wir behalten uns das Recht vor, die Erstattung von Verwaltungskosten im Zusammenhang mit der Beantwortung von Informationsanfragen zu beantragen, soweit dies gesetzlich zulässig ist. +Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. + +While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: + +- Initial search of up to 25 identifiers: Free +- Production of subscriber information/data for up to 5 accounts: Free +- Production of subscriber information/data for more than 5 accounts: $20 per account +- Secondary searches: $10 per search ### Datenaufbewahrung diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index d023e9cd4e..1f10ba220b 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -22,7 +22,7 @@ You can sponsor an account on behalf of your user account to invest in projects - Developing brand awareness as an organization that values open source - Thanking open source developers for building libraries that complement the product your organization offers -You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)“. diff --git a/translations/de-DE/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/de-DE/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index 0c903216b2..efdc88a944 100644 --- a/translations/de-DE/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/de-DE/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ Du kannst die meisten Jekyll-Einstellungen konfigurieren, beispielsweise das Des Einige Konfigurationseinstellungen können für {% data variables.product.prodname_pages %}-Websites nicht geändert werden. -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ Standardmäßig werden Codeblöcke auf Deiner Website von Jekyll markiert. Jekyl Wenn Du einen anderen Markierer verwenden möchtest, z. B. `highlight.js`, musst Du die Jekyll-Syntaxmarkierung deaktivieren, indem Du die *_config.yml*-Datei Deines Projekts änderst. -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md b/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md index 2549348cdb..cbff76237d 100644 --- a/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/de-DE/content/github/working-with-github-pages/about-github-pages.md @@ -25,11 +25,15 @@ You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. Weitere Informationen finden Sie unter „[Eine benutzerdefinierte Domain mit {% data variables.product.prodname_pages %} verwenden](/articles/using-a-custom-domain-with-github-pages)“. {% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + Informationen zu den ersten Schritten findest Du unter „[Eine {% data variables.product.prodname_pages %}-Website erstellen](/articles/creating-a-github-pages-site).“ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Organization owners can disable the publication of -{% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." +{% 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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} ### Arten von {% data variables.product.prodname_pages %}-Websites @@ -40,6 +44,10 @@ To publish a user site, you must create a repository owned by your user account Die Quelldateien für eine Projekt-Website werden im selben Repository gespeichert wie das zugehörige Projekt. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +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](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} Weitere Informationen dazu, wie sich die URL Ihrer Website bei benutzerdefinierten Domains ändert, finden Sie unter „[Informationen zu benutzerdefinierten Domains und {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)“. {% endif %} @@ -57,7 +65,7 @@ The URL where your site is available depends on whether subdomain isolation is e `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///` -Weitere Informationen findest Du unter „[Subdomänen-Isolation aktivieren](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)“. Bei Fragen kannst Du Dich auch an den Websiteadministrator wenden. +For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -90,9 +98,9 @@ Die standardmäßige Veröffentlichungsquelle für Projekt-Websites ist der `gh- Du kannst Projekt-Websites auch vom `master`-Branch oder einem `/docs`-Ordner auf dem `master`-Branch veröffentlichen. Um Deine Website aus einer dieser Quellen zu veröffentlichen, musst Du eine andere Veröffentlichungsquelle konfigurieren. Weitere Informationen findest Du unter „[Eine Veröffentlichungsquelle für Deine {% data variables.product.prodname_pages %}-Website konfigurieren](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source).“ - If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. Weitere Informationen zu _CNAME_-Dateien findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site)“.{% endif %} +If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. Weitere Informationen zu _CNAME_-Dateien findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site)“.{% endif %} - Du kannst Deine Projekt-Website nicht aus einem anderen Branch veröffentlichen, auch wenn der Standard-Branch nicht `Master` oder `gh-pages` ist. +Du kannst Deine Projekt-Website nicht aus einem anderen Branch veröffentlichen, auch wenn der Standard-Branch nicht `Master` oder `gh-pages` ist. {% endif %} @@ -118,8 +126,8 @@ Du kannst Projekt-Websites auch vom `master`-Branch oder einem `/docs`-Ordner au - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} - Veröffentlichte {% data variables.product.prodname_pages %}-Websites dürfen nicht größer als 1 GB sein. {% if currentVersion == "free-pro-team@latest" %} - - {% 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. + - {% data variables.product.prodname_pages %}-Websites besitzen eine *weiche* Bandbreitenbegrenzung von 100 GB pro Monat. + - {% data variables.product.prodname_pages %}-Websites besitzen eine *weiche* Begrenzung von 10 Builds pro Stunde. Wenn Ihre Website diese Nutzungskontingente überschreitet, kann Ihre Website ggf. nicht bedient werden oder Sie erhalten eine höfliche E-Mail von {% data variables.contact.contact_support %}, in der Strategien vorgeschlagen werden, um die Auswirkung Ihrer Website auf unsere Server zu reduzieren. Dazu zählen das Einsetzen eines Drittanbieter-CDNs (Content Distribution Networks) vor Ihrer Website, die Nutzung anderer {% data variables.product.prodname_dotcom %}-Features, beispielsweise Veröffentlichungen, oder der Wechsel zu einem anderen Hosting-Dienst, der ggf. besser zu Ihren Anforderungen passt. diff --git a/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index f33edb1ec8..8ab8db35ba 100644 --- a/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/de-DE/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ Build-Fehler (aber keine Build-Warnungen) für Ihre Website können Sie auf {% d Du kannst einen Drittanbieterdienst, beispielsweise [Travis CI](https://travis-ci.org/), so konfigurieren, dass nach jedem Commit Fehlermeldungen angezeigt werden. 1. Wenn Du dies noch nicht getan hast, füge eine Datei namens _Gemfile_ in das Root-Verzeichnis Deiner Veröffentlichungsquelle ein. Die Gemfile-Datei sollte den folgenden Inhalt aufweisen: - ``` + ```ruby source `https://rubygems.org` gem `github-pages` ``` 2. Konfiguriere das Repository Deiner Website für die gewünschte Test-Dienstleistung. Wenn Du beispielsweise [Travis CI](https://travis-ci.org/) verwenden möchtest, füge eine Datei namens _.travis.yml_ in das Root-Verzeichnis Deiner Veröffentlichungsquelle ein, und zwar mit folgendem Inhalt: - ``` + ```yaml language: ruby rvm: - 2.3 diff --git a/translations/de-DE/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 105fe8b524..2428f64998 100644 --- a/translations/de-DE/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/de-DE/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ Personen mit Schreibberechtigungen für ein Repository können mit Jekyll ein De {% data reusables.pages.navigate-publishing-source %} 1. Erstelle eine neue Datei mit den Namen _/assets/css/style.scss_. 2. Füge oben in der Datei den folgenden Inhalt hinzu: - ``` + ```scss --- --- diff --git a/translations/de-DE/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/de-DE/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..57ca0f9f25 --- /dev/null +++ b/translations/de-DE/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. You can see your site's URL in the repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. Um Deine veröffentlichte Website anzuzeigen, klicke unter „{% data variables.product.prodname_pages %}" auf die URL Deiner Website. ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/de-DE/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/de-DE/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 64e327b0ec..698bb1bbd1 100644 --- a/translations/de-DE/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/de-DE/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. Gib im Feld für den Dateinamen `404.html` oder `404.md` ein. ![Feld für den Dateinamen](/assets/images/help/pages/404-file-name.png) 4. Wenn Du die Datei `404.md` genannt hast, füge den folgenden YAML-Frontmatter am Anfang der Datei hinzu: - ``` + ```yaml --- permalink: /404.html --- diff --git a/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index a8a3e6031a..0b93f625bc 100644 --- a/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,9 +11,11 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### Vorrausetzungen -Bevor Du mit Jekyll eine {% data variables.product.prodname_pages %}-Website erstellen kannst, musst Du Jekyll und Git installieren. Weitere Informationen finden Sie unter „[Installation](https://jekyllrb.com/docs/installation/)“ in der Jekyll-Dokumentation und unter „[Git einrichten](/articles/set-up-git)“. +Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website erstellen können, müssen Sie Jekyll und Git installieren. Weitere Informationen findest Du unter „[Installation](https://jekyllrb.com/docs/installation/)“ in der Jekyll-Dokumentation und unter „[Git einrichten](/articles/set-up-git).“ {% data reusables.pages.recommend-bundler %} @@ -58,7 +60,7 @@ Bevor Du mit Jekyll eine {% data variables.product.prodname_pages %}-Website ers # Erstellt einen neuen Ordner mit dem Namen docs $ cd docs ``` - Wenn Du Deine Website aus dem `gh-pages`-Branch veröffentlichen möchtest, erstelle den `gh-pages`-Branch und checke ihn aus. + Wenn Sie Ihre Website aus dem `gh-pages`-Branch veröffentlichen möchten, erstellen Sie den `gh-pages`-Branch und checken ihn aus. ```shell $ git checkout --orphan gh-pages # Erstellt einen neuen Branch, ohne Verlauf und Inhalte, mit dem namen gh-pages und wechselt zum gh-pages-Branch @@ -95,13 +97,14 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md` verfügbar. +Du kannst Deiner Website weitere Seiten hinzufügen, indem Du zusätzliche neue Dateien erstellst. Jede Datei wird auf Deiner Website im selben Verzeichnis verfügbar sein wie Deine Veröffentlichungsquelle. For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html` verfügbar. Du kannst auch ein Design hinzufügen, um das Aussehen der Website anzupassen. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." diff --git a/translations/de-DE/content/github/working-with-github-pages/index.md b/translations/de-DE/content/github/working-with-github-pages/index.md index 23ce7daa00..d5fcbf18d3 100644 --- a/translations/de-DE/content/github/working-with-github-pages/index.md +++ b/translations/de-DE/content/github/working-with-github-pages/index.md @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/de-DE/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 77791115bb..4e593ee90f 100644 --- a/translations/de-DE/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/de-DE/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -78,7 +78,7 @@ Dieser Fehler bedeutet, dass der Code auf eine per Symlink verknüpfte Datei ver Dieser Fehler bedeutet, dass Du nicht lateinische Buchstaben wie `日本語` verwendet hast, ohne dem Computer mitzuteilen, dass er diese Symbole erwarten soll. Zur Fehlerbehebung erzwinge die UTF-8-Codierung. Trage hierzu die folgende Zeile in die Datei *_config.yml* ein: -``` +```yaml encoding: UTF-8 ``` diff --git a/translations/de-DE/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/de-DE/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index 4e9c0443b2..59987630a4 100644 --- a/translations/de-DE/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/de-DE/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: Veröffentlichung einer GitHub Pages-Website zurückziehen -intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available to {% if currentVersion == "free-pro-team@latest" %}the public{% else %}everyone using {% data variables.product.product_location %}{% endif %}.' +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 74d2616783..fa68849caa 100644 --- a/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -13,7 +13,7 @@ versions: Um eine Überschrift zu erstellen, füge bis zu sechs Rautenzeichen (`#`) vor dem Text der Überschrift hinzu. Die Anzahl an `#` bestimmt die Größe der Überschrift. -``` +```markdown # Die größte Überschrift ## Die zweitgrößte Überschrift ###### Die kleinste Überschrift @@ -37,7 +37,7 @@ Um Text hervorzuheben, kannst Du die Fett- und/oder Kursivschrift verwenden oder Du kannst einen Text mit einem `>` zitieren. -``` +```markdown Mit den Worten von Abraham Lincoln: > Verzeihen Sie meine Ausdrucksweise. @@ -55,7 +55,7 @@ Mit den Worten von Abraham Lincoln: Du kannst Code oder einen Befehl innerhalb eines Satzes mit einfachen Backticks zitieren. Der Text innerhalb der Backticks wird nicht formatiert. -``` +```markdown Verwende `git status`, um alle neuen oder geänderten Dateien aufzulisten, die noch nicht freigegeben wurden. ``` @@ -102,7 +102,7 @@ Du kannst einen Inline-Link erstellen, indem Du den Text in eckige Klammern `[ ] Du kannst eine ungeordnete Liste erstellen, indem Du einer Textzeile oder mehreren Textzeilen ein `-` oder `*` voranstellst. -``` +```markdown - George Washington - John Adams - Thomas Jefferson @@ -112,7 +112,7 @@ Du kannst eine ungeordnete Liste erstellen, indem Du einer Textzeile oder mehrer Um Deine Liste zu ordnen, stelle jeder Zeile eine Zahl voran. -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams @@ -126,7 +126,7 @@ Du kannst eine verschachtelte Liste erstellen, indem Du ein Listenelement oder m Beim Web-Editor auf {% data variables.product.product_name %} oder bei einem Texteditor wie [Atom](https://atom.io/), der eine nicht proportionale Schriftart verwendet, kannst Du Deine Liste visuell ausrichten. Gib vor dem einzurückenden Listenelement so viele Leerzeichen ein, bis das Listenzeichen (`-` oder `*`) direkt unter dem ersten Zeichen des darüber liegenden Elements liegt. -``` +```markdown 1. First list item - First nested list item - Second nested list item @@ -140,7 +140,7 @@ Um eine verschachtelte Liste im Kommentareditor auf {% data variables.product.pr Im folgenden Beispiel kannst Du ein untergeordnetes Listenelement unter dem Listenelement `100. Erstes Listenelement` hinzufügen, indem Du das untergeordnete Listenelement um mindestens fünf Leerzeichen einrückst, da sich vor `Erstes Listenelement` fünf Zeichen (`100.`) befinden. -``` +```markdown 100. Erstes Listenelement - Erstes untergeordnetes Listenelement ``` @@ -149,7 +149,7 @@ Im folgenden Beispiel kannst Du ein untergeordnetes Listenelement unter dem List Du kannst mit derselben Methode mehrere Ebenen an verschachtelten Listen erstellen. Beispiel: Beim ersten untergeordneten Listenelement stehen sieben Zeichen (`␣␣␣␣␣-␣`) vor `Erstes untergeordnetes Listenelement`. Daher musst Du das zweite untergeordnete Listenelement um sieben Leerzeichen einrücken. -``` +```markdown 100. Erstes Listenelement - Erstes untergeordnetes Listenelement - Zweites untergeordnetes Listenelement diff --git a/translations/de-DE/content/github/writing-on-github/organizing-information-with-tables.md b/translations/de-DE/content/github/writing-on-github/organizing-information-with-tables.md index c6f12e9c0a..0467856252 100644 --- a/translations/de-DE/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/de-DE/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: Tabellen werden mit senkrechten Strichen (`|`) und Bindestrichen (`-`) erstellt. Mit Bindestrichen werden die Überschriften der Tabelle erstellt; die senkrechten Striche trennen die Spalten voneinander ab. Vor der Tabelle musst Du eine Zeile frei lassen, damit sie korrekt dargestellt wird. -``` +```markdown | First Header | Second Header | | ------------- | ------------- | @@ -27,7 +27,7 @@ Die senkrechten Striche am linken und rechten Rand der Tabelle sind optional. Die Zellen können unterschiedlich breit sein und müssen nicht perfekt an den Spalten ausgerichtet sein. In jeder Spalte der Überschriftenzeile müssen mindestens drei Bindestriche vorhanden sein. -``` +```markdown | Command | Description | | --- | --- | | git status | List all new or modified files | @@ -40,7 +40,7 @@ Die Zellen können unterschiedlich breit sein und müssen nicht perfekt an den S Du kannst [Formatierungen](/articles/basic-writing-and-formatting-syntax) wie Links, Inline-Codeblöcke und Textstile in Deiner Tabelle verwenden: -``` +```markdown | Command | Description | | --- | --- | | `git status` | List all *new or modified* files | @@ -51,7 +51,7 @@ Du kannst [Formatierungen](/articles/basic-writing-and-formatting-syntax) wie Li Du kannst den Text links oder rechts ausrichten oder zentrieren, indem Du links oder rechts oder an beiden Seiten der Bindestriche in der Überschriftenzeile einen Doppelpunkt (`:`) hinzufügst. -``` +```markdown | Left-aligned | Center-aligned | Right-aligned | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ Du kannst den Text links oder rechts ausrichten oder zentrieren, indem Du links Wenn Du einen senkrechten Strich (`|`) als Inhalt einer Zelle einfügen möchtest, verwende das Zeichen '\' vor dem senkrechten Strich: -``` +```markdown | Name | Character | | --- | --- | | Backtick | ` | diff --git a/translations/de-DE/content/graphql/guides/introduction-to-graphql.md b/translations/de-DE/content/graphql/guides/introduction-to-graphql.md index 017b674775..069cb73fd6 100644 --- a/translations/de-DE/content/graphql/guides/introduction-to-graphql.md +++ b/translations/de-DE/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This * Query `__schema` to list all types defined in the schema and get details about each: ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* Query `__type` to get details about any type: + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* Query `__type` to get details about any type: - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * You can also run an _introspection query_ of the schema via a `GET` request: diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 20b33760bb..b679ad2a3e 100644 --- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -14,7 +14,7 @@ After you enable the link, each user can navigate directly from {% data variable 1. Connect to the administrative shell for {% data variables.product.prodname_ghe_server %}. Weitere Informationen finden Sie unter „[Auf die Verwaltungsshell (SSH) zugreifen](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)“. 2. Run the following command. - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. Return to diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index ab1ce4a271..913fd3dce1 100644 --- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - You must install dependencies on the application server. - [Docker](https://docs.docker.com/install/) 1.13.0+ - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/), available via apt for [Debian](https://packages.debian.org/search?keywords=netcat) and [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} diff --git a/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index ece0d0f81d..d74b8e83a1 100644 --- a/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ If you want to interact with multiple repositories, you can add each repository If your instance has subdomain isolation enabled: {% endif %} -``` +```xml "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` @@ -118,7 +118,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y {% data reusables.package_registry.authenticate-step %} 2. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -130,7 +130,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y 3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html). - ``` + ```ruby source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" diff --git a/translations/de-DE/content/packages/index.md b/translations/de-DE/content/packages/index.md index 1defcebba0..3d492fe556 100644 --- a/translations/de-DE/content/packages/index.md +++ b/translations/de-DE/content/packages/index.md @@ -12,13 +12,18 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: + - + title: ghcr.io maintenance mode on 2021-01-09 + date: '2021-01-08' + href: https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/ - title: ghcr.io container names redirect to the container page date: '2020-12-14' @@ -27,10 +32,6 @@ changelog: title: Filter for tagged and untagged containers date: '2020-12-14' href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: Packages container support is an opt-in beta - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/de-DE/content/packages/manage-packages/deleting-a-package.md b/translations/de-DE/content/packages/manage-packages/deleting-a-package.md index 26ec6cab51..591b51e088 100644 --- a/translations/de-DE/content/packages/manage-packages/deleting-a-package.md +++ b/translations/de-DE/content/packages/manage-packages/deleting-a-package.md @@ -54,7 +54,7 @@ Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token. {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md index 6dc2e0240c..2d0f25d9c9 100644 --- a/translations/de-DE/content/rest/overview/libraries.md +++ b/translations/de-DE/content/rest/overview/libraries.md @@ -79,6 +79,10 @@ Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https: Library name | Repository |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +### Rust + +Library name | Repository |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) + ### Scala Library name | Repository |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) diff --git a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md index cfbcf43b1a..ab286e3b63 100644 --- a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md @@ -107,7 +107,7 @@ _Suche_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permission on "actions" - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Mitarbeiter_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Commit-Kommentare_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -836,6 +842,9 @@ _Teams_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/de-DE/data/glossaries/external.yml b/translations/de-DE/data/glossaries/external.yml index f67f6c68d1..3a8f9d4c8d 100644 --- a/translations/de-DE/data/glossaries/external.yml +++ b/translations/de-DE/data/glossaries/external.yml @@ -35,7 +35,7 @@ - term: Bio description: >- - Die vom Benutzer generierte Beschreibung, die sich in einem Profil befindet: https://help.github.com/articles/adding-a-bio-to-your-profile/ + The user-generated description found on a profile: [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile) - term: Abrechnungszeitraum description: Das Zeitintervall für Ihren spezifischen Abrechnungsplan. @@ -156,7 +156,7 @@ - term: Beiträge description: >- - Spezifische Aktivitäten auf GitHub, die: - dem Beteiligungsdiagramm eines Benutzers ein Quadrat hinzufügen: „[Was zählt als ein Beitrag](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)“ - der Zeitleiste eines Benutzers in dessen Profil Aktivitäten hinzufügen "[Beitragsaktivität](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" + Specific activities on GitHub that will: - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - term: Mitwirkende description: >- @@ -229,7 +229,7 @@ Ein Branch, der verwendet wird, um mit einem neuen Feature zu experimentieren oder einen nicht in der Produktion befindlichen Issue zu korrigieren. Wird auch als Themen-Branch bezeichnet. - term: Fenced-Code-Block - description: 'Ein eingerückter Codeblock, den Du mit GitHub Flavored Markdown mit dreifachen Backticks vor und nach dem Codeblock erstellen kannst. Siehe hierzu dieses [example](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' + description: 'An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' - term: abrufen description: >- diff --git a/translations/de-DE/data/learning-tracks/README.md b/translations/de-DE/data/learning-tracks/README.md new file mode 100644 index 0000000000..ec0f70309e --- /dev/null +++ b/translations/de-DE/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Learning Tracks (aka Learning Paths) + +Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. \ No newline at end of file diff --git a/translations/de-DE/data/learning-tracks/actions.yml b/translations/de-DE/data/learning-tracks/actions.yml index e13873512c..b6017eeb75 100644 --- a/translations/de-DE/data/learning-tracks/actions.yml +++ b/translations/de-DE/data/learning-tracks/actions.yml @@ -31,6 +31,13 @@ continuous_deployment: - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Deploy to the cloud' + description: 'Learn how to use {% data variables.product.prodname_actions %} to build an application and deploy it to various cloud-based platforms.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine hosting_your_own_runners: title: 'Host your own runners' description: 'Du kannst selbst-gehostete Runner erstellen, um Workflows in einer hochgradig anpassbaren Umgebung zu betreiben.' diff --git a/translations/de-DE/data/release-notes/2-20/18.yml b/translations/de-DE/data/release-notes/2-20/18.yml index 3aab7ba337..f38b400522 100644 --- a/translations/de-DE/data/release-notes/2-20/18.yml +++ b/translations/de-DE/data/release-notes/2-20/18.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/9.yml b/translations/de-DE/data/release-notes/2-21/9.yml index 46656c9e6b..a712183036 100644 --- a/translations/de-DE/data/release-notes/2-21/9.yml +++ b/translations/de-DE/data/release-notes/2-21/9.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-22/1.yml b/translations/de-DE/data/release-notes/2-22/1.yml index fbd3988c3d..8edfa619f0 100644 --- a/translations/de-DE/data/release-notes/2-22/1.yml +++ b/translations/de-DE/data/release-notes/2-22/1.yml @@ -12,7 +12,7 @@ sections: - | Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | diff --git a/translations/de-DE/data/release-notes/3-0/0-rc1.yml b/translations/de-DE/data/release-notes/3-0/0-rc1.yml new file mode 100644 index 0000000000..1d9293905b --- /dev/null +++ b/translations/de-DE/data/release-notes/3-0/0-rc1.yml @@ -0,0 +1,145 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. 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 variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - 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. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/de-DE/data/release-notes/3-0/0-rc2.yml b/translations/de-DE/data/release-notes/3-0/0-rc2.yml new file mode 100644 index 0000000000..0e6ed5fd3f --- /dev/null +++ b/translations/de-DE/data/release-notes/3-0/0-rc2.yml @@ -0,0 +1,25 @@ +--- +date: '2021-01-29' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +sections: + bugs: + - + heading: Fixes for known issues from Release Candidate 1 + notes: + - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. + - The "Mandatory message viewed" audit log event was not being saved. + - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' + - Removing yourself as an enterprise owner returned a 404. + - + heading: Fixes for other issues + notes: + - Issues with migrations and upgrades to 3.0.0 have been fixed. + - Backup Utilities versioning now works for release candidate versions. + - Generating a support bundle resulted in an error in the orchestrator logs. + - A large restore could result in Redis running out of memory. + - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. + - GitHub Actions can only be enabled if the required storage is also configured. + - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + known_issues: + - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/translations/de-DE/data/reusables/actions/actions-not-verified.md b/translations/de-DE/data/reusables/actions/actions-not-verified.md index 3107e5a79f..1eebaf90f5 100644 --- a/translations/de-DE/data/reusables/actions/actions-not-verified.md +++ b/translations/de-DE/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/de-DE/data/reusables/code-scanning/not-available.md b/translations/de-DE/data/reusables/code-scanning/not-available.md index 6531f5e1d0..0e4d2ac82f 100644 --- a/translations/de-DE/data/reusables/code-scanning/not-available.md +++ b/translations/de-DE/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." {% endnote %} {% endif %} diff --git a/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md new file mode 100644 index 0000000000..c5142332f6 --- /dev/null +++ b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + +{% endnote %} diff --git a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md index 2b866ca1c3..3fd62db750 100644 --- a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md +++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md @@ -1,34 +1,35 @@ -The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. +The following table shows, for each package manager: +- The YAML value to use in the *dependabot.yml* file +- The supported versions of the package manager +- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +- Whether vendored dependencies are supported -| Paketmanager | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | -| -------------------------------- |:-----------------------------------------------------------------:|:---------:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir: `hex` | | | -| Elm: `elm` | **✓** | | -| git submodule: `gitsubmodule` | **✓** | | -| GitHub Actions: `github-actions` | **✓** | | -| Go modules: `gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +| Paketmanager | YAML value | Supported versions | Private repositories | Vendoring | +| -------------- | ---------------- | ------------------------- |:--------------------:|:---------:| +| Bundler | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1,v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | +| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | +| Go modules | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | see (A) below | **✓** | | +| Maven | `maven` | see (B) below | **✓** | | +| npm | `npm` | v6 | **✓** | | +| NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**Note**: {% data variables.product.prodname_dependabot %} also supports the following package managers: +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn` (v1 only) (specify `npm`) +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --`.gradle.kts` files, for Kotlin projects (specify `gradle`) - --`pipenv`, `pip-compile`, and `poetry` (specify `pip`) - -For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. diff --git a/translations/de-DE/data/reusables/desktop/delete-tag.md b/translations/de-DE/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..40d455b880 --- /dev/null +++ b/translations/de-DE/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Right-click the commit. + + - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) + - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/education/about-github-education-link.md b/translations/de-DE/data/reusables/education/about-github-education-link.md index 07fa77c6a3..89bb45f873 100644 --- a/translations/de-DE/data/reusables/education/about-github-education-link.md +++ b/translations/de-DE/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Bevor Sie einen individuellen Rabatt anwenden, sollten Sie überprüfen, ob Ihre Lerngemeinschaft bereits mit uns als {% data variables.product.prodname_education %}-Bildungseinrichtung zusammenarbeitet. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)“. +Bevor Sie einen individuellen Rabatt anwenden, sollten Sie überprüfen, ob Ihre Lerngemeinschaft bereits mit uns als {% data variables.product.prodname_education %}-Bildungseinrichtung zusammenarbeitet. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)." diff --git a/translations/de-DE/data/reusables/education/apply-for-team.md b/translations/de-DE/data/reusables/education/apply-for-team.md index 0b4fc2dd78..23f7390ef7 100644 --- a/translations/de-DE/data/reusables/education/apply-for-team.md +++ b/translations/de-DE/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Melden Sie sich kostenlos für[{% data variables.product.prodname_team %}](/articles/github-s-products) an, was unbegrenzte Benutzer- und private Repositorys ermöglicht. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." +- Melden Sie sich kostenlos für[{% data variables.product.prodname_team %}](/articles/github-s-products) an, was unbegrenzte Benutzer- und private Repositorys ermöglicht. For more information, see "[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)." diff --git a/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md index 0575e98979..b954fd40d9 100644 --- a/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. Stellen Sie eine SSH-Verbindung zu {% data variables.product.product_location %} her. +1. Stellen Sie eine SSH-Verbindung zu {% data variables.product.product_location %} her. Weitere Informationen findest Du unter "[Auf die administrative Shell (SSH) zugreifen](/admin/configuration/accessing-the-administrative-shell-ssh)." ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 7509a88325..0cdbb1f880 100644 --- a/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. Informationen zum Importieren der archivierten Migrationsdaten auf eine {% data variables.product.prodname_ghe_server %}-Instanz findest Du unter „[Migrationsdaten in {% data variables.product.prodname_ghe_server %} importieren](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)“. +1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[Preparing to migrate data to your enterprise](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/de-DE/data/reusables/gated-features/private-pages.md b/translations/de-DE/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..3fb7f0a3a7 --- /dev/null +++ b/translations/de-DE/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/de-DE/data/reusables/github-actions/actions-billing.md b/translations/de-DE/data/reusables/github-actions/actions-billing.md index ce71eadc8a..f8681e17b4 100644 --- a/translations/de-DE/data/reusables/github-actions/actions-billing.md +++ b/translations/de-DE/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. Für private Repositorys erhält jedes {% data variables.product.prodname_dotcom %} Konto eine bestimmte Menge von kostenlosen Minuten und Speicher, abhängig vom Produkt, das mit dem Konto verwendet wird. Any usage beyond the included amounts is controlled by spending limits. +{% data variables.product.prodname_actions %} usage is free for both public repositories and self-hosted runners. Für private Repositorys erhält jedes {% data variables.product.prodname_dotcom %} Konto eine bestimmte Menge von kostenlosen Minuten und Speicher, abhängig vom Produkt, das mit dem Konto verwendet wird. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md b/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md index 12aa7839a6..170cb9d652 100644 --- a/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ Die Starter-Workflowvorlage richtet den `PATH` so ein, dass er OpenJDK 8 für di Um beispielsweise Version 9.0.4 des JDK für die x64-Plattform zu verwenden, kannst Du die `setup-java` Aktion verwenden und die `java-version`- und `architecture`-Parameter auf `'9.0.4'` und `x64` konfigurieren. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md b/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md index e6db4f8803..0114ffafd7 100644 --- a/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a private preview only. Any users or organizations that are already using this runner can continue using it, but we're not accepting any further users or organizations at this time. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/de-DE/data/reusables/marketplace/launch-with-free.md b/translations/de-DE/data/reusables/marketplace/launch-with-free.md index 2151c241cc..15e06d0cb2 100644 --- a/translations/de-DE/data/reusables/marketplace/launch-with-free.md +++ b/translations/de-DE/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md index c1f424a22c..29620e32dc 100644 --- a/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ b/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -1 +1 @@ -Wenn Du kein Abrechnungsmanager für die Organisation bist, bitte Deinen Kunden, einen *Inhaber* der Organisation aufzufordern, [Dich als Abrechnungsmanager zur Organisation hinzuzufügen](/articles/adding-a-billing-manager-to-your-organization). +If you're not a billing manager for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/de-DE/data/reusables/pages/about-private-publishing.md b/translations/de-DE/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..f1f13531ce --- /dev/null +++ b/translations/de-DE/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. diff --git a/translations/de-DE/data/reusables/pages/choose-visibility.md b/translations/de-DE/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..bd794a90d7 --- /dev/null +++ b/translations/de-DE/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..fc98787aaa --- /dev/null +++ b/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md b/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md index b4f8191832..04d4ddeb1c 100644 --- a/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. Wenn Du sensitive Daten im Repository Deiner Website hast, solltest Du diese vor der Veröffentlichung entfernen. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md b/translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..cb26664aee --- /dev/null +++ b/translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**Hinweis:** Es kann bis zu 20 Minuten dauern, bis die Änderungen auf Ihrer Website veröffentlicht werden, nachdem Sie die Änderungen zu {% data variables.product.product_name %} gepusht haben. Wenn Deine Änderungen nach einer Stunde in Deinem Browser nicht angezeigt werden, findest Du weitere Informationen unter „[Über Jekyll-Build-Fehler für {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/pages/visit-site.md b/translations/de-DE/data/reusables/pages/visit-site.md index 70a87291a9..ba9f775cf9 100644 --- a/translations/de-DE/data/reusables/pages/visit-site.md +++ b/translations/de-DE/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% note %} - **Hinweis:** Es kann bis zu 20 Minuten dauern, bis die Änderungen auf Ihrer Website veröffentlicht werden, nachdem Sie die Änderungen zu {% data variables.product.product_name %} gepusht haben. Wenn Deine Änderungen nach einer Stunde in Deinem Browser nicht angezeigt werden, findest Du weitere Informationen unter „[Über Jekyll-Build-Fehler für {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md index 2a8006d4af..1453480814 100644 --- a/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ Wenn Du die Option **Rebase and merge** (Rebase und Merge) für einen Pull Reque Für das Rebasing und Mergen von Pull Requests musst Du im Repository über [Schreibberechtigungen](/articles/repository-permission-levels-for-an-organization/) verfügen. Zudem muss das Repository [Rebase-Merging zulassen](/articles/configuring-commit-rebasing-for-pull-requests/). -Das Rebase- und Merge-Verhalten auf {% data variables.product.product_name %} weicht etwas von `git rebase` ab. Rebase und Merge auf {% data variables.product.prodname_dotcom %} aktualisiert jederzeit die Informationen zum Beitragenden und erstellt neue Commit-SHAs. Demgegenüber ändert `git rebase` außerhalb von {% data variables.product.prodname_dotcom %} nicht die Informationen zum Beitragenden, wenn das Rebasing zusätzlich zu einem Vorgänger-Commit erfolgt. Weitere Informationen zu `git rebase` findest Du im [Kapitel zu „Git rebase“ im _Pro Git_-Buch](https://git-scm.com/docs/git-rebase). +Das Rebase- und Merge-Verhalten auf {% data variables.product.product_name %} weicht etwas von `git rebase` ab. Rebase und Merge auf {% data variables.product.prodname_dotcom %} aktualisiert jederzeit die Informationen zum Beitragenden und erstellt neue Commit-SHAs. Demgegenüber ändert `git rebase` außerhalb von {% data variables.product.prodname_dotcom %} nicht die Informationen zum Beitragenden, wenn das Rebasing zusätzlich zu einem Vorgänger-Commit erfolgt. For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). Eine visuelle Darstellung von `git rebase` findest Du im [Kapitel „Git-Branching - Rebasing“ im _Pro Git_-Buch](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md index 918dab289f..c83e052fa8 100644 --- a/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -If you use Okta as your IdP, you can use SCIM to manage organization membership in your enterprise account. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. +If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. diff --git a/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md b/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md index 7b7bf4115a..306c505acf 100644 --- a/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. Scroll down to the Marketplace section and click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md index aa6f41ba89..27f9b17d1c 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Schlüssel | Typ | Beschreibung | -| --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| Schlüssel | Typ | Beschreibung | +| --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml index 459188439c..dcdf70a038 100644 --- a/translations/de-DE/data/ui.yml +++ b/translations/de-DE/data/ui.yml @@ -138,9 +138,19 @@ product_sublanding: learning_paths: Learning paths learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. more_guides: more guides - guideTypes: + load_more: Load more guides + all_guides: All Guides + no_result: Sorry, there is no guide that match your filter. + filters: + type: Typ + topic: Topic + all: Alle + guide_types: overview: Übersicht quick_start: Schnellstart tutorial: Tutorial how_to: How-to guide reference: Referenz +learning_track_nav: + prevGuide: Previous guide + nextGuide: Next guide diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml index c9d8fb7264..20dbdcb2ac 100644 --- a/translations/de-DE/data/variables/product.yml +++ b/translations/de-DE/data/variables/product.yml @@ -61,6 +61,7 @@ prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub App' prodname_github_apps: 'GitHub Apps' prodname_oauth_app: 'OAuth App' +prodname_oauth_apps: 'OAuth Apps' #API and developer docs prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs' prodname_support_forum_with_url: '[GitHub API Entwicklungs- und Support-Forum](https://github.community/c/github-api-development-and-support/37)' diff --git a/translations/es-ES/content/actions/creating-actions/about-actions.md b/translations/es-ES/content/actions/creating-actions/about-actions.md index b0a3fae16a..9137bc0d9e 100644 --- a/translations/es-ES/content/actions/creating-actions/about-actions.md +++ b/translations/es-ES/content/actions/creating-actions/about-actions.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - Action development + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ steps: #### Utilizar el SHA de las confirmaciones para la administración de lanzamientos -Cada confirmación de Git recibe un valor calculado de SHA, el cual es único e inmutable. Los usuarios de tus acciones podrían preferir obtener un valor de SHA para la confirmación, ya que este acercamiento puede ser más confiable que especificar una etiqueta, la cual podría borrarse o moverse. Sin embargo, esto significa que los usuarios no recibirán ls actualizaciones posteriores que se hagan a la acción. Utilizar el valor completo de SHA de una confirmación en vez de su valor abreviado puede ayudar a prevenir que las personas utilicen una confirmación malintencionada que utilice la misma abreviación. +Cada confirmación de Git recibe un valor calculado de SHA, el cual es único e inmutable. Los usuarios de tus acciones podrían preferir obtener un valor de SHA para la confirmación, ya que este acercamiento puede ser más confiable que especificar una etiqueta, la cual podría borrarse o moverse. Sin embargo, esto significa que los usuarios no recibirán ls actualizaciones posteriores que se hagan a la acción. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Debes utilizar el valor completo del SHA de la confirmación y no el abreviado.{% else %}El utilizar el valor completo del SHA de la confirmación en vez del abreviado ayuda a prevenir que las personas utilicen una confirmación mal intencionada que utiice la misma abreviación.{% endif %} ```yaml steps: @@ -163,6 +166,6 @@ Mientras que tanto las {% data variables.product.prodname_actions %} como las {% * No necesitan que implementas un código o que sirvas una aplicación. * Tienen una interfaz simple para crear y usar secretos, que permite que las acciones interactúen con servicios de terceros sin la necesidad de almacenar las credenciales de la persona que utiliza la acción. -### Further reading +### Leer más - "[Herramientas de desarrollo para {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)" diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md index d31c1b8402..ed51399971 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Action development' --- {% data reusables.actions.enterprise-beta %} @@ -65,12 +67,12 @@ Antes de que comiences, crearás un repositorio de {% data variables.product.pro required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -122,7 +124,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} 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 75c588f069..50fbe97a58 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 @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Action development' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ Antes de comenzar, necesitarás crear un repositorio GitHub. 1. Desde tu terminal, cambia los directorios en el repositorio nuevo. - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ Antes de comenzar, necesitarás crear un repositorio GitHub. 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)". **Dockerfile** -```dockerfile +```dockerfile{:copy} # Imagen del contenedor que ejecuta tu código FROM alpine:3.10 @@ -65,7 +68,7 @@ Crear un nuevo archivo `action.yml` en el directorio `hello-world-docker` que cr {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ A continuación, el script obtiene la hora actual y la establece como una variab 1. Crea un archivo `entrypoint.sh` nuevo en el directorio `hello-world-docker-action`. -1. Convierte tu archivo `entrypoint.sh` en ejecutable: - - ```shell - chmod +x entrypoint.sh - ``` - 1. Agrega el siguiente código a tu archivo `entrypoint.sh`. **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" 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)". +1. Haz ejecutable tu archivo `entrypoint.sh` ejecutando el siguiente comando en tu sistema. + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### Crear un 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. @@ -130,7 +132,7 @@ En tu directorio <`hello-world-docker-action`, crea un archivo `README.md` que e - Un ejemplo de cómo usar tu acción en un flujo de trabajo. **README.md** -```markdown +```markdown{:copy} # Acción de docker Hello world Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro. @@ -160,7 +162,7 @@ Desde tu terminal, confirma tus archivos `action.yml`, `entrypoint.sh`, `Dockerf 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)". -```shell +```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 @@ -175,11 +177,11 @@ Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acc #### Ejemplo usando una acción pública -El siguiente código de flujo de trabajo usa 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` por tu nombre de repositorio y acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. +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` por tu nombre de repositorio y acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. {% if currentVersion == "free-pro-team@latest" %}Las acciones públicas pueden utilizarse aún si no se han publicado en {% 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 %} {% raw %} **.github/workflows/main.yml** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### Ejemplo usando una acción privada -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. +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. {% if currentVersion == "free-pro-team@latest" %}Esta acción privada no puede publicarse en {% data variables.product.prodname_marketplace %} y solo puede utilizarse en este repositorio.{% endif %} {% raw %} **.github/workflows/main.yml** -```yaml +```yaml{:copy} on: [push] jobs: diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md index 70427bb274..febc90dd13 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Action development' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 16760fb16e..27421c61b5 100644 --- a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -48,20 +48,21 @@ La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`. -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` Si quieres la sustitución de variables, entonces puedes utilizar la forma _shell_ o ejecutar el shell directamente. Por ejemplo, al utilizar el siguiente formato _exec_ puedes ejecutar un shell para imprimir el valor almacenado en la variable de ambiente `GITHUB_SHA`. -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` Para proporcionar el `args` que se definió en el archivo de metadatos de la acción en un contenedor de Docker que utiliza la forma _exec_ en el `ENTRYPOINT`, recomendamos crear un script de shell llamado `entrypoint.sh` al que puedas llamar desde la instrucción `ENTRYPOINT`: ##### *Dockerfile* de ejemplo -``` + +```dockerfile # Container image that runs your code FROM debian:9.5-slim diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 6200ec5b79..6d4e625db9 100644 --- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -330,7 +330,7 @@ Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si u {% data reusables.github-actions.dockerfile-guidelines %} -Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entoces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos. +Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entonces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos. Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)". @@ -350,7 +350,7 @@ runs: ### `branding (marca)` -Puedes usar un color y un icono de [Pluma](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). +Puedes usar un color y un icono de [Feather](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Las insignias se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). #### Ejemplo @@ -362,400 +362,399 @@ branding: #### `branding.color` -El color de fondo de la insignia. Puede ser: `blanco`, `amarillow`, `azul`, `verde`, `anaranjado`, `rojo`, `púrpura` o `gris oscuro`. +El color de fondo de la insignia. Puede ser: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, o `gray-dark`. #### `branding.icon` -El nombre del icono de [Pluma](https://feathericons.com/) que se debe usar. +El nombre del icono de [Feather](https://feathericons.com/) que se debe usar. - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - + - - + + - - - - + + + + - - - + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - + - - + + - - - + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - - + + + + - + - - + + - - - - + + + + - - - + + + - - - - + + + + - - - - + + + + - - - - + + + + - - - + + + - - - - + + + + - - - + + + - - + + - + - - - - + + + + - - - - + + + + - - - + + + - - - - + + + + - - - - + + + + - - + + - + - - - + + + - - - - + + + + - - - + + + - - - + + + - + diff --git a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md index 970913b379..f90208762c 100644 --- a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,11 +41,13 @@ Para obtener más información, consulta "[Crear una acción JavaScript](/articl Si vas a crear una acción de contenedor Docker, puedes establecer un código de salida fallida en tu script `entrypoint.sh`. Por ejemplo: +{% raw %} ``` if ; then echo "Game over!" exit 1 fi ``` +{% endraw %} Para obtener más información, consulta "[Crear una acción de contenedor Docker](/articles/creating-a-docker-container-action)". diff --git a/translations/es-ES/content/actions/guides/about-continuous-integration.md b/translations/es-ES/content/actions/guides/about-continuous-integration.md index 133621c5a1..25a9b0df75 100644 --- a/translations/es-ES/content/actions/guides/about-continuous-integration.md +++ b/translations/es-ES/content/actions/guides/about-continuous-integration.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -56,7 +59,7 @@ Busca en la lista completa de plantillas de flujo de trabajo para IC que ofrece Para obtener más información, consulta "[ Configuración de flujo de trabajo](/articles/configuring-a-workflow)". -### Further reading +### Leer más - "[Configurar la integración continua utilizando {% data variables.product.prodname_actions %}](/articles/setting-up-continuous-integration-using-github-actions)" {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md b/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md index fe715f097c..777f474052 100644 --- a/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - Embalaje --- {% data reusables.actions.enterprise-beta %} @@ -48,6 +50,6 @@ Además de cargar artefactos de empaquetado para las pruebas en un flujo de trab Puedes automatizar esto creando un flujo de trabajo que publique paquetes en un registro de paquetes en cada creación de lanzamiento. Para obtener más información, consulta "[Crear lanzamientos](/github/administering-a-repository/creating-releases)." -### Further reading +### Leer más - "[Publicar paquetes Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)" diff --git a/translations/es-ES/content/actions/guides/about-service-containers.md b/translations/es-ES/content/actions/guides/about-service-containers.md index 2d7a39ad2b..95c4d0ffe3 100644 --- a/translations/es-ES/content/actions/guides/about-service-containers.md +++ b/translations/es-ES/content/actions/guides/about-service-containers.md @@ -8,7 +8,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ Puedes usar la palabra clave `services` para crear contenedores de servicios que Este ejemplo crea un servicio llamado `redis` en un trabajo llamado `container-job`. El host de Docker en este ejemplo es el contenedor `node: 10.18-jessie`. {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -88,7 +91,7 @@ Cuando especificas el puerto del host de Docker pero no el puerto del contenedor Este ejemplo asigna el puerto 6379 del contenedor de servicios `redis` al puerto 6379 del host de Docker. {% raw %} -```yaml +```yaml{:copy} name: Redis Service Example on: push @@ -110,7 +113,7 @@ Jobs: ``` {% endraw %} -### Further reading +### Leer más - "[Crear contenedores de servicios Redis](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)" - "[Crear contenedores de servicios PostgreSQL](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)" diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md index f73b47f9ae..1f4feb8a51 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Para comenzar rápidamente, puedes elegir la plantilla de Ant preconfigurada cua También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ El flujo de trabajo de inicio ejecutará el destino predeterminado especificado Si usas diferentes comandos para construir tu proyecto, o si deseas ejecutar un objetivo diferente, puedes especificarlos. Por ejemplo, es posible que desees ejecutar el destino `jar` que está configurado en tu archivo _build-ci.xml_. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es po Por lo general, Ant crea archivos de salida como JAR, EAR o WAR en el directorio `build/jar`. Puedes cargar los contenidos de ese directorio utilizando la acción `upload-Artifact`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md index c7701d50eb..3b7342ef86 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Para comenzar rápidamente, puedes elegir la plantilla de Gradle preconfigurada También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ El flujo de trabajo de inicio ejecutará la tarea `build` por defecto. En la con Si usas diferentes comandos para construir tu proyecto, o si quieres usar una tarea diferente, puedes especificarlo. Por ejemplo, es posible que desees ejecutar la tarea `package` que está configurada en tu archivo _ci.gradle_. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar tus dependencias en el caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu caché de paquete de Gradle local se almacenará en la infraestructura de acciones de GitHub. En las ejecuciones de flujo de trabajo futuras, la caché se restaurará para que las dependencias no necesiten ser descargadas desde los repositorios de paquetes remotos. Para obtener más información, consulta "Almacenar en caché las dependencias para agilizar los flujos de trabajo" y la acción [`cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. + # Restoring these files from a GitHub Actions cache might cause problems for future builds. + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -Este flujo de trabajo guardará los contenidos de tu caché de paquete Gradle local, que se encuentra en el directorio `.gradle/caches` del directorio de inicio del ejecutor. La clave de caché será el contenido con hash de los archivos de construcción de Gradle, por lo que los cambios en ellos invalidarán la memoria caché. +Este flujo de trabajo guardará el contenido del caché de tu paquete local de Gradle, el cual se ubica en los directorios `.gradle/caches` y `.gradle/wrapper` dek directorio de inicio del ejecutor. La clave del caché será el contenido cifrado de los archivos de compilación de gradle (incluyendo las propiedades del archivo de envoltorio (wrapper)), así que cualquier cambio que se realice sobre ellos invalidará el caché. ### Empaquetar datos de flujo de trabajo como artefactos @@ -122,7 +135,7 @@ Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es po Por lo general, Gradle creará archivos de salida como JAR, EAR o WAR en el directorio `build/libs`. Puedes cargar los contenidos de ese directorio utilizando la acción `upload-Artifact`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md index daf23c710a..2e6a7b9260 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Para comenzar rápidamente, puedes elegir la plantilla Maven preconfigurada cuan También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ El flujo de trabajo de inicio ejecutará el `paquete` destino por defecto. En la Si usas diferentes comandos para compilar tu proyecto, o si quieres usar un destino diferente, puedes especificarlos. Por ejemplo, es posible que desees ejecutar el objetivo `verify (verificar)` que está configurado en un archivo _pom-ci.xml_. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar tus dependencias en el caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu repositorio Maven local se almacenará en la infraestructura de acciones de GitHub. En las ejecuciones de flujo de trabajo futuras, el caché se restaurará para que las dependencias no necesiten descargarse desde los repositorios remotos de Maven. Para obtener más información, consulta "Almacenar en caché las dependencias para agilizar los flujos de trabajo" y la acción [`cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -122,7 +126,7 @@ Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es po Por lo general, Maven creará archivos de salida como tarros, orejas o guerras en el `Objetivo` Directorio. Para cargarlos como artefactos, puedes copiarlos en un nuevo directorio que contenga artefactos para cargar. Por ejemplo, puedes crear un directorio llamado `staging` (preparación). Luego puedes cargar los contenidos de ese directorio usando la acción `upload-artifact (cargar artefacto)`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/es-ES/content/actions/guides/building-and-testing-net.md b/translations/es-ES/content/actions/guides/building-and-testing-net.md index fd1643426e..62a982d039 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-net.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: Para utilizar una versión preinstalada de .NET Core SDK en un ejecutor hospedado en {% data variables.product.prodname_dotcom %}, utiliza la acción `setup-dotnet`. Esta acción encuentra una versión específica de .NET desde el caché de las herramientas en cada ejecutor y agrega los binarios necesarios a `PATH`. Estos cambios persistirán para el recordatorio del job. -La acción `setup-dotnet` es la forma recomendada de utilizar .NET con las {% data variables.product.prodname_actions %}, porque garantiza el comportamiento consistente a través de diversos ejecutores y diversas versiones de .NET. Si estás utilizando un ejecutor auto-hospedado, debes instalar .NET y agregarlo a `PATH`. Para obtener más información, consulta la acción [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). +La acción `setup-dotnet` es la forma recomendada de utilizar .NET con las {% data variables.product.prodname_actions %}, porque garantiza el comportamiento consistente a través de diversos ejecutores y diversas versiones de .NET. Si estás utilizando un ejecutor auto-hospedado, debes instalar .NET y agregarlo a `PATH`. Para obtener más información, consulta la acción [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk). #### Utilizar versiones múltiples de .NET diff --git a/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md b/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md index 4019bd6bf6..60ece468ed 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md @@ -9,6 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Nodo' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} @@ -77,7 +81,7 @@ La plantilla incluye una estrategia de matriz que crea y prueba tu código con c Cada trabajo puede acceder al valor definido en la matriz `node-version` por medio del contexto `matrix`. La acción `setup-node` utiliza el contexto como la entrada `node-version`. La acción `setup-node` configura cada trabajo con una versión diferente de Node.js antes de construir y probar código. Para obtener más información acerca de las estrategias y los contextos de la matriz, 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_idstrategymatrix) y "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". {% raw %} -```yaml +```yaml{:copy} strategy: matrix: node-version: [10.x, 12.x, 14.x, 15.x] @@ -93,7 +97,7 @@ steps: Como alternativa, puedes construir y probar con las versiones exactas de Node.js. -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -102,7 +106,7 @@ strategy: O bien, puedes construir y probar mediante una versión única de Node.js. {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -136,7 +140,7 @@ Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotc Este ejemplo instala las dependencias definidas en el archivo *package.json*. Para obtener más información, consulta [`Instalar npm`](https://docs.npmjs.com/cli/install). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -150,7 +154,7 @@ steps: Mediante `npm ci` se instalan las versiones en el archivo *package-lock.json* o *npm-shrinkwrap.json* y se evitan las actualizaciones al archivo de bloqueo. Usar `npm ci` generalmente es más rápido que ejecutar `npm install`. Para obtener más información, consulta [`npm ci`](https://docs.npmjs.com/cli/ci.html) e [Introducir `npm ci` para construcciones más rápidas y confiables](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)." {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -166,7 +170,7 @@ steps: Este ejemplo instala las dependencias definidas en el archivo *package.json*. Para obtener más información, consulta [`Instalar yarn`](https://yarnpkg.com/en/docs/cli/install). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -179,7 +183,7 @@ steps: De forma alternativa, puede pasar `--frozen-lockfile` para instalar las versiones en el archivo *yarn.lock* y evitar actualizaciones al archivo *yarn.lock*. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -201,7 +205,7 @@ En el siguiente ejemplo, el secreto `NPM_TOKEN` almacena el token de autenticaci Antes de instalar dependencias, utiliza la acción `setup-node` para crear el archivo *.npmrc*. La acción tiene dos parámetros de entrada. El parámetro `node-version` establece la versión de Node.js y el parámetro `registry-url` establece el registro predeterminado. Si tu registro de paquetes usa ámbitos, debes usar el parámetro `scope`. Para obtener más información, consulta [`npm-scope`](https://docs.npmjs.com/misc/scope). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -220,7 +224,7 @@ steps: El ejemplo anterior crea un archivo *.npmrc* con el siguiente contenido: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -231,7 +235,7 @@ always-auth=true Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar las dependencias en el caché utilizando una clave única y restaurar las dependencias cuando ejecutes flujos de trabajo subsecuentes, utilizando la acción `cache`. Para obtener más información, consulta "Almacenar en caché las dependencias para agilizar los flujos de trabajo" y la acción [`cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -256,7 +260,7 @@ steps: Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. Por ejemplo, si ejecutas `npm run build` para ejecutar pasos de construcción definidos en tu archivo *package.json* y `npm test` para ejecutar tu conjunto de pruebas, añadirías esos comandos en tu archivo de flujo de trabajo. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/es-ES/content/actions/guides/building-and-testing-powershell.md b/translations/es-ES/content/actions/guides/building-and-testing-powershell.md index 72691f5028..81da8547e6 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-powershell.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-powershell.md @@ -8,6 +8,9 @@ versions: authors: - potatoqualitee type: 'tutorial' +topics: + - 'CI' + - 'Powershell' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/guides/building-and-testing-python.md b/translations/es-ES/content/actions/guides/building-and-testing-python.md index ea0353313a..a185962500 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-python.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-python.md @@ -8,6 +8,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Te recomendamos que tengas una comprensión básica de Python, PyPy y pip. Para Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -94,7 +97,7 @@ Si estás utilizando un ejecutor auto-hospedado, puedes configurarlo para utiliz #### Usar múltiples versiones de Python {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -126,7 +129,7 @@ jobs: 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. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -158,7 +161,7 @@ Si especificas una versión de Python que no está disponible, `setup-python` fa 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)". {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -196,7 +199,7 @@ Los ejecutores alojados {% data variables.product.prodname_dotcom %} tienen inst 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". {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -213,7 +216,7 @@ steps: Después de actualizar `pip`, un siguiente paso típico es instalar dependencias desde *requirements.txt*. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -234,7 +237,7 @@ Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotc 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 [Ejemplos de almacenamiento en caché de Python](https://github.com/actions/cache/blob/main/examples.md#python---pip). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Setup Python @@ -271,7 +274,7 @@ Puedes usar los mismos comandos que usas de forma local para construir y probar 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/). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -295,7 +298,7 @@ steps: 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/). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -318,7 +321,7 @@ steps: 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/). {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -352,7 +355,7 @@ Puedes cargar artefactos para ver después de que se complete un flujo de trabaj 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). {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -365,26 +368,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} ``` {% endraw %} @@ -395,7 +398,7 @@ Puedes configurar tu flujo de trabajo para que publique tu paquete de Python en Puedes almacenar cualquier token de acceso o credenciales que se necesiten para publicar tu paquete utilizando secretos. En el siguiente ejemplo, se crea y se publica un paquete para PyPI mediante `twine` y `dist`. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." {% raw %} -```yaml +```yaml{:copy} name: Upload Python Package on: diff --git a/translations/es-ES/content/actions/guides/building-and-testing-ruby.md b/translations/es-ES/content/actions/guides/building-and-testing-ruby.md index 51dbfec857..f1295f4adf 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-ruby.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-ruby.md @@ -6,6 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Ruby' --- {% data reusables.actions.enterprise-beta %} @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -63,7 +63,7 @@ jobs: La forma más fácil de especificar una versión de Ruby es utilizando la acción `ruby/setup-ruby` que se proporciona en la organización de Ruby en GitHub. Esta acción agrega cualquier versión compatible con Ruby al `PATH` de cada ejecución de un job en un flujo de trabajo. Para obtener más información, consulta [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Se recomienda utilizar Ruby con GitHub Actions, ya sea mediante la acción `ruby/setup-ruby` de Ruby, o mediante la acción `actions/setup-ruby` de Github; debido a que esto garantiza el comportamiento consistente entre ejecutores y versiones distintas de Ruby. +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. La acción `setup-ruby` toma una versión de Ruby como entrada y la configura en el ejecutor. @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 3883e180dd..b23047a420 100644 --- a/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -10,6 +10,8 @@ redirect_from: versions: free-pro-team: '*' type: 'tutorial' +topics: + - 'Flujos de trabajo' --- ### Acerca de almacenar en caché las dependencias de flujo de trabajo @@ -68,7 +70,7 @@ Para más información, consulta [`actions/cache`](https://github.com/actions/ca Este ejemplo crea una nueva memoria caché cuando los paquetes en el archivo `package-lock.json` cambian o cuando cambia el sistema operativo del ejecutor. La clave de caché usa contextos y expresiones para generar una clave que incluye el sistema operativo del ejecutor y un hash SHA-256 del archivo `package-lock.json`. {% raw %} -```yaml +```yaml{:copy} name: Caching with npm on: push @@ -124,14 +126,14 @@ Una clave de caché puede incluir cualquiera de los contextos, funciones, litera Usar expresiones para crear una `key` te permite crear automáticamente una nueva caché cuando las dependencias han cambiado. Por ejemplo, puedes crear una `key` utilizando una expresión que calcule el hash de un archivo `package-lock.json` de npm. {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %} evalúa la expresión `hash "package-lock.json"` para obtener la última `key`. -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ Puedes proporcionar una lista de claves de restauración para usar cuando haya u #### Ejemplo usando múltiples claves de restauración {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | El ejecutor evalúa las expresiones, que resuelven estas `restore-keys`: {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md b/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md index 64d589fb3e..810fd76229 100644 --- a/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md @@ -10,6 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ También puede ser útil tener un conocimiento básico de YAML, la sintaxis para {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL service example on: push @@ -93,7 +96,7 @@ Jobs: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} jobs: # Etiqueta del trabajo del contenedor container-job: @@ -118,7 +121,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI - name: Check out repository code @@ -153,7 +156,7 @@ Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás as {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL Service Example on: push @@ -213,7 +216,7 @@ Jobs: El flujo de trabajo asigna el puerto 5432 del contenedor de servicios PostgreSQL al host de Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". -```yaml +```yaml{:copy} jobs: # Etiqueta del trabajo del ejecutador Runner-Job: @@ -243,7 +246,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI - name: Check out repository code @@ -279,7 +282,7 @@ Puedes modificar *client.js* para incluir cualquier operación de PostgreSQL que {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/es-ES/content/actions/guides/creating-redis-service-containers.md b/translations/es-ES/content/actions/guides/creating-redis-service-containers.md index 7a639ad341..dee5fee7fc 100644 --- a/translations/es-ES/content/actions/guides/creating-redis-service-containers.md +++ b/translations/es-ES/content/actions/guides/creating-redis-service-containers.md @@ -10,6 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ También puede ser útil tener una comprensión básica de YAML, la sintaxis par {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -89,7 +92,7 @@ jobs: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} jobs: # Etiqueta del trabajo del contenedor container-job: @@ -115,7 +118,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI - name: Check out repository code @@ -149,7 +152,7 @@ Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás as {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis runner example on: push @@ -207,7 +210,7 @@ jobs: El flujo de trabajo asigna el puerto 6379 en el contenedor del servicio Redis al host Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". -```yaml +```yaml{:copy} jobs: # Etiqueta del trabajo del ejecutor runner-job: @@ -235,7 +238,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Descarga una copia del código en tu repositorio antes de ejecutra pruebas de CI - name: Check out repository code @@ -271,7 +274,7 @@ Puedes modificar *client.js* para incluir cualquier operación de Redis que nece {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // Crea un nuevo cliente Redis diff --git a/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md index 8c1b0fbf2f..4853d9a459 100644 --- a/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md b/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md index 561d3ea09a..05b6c0f282 100644 --- a/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/es-ES/content/actions/guides/deploying-to-azure-app-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Azure App Service' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md index a0783e330a..719d3b74d2 100644 --- a/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/es-ES/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/guides/index.md b/translations/es-ES/content/actions/guides/index.md index 47d062d2b1..34a869a2b5 100644 --- a/translations/es-ES/content/actions/guides/index.md +++ b/translations/es-ES/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/es-ES/content/actions/guides/publishing-docker-images.md b/translations/es-ES/content/actions/guides/publishing-docker-images.md index 98fa73875c..a5c5976958 100644 --- a/translations/es-ES/content/actions/guides/publishing-docker-images.md +++ b/translations/es-ES/content/actions/guides/publishing-docker-images.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Embalaje' + - 'Publishing' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -55,7 +59,7 @@ Las opciones de `build-push-action` que se requieren para Docker Hub son: * `repository`: Tu repositorio de Docker hub en el formato `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -93,7 +97,7 @@ Las opciones de `build-push-action` requeridas para {% data variables.product.pr * `repository`: Debe configurarse en el formato `OWNER/REPOSITORY/IMAGE_NAME`. Por ejemplo, para una imagen nombrada como `octo-image` almacenada en {% data variables.product.prodname_dotcom %} en `http://github.com/octo-org/octo-repo`, la opción de `repository` debe configurarse como `octo-org/octo-repo/octo-image`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -126,7 +130,7 @@ En un solo flujo de trabajo, puedes publicar tu imagen de Docker en varios regis El siguiente flujo de trabajo de ejemplo utiliza los pasos de `build-push-action` de las secciones anteriores ("[Publicar imágenes en Docker Hub](#publishing-images-to-docker-hub)" y "[Publicar imágenes en {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para crear un solo flujo de trabajo que cargue ambos registros. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: diff --git a/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md index f3cb1567e4..ab01ed53d3 100644 --- a/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md @@ -8,6 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Embalaje' + - 'Publishing' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo Puedes definir un nuevo repositorio de Maven en el bloque de publicación de tu archivo _build.gradle_ que apunta al repositorio de tu paquete. Por ejemplo, si estás desplegando en el repositorio central de Maven a través del proyecto de alojamiento OSSRH, tu _build.gradle_ podría especificar un repositorio con el nombre `"OSSRH"`. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -67,7 +72,7 @@ En el paso de implementación, necesitarás establecer variables de entorno para {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -105,7 +110,7 @@ El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectu Por ejemplo, si tu organización se llama "octocat" y tu repositorio se llama "hello-world", entonces la configuración {% data variables.product.prodname_registry %} en _build.gradle_ tendría un aspecto similar al ejemplo a continuación. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -126,7 +131,7 @@ publishing { Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven al ejecutar el comando `gradle publish`. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -162,7 +167,7 @@ Por ejemplo, si implementas el repositorio central a través del proyecto de alo Si tu organización se llama "octocat" y tu repositorio se llama "hello-world", entonces la configuración {% data variables.product.prodname_registry %} en _build.gradle_ tendría un aspecto similar al ejemplo a continuación. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -191,7 +196,7 @@ publishing { Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven y {% data variables.product.prodname_registry %} al ejecutar el comando `gradle publish`. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md b/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md index 64f52a2e57..35da83ed51 100644 --- a/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md @@ -8,6 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Embalaje' + - 'Publishing' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +52,7 @@ En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción inst Por ejemplo, si estás desplegando en el repositorio central de Maven a través del proyecto de alojamiento OSSRH, tu _pom.xml_ podría especificar un repositorio de administración de distribución con el `id` de `ossrh`. {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ En el paso de implementación, necesitarás establecer las variables de entorno {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ Para un proyecto basado en Maven, puedes hacer uso de estas configuraciones crea Por ejemplo, si tu organización se llama "octocat", y tu repositorio se llama "hello-world", la configuración de {% data variables.product.prodname_registry %} en _pom.xml_ sería parecida al siguiente ejemplo. {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ Por ejemplo, si tu organización se llama "octocat", y tu repositorio se llama " Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en {% data variables.product.prodname_registry %} haciendo uso del _settings.xml_ generado automáticamente. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ Puedes publicar tus paquetes en el repositorio central de Maven y en el {% data Asegúrate de que tu archivo _pom.xml_ incluya un repositorio de administración de distribución para tu repositorio de {% data variables.product.prodname_dotcom %} y para tu proveedor de repositorios centrales de Maven. Por ejemplo, si implementas el repositorio central a través del proyecto de alojamiento de OSSRH, es posible que desees especificarlo en un repositorio de administración de distribución con la `id` establecida en `ossrh`, y que desees especificar el {% data variables.product.prodname_registry %} en un repositorio de administración de distribución con la `id` establecida en `github`. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md b/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md index fef802a477..ea7009bd5a 100644 --- a/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md @@ -9,6 +9,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Embalaje' + - 'Publishing' + - 'Nodo' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} @@ -54,7 +59,7 @@ Si estás publicando un paquete que incluye un prefijo de alcance, incluye el á Este ejemplo almacena el secreto `NPM_TOKEN` en la variable de entorno `NODE_AUTH_TOKEN`. Cuando la acción `setup-node` crea un archivo *.npmrc*, hace referencia al token de la variable de entorno `NODE_AUTH_TOKEN`. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -78,7 +83,7 @@ jobs: En el ejemplo anterior, la acción `setup-node` crea un archivo *.npmrc* en el ejecutor con el siguiente contenido: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -114,7 +119,7 @@ Si quieres publicar tu paquete en un repositorio diferente, debes utilizar un to Este ejemplo almacena el secreto `GITHUB_TOKEN` en la variable de entorno `NODE_AUTH_TOKEN`. Cuando la acción `setup-node` crea un archivo *.npmrc*, hace referencia al token de la variable de entorno `NODE_AUTH_TOKEN`. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -140,7 +145,7 @@ jobs: La acción `setup-node` crea un archivo *.npmrc* en el ejecutor. Cuando utilizas la entrada `scope` a la acción `setup-node`, el archivo *.npmrc* incluye el prefijo de alcance. Por defecto, la acción `setup-node` establece el ámbito en el archivo *.npmrc* en la cuenta que contiene ese archivo de flujo de trabajo. -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -151,7 +156,7 @@ always-auth=true Si usas el gestor de paquetes Yarn, puedes instalar y publicar paquetes mediante Yarn. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -167,7 +172,7 @@ jobs: node-version: '12.x' registry-url: 'https://registry.npmjs.org' # Defaults to the user or organization that owns the workflow file - scope: '@octocat' + scope: '@octocat' - run: yarn - run: yarn publish env: @@ -196,7 +201,7 @@ Cuando utilizas la entrada `scope` a la acción `setup-node`, la acción crea un Este flujo de trabajo llama a la acción `setup-node` dos veces. Cada vez que se ejecuta la acción `setup-node`, sobrescribe el archivo *.npmrc*. El archivo *.npmrc* hace referencia al token que te permite realizar operaciones autenticadas frente al registro del paquete desde la variable de entorno `NODE_AUTH_TOKEN`. El flujo de trabajo establece la variable de entorno `NODE_AUTH_TOKEN` cada vez que se ejecuta el comando `npm publish`, primero con un token para publicar en el (`NPM_TOKEN`) de npm y luego con un token para publicar en el {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`). {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: diff --git a/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 69e2647f9e..e5cd2dcc22 100644 --- a/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/es-ES/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -12,6 +12,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Flujos de trabajo' + - 'CI' --- {% data reusables.actions.enterprise-beta %} @@ -35,7 +38,7 @@ Una vez que se hace una inserción en tu repositorio, puedes seguir el estado y Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". -### Further reading +### Leer más - "[Acerca de la integración continua](/articles/about-continuous-integration)" - "[Administrar una ejecución de flujo de trabajo](/articles/managing-a-workflow-run)" diff --git a/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md index c50cc4c732..f053e7b283 100644 --- a/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/es-ES/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -12,6 +12,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Flujos de trabajo' --- {% data reusables.actions.enterprise-beta %} @@ -79,7 +81,7 @@ En este ejemplo se muestra cómo crear un flujo de trabajo para un proyecto Node 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. -```yaml +```yaml{:copy} name: Node CI on: [push] @@ -114,7 +116,7 @@ jobs: 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`: -``` +```yaml{:copy} - name: 'Upload Artifact' uses: actions/upload-artifact@v2 with: @@ -183,7 +185,7 @@ El job 3 muestra el resultado cargado en el trabajo anterior: La operación matemática completa realizada en este ejemplo de flujo de trabajo es `(3 + 7) x 9 = 90`. -```yaml +```yaml{:copy} name: Share data between jobs on: [push] @@ -246,7 +248,7 @@ La ejecución de flujo de trabajo archivará cualquier artefacto que haya genera {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Administrar la facturación de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)". 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 1f1f621acf..9b55022371 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,83 +1,83 @@ --- -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 versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: 'overview' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### 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 auto-alojados, consulta la sección "[Agregar ejecutores auto-alojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" y "[Usar ejecutores auto-alojados 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 estos 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 auto-hospedados:** -- 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 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 "[Sistemas operativos compatibles para ejecutores autoalojados](#supported-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 operating systems for self-hosted runners](#supported-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. -### 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 %} -### Sistemas operativos compatibles para ejecutores autoalojados +### Supported 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 - CentOS 7 - 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 @@ -90,23 +90,23 @@ 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 {% if enterpriseServerVersions contains currentVersion %} -### La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }} +### Supported actions on 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)." +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 jobs 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. {% if currentVersion == "free-pro-team@latest" %} -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. +You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below. ``` github.com @@ -115,25 +115,25 @@ api.github.com codeload.github.com ``` -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. Para obtener más información, consulta "[Administrar las direcciones IP permitidas para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" o "[Hacer cumplir los parámetros de seguridad en tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#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](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". {% else %} -Debes asegurarte de que la máquina tenga el acceso de red adecuado para comunicarse con {% data variables.product.product_location %}. +You must ensure that the machine has the appropriate network access to communicate with {% 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)." +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)." -### Seguridad de ejecutores autoalojdados con repositorios públicos +### Self-hosted runner security with public repositories {% data reusables.github-actions.self-hosted-runner-security %} -Este no es un problema con los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, ya que cada uno de ellos siempre constituye una máquina virtual limpia y aislada, la cual se destruya al final de la ejecución del job. +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. -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: +Untrusted workflows running on your self-hosted runner poses significant security risks for your machine and network environment, especially if your machine persists its environment between jobs. Some of the risks include: -* 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. +* 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. 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 2f2ab7e709..e8a3ec454b 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: Agregar ejecutores autoalojados -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 @@ -13,69 +13,68 @@ type: 'tutorial' {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -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 con los ejecutores auto-hospedados o sobre el uso de ejecutores auto-hospedados con un servidor proxy, consulta "[Acerca de los ejecutores auto-hospedados](/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)." {% 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 %} -### 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 auto-hospedado a un repositorio de usuario, debes ser el dueño del mismo. 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. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Debajo de "ejecutores auto-hospedados", da clic en **Agregar ejecutor**. +1. Under "Self-hosted runners," click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% 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. {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Debajo de "Ejecutores auto-hospedados", da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. +1. Under "Self-hosted runners," click **Add new**, then click **New runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% 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. {% if currentVersion == "free-pro-team@latest" %} -Para agregar un ejecutor auto-hospedado a una cuenta empresarial, debes ser un propietario de la empresa. +To add a self-hosted runner to an enterprise account, you must be an enterprise owner. {% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} -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. {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Da clic en la pestaña de **Ejecutores auto-hospedados**. -1. Da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. 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)". +1. Click the **Self-hosted runners** tab. +1. Click **Add new**, then click **New runner**. 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)." {% data reusables.github-actions.self-hosted-runner-configure %} {% 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/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 178ac602ff..d447826329 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -48,7 +48,7 @@ Cuando creas un grupo, debes elegir una política que defina qué repositorios t {% warning %} - **Warning** + **Advertencia** {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} @@ -80,7 +80,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones {% warning %} - **Warning** + **Advertencia** {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} 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 9595ed6424..36a11e07c2 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,10 +1,10 @@ --- -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 - - /Actions/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: free-pro-team: '*' enterprise-server: '>=2.22' @@ -15,51 +15,51 @@ defaultPlatform: linux {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### 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 %} {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.organizations.settings-sidebar-actions %} -1. Debajo de "Ejecutores auto-hospedados", puedes ver una lista de ejecutores registrados, incluyendo su nombre, etiquetas y estado. +1. Under "Self-hosted runners," you can view a list of registered runners, including the runner's name, labels, and status. - ![Lista de ejecutores](/assets/images/help/settings/actions-runner-list.png) + ![Runner list](/assets/images/help/settings/actions-runner-list.png) - 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 @@ -71,22 +71,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 @@ -96,25 +97,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 @@ -123,7 +125,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 @@ -142,34 +144,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' @@ -177,15 +179,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/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 26cdbe9268..a3a1aaa715 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -38,7 +38,7 @@ Si establecer variables de entorno no es práctico, puedes establecer las variab A continuación se muestra un ejemplo de configuración del proxy _.env_: -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 524f5f3130..5073a11286 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -64,8 +64,11 @@ Estas etiquetas operan acumulativamente, así que las etiquetas de un ejecutor a ### Precedencia de enrutamiento para los ejecutores auto-hospedados -Si utilizas ejecutores tanto a nivel de repositorio como a nivel de organización, {% data variables.product.prodname_dotcom %} sigue un orden de precedencia cuando enruta los jobs hacia los ejecutores auto-hospedados: +When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels: -1. Se procesan las etiquetas de `runs-on` del job. Entonces, {% data variables.product.prodname_dotcom %} intenta ubicar un ejecutor que coincida con los requisitos de la etiqueta: -2. El job se envía a un ejecutor a nivel de repositorio que coincida con las etiquetas del mismo. Si no hay un ejecutor a nivel de repositorio disponible (ya sea que esté ocupado, sin conexión, o no tenga etiquetas que coincidan): -3. El job se envía a un ejecutor de nivel organizacional que coincida con las etiquetas del mismo. Si hay un ejecutor de nivel organizacional disponible, el la solicitud del job falla con un error. +1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}. +2. The job is then sent to the first matching runner that is online and idle. + - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners. + - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners. + - If there are no matching runners at any level, the job will fail. + - If the job remains queued for more than 24 hours, the job will fail. diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md index 35c22cdf14..0df9dccc2d 100644 --- a/translations/es-ES/content/actions/index.md +++ b/translations/es-ES/content/actions/index.md @@ -10,34 +10,28 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: - - - title: Visualización de flujos de trabajo + - title: 'Ambientes, reglas de protección de ambiente y secretos de ambiente (beta)' + date: '2020-12-15' + href: 'https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/' + - title: Visualización de flujos de trabajo date: '2020-12-08' - href: https://github.blog/changelog/2020-12-08-github-actions-workflow-visualization/ - - - title: Eliminación de los comandos de set-env y add-path en el 16 de Noviembre - date: '09-11-2020' - href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Los flujos de trabajo más recientes de Ubuntu utilizarán Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 -product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU + href: 'https://github.blog/changelog/2020-12-08-github-actions-workflow-visualization/' + - title: Eliminación de los comandos de set-env y add-path en el 16 de Noviembre + date: '2020-11-09' + href: 'https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/' +product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU' redirect_from: - /articles/automating-your-workflow-with-github-actions/ - /articles/customizing-your-project-with-github-actions/ @@ -73,7 +67,7 @@ versions: {% render 'code-example-card' for actionsCodeExamples as example %} - +
{% octicon "search" width="24" %}
diff --git a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md index 70c581c1ea..bc1f97b701 100644 --- a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,7 +5,9 @@ intro: 'Las {% data variables.product.prodname_actions %} se diseñaron para ayu versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md index 33bcb0b94f..5d0497a18e 100644 --- a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} @@ -68,7 +70,7 @@ steps: #### Utilizar SHAs -Si necesitas utilizar un versionamiento más confiable, debes utilizar el valor de SHA asociado con la versión de la acción. Los SHA son inmutables y, por lo tanto, más confiables que las etiquetas o las ramas. Sin embargo, este acercamiento significa que no recibirás actualizaciones para una acción automáticamente, incluyendo las correcciones de errores y actualizaciones de seguridad. Este ejemplo apunta al SHA de una acción: +Si necesitas utilizar un versionamiento más confiable, debes utilizar el valor de SHA asociado con la versión de la acción. Los SHA son inmutables y, por lo tanto, más confiables que las etiquetas o las ramas. Sin embargo, este acercamiento significa que no recibirás actualizaciones para una acción automáticamente, incluyendo las correcciones de errores y actualizaciones de seguridad. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Debes utilizar el valor completo del SHA de la confirmación y no uno abreviado. {% endif %}Este ejemplo apunta al SHA de una acción: ```yaml steps: diff --git a/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md index a527a8e3a8..ee30fbd9ba 100644 --- a/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -9,7 +9,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -147,7 +149,7 @@ Para ayudarte a entender cómo se utiliza la sintaxis de YAML para crear un fluj ```
@@ -180,7 +182,7 @@ Para ayudarte a entender cómo se utiliza la sintaxis de YAML para crear un fluj ``` diff --git a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md index e73669ebcf..b52224e754 100644 --- a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Flujos de trabajo' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 14ff67e491..0880db6c5f 100644 --- a/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Azure Pipelines' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -62,16 +67,16 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: scripts - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in the default shell" - - bash: echo "This step runs in bash" - - pwsh: Write-Host "This step runs in PowerShell Core" - - task: PowerShell@2 - inputs: - script: Write-Host "This step runs in PowerShell" + - job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" ``` {% endraw %} @@ -82,13 +87,13 @@ jobs: scripts: runs-on: windows-latest steps: - - run: echo "This step runs in the default shell" - - run: echo "This step runs in bash" - shell: bash - - run: Write-Host "This step runs in PowerShell Core" - shell: pwsh - - run: Write-Host "This step runs in PowerShell" - shell: powershell + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell ``` {% endraw %} @@ -123,11 +128,11 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_command - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in CMD on Windows by default" + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} @@ -138,9 +143,9 @@ jobs: run_command: runs-on: windows-latest steps: - - run: echo "This step runs in PowerShell on Windows by default" - - run: echo "This step runs in CMD on Windows explicitly" - shell: cmd + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %} @@ -171,12 +176,12 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: conditional - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This step runs with str equals 'ABC' and num equals 123" - condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) + - job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) ``` {% endraw %} @@ -187,8 +192,8 @@ jobs: conditional: runs-on: ubuntu-latest steps: - - run: echo "This step runs with str equals 'ABC' and num equals 123" - if: ${{ env.str == 'ABC' && env.num == 123 }} + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %} @@ -217,29 +222,29 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: initial - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This job will be run first." -- job: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout2." -- job: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout1." -- job: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - steps: - - script: echo "This job will run after fanout1 and fanout2 have finished." + - job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." + - job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." + - job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." + - job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -250,22 +255,22 @@ jobs: initial: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." fanout1: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout2." - fanout2: + - run: echo "This job will run after the initial job, in parallel with fanout2." + fanout1: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout1." + - run: echo "This job will run after the initial job, in parallel with fanout2." fanin: runs-on: ubuntu-latest needs: [fanout1, fanout2] steps: - - run: echo "This job will run after fanout1 and fanout2 have finished." + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -294,15 +299,15 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_python - pool: - vmImage: 'ubuntu-latest' - steps: - - task: UsePythonVersion@0 - inputs: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} @@ -313,11 +318,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index cd1348761a..8e69fd2160 100644 --- a/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CircleCI' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -258,24 +263,24 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem - - name: Setup file system permissions - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} @@ -412,35 +417,35 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - - uses: actions/checkout@v2 - - name: Setup Ruby - uses: eregon/use-ruby-action@master - with: - ruby-version: ${{ matrix.ruby }} - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: vendor/bundle - key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - name: Install postgres headers - run: sudo apt-get install libpq-dev - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake - - name: Install appraisal - run: bundle exec appraisal install - - name: Run appraisal - run: bundle exec appraisal rake + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %} diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 8ddea2c002..456d4dcfab 100644 --- a/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -5,6 +5,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'GitLab' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,12 +340,12 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} @@ -371,7 +376,7 @@ IC/EC de GitLab script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -424,12 +429,12 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js tags: - docker ``` diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index 119a408105..dc7a742cb3 100644 --- a/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Jenkins' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ Jenkis te permite enviar compilaciones a un agente de compilación sencilla, o p De forma similar, las {% data variables.product.prodname_actions %} pueden enviar jobs a los ejecutores auto-hospedados u hospedados en {% data variables.product.prodname_dotcom %}, y puedes utilizar etiquetas para clasificar los ejecutores de acuerdo con diversos atributos. La siguiente tabla compara cómo se implementa el concepto de compilación distribuido tanto para Jenkins como para {% data variables.product.prodname_actions %}. | Jenkins | {% data variables.product.prodname_actions %} -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
[`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
[`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### Utilizar secciones para organizar mapas @@ -51,7 +56,6 @@ Jenkins divide sus Mapas Declarativos en varias secciones. De forma similar, las | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`Trabajos`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`pasos`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### Utilizar directivas Jenkins utiliza directivas para administrar los _Mapas Declarativos_. Estas directivas definen las características de tu flujo de trabajo y la manera en que se ejecuta. La tabla siguiente demuestra cómo dichas directivas mapean los conceptos en {% data variables.product.prodname_actions %}. @@ -69,7 +73,6 @@ Jenkins utiliza directivas para administrar los _Mapas Declarativos_. Estas dire | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs (entrada)`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### Utilizar etapas secuenciales #### Proceso paralelo de jobs @@ -114,23 +117,23 @@ Flujo de trabajo de {% data variables.product.prodname_actions %} @@ -150,25 +153,24 @@ Flujo de trabajo de {% data variables.product.prodname_actions %} @@ -188,30 +190,28 @@ Flujo de trabajo de {% data variables.product.prodname_actions %} @@ -231,26 +231,27 @@ Flujo de trabajo de {% data variables.product.prodname_actions %} diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 28fa760331..ddc3525316 100644 --- a/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Travis CI' + - 'Migration' + - 'CI' + - 'CD' --- ### Introducción @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -155,9 +160,9 @@ git: @@ -207,10 +212,10 @@ Cuando trabajas con lenguajes diferentes en {% data variables.product.prodname_a Por ejemplo: ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` ### Manejo de errores en {% data variables.product.prodname_actions %} @@ -275,11 +280,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} @@ -345,20 +350,20 @@ Flujo de trabajo de {% data variables.product.prodname_actions %} @@ -378,24 +383,24 @@ Flujo de trabajo de {% data variables.product.prodname_actions %} diff --git a/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 2d6cf97b8c..9343f0cf3d 100644 --- a/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'resumen' +type: overview +topics: + - Seguridad --- {% data reusables.actions.enterprise-beta %} @@ -20,7 +22,7 @@ Esta guía explica cómo configurar el fortalecimiento de seguridad para ciertas ### Utilizar secretos -Los valores sensibles jamás deben almacenarse como texto simple e archivos de flujo de trabajo, sino más bien como secretos. Los [Secretos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) pueden configurarse a nivel de la organización% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositorio o ambiente{% else %} o repositorio{% endif %}, y permitirte almacenar información sensible en {% data variables.product.product_name %}. +Los valores sensibles jamás deben almacenarse como texto simple e archivos de flujo de trabajo, sino más bien como secretos. Los [Secretos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) pueden configurarse a nivel de la organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositorio o ambiente{% else %} o repositorio{% endif %}, y permitirte almacenar información sensible en {% data variables.product.product_name %}. Los secretos utilizan [Cajas selladas de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) de manera que se cifran antes de llegar a {% data variables.product.product_name %}. Esto ocurre cuando el secreto se emite [utilizando la IU](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) o a través de la [API de REST](/rest/reference/actions#secrets). Este cifrado del lado del cliente ayuda a minimizar los riesgos relacionados con el registro accidental (por ejemplo, bitácoras de exepción y de solicitud, entre otras) dentro de la infraestructura de {% data variables.product.product_name %}. Una vez que se carga el secreto, {% data variables.product.product_name %} puede entonces descifrarlo para que se pueda inyectar en el tiempo de ejecución del flujo de trabajo. @@ -54,11 +56,13 @@ Esto significa que el poner en riesgo una sola acción dentro de un flujo de tra Fijar una acción a un SHA de confirmación de longitud completa es actualmente la única forma de utilizar una acción como un lanzamiento inmutable. Fijar las acciones a un SHA en particular ayuda a mitigar el riesgo de que un actor malinencionado agregue una puerta trasera al repositorio de la acción, ya que necesitarían generar una colisión de SHA-1 para una carga útil vlálida de un objeto de Git. + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **Advertencia:** La versión corta del SHA de confirmación no es segura y jamás debería utilizarse para especificar la referencia de Git de una acción. Debido a cómo funcionan las redes de los repositorios, cualquier usuario puede bifurcar el repositorio y cargar una confirmación creada a éste, la cual colisione con el SHA corto. Esto causa que fallen los clones subsecuentes a ese SHA, debido a que se convierte en una confirmación ambigua. Como resultado, cualquier flujo de trabajo que utilice el SHA acortado fallará de inmediato. {% endwarning %} + {% endif %} * **Audita el código fuente de la acción** @@ -113,7 +117,7 @@ Puedes utilizar la bitácora de auditoría para monitorear las tareas administra Por ejemplo, puedes utilizar la bitácora de auditoría para rastrear el evento `action:org.update_actions_secret`, el cual rastrea los cambios a los secretos de la organización: ![Entradas de la bitácora de auditoría](/assets/images/help/repository/audit-log-entries.png) -Las siguientes tablas describen los eventos de {% data variables.product.prodname_actions %} que puedes encontrar en la bitácora de auditoría. Para obtener más información sobre cómo utilizar la bitácora de auditoría, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". +Las siguientes tablas describen los eventos de {% data variables.product.prodname_actions %} que puedes encontrar en la bitácora de auditoría. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." #### Eventos para la administración de secretos | Acción | Descripción | @@ -140,4 +144,4 @@ Las siguientes tablas describen los eventos de {% data variables.product.prodnam | `action:org.runner_group_removed` | Se activa cuando un administrador de la organización elimina el grupo de ejecutores auto-hospedados. | | `action:org.runner_group_renamed` | Se activa cuando un administrador de la organización renombra un grupo de ejecutores auto-hospedados. | | `action:org.runner_group_runners_added` | Se activa cuando un administrador de la organización [agrega 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). | -| `action:org.runner_group_runners_removed` | Se activa cuando un administrador de la organización elimina un ejecutor auto-hospedado de un grupo. | +| `action:org.runner_group_runners_removed` | Se activa cuando un administrador de la organización elimina un ejecutor auto-hospedado de un grupo. | diff --git a/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index 550b6a0475..3d4669a405 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///workflows//badge.svg Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabajo con el nombre "Greet Everyone". El `PROPIETARIO` del repositorio es la organización `actions` y el nombre del `REPOSITORIO` es `hello-world`. -``` +```markdown ![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabaj Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabajo con la ruta de archivo `.github/workflows/main.yml`. El `PROPIETARIO` del repositorio es la organización `actions` y el nombre del `REPOSITORIO` es `hello-world`. -``` +```markdown ![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabaj Este ejemplo de Markdown añade un distintivo de estado para una rama con el nombre `feature-1`. -``` +```markdown ![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ Este ejemplo de Markdown añade un distintivo de estado para una rama con el nom Este ejemplo de Markdown agrega un distintivo que muestra el estado de las ejecuciones de flujo de trabajo activadas por el evento `pull_request`. -``` +```markdown ![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` 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 147233f0e6..753dda70cb 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,6 +1,6 @@ --- -title: Ejecutar un flujo de trabajo manualmente -intro: 'Cuando se configura un flujo de trabajo para ejecutarse en un evento de `workflow_dispatch`, puedes ejecutarlo utilizando la API de REST desde la pestaña de acciones en {% data variables.product.prodname_dotcom %}.' +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 REST API or from the Actions tab on {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -10,24 +10,27 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### 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 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. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". -### Ejecutar un flujo de trabajo en {% data variables.product.prodname_dotcom %} +### Running a workflow on {% data variables.product.prodname_dotcom %} -Para activar el evento `workflow_dispatch` en {% data variables.product.prodname_dotcom %}, tu flujo de trabajo deberá estar en la rama predeterminada. Sigue estos pasos para activar una ejecución de flujo de trabajo manualmente. +To trigger the `workflow_dispatch` event on {% data variables.product.prodname_dotcom %}, your workflow must be in the default branch. Follow these steps to manually trigger a workflow run. -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% 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. Selecciona la rama en donde el flujo de trabajo se ejecutará y teclea los parámetros de entrada que éste utiliza. 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. Select the branch where the workflow will run and type the input parameters used by the workflow. Click **Run workflow**. +![actions manually run workflow](/assets/images/actions-manually-run-workflow.png) -### 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 6b8a94b79b..9602d5bf9a 100644 --- a/translations/es-ES/content/actions/quickstart.md +++ b/translations/es-ES/content/actions/quickstart.md @@ -1,25 +1,28 @@ --- -title: Guía de inicio rápido para GitHub Actions -intro: 'Agrega un flujo de trabajo de {% data variables.product.prodname_actions %} a un repositorio existente en 5 minutos o menos.' -allowTitleToDifferFromFilename: verdadero +title: Quickstart for GitHub Actions +intro: 'Add a {% data variables.product.prodname_actions %} workflow to an existing repository in 5 minutes or less.' +allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Introducción +### Introduction -Solo necesitas tener 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 limpia varios lenguajes de programación utilizando la [Acción de Super-Linter de {% data variables.product.prodname_dotcom %}](https://github.com/github/super-linter). El flujo de trabajo utiliza Super-Linter para validar tu código fuente cada que se sube una confirmación a tu repositorio. +You only need an existing {% 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 lints multiple coding languages using the [{% data variables.product.prodname_dotcom %} Super-Linter action](https://github.com/github/super-linter). The workflow uses Super-Linter to validate your source code every time a new commit is pushed to your repository. -### Crear tu primer flujo de trabajo +### Creating your first workflow -1. Desde tu repositorio en {% data variables.product.prodname_dotcom %}, crea un archivo nuevo en el directorio `.github/workflows` que se llame `superlinter.yml`. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." -2. Copia el siguiente contenido de YAML en el arcvhivo `superlinter.yml`. **Nota:** Si tu rama predeterminada no es `main`, actualiza el valor de `DEFAULT_BRANCH` para que refleje el nombre de la rama predeterminada de tu repositorio. +1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `superlinter.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +2. Copy the following YAML contents into the `superlinter.yml` file. **Note:** If your default branch is not `main`, update the value of `DEFAULT_BRANCH` to match your repository's default branch name. {% raw %} ```yaml{:copy} name: Super-Linter @@ -49,45 +52,48 @@ Solo necesitas tener un repositorio de {% data variables.product.prodname_dotcom GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` {% endraw %} -3. Para ejecutar tu flujo de trabajo, desplázate al 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/commit-workflow-file.png) +3. To run your workflow, 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/commit-workflow-file.png) -El confirmar el flujo de trabajo en tu repositorio activará el evento de `push` y ejecutará tu flujo de trabajo. +Committing the workflow file 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 %} {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -1. Debajo de **Jobs** o en la gráfica de visualización, da clic en el job de **Limpiar base de código**. ![Limpiar el job de código base](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +1. Under **Jobs** or in the visualization graph, click the **Lint code base** job. + ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) {% else %} -1. En la barra lateral, da clic en el job de **Lint code base**. ![Limpiar el job de código base](/assets/images/help/repository/superlinter-lint-code-base-job.png) +1. In the left sidebar, click the **Lint code base** job. + ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### Más plantillas de flujo de trabajo +### More workflow templates {% data reusables.actions.workflow-template-overview %} -### Pasos siguientes +### Next steps -El flujo de trabajo de super-linter que acabas de agregar se ejecuta en cualquier momento en que se suba cópdigo a tu repositorio para ayudarte a detectar los errores y las coincidencias del mismo. Pero esto es solo el inicio de lo que puedes hacer con {% data variables.product.prodname_actions %}. Tu repositorio puede contener varios flujos de trabajo que activen jobs diferentes basándose en eventos diferentes. {% 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 %}: +The super-linter workflow you just added runs any time code is pushed to your repository to help you spot errors and inconsistencies in your code. But, this is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% 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 -- "[Guías](/actions/guides)" para casos de uso específico y ejemplos -- [github/super-linter](https://github.com/github/super-linter) para obtener más detalles sobre la configuración de la acción de Super-Linter +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial +- "[Guides](/actions/guides)" for specific uses cases and examples +- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action diff --git a/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md b/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md index caf4d1320f..75390d7901 100644 --- a/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md @@ -86,8 +86,8 @@ Para obtener información sobre los puntos finales de la API a los que {% data v | contenidos | lectura/escritura | lectura | | implementaciones | lectura/escritura | lectura | | propuestas | lectura/escritura | lectura | -| metadata | lectura | lectura | -| packages | 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 | diff --git a/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 9a918bacdd..01759a2874 100644 --- a/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -186,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -348,7 +348,7 @@ El valor para `array` puede ser una matriz o una cadena. Todos los valores en `a `join(github.event.issue.labels.*.name, ', ')` puede devolver 'bug, help wanted' -#### toJson +#### toJSON `toJSON(value)` @@ -358,13 +358,13 @@ Devuelve una representación JSON con formato mejorado de `valor`. Puedes usar e `toJSON(job)` puede devolver `{ "status": "Success" }` -#### fromJson +#### fromJSON `fromJSON(value)` -Devuelve un objeto de JSON para `value`. Puedes utilizar esta función para proporcionar un objeto de JSON como una expresión evaluada. +Devuelve un objeto de JSON o un tipo de datos de JSON para `value`. Puedes utilizar esta función para proporcionar un objeto JSON como una expresión evaluada o para convertir variables de ambiente desde una secuencia. -##### Ejemplo +##### Ejemplo de devolver un objeto JSON Este flujo de trabajo configura una matriz de JSON en un job, y lo pasa al siguiente job utilizando un resultado y `fromJSON`. @@ -384,12 +384,33 @@ jobs: needs: job1 runs-on: ubuntu-latest strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} steps: - run: build ``` {% endraw %} +##### Ejemplo de devolver un tipo de datos JSON + +Este flujo de trabajo utiliza `fromJSON` para convertir las variables de ambiente de una secuencia a un número entero o Booleano. + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... +``` +{% endraw %} + #### hashFiles `hashFiles(path)` diff --git a/translations/es-ES/content/actions/reference/environment-variables.md b/translations/es-ES/content/actions/reference/environment-variables.md index 18a21c10f4..b368bc6cc2 100644 --- a/translations/es-ES/content/actions/reference/environment-variables.md +++ b/translations/es-ES/content/actions/reference/environment-variables.md @@ -21,15 +21,25 @@ versions: 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)". ```yaml -steps: - - name: Hello world - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +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. + +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. + Tambièn puedes utilizar el archivo de ambiente de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV`{% else %} el comando de flujo de trabajo `set-env`{% endif %} para configurar una variable de ambiente que pueda utilizar los siguientes pasos en un flujo de trabajo. El {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}archivo de ambiente{% else %} comando `set-env`{% endif %} puede utilizarse directamente a travès de una acciòn o como un comando de shell en un archivo de trabajo utilizando la palabra clave `run`. 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)." ### Variables de entorno predeterminadas diff --git a/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md b/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md index f35d099103..5835465624 100644 --- a/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md @@ -224,15 +224,15 @@ on: create ``` -#### `eliminar` +#### `delete` Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, lo que activa el evento `delete`. Para obtener más información sobre la API de REST, consulta la sección "[Borrar una referencia](/rest/reference/git#delete-a-reference)". {% data reusables.github-actions.branch-requirement %} -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------- | ------------------ | --------------------------------------------- | ---------------- | -| [`eliminar`](/webhooks/event-payloads/#delete) | n/a | Última confirmación en la rama predeterminada | Rama por defecto | +| 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 | Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `delete`. diff --git a/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md index cc043d46a4..9b6d20001d 100644 --- a/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md @@ -95,7 +95,7 @@ La lista de direcciones IP permitidas de {% data variables.product.prodname_acti | Directorio | Variable de entorno | Descripción | | --------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `hogar` | `HOME` | Contiene datos relacionados con el usuario. Por ejemplo, este directorio podría contener las credenciales de un intento de inicio de sesió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. | diff --git a/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md index bd59ab6f52..4c06f20058 100644 --- a/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/es-ES/content/actions/reference/usage-limits-billing-and-administration.md @@ -40,7 +40,7 @@ el uso de {% data variables.product.prodname_actions %} cuando se utilizan ejecu | Plan de GitHub | Jobs simultáneos totales | Jobs simultáneos de macOS máximos | | -------------- | ------------------------ | --------------------------------- | - | Free | 20 | 5 | + | Gratis | 20 | 5 | | Pro | 40 | 5 | | Team | 60 | 5 | | Empresa | 180 | 50 | diff --git a/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md index 5bcecfdcae..7544c18012 100644 --- a/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md @@ -83,7 +83,7 @@ La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles | `core.setFailed` | Utilizada como un atajo para `::error` y `exit 1` | | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | -| `core.startGroup` | `group` | +| `core.startGroup` | `grupo` | | `core.warning` | `warning file` | {% if currentVersion ver_lt "enterprise-server@2.23" %} @@ -257,7 +257,7 @@ Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos tempor **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: -``` +```yaml steps: - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` @@ -272,11 +272,19 @@ Crea o actualiza una variable de entorno para todas las acciones que se ejecutan #### Ejemplo -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` - -Cuando ejecutes `$action_state` en un paso subsecuente ahora se devolverá `yellow` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} #### Secuencias de línea múltiple @@ -291,7 +299,7 @@ Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la s ##### Ejemplo En este ejemplo, utilizamos `EOF` como delimitador y configuramos la variable de ambiente `JSON_RESPONSE` para el valor de la respuesta de curl. -``` +```yaml steps: - name: Set the value id: step_one diff --git a/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md index 552de34ad4..813b9cb7c5 100644 --- a/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ El nombre de tu flujo de trabajo. {% data variables.product.prodname_dotcom %} m ### `on` -**Obligatorio** El nombre del evento {% 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)". +**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)". {% data reusables.github-actions.actions-on-examples %} @@ -286,7 +286,7 @@ En este ejemplo, `job3` utiliza la expresión condicional `always()` para que si ### `jobs..runs-on` -**Obligatorio** El tipo de máquina en la que se ejecuta el trabajo. La máquina puede ser un ejecutor alojado {% data variables.product.prodname_dotcom %} o un ejecutor autoalojado. +**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. {% data reusables.actions.enterprise-github-hosted-runners %} @@ -299,6 +299,7 @@ Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} di {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} ##### Ejemplo @@ -518,7 +519,7 @@ Las acciones son archivos JavaScript o contenedores Docker. Si la acción que es ```yaml steps: # Reference a specific commit - - uses: actions/setup-node@74bc508 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e # Reference the major version of a release - uses: actions/setup-node@v1 # Reference a minor version of a release @@ -700,12 +701,24 @@ steps: 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}`. +Por ejemplo: + +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +The command used, `perl` in this example, must be installed on the runner. 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)." + #### Códigos de salida y preferencia de acción de error Para palabras clave shell incorporadas, brindamos los siguientes valores predeterminados accionados por los ejecutores alojados {% data variables.product.prodname_dotcom %}. Deberías usar estos lineamientos al ejecutar scripts shell. - `bash`/`sh`: - - Comportamiento a prueba de fallos utilizando `set -e o 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. + - 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. @@ -1186,7 +1199,7 @@ Para obtener más información acerca de la sintaxis de filtro de ramas, de etiq | `'**'` | 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]+` | Encuentra todas las etiquetas de versión semántica con las versiones principales 1 o 2 | `v1.10.1`

`v2.0.0` | +| `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 diff --git a/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md index 840380259f..b3f9be5788 100644 --- a/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md @@ -21,7 +21,7 @@ Para aprender cómo configurar tanto la autenticación como el aprovisionamiento {% endif %} -### Further reading +### Leer más - [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio de OASIS - [Sistema para la Administración de Identidad entre Dominios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) en el sitio web de IETF diff --git a/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md index 91943c3c72..abc163cb5d 100644 --- a/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md +++ b/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md @@ -43,7 +43,7 @@ Cuando un usuario acepta la invitación, puede utilizar su nombre de usuario y c {% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} {% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} -### Further reading +### Leer más - "[Usar LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap)" - "[Usar SAML](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-saml)" diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md index 60dc277c78..b93ea66846 100644 --- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md +++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance.md @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/ - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md index abc663192c..a6a2a048bc 100644 --- a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md +++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md @@ -1,7 +1,7 @@ --- title: Configurar la autenticación y el aprovisionamiento con tu proveedor de identidad -intro: Puedes utilizar un proveedor de identidad (IdP) que sea compatible tanto con el inicio de sesión único (SSO) de SAML y con el Sistema para la Administración de Identidad entre Dominios (SCIM) para configurar la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_location %}. -mapTopic: verdadero +intro: 'Puedes utilizar un proveedor de identidad (IdP) que sea compatible tanto con el inicio de sesión único (SSO) de SAML y con el Sistema para la Administración de Identidad entre Dominios (SCIM) para configurar la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_location %}.' +mapTopic: true versions: github-ae: '*' --- diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md index 98864a299f..7e1d074b11 100644 --- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md +++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md @@ -1,8 +1,8 @@ --- title: Administrar la identidad y el acceso para tu empresa shortTitle: Administrar el acceso y la identidad -intro: Puedes adminsitrar centralmente el acceso y las cuentas en {% data variables.product.product_location %}. -mapTopic: verdadero +intro: 'Puedes adminsitrar centralmente el acceso y las cuentas en {% data variables.product.product_location %}.' +mapTopic: true versions: github-ae: '*' --- diff --git a/translations/es-ES/content/admin/authentication/using-cas.md b/translations/es-ES/content/admin/authentication/using-cas.md index d045dfb798..2c6c6b95a5 100644 --- a/translations/es-ES/content/admin/authentication/using-cas.md +++ b/translations/es-ES/content/admin/authentication/using-cas.md @@ -27,7 +27,7 @@ Están disponibles los siguientes atributos. | Nombre del atributo | Type | Descripción | | ------------------- | --------- | ------------------------------------------------------------------------ | -| `username` | Requerido | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | +| `nombre de usuario` | Requerido | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | ### Configurar CAS {% warning %} diff --git a/translations/es-ES/content/admin/authentication/using-ldap.md b/translations/es-ES/content/admin/authentication/using-ldap.md index 9c8ae4de21..c66e161932 100644 --- a/translations/es-ES/content/admin/authentication/using-ldap.md +++ b/translations/es-ES/content/admin/authentication/using-ldap.md @@ -156,7 +156,7 @@ Si no se desea divulgar dicha información, su empresa u organización debe rest El {% data variables.product.prodname_ghe_server %} admite estas clases de objetos del grupo LDAP. Los grupos se pueden anidar. -- `group` +- `grupo` - `groupOfNames` - `groupOfUniqueNames` - `posixGroup` diff --git a/translations/es-ES/content/admin/authentication/using-saml.md b/translations/es-ES/content/admin/authentication/using-saml.md index 86cfa84660..9ce7104c78 100644 --- a/translations/es-ES/content/admin/authentication/using-saml.md +++ b/translations/es-ES/content/admin/authentication/using-saml.md @@ -1,39 +1,39 @@ --- -title: Usar SAML +title: Using 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 -intro: 'SAML es un estándar basado en XML para autenticación y autorización. {% data variables.product.prodname_ghe_server %} puede actuar como un proveedor de servicios (SP) con tu proveedor de identidad (IdP) SAML interno.' +intro: 'SAML is an XML-based standard for authentication and authorization. {% data variables.product.prodname_ghe_server %} can act as a service provider (SP) with your internal SAML identity provider (IdP).' versions: enterprise-server: '*' --- {% data reusables.enterprise_user_management.built-in-authentication %} -### Servicios SAML admitidos +### Supported SAML services {% data reusables.saml.saml-supported-idps %} {% data reusables.saml.saml-single-logout-not-supported %} -### Consideraciones sobre el nombre de usuario con SAML +### Username considerations with SAML -Cada nombre de usuario {% data variables.product.prodname_ghe_server %} lo determina una de las siguientes aserciones en la respuesta SAML, ordenadas por prioridad: +Each {% data variables.product.prodname_ghe_server %} username is determined by one of the following assertions in the SAML response, ordered by priority: -- El atributo de nombre de usuario personalizado, si está definido y si hay uno. -- Una aserción `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`, si hay una. -- Una aserción `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` assertion, si hay una. -- El elemento `NameID`. +- The custom username attribute, if defined and present +- An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` assertion, if present +- An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` assertion, if present +- The `NameID` element -Se requiere el elemento `NameID`, incluso si hay otros atributos. +The `NameID` element is required even if other attributes are present. -Se crea un mapeo entre la `NameID` y el nombre de usuario de {% data variables.product.prodname_ghe_server %}, para que la `NameID` deba ser persistente, única, y no estar sujeta a cambios para el ciclo de vida del usuario. +A mapping is created between the `NameID` and the {% data variables.product.prodname_ghe_server %} username, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. {% note %} -**Nota**: Si la `NameID` de un usuario sí cambia en el IdP, el usuario verá un mensaje de error cuando intente ingresar en tu instancia de {% data variables.product.prodname_ghe_server %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}Para restablecer el acceso del usuario, necesitarás actualizar el mapeo de `NameID` de la cuenta de usuario. Para obtener más información, consulta la sección "[Actualizar la `NameID`](#updating-a-users-saml-nameid) de SAML de un usuario.{% else %} Para obtener más información, consulta "[Error: 'Another user already owns the account'](#error-another-user-already-owns-the-account)".{% endif %} +**Note**: If the `NameID` for a user does change on the IdP, the user will see an error message when they try to sign in to your {% data variables.product.prodname_ghe_server %} instance. {% if currentVersion ver_gt "enterprise-server@2.21" %}To restore the user's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."{% else %} For more information, see "[Error: 'Another user already owns the account'](#error-another-user-already-owns-the-account)."{% endif %} {% endnote %} @@ -44,75 +44,88 @@ Se crea un mapeo entre la `NameID` y el nombre de usuario de {% data variables.p {% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -### Metadatos SAML +### SAML metadata -Los metadatos del provedor de servicios de tu instancia de {% data variables.product.prodname_ghe_server %} se encuentran disponibles en `http(s)://[hostname]/saml/metadata`. +Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. -Para configurar tu proveedor de identidad de forma manual, la URL del Servicio de consumidor de aserciones (ACS) es `http(s)://[hostname]/saml/consume`. Esta usa el enlace `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. +To configure your identity provider manually, the Assertion Consumer Service (ACS) URL is `http(s)://[hostname]/saml/consume`. It uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. -### Atributos de SAML +### SAML attributes -Estos atributos están disponibles. Puedes modificar el nombre del atributo en [Consola de administración](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), a excepción del atributo `administrator`. +These attributes are available. You can change the attribute names in the [management console](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), with the exception of the `administrator` attribute. -| Nombre de atributo predeterminado | Type | Descripción | -| --------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ID del nombre` | Requerido | Un identificador de usuario persistente. Se puede usar cualquier formato de identificador de nombre persistente. El elemento `NameID` se usará para un nombre de usuario {% data variables.product.prodname_ghe_server %}, a menos que se proporcione una de las aserciones alternativas. | -| `administrator` | Opcional | Cuando el valor es "true", el usuario será promovido automáticamente como un administrador. Cualquier otro valor o un valor no existente degradará al usuario a una cuenta de usuario normal. | -| `username` | Opcional | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | -| `nombre_completo` | Opcional | El nombre del usuario que se muestra en su página de perfil. Los usuarios pueden cambiar sus nombres después del aprovisionamiento. | -| `emails` | Opcional | Las direcciones de correo electrónico para el usuario. Se puede especificar más de una. | -| `claves_públicas` | Opcional | Las claves SSH públicas para el usuario. Se puede especificar más de una. | -| `gpg_keys` | Opcional | Las claves GPG para el usuario. Se puede especificar más de una. | +| Default attribute name | Type | Description | +|-----------------|----------|-------------| +| `NameID` | Required | A persistent user identifier. Any persistent name identifier format may be used. The `NameID` element will be used for a {% data variables.product.prodname_ghe_server %} username unless one of the alternative assertions is provided. | +| `administrator` | Optional | When the value is 'true', the user will automatically be promoted as an administrator. Any other value or a non-existent value will demote the user to a normal user account. | +| `username` | Optional | The {% data variables.product.prodname_ghe_server %} username. | +| `full_name` | Optional | The name of the user displayed on their profile page. Users may change their names after provisioning. | +| `emails` | Optional | The email addresses for the user. More than one can be specified. | +| `public_keys` | Optional | The public SSH keys for the user. More than one can be specified. | +| `gpg_keys` | Optional | The GPG keys for the user. More than one can be specified. | -### Configurar parámetros SAML +### Configuring SAML settings {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. Selecciona **SAML**. ![Autenticación SAML](/assets/images/enterprise/management-console/auth-select-saml.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación Autenticación integrada SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -5. Opcionalmente, para activar el SSO de respuesta no solicitada, selecciona **IdP initiated SSO**. Por defecto, {% data variables.product.prodname_ghe_server %} responderá a una solicitud iniciada por un proveedor de identidad (IdP) no solicitada con una `AuthnRequest` de vuelta al IdP. ![SSO del IdP SAML](/assets/images/enterprise/management-console/saml-idp-sso.png) +3. Select **SAML**. +![SAML authentication](/assets/images/enterprise/management-console/auth-select-saml.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select SAML built-in authentication checkbox](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +5. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP. +![SAML idP SSO](/assets/images/enterprise/management-console/saml-idp-sso.png) {% tip %} - **Nota**: Te recomendamos mantener este valor **sin seleccionar**. Debes activar esta función **solo** en el caso inusual que tu implementación SAML no admita el SSO iniciado del proveedor de servicios y que {% data variables.contact.enterprise_support %} lo aconseje. + **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. {% endtip %} -5. Selecciona **Disable administrator demotion/promotion (Desactivar la degradación/promoción del administrador)** si **no** quieres que tu proveedor de SAML determine los derechos del administrador para los usuarios en {% data variables.product.product_location %}. ![Configuración de administración para desactivar SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -6. En el campo **URL de inicio de sesión único**, escribe la HTTP o el extremo HTTPS en tu IdP para las solicitudes de inicio de sesión único. Este valor lo provee la configuración de tu IdP. Si el host solo está disponible desde tu red interna, es posible que sea necesario [configurar {% data variables.product.product_location %} para usar los servidores de nombres internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticación SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png) -7. También puedes escribir tu nombre de emisor de SAML en el campo **Emisor**. Esto verifica la autenticidad de los mensajes enviados a {% data variables.product.product_location %}. ![Emisor SAML](/assets/images/enterprise/management-console/saml-issuer.png) -8. En los menúes desplegables **Método de firma** y **Método de resumen**, elige el algoritmo de hash que usa tu emisor SAML para verificar la integridad de las respuestas desde {% data variables.product.product_location %}. Especifica el formato con el menú desplegable **Formato de identificador de nombre**. ![Método SAML](/assets/images/enterprise/management-console/saml-method.png) -9. Dentro de **Verification certificate (Certificado de comprobación)**, haz clic en **Choose File (Elegir archivo)** y elige un certificado para validar las respuestas SAML desde el IdP. ![Autenticación SAML](/assets/images/enterprise/management-console/saml-verification-cert.png) -10. Modifica los nombres de atributo de SAML para hacerlos coincidir con tu IdP, si es necesario, o acepta los nombres predeterminados. ![Nombres de atributo de SAML](/assets/images/enterprise/management-console/saml-attributes.png) +5. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.product.product_location %}. +![SAML disable admin config](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) +6. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.product.product_location %} to use internal nameservers](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). +![SAML authentication](/assets/images/enterprise/management-console/saml-single-sign-url.png) +7. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.product.product_location %}. +![SAML issuer](/assets/images/enterprise/management-console/saml-issuer.png) +8. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.product.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. +![SAML method](/assets/images/enterprise/management-console/saml-method.png) +9. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP. +![SAML authentication](/assets/images/enterprise/management-console/saml-verification-cert.png) +10. Modify the SAML attribute names to match your IdP if needed, or accept the default names. + ![SAML attribute names](/assets/images/enterprise/management-console/saml-attributes.png) {% if currentVersion ver_gt "enterprise-server@2.21" %} -### Revocar acceso a {{ site.data.variables.product.product_location_enterprise }} +### Updating a user's SAML `NameID` {% data reusables.enterprise_site_admin_settings.access-settings %} -2. Selecciona **SAML**. ![Elemento de "Todos los usuarios" en la barra lateral en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/all-users.png) -3. En la lista de usuarios, da clic en el nombre de usuario del cual te gustaría actualizar el mapeo de la `NameID`. ![Nombre de usuario en la lista de cuentas de usuario de la instancia](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) +2. In the left sidebar, click **All users**. + !["All users" sidebar item in site administrator settings](/assets/images/enterprise/site-admin-settings/all-users.png) +3. In the list of users, click the username you'd like to update the `NameID` mapping for. + ![Username in list of instance user accounts](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) {% data reusables.enterprise_site_admin_settings.security-tab %} -5. Dentro de **Verification certificate (Certificado de comprobación)**, haz clic en **Choose File (Elegir archivo)** y elige un certificado para validar las respuestas SAML desde el IdP. ![Botón de "Editar" debajo de "Autenticación de SAML" y a la derecha de "Actualizar la NameID de SAML"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) -6. En el campo de "NameID", teclea la `NameID` nueva para el usuario. ![Campo de "NameID" en diálogo modal con el valor de NameID ingresado](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) -7. Da clic en **Actualizar NameID**. ![Botón de "Actualizar NameID" debajo del valor actualizado de la NameID dentro del modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) +5. To the right of "Update SAML NameID", click **Edit** . + !["Edit" button under "SAML authentication" and to the right of "Update SAML NameID"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) +6. In the "NameID" field, type the new `NameID` for the user. + !["NameID" field in modal dialog with NameID typed](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) +7. Click **Update NameID**. + !["Update NameID" button under updated NameID value within modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) {% endif %} -### Revocar acceso a {% data variables.product.product_location %} +### Revoking access to {% data variables.product.product_location %} -Si eliminas un usuario desde tu proveedor de identidad, también debes suspenderlos de forma manual. De lo contrario, seguirán estando disponibles para autenticarse usando los tokens de acceso o las claves SSH. Para obtener más información, consulta "[Suspender y anular suspensión de usuarios](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". +If you remove a user from your identity provider, you must also manually suspend them. Otherwise, they'll continue to be able to authenticate using access tokens or SSH keys. For more information, see "[Suspending and unsuspending users](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". -### Requisitos para los mensajes de respuesta +### Response message requirements -El mensaje de respuesta debe cumplir con los siguientes requisitos: +The response message must fulfill the following requirements: -- Se debe proporcionar el elemento `` en el documento de respuesta raíz y empatar la URL ACS únicamente cuando dicho documento se firme. Si la aserción está firmada, ésta se ignorará. -- Siempre deberá proporcionarse el elemento `` como parte del elemento ``. Siempre deberá proporcionarse el elemento `` como parte del elemento ``. Ésta es la URL para la instancia de {% data variables.product.prodname_ghe_server %}, tal como `https://ghe.corp.example.com`. -- Cada aserción en la respuesta **debe** estar protegida por una firma digital. Esto se puede lograr firmando cada elemento `` individual o firmando el elemento ``. -- Un elemento `` se debe proporcionar como parte del elemento ``. Se puede usar cualquier formato de identificador de nombre persistente. -- El atributo `Recipient` debe estar presente y establecido en la URL ACS. Por ejemplo: +- The `` element must be provided on the root response document and match the ACS URL only when the root response document is signed. If the assertion is signed, it will be ignored. +- The `` element must always be provided as part of the `` element. It must match the `EntityId` for {% data variables.product.prodname_ghe_server %}. This is the URL to the {% data variables.product.prodname_ghe_server %} instance, such as `https://ghe.corp.example.com`. +- Each assertion in the response **must** be protected by a digital signature. This can be accomplished by signing each individual `` element or by signing the `` element. +- A `` element must be provided as part of the `` element. Any persistent name identifier format may be used. +- The `Recipient` attribute must be present and set to the ACS URL. For example: ```xml @@ -132,50 +145,50 @@ El mensaje de respuesta debe cumplir con los siguientes requisitos: ``` -### Autenticación SAML +### Troubleshooting SAML authentication -de entidad del {% data variables.product.prodname_ghe_server %}, se presentará el siguiente mensaje de error en el registro de autenticación: Para obtener más información sobre los requisitos de respuesta de SAML, consulta la sección "[Requisitos de mensaje de respuesta](#response-message-requirements)". +{% data variables.product.prodname_ghe_server %} logs error messages for failed SAML authentication in the authentication log at _/var/log/github/auth.log_. For more information about SAML response requirements, see "[Response message requirements](#response-message-requirements)." #### Error: "Another user already owns the account" -Cuando un usuario ingresa en {% data variables.product.prodname_ghe_server %} por primera vez con la autenticación de SAML, {% data variables.product.prodname_ghe_server %} crea una cuenta de usuario en la instancia y mapea la `NameID` de SAML hacia la cuenta. +When a user signs in to {% data variables.product.prodname_ghe_server %} for the first time with SAML authentication, {% data variables.product.prodname_ghe_server %} creates a user account on the instance and maps the SAML `NameID` to the account. -Cuando el usuario vuelve a ingresar, {% data variables.product.prodname_ghe_server %} compara el mapeo de la `NameID` de la cuenta con la respuesta del IdP. Si la `NameID` en la respuesta del IdP ya no empata con la `NameID` que {% data variables.product.prodname_ghe_server %} espera para el usuario, el inicio de sesión fallará. El usuario verá el siguiente mensaje. +When the user signs in again, {% data variables.product.prodname_ghe_server %} compares the account's `NameID` mapping to the IdP's response. If the `NameID` in the IdP's response no longer matches the `NameID` that {% data variables.product.prodname_ghe_server %} expects for the user, the sign-in will fail. The user will see the following message. > Another user already owns the account. Please have your administrator check the authentication log. -Este mensaje habitualmente indica que el nombre de usuario o dirección de correo electrónico cambió en el IdP. {% if currentVersion ver_gt "enterprise-server@2.21" %}Asegúrate de que el mapeo de la `NameID` para la cuenta de usuario en {% data variables.product.prodname_ghe_server %} concuerde con la `NameID` del usuario en tu IdP. Para obtener más información, consulta la sección "[Actualizar la `NameID` de SAML de un usuario](#updating-a-users-saml-nameid)".{% else %}Para encontrar ayuda para actualizar el mapeo de la `NameID`, contacta a {% data variables.contact.contact_ent_support %}.{% endif %} +The message typically indicates that the person's username or email address has changed on the IdP. {% if currentVersion ver_gt "enterprise-server@2.21" %}Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."{% else %}For help updating the `NameID` mapping, contact {% data variables.contact.contact_ent_support %}.{% endif %} -#### Si la respuesta SAML no está firmada o la firma no coincide con los contenidos, se presentará el siguiente mensaje de error en el registro de autenticación: +#### Error: Recipient in SAML response was blank or not valid -Si el `Recipient` no coincide con la URL ACS, se presentará el siguiente mensaje de error en el registro de autenticación: +If the `Recipient` does not match the ACS URL for your {% data variables.product.prodname_ghe_server %} instance, one of the following two error messages will appear in the authentication log when a user attempts to authenticate. ``` -El destinatario en la respuesta SAML no debe estar en blanco. +Recipient in the SAML response must not be blank. ``` ``` -El destinatario en la respuesta SAML no era válido. +Recipient in the SAML response was not valid. ``` -Asegúrate de que configuraste el valor para `Recipient` en tu IdP como la URL de ACS completa para tu instancia de {% data variables.product.prodname_ghe_server %}. Por ejemplo, `https://ghe.corp.example.com/saml/consume`. +Ensure that you set the value for `Recipient` on your IdP to the full ACS URL for your {% data variables.product.prodname_ghe_server %} instance. For example, `https://ghe.corp.example.com/saml/consume`. #### Error: "SAML Response is not signed or has been modified" -Si tu IdP no firma la respuesta de SAML, o si la firma no empata con el contenido, se mostrará el siguiente mensaje de error en la bitácora de autenticación. +If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log. ``` SAML Response is not signed or has been modified. ``` -Asegúrate de haber configurado aserciones firmadas para la aplicación de {% data variables.product.prodname_ghe_server %} en tu IdP. +Ensure that you configure signed assertions for the {% data variables.product.prodname_ghe_server %} application on your IdP. #### Error: "Audience is invalid" or "No assertion found" -Si la respuesta del IdP carece o tiene un valor incorrecto para `Audience`, se mostrará el siguiente mensaje de error en la bitácora de autenticación. +If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log. ```shell -La audiencia es no válida. Audience attribute does not match https://YOUR-INSTANCE-URL +Audience is invalid. Audience attribute does not match https://YOUR-INSTANCE-URL ``` -Asegúrate de haber configurado el valor para `Audience` en tu IdP como la `EntityId` para tu instancia de {% data variables.product.prodname_ghe_server %}, la cual es la URL completa para tu instancia de {% data variables.product.prodname_ghe_server %}. Por ejemplo, `https://ghe.corp.example.com`. +Ensure that you set the value for `Audience` on your IdP to the `EntityId` for your {% data variables.product.prodname_ghe_server %} instance, which is the full URL to your {% data variables.product.prodname_ghe_server %} instance. For example, `https://ghe.corp.example.com`. diff --git a/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md b/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md index b1b42b95f5..198d472956 100644 --- a/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md +++ b/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md @@ -25,7 +25,7 @@ Posteriormente, puedes utilizar el panel de administrador de sitio y la configur Todas las empresas se configuran con aislamiento de subdominios y compatibilidad con TLS 1.2 y superior únicamente para el tráfico cifrado. {% endif %} -### Further reading +### Leer más - "[Administrar usuarios, organizaciones y repositorios](/admin/user-management)" - "[Configurar políticas para tu empresa](/admin/policies)" diff --git a/translations/es-ES/content/admin/configuration/command-line-utilities.md b/translations/es-ES/content/admin/configuration/command-line-utilities.md index 2a56337bca..f9b12ddb7c 100644 --- a/translations/es-ES/content/admin/configuration/command-line-utilities.md +++ b/translations/es-ES/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` Te permite encontrar el uuid de tu nodo en `cluster.conf`. -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -545,8 +545,8 @@ estado ghe-dpages ``` Para evacuar un servicio de almacenamiento {% data variables.product.prodname_pages %} antes de evacuar un nodo de agrupación: -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -571,16 +571,16 @@ ruta ghe-spokes Para evacuar los servicios de almacenamiento en un nodo de la agrupación: -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage Esta utilidad te permite evacuar todos los servicios de almacenamiento antes de evacuar un nodo de agrupación. -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md b/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md index 6bf41924b8..ead25545a5 100644 --- a/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md +++ b/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md @@ -2,7 +2,7 @@ title: Configurar las características de seguridad avanzada shortTitle: Configurar la seguridad avanzada intro: 'Puedes habilitar o inhabilitar las características de {% data variables.product.prodname_advanced_security %}, tales como el {% data variables.product.prodname_code_scanning %}, en tu instancia.' -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/configuration/configuring-advanced-security-features versions: diff --git a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index 9f74d87958..c1ada5ff63 100644 --- a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -66,6 +66,6 @@ Para descongelar tu empresa después de que hayas borrado tu llave de cifrado, c curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Further reading +### Leer más - "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST diff --git a/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md b/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md index be89739f5b..d0c2cef8a3 100644 --- a/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ Para obtener más información sobre contactar a soporte, consulta la sección " - En el desplegable **Autenticación**, elige el tipo de cifrado usado por tu servidor SMTP. - En el campo **Dirección de correo electrónico sin respuesta**, escribe la dirección de correo electrónico para usar en los campos De y Para para todos los correos electrónicos para notificaciones. - {% note %} - - **Nota:** si seleccionas la casilla de verificación **Send from author (Enviar desde autor)** en el webhook del correo electrónico **Services (Servicios)** de un repositorio, el correo electrónico de salida para ese repositorio se enviará desde el autor y no desde el correo electrónico sin respuesta. Para obtener más información, consulta la sección "[Acerca de las notificaciones por correo electrónico para las cargas a tu repositorio](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)". - - {% endnote %} - 6. Si quieres descartar todos los correos electrónicos entrantes que estén dirigidos al correo electrónico sin respuesta, selecciona **Descartar correo electrónico dirigido a la dirección de correo electrónico sin respuesta**. ![Casilla de verificación para descartar los correos electrónicos dirigidos a la dirección de correo electrónico sin respuesta](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. En **Soporte**, elige un tipo de enlace para ofrecer un soporte adicional a tus usuarios: - **Correo electrónico:** Una dirección de correo electrónico interna. @@ -129,7 +123,7 @@ Este registro muestra que el aparato: Si necesitas verificar que tu correo electrónico entrante está funcionando, hay dos archivos de registro que puedes examinar en tu instancia: para verificar */var/log/mail.log* y */var/log/mail-replies/metroplex.log*. -*/var/log/mail.log* verifies that messages are reaching your server. Este es un ejemplo de una respuesta de correo electrónico exitosa: +*/var/log/mail.log* verifica que los mensajes estén alcanzando tu servidor. Este es un ejemplo de una respuesta de correo electrónico exitosa: ``` Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250] @@ -143,7 +137,7 @@ Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asm Ten en cuenta que el cliente primero se conecta; luego, la cola se vuelve activa. Entonces, el mensaje es entregado, el cliente es retirado de la cola y la sesión se desconecta. -*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. Este es un ejemplo de un mensaje exitoso: +*/var/log/mail-replies/metroplex.log* muestra si los correos electrónicos entrantes están siendo procesados para agregarse a las propuestas y a las solicitudes de extracción como respuestas. Este es un ejemplo de un mensaje exitoso: ``` [2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing @@ -155,7 +149,7 @@ Notarás que `metroplex` captura el mensaje entrante, lo procesa y luego desplaz #### Verificar los parámetros de tu DNS -Para procesar los correos electrónicos entrantes de manera adecuada, debes configurar un Registro A válido (o CNAME), así como un Registro MX. Para obtener más información, consulta "[Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." +Para procesar los correos electrónicos entrantes de manera adecuada, debes configurar un Registro A válido (o CNAME), así como un Registro MX. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." #### Controlar los parámetros de AWS Security Group o firewall diff --git a/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md index 0cbc689b8b..b0b97e90ba 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md @@ -59,7 +59,7 @@ Si se inhabilita el aislamiento de subdominios para tu empresa, también deberá {% endif %} {% if enterpriseServerVersions contains currentVersion %} -### Further reading +### Leer más - "[Habilitar el modo privado](/admin/configuration/enabling-private-mode)" {% endif %} diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings.md b/translations/es-ES/content/admin/configuration/configuring-network-settings.md index 4d78e874e7..ede47665c0 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings.md @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings - /enterprise/admin/configuration/configuring-network-settings intro: 'Configura {% data variables.product.prodname_ghe_server %} con los servidores de nombres y el nombre del host DNS necesarios para tu red. También puedes configurar un servidor proxy o reglas de firewall. Debes permitir el acceso a determinados puertos con fines administrativos y relacionados con el usuario.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md index f41abea7c8..6295cbc243 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise.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." +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.' redirect_from: - /enterprise/admin/guides/installation/basic-configuration/ - /enterprise/admin/guides/installation/administrative-tools/ @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/guides/installation/configuring-the-github-enterprise-appliance/ - /enterprise/admin/installation/configuring-the-github-enterprise-server-appliance - /enterprise/admin/configuration/configuring-your-enterprise -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md index 5cd302b850..3930fd411c 100644 --- a/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md +++ b/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md @@ -25,6 +25,6 @@ Buscar a través de las API REST y GraphQL no incluye {% data variables.product. 5. En "Los usuarios pueden buscar {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) 6. De manera opcional, en "Users can search private repositories on (Los usuarios pueden buscar repositorios privados en) {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda de repositorios privados en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) -### Further reading +### Leer más - "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)" diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md index d02f27528e..7b17b3da21 100644 --- a/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -1,7 +1,7 @@ --- title: Administrar conexiones entre el servidor de GitHub Enterprise y GitHub Enterprise Cloud intro: 'Con {% data variables.product.prodname_github_connect %}, puedes compartir determinadas características y datos entre {% data variables.product.product_location_enterprise %} y la cuenta de tu organización u emprendimiento {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ diff --git a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md index 3a605dfe70..6e24da8a36 100644 --- a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md +++ b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md @@ -1,5 +1,5 @@ --- -title: Tablero de administración del sitio +title: Site admin dashboard intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}' redirect_from: - /enterprise/admin/articles/site-admin-dashboard/ @@ -9,196 +9,197 @@ versions: enterprise-server: '*' --- -Para acceder al tablero, en la esquina superior derecha de cualquier página, haz clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +To access the dashboard, in the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}. +![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% if currentVersion ver_gt "enterprise-server@2.21" %} ### Search -Aquí puedes iniciar la {{ site.data.variables.enterprise.management_console }} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. +Refer to this section of the site admin dashboard to search for users and repositories, and to query the [audit log](#audit-log). {% else %} -### Información de la licencia & buscar +### License info & search -Consulta esta sección del tablero de administración del sitio para controlar tu licencia {% data variables.product.prodname_enterprise %} actual, para buscar usuarios y repositorios y para consultar el [registro de auditoría](#audit-log). +Refer to this section of the site admin dashboard to check your current {% data variables.product.prodname_enterprise %} license; to search for users and repositories; and to query the [audit log](#audit-log). {% endif %} ### {% data variables.enterprise.management_console %} -Aquí puedes iniciar la {% data variables.enterprise.management_console %} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. +Here you can launch the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL. -### Explorar +### Explore -Los datos para la [página de tendencia][] de GitHub se calculan en lapsos de tiempo diarios, semanales y mensuales para ambos repositorios y programadores. Puedes ver cuándo estos datos fueron almacenados en caché por última vez y poner en cola las tareas nuevas de cálculo de tendencia desde la sección **Explore (Explorar)**. +Data for GitHub's [trending page][] is calculated into daily, weekly, and monthly time spans for both repositories and developers. You can see when this data was last cached and queue up new trending calculation jobs from the **Explore** section. -### Registro de auditoría + [trending page]: https://github.com/blog/1585-explore-what-is-trending-on-github -{% data variables.product.prodname_enterprise %} mantiene un registro continuo de las acciones auditadas que puedes consultar. +### Audit log -Por defecto, el registro de auditoría te muestra una lista de todas las acciones auditadas en orden cronológico reverso. Puedes filtrar esta lista al ingresar pares de valores clave en el casillero de texto de **Query (Consulta)** y después hacer clic en **Search (Buscar)**, como se explicó en "[Buscar el registro de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)." +{% data variables.product.prodname_enterprise %} keeps a running log of audited actions that you can query. -Para obtener más información acerca de las bitácoras de auditoria en general, consulta "[Bitácoras de Auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". Para encontrar una lista completa de las acciones auditadas, consulta la sección "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". +By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)." -### Informes +For more information on audit logging in general, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." For a full list of audited actions, see "[Audited actions](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)." -Si necesitas obtener información sobre los usuarios, organizaciones y repositorios en {% data variables.product.product_location %}, comúnmente extraerías datos JSON a través de la [API de GitHub](/rest). Lamentablemente, es posible que la API no proporcione todos los datos que deseas y se requiera algo de conocimiento técnico para usarla. Este tablero de administración del sitio ofrece una sección de **Reports (Informes)** como una alternativa, haciendo que sea fácil descargar informes CSV con la mayoría de la información que probablemente necesites para los usuarios, las organizaciones y los repositorios. +### Reports -Específicamente, puedes descargar informes CSV que enumeren a +If you need to get information on the users, organizations, and repositories in {% data variables.product.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories. -- todos los usuarios -- todos los usuarios que han estado activos dentro del último mes -- todos los usuarios que han estado inactivos durante un mes o más -- todos los usuarios que han sido suspendidos -- todas las organizaciones -- todos los repositorios +Specifically, you can download CSV reports that list -También puedes acceder a estos informes mediante programación a través de una autenticación estándar de HTTP con una cuenta de administrador del sitio. Debes utilizar un token de acceso personal con alcance de `site_admin`. 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)". +- all users +- all users who have been active within the last month +- all users who have been inactive for one month or more +- all users who have been suspended +- all organizations +- all repositories -Por ejemplo, así es como descargarías el informe "todos los usuarios" utilizando cURL: +You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a personal access token with the `site_admin` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." + +For example, here is how you would download the "all users" report using cURL: ```shell curl -L -u username:token http(s)://hostname/stafftools/reports/all_users.csv ``` -Para acceder a otros informes mediante programación, reemplaza `all_users` con `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, o `all_repositories`. +To access the other reports programmatically, replace `all_users` with `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, or `all_repositories`. {% note %} -**Nota:** La solicitud `curl` inicial devolverá una respuesta 202 HTTP si no hay informes en caché disponibles; se generará un informe en segundo plano. Puedes enviar una segunda solicitud para descargar el informe. Puedes utilizar una contraseña o un token de OAuth con el alcance `site_admin` en lugar de la contraseña. +**Note:** The initial `curl` request will return a 202 HTTP response if there are no cached reports available; a report will be generated in the background. You can send a second request to download the report. You can use a password or an OAuth token with the `site_admin` scope in place of a password. {% endnote %} -#### Informes del usuario +#### User reports -| Clave | Descripción | -| ------------------------:| --------------------------------------------------------------------------------- | -| `created_at (creado en)` | Cuándo fue creada la cuenta de usuario (como una marca de tiempo ISO 8601) | -| `id` | ID de la cuenta para el usuario o la organización | -| `login` | Nombre de inicio de sesión de la cuenta | -| `email` | Dirección principal de correo electrónico de la cuenta | -| `role` | Si la cuenta es de un usuario administrador o de un usuario común | -| `suspended?` | Si la cuenta ha sido suspendida | -| `last_logged_ip` | La dirección IP más reciente que se registró en la cuenta | -| `repos` | Cantidad de repositorios que posee la cuenta | -| `ssh_keys` | Cantidad de claves SSH registradas en la cuenta | -| `org_memberships` | Cantidad de organizaciones a las que pertenece la cuenta | -| `dormant?` | Si la cuenta está inactiva | -| `last_active` | Cuándo la cuenta estuvo activa por última vez (como una marca de tiempo ISO 8601) | -| `raw_login` | Información de inicio de sesión sin procesar (en formato JSON) | -| `2fa_enabled?` | Si el usuario ha habilitado autenticación de dos factores | +Key | Description +-----------------:| ------------------------------------------------------------ +`created_at` | When the user account was created (as an ISO 8601 timestamp) +`id` | Account ID for the user or organization +`login` | Account's login name +`email` | Account's primary email address +`role` | Whether the account is an admin or an ordinary user +`suspended?` | Whether the account has been suspended +`last_logged_ip` | Most recent IP address to log into the account +`repos` | Number of repositories owned by the account +`ssh_keys` | Number of SSH keys registered to the account +`org_memberships` | Number of organizations to which the account belongs +`dormant?` | Whether the account is dormant +`last_active` | When the account was last active (as an ISO 8601 timestamp) +`raw_login` | Raw login information (in JSON format) +`2fa_enabled?` | Whether the user has enabled two-factor authentication -#### Informes de la organización +#### Organization reports -| Clave | Descripción | -| ------------------------:| ------------------------------------------------------------ | -| `id` | ID de la organización | -| `created_at (creado en)` | Cuándo se creó la organización | -| `login` | Nombre de inicio de sesión de la organización | -| `email` | Dirección principal de correo electrónico de la organización | -| `owners` | Cantidad de propietarios de la organización | -| `members` | Cantidad de miembros de la organización | -| `equipos` | Cantidad de equipos de la organización | -| `repos` | Cantidad de repositorios de la organización | -| `2fa_required?` | Si la organización requiere autenticación de dos factores | +Key | Description +--------------:| ------------------------------------ +`id` | Organization ID +`created_at` | When the organization was created +`login` | Organization's login name +`email` | Organization's primary email address +`owners` | Number of organization owners +`members` | Number of organization members +`teams` | Number of organization teams +`repos` | Number of organization repositories +`2fa_required?`| Whether the organization requires two-factor authentication -#### Informes del repositorio +#### Repository reports -| Clave | Descripción | -| ------------------------:| ------------------------------------------------------------------ | -| `created_at (creado en)` | Cuándo fue creado el repositorio | -| `owner_id` | ID del propietario del repositorio | -| `owner_type` | Si el repositorio es propiedad de un usuario o de una organización | -| `owner_name` | Nombre del propietario del repositorio | -| `id` | ID del repositorio | -| `name (nombre)` | Nombre del repositorio | -| `visibility` | Si el repositorio es público o privado | -| `readable_size` | El tamaño del repositorio en un formato legible | -| `raw_size` | Tamaño del repositorio como un número | -| `collaborators` | Cantidad de colaboradores del repositorio | -| `fork?` | Si el repositorio es una bifurcación | -| `deleted?` | Si el repositorio ha sido borrado | +Key | Description +---------------:| ------------------------------------------------------------ +`created_at` | When the repository was created +`owner_id` | ID of the repository's owner +`owner_type` | Whether the repository is owned by a user or an organization +`owner_name` | Name of the repository's owner +`id` | Repository ID +`name` | Repository name +`visibility` | Whether the repository is public or private +`readable_size` | Repository's size in a human-readable format +`raw_size` | Repository's size as a number +`collaborators` | Number of repository collaborators +`fork?` | Whether the repository is a fork +`deleted?` | Whether the repository has been deleted -### Indexar +### Indexing -Las funciones de [búsqueda de código][] de GitHub son propulsadas por [ElasticSearch][]. Esta sección del tablero de administración del sitio muestra el estado actual de tu agrupación de ElasticSearch y brinda diversas herramientas para controlar el comportamiento de búsqueda e indexación. Estas herramientas están separadas en las siguientes tres categorías. +GitHub's [code search][] features are powered by [ElasticSearch][]. This section of the site admin dashboard shows you the current status of your ElasticSearch cluster and provides you with several tools to control the behavior of searching and indexing. These tools are split into the following three categories. -#### Búsqueda de código + [Code Search]: https://github.com/blog/1381-a-whole-new-code-search + [ElasticSearch]: http://www.elasticsearch.org/ -Esto te permite habilitar o deshabilitar tanto las operaciones de búsqueda como de indexación en el código fuente. +#### Code search -#### Reparación del índice de búsqueda de código +This allows you to enable or disable both search and index operations on source code. -Esto controla cómo se repara el índice de búsqueda de código. Puedes +#### Code search index repair -- habilitar o inhabilitar tareas de reparación de índices -- comenzar una nueva tarea de reparación de índice -- restablecer todos los estados de reparación de índices +This controls how the code search index is repaired. You can -{% data variables.product.prodname_enterprise %} utiliza tareas de reparación para compaginar el estado del índice de búsqueda con los datos almacenados en una base de datos (propuestas, solicitudes de extracción, repositorios y usuarios) y los datos almacenados en los repositorios de Git (código fuente). Esto sucede cuando +- enable or disable index repair jobs +- start a new index repair job +- reset all index repair state -- se crea un nuevo índice de búsqueda; -- faltan datos que se deben reponer; o -- los datos de búsqueda antiguos deben ser actualizados. +{% data variables.product.prodname_enterprise %} uses repair jobs to reconcile the state of the search index with data stored in a database (issues, pull requests, repositories, and users) and data stored in Git repositories (source code). This happens when -En otras palabras, las tareas de reparación se inician según se necesiten y se ejecutan en segundo plano, no están programados por los administradores del sitio de ningún modo. +- a new search index is created; +- missing data needs to be backfilled; or +- old search data needs to be updated. -Además, las tareas de reparación utilizan una "compensación de reparación" para la paralelización. Esto es una compensación dentro de la tabla de base de datos para el registro que se está compaginando. Múltiples tareas en segundo plano pueden sincronizar el trabajo en base a esta compensación. +In other words, repair jobs are started as needed and run in the background—they are not scheduled by site admins in any way. -Una barra de progreso muestra el estado actual de la tarea de reparación a través de todos sus trabajadores en segundo plano. Es la diferencia de porcentaje de la compensación de reparación con el ID de registro más alto en la base de datos. No te preocupes sobre el valor que se muestra en la barra de progreso después de que una tarea de reparación se haya completado: ya que muestra la diferencia entre la compensación de reparación y el ID del registro más alto en la base de datos, disminuirá a medida que se agreguen más repositorios a {% data variables.product.product_location %} incluso aquellos repositorios que están de hecho indexados. +Furthermore, repair jobs use a "repair offset" for parallelization. This is an offset into the database table for the record being reconciled. Multiple background jobs can synchronize work based on this offset. -Puedes comenzar una nueva tarea de reparación de índice de búsqueda de código en cualquier momento. Utilizará una CPU única ya que compagina el índice de búsqueda con la base de datos y los datos del repositorio de Git. Para minimizar los efectos que esto tendrá en el desempeño de I/O y reducir las posibilidades de que las operaciones queden inactivas, trata de ejecutar una tarea de reparación durante las horas valle en primer lugar. Controla las cargas promedio de tu sistema y el uso de tu CPU con una herramienta como `top`; si no notas cambios significativos, debería ser seguro ejecutar una tarea de reparación de índice también durante las horas pico. +A progress bar shows the current status of a repair job across all of its background workers. It is the percentage difference of the repair offset with the highest record ID in the database. Don't worry about the value shown in the progress bar after a repair job has completed: because it shows the difference between the repair offset and the highest record ID in the database, it will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed. -#### Reparación de índice de propuestas +You can start a new code-search index repair job at any time. It will use a single CPU as it reconciles the search index with database and Git repository data. To minimize the effects this will have on I/O performance and reduce the chances of operations timing out, try to run a repair job during off-peak hours first. Monitor your system's load averages and CPU usage with a utility like `top`; if you don't notice any significant changes, it should be safe to run an index repair job during peak hours, as well. -Esto controla de qué manera se repara el [índice de propuestas][]. Puedes +#### Issues index repair -- habilitar o inhabilitar tareas de reparación de índices -- comenzar una nueva tarea de reparación de índice -- restablecer todos los estados de reparación de índices +This controls how the [Issues][] index is repaired. You can + + [Issues]: https://github.com/blog/831-issues-2-0-the-next-generation + +- enable or disable index repair jobs +- start a new index repair job +- reset all index repair state {% if currentVersion ver_gt "enterprise-server@2.21" %} -### Todos los usuarios +### Enterprise overview -Aquí puedes ver todos los usuarios que han sido suspendidos en {{ site.data.variables.product.product_location_enterprise }}, e [iniciar una auditoría clave de SSH](/enterprise/{{ page.version }}/admin/guides/user-management/auditing-ssh-keys). +Refer to this section of the site admin dashboard to manage organizations, people, policies, and settings. {% endif %} -### Repositorios +### Repositories -Es una lista de los repositorios en {% data variables.product.product_location %}. Puedes hacer clic en un nombre de repositorio y acceder a las funciones para administrar el repositorio. +This is a list of the repositories on {% data variables.product.product_location %}. You can click on a repository name and access functions for administering the repository. -- [Bloquear empujes forzados en un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) -- [Configurar {% 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) -- [Archivar y desarchivar repositorios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) +- [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) +- [Configuring {% 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) +- [Archiving and unarchiving repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) -### Todos los usuarios +### All users -Aquí puedes ver todos los usuarios en {% data variables.product.product_location %}—, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users on {% data variables.product.product_location %}—, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). -### Administrador del sitio +### Site admins -Aquí puedes ver todos los administradores en {% data variables.product.product_location %}, e [iniciar una auditoría clave en SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). -### Usuarios inactivos +### Dormant users -Aquí puedes ver y [suspender](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) todos los usuarios inactivos en {% data variables.product.product_location %}. Una cuenta de usuario se considera inactiva ("dormant") cuando: +Here you can see and [suspend](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: -- Ha existido durante más tiempo del umbral de inactividad que está establecido para {% data variables.product.product_location %}. -- No ha generado ninguna actividad dentro de ese período. -- No es un administrador del sitio. +- Has existed for longer than the dormancy threshold that's set for {% data variables.product.product_location %}. +- Has not generated any activity within that time period. +- Is not a site administrator. -{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} Para obtener más información, consulta "[Administrar usuarios inactivos](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." +{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} For more information, see "[Managing dormant users](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." -### Usuarios suspendidos +### Suspended users -Aquí puedes ver todos los usuarios que han sido suspendidos en {% data variables.product.product_location %}, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - - [página de tendencia]: https://github.com/blog/1585-explore-what-is-trending-on-github - - [búsqueda de código]: https://github.com/blog/1381-a-whole-new-code-search - [ElasticSearch]: http://www.elasticsearch.org/ - - [índice de propuestas]: https://github.com/blog/831-issues-2-0-the-next-generation +Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). diff --git a/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md b/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md index d2932b5ab4..9ce5d9d9ac 100644 --- a/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md +++ b/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md @@ -24,5 +24,5 @@ Escribir solicitudes para la réplica exige que se envíen los datos al principa {% data reusables.enterprise_installation.monitoring-replicas %} -### Further reading +### 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)" diff --git a/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md index 2fcb79cdbe..51a0d0c243 100644 --- a/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md +++ b/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md @@ -174,6 +174,6 @@ Exitoso: la réplica se promovió a principal y ahora está aceptando solicitude El comando `ghe-repl-teardown` inhabilita el modo de replicación por completo, eliminando la configuración de la réplica. -### Further reading +### Leer más - "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)" diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md index 045565d933..ce42968814 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md @@ -6,7 +6,7 @@ redirect_from: - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster/ - /enterprise/admin/enterprise-management/configuring-clustering -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index 1868471de9..9e9642e26e 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -10,7 +10,7 @@ versions: ### Acerca de la replicación de disponibilidad alta para clústers -Puedes configurar el despliegue de un clúster de {% data variables.product.prodname_ghe_server %} para que tenga disponibilidad alta, mientras que un conjunto idéntico de nodos pasivos se sincroniza con los nodos en tu clúster activo. Si los fallos de hardware o de software afectan el datacenter que tiene tu clúster activo, puedes conmutar por error a los nódos de réplica y continuar procesando las solicitudes de los usuarios sin perder datos. +Puedes configurar el despliegue de un clúster de {% data variables.product.prodname_ghe_server %} para que tenga disponibilidad alta, mientras que un conjunto idéntico de nodos pasivos se sincroniza con los nodos en tu clúster activo. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage. En el modo de alta disponibilidad, cada nodo activo se sincroniza regularmente con un nodo pasivo correspondiente. El nodo pasivo se ejecuta en espera y no sirve a las aplicaciones ni procesa solicitudes de usuarios. diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md index be0ff7a756..905dc9cac2 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md @@ -7,7 +7,7 @@ redirect_from: - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability/ - /enterprise/admin/enterprise-management/configuring-high-availability intro: '{% data variables.product.prodname_ghe_server %} admite un modo de alta disponibilidad de funcionamiento diseñado para minimizar la interrupción del servicio en caso que ocurra una falla de hardware o una interrupción de red importante que afecte al aparato principal.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md index af6b994e19..faf22008e1 100644 --- a/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md +++ b/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md @@ -95,7 +95,7 @@ Para probarlo, puedes agregar entradas al archivo de `hosts` de la estación de HOSTNAME ``` -### Further reading +### Leer más - "[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)" diff --git a/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md index 2e05609563..379eaca2a5 100644 --- a/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md +++ b/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md @@ -36,7 +36,7 @@ Las características de disponibilidad, especialmente las que tienen conmutació -### Further reading +### Leer más - Para obtener más información acerca del {% data variables.product.prodname_ghe_server %} Agrupamiento, visite la sección de "[Acerca del agrupamiento](/enterprise/{{ currentVersion}}/admin/guides/clustering/about-clustering/)." - Para obtener más información sobre HA, consulta "[Configurar {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)". diff --git a/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md index abf38729ec..e37b7dc0bb 100644 --- a/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ Si colocas fuera de línea un nodo que tiene otros servicios de datos (como git, ghe-spokes evac-status ``` Para {% data variables.product.prodname_pages %} + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} Para almacenamiento ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ Si colocas fuera de línea un nodo que tiene otros servicios de datos (como git, 3. Una vez que la copia esté completa, puedes evacuar el servicio de almacenamiento. Ejecuta alguno de los siguientes comandos: Para Git + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} Para {% data variables.product.prodname_pages %} + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} Para almacenamiento, coloca el nodo fuera de línea + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} luego evacúa + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md b/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md index 03bbe6e78e..ed8716b944 100644 --- a/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ Los nombres de los nodos pueden ser cualquier nombre de host válido que elijas. Especifica el primer nodo de clùster que configuraste como el primario de MySQL a travès de `mysql-server` y de `mysql-master`. -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index e50b583189..6164e4c545 100644 --- a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -40,6 +40,6 @@ El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para $ ghe-repl-teardown -u UUID ``` -### Further reading +### Leer más - "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" diff --git a/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md index 858367c5a1..00638ec3d9 100644 --- a/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md +++ b/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md @@ -1,5 +1,5 @@ --- -title: Migrar desde GitHub Enterprise 11.10.x a 2.1.23 +title: Migrating from GitHub Enterprise 11.10.x to 2.1.23 redirect_from: - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123 - /enterprise/admin-guide/migrating/ @@ -9,83 +9,88 @@ redirect_from: - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x/ - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23 - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123 -intro: 'Para migrar desde {% data variables.product.prodname_enterprise %} 11.10.x a 2.1.23, deberás configurar una nueva instancia de aparato y migrar los datos de la instancia anterior.' +intro: 'To migrate from {% data variables.product.prodname_enterprise %} 11.10.x to 2.1.23, you''ll need to set up a new appliance instance and migrate data from the previous instance.' versions: enterprise-server: '*' --- -Se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 y superior. No se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 o inferior. Primero debes actualizar a 11.10.348 en varias actualizaciones. Para obtener más información, consulta el procedimiento de actualización 11.10.348, "[Actualizar al lanzamiento más reciente](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)." +Migrations from {% data variables.product.prodname_enterprise %} 11.10.348 and later are supported. Migrating from {% data variables.product.prodname_enterprise %} 11.10.348 and earlier is not supported. You must first upgrade to 11.10.348 in several upgrades. For more information, see the 11.10.348 upgrading procedure, "[Upgrading to the latest release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)." -Para actualizar a la versión más reciente {% data variables.product.prodname_enterprise %}, primero debes migrar a {% data variables.product.prodname_ghe_server %} 2.1, entonces puedes aplicar el proceso normal de actualización. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". +To upgrade to the latest version of {% data variables.product.prodname_enterprise %}, you must first migrate to {% data variables.product.prodname_ghe_server %} 2.1, then you can follow the normal upgrade process. For more information, see "[Upgrading {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". -### Prepárate para la migración +### Prepare for the migration -1. Revisa la guía de Abastecimiento e instalación y controla que se cumplan todos los requisitos previos necesarios para abastecer y configurar {% data variables.product.prodname_enterprise %} 2.1.23 en tu entorno. Para obtener más información, consulta "[Abastecimiento e instalación](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)." -2. Verifica que la instancia actual esté ejecutando una versión actualizada compatible. -3. Configura la versión más reciente de {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). - - Si ya has configurado copias de seguridad programadas utilizando {% data variables.product.prodname_enterprise_backup_utilities %}, asegúrate de que hayas actualizado a la versión más reciente. - - Si no estás ejecutando actualmente copias de seguridad programadas, configura {% data variables.product.prodname_enterprise_backup_utilities %}. -4. Toma una instantánea de copia de respaldo completa inicial de la instancia actual utilizando el comando `ghe-backup`. Si ya configuraste copias de seguridad programadas para tu instancia actual, no debes tomar una instantánea de tu instancia. +1. Review the Provisioning and Installation guide and check that all prerequisites needed to provision and configure {% data variables.product.prodname_enterprise %} 2.1.23 in your environment are met. For more information, see "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)." +2. Verify that the current instance is running a supported upgrade version. +3. Set up the latest version of the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). + - If you have already configured scheduled backups using {% data variables.product.prodname_enterprise_backup_utilities %}, make sure you have updated to the latest version. + - If you are not currently running scheduled backups, set up {% data variables.product.prodname_enterprise_backup_utilities %}. +4. Take an initial full backup snapshot of the current instance using the `ghe-backup` command. If you have already configured scheduled backups for your current instance, you don't need to take a snapshot of your instance. {% tip %} - **Sugerencia:** puedes dejar la instancia en línea y en uso activo durante la instantánea. Tomarás otras instantánea durante la parte de mantenimiento de la migración. Ya que las copias de seguridad son incrementales, esta instantánea inicial reduce la cantidad de datos transferidos en la instantánea final, que pueden acortar la ventana de mantenimiento. + **Tip:** You can leave the instance online and in active use during the snapshot. You'll take another snapshot during the maintenance portion of the migration. Since backups are incremental, this initial snapshot reduces the amount of data transferred in the final snapshot, which may shorten the maintenance window. {% endtip %} -5. Determina el método para cambiar el tráfico de red de usuario a la nueva instancia. Después de la migración, todo el tráfico de red de HTTP y Git se dirige a la nueva instancia. - - **DNS** - Recomendamos este método para todos los entornos, ya que es simple y funciona bien incluso cuando se migra desde una base de datos a otra. Antes de comenzar la migración, reduce los TTL de los registros DNS existentes a cinco minutos o menos y permite el cambio a propagar. Una vez que la migración se completa, actualiza los registros DNS para que apunten a la dirección IP de la nueva instancia. - - **Asignación de dirección IP** - Este método está únicamente disponible en VMware para la migración VMware y no se recomienda excepto que el método DNS no esté disponible. Antes de comenzar la migración, deberás cerrar la instancia anterior y asignar tu dirección IP a la nueva instancia. -6. Programa una ventana de mantenimiento. La ventana de mantenimiento debe incluir tiempo suficiente para transferir datos desde el servidor de seguridad a la nueva instancia y variará en base al tamaño de la instantánea de respaldo y el ancho de banda de la red disponible. Durante este tiempo tu instancia actual no estará disponible y estará en modo mantenimiento mientras migras a la nueva instancia. +5. Determine the method for switching user network traffic to the new instance. After you've migrated, all HTTP and Git network traffic directs to the new instance. + - **DNS** - We recommend this method for all environments, as it's simple and works well even when migrating from one datacenter to another. Before starting migration, reduce the existing DNS record's TTL to five minutes or less and allow the change to propagate. Once the migration is complete, update the DNS record(s) to point to the IP address of the new instance. + - **IP address assignment** - This method is only available on VMware to VMware migration and is not recommended unless the DNS method is unavailable. Before starting the migration, you'll need to shut down the old instance and assign its IP address to the new instance. +6. Schedule a maintenance window. The maintenance window should include enough time to transfer data from the backup host to the new instance and will vary based on the size of the backup snapshot and available network bandwidth. During this time your current instance will be unavailable and in maintenance mode while you migrate to the new instance. -### Realiza la migración +### Perform the migration -1. Aprovisiona una nueva instancia {% data variables.product.prodname_enterprise %} 2.1. Para obtener más información, consulta la "[Guía de aprovisionamiento e instalación](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" para tu plataforma destino. -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. Configura una contraseña de administrador. -5. Haz clic en **Migrate (Migrar)**. ![Elegir el tipo de instalación](/assets/images/enterprise/migration/migration-choose-install-type.png) -6. Pega tu clave SSH de acceso al servidor de respaldo en "Add new SSH key (Agregar nueva clave SSH)". ![Autorizar la copia de seguridad](/assets/images/enterprise/migration/migration-authorize-backup-host.png) -7. Da clic en **Agregar llave** y luego en **Continuar**. -8. Copia el comando `ghe-restore` que ejecutarás en el servidor de respaldo para migrar datos a la nueva instancia. ![Iniciar la migración](/assets/images/enterprise/migration/migration-restore-start.png) -9. Habilita el modo mantenimiento en la instancia anterior y espera a que se completen todos los procesos activos. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +1. Provision a new {% data variables.product.prodname_enterprise %} 2.1 instance. For more information, see the "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" guide for your target platform. +2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license. +3. Set an admin password. +5. Click **Migrate**. +![Choosing install type](/assets/images/enterprise/migration/migration-choose-install-type.png) +6. Paste your backup host access SSH key into "Add new SSH key". +![Authorizing backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png) +7. Click **Add key** and then click **Continue**. +8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance. +![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png) +9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% note %} - **Nota:** la instancia no estará disponible para el uso normal desde este punto en adelante. + **Note:** The instance will be unavailable for normal use from this point forward. {% endnote %} -10. En el servidor de respaldo, ejecuta el comando `ghe-backup` para tomar una instantánea de respaldo final. Esto asegura que se capturen todos los datos de la instancia anterior. -11. En el servidor de respaldo, ejecuta el comando `ghe-restore` que copiaste en la pantalla de estado de restauración de la nueva instancia para restaurar la instantánea más reciente. +10. On the backup host, run the `ghe-backup` command to take a final backup snapshot. This ensures that all data from the old instance is captured. +11. On the backup host, run the `ghe-restore` command you copied on the new instance's restore status screen to restore the latest snapshot. ```shell $ ghe-restore 169.254.1.1 The authenticity of host '169.254.1.1:122' can't be established. - La clave de huella digital RSA es fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1. - ¿Estás seguro que deseas continuar conectado (sí/no)? yes + RSA key fingerprint is fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1. + Are you sure you want to continue connecting (yes/no)? yes Connect 169.254.1.1:122 OK (v2.0.0) Starting restore of 169.254.1.1:122 from snapshot 20141014T141425 Restoring Git repositories ... - Restaurando las páginas GitHub ... - Restaurando los adjuntos de activo ... - Restaurando las entregas de enlace ... - Restaurando la base de datos MySQL ... - Restaurando la base de datos Redis ... - Restaurando las claves autorizadas de SSH ... - Restaurando los índice de ElasticSearch... - Restaurando las claves del servidor SSH ... + Restoring GitHub Pages ... + Restoring asset attachments ... + Restoring hook deliveries ... + Restoring MySQL database ... + Restoring Redis database ... + Restoring SSH authorized keys ... + Restoring Elasticsearch indices ... + Restoring SSH host keys ... Completed restore of 169.254.1.1:122 from snapshot 20141014T141425 Visit https://169.254.1.1/setup/settings to review appliance configuration. ``` -12. Regresa a la pantalla de estado de restauración de la nueva instancia para ver que la restauración está completa. ![Restaurar la pantalla completa](/assets/images/enterprise/migration/restore-complete-screen.png) -13. Haz clic en **Continue to settings (Continuar a configuraciones)** para revisar y ajustar la información de configuración y los parámetros que se importaron de la instancia anterior. ![Revisar los parámetros importados](/assets/images/enterprise/migration/migration-status-complete.png) -14. Haz clic en **Guardar parámetros**. +12. Return to the new instance's restore status screen to see that the restore completed. +![Restore complete screen](/assets/images/enterprise/migration/restore-complete-screen.png) +13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance. +![Review imported settings](/assets/images/enterprise/migration/migration-status-complete.png) +14. Click **Save settings**. {% note %} - **Nota:** puedes usar la nueva instancia después de haber aplicado los parámetros de configuración y restaurar el servidor. + **Note:** You can use the new instance after you've applied configuration settings and restarted the server. {% endnote %} -15. Cambia el tráfico de red de usuario desde la instancia anterior a la nueva instancia utilizando la asignación de DNS o la dirección IP. -16. Actualiza a la versión más reciente del lanzamiento del patch de {{ currentVersion }}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." +15. Switch user network traffic from the old instance to the new instance using either DNS or IP address assignment. +16. Upgrade to the latest patch release of {{ currentVersion }}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md index d5445dccb9..b25772e4ad 100644 --- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md +++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md @@ -6,7 +6,7 @@ redirect_from: - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance/ - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance - /enterprise/admin/enterprise-management/monitoring-your-appliance -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md index 4059761f9b..946bf3d096 100644 --- a/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md +++ b/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md @@ -14,10 +14,10 @@ versions: Recomendamos que controles los dispositivos de almacenamiento de usuario y raíz y configures una alerta con valores que permitan un gran tiempo de respuesta cuando el espacio de disco disponible sea bajo. -| Severity | Límite | -| ----------- | ---------------------------------------------------- | -| **Warning** | El disco excede el 70 % del total disponible | -| **Crítico** | El uso del disco excede el 85 % del total disponible | +| Gravedad | Límite | +| --------------- | ---------------------------------------------------- | +| **Advertencia** | El disco excede el 70 % del total disponible | +| **Crítico** | El uso del disco excede el 85 % del total disponible | Puedes ajustar estos valores en base a la cantidad total de almacenamiento asignado, los patrones de crecimiento histórico y el tiempo esperado de respuesta. Recomendamos asignar en exceso recursos de almacenamiento para permitir el crecimiento y evitar el tiempo de inactividad requerido para asignar almacenamiento adicional. @@ -25,10 +25,10 @@ Puedes ajustar estos valores en base a la cantidad total de almacenamiento asign A pesar de que es normal que el uso de CPU fluctúe en base a las operaciones Git que utilizan muchos recursos, recomendamos configurar una alerta para la utilización del CPU anormalmente alta, ya que spikes prolongados puede significar que tu instancia tiene un aprovisionamiento insuficiente. Recomendamos controlar la carga promedio del sistema de quince minutos para los valores que se acerquen o excedan la cantidad de núcleos de CPU asignados en la máquina virtual. -| Severity | Límite | -| ----------- | --------------------------------------------------------------- | -| **Warning** | La carga promedio de quince minutos excede 1x de núcleos de CPU | -| **Crítico** | La carga promedio de quince minutos excede 2x de núcleos de CPU | +| Gravedad | Límite | +| --------------- | --------------------------------------------------------------- | +| **Advertencia** | La carga promedio de quince minutos excede 1x de núcleos de CPU | +| **Crítico** | La carga promedio de quince minutos excede 2x de núcleos de CPU | También recomendamos que controles el tiempo de "robo" de virtualización para asegurar que otras máquinas virtuales ejecutándose en el mismo sistema de servidor no estén usando todos los recursos de la instancia. @@ -36,9 +36,9 @@ También recomendamos que controles el tiempo de "robo" de virtualización para La cantidad de memoria física asignada a {% data variables.product.product_location %} puede tener un gran impacto sobre el desempeño general y la capacidad de respuesta de la aplicación. El sistema está designado para realizar un uso intenso del caché del disco kernel para acelerar las operaciones Git. Recomendamos que el conjunto en funcionamiento de RSS normal se acomode dentro del 50 % del total de RAM disponible para un uso máximo. -| Severity | Límite | -| ----------- | ---------------------------------------------------------------------- | -| **Warning** | El uso sostenido de RSS excede el 50 % del total de memoria disponible | -| **Crítico** | El uso sostenido de RSS excede el 70 % del total de memoria disponible | +| Gravedad | Límite | +| --------------- | ---------------------------------------------------------------------- | +| **Advertencia** | El uso sostenido de RSS excede el 50 % del total de memoria disponible | +| **Crítico** | El uso sostenido de RSS excede el 70 % del total de memoria disponible | Si se acaba la memoria, el killer de OOM kernel intentará liberar recursos de memoria al sacrificar de manera forzosa procesos de aplicación con mucho uso de RAM, lo que puede dar como resultado una interrupción del servicio. Recomendamos asignar más memoria a la máquina virtual de la requerida en el curso normal de las operaciones. diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md index 45c6093fce..9daf46a3bd 100644 --- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md +++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources.md @@ -6,7 +6,7 @@ redirect_from: - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources/' - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md index c825130742..231337b03f 100644 --- a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -220,7 +220,7 @@ Para obtener más información, consulta "[Herramientas de línea de comando](/e 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)." {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Further reading +### Leer más - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" {% endif %} \ No newline at end of file diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md index c4186a5ba3..e8241a80a3 100644 --- a/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md @@ -123,7 +123,6 @@ Cuando contactas a {% data variables.contact.enterprise_support %}, puedes escog ### Leer más {% if enterpriseServerVersions contains currentVersion %} -- [Preguntas frecuentes sobre {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) - 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)"{% if enterpriseServerVersions contains currentVersion %} - "[Prepararse para emitir un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} diff --git a/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md index 75b5448dd7..d3305c6ae5 100644 --- a/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md +++ b/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md @@ -38,13 +38,13 @@ Puedes ponerte en contacto con {% data variables.contact.enterprise_support %} a ### Horas de operación -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. holidays. El tiempo de respuesta estándar es de 1 día hábil. +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. ### Cronograma de feriados -{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. holidays. +{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. EE.UU. -| Feriado en EE.UU. holiday | Fecha en la que se celebra | +| Feriado en EE.UU. | Fecha en la que se celebra | | --------------------------------- | --------------------------- | | Año Nuevo | 1 de enero | | Día de Martin Luther King, Jr. | Tercer lunes de enero | diff --git a/translations/es-ES/content/admin/enterprise-support/overview.md b/translations/es-ES/content/admin/enterprise-support/overview.md index c7a152e50e..a22ceafaa0 100644 --- a/translations/es-ES/content/admin/enterprise-support/overview.md +++ b/translations/es-ES/content/admin/enterprise-support/overview.md @@ -1,7 +1,7 @@ --- title: Resumen intro: 'Conoce las opciones de soporte disponibles para {% data variables.product.product_name %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/enterprise-support/overview versions: diff --git a/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md index b9c94d00b3..4125bcc916 100644 --- a/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md @@ -148,7 +148,7 @@ Puedes cargar directamente un paquete de soporte a nuestro servidor si: $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u -x' ``` -### Further reading +### Leer más - "[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)". diff --git a/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md b/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md index 4b3ea8f079..be251b0e4f 100644 --- a/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md +++ b/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md @@ -31,12 +31,12 @@ Puedes usar el {% data variables.contact.enterprise_portal %} para ver tickets d 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)". {% endif %} -### Contacting sales +### Contacto de ventas 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). {% if enterpriseServerVersions contains currentVersion %} -### Contacting training +### Contacto de capacitación 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/). @@ -47,7 +47,7 @@ Para conocer más sobre las opciones de capacitación, incluida la capacitación {% endnote %} {% endif %} -### Further reading +### Leer más - "[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)". diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md index 3d25b2563c..60cb477495 100644 --- a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md +++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support.md @@ -4,7 +4,7 @@ intro: 'Puedes contactar a {% data variables.contact.enterprise_support %} para redirect_from: - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/ - /enterprise/admin/enterprise-support/receiving-help-from-github-support -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md b/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md index 2b790cd0af..ddd6a5a07e 100644 --- a/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md +++ b/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md @@ -57,7 +57,7 @@ Para problemas urgentes, para asegurar una respuesta rápida, después de emitir {% endif %} -### Further reading +### Leer más - "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% if enterpriseServerVersions contains currentVersion %} - "[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 %} diff --git a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md index 9a4a080bfe..9786bc4116 100644 --- a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md +++ b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -1,7 +1,7 @@ --- title: Configuración avanzada y solución de problemas intro: 'Configura la disponibilidad alta para {% data variables.product.prodname_actions %} y soluciona los problemas de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '>=3.0' --- diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md index 217962daac..40216baced 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -1,7 +1,7 @@ --- 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 %}.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '>=2.22' --- diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md index 1d4955b5af..57ea5e8624 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom.md @@ -1,7 +1,7 @@ --- title: Administrar el acceso a las acciones desde GitHub.com intro: 'En tu empresa, puedes controlar qué acciones de {% data variables.product.prodname_dotcom_the_website %} y de {% data variables.product.prodname_marketplace %} se pueden utilizar.' -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom versions: diff --git a/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 80e9f3c337..4ab484dcdf 100644 --- a/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -63,7 +63,7 @@ Este ejemplo demuestra el uso de la herramienta `actions-sync` para sincronizar * 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 instancia empresarial, 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: - ``` + ```yaml uses: synced-actions/docker-build-push-action@v1 ``` diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md index af4485bf23..57926795d5 100644 --- a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -128,7 +128,7 @@ Tanto en la instancia principal y en la de réplica deberían asignarse EIP sepa {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -### Further reading +### Leer más - "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md index 95fe583b17..2274f28813 100644 --- a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,7 +106,7 @@ Te recomendamos que uses un tipo de instancia DS v2 con 14 GB de RAM como mínim {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -### Further reading +### Leer más - "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index 50cf7f88ab..39ac301070 100644 --- a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -111,7 +111,7 @@ Para crear la instancia {% data variables.product.prodname_ghe_server %}, deber {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -### Further reading +### Leer más - "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index 7e401d1931..b7eef3768d 100644 --- a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -47,7 +47,7 @@ imagen de {% data variables.product.prodname_ghe_server %} que descargaste. Para {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -### Further reading +### Leer más - "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 48bfea3eac..8b2126b8d4 100644 --- a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -46,7 +46,7 @@ versions: {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -### Further reading +### Leer más - "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index 59f88e7e0f..4d058ea0ee 100644 --- a/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/es-ES/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -43,7 +43,7 @@ versions: {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} -### Further reading +### Leer más - "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md index 39815e65c2..211f164f45 100644 --- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md +++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance.md @@ -7,7 +7,7 @@ redirect_from: - /enterprise/admin/guides/installation/provisioning-and-installation/ - /enterprise/admin/guides/installation/setting-up-a-github-enterprise-instance/ - /enterprise/admin/installation/setting-up-a-github-enterprise-server-instance -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/overview/about-github-ae.md b/translations/es-ES/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..e874b7d4a0 --- /dev/null +++ b/translations/es-ES/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: Acerca de GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} es la forma más segura y compatible para utilizar {% data variables.product.prodname_dotcom %}.' +versions: + github-ae: '*' +--- + +### Acerca de {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} ofrece una plataforma de desarrollo que va desde la idea hasta la producción. Puedes incrementar la velocidad de desarrollo, automatizar los flujos de trabajo integralmente, asegurar tu código y colaborar en la herramienta favorita del desarrollador. + +{% data variables.product.prodname_ghe_managed %} proporciona todo el poder de [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) a tu organización. Con {% data variables.product.prodname_ghe_managed %}, también puedes adecuarte a las medidas de seguridad y cumplimiento con una suite de características y certificaciones que te dan todo el control. + +### Una nube de disponibilidad alta y escala planetaria + +{% data variables.product.prodname_ghe_managed %} es un servicio totalmente administrado, el cual se hospeda en una arquitectura de disponibilidad alta. {% data variables.product.prodname_ghe_managed %} se hospeda globalmente en una nube que puede escalarse para ser compatible con el ciclo de vida integral de tu desarrollo, sin límites. {% data variables.product.prodname_dotcom %} administra integralmente los respaldos, recuperaciones de fallos y de desastres para que jamás tengas que preocuparte por tus datos o tu servicio. + +### Residencia de los datos + +Todos tus datos se almacenan dentro de la región geográfica de tu elección. Puedes apegarte a la GDPR y a los estándares de protección de datos globales manteniendo todos tus datos dentro de tu región de elección. + +### Cifrado bajo tus condiciones + +Todos los datos del cliente se cifran estáticos y puedes proporcionar tus propias llaves de cifrado para cifrar tus datos bajo tus propias políticas. Tú controlas tu llave y el acceso a todos tus datos. Para obtener más información, consulta la sección "[Configurar el cifrado de datos para tu empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)". + +### Cuentas aisladas + +Todas las cuentas de desarrollador se aislan por completo en {% data variables.product.prodname_ghe_managed %}. Puedes controlar las cuentas integralmente a través de tu proveedor de identidad, haciendo obligatorio el inicio de sesión único de SAML. El SCIM te permite garantizar que los empleados solo tengan acceso a los recursos que necesitan, de acuerdo como se define en tu sistema central de administración de identidades. Para obtener más información, consulta la sección "[Administrar el acceso y la identidad en tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". + +### Acceso restringido a las redes + +Asegura el acceso a tu empresa en {% data variables.product.prodname_ghe_managed %} con políticas de acceso restrictivo para que solo se pueda llegar a tus datos desde dentro de tu red. Para obtener más información, consulta la sección "[Restringir el tráfico de red para tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)". + +### Ambientes comerciales y gubernamentales + +{% data variables.product.prodname_ghe_managed %} se encuentra disponible en la nube de Azure Government, la nube de confianza de las agencias gubernamentales de los EE.UU. y de sus socios. {% data variables.product.prodname_ghe_managed %} también se encuentra disponible en la nube comercial, para que puedas elegir el ambiente de hospedaje que se adecua a tu organización. + +### Soporte Premium Plus + +El soporte Premium Plus se encuentra disponible para todos los clientes de {% data variables.product.prodname_ghe_managed %} para garantizar que tengas la experiencia de soporte más rápida y personal. Un representante de cuenta dedicado trabajará contigo para ayudarte a obtener el máximo provecho de {% data variables.product.prodname_dotcom %}. Nuestro equipo de soporte resolverá tus problemas a cualquier hora del día y en el menor tiempo posible. + +### Acerca de la facturación para {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.about-billing %} Para obtener más información, consulta la sección "[Administrar la facturación de tu empresa](/admin/overview/managing-billing-for-your-enterprise)". \ No newline at end of file diff --git a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md index 76a55c1e1d..ec1d847c7e 100644 --- a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md @@ -24,10 +24,10 @@ Utilizaremos tu retroalimentación para aplicar las correcciones de errores y cu {% endwarning %} -Los lanzamientos menores, los cuales consisten únicamente de parches y correcciones de errores, ocurren con mayor frecuencia. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. +Los lanzamientos menores, los cuales consisten únicamente de parches y correcciones de errores, ocurren con mayor frecuencia. Los lanzamientos menores se encuentran generalmente disponibles cuando se lanzan por primera vez, sin candidatos de lanzamiento. El mejorar a un lanzamiento menor habitualmente requiere menos de cinco minutos de tiempo de inactividad. -To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +Para mejorar tu empresa a un lanzamiento nuevo, consulta las secciones "[Notas de lanzamiento](/enterprise-server/admin/release-notes)" y "[Mejorar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)". -### Further reading +### Leer más - [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` diff --git a/translations/es-ES/content/admin/overview/index.md b/translations/es-ES/content/admin/overview/index.md index 28769913e0..eb0bd51a10 100644 --- a/translations/es-ES/content/admin/overview/index.md +++ b/translations/es-ES/content/admin/overview/index.md @@ -12,6 +12,7 @@ Para obtener más información, o para comprar {% data variables.product.prodnam ### Índice +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} diff --git a/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md b/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md index 7983692501..9c2c6c68fb 100644 --- a/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ instancia de {% data variables.product.prodname_ghe_server %} como administrador {% data reusables.enterprise-accounts.license-tab %} 12. Dentro de "Quick links (Vínculos rápidos)", haz clic en **Update license (Actualizar licencia)**. ![Actualizar enlace de la licencia](/assets/images/enterprise/business-accounts/update-license-link.png) 13. Para seleccionar tu licencia, da clic en **Archivo de licencia**, o arrastra tu archivo de licencia a **Archivo de licencia**. ![Sube el archivo de licencia](/assets/images/enterprise/management-console/upload-license.png) -14. Da clic en **Cargar**. ![Comienza la actualización](/assets/images/enterprise/management-console/begin-upload.png) +14. Da clic en **Cargar**. ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %} ### Ver el uso de la licencia @@ -52,11 +54,11 @@ instancia de {% data variables.product.prodname_ghe_server %} como administrador ### Sincronizar de forma automática el uso de la licencia de usuario con {% data variables.product.prodname_ghe_cloud %} -Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de las licencias de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar la sincronización de licencias de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)". +Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de la licencia de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar la sincronización de licencias de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)". ### Sincronizar el uso de licencias de usuario manualmente entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} -Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar el uso de la licencia de usuario entre dos implementaciones de forma manual. +Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar de forma manual el uso de la licencia de usuario entre dos implementaciones. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} @@ -70,3 +72,23 @@ Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_se {% data reusables.enterprise-accounts.license-tab %} 10. Debajo de "Instancias de Enterprise Server", da clic en **Agregar uso del servidor**. ![Sube el vínculo de uso de los servidores de GitHub Enterprise](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. Sube el archivo JSON que descargaste de {% data variables.product.prodname_ghe_server %}. ![Arrastra y suelta o selecciona un archivo para cargar](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### Solución de problemas + +In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Restart the services for Git authentication and the HTTP server. + + {% warning %} + + **Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again. + +{% endif %} diff --git a/translations/es-ES/content/admin/overview/system-overview.md b/translations/es-ES/content/admin/overview/system-overview.md index 9b3328f4cf..b59c3c75fa 100644 --- a/translations/es-ES/content/admin/overview/system-overview.md +++ b/translations/es-ES/content/admin/overview/system-overview.md @@ -135,7 +135,7 @@ Están disponibles en tu aparato los tarballes con una lista completa de depende También están disponibles los tarballes, con una lista completa de las dependencias y los metadatos, en `https://enterprise.github.com/releases//download.html`. -### Further reading +### Leer más - "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" - "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md index 5b1289d0a5..a3ae17153c 100644 --- a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md +++ b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Configuring package ecosystem support for your enterprise -intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.' +title: Configurar la compatibilidad del ecosistema de paquetes para tu empresa +intro: 'Puedes configurar el {% data variables.product.prodname_registry %} para tu empresa si habilitas o inhabilitas globalmente los ecosistemas de paquetes individuales en tu empresa, incluyendo Docker, RubyGems, npm, Apache Maven, Gradle o NuGet. Aprende sobre otros requisitos de configuración para hacer compatibles algunos ecosistemas de paquetes específicos.' redirect_from: - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise - /admin/packages/configuring-packages-support-for-your-enterprise @@ -10,13 +10,13 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -### Enabling or disabling individual package ecosystems +### Habilitar o inhabilitar los ecosistemas de paquetes individuales -To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded. +Para prevenir que los paquetes nuevos se carguen, puedes configurar un ecosistema que hayas habilitado previamente como **Solo lectura**, mientras aún permites que los paquetes existentes se descarguen. {% if currentVersion == "enterprise-server@2.22" %} -To use -{% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. Para obtener más información, consulta la sección "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)". +Para utilizar +el {% data variables.product.prodname_registry %} con Docker, debes tener habilitado el aislamiento de subdominios para tu instancia. Para obtener más información, consulta la sección "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)". {% endif %} {% data reusables.enterprise_site_admin_settings.access-settings %} @@ -26,22 +26,22 @@ To use {% data reusables.enterprise_management_console.save-settings %} {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} -### Connecting to the official NPM registry +### Conectarse al registro oficial de NPM -If you've enabled npm packages on your enterprise and want to allow access to the official NPM registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration. +Si habilitaste los paquetes de npm en tu empresa y quieres permitir el acceso al registro oficial de NPM así como al registro de npm del {% data variables.product.prodname_registry %}, entonces debes realizar algunos ajustes adicionales. -{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official NPM registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled. +El {% data variables.product.prodname_registry %} utiliza un proxy transparente para el tráfico de red que conecta el registro oficial de NPM en `registry.npmjs.com`. El proxy se habilita predeterminadamente y no puede inhabilitarse. -To allow network connections to the NPM registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com` over port 443: +Para permitir las conexiones de red en el registro de NPM, necesitarás configurar las ACL de red que permitan a {% data variables.product.prodname_ghe_server %} enviar el tráfico de HTTPS a `registry.npmjs.com` por el puerto 443: -| Source | Destination | Port (Puerto) | Type | +| Origen | Destino | Port (Puerto) | Tipo | | -------------------------------------------------- | -------------------- | ------------- | ----- | | {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS | -Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/. +Nota que las conexiones a `registry.npmjs.com` atraviesan por la red de Cloudflare y, subsecuentemente, no se conectan a una IP estática única; en vez de esto, se hace una conexión a una dirección IP dentro de los rangos CIDR que se listan aquí: https://www.cloudflare.com/ips/. {% endif %} ### Pasos siguientes -As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +Como paso siguiente, te recomendamos verificar si necesitas actualizar o cargar un certificado TLS para tu URL de hospedaje de paquetes. Para obtener más información, consulta la sección "[Iniciar con GitHub Packages para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md index b4416b0b2c..9467c37b67 100644 --- a/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md +++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-aws.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Packages with AWS -intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +title: Habilitar GitHub packages con AWS +intro: 'Configura el {% data variables.product.prodname_registry %} con AWS como tu almacenamiento externo.' versions: enterprise-server: '>=2.22' --- @@ -8,7 +8,7 @@ versions: {% warning %} **Advertencias:** -- It is critical that you configure any 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 to the public internet. For more information, see "[Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" in the AWS Documentation. +- Es crítico que configures cualquier política de acceso restrictivo que necesites para tu bucket de almacenamiento, ya que {% data variables.product.company_short %} no aplica permisos de objeto específicos para cualquier lista de control de accesos (ACL) a tu configuración de bucket de almacenamiento. Por ejemplo, si haces público tu bucket, el público general en la internet podrá acceder a los datos que se encuentren ahí. Para obtener más información, consulta la sección "[Configurar los permisos de acceso de objetos y buckets](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" en la documentación de AWS. - 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 %}. @@ -16,9 +16,9 @@ versions: ### Prerrequisitos -Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). +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 AWS. Para preparar tu bucket de almacenamiento de AWS, te recomendamos consultar los documentos oficiales de AWS en la [documentación de AWS](https://docs.aws.amazon.com/index.html). -Ensure your AWS access key ID and secret have the following permissions: +Asegúrate de que la ID de tu clave y secreto de acceso de AWS tengan los siguientes permisos: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -27,7 +27,7 @@ Ensure your AWS access key ID and secret have the following permissions: - `s3:DeleteObject` - `s3:ListBucket` -### Enabling {% data variables.product.prodname_registry %} with AWS external storage +### Habilitar el {% data variables.product.prodname_registry %} con el almacenamiento externo de AWS {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -41,17 +41,17 @@ Ensure your AWS access key ID and secret have the following permissions: 1. Debajo de "AWS S3 Region", teclea tu región para S3. ![Campo de región de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: - - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. +1. Debajo de "Almacenamiento de Paquetes", selecciona **Amazon S3** e ingresa los detalles de tu bucket de almacenamiento: + - **AWS Service URL:** La URL de servicio para tu bucket. Por ejemplo, si tu bucket de S3 se creó en la `us-west-2 region`, este valor deberá ser `https://s3.us-west-2.amazonaws.com`. - For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + Para obtener más información, consulta la sección "[terminales de servicio de AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" en la documentación de AWS. - - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. - - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + - **AWS S3 Bucket:** El nombre de tu bucket de S3 dedicado para el {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** y **AWS S3 Secret Key**: La ID de clave de acceso y secreto de AWS para acceder a tu bucket. - For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + Para obtener más información sobre cómo administrar las claves de acceso de AWS, consulta la "[Documentación para la Administración de Accesos e Identidad de AWS](https://docs.aws.amazon.com/iam/index.html)". - ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) + ![Cajas de entrada para los detalles de tu bucket de AWS S3](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index 5fc2045680..b2de0034a4 100644 --- a/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/es-ES/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Packages with Azure Blob Storage -intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +title: Habilitar GitHub Packages con Azure Blob Storage +intro: 'Configura el {% data variables.product.prodname_registry %} con Azure Blob Storage como tu almacenamiento externo.' versions: enterprise-server: '>=3.0' --- @@ -8,7 +8,7 @@ versions: {% warning %} **Advertencias:** -- 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. Por ejemplo, si haces a tu bucket público, el público general en la internet podrá acceder a ellos. +- 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 %}. @@ -16,15 +16,15 @@ versions: ### Prerrequisitos -Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). +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 Azure Blob Storage. Para preparar tu bucket de Azure Blob Storage, te recomendamos consultar los documentos oficiales de este servicio en el [sitio oficial de documentación de Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/). -### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage +### Habilitar el {% data variables.product.prodname_registry %} con Azure Blob Storage {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} -1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) +1. Debajo de "Almacenamiento de Packages", selecciona **Azure Blob Storage** e ingresa el nombre de tu contenedor de Azure para tu bucket de almacenamiento de paquetes y secuencia de conexión. ![Cajas para el nombre del contenedor de Azure Blob Storage y secuencia de conexión](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% data reusables.enterprise_management_console.save-settings %} 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 4f46c8542b..d6f34333cd 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: Enabling GitHub Packages with MinIO -intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +title: Habilitar los GitHub Packages con MinIO +intro: 'Configura el {% data variables.product.prodname_registry %} con MinIO como tu almacenamiento externo.' versions: enterprise-server: '>=2.22' --- @@ -8,15 +8,15 @@ versions: {% warning %} **Advertencias:** -- 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. Por ejemplo, si haces a tu bucket público, el público general en la internet podrá acceder a ellos. +- 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 %}. {% endwarning %} ### Prerrequisitos -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)." +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)". -Ensure your MinIO external storage access key ID and secret have these permissions: +Asegúrate que tu ID de clave de acceso y secreto de almacenamiento externo de MinIO tenga estos permisos: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -25,29 +25,29 @@ Ensure your MinIO external storage access key ID and secret have these permissio - `s3:DeleteObject` - `s3:ListBucket` -### Enabling {% data variables.product.prodname_registry %} with MinIO external storage +### Habilitar el {% data variables.product.prodname_registry %} con el almacenamiento externo de MinIO -Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} 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. +Aunque MinIO no aparece actualmente en la interface de usuario bajo "Almacenamiento de paquetes", aún es {% if currentVersion == "enterprise-server@2.22" %} oficialmente{% endif %} compatible con el {% data variables.product.prodname_registry %} en {% 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. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} {% if currentVersion == "enterprise-server@2.22" %} -1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![Campo de URL de servicio de AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) -1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![Campo de espacio de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) -1. Under "AWS S3 Access Key", type your access key for MinIO. ![Campo de clave de acceso de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) -1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![Campo de clave secreta de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) -1. Under "AWS S3 Region", type your region for MinIO. ![Campo de región de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +1. Debajo de "URL de Servicio de AWS", teclea la URL de MinIO para la región de tu bucket. ![Campo de URL de servicio de AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Debajo de "Bucket de AWS S3", teclea el nombre del bucket de MinIO que quieras utilizar para almacenar artefactos de paquetes. ![Campo de espacio de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Debajo de "Clave de Acceso de AWS S3", teclea tu clave de acceso para MinIO. ![Campo de clave de acceso de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Debajo de "Clave secreta de AWS S3", teclea tu clave secreta para MinIO. ![Campo de clave secreta de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Debajo de "Región de AWS S3", teclea tu región para MinIO. ![Campo de región de AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -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. +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. - ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) + ![Cajas de entrada para los detalles de tu bucket de AWS S3](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index 58ad9273f1..453ed85c06 100644 --- a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Getting started with GitHub Packages for your enterprise -intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +title: Iniciar con GitHub Packages para tu empresa +intro: 'Puedes comenzar a utilizar el {% data variables.product.prodname_registry %} en {% data variables.product.product_location %} si habilitas esta característica, configurando un almacenamiento de terceros, configurando los ecosistemas que quieras que sea compatibles y actualizando tu certificado TLS.' redirect_from: - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise - /admin/packages/enabling-github-packages-for-your-enterprise @@ -14,7 +14,7 @@ versions: {% note %} -**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. +**Nota:** Después de que se te ha invitado a unirte al beta, sigue las instrucciones de tu representante de cuenta para habilitar el {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}. {% endnote %} @@ -22,28 +22,28 @@ versions: {% data reusables.package_registry.packages-cluster-support %} -### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage +### Paso 1: Habilita el {% data variables.product.prodname_registry %} y configura el almacenamiento externo {% data variables.product.prodname_registry %} en {% data variables.product.prodname_ghe_server %} utiliza almacenamiento externo de blobs para almacenar tus paquetes. -After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. +Después de habilitar el {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, necesitarás preparar tu bucket de almacenamiento de terceros. La cantidad de almacenamiento que requieras dependerá de tu uso del {% data variables.product.prodname_registry %}, y los lineamientos de configuración podrán variar dependiendo del proveedor de almacenamiento. -Supported external storage providers +Proveedores de almacenamiento externo compatibles - Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} - Azure Blob Storage {% endif %} - MinIO -To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: - - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} - - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" +Para habilitar el {% data variables.product.prodname_registry %} y configurar el almacenamiento de terceros, consulta: + - "[Habilitar GitHub Packages con AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Habilitar GitHub Packages con Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Habilitar GitHub Packages con MinIO](/admin/packages/enabling-github-packages-with-minio)" -### Step 2: Specify the package ecosystems to support on your instance +### Paso 2: Especifica los ecosistemas de paquetes que serán compatibles con tu instancia -Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." +Elige qué ecosistemas de paquetes te gustaría habilitar, inhabilitar o configurar como de solo lectura en tu {% data variables.product.product_location %}. Las opciones disponibles son Docker, RubyGems, npm, Apache maven, Gradle o NuGet. Para obtener más información, consulta la sección "[Configurar la compatibilidad de ecosistemas de paquetes para tu empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". -### Step 3: Ensure you have a TLS certificate for your package host URL, if needed +### Paso 3: De ser necesario, asegúrate de que tienes un certificado de TLS para la URL de hospedaje de tu paquete -If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Asegúrate de que cada URL de host de paquete incluya `https://`. +Si está habilitado el aislamiento de subdominios para {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, el cual se necesita para utilizar el {% data variables.product.prodname_registry %} con Docker{% endif %}, necesitarás crear y cargar un certificado TLS que permita la URL de hospedaje de paquetes para cada ecosistema que quieras utilizar, tal como `npm.HOSTNAME`. Asegúrate de que cada URL de host de paquete incluya `https://`. - You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. Para obtener más información acerca de las URL del host de los paquetes, consulta "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obtener más información sobre cómo cargar certificados TLS a {% data variables.product.product_name %}, consulta la sección "[Configurar el TLS](/enterprise/admin/configuration/configuring-tls)". + Puedes crear el certificado manualmente, o puedes utilizar _Let's Encrypt_. Si ya utilizas _Let's Encrypt_, debes solicitar un certificado TLS nuevo después de habilitar el {% data variables.product.prodname_registry %}. Para obtener más información acerca de las URL del host de los paquetes, consulta "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obtener más información sobre cómo cargar certificados TLS a {% data variables.product.product_name %}, consulta la sección "[Configurar el TLS](/enterprise/admin/configuration/configuring-tls)". diff --git a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md index 1c7bdd3f85..b0a6d7e4a6 100644 --- a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md +++ b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -1,6 +1,6 @@ --- -title: Quickstart for configuring your MinIO storage bucket for GitHub Packages -intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +title: Guía de inicio rápido para configurar tu bucket de almacenamiento de MinIO para GitHub Packages +intro: 'Configura tu bucket de almacenamiento de MinIO personalizado para utilizarlo con {% data variables.product.prodname_registry %}.' versions: enterprise-server: '>=2.22' --- @@ -129,4 +129,4 @@ Para terminar de configurar el almacenamiento para el {% data variables.product. echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" ``` -For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." +Para los pasos siguientes, consulta la sección "[Habilitar el {% data variables.product.prodname_registry %} con MinIO](/admin/packages/enabling-github-packages-with-minio)". diff --git a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md index 79afed7e7f..ba9ee396d6 100644 --- a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -57,8 +57,9 @@ Fuera de los valores que se brindan a `stdin`, existen variables adicionales que | $GITHUB_PULL_REQUEST_BASE | Una secuencia en el formato: `user:branch` para la BASE de la Solicitud de Extracción.
Ejemplo: `octocat:main` | | $GITHUB_VIA | Método usado para crear la ref.
**Valores posibles:**
- `auto-merge deployment api`
- `blob edit`
- `branch merge api`
- `branches page delete button`
- `git refs create api`
- `git refs delete api`
- `git refs update api`
- `merge api`
- `pull request branch delete button`
- `pull request branch undo button`
- `pull request merge api`
- `pull request merge button`
- `pull request revert button`
- `releases delete button`
- `stafftools branch restore`
- `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | El número de opciones de extracción que envió el cliente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. | -| $GIT_PUSH_OPTION_N | Where N is an integer starting at 0, this variable contains the push option string that was sent by the client. La primera opción que se envió se almacenó en GIT_PUSH_OPTION_0, la segunda opción que se envió se almacenó en GIT_PUSH_OPTION_1, y así sucesivamente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | La secuencia de usuario-agente que envió el cliente que subió los cambios. |{% endif %} +| $GIT_PUSH_OPTION_N | En donde N es un número entero que comienza con 0, esta variable contiene la cadena de opción de subida que envió el cliente. La primera opción que se envió se almacenó en GIT_PUSH_OPTION_0, la segunda opción que se envió se almacenó en GIT_PUSH_OPTION_1, y así sucesivamente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. |{% if currentVersion ver_gt "enterprise-server@2.21" %} +| $GIT_USER_AGENT | La secuencia de usuario-agente que envió el cliente que subió los cambios. +{% endif %} ### Establecer permisos y subidas a un ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} @@ -93,30 +94,30 @@ Puedes probar un script de gancho de pre-recepción localmente antes de crear o 2. Crear un archivo denominado `Dockerfile.dev` que contenga: - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. Crear un script de pre-recepción de prueba denominado `always_reject.sh`. Este script del ejemplo rechazará todas las subidas, lo cual es útil para bloquear un repositorio: + 3. Crear un script de pre-recepción de prueba denominado `always_reject.sh`. Este script del ejemplo rechazará todas las subidas, lo cual es útil para bloquear un repositorio: - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 @@ -197,5 +198,5 @@ Puedes probar un script de gancho de pre-recepción localmente antes de crear o Observa que la subida fue rechazada después de ejecutar el ganchos de pre-recepción y de hace eco la salida del script. -### Further reading +### Leer más - "[Personalizar Git - Un ejemplo de la política activa de Git](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" desde el *sitio web de Pro Git* diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md index f2439cea28..d9cdd396ad 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Requerir políticas para tu empresa -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/policies/enforcing-policies-for-your-enterprise versions: diff --git a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md index 5d1237c55c..6eb5da5a36 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md +++ b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks.md @@ -1,7 +1,7 @@ --- title: Requerir políticas para los ganchos de pre-recepción intro: Usar ganchos de pre-recepción para implementar estándares de flujo de trabajo dentro de tu organización. Los ganchos de pre-recepción requieren un código para aprobar un conjunto de verificaciones de calidad predefinido antes de que la extracción sea aceptada en el repositorio. -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy - /enterprise/admin/policies/enforcing-policy-with-pre-receive-hooks diff --git a/translations/es-ES/content/admin/release-notes.md b/translations/es-ES/content/admin/release-notes.md index 7f4e202b7f..7c2566b11e 100644 --- a/translations/es-ES/content/admin/release-notes.md +++ b/translations/es-ES/content/admin/release-notes.md @@ -1,7 +1,7 @@ --- title: Notas de lanzamiento -intro: Las notas de lanzamiento para {{ allVersions[currentVersion].versionTitle }}. -layout: notas de lanzamiento +intro: 'Las notas de lanzamiento para {{ allVersions[currentVersion].versionTitle }}.' +layout: release-notes versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/admin/user-management/audited-actions.md b/translations/es-ES/content/admin/user-management/audited-actions.md index 44246bd880..4c1eed89ca 100644 --- a/translations/es-ES/content/admin/user-management/audited-actions.md +++ b/translations/es-ES/content/admin/user-management/audited-actions.md @@ -80,7 +80,7 @@ versions: | Nombre | Descripción | | ------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.access` | La visbilidad de un repositorio cambió a privado{% if enterpriseServerVersions contains currentVersion %}, público,{% endif %} o interno. | -| `repo.archive` | 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.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. | @@ -89,7 +89,7 @@ versions: | `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.unarchive` | 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)".{% if enterpriseServerVersions contains currentVersion %} +| `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)".{% if enterpriseServerVersions contains currentVersion %} | `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)". | @@ -107,36 +107,36 @@ versions: #### Equipos -| Nombre | 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.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} -| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} +| Nombre | Descripción | +| -------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | Se agregó una cuenta de usuario o repositorio a un equipo. | +| `team.delete` | Se eliminó una cuenta de usuario o repositorio de un equipo.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `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.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | Se promovió a un usuario de miembro de equipo a mantenedor de equipo.{% endif %} #### Usuarios -| Nombre | Descripción | -| -------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | Se agregó una dirección de correo electrónico a una cuenta de usuario. | +| Nombre | 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`.{% if enterpriseServerVersions contains currentVersion %} | `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.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`.{% if enterpriseServerVersions contains currentVersion %} -| `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.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` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `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` | 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.login` | Un usuario inició sesión.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `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.{% if enterpriseServerVersions contains currentVersion %} | `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. | +| `user.unsuspend` | Un administrador del sitió dejó de suspender una cuenta de usuario. | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [llave de implementación]: /guides/managing-deploy-keys/#deploy-keys diff --git a/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md index e2c561804a..0ae2a13d6a 100644 --- a/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md @@ -76,10 +76,10 @@ El calificador `action` busca los eventos específicos, agrupados dentro de cate | Nombre de la categoría | Descripción | | ---------------------- | ----------------------------------------------------------------------------------------------------- | -| `hook` | Contiene todas las actividades relacionadas con los webhooks. | +| `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. | -| `team` | Contiene todas las actividades relacionadas con los equipos en tu organización. | +| `equipo` | Contiene todas las actividades relacionadas con los equipos en tu organización. | Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: diff --git a/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md index 7f9eaf22ac..4809037da2 100644 --- a/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md @@ -132,6 +132,6 @@ Antes de migrarte a un servidor de {% data variables.large_files.product_name_lo ``` {% endif %} -### Further reading +### Leer más - [Sitio del proyecto {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/) diff --git a/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 06def39d2c..91425fa143 100644 --- a/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -4,18 +4,18 @@ redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message/ - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance -intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' +intro: 'Puedes crear mensajes personalizados que los usuarios verán en {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -### About user messages +### Acerca de los mensajes de usuario -There are several types of user messages. -- Messages that appear on the {% if enterpriseServerVersions contains currentVersion %}sign in or {% endif %}sign out page{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -- Announcement banners, which appear at the top of every page{% endif %} +Hay varios tipos de mensajes de usuario. +- Los mensajes que aparecen en la {% if enterpriseServerVersions contains currentVersion %}página de ingreso o de {% endif %}salida{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mensajes obligatorios, los cuales aparecen una vez en una ventana emergente que debe descartarse{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Letreros de anuncio, los cuales aparecen en la parte superior de cada página{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -31,7 +31,7 @@ Puedes usar Markdown para dar formato al mensaje. Para obtener más información {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% if currentVersion ver_gt "enterprise-server@2.22" %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" %}A la derecha de{% else %}Debajo de{% endif %} "Página de inicio de sesión", da clic en **Agregar mensaje** o **Editar mensaje**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Botón de mensaje de Agregar{% else %}Editar{% endif %}](/assets/images/enterprise/site-admin-settings/edit-message.png) 6. En **Mensaje de inicio de sesión**, escribe el mensaje que quisieras que vean los usuarios. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} @@ -45,7 +45,7 @@ Puedes usar Markdown para dar formato al mensaje. Para obtener más información {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}A la derecha de{% else %}Debajo de{% endif %} "Página de salida", da clic en **Agregar mensaje** o **Editar mensaje**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) 6. En **Mensaje de cierre de sesión**, escribe el mensaje que quieras que vean los usuarios. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} @@ -54,23 +54,23 @@ Puedes usar Markdown para dar formato al mensaje. Para obtener más información {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -### Creating a mandatory message +### Crear un mensaje obligatorio -You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. Mandatory messages have a variety of uses. +Puedes crear un mensaje obligatorio que {% data variables.product.product_name %} mostrará a todos los usuarios la primera vez que inicien sesión después de que guardaste el mensaje. El mensaje aparece en una ventana emergente que el usuario deberá descartar antes de poder utilizar {% data variables.product.product_location %}. Los mensajes obligatorios tienen varios usos. -- Providing onboarding information for new employees -- Telling users how to get help with {% data variables.product.product_location %} -- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} +- Proporcinar información de integración para los empleados nuevos +- Decir a los usuarios cómo obtener ayuda con {% data variables.product.product_location %} +- Garantizar que todos los usuarios lean tus condiciones de servicio para utilizar {% data variables.product.product_location %} -If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. +Si incluyes cajas de verificación con lenguaje de marcado en el mensaje, todas ellas deberán seleccionarse antes de que el usuario pueda descartar el mensaje. Por ejemplo, si incluyes tus condiciones de servicio en el mensaje obligatorio, puede que necesites que cada usuario seleccione una casilla para confirmar que leyó dichas condiciones. -Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." +Cada vez que un usuario vea un mensaje obligatorio, se crea un evento de bitácora de auditoría. El evento incluye la versión del mensaje que vio el usuario. Para obtener más información, consulta la sección "[Acciones auditadas](/admin/user-management/audited-actions)". {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. To the right of "Mandatory message", click **Add message**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. Under "Mandatory message", in the text box, type your message. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +1. A la derecha de "Mensaje obligatorio", da clic en **Agregar mensaje**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Debajo de "Mensaje obligatorio", en la casilla de texto, teclea tu mensaje. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} @@ -81,8 +81,8 @@ Each time a user sees a mandatory message, an audit log event is created. The ev Puedes configurar un letrero de anuncio global para que se muestre a todos los usuarios en la parte superior de cada página. {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -You can also set an announcement banner -{% if enterpriseServerVersions contains currentVersion %} in the administrative shell using a command line utility or{% endif %} using the API. Para obtener más información, consulta las secciones {% if enterpriseServerVersions contains currentVersion %}"[Utilidades de la línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" y {% endif %}"[Administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". +También puedes configurar un letrero de anuncio +{% if enterpriseServerVersions contains currentVersion %} en el shell administrativo utilizando una utilidad de línea de comandos o{% endif %} utilizando la API. Para obtener más información, consulta las secciones {% if enterpriseServerVersions contains currentVersion %}"[Utilidades de la línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" y {% endif %}"[Administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". {% else %} También puedes configurar un letrero de anuncio en el shell administrativo utilizando una utilidad de línea de comandos. Para obtener más información, consulta la sección "[Utilidades de línea de comandos](/enterprise/admin/configuration/command-line-utilities#ghe-announce)". @@ -92,8 +92,8 @@ También puedes configurar un letrero de anuncio en el shell administrativo util {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}A la derecha de{% else %}Debajo de {% endif %} "Anuncio", da clic en **Agregar anuncio**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Debajo de "Anuncio", en el campo de texto, teclea el anuncio que quieras mostrar en un letrero. ![Campo de texto para ingresar el anuncio](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. ![Menú desplegable de calendario para elegir una fecha de vencimiento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +1. Opcionalmente, debajo de "Vence en", selecciona el menú desplegable de calendario y da clic en la fecha de vencimiento. ![Menú desplegable de calendario para elegir una fecha de vencimiento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md index 0f7f751d87..9e28efd1c0 100644 --- a/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md +++ b/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md @@ -68,6 +68,6 @@ versions: $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE ``` -### Further reading +### Leer más - "[Command-line-utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#import-and-export)" diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md index 9a2c87dbf5..5ca96a3f40 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise.md @@ -6,7 +6,7 @@ redirect_from: - /enterprise/admin/user-management/organizations-and-teams - /enterprise/admin/user-management/managing-organizations-in-your-enterprise intro: 'Las organizaciones son ideales para crear grupos diferentes de usuarios dentro de tu empresa, como divisiones o grupos trabajando en proyectos similares. {% if currentVersion == "github-ae@latest" %}Los usuarios de otras organizaciones pueden acceder a los repositorios internos{% else %}públicos e internos{% endif %} que pertenezcan a una organización diferente, pero solo los miembros de la organización que hayan recibido acceso a los repositorios privados podrán acceder a ellos.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md index f27afa34ea..b7e8798b72 100644 --- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise.md @@ -1,10 +1,10 @@ --- title: Administrar repositorios en tu empresa -intro: 'Puedes administrar la configuración disponible para los administradores de repositorios en tu empresa.' +intro: Puedes administrar la configuración disponible para los administradores de repositorios en tu empresa. redirect_from: - /enterprise/admin/user-management/repositories - /enterprise/admin/user-management/managing-repositories-in-your-enterprise -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md index 096ca667ce..7e107690e7 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise.md @@ -1,12 +1,12 @@ --- title: Administrar los usuarios en tu empresa -intro: 'Puedes auditar la actividad de los usuarios y administrar sus configuraciones de usuario.' +intro: Puedes auditar la actividad de los usuarios y administrar sus configuraciones de usuario. redirect_from: - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ - /enterprise/admin/user-management/basic-account-settings - /enterprise/admin/user-management/user-security - /enterprise/admin/user-management/managing-users-in-your-enterprise -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md index 41947e2981..74368fc5e5 100644 --- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise.md @@ -1,7 +1,7 @@ --- title: Migrar los datos desde y hacia tu empresa intro: 'Puedes exportar datos de usuario, organización y repositorio desde {% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_dotcom_the_website %}, y posteriormente importar los datos en {% data variables.product.product_location %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/ - /enterprise/admin/categories/migrations-and-upgrades/ diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md index e568daed8c..7e35ea49f0 100644 --- a/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -45,19 +45,19 @@ Los tipos de registro coinciden con los encontrados en los [datos migrados](/ent | Tipo de registro | Nombre del filtro | | --------------------------------------------------------------- | --------------------------------------------------- | -| Usuarios | `user` | +| Usuarios | `usuario` | | Organizaciones | `organization` | | Repositorios | `repositorio` | -| Equipos | `team` | -| Hitos | `milestone` | +| Equipos | `equipo` | +| Hitos | `hito` | | Tableros de proyecto | `project` | -| Problemas | `issue` | +| Problemas | `propuesta` | | Comentarios de propuestas | `comentario_propuesta` | | Solicitudes de cambios | `solicitud_extracción` | | Revisiones de solicitudes de extracción | `revisión_solicitud de extracción` | | Comentarios sobre confirmación de cambios | `comentario_confirmación de cambios` | | Comentarios sobre revisiones de solicitudes de extracción | `comentarios _revisiones_solicitudes de extracción` | -| Lanzamientos | `release` | +| Lanzamientos | `lanzamiento` | | Medidas adoptadas en las solicitudes de extracción o propuestas | `evento_propuesta` | | Ramas protegidas | `rama_protegida` | @@ -67,9 +67,9 @@ Los tipos de registro coinciden con los encontrados en los [datos migrados](/ent | --------------------- | ---------------------------------- | | `exportar` | El registro se exportará. | | `importar` | El registro se importará. | -| `asignar` | El registro se asignará. | +| `map` | El registro se asignará. | | `rename (renombrar)` | El registro se renombrará. | -| `merge` | El registro se fusionará. | +| `fusionar` | El registro se fusionará. | | `exportado` | El registro se exportó con éxito. | | `importado` | El registro se importó con éxito. | | `asignado` | El registro se asignó con éxito. | diff --git a/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md b/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md index 2abc0ae140..9de20598ca 100644 --- a/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,16 +33,16 @@ El script de migración no tendrá efecto si no tienes el modo privado habilitad 1. Conecta con el shell administrativo. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)." 2. Navega hacia el directorio `/data/github/current`. - ``` + ```shell cd /data/github/current ``` 3. Ejecuta el comando de migración. - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` Se mostrará el registro de salida en la terminal y quedará en `/tmp/convert_public_ghes_repos_to_internal.log`. -### Further reading +### Leer más - "[Habilitar el modo privado](/enterprise/admin/installation/enabling-private-mode)" diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md index c7055bfebf..0a1716988f 100644 --- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Monitorear la actividad en tu empresa -mapTopic: verdadero +mapTopic: true redirect_from: - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise diff --git a/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md index 1a4c3fb9cf..f0b5d902c7 100644 --- a/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md @@ -53,10 +53,10 @@ El archivo *conflicts.csv* contiene un *mapa de migración* de conflictos y acci | `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | | --------------- | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- | -| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `asignar` | -| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `asignar` | +| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `map` | +| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` | | `repositorio` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename (renombrar)` | -| `team` | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` | +| `equipo` | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `fusionar` | Cada fila de *conflicts.csv* proporciona la siguiente información: @@ -74,10 +74,10 @@ Hay varias acciones de asignación diferentes que `ghe-migrator` puede realizar | `Acción` | Descripción | Modelos aplicables | | --------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------- | | `importar` | (predeterminado) Los datos del origen se importan al destino. | Todos los tipos de registro | -| `asignar` | Los datos del origen se reemplazan por los datos existentes en el destino. | Usuarios, organizaciones, repositorios | +| `map` | Los datos del origen se reemplazan por los datos existentes en el destino. | Usuarios, organizaciones, repositorios | | `rename (renombrar)` | Los datos del origen se renombran y luego se copian en el destino. | Usuarios, organizaciones, repositorios | | `asignar_o_renombrar` | Si el destino existe, asignar a ese destino. De lo contrario, renombrar el modelo importado. | Usuarios | -| `merge` | Los datos del origen se combinan con los datos existentes en el destino. | Equipos | +| `fusionar` | Los datos del origen se combinan con los datos existentes en el destino. | Equipos | **Te recomendamos ampliamente que revises el archivo *conflicts.csv* y que utilices [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) para garantizar que se estén tomando las acciones adecuadas.** Si todo se ve bien, puedes continuar con las acciones para "[Migrar los datos a tu empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)". @@ -90,13 +90,13 @@ Por ejemplo, supongamos que observas que el usuario `octocat` del origen se est | `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | | --------------- | ------------------------------------ | ----------------------------------- | -------------------- | -| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `asignar` | +| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `map` | Puedes optar por asignar el usuario a un usuario diferente en el destino. Supongamos que sabes que `octocat` en realidad debe ser `monalisa` en el destino. Puedes cambiar la columna `target_url` en *conflicts.csv* a `monalisa`: | `nombre_modelo` | `url_origen` | `url_destino` | `recommended_action` | | --------------- | ------------------------------------ | ------------------------------------ | -------------------- | -| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `asignar` | +| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `map` | Como otro ejemplo, si deseas cambiar el nombre del repositorio `octo-org/widgets` a `octo-org/amazing-widgets` en la instancia de destino, cambia la `target_url` a `octo-org/amazing-widgets` y la `recommended_action` a `rename`: @@ -122,7 +122,7 @@ Por ejemplo, para cambiar el nombre del usuario `octocat` a `monalisa` en el `ht | `nombre_modelo` | `url_origen` | `url_destino` | `state` | | --------------- | ------------------------------------ | ------------------------------------ | -------------------- | -| `user` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `rename (renombrar)` | +| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `rename (renombrar)` | Se puede usar el mismo proceso para crear asignaciones para cada registro que admita asignaciones personalizadas. Para obtener más información, consulta [nuestra tabla sobre las posibles asignaciones de registro](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type). diff --git a/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md index 33604f4928..46dca6e322 100644 --- a/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md +++ b/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md @@ -55,7 +55,7 @@ Para ver las personas que fueron automáticamente eliminadas de tu organización Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización. -### Further reading +### Leer más - "[Ver si los usuarios de tu organización tienen la 2FA activada](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" - "[Asegurar tu cuenta con autenticación de dos factores (2FA)](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa)" diff --git a/translations/es-ES/content/admin/user-management/searching-the-audit-log.md b/translations/es-ES/content/admin/user-management/searching-the-audit-log.md index 361651f538..17e6bad684 100644 --- a/translations/es-ES/content/admin/user-management/searching-the-audit-log.md +++ b/translations/es-ES/content/admin/user-management/searching-the-audit-log.md @@ -21,7 +21,7 @@ Redacta una consulta de búsqueda de uno o más pares de clave-valor separados p | `oauth_app_id` | ID de la aplicación OAuth asociada con la acción | | `Acción` | Nombre de la acción auditada | | `user_id` | ID del usuario afectado por la acción | -| `user` | Nombre del usuario afectado por la acción | +| `usuario` | Nombre del usuario afectado por la acción | | `repo_id` | ID del repositorio afectado por la acción (si corresponde) | | `repo` | Nombre del repositorio afectado por la acción (si corresponde) | | `actor_ip` | Dirección IP desde donde se inició la acción | diff --git a/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md index dc918269e9..98c0bdfa78 100644 --- a/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md @@ -82,5 +82,5 @@ Puedes crear un mensaje personalizado que los usuarios suspendidos verán cuando $ ghe-user-unsuspend username ``` -### Further reading +### Leer más - "[Suspender a un usuario](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/es-ES/content/admin/user-management/viewing-push-logs.md b/translations/es-ES/content/admin/user-management/viewing-push-logs.md index d2cb7abd70..1d660c6e26 100644 --- a/translations/es-ES/content/admin/user-management/viewing-push-logs.md +++ b/translations/es-ES/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ Las entradas de registro de subida muestran: ### Ver registros de subida de un repositorio +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. 1. Navegar a un repositorio. -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. In the upper-right corner of the repository's page, click +{% octicon "rocket" aria-label="The rocket ship" %}. + ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. En la barra lateral izquierda, haz clic en **Push Log (Registro de subida)**. ![Pestaña de registro de subida](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### Ver registros de subida de un repositorio en la línea de comando -1. SSH en tu aparato. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -2. En el repositorio Git adecuado, abre el archivo de registro de auditoría: +{% data reusables.enterprise_installation.ssh-into-instance %} +1. En el repositorio Git adecuado, abre el archivo de registro de auditoría: ```shell ghe-repo owner/repository -c "less audit_log" ``` diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md index ff8247faf3..8a67d247e8 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories.md @@ -1,7 +1,7 @@ --- title: Agregar y clonar repositorios intro: 'Añadir repositorios existentes desde su equipo local a {% data variables.product.prodname_desktop %}o clonar repositorios desde {% data variables.product.product_name %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /desktop/contributing-to-projects/adding-and-cloning-repositories versions: diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md index 937a43c59c..6850871444 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop.md @@ -10,7 +10,7 @@ versions: {% mac %} -1. In the **Repository** menu, click **Repository Settings...**. ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-mac.png) +1. En el menú de **Repositorio**, da clic en **Configuración de repositorio...**. ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-mac.png) 2. En el campo **Primary remote repository** (Repositorio remoto principal) escribe la URL que desees. ![Campo Primary remote repository (Repositorio remoto principal)](/assets/images/help/desktop/repository-settings-remote-mac.png) 3. Haz clic en **Save ** (guardar). ![El botón Save (Guardar)](/assets/images/help/desktop/repository-settings-save-mac.png) @@ -18,7 +18,7 @@ versions: {% windows %} -1. In the **Repository** menu, click **Repository settings...**. ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-win.png) +1. En el menú de **Repositorio**, da clic en **Configuración de repositorio...**. ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-win.png) 2. En el campo **Primary remote repository** (Repositorio remoto principal) escribe la URL que desees. ![Campo Primary remote repository (Repositorio remoto principal)](/assets/images/help/desktop/repository-settings-remote-win.png) 3. Haz clic en **Save ** (guardar). ![El botón Save (Guardar)](/assets/images/help/desktop/repository-settings-save-win.png) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md index aa5e79ff74..ab7eefca9f 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request.md @@ -70,7 +70,7 @@ Amtes de crear una solicitud de extracción, necesitarás subir los cambios a un {% endwindows %} -### Further reading +### Leer más - "[Informe de problemas](/github/getting-started-with-github/github-glossary#issue)" en el glosario de {% data variables.product.prodname_dotcom %} - "[Solicitud de extracción](/github/getting-started-with-github/github-glossary#pull-request)" en el glosario de {% data variables.product.prodname_dotcom %} - "[Rama base](/github/getting-started-with-github/github-glossary#base-branch)" en el glosario de {% data variables.product.prodname_dotcom %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md index 1430d50319..1680ae4e48 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github.md @@ -1,7 +1,7 @@ --- title: Mantener tu repositorio local sincronizado con GitHub intro: 'Puedes mantener tu repositorio local sincronizado con tu repositorio remoto mientras actualizas cualquiera de estos. En Git, *remoto* hace referencia al servidor donde se almacena tu código. En tu caso, ese servidor es un repositorio en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md index abce8123be..2e843a2501 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch.md @@ -1,7 +1,7 @@ --- title: Realizar cambios en una rama intro: 'Usa tu editor de texto favorito, como [Atom](https://atom.io/), para realizar cambios en el proyecto y, a continuación, utiliza {% data variables.product.prodname_desktop %} para visualizar confirmaciones útiles.' -mapTopic: verdadero +mapTopic: true redirect_from: - /desktop/contributing-to-projects/making-changes-in-a-branch versions: diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md index 8a048e8f98..8dfd821eb8 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-branches.md @@ -110,7 +110,7 @@ No puedes borrar una rama que esté actualmente asociada con una solicitud de ex {% endwindows %} -### Further reading +### Leer más - [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 %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index a9b79d1937..bf6dc75875 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ versions: ![Visualizar una etiqueta en el historial](/assets/images/help/desktop/viewing-tags-in-history.png) 3. Todas las etiquetas asociadas con la confirmación se pueden ver en los metadatos de dicha confirmación. ![Visualizar una etiqueta en la confirmación](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### Borrar las etiquetas + +{% note %} + +**Nota**: Solo puedes borrar las etiquetas que se asocian con las confirmaciones que aún no se hayan subido. + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md index 3923e4c739..7393543a2a 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md @@ -34,6 +34,6 @@ Si configuras a {% data variables.large_files.product_name_long %} para rastrear 2. Si {% data variables.product.prodname_desktop %} te pide traer las confirmaciones nuevas de la rama remota, da clic en **Recuperar**. ![El botón de recuperar](/assets/images/help/desktop/fetch-newer-commits.png) 3. Opcionalmente, da clic en **Crear Solicitud de Extracción** para abrir una solicitud de extracción y colaborar en tus cambios. 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)" ![El botón de crear solicitud de extracción](/assets/images/help/desktop/create-pull-request.png) -### Further reading +### Leer más - "[Cargar](/github/getting-started-with-github/github-glossary/#push)" en el glosario de {% data variables.product.prodname_dotcom %} - "[Confirmar y revisar los cambios hechos a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)" diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md index 706ce8c4bd..463a805877 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history.md @@ -18,6 +18,6 @@ Cada confirmación muestra: 2. En la pestaña **History** (Historial), haz clic en la confirmación que deseas revisar. ![Una confirmación en la pestaña History (Historial)](/assets/images/help/desktop/branch-history-commit.png) 3. Si existen múltiples archivos en la confirmación, haz clic en un archivo individual para ver los cambios que se realizan a ese archivo en esa confirmación. ![Un archivo en la confirmación](/assets/images/help/desktop/branch-history-file.png) -### Further reading +### Leer más - [Sincronizar tu rama](/desktop/guides/contributing-to-projects/syncing-your-branch/)" diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md index 068be04af0..686b336ac3 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise.md @@ -1,7 +1,7 @@ --- title: Trabajar con tu repositorio remoto en GitHub o GitHub Enterprise intro: 'A medida que realizas cambios a tu proyecto localmente, puedes mantenerlos actualizados con tu repositorio remoto. En Git, *remoto* hace referencia al servidor donde se almacena tu código. En tu caso, ese servidor es un repositorio en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise versions: diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md index db2f0ede51..4bc0363a39 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md @@ -13,5 +13,5 @@ Después de que te autentiques en {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_desktop %} se conecta con {% data variables.product.prodname_dotcom %} utilizando HTTPS. Si utilizas {% data variables.product.prodname_desktop %} para acceder a los repositorios que se clonaron utilizando SSH, podrías encontrar errores. Para conectarte a un repositorio que se clonó utilizando SSH, cambia las URL del destino remoto. Para obtener más información, consulta "[Changing a remote's URL](/github/using-git/changing-a-remotes-url) (Cambiar la URL de un remoto). -### Further reading +### Leer más - "[Clonar y bifurcar repositorios desde GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md index 69ca9f3449..b6b664dd0e 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop.md @@ -14,6 +14,6 @@ Para utilizar {% data variables.large_files.product_name_short %} con {% data va Después de que configuras a {% data variables.large_files.product_name_short %} para rastrear los archivos en un repositorio, puedes acceder sin problema y administrar archivos grandes con {% data variables.product.prodname_desktop %} como lo harías con cualquier otro archivo en el repositorio. -### Further reading +### Leer más - "[Trabajar con archivos grandes](/github/managing-large-files/working-with-large-files)" - "[Control de versiones de archivos grandes](/github/managing-large-files/versioning-large-files)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md index 378c40d2ab..19512c9ded 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/authenticating-to-github.md @@ -182,5 +182,5 @@ Si tu nombre de usuario de Windows tiene caracteres extendidos de Unicode, esto {% endwindows %} -### Further reading +### Leer más - "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md index 98483f273f..6221d9e1d2 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop.md @@ -1,7 +1,7 @@ --- title: Configurar y personalizar GitHub Desktop intro: 'Cómo configurar Git, conectar tu editor predeterminado y personalizar las opciones para alinear GitHub Desktop con tu flujo de trabajo.' -mapTopic: verdadero +mapTopic: true redirect_from: - /desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop versions: diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md index 32d7544d1f..ed658e7c3a 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-basic-settings.md @@ -23,6 +23,6 @@ versions: {% endwindows %} -### Further reading +### Leer más - "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/guides/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md index e87dc1321d..ce722c9b82 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop.md @@ -54,7 +54,7 @@ versions: {% endwindows %} -### Further reading +### Leer más - [Agregar una dirección de correo electrónico a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account/)" - "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)." diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md index ddd3c4dcd4..12785706bf 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md @@ -91,7 +91,7 @@ Ahora que creaste y publicaste tu repositorio, estás listo para hacer cambios e ### Conclusión Ya creaste un repositorio, lo publicaste en {% data variables.product.product_name %}, hiciste una confirmación y subiste tus cambios a {% data variables.product.product_name %}. Puedes seguir este flujo de trabajo cuando colabores con otros proyectos que crees o en los cuales colabores. -### Further reading +### Leer más - "[Aprender más sobre Git](/github/using-git/learning-about-git)" - "[Aprender más sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" - "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md index 91f180beb2..38e7f93e1d 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md @@ -102,6 +102,6 @@ Puedes ver tus propias solicitudes de extracción o las de tus colaboradores en #### Mantener tu repositorio local sincronizado Cuando haces cambios a tus repositorios locales o cuando otros hacen cambios a los repositorios remotos, necesitarás sincronizar tu copia local del proyecto con el repositorio remoto. {% data variables.product.prodname_desktop %} puede mantener sincronizada tu copia local de un proyecto con la versión remota al subir y extraer las confirmaciones. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)". -### Further reading +### Leer más - "[Instalar y autenticarse en {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop)" - "[Colaborar y contribuir utilizando {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop)" diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md index 71b7006814..4a33460c71 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop.md @@ -1,7 +1,7 @@ --- title: Cómo instalar y autenticarse en GitHub Desktop intro: Instalar GitHub Desktop y conectar tus cuentas de GitHub y GitHub Enterprise. -mapTopic: verdadero +mapTopic: true redirect_from: - /desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop versions: diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md index a309a06077..9e1f79dc7b 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview.md @@ -1,7 +1,7 @@ --- title: Resumen intro: Conozca GitHub Desktop y cree rápidamente su primer repositorio. -mapTopic: verdadero +mapTopic: true redirect_from: - /desktop/getting-started-with-github-desktop/overview versions: diff --git a/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md index 01776be235..a3a6dd3005 100644 --- a/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md @@ -53,7 +53,7 @@ Cuando tu GitHub App especifica un parámetro de `login`, solicita a los usuario ##### Parámetros -| Nombre | Type | Descripción | +| Nombre | Tipo | Descripción | | -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `client_id` | `secuencia` | **Requerido**. La ID de ciente que recibiste de GitHub cuando te {% if currentVersion == "free-pro-team@latest" %}[registraste](https://github.com/settings/applications/new){% else %}registraste{% endif %}. | | `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Consulta los siguientes detalles sobre [urls de redireccionamiento](#redirect-urls). | @@ -72,7 +72,7 @@ Intercambia este `code` por un token de acceso: ##### Parámetros -| Nombre | Type | Descripción | +| Nombre | Tipo | Descripción | | --------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. | | `client_secret` | `secuencia` | **Requerido.** El secreto del cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. | @@ -138,7 +138,7 @@ Tu app debe solicitar un código de verificación de usuario y una URL de verifi ##### Parámetros de entrada -| Nombre | Type | Descripción | +| Nombre | Tipo | Descripción | | ----------- | ----------- | ------------------------------------------------------------------------------------------------------- | | `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu app. | | `scope` | `secuencia` | El alcance al cual está solicitando acceso tu app. | @@ -169,7 +169,7 @@ Tu app debe solicitar un código de verificación de usuario y una URL de verifi ##### Parámetros de respuesta -| Nombre | Type | Descripción | +| Nombre | Tipo | Descripción | | ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `device_code` | `secuencia` | El código de verificación de dispositivo es de 40 caracteres y se utiliza para verificar dicho dispositivo. | | `user_code` | `secuencia` | El código de verificación de usuario se muestra en el dispositivo para que el usuario pueda ingresar dicho código en un buscador. El código es de 8 caracteres con un guión medio a la mitad. | @@ -195,7 +195,7 @@ Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se ##### Parámetros de entrada -| Nombre | Type | Descripción | +| Nombre | Tipo | Descripción | | ------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. | | `device_code` | `secuencia` | **Requerido.** El código de verificación del dispositivo que recibiste de la solicitud de `POST {% data variables.product.oauth_host_code %}/login/device/code`. | @@ -213,7 +213,7 @@ Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se #### Límites de tasa para el flujo del dispositivo -When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. +Cuando un usuario emite el código de verificación en el buscador, hay un límite de tasa de 50 emisiones en una hora por aplicación. Si realizas más de una solicitud de acceso con token (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) dentro del marco de tiempo mínimo requerido entre solicitudes (o `interval`), alcanzarás el límite de tasa y recibirás una respuesta de error de `slow_down`. La respuesta de error `slow_down` agrega 5 segundos al último `interval`. Para obtener más información, consulta los [Errores para el flujo del dispositivo](#errors-for-the-device-flow). diff --git a/translations/es-ES/content/developers/apps/building-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps.md index cdbbc6cc28..60348da29c 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps.md @@ -1,7 +1,7 @@ --- title: Crear GitHub Apps intro: Puedes crear GitHub Apps para uso personal o público. Aprende como registrar y configurar permisos y opciones de autenticación para GitHub Apps. -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/building-integrations/setting-up-and-registering-github-apps/ - /apps/building-github-apps diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps.md index a76fe5f07b..540dd5f976 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps.md @@ -1,7 +1,7 @@ --- title: Crear Apps de OAuth intro: Puedes crear Apps de OAuth para uso personal o público. Aprende como registrar y configurar permisos y opciones de autenticación para Apps de OAuth. -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/ - /apps/building-oauth-apps diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md index 153ab8defd..2b6b202e45 100644 --- a/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -56,12 +56,12 @@ Se redirigirá al creador de la app a una página de GitHub en donde encontrará | --------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name (nombre)` | `secuencia` | El nombre dela GitHub App. | | `url` | `secuencia` | **Requerido.** La página principal de tu GitHub App. | - | `hook_attributes` | `object` | La configuración del webhook de la GitHub App. | + | `hook_attributes` | `objeto` | La configuración del webhook de la GitHub App. | | `redirect_url` | `secuencia` | La URL completa a la cual se redireccionará a la persona después de que instale la GitHub App. | - | `description` | `secuencia` | Una descripción de la GitHub App. | + | `descripción` | `secuencia` | Una descripción de la GitHub App. | | `public` | `boolean` | Configúralo como `true` cuando tu GitHub App esté disponible al público o como `false` si solo puede acceder el propietario de la misma. | | `default_events` | `arreglo` | La lista de [eventos](/webhooks/event-payloads) a la cual se suscribe la GitHub App. | - | `default_permissions` | `object` | El conjunto de [permisos](/rest/reference/permissions-required-for-github-apps) que requiere la GitHub App. El formato del objeto utiliza el nombre del permiso para la clave (por ejemplo, `issues`) y el tipo de acceso para el valor (por ejemplo, `write`). | + | `default_permissions` | `objeto` | El conjunto de [permisos](/rest/reference/permissions-required-for-github-apps) que requiere la GitHub App. El formato del objeto utiliza el nombre del permiso para la clave (por ejemplo, `issues`) y el tipo de acceso para el valor (por ejemplo, `write`). | El objeto `hook_attributes` tiene la siguiente clave: @@ -80,7 +80,7 @@ El objeto `hook_attributes` tiene la siguiente clave: Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de usuario: -``` +```html Create a GitHub App Manifest:
@@ -111,7 +111,7 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s ``` Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de organización. Reemplaza a `ORGANIZATION` con el nombre de la cuenta de organización en donde quieras crear la app. -``` +```html Create a GitHub App Manifest:
diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md index 6a3b153054..50e2d66b94 100644 --- a/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -31,7 +31,7 @@ La lista completa de parámetros de consulta, permisos y eventos disponibles se | Nombre | Type | Descripción | | -------------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name (nombre)` | `secuencia` | El nombre de la {% data variables.product.prodname_github_app %}. Pónle un nombre claro y breve a tu app. Tu app no puede tener el mismo nombre que un usuario de GitHub, a menos de que sea tu propio nombre de usuario u organización. Una versión simplificada del nombre de tu aplicación se mostrará en la interface de usuario cuando tu integración tome alguna acción. | - | `description` | `secuencia` | Una descripción de la {% data variables.product.prodname_github_app %}. | + | `descripción` | `secuencia` | Una descripción de la {% data variables.product.prodname_github_app %}. | | `url` | `secuencia` | La URL complea de la página principal del sitio web de tu {% data variables.product.prodname_github_app %}. | | `callback_url` | `secuencia` | La URL completa a la cual se redirigirá después de que alguien autorice la instalación. Esta URL se utiliza si tu app necesita identificar y autorizar las solicitudes de usuario a servidor. | | `request_oauth_on_install` | `boolean` | Si tu app autoriza a los usuarios mediante el flujo de OAuth, puedes configurar esta opción como `true` para permitir que las personas autoricen la app cuando la instalen, lo cual te ahorra un paso. Si seleccionas esta opción, la `setup_url` deja de estar disponible y se redirigirá a los usuarios a tu `callback_url` después de que instalen la app. | @@ -41,7 +41,7 @@ La lista completa de parámetros de consulta, permisos y eventos disponibles se | `webhook_url` | `secuencia` | La URL completa a la cual quisieras enviar cargas útiles de eventos de webhook. | | `webhook_secret` | `secuencia` | Puedes especificar un secreto para asegurar tus webhooks. Consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)" para obtener más detalles. | | `events` | `conjunto de secuencias` | Eventos de webhook. Algunos eventos de webhook requieren asignar permisos de `read` o de `write` a un recurso antes de que puedas seleccionar el evento cuando registras una {% data variables.product.prodname_github_app %} nueva. Consulta la sección "[Eventos de webhook de las {% data variables.product.prodname_github_app %}](#github-app-webhook-events)" para encontrar los eventos disponibles y sus permisos requeridos. Puedes seleccionar eventos múltiples en una secuencia de consulta. Por ejemplo, `events[]=public&events[]=label`. | - | `domain` | `secuencia` | La URL de una referencia de contenido. | + | `dominio` | `secuencia` | La URL de una referencia de contenido. | | `single_file_name` | `secuencia` | Este es un permiso con alcance corto que permite a la app acceder a un solo archivo en cualquier repositorio. Cuando configuras el permiso de `single_file` en `read` o `write`, este campo proporciona la ruta al archivo único que administrará tu {% data variables.product.prodname_github_app %}. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Si necesitas administrar varios archivos, consulta la opción `single_file_paths` a continuación. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | `single_file_paths` | `conjunto de secuencias` | Esto permite a la app acceder hasta a 10 archivos especificos en un repositorio. Cuando configuras el permiso `single_file` en `read` o `write`, este arreglo puede almacenar las rutas de hasta diez archivos que administrará tu {% data variables.product.prodname_github_app %}. Estos archivos reciben el mismo permiso que se configuró para `single_file`, y no tienen permisos individuales por separado. Cuando dos o mas archivos se configuran, la API devuelve `multiple_single_files=true`, de lo contrario, devuelve `multiple_single_files=false`.{% endif %} @@ -63,7 +63,7 @@ Puedes seleccionar los permisos en una secuencia de consulta utilizando los nomb | [`propuestas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Otorga acceso a la [API de Informe de problemas](/rest/reference/issues). Puede ser uno de entre `none`, `read`, o `write`. | | [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Otorga acceso a la [API de Llaves Públicas](/rest/reference/users#keys). Puede ser uno de entre `none`, `read`, o `write`. | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Otorga acceso para administrar los miembros de una organización. Puede ser uno de entre: `none`, `read`, o `write`.{% if currentVersion == "free-pro-team@latest" %} -| [`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Otorga acceso a las terminales de solo lectura que no filtran datos sensibles. Puede ser `read` o `none`. Su valor predeterminado es `read` cuando configuras cualquier permiso, o bien, `none` cuando no especificas ningún permiso para la {% data variables.product.prodname_github_app %}. | +| [`metadatos`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Otorga acceso a las terminales de solo lectura que no filtran datos sensibles. Puede ser `read` o `none`. Su valor predeterminado es `read` cuando configuras cualquier permiso, o bien, `none` cuando no especificas ningún permiso para la {% data variables.product.prodname_github_app %}. | | [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Otorga acceso a la terminal "[Actualizar una organización](/rest/reference/orgs#update-an-organization)" y a la [API de Restricciones de Interacción en la Organización](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Puede ser uno de entre `none`, `read`, o `write`.{% endif %} | [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Otorga acceso a la [API de Webhooks de la Organización](/rest/reference/orgs#webhooks/). Puede ser uno de entre `none`, `read`, o `write`. | | `organization_plan` | Otorga acceso para obtener información acerca del plan de una organización que utilice la terminal "[Obtener una organización](/rest/reference/orgs#get-an-organization)". Puede ser uno de entre `none` o `read`. | @@ -81,7 +81,7 @@ Puedes seleccionar los permisos en una secuencia de consulta utilizando los nomb | [`estados`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Otorga acceso a la [API de Estados](/rest/reference/repos#statuses). Puede ser uno de entre `none`, `read`, o `write`. | | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Otorga acceso a la [API de debates de equipo](/rest/reference/teams#discussions) y a la [API de comentarios en debates de equipo](/rest/reference/teams#discussion-comments). Puede ser uno de entre: `none`, `read`, o `write`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %} | `vulnerability_alerts` | Otorga acceso para recibir alertas de seguridad para las dependencias vulnerables en un repositorio. Consulta la sección "[Acerca de las alertas de seguridad para las dependencias vulnerables](/articles/about-security-alerts-for-vulnerable-dependencies)" para aprender más. Puede ser uno de entre: `none` o `read`.{% endif %} -| `watching` | Otorga acceso a la lista y cambia los repositorios a los que un usuario está suscrito. Puede ser uno de entre `none`, `read`, o `write`. | +| `observando` | Otorga acceso a la lista y cambia los repositorios a los que un usuario está suscrito. Puede ser uno de entre `none`, `read`, o `write`. | ### Eventos de webhook de {% data variables.product.prodname_github_app %} @@ -92,32 +92,32 @@ Puedes seleccionar los permisos en una secuencia de consulta utilizando los nomb | [`comentario_confirmación de cambios`](/webhooks/event-payloads/#commit_comment) | `contenidos` | {% data reusables.webhooks.commit_comment_short_desc %} | [`content_reference`](/webhooks/event-payloads/#content_reference) | `content_references` | {% data reusables.webhooks.content_reference_short_desc %} | [`create (crear)`](/webhooks/event-payloads/#create) | `contenidos` | {% data reusables.webhooks.create_short_desc %} -| [`eliminar`](/webhooks/event-payloads/#delete) | `contenidos` | {% data reusables.webhooks.delete_short_desc %} +| [`delete`](/webhooks/event-payloads/#delete) | `contenidos` | {% data reusables.webhooks.delete_short_desc %} | [`deployment`](/webhooks/event-payloads/#deployment) | `implementaciones` | {% data reusables.webhooks.deployment_short_desc %} | [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `implementaciones` | {% data reusables.webhooks.deployment_status_short_desc %} -| [`fork`](/webhooks/event-payloads/#fork) | `contenidos` | {% data reusables.webhooks.fork_short_desc %} +| [`bifurcación`](/webhooks/event-payloads/#fork) | `contenidos` | {% data reusables.webhooks.fork_short_desc %} | [`gollum`](/webhooks/event-payloads/#gollum) | `contenidos` | {% data reusables.webhooks.gollum_short_desc %} | [`propuestas`](/webhooks/event-payloads/#issues) | `propuestas` | {% data reusables.webhooks.issues_short_desc %} | [`comentario_propuesta`](/webhooks/event-payloads/#issue_comment) | `propuestas` | {% 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 %} +| [`etiqueta`](/webhooks/event-payloads/#label) | `metadatos` | {% data reusables.webhooks.label_short_desc %} +| [`miembro`](/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) | `solicitud_extracción` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} +| [`hito`](/webhooks/event-payloads/#milestone) | `solicitud_extracción` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} | [`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) | `páginas` | {% data reusables.webhooks.page_build_short_desc %} | [`project`](/webhooks/event-payloads/#project) | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_short_desc %} | [`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} | [`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} -| [`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %} +| [`public`](/webhooks/event-payloads/#public) | `metadatos` | {% data reusables.webhooks.public_short_desc %} | [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} | [`revisión_solicitud de extracción`](/webhooks/event-payloads/#pull_request_review) | `solicitud_extracción` | {% data reusables.webhooks.pull_request_review_short_desc %} | [`comentarios _revisiones_solicitudes de extracción`](/webhooks/event-payloads/#pull_request_review_comment) | `solicitud_extracción` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} -| [`push`](/webhooks/event-payloads/#push) | `contenidos` | {% data reusables.webhooks.push_short_desc %} -| [`release`](/webhooks/event-payloads/#release) | `contenidos` | {% data reusables.webhooks.release_short_desc %} -| [`repositorio`](/webhooks/event-payloads/#repository) | `metadata` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} +| [`subir`](/webhooks/event-payloads/#push) | `contenidos` | {% data reusables.webhooks.push_short_desc %} +| [`lanzamiento`](/webhooks/event-payloads/#release) | `contenidos` | {% data reusables.webhooks.release_short_desc %} +| [`repositorio`](/webhooks/event-payloads/#repository) | `metadatos` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} | [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contenidos` | Permite que los integradores que utilizan GitHub Actions activen eventos personalizados.{% endif %} -| [`status`](/webhooks/event-payloads/#status) | `estados` | {% data reusables.webhooks.status_short_desc %} -| [`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} +| [`estado`](/webhooks/event-payloads/#status) | `estados` | {% data reusables.webhooks.status_short_desc %} +| [`equipo`](/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 %} +| [`observar`](/webhooks/event-payloads/#watch) | `metadatos` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 191979d297..9be31f856a 100644 --- a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ Un servidor de IC hospeda código que ejecuta pruebas de IC, tal como los limpí La [API de Verificaciones](/rest/reference/checks) te permite configurar las pruebas de IC que se ejecutan automáticamente contra cada confirmación de código en un repositorio. La API de Verificaciones reporta información detallada acerca de cada verificación en GitHub dentro de la pestaña de **Verificaciones** de las solicitudes de extracción. Con la API de verificaciones, puedes crear anotaciones con detalles adicionales para líneas específicas de código. Las anotaciones se encuentran visibles en la pestaña de **Verificaciones**. Cuando creas una anotación para un archivo que es parte de la solicitud de extracción, estas también se muestran en la pestaña **Archivos cambiados**. -Un _conjunto de verificaciones_ es un grupo de _ejecuciones de verificación_ (pruebas de IC individuales). Tanto estos conjuntos como las ejecuciones contienen _estados_ que pueden visualizarse en la solicitud de extracción en GitHub. Puedes utilizar estados para determinar cuando una confirmación de código introduce errores. El utilizar estos estados con [ramas protegidas](/rest/reference/repos#branches) puede prevenir que las personas fusionen solicitudes de extracción prematuramente. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. +Un _conjunto de verificaciones_ es un grupo de _ejecuciones de verificación_ (pruebas de IC individuales). Tanto estos conjuntos como las ejecuciones contienen _estados_ que pueden visualizarse en la solicitud de extracción en GitHub. Puedes utilizar estados para determinar cuando una confirmación de código introduce errores. El utilizar estos estados con [ramas protegidas](/rest/reference/repos#branches) puede prevenir que las personas fusionen solicitudes de extracción prematuramente. Para encontrar más detalles, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". La API de Verificaciones envía el [evento de webhook `check_suite`](/webhooks/event-payloads/#check_suite) a todas las GitHub Apps que se instalan en un repositorio cada vez que se carga código nuevo a éste. Para recibir todas las acciones de los eventos de la API de Verificaciones, la app debe contar con el permiso `checks:write`. GitHub crea los eventos de `check_suite` automáticamente para las nuevas confirmaciones de código en un repositorio utilizando el flujo predeterminado, aunque puedes [Actualizar las preferencias del repositorio para los conjuntos de verificaciones](/rest/reference/checks#update-repository-preferences-for-check-suites) si así lo quieres. Aquí te mostramos cómo funciona el flujo predeterminado: @@ -435,7 +435,7 @@ El código anterior obtiene el nombre completo del repositorio y el SHA de encab ### Paso 2.3. Ejecutar RuboCop -¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Ahora te meterás en los detalles más minusciosos del [Limpiador de RuboCop](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) y de las [Anotaciones de la API de Verificaciones](/rest/reference/checks#create-a-check-run). +¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). El siguiente código ejecuta RuboCop y guarda los errores de estilo en el código con un formato JSON. Agrega el código siguiente debajo de la llamada a `clone_repository` que agregaste en el [paso anterior](#step-22-cloning-the-repository) y sobre el código que actualiza la ejecución de verificación para completarse. @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -Este código utiliza RuboCop en todos los archivos dentro del directorio del repositorio. La opción `--format json` es una manera útil de guardar una copia de los resultados que se han limpiado en un formato que pueda analizar la máquina. Consulta los [Documentos de RuboCop](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) para obtener más detalles y un ejemplo del formato en JSON. +Este código utiliza RuboCop en todos los archivos dentro del directorio del repositorio. La opción `--format json` es una manera útil de guardar una copia de los resultados que se han limpiado en un formato que pueda analizar la máquina. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. Ya que este código almacena los resultados de RuboCop en una variable de `@report`, puede eliminar la salida del repositorio con seguridad. Este código también analiza el JSON para que puedas acceder fácilmente a las claves y valores en tu GitHub App utilizando la variable `@output`. @@ -588,7 +588,7 @@ Este código limita la cantidad total de anotaciones a 50. Pero puedes modificar Cuando la `offense_count` es de cero, la prueba de IC se muestra como `success`. Si hay errores, este código configura la conclusión como `neutral` para prevenir los errores estrictamente implementados desde los limpiadores de código. Pero puedes cambiar la conclusión a `failure` si quisieras garantizar que el conjunto de verificaciones falle cuando existan errores de limpieza. -Cuando se reportan los errores, el código anterior itera a través de la matriz de `files` en el reporte de RuboCop. Para cada archivo, extrae la ruta del mismo y configura el nivel de anotcación en `notice`. Puedes incluso ir más allá y especificar ls niveles de advertencia para cada tipo de [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), pero para simplificar todo aún más en esta guía rápida, todos los errores se configurarán en un nivel de `notice`. +Cuando se reportan los errores, el código anterior itera a través de la matriz de `files` en el reporte de RuboCop. Para cada archivo, extrae la ruta del mismo y configura el nivel de anotcación en `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. Este código también itera a través de cada error en la matriz de `offenses` y recolecta la ubicación de la falta y el mensaje de error. Después de extraer la información requerida, el código crea una anotación para cada error y lo almacena en la matriz de `annotations`. Ya que las anotaciones solo son compatibles con las columnas de inicio y fin en la misma línea, `start_column` y `end_column` se agregarán únicamente al objeto `annotation` si los valores iniciales y finales de la línea son los mismos. @@ -718,13 +718,13 @@ Si las anotaciones se relacionan con un archivo que ya se incluya en la solicitu Si has llegado hasta aquí, ¡excelente! 👏 Ya creaste una prueba de IC. En esta sección vas a agregar una característica más que utiliza a RuboCop para corregir automáticamente los errores que encuentre. Ya agregaste el botón de "Corregir esto" en la [sección anterior](#step-25-updating-the-check-run-with-ci-test-results). Ahora agregarás el código para gestionar el evento de ejecución de verificación `requested_action` que se activa cuando alguien da clic en dicho botón. -La herramienta de RuboCop [ofrece](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) la opción de línea de comandos `--auto-correct` para corregir automáticamente los errores que encuentre. Cuado utilizas la característica de `--auto-correct`, se aplican las actualizaciones en los archivos locales del servidor. Necesitarás cargar los cambios a GitHub después de que RuboCop haga su magia. +The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. Cuado utilizas la característica de `--auto-correct`, se aplican las actualizaciones en los archivos locales del servidor. Necesitarás cargar los cambios a GitHub después de que RuboCop haga su magia. Para cargar un repositorio, tu app debe tener permisos de escritura para "contenido de repositorio". Estos permisos los configuraste en el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository) como **Lectura & escritura**, así que estás listo. Para confirmar los archivos, Git debe saber qué [nombre de usuario](/articles/setting-your-username-in-git/) y [correo electrónico](/articles/setting-your-commit-email-address-in-git/) asociará con la confirmación. Agrega dos variables de ambiente adicionales en tu archivo `.env` para almacenar las configuraciones de nombre(`GITHUB_APP_USER_NAME`) y de correo electrónico (`GITHUB_APP_USER_EMAIL`). Tu nombre puede ser aquél de tu app y la dirección de correo electrónico puede ser cualquiera para este ejemplo. Por ejemplo: -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 19f1ebd151..3bd7268a2a 100644 --- a/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ Una App de OAuth _autorizada_ tiene acceso a todos los recursos que son accesibl | Los tokens de instalación caducan después de un tiempo predefinido (actualmente, 1 hora). | Los tokens de OAuth permanecen activos hasta que el cliente los revoque. | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Aplicarán límites de tasa más altos para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Límites de tasa para las GitHub Apps](/developers/apps/rate-limits-for-github-apps)".{% endif %} | Los tokens de OAuth utilizan el límite de tasa del usuario de 5,000 solicitudes por hora. | | Pueden otorgarse incrementos en el límite de tasa tanto a nivel de las GitHub Apps (lo cual afecta a todas las instalaciones) como a nivel de la instalación individual. | Los incrementos en el límite de tasa se otorgan por cada App de OAuth. Cada token que se otorgue a esa App de OAuth obtiene el límite incrementado. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| Las {% data variables.product.prodname_github_app %} pueden autenticarse a nombre del usuario y a esto se le llama solicitudes de usuario a servidor. El flujo para autorizaciones es el mismo que aquél de las autorizaciones para las apps de OAuth. Los tokens de usuario a servidor pueden caducar y renovarse con un token de actualización. Para obtener más información, consulta las secciones "[Actualizar un token de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" y "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | El flujo de OAuth que utilizan las {% data variables.product.prodname_oauth_app %} autoriza a una {% data variables.product.prodname_oauth_app %} a nombre del usuario. Este es el mismo flujo que se utiliza en las autorizaciones de usuario a servidor de una {% data variables.product.prodname_github_app %}. |{% endif %} +| Las {% data variables.product.prodname_github_app %} pueden autenticarse a nombre del usuario y a esto se le llama solicitudes de usuario a servidor. El flujo para autorizaciones es el mismo que aquél de las autorizaciones para las apps de OAuth. Los tokens de usuario a servidor pueden caducar y renovarse con un token de actualización. Para obtener más información, consulta las secciones "[Actualizar un token de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" y "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | El flujo de OAuth que utilizan las {% data variables.product.prodname_oauth_app %} autoriza a una {% data variables.product.prodname_oauth_app %} a nombre del usuario. Este es el mismo flujo que se utiliza en las autorizaciones de usuario a servidor de una {% data variables.product.prodname_github_app %}. +{% endif %} ### Solicitar niveles de permiso para recursos @@ -85,7 +86,7 @@ A diferencia de las apps de OAuth, las GitHub Apps tiene permisos específicos q | GitHub Apps | OAuth Apps | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Predeterminadamente, las GitHub Apps tienen un solo webhook que recibe los eventos que se les ha configurado para recibir para cada repositorio al que tengan acceso. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. | +| Predeterminadamente, las GitHub Apps tienen un solo webhook que recibe los eventos que se les ha configurado para recibir para cada repositorio al que tengan acceso. | Las Apps de OAuth solicitan el alcance de webhook para crear un webhook de repositorio para cada repositorio del cual necesiten recibir eventos. | | Las GitHub Apps reciben algunos eventos a nivel organizacional con el permiso del miembro de la organización. | Las Apps de OAuth solicitan el alcance de webhook de la organización para crear un webhook de organización para cada organización de la cual necesiten recibir eventos de nivel organizacional. | ### Acceso a Git diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps.md index ccf0d4055d..8f97686725 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps.md @@ -1,7 +1,7 @@ --- title: Comenzar con las apps intro: Aprende cómo crear apps y como configurar tu ambiente de desarrollo. -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/developers/apps/guides.md b/translations/es-ES/content/developers/apps/guides.md index 04399979ee..0768ec9419 100644 --- a/translations/es-ES/content/developers/apps/guides.md +++ b/translations/es-ES/content/developers/apps/guides.md @@ -1,7 +1,7 @@ --- title: Guías intro: 'Aprende cómo utilizar la API de {% data variables.product.prodname_dotcom %} con tu app, integración continua, y cómo compilar con las apps.' -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/quickstart-guides versions: diff --git a/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index bd59f982c9..b00f88f367 100644 --- a/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/es-ES/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -79,7 +79,7 @@ Los tokens de usuario con caducidad son parte del beta de caducidad de tokens de | --------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `client_id` | `secuencia` | **Requerido.** La ID de cliente para tu GitHub App. | | `client_secret` | `secuencia` | **Requerido.** El secreto de cliente para tu GitHub App. | -| `code` | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1. | +| `código` | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1. | | `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Esta debe ser una copia exacta de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} una de las URL que proporcionaste como **URL de rellamado** {% else %} la URL que proporcionaste en el campo **URL de rellamado de autorización de usuario** {% endif %} cuando configuraste tu GitHub App y no puede contener ningún parámetro adicional. | | `state` | `secuencia` | La secuencia aleatoria indescifrable que proporcionaste en el Paso 1. | @@ -89,7 +89,7 @@ Los tokens de usuario con caducidad son parte del beta de caducidad de tokens de Predeterminadamente, la respuesta toma la siguiente forma. Los parámetros de respuesta `expires_in`, `refresh_token`, y `refresh_token_expires_in` solo se devuelven cuando habilitas el beta para la caducidad de los tokens de acceso de usuario a servidor. -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", @@ -229,7 +229,7 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [Listar las ejecuciones de verificación en un conjunto de verificaciones](/rest/reference/checks#list-check-runs-in-a-check-suite) * [Listar las ejecuciones de verificación para una referencia de Git](/rest/reference/checks#list-check-runs-for-a-git-reference) -##### Check Suites +##### Conjuntos de Verificaciones * [Crear un conjunto de verificaciones](/rest/reference/checks#create-a-check-suite) * [Obtener un conjunto de verificaciones](/rest/reference/checks#get-a-check-suite) @@ -809,7 +809,7 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [Emojis](/rest/reference/emojis#emojis) * [Obtener un estado de límite de tasa para el usuario autenticado](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user) -##### Search +##### Buscar * [Buscar código](/rest/reference/search#search-code) * [Buscar confirmaciones](/rest/reference/search#search-commits) diff --git a/translations/es-ES/content/developers/apps/managing-github-apps.md b/translations/es-ES/content/developers/apps/managing-github-apps.md index a31b60d5d4..b7f5582650 100644 --- a/translations/es-ES/content/developers/apps/managing-github-apps.md +++ b/translations/es-ES/content/developers/apps/managing-github-apps.md @@ -1,7 +1,7 @@ --- title: Adminsitrar las GitHub Apps intro: 'Después de que creas y registras una GitHub App, puedes hacer modificaciones a la misma, cambiar sus permisos, transferir la propiedad, y borrarla.' -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/building-integrations/managing-github-apps/ - /apps/managing-github-apps diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps.md b/translations/es-ES/content/developers/apps/managing-oauth-apps.md index f2fc4b0b99..76d0aae6ce 100644 --- a/translations/es-ES/content/developers/apps/managing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/managing-oauth-apps.md @@ -1,7 +1,7 @@ --- title: Adminsitrar las Apps de OAuth intro: 'Después de que creas y registras una App de OAuth, puedes hacerle modificaciones, cambiar sus permisos, transferir su propiedad y borrarla.' -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/building-integrations/managing-oauth-apps/ - /apps/managing-oauth-apps diff --git a/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md b/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md index 2c32a0de01..9e58f2038a 100644 --- a/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### Alcances disponibles -| Nombre | Descripción | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Nombre | Descripción | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`(no scope)`** | Otorga acceso de solo lectura a la información pública (incluyendo la información del perfil de usuario público, información de repositorio público, y gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`site_admin`** | Otorga a los administradores de sitio acceso a las [Terminales de la API para la Administración de {% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Otorga acceso completo a los repositorios públicos y privados. Esto incluye acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio y de organización, invitaciones, colaboradores, agregar membrecías de equipo, estados de despliegue, y webhooks de repositorio para aquellos repositorios privados y públicos y para las organizaciones. También otorga la capacidad de administrar proyectos de usuario. | -|  `repo:status` | Otorga acceso de lectura/escritura en los estados de confirmación de los repositorios privados. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de las confirmaciones en repositorios privados *sin* otorgarles acceso al código. | -|  `repo_deployment` | Otorga acceso a los [estados de despliegue](/rest/reference/repos#deployments) para los repositorios públicos y privados. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de despliegue *sin* otorgarles acceso al código. | -|  `public_repo` | Limita el acceso a los repositorios públicos. Esto incluye el acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio, colaboradores y estados de despliegue para los repositorios públicos y para las organizaciones. También se requiere para marcar a los repositorios públicos con una estrella. | +| **`repo`** | Otorga acceso completo a los repositorios públicos y privados. Esto incluye acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio y de organización, invitaciones, colaboradores, agregar membrecías de equipo, estados de despliegue, y webhooks de repositorio para aquellos repositorios privados y públicos y para las organizaciones. También otorga la capacidad de administrar proyectos de usuario. | +|  `repo:status` | Otorga acceso de lectura/escritura en los estados de confirmación de los repositorios privados. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de las confirmaciones en repositorios privados *sin* otorgarles acceso al código. | +|  `repo_deployment` | Otorga acceso a los [estados de despliegue](/rest/reference/repos#deployments) para los repositorios públicos y privados. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de despliegue *sin* otorgarles acceso al código. | +|  `public_repo` | Limita el acceso a los repositorios públicos. Esto incluye el acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio, colaboradores y estados de despliegue para los repositorios públicos y para las organizaciones. También se requiere para marcar a los repositorios públicos con una estrella. | |  `repo:invite` | Otorga capacidades de aceptar/rechazar las invitaciones para colaborar con un repositorio. Este alcance solo es necesario para otorgar a otros usuarios o servicios acceso a las invitaciones *sin* otorgar acceso al código.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `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 %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@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`** | Otorga acceso de lectura, escritura, ping y borrado a los ganchos de los repositorios privados y públicos. Los alcances `repo` y `public_repo` otorgan acceso completo a los repositorios, incluyendo a los ganchos de éstos. Utiliza el alcance `admin:repo_hook` para limitar el acceso únicamente a los ganchos de los repositorios. | -|  `write:repo_hook` | Otorga acceso de lectura, escritura y ping a los ganchos en los repositorios públicos o privados. | -|  `read:repo_hook` | Otorga acceso de lectura y de ping a los ganchos en los repositorios privados o públicos. | -| **`admin:org`** | Para administrar totalmente la organización y sus equipos, proyectos y membrecías. | -|  `write:org` | Acceso de lectura y escritura para la membrecía de organización y de los equipos y para los proyectos de la organización. | -|  `read:org` | Acceso de solo lectura para la membrecía de organización y de los equipos y para los proyectos de la organización. | -| **`admin:public_key`** | Administrar totalmente las llaves públicas. | -|  `write:public_key` | Crear, listar y ver los detalles de las llaves públicas. | -|  `read:public_key` | Listar y ver los detalles para las llaves públicas. | -| **`admin:org_hook`** | Otorga acceso de lectura, escritura, ping y borrado para los ganchos de la organización. **Nota:** Los tokens de OAuth solo podrán realizar estas acciones en los ganchos de la organización los cuales haya creado la App de OAuth. Los tokens de acceso personal solo podrán llevar a cabo estas acciones en los ganchos de la organización que cree un usuario. | -| **`gist`** | Otorga acceso de escritura a los gists. | -| **`notificaciones`** | Otorga:
* acceso de lectura a las notificaciones de un usuario
* acceso de marcar como leído en los hilos
* acceso de observar y dejar de observar en un repositorio, y
* acceso de lectura, escritura y borrado para las suscripciones a los hilos. | -| **`user`** | Otorga acceso de lectura/escritura únicamente para la información de perfil. Este alcance incluye a `user:email` y `user:follow`. | -|  `read:user` | Otorga acceso para leer los datos de perfil de un usuario. | -|  `user:email` | Otorga acceso de lectura para las direcciones de correo electrónico de un usuario. | -|  `user:follow` | Otorga acceso para seguir o dejar de seguir a otros usuarios. | -| **`delete_repo`** | Otorga acceso para borrar los repositorios administrables. | -| **`write:discussion`** | Permite el acceso de lectura y escritura para los debates de equipo. | +|  `security_events` | Otorga:
acceso de escritura y lectura a los eventos de seguridad en la [API del {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning)
acceso de lectura y escritura para los eventos de seguridad en la [API del {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning)
Este alcance es únicamente necesario para otorgar acceso a los eventos de seguridad a otros usuarios o servicios *sin* darles acceso al código.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | Otorga acceso de lectura y escritura a los eventos de seguridad en la [API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este alcance solo es necesario para otorgar acceso a los eventos de seguridad a otros usuarios o servicios *sin* otorgarles acceso al código.{% endif %} +| **`admin:repo_hook`** | Otorga acceso de lectura, escritura, ping y borrado a los ganchos de los repositorios privados y públicos. Los alcances `repo` y `public_repo` otorgan acceso completo a los repositorios, incluyendo a los ganchos de éstos. Utiliza el alcance `admin:repo_hook` para limitar el acceso únicamente a los ganchos de los repositorios. | +|  `write:repo_hook` | Otorga acceso de lectura, escritura y ping a los ganchos en los repositorios públicos o privados. | +|  `read:repo_hook` | Otorga acceso de lectura y de ping a los ganchos en los repositorios privados o públicos. | +| **`admin:org`** | Para administrar totalmente la organización y sus equipos, proyectos y membrecías. | +|  `write:org` | Acceso de lectura y escritura para la membrecía de organización y de los equipos y para los proyectos de la organización. | +|  `read:org` | Acceso de solo lectura para la membrecía de organización y de los equipos y para los proyectos de la organización. | +| **`admin:public_key`** | Administrar totalmente las llaves públicas. | +|  `write:public_key` | Crear, listar y ver los detalles de las llaves públicas. | +|  `read:public_key` | Listar y ver los detalles para las llaves públicas. | +| **`admin:org_hook`** | Otorga acceso de lectura, escritura, ping y borrado para los ganchos de la organización. **Nota:** Los tokens de OAuth solo podrán realizar estas acciones en los ganchos de la organización los cuales haya creado la App de OAuth. Los tokens de acceso personal solo podrán llevar a cabo estas acciones en los ganchos de la organización que cree un usuario. | +| **`gist`** | Otorga acceso de escritura a los gists. | +| **`notificaciones`** | Otorga:
* acceso de lectura a las notificaciones de un usuario
* acceso de marcar como leído en los hilos
* acceso de observar y dejar de observar en un repositorio, y
* acceso de lectura, escritura y borrado para las suscripciones a los hilos. | +| **`user`** | Otorga acceso de lectura/escritura únicamente para la información de perfil. Este alcance incluye a `user:email` y `user:follow`. | +|  `read:user` | Otorga acceso para leer los datos de perfil de un usuario. | +|  `user:email` | Otorga acceso de lectura para las direcciones de correo electrónico de un usuario. | +|  `user:follow` | Otorga acceso para seguir o dejar de seguir a otros usuarios. | +| **`delete_repo`** | Otorga acceso para borrar los repositorios administrables. | +| **`write:discussion`** | Permite el acceso de lectura y escritura para los debates de equipo. | |  `read:discussion` | Permite el acceso de lectura para los debates de equipo.{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | Otorga acceso para cargar o publicar un paquete en el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Publicar un paquete](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Otorga acceso para descargar o instalar paquetes desde el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Instalar un paquete](/github/managing-packages-with-github-packages/installing-a-package)". | +| **`write:packages`** | Otorga acceso para cargar o publicar un paquete en el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Publicar un paquete](/github/managing-packages-with-github-packages/publishing-a-package)". | +| **`read:packages`** | Otorga acceso para descargar o instalar paquetes desde el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Instalar un paquete](/github/managing-packages-with-github-packages/installing-a-package)". | | **`delete:packages`** | Otorga acceso para borrar paquetes del {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Borrar paquetes](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -| **`admin:gpg_key`** | Administra las llaves GPG totalmente. | -|  `write:gpg_key` | Crea, lista, y visualiza los detalles de las llaves GPG. | +| **`admin:gpg_key`** | Administra las llaves GPG totalmente. | +|  `write:gpg_key` | Crea, lista, y visualiza los detalles de las llaves GPG. | |  `read:gpg_key` | Listar y visualizar los detalles para las llaves GPG.{% if currentVersion == "free-pro-team@latest" %} | **`workflow`** | Otorga la capacidad de agregar y actualizar archivos del flujo de trabajo de las {% data variables.product.prodname_actions %}. Los archivos de flujo de trabajo pueden confirmarse sin este alcance en caso de que el mismo archivo (con la misma ruta y el mismo contenido) exista en otra rama en el mismo repositorio. Los archivos de flujo de trabajo pueden exponer `GITHUB_TOKEN` que pueden tener un conjunto diferente de alcances, consulta https://docs.github.com/en/free-pro-team@latest/actions/reference/autentication-in-a-workflow#permissions-for-the-github_token para obtener más detalles.{% endif %} diff --git a/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md index 6e2f81f50a..2fa82ce012 100644 --- a/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/es-ES/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ Para aprender sobre cómo publicar {% data variables.product.prodname_actions %} ### Aplicaciones -Cualquiera puede compartir sus apps con otros usuarios en {% data variables.product.prodname_marketplace %}, pero solo las listas que verifique {% data variables.product.company_short %} podrán incluir planes pagados. Para obtener más información, consulta la sección "[Acerca de los creadores verificados](/developers/github-marketplace/about-verified-creators)". +Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. + +To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments. + +To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)." + +#### New to apps? Si te interesa crear una app para {% data variables.product.prodname_marketplace %} pero eres nuevo en las {% data variables.product.prodname_github_apps %} o en las {% data variables.product.prodname_oauth_app %}s, consulta la sección "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" o "[Crear {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)". +#### GitHub Apps vs. OAuth Apps + {% data reusables.marketplace.github_apps_preferred %}, aunque puedes listar tanto las Apps de OAuth como las {% data variables.product.prodname_github_app %} en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta las secciones "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" y "[Migrarse de las {% data variables.product.prodname_oauth_app %}s a las {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)". -Si tienes preguntas acerca de {% data variables.product.prodname_marketplace %}, por favor contacta directamente a {% data variables.contact.contact_support %}. - -### Publicar una app en {% data variables.product.prodname_marketplace %} +### Publishing an app to {% data variables.product.prodname_marketplace %} overview Cuando termines de crear tu app, puedes compartirla con otros usuarios si la publicas en {% data variables.product.prodname_marketplace %}. En resúmen, el proceso es: @@ -38,13 +46,9 @@ Cuando termines de crear tu app, puedes compartirla con otros usuarios si la pub 1. Agrega un plan de precios. Para obtener más información, consulta la sección "[Configurar planes de precios para tu listado](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". -1. Verifica si tu app cumple con los requisitos para los listados en {% data variables.product.prodname_marketplace %} como una app gratuita o pagada. Para obtener más información, consulta la sección "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)". - 1. Lee y acepta las condiciones del "[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". -1. Emite tu lista para publicarla en {% data variables.product.prodname_marketplace %} y solicita su verificación si quieres vender la app. Para obtener más información, consulta la sección "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication)". - -Un experto en incorporaciones te contactará para hacerte cualquier pregunta o para indicarte los pasos siguietnes. Por ejemplo, si agregaste un plan de pago, necesitarás completar el proceso de verificación y completar una incorporación financiera. La app se publicará en {% data variables.product.prodname_marketplace %} tan pronto como se apruebe tu lista. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication)". ### Ver el desempeño de tu app @@ -52,3 +56,7 @@ Puedes acceder a las métricas y transacciones de tu lista. Para obtener más in - "[Visualizar las métricas de tu lista](/developers/github-marketplace/viewing-metrics-for-your-listing)" - "[Visualizar las transacciones de tu lista](/developers/github-marketplace/viewing-transactions-for-your-listing)" + +### Contacting Support + +Si tienes preguntas acerca de {% data variables.product.prodname_marketplace %}, por favor contacta directamente a {% data variables.contact.contact_support %}. diff --git a/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md b/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..2d1c0b0502 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: About marketplace badges +intro: 'Learn about the badges that you may see for some apps and actions listings on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### For GitHub Apps + +Apps with the {% octicon "verified" aria-label="The verified badge" %}, are owned by an organization that has: +- Confirmed their domain +- Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization +- Required two-factor authentication for their organization. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en tu organización](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + +![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +To learn how you can add this badge to your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +Para obtener más información sobre los requisitos para listar una app en {% data variables.product.prodname_marketplace %}, consulta los "[Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". + +Para obtener información sobre cómo encontrar apps que puedas utilizar, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". + +### For GitHub actions + +Actions with the {% octicon "verified" aria-label="The verified badge" %}, or verified creator badge, indicate that {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization. + +![Verified creator badge for GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +For information on how to publish a GitHub action to {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." + +### About the previous verification process for apps + +Adicionalmente a la insignia de creador verificado, también podrás ver insignias para las apps que estén verificadas, y para las que no lo estén. Estas apps se publicaron utilizando el método anterior para verificar las apps individuales. + +![Insignias verde para verificado y gris para no verificado](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**Note:** The new publisher verification process for apps replaces the previous process where individual apps were verified. The new publisher verification process is similar to the verification process for actions. Si tienes apps que se verificaron con el proceso anterior, estas no se verán afectadas por estos cambios. El equipo de {% data variables.product.prodname_marketplace %} te contactará con los detalles de cómo migrarte a una verificación basada en la organización. + +{% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..49e20d558b --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Applying for publisher verification for your organization +intro: 'To offer paid plans for your app or to include a marketplace badge in your app listing, you must complete the publisher verification process for your organization.' +versions: + free-pro-team: '*' +--- + +Publisher verification ensures that {% data variables.product.prodname_dotcom %} has a way to contact you, that you've enabled two-factor authentication for your organization, and that your organization's domain has been verified. + +Once your organization has been verified, you can publish paid plans for your app. For information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)." + +### Requesting publisher verification + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) +1. Under "Publisher Verification", complete the information in the checklist: + - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. + - Ensure that Two-factor authentication is enabled for your organization. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en tu organización](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + - Submit a verified domain. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + + ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) + +1. Click **Request Verification**. {% data variables.product.company_short %} will review your details and let you know once your publisher verification is complete. + +### Leer más + +For information about the process of publishing apps, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)." diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md index dd169c4654..ebfe6d39fc 100644 --- a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md +++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace.md @@ -1,7 +1,7 @@ --- title: Crear apps para GitHub Marketplace intro: 'Puedes listar herramientas gratuitas y de pago para que las utilicen los desarrolladores en {% data variables.product.prodname_marketplace %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 72455c12c5..a966e3cdc9 100644 --- a/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/es-ES/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ Ya que hayas creado un borrador de listado de {% data variables.product.prodname ### Emitir tu app -Ya que hayas completado tu listado de {% data variables.product.prodname_marketplace %}, puedes emitirlo para su revisión a través de la página **Resumen**. Necesitas leer y aceptar el "[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)", y luego puedes dar clic en **Emitir para revisión**. Después de emitir tu app para su revisión te contactará un experto en integraciones con cualquier tipo de información adicional que se requiera para el proceso de integración. Puedes aprender más acerca del proceso de integración y revisión de seguridad en la sección "[Comenzar con {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)". +Ya que hayas completado tu listado de {% data variables.product.prodname_marketplace %}, puedes emitirlo para su revisión a través de la página **Resumen**. Necesitas leer y aceptar el "[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)", y luego puedes dar clic en **Emitir para revisión**. Después de emitir tu app para su revisión te contactará un experto en integraciones con cualquier tipo de información adicional que se requiera para el proceso de integración. ### Eliminar un listado de {% data variables.product.prodname_marketplace %} diff --git a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..c0d9dfb944 --- /dev/null +++ b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,9 @@ +--- +title: GitHub Marketplace Overview +intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.' +mapTopic: true +versions: + free-pro-team: '*' +--- + + diff --git a/translations/es-ES/content/developers/github-marketplace/index.md b/translations/es-ES/content/developers/github-marketplace/index.md index ce31b9b816..bd9e98ef01 100644 --- a/translations/es-ES/content/developers/github-marketplace/index.md +++ b/translations/es-ES/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md index 6c03762016..a0ebefbd6e 100644 --- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md +++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace.md @@ -1,7 +1,7 @@ --- title: Listar una app en GitHub Marketplace intro: 'Aprende sobre los requisitos y mejores prácticas para listar tu app en {% data variables.product.prodname_marketplace %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/ diff --git a/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md b/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md index aa81aa8421..21bbc83a2f 100644 --- a/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md +++ b/translations/es-ES/content/developers/github-marketplace/receiving-payment-for-app-purchases.md @@ -13,14 +13,14 @@ versions: -After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process. +Después de que tu listado de {% data variables.product.prodname_marketplace %} para una app con un plan de pago se cree y apruebe, deberás proporcionar los detalles de pago a {% data variables.product.product_name %} como parte del proceso de integración financiera. -Once your revenue reaches a minimum of $500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs. +Una vez que tus ganancias lleguen a un mínimo de $500 dolares estadounidenses por el mes, recibirás un pago electrónico de {% data variables.product.company_short %}. Este será el ingreso de las transacciones de marketplace menos la cantidad que cobra {% data variables.product.company_short %} para cubrir los costos de operación. -For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward. +Para las transacciones que se realicen antes del 1 de enero de 2021, {% data variables.product.company_short %} retendrá el 25% del ingreso de ellas. Para las transacciones que se realicen después de esta fecha, {% data variables.product.company_short %} solo retendrá el 5%. Este cambio se reflejará en los pagos que se reciban desde el final de enero 2021 en adelante. {% note %} -**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/github/site-policy/github-marketplace-developer-agreement)." +**Nota:** Para obtener más detalles de los precios y condiciones de pago actuales, consulta la sección "[acuerdo de desarrollador de {% data variables.product.prodname_marketplace %}](/github/site-policy/github-marketplace-developer-agreement)". {% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md index 907cc89649..f3b453ce93 100644 --- a/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/es-ES/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ Para proteger a tus clientes, te recomendamos que también sigas las mejores pr ### Requisitos para las apps de pago -Adicionalmente a los requisitos para todas las apps que se mencionaron anteriormente, cada app que ofrezcas en {% data variables.product.prodname_marketplace %} como un servicio pagado deberá cumplir con los siguientes requisitos: +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transfering ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. Para obtener más información, consulta la sección "[Configurar planes de precios para tu listado](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". + +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: - Las {% data variables.product.prodname_github_app %} deben contar con un mínimo de 100 instalaciones. - Las {% data variables.product.prodname_oauth_app %} deben tener un mínimo de 200 usuarios. - Todas las apps de pago deben gestinar los eventos de compra de {% data variables.product.prodname_marketplace %} para las compras nuevas, mejoras, retrocesos, cancelaciones y pruebas gratuitas. Para obtener más información, consulta la sección "[Requisitos de facturación para las apps de pago](#billing-requirements-for-paid-apps)" que se encuentra más adelante. -- Las organizaciones publicadoras deben tener un dominio verificado y deben habilitar la autenticación bifactorial. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en tu organización](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." -Cuando estés listo para publicar la app en {% data variables.product.prodname_marketplace %}, deberás solicitar la verificación de la lista. +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -El proceso de verificación está disponible para las organizaciones. {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección: "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md index 45ea865274..1d780112e5 100644 --- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md +++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace.md @@ -1,7 +1,7 @@ --- title: Vender tu app en GitHub Marketplace intro: 'Aprende sobre los requisitos y mejores prácticas para vender tu app en {% data variables.product.prodname_marketplace %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/ - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/ diff --git a/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index ba13e1e6ce..3a563f6703 100644 --- a/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/es-ES/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,11 +19,13 @@ versions: ### Acerca de configurar planes de precios -Si quieres vender una app en {% data variables.product.prodname_marketplace %}, necesitas solicitar una verificación cuando publicas la lista para tu app. Durante el proceso de verificación, un experto en integración revisará la identidad de la organización y su configuración de seguridad. El experto en integración también llevará a la organización a través de una integración financiera. Para obtener más información, consulta la sección "[Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". +{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. Para obener información detallada, consulta la sección "[Planes de precios para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". -{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección: "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". +To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -{% data variables.product.prodname_marketplace %} ofrece varios tipos diferentes de planes de precios. Para obener información detallada, consulta la sección "[Planes de precios para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". +If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. + +![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png) ### Acerca de guardar los planes de precios diff --git a/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md index f6163f3b39..255f0a22de 100644 --- a/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/es-ES/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: Emitir tu listado para que se publique -intro: 'Puedes emitir tu listado para que lo utilice la comunidad de {% data variables.product.prodname_dotcom %}.' +intro: 'To finish your app listing submission, you can request a review by an onboarding expert.' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +Once your app listing meets the {% data variables.product.prodname_marketplace %} requirements, you can submit your app. For an overview of the app listing requirements, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +1. In the top left of the app listing page, click **Overview**. For information on finding your app listing page, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -Una vez que hayas completado el listado para tu app, verás dos botones que te permiten solicitar la publicación del mismo con o sin verificación. El botón **Solicitar** para "Publicar sin verificación" estará inhabilitado si publicaste cualquier plan de precios en el listado. + ![Overview option for the marketplace draft listing](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![Botón para solicitudes verificadas y sin verificar](/assets/images/marketplace/marketplace-request-button.png) +2. To submit your your completed app listing, click **Request review**. -{% data reusables.marketplace.launch-with-free %} + !["Publish your app to Marketplace" checklist with submission button at the bottom](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -Un experto en incorporación te contactará con información adicional después de que emitas tu listado para su revisión. - -Para encontrar un resumen del proceso para crear y emitir un listado, consulta la sección "[Acerca de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)". - -### Prerequisitos para publicar con verificación - -Antes de que solicites una verificación para tu listado, necesitarás integrar los flujos de facturación y webhook de {% data variables.product.prodname_marketplace %} en tu app. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". - -Si cumpliste con los requisitos de los listados y te integraste con la API de {% data variables.product.prodname_marketplace %}, puedes seguir con la emisión de tu listado. Para obtener más información, consulta la sección "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)". - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo hacer esto, consulta la sección "[Transferir una app a una organización antes de emitirla](#transferring-an-app-to-an-organization-before-you-submit)" que se encuentra más adelante. - -### Transferir una app a una organización antes de emitirla - -No puedes vender una app que pertenezca a una cuenta de usuario. Necesitas transferir la app a una organización que ya constituya un creador verificado, o que pueda solicitar la verificación de un listado para la app. Para obtener más detalles, consulta: - -1. "[Crear una organización desde cero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" - -1. "[Transferir la propiedad de una GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" o "[Transferir la propiedad de una OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" +An onboarding expert will reach out to you with additional information. diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md index 6f5b4e681d..87d5ae47a2 100644 --- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md +++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app.md @@ -1,7 +1,7 @@ --- title: Utilizar la API de GitHub Marketplace en tu app intro: 'Aprende cómo integrar la API y eventos de webhook de {% data variables.product.prodname_marketplace %} en tu app para {% data variables.product.prodname_marketplace %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/ diff --git a/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index 0b8ee7a389..a0ccb59704 100644 --- a/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/es-ES/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Visualizar las transacciones para tu listado -intro: 'La página de transacciones de {% data variables.product.prodname_marketplace %} te permite descargar y visualizar todas las transacciones de tu listado de {% data variables.product.prodname_marketplace %}. You can view transactions for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.' +intro: 'La página de transacciones de {% data variables.product.prodname_marketplace %} te permite descargar y visualizar todas las transacciones de tu listado de {% data variables.product.prodname_marketplace %}. Puedes ver las transacciones del día anterior (24 horas), de la semana, el mes, o de la duración total de tiempo que ha estado listada tu {% data variables.product.prodname_github_app %}.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index e6723353e5..77e9b49683 100644 --- a/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/es-ES/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -26,20 +26,20 @@ Cada carga útil de webhook de una `marketplace_purchase` tendrá la siguiente i | ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción realizada para generar el webhook. Puede ser `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, o `changed`. Para obtener más información, consulta los ejemplos de cargas útiles de webhook a continuación. **Nota:** las cargas útiles de `pending_change` y `pending_change_cancelled` contienen las mismas claves que se muestra en el [ejemplo de carga útil de `changed`](#example-webhook-payload-for-a-changed-event). | | `effective_date` | `secuencia` | La fecha en la que la `action` se hace efectiva. | -| `sender` | `object` | La persona que tomó la `action` que activó el webhook. | -| `marketplace_purchase` | `object` | La información de compra de {% data variables.product.prodname_marketplace %}. | +| `sender` | `objeto` | La persona que tomó la `action` que activó el webhook. | +| `marketplace_purchase` | `objeto` | La información de compra de {% data variables.product.prodname_marketplace %}. | El objeto `marketplace_purchase` tiene las siguientes claves: | Clave | Type | Descripción | | -------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `account` | `object` | La cuenta de `organización` o `usuario` asociada con la suscripción. Las cuentas de organización incluirán `organization_billing_email`, que es la dirección de correo electrónico administrativa de la misma. Para encontrar direcciones de correo electrónico para cuentas personales, puedes utilizar la terminal [Obtener el usuario autenticado](/rest/reference/users#get-the-authenticated-user). | +| `cuenta` | `objeto` | La cuenta de `organización` o `usuario` asociada con la suscripción. Las cuentas de organización incluirán `organization_billing_email`, que es la dirección de correo electrónico administrativa de la misma. Para encontrar direcciones de correo electrónico para cuentas personales, puedes utilizar la terminal [Obtener el usuario autenticado](/rest/reference/users#get-the-authenticated-user). | | `billing_cycle` | `secuencia` | Puede ser `yearly` o `monthly`. Cuando el dueño de la `account` tiene un plan gratuito de GitHub y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `billing_cycle` será `nil`. | | `unit_count` | `número` | Cantidad de unidades compradas. | | `on_free_trial` | `boolean` | Es `true` cuando la `account` está en un periodo de prueba gratuito. | | `free_trial_ends_on` | `secuencia` | La fecha en la que caduca el periodo de prueba gratuito. | | `next_billing_date` | `secuencia` | La fecha en la que comenzará el siguiente ciclo de facturación. Cuando el dueño de la `account` tiene un plan gratuito de GitHub.com y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `next_billing_date` será `nil`. | -| `plan` | `object` | El plan que compra el `user` u `organization`. | +| `plan` | `objeto` | El plan que compra el `user` u `organization`. | El objeto `plan` tiene las siguientes claves: @@ -47,7 +47,7 @@ El objeto `plan` tiene las siguientes claves: | ------------------------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `número` | El identificador único para este plan. | | `name (nombre)` | `secuencia` | El nombre del plan. | -| `description` | `secuencia` | La descripción de este plan. | +| `descripción` | `secuencia` | La descripción de este plan. | | `monthly_price_in_cents` | `número` | El precio mensual de este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 10 dólares de EEUU por mes sería de 1000 centavos. | | `yearly_price_in_cents` | `número` | El precio anual para este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 100 dólares de EEUU por mes sería de 10000 centavos. | | `price_model` | `secuencia` | El modelo de precios para este listado. Puede ser alguno de entre `flat-rate`, `per-unit`, o `free`. | diff --git a/translations/es-ES/content/developers/overview/secret-scanning.md b/translations/es-ES/content/developers/overview/secret-scanning.md index 3ab1485aec..eca74250a5 100644 --- a/translations/es-ES/content/developers/overview/secret-scanning.md +++ b/translations/es-ES/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: Escaneo de secretos intro: 'Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que se aseguren nuestros formatos de token secretos a través de un escaneo de secretos, el cual busca las confirmaciones accidentales de tus formatos secretos y puede enviarse a la terminal de verificación de un proveedor de servicios.' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -{% data variables.product.prodname_dotcom %} escanea los repositorios en busca de formatos secretos para prevenir el uso fraudulento de las credenciales que se confirmaron por accidente. El escaneo de secretos ocurre predeterminadamente en los repositorios públicos, y se puede habilitar en los privados por parte de los administradores de dicho repositorio o de los propietarios de la organización. Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que tus formatos secretos se incluyan en nuestro escaneo de secretos. +{% data variables.product.prodname_dotcom %} escanea los repositorios en busca de formatos secretos para prevenir el uso fraudulento de las credenciales que se confirmaron por accidente. El {% data variables.product.prodname_secret_scanning_caps %} ocurre predeterminadamente en los repositorios públicos y los administradores de repositorio o propietarios de la organización pueden habilitarlo en los repositorios privados. Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que tus formatos de secreto se incluyan en nuestro {% data variables.product.prodname_secret_scanning %}. Cuando se encuentra una coincidencia de tu formato secreto en un repositorio público, se envía una carga útil a una terminal HTTP de tu elección. -Cuando se encuentra una coincidencia de tu formato secreto en un repositorio privado configurado para el escaneo de secretos, entonces se les alerta a los administradores del repositorio y estos pueden ver y administrar los resultados del escaneo de secretos en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar alertas del escaneo de secretos](/github/administering-a-repository/managing-alerts-from-secret-scanning)". +Cuando se encuentra una coincidencia con tu formato de secreto en un repositorio privado que se haya configurado para el {% data variables.product.prodname_secret_scanning %}, entonces, se alerta a los administradores de repositorio y éstos pueden ver y administrar los resultados del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)". {% note %} -**Nota:** El escaneo de secretos para repositorios privados se encuentra actualmente en beta. +**Nota:** El {% data variables.product.prodname_secret_scanning_caps %} para los repositorios privados se encuentran actualmente en beta y está sujeto a cambios. {% endnote %} -Este artículo describe cómo puedes asociarte con {% data variables.product.prodname_dotcom %} como un proveedor de servicios y unirte al programa de escaneo de secretos. +Este artículo describe cómo puedes asociarte con {% data variables.product.prodname_dotcom %} como un proveedor de servicios y unirte al programa del {% data variables.product.prodname_secret_scanning %}. -### El proceso de escaneo de secretos +### El proceso del {% data variables.product.prodname_secret_scanning %} -##### Cómo funciona el escaneo de secretos en un repositorio público +##### Cómo funciona el {% data variables.product.prodname_secret_scanning %} en un repositorio público -El siguiente diagrama resume el proceso de escaneo de secretos para los repositorios públicos y cualquier coincidencia se envía a una terminal de verificación de un proveedor de servicios. +El siguiente diagrama resume el proceso del {% data variables.product.prodname_secret_scanning %} para los repositorios públicos y muestra como cualquier coincidencia se envía a la terminal de verificación de un proveedor de servicios. -![Diagrama de flujo que muestra el proceso de escaneo para un secreto y el envío de coincidencias a una terminal de verificación del proveedor de servicios](/assets/images/secret-scanning-flow.png "Flujo de escaneo de secretos") +![Diagrama de flujo que muestra el proceso de escaneo para un secreto y el envío de coincidencias a una terminal de verificación del proveedor de servicios](/assets/images/secret-scanning-flow.png "Flujo del {% data variables.product.prodname_secret_scanning_caps %}") -### Unirse al programa de escaneo de secretos en {% data variables.product.prodname_dotcom %} +### Unirse al programa del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.prodname_dotcom %} 1. Contacta a {% data variables.product.prodname_dotcom %} para iniciar el proceso. 1. Identifica los secretos relevantes que quieres escanear y crea expresiones regulares para capturarlos. -1. Para las coincidencias de secretos que estén en repositorios públicos, crea un servicio de alerta de secretos que acepte webhooks de {% data variables.product.prodname_dotcom %} que contengan la carga útil del mensaje del escaneo de secretos. +1. Para las coincidencias de secretos que se encuentran en los repositorios públicos, crea un servicio de alerta de secretos que acepte webhooks de {% data variables.product.prodname_dotcom %}, el cual contenga la carga últil del mensaje del {% data variables.product.prodname_secret_scanning %}. 1. Implementa la verificación de firmas en tu servicio de alerta secreto. 1. Implementa la revocación de secretos y las notificaciones al usuario en tu servicio de alerta de secretos. +1. Proporciona retroalimentación para los falsos positivos (opcional). #### Contacta a {% data variables.product.prodname_dotcom %} para iniciar el proceso -Para iniciar con el proceso de inscripción, manda un mensaje de correo electrónico a secret-scanning@github.com. +Para iniciar con el proceso de inscripción, manda un correo electrónico a secret-scanning@github.com. -Recibirás los detalles del programa de escane de secretos, y necesitarás aceptar las condiciones de participación de {% data variables.product.prodname_dotcom %} antes de seguir con el proceso. +Recibirás los detalles del programa del {% data variables.product.prodname_secret_scanning %} y necesitarás aceptar las condiciones de participación de {% data variables.product.prodname_dotcom %} antes de proceder. #### Identifica tus secretos y crea expresiones regulares -Para escanear en busca de tus secretos, {% data variables.product.prodname_dotcom %} necesita saber los siguientes detalles de cada secreto que quieras incluir en el programa de escaneo de secretos: +Para escanear tus secretos, {% data variables.product.prodname_dotcom %} necesita la siguiente información de cada secreto que quieras incluir en el programa del {% data variables.product.prodname_secret_scanning %}: * Un nombre único y legible para las personas para el tipo de secreto. Lo utilizaremos para generar el valor `Type` en la carga útil del mensaje más adelante. * Una expresión regular que encuentre el tipo de secreto. Sé tan preciso como sea posible, ya que esto reducirá la cantidad de falsos positivos. * La URL de la terminal que recibe mensajes de {% data variables.product.prodname_dotcom %}. Esto no tiene que ser único para cada tipo de secreto. -Envía esta información a secret-scanning@github.com. +Envía esta información a secret-scanning@github.com. #### Crea un servicio de alerta de secretos @@ -61,7 +62,7 @@ Crea una terminal HTTP pública y accesible desde la internet en la URL que nos ##### Ejemplo del POST que se envía a tu terminal -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ Puedes recuperar la llave pública del escaneo de secretos de {% data variables. Asumiendo que recibes el siguiente mensaje, los extractos de código que presentamos a continuación demuestran cómo pudiste realizar la validación de firmas. El código también asume que configuraste una variable de ambiente llamada `GITHUB_PRODUCTION_TOKEN` con un PAT generado (https://github.com/settings/tokens). El token no necesita que se configure ningún permiso. **Mensaje de ejemplo que se envía a tu terminal de verificación** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -277,4 +278,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### Implementa la revocación de secretos y la notificación a usuarios en tu servicio de alerta de secretos -Para escanear secretos en los repositorios públicos, puedes ampliar tu servicio de alerta de secretos para revocar los secretos expuestos y notificar a los usuarios afectados. Depende de ti el cómo implementas esto en tu servicio de alerta de secretos, pero te recomendamos considerar cualquier secreto del cual {% data variables.product.prodname_dotcom %} te envíe mensajes de que es público y está puesto en riesgo. +Para el {% data variables.product.prodname_secret_scanning %} en repositorios públicos, puedes ampliar tu servicio de alerta de secretos para que revoque los secretos expuestos y notifique a los usuarios afectados. Depende de ti el cómo implementas esto en tu servicio de alerta de secretos, pero te recomendamos considerar cualquier secreto del cual {% data variables.product.prodname_dotcom %} te envíe mensajes de que es público y está puesto en riesgo. + +#### Proporciona retroalimentación sobre los falsos positivos + +Recolectamos la retroalimentación sobre la validez de los secretos individuales que se detectan en las respuestas de los socios. Si quieres formar parte, mándanos un correo electrónico a secret-scanning@github.com. + +Cuando te reportamos los secretos, enviamos un arreglo de JSON con cada elemento que contiene el token, identificador de tipo y URL de confirmación. Cuando envías retroalimentación, nos envías información sobre si el token que se detectó fue una credencial real o falsa. Aceptamos la retroalimentación en los siguientes formatos. + +Puedes enviarnos el token sin procesar: + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +También puedes proporcionar el token en forma de hash después de realizar un hash criptográfico de una sola vía para el token sin procesar utilizando SHA-256: + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +Algunos puntos importantes: +- Solo debes enviarnos ya sea la forma sin procesar del token ("token raw") o la forma en hash ("token_hash"), pero no ambas. +- En el caso de la forma en hash del token sin procesar, solo puedes utilizar SHA-256 para crear el hash del token y no algún otro algoritmo. +- La etiqueta indica si un token es un positivo verdadero ("true_positive") o falso ("false_positive"). Solo se permiten estas secuencias en minúsculas. + +{% note %} + +**Nota:** Nuestro tiempo límite se configura para que sea mayor (es decir, 30 segundos) para los socios que proporcionen datos sobre falsos positivos. Si requieres de un tiempo límite mayor a 30 segundos, envíanos un correo electrónico a secret-scanning@github.com. + +{% endnote %} + diff --git a/translations/es-ES/content/developers/webhooks-and-events/events.md b/translations/es-ES/content/developers/webhooks-and-events/events.md index 43d087fec0..34c57a7249 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/events.md +++ b/translations/es-ES/content/developers/webhooks-and-events/events.md @@ -1,7 +1,7 @@ --- title: Eventos intro: 'Tus integraciones pueden suscribirse y reaccionar a los eventos en {% data variables.product.prodname_dotcom %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md index 2fd0ad3707..ce9db39dc3 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md @@ -204,12 +204,12 @@ Este evento devuelve un objeto de `payload` vacío. | `size` | `número` | La cantidad de confirmaciones de la carga. | | `distinct_size` | `número` | La cantidad de confimraciones distintas para la carga. | | `ref` | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main`. | -| `head` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | +| `encabezado` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | | `before` | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga. | | `commits` | `arreglo` | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (El conjunto incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks). | | `commits[][sha]` | `secuencia` | El SHA de la confirmación. | | `commits[][message]` | `secuencia` | El mensaje de la confirmación. | -| `commits[][author]` | `object` | El autor de git de la confirmación. | +| `commits[][author]` | `objeto` | El autor de git de la confirmación. | | `commits[][author][name]` | `secuencia` | El nombre del autor de git. | | `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | | `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | diff --git a/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md index 6169995515..1488e37b36 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/es-ES/content/developers/webhooks-and-events/issue-event-types.md @@ -130,13 +130,13 @@ Un comentario se agregó al informe de problemas o solicitud de extracción. | `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](/graphql/guides/using-global-node-ids) del evento. | -| `user` | `object` | La persona que comentó en el informe de problemas. | +| `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. | -| `body` | `secuencia` | El cuerpo de texto del comentario. | +| `cuerpo` | `secuencia` | El cuerpo de texto del comentario. | | `event` | `secuencia` | El valor del evento es `"commented"`. | -| `actor (actor)` | `object` | La persona que generó el evento. | +| `actor (actor)` | `objeto` | La persona que generó el evento. | ### committed @@ -158,12 +158,12 @@ Una confirmación se agregó a la rama `HEAD` de la solicitud de extracción. | `node_id` | `secuencia` | La [ID de Nodo Global](/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. | -| `author` | `object` | La persona que autorizó la confirmación. | -| `committer` | `object` | La persona que confirmó la confirmación en nombre del autor. | -| `tree` | `object` | El árbol de Git 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. | -| `verfication` | `object` | 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#signature-verification-object)". | +| `verfication` | `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#signature-verification-object)". | | `event` | `secuencia` | El valor del evento es `"committed"`. | ### connected @@ -228,12 +228,12 @@ El informe de problemas o solicitud de extración se referenció desde otro info | Nombre | Type | Descripción | | ------------------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor (actor)` | `object` | La persona que generó el evento. | +| `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` | `object` | La solicitud de extracción o informe de problemas que agregó la referencia cruzada. | +| `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]` | `object` | El objeto del `issue` que agregó la referencia cruzada. | +| `source[issue]` | `objeto` | El objeto del `issue` que agregó la referencia cruzada. | | `event` | `secuencia` | El valor del evento es `"cross-referenced"`. | ### demilestoned @@ -584,15 +584,15 @@ Se revisió la solicitud de extracción. | -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `número` | El identificador único del evento. | | `node_id` | `secuencia` | La [ID de Nodo Global](/graphql/guides/using-global-node-ids) del evento. | -| `user` | `object` | La persona que comentó en el informe de problemas. | -| `body` | `secuencia` | El texto de resúmen de la revisión. | +| `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` | `object` | El `html_url` y `pull_request_url`. | +| `_links` | `objeto` | El `html_url` y `pull_request_url`. | | `event` | `secuencia` | El valor del evento es `"reviewed"`. | ### subscribed diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md index d4a4025afc..4468a05b48 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -231,7 +231,7 @@ Solo las {% data variables.product.prodname_github_app %}s podrán recibir este {{ webhookPayloadsForCurrentVersion.create }} -### eliminar +### delete {% data reusables.webhooks.delete_short_desc %} @@ -294,7 +294,7 @@ Solo las {% data variables.product.prodname_github_app %}s podrán recibir este | Clave | Type | Descripción | | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} -| `deployment` | `object` | El [despliegue](/rest/reference/repos#list-deployments). | +| `deployment` | `objeto` | El [despliegue](/rest/reference/repos#list-deployments). | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -319,11 +319,11 @@ Solo las {% data variables.product.prodname_github_app %}s podrán recibir este | Clave | Type | Descripción | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} -| `deployment_status` | `object` | El [Estado del despliegue](/rest/reference/repos#list-deployment-statuses). | +| `deployment_status` | `objeto` | El [Estado del despliegue](/rest/reference/repos#list-deployment-statuses). | | `deployment_status["state"]` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | | `deployment_status["target_url"]` | `secuencia` | El enlace opcional agregado al estado. | | `deployment_status["description"]` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | -| `deployment` | `object` | El [despliegue](/rest/reference/repos#list-deployments) con el que se asocia este estado. | +| `deployment` | `objeto` | El [despliegue](/rest/reference/repos#list-deployments) con el que se asocia este estado. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -537,8 +537,8 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl | Clave | Type | Descripción | | ---------------------- | ----------- | --------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`, `edited`, o `deleted`. | -| `label` | `object` | La etiqueta que se añadió. | -| `changes` | `object` | Los cambios a la etiqueta si la acción se `edited` (editó). | +| `label` | `objeto` | La etiqueta que se añadió. | +| `changes` | `objeto` | Los cambios a la etiqueta si la acción se `edited` (editó). | | `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | | `changes[color][from]` | `secuencia` | La versión previa del color si la acción se `edited` (editó). | {% data reusables.webhooks.repo_desc %} @@ -631,7 +631,7 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic | --------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción realizada. Puede ser `deleted`. | | `hook_id` | `número` | La id del webhook modificado. | -| `hook` | `object` | El webhook modificado. Este contendrá claves diferentes con base en el tipo de webhook que sea: de repositorio, organización, negocio, app, o GitHub Marketplace. | +| `hook` | `objeto` | El webhook modificado. Este contendrá claves diferentes con base en el tipo de webhook que sea: de repositorio, organización, negocio, app, o GitHub Marketplace. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} @@ -678,8 +678,8 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic | Clave | Type | Descripción | | ------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre:{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, o `member_invited`. | -| `invitation` | `object` | La invitación para el usuario o correo electrónico si la acción es `member_invited`. | -| `membership` | `object` | La membrecía entre el usuario y la organización. No está presente cuando la cción es `member_invited`. | +| `invitation` | `objeto` | La invitación para el usuario o correo electrónico si la acción es `member_invited`. | +| `membership` | `objeto` | La membrecía entre el usuario y la organización. No está presente cuando la cción es `member_invited`. | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} @@ -704,7 +704,7 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic | Clave | Type | Descripción | | -------------- | ----------- | ----------------------------------------------------------- | | `Acción` | `secuencia` | La acción realizada. Puede ser `blocked` o `unblocked`. | -| `blocked_user` | `object` | Información acerca del usuario que se bloqueó o desbloqueó. | +| `blocked_user` | `objeto` | Información acerca del usuario que se bloqueó o desbloqueó. | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} @@ -749,7 +749,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% | Clave | Type | Descripción | | ------- | -------- | ---------------------------------------------------------------------------------------------------------------- | | `id` | `número` | El idientificador único de la compilación de la página. | -| `build` | `object` | La misma terminal de [Listar las compilaciones de GitHub Pages](/rest/reference/repos#list-github-pages-builds). | +| `build` | `objeto` | La misma terminal de [Listar las compilaciones de GitHub Pages](/rest/reference/repos#list-github-pages-builds). | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -775,7 +775,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% | -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `zen` | `secuencia` | Secuencia aleatoria de GitHub zen. | | `hook_id` | `número` | La ID del webhook que activó el ping. | -| `hook` | `object` | La [configuración del webhook](/rest/reference/repos#get-a-repository-webhook). | +| `hook` | `objeto` | La [configuración del webhook](/rest/reference/repos#get-a-repository-webhook). | | `hook[app_id]` | `número` | Cuando registras una {% data variables.product.prodname_github_app %} nueva, {% data variables.product.product_name %} envía un evento de ping a la **URL del webhook** que especificaste durante el registro. El evento contiene la `app_id`, la cual se requiere para [autenticar](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) una app. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -978,7 +978,7 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend | `commits[][id]` | `secuencia` | El SHA de la confirmación. | | `commits[][timestamp]` | `secuencia` | La marca de tiempo de tipo ISO 8601 de la confirmación. | | `commits[][message]` | `secuencia` | El mensaje de la confirmación. | -| `commits[][author]` | `object` | El autor de git de la confirmación. | +| `commits[][author]` | `objeto` | El autor de git de la confirmación. | | `commits[][author][name]` | `secuencia` | El nombre del autor de git. | | `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | | `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | @@ -986,7 +986,7 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend | `commits[][added]` | `arreglo` | Un arreglo de archivos que se agregaron en la confirmación. | | `commits[][modified]` | `arreglo` | Un areglo de archivos que modificó la confirmación. | | `commits[][removed]` | `arreglo` | Un arreglo de archivos que se eliminaron en la confirmación. | -| `pusher` | `object` | El usuario que subió la confirmación. | +| `pusher` | `objeto` | El usuario que subió la confirmación. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1140,7 +1140,7 @@ Actividad relacionada con una asesoría de seguridad. Una asesoría de seguridad | Clave | Type | Descripción | | ------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. La acción puede ser una de entre `published`, `updated`, o `performed` en el caso de todos los eventos nuevos. | -| `security_advisory` | `object` | Los detalles de la asesoría de seguridad, incluyendo el resumen, descripción, y severidad. | +| `security_advisory` | `objeto` | Los detalles de la asesoría de seguridad, incluyendo el resumen, descripción, y severidad. | #### Ejemplo de carga útil del webhook @@ -1236,15 +1236,15 @@ Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname | Clave | Type | Descripción | | ----------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `created`, `deleted`, `edited`, `added_to_repository`, o `removed_from_repository`. | -| `team` | `object` | El equipo mismo. | -| `changes` | `object` | Los cambios al equipo si la acción está como `edited`. | +| `team` | `objeto` | El equipo mismo. | +| `changes` | `objeto` | Los cambios al equipo si la acción está como `edited`. | | `changes[description][from]` | `secuencia` | La versión previa de la descripción si la acción está como `edited`. | | `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | | `changes[privacy][from]` | `secuencia` | La versión previa de la privacidad del equipo si ésta se encuentra como `edited`. | | `changes[repository][permissions][from][admin]` | `boolean` | La versión previa de los permisos de `admin` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | | `changes[repository][permissions][from][pull]` | `boolean` | La versión previa de los permisos de `pull` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | | `changes[repository][permissions][from][push]` | `boolean` | La versión previa de los permisos de `push` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | -| `repositorio` | `object` | El repositorio que se agregó o eliminó del alcance del equipo si la acción se encuentra como `added_to_repository`, `removed_from_repository`, o `edited`. Para las acciones que estén como `edited`, el `repository` también contendrá los nuevos niveles de permiso del equipo para dicho repositorio. | +| `repositorio` | `objeto` | El repositorio que se agregó o eliminó del alcance del equipo si la acción se encuentra como `added_to_repository`, `removed_from_repository`, o `edited`. Para las acciones que estén como `edited`, el `repository` también contendrá los nuevos niveles de permiso del equipo para dicho repositorio. | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} @@ -1266,7 +1266,7 @@ Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname | Clave | Type | Descripción | | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------- | -| `team` | `object` | El [equipo](/rest/reference/teams) que se modificó. **Nota:** Los eventos anteriores podrían no incluir esto en la carga útil. | +| `team` | `objeto` | El [equipo](/rest/reference/teams) que se modificó. **Nota:** Los eventos anteriores podrían no incluir esto en la carga útil. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks.md index 228bb709a1..30d1a86499 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks.md @@ -1,7 +1,7 @@ --- title: Webhooks intro: 'Aprende a configurar, probar y asegurar los webhooks para integrarte con {% data variables.product.prodname_dotcom %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 6fd5ec9c1f..4d9920e7fd 100644 --- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -45,7 +45,7 @@ Puedes destacar los debates que contengan conversaciones importantes, útiles o Puedes compartir tu retroalimentación sobre los {% data variables.product.prodname_discussions %} con {% data variables.product.company_short %}. Para unirte a la conversación, consulta la sección [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). -### Further reading +### Leer más - "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" - "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)" diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index a2130dd1ce..e6ad948df1 100644 --- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -42,7 +42,7 @@ Puedes buscar debates y filtrar la lista de éstos en un repositorio. Para obten {% data reusables.discussions.you-can-convert-an-issue %} Para obtener más información, consulta la sección "[Moderar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)". -### Further reading +### Leer más - "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" - "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" 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 d42b85c675..e829b00573 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 @@ -41,7 +41,7 @@ Para encontrar más información, visita la sección "[ Configurar tu proyecto p 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)". -### Further reading +### Leer más - "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" - [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" diff --git a/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md index f3c14d8050..3506797279 100644 --- a/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -13,7 +13,7 @@ versions: 1. En la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %}, da clic en tu foto de perfil y luego en **Tus debates**. !["Tus debates" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) 1. Alterna entre **Creados** y **Comentados** para ver los debates que creaste o en los que has participado. -### Further reading +### Leer más - "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)" - "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" diff --git a/translations/es-ES/content/discussions/index.md b/translations/es-ES/content/discussions/index.md index 73218713ce..429f32ddbd 100644 --- a/translations/es-ES/content/discussions/index.md +++ b/translations/es-ES/content/discussions/index.md @@ -1,8 +1,8 @@ --- -title: Documentación sobre los debates de GitHub -beta_product: verdadero +title: GitHub Discussions Documentation +beta_product: true 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: @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -37,19 +37,19 @@ versions: {% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} {% if discussionsCommunityExamples %}
-

Comunidades que utilizan debates

+

Communities using discussions

{% render 'discussions-community-card' for discussionsCommunityExamples as example %}
{% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
{% octicon "search" width="24" %}
-

Lo sentimos, no hay respultados para

-

Parece que no tenemos un ejemplo que se adapte a tu filtro.
Intenta con otro filtro o agrega tu ejemplo de código

- Agrega tu comunidad {% octicon "arrow-right" %} +

Sorry, there is no result for

+

It looks like we don't have an example that fits your filter.
Try another filter or add your code example

+ Add your community {% octicon "arrow-right" %}
{% endif %} diff --git a/translations/es-ES/content/discussions/quickstart.md b/translations/es-ES/content/discussions/quickstart.md index d4c69465af..9ed50550bb 100644 --- a/translations/es-ES/content/discussions/quickstart.md +++ b/translations/es-ES/content/discussions/quickstart.md @@ -1,7 +1,7 @@ --- title: Guía de inicio rápido para los debates de GitHub intro: 'Habilita los {% data variables.product.prodname_discussions %} en un repositorio existente e inicia conversaciones con tu comunidad.' -allowTitleToDifferFromFilename: verdadero +allowTitleToDifferFromFilename: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..df8021ed9e --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +title: Acerca de Asesores de campus +intro: 'Como instructor o mentor, aprende a usar {% data variables.product.prodname_dotcom %} en tu escuela con el soporte técnico y la capacitación de Asesores de campus.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-advisors + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Profesores, maestros y mentores pueden usar la capacitación en línea de Asesores de campus para ser expertos en Git y {% data variables.product.prodname_dotcom %} y aprender las mejores prácticas para enseñarles a los alumnos con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Asesores de campus](https://education.github.com/teachers/advisors)". + +{% note %} + +**Nota:** Como instructor, no puedes crear cuentas de {% data variables.product.prodname_dotcom %} para tus alumnos. Los alumnos deben crear sus propias cuentas de {% data variables.product.prodname_dotcom %}. + +{% endnote %} diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..5355204f0b --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: Acerca de Expertos en campus +intro: 'Como estudiante, aprende las habilidades que necesitas para crear un portfolio real y una comunidad tecnológica de tu escuela, con la capacitación de Expertos en campus de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +Aprende habilidades comunicativas en público, escritura técnica, liderazgo comunitario y habilidades de desarrollo de software como un Experto en campus de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Expertos en campus](https://education.github.com/students/experts)". diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..37a4b7560e --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: Acerca de Educación GitHub para educadores e investigadores +intro: '{% data variables.product.prodname_education %} ofrece una variedad de herramientas para ayudar a los educadores y los investigadores a trabajar de manera más eficaz dentro y fuera del aula.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} para educadores + +Con los servicios y las herramientas de {% data variables.product.prodname_education %} para educadores de todos los niveles, puedes: + - Usar [{% data variables.product.prodname_classroom %}](https://classroom.github.com) para distribuir el código, hacerles comentarios a los estudiantes y recolectar las tareas en {% data variables.product.prodname_dotcom %}. + - Unirte a nuestra [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) para debatir tendencias actuales sobre educación tecnológica con tus pares de todo el mundo. + - Acceder y adaptar nuestros [planes de lecciones de código abierto](https://education.github.community/t/open-source-lesson-plans/1591) para enseñar Git y {% data variables.product.prodname_dotcom %}. + - [Solicitar un botín {% data variables.product.prodname_dotcom %}](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) con beneficios y materiales educativos para tus estudiantes. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} para investigadores + +Con los servicios y las herramientas de {% data variables.product.prodname_education %} para investigadores, puedes: + - Colaborar con otros en tu trabajo de investigación en todo el mundo en {% data variables.product.prodname_dotcom %}. + - [Aprender](https://education.github.com/stories) cómo usan {% data variables.product.prodname_dotcom %} las instituciones académicas en todo el mundo para su investigación. + {% data reusables.education.apply-for-team %} + +### Leer más + +- "[Acerca de {% data variables.product.prodname_education %} para estudiantes](/articles/about-github-education-for-students)" diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..afa27b7c74 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: Acerca de Educación GitHub para estudiantes +intro: '{% data variables.product.prodname_education %} le ofrece a los estudiantes experiencia práctica con acceso gratuito a diversas herramientas de programadores de los socios de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Usar {% data variables.product.prodname_dotcom %} para tus proyectos escolares es un modo práctico de colaborar con otros y crear un portfolio que exhiba experiencia práctica. + +{% data reusables.education.about-github-education-link %} + +Cualquiera con una cuenta de {% data variables.product.prodname_dotcom %} puede colaborar en repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %}. Como estudiante, también puedes solicitar el {% data variables.product.prodname_student_pack %}, que ofrece acceso gratuito a herramientas y servicios usados por programadores profesionales. Para obtener más información, consulta las secciones "[Postularse para un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" y [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +Si eres un miembro de un club de robótica FIRST, tu mentor puede solicitar un descuento de educador para que tu equipo pueda colaborar usando {% data variables.product.prodname_team %}, lo que permite repositorios privados y usuarios ilimitados, de forma gratuita. Para obtener más información, consulta la sección "[Postularse para un descuento para educador o investigador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)". + +### Leer más + +- "[Acerca de {% data variables.product.prodname_education %} para educadores e investigadores](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..2d08ca5c03 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: Acerca de Educación GitHub +intro: '{% data variables.product.prodname_education %} ofrece un producto gratuito especial para las escuelas que quieren aprovechar al máximo {% data variables.product.prodname_dotcom %} para su comunidad y que aceptan los requisitos específicos del programa.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +Si tu escuela acepta cumplir con ciertos requisitos, tu escuela secundaria, universidad o seminario intensivo profesional puede obtener {% data variables.product.prodname_education %}, que ofrece lo mejor de {% data variables.product.prodname_dotcom %} gratis, e incluye: +- {% data variables.product.prodname_ghe_cloud %} y/o {% data variables.product.prodname_ghe_server %} +- Capacitación para docentes para el Git principal y {% data variables.product.prodname_dotcom %} con nuestro programa Asesores de campus +- Acceso automatizado a las funciones premium de {% data variables.product.prodname_education %}, como {% data variables.product.prodname_student_pack %} +- Desarrollo de liderazgo y capacitación técnica para estudiantes con el programa Expertos en campus + +Para obtener más información, consulta la página [oficial {% data variables.product.prodname_education %}](https://education.github.com/partners/schools). + +Los maestros pueden administrar un curso sobre desarrollo de software con {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} te ayuda a distribuir código, proporcionar retroalimentación y administrar el trabajo del curso utilizando {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Administrar el trabajo del curso con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)". + +Para conocer más acerca de los programas de capacitación para líderes estudiantiles y docentes, consulta "[{% data variables.product.prodname_dotcom %} Expertos en campus](https://education.github.com/students/experts)" y "[Asesores de campus](https://education.github.com/teachers/advisors)". + +Si eres un estudiante validado o académico y tu escuela no está asociada con {% data variables.product.prodname_dotcom %} como una escuela {% data variables.product.prodname_education %}, aún puedes solicitar descuentos de forma individual para usar {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Usar {% 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)" o "[Usar {% 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/)". diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..d29a44e3dc --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: Aplicar un paquete de desarrollo para alumnos +intro: 'Como estudiante, puedes aplicar para el {% data variables.product.prodname_student_pack %}, que incluye ofertas y beneficios de los socios de {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Requisitos + +Para ser elegible para el {% data variables.product.prodname_student_pack %}, debes: +- Estar inscrito actualmente en un curso que otorgue un título o diploma que garantice un curso de estudio como colegio, escuela secundaria, facultad, universidad, escolarización en casa o institución educativa similar +- Tener una dirección de correo electrónico verificable suministrada por la escuela o cargar documentos que demuestren tu situación de estudiante actual +- Tener una cuenta de usuario de [{% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account) +- Tener al menos 13 años + +Entre los documentos que comprueban tu estado actual de alumno se incluye una foto de la ID de tu escuela con la fecha de inscripción actual, horario de clases, transcripción y carta de verificación de inscripción o de afiliación. + +Es posible que se te pida periódicamente que vuelvas a verificar tu estado académico actual para confirmar que eres estudiante. + +{% note %} + +**Nota:** No puedes transferir tus descuentos académicos de una cuenta a otra. Si tienes más de una cuenta a la que deseas aplicarle el descuenta, considera [fusionar](/articles/merging-multiple-user-accounts) tus cuentas de usuario y [cambiar el nombre](/articles/changing-your-github-username) a la cuenta retenida si así lo deseas. + +{% endnote %} + +Para obtener información sobre cómo renovar tu {% data variables.product.prodname_student_pack %}, consulta "[Caducidad y renovaciones](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)". + +### Aplicar para un {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. En "¿Qué es lo que mejor describe tu estado académico?", selecciona **Student** (Estudiante). ![Selecciona el estado académico](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Caducidad y renovaciones + +Una vez que caduca tu acceso a {% data variables.product.prodname_student_pack %}, puedes volver a aplicar si sigues siendo elegible, aunque es posible que las ofertas de algunos socios no puedan renovarse. La mayoría de las ofertas regulares de nuestros socios comiencen una vez que las configuraste. Para obtener más información, consulta la página [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). + +Para ver cuándo caduca tu acceso gratis al {% data variables.product.prodname_student_pack %}, visita los [ajustes de facturación](https://github.com/settings/billing). + +### Leer más + +- "[¿Por qué no aprobaron mi aplicación para un {% data variables.product.prodname_student_pack %}?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Registrarse para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..72ae5968e0 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: Postularse para un descuento de investigador o educador +intro: 'Si eres educador o investigador, puedes aplicar para recibir {% data variables.product.prodname_team %} para la cuenta de tu organización de manera gratuita.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### Acerca de descuentos para educadores e investigadores + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +Para obtener más información acerca de las cuentas de usuario en {% data variables.product.product_name %}, consulta la sección "[Registrarse para una cuenta nueva de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-a-new-github-account)". + +### Aplicar para un descuento de educador o investigador + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Actualizar tu organización + +Después de que se apruebe tu solicitud para un descuento de investigador o de maestro, puedes mejorar las organizaciones que utilizas con tu comunidad educativa a {% data variables.product.prodname_team %}, lo cual permitirá que tengas usuarios y repositorios privados ilimitados con todas las características gratuitamente. Puedes actualizar una organización existente o crear una organización nueva para actualizarla. + +#### Actualizar una organización existente + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Actualizar una organización nueva + +{% data reusables.education.upgrade-page %} +1. Da clic en {% octicon "plus" aria-label="The plus symbol" %}**Crear una organización**. ![Botón para crear una organizacion](/assets/images/help/education/create-org-button.png) +3. Lee la información, posteriormente da clic en **Crear organización**. ![Botón Create organization (Crear organización)](/assets/images/help/education/create-organization-button.png) +4. Debajo de "Elige tu plan", da clic en **Elegir {% data variables.product.prodname_free_team %}**. +5. Sigue las propuestas para crear tu organización. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Leer más + +- "[¿Por que no ha sido aprobada mi aplicación para recibir un descuento como educador o investigador?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [Videos de {% data variables.product.prodname_classroom %}](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..2214e409b8 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explora los beneficios de enseñar y aprender con GitHub Education +shortTitle: Explorar +intro: Aprende cómo {% data variables.product.prodname_education %} puede beneificiar a tu aula, trabajo escolar o investigación y cómo postularse para obtener acceso gratuito a varias herramientas de desarrollo de los socios de {% data variables.product.company_short %}. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Índice + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..c532b9a6e6 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub at your educational institution +intro: 'Maximize the benefits of using {% data variables.product.prodname_dotcom %} at your institution for your students, instructors, and IT staff with {% data variables.product.prodname_education %} and our various training programs for students and instructors.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..8512b9b548 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub for your schoolwork +intro: 'As a student, use {% data variables.product.prodname_dotcom %} to collaborate on your school projects and build real-world experience.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..3dc25db887 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub in your classroom and research +intro: 'As an educator or researcher, use {% data variables.product.prodname_dotcom %} to collaborate on your work in a classroom, student or research group, and more.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..f80e837b77 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +title: '¿Por qué no se aprobó mi solicitud para un paquete de desarrollo para estudiantes?' +intro: 'Revisa las razones comunes por las que las solicitudes para el {% data variables.product.prodname_student_pack %} no se aprueban y lee las sugerencias para volver a solicitarlo con éxito.' +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Documentos de afiliación académica poco claros + +Si la imagen que cargaste no identifica claramente tu situación académica actual, solicitamos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico con un dominio no verificado + +Si tu dirección de correo electrónico académica tiene un dominio no verificado, requerimos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico de una escuela con políticas de correo electrónico poco estrictas + +Si tu escuela expide direcciones de correo electrónico antes del pago de la inscripción, requerimos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +Si tienes otras preguntas o inquietudes acerca del dominio de la escuela solicita al personal de informática de tu escuela que nos contacte. + +### Dirección de correo electrónico académica que ya se usó + +Si tu dirección de correo electrónico académica ya se usó para solicitar un {% data variables.product.prodname_student_pack %} para una cuenta {% data variables.product.prodname_dotcom %} diferente, no puedes volver a usar la dirección de correo electrónico académica para solicitar con éxito otro {% data variables.product.prodname_student_pack %} hasta que ese descuento haya vencido. + +{% note %} + +**Nota:** mantener más de una cuenta individual no respeta los {% data variables.product.prodname_dotcom %} [Términos del servicio](/articles/github-terms-of-service/#3-account-requirements). + +{% endnote %} + +Si tienes más de una cuenta de usuario, debes fusionar tus cuentas. Para conservar el descuento, debes mantener la cuenta a la que se le otorgó el descuento. Puedes renombrar la cuenta retenida y conservar tu historial de contribuciones agregando todas las direcciones de correo electrónico a la cuenta retenida. + +Para obtener más información, consulta: +- "[Fusionar cuentas de usuario múltiples](/articles/merging-multiple-user-accounts)" +- "[Cambiar tu nombre de usuario {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)" +- "[Agregar una dirección de correo electrónico a tu cuenta {% data variables.product.prodname_dotcom %}](/articles/adding-an-email-address-to-your-github-account)" + +### Situación de estudiante inadmisible + +No eres apto para un {% data variables.product.prodname_student_pack %} si: +- Estás inscrito en un programa de aprendizaje informal que no forma parte del [Programa del Campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/schools) y no estás inscrito en un diploma o título que otorgue un reconocimiento de estudios. +- Tienes menos de 13 años. + +Tu instructor todavía puede solicitar un descuento para uso escolar {% data variables.product.prodname_education %}. Si estás estudiando en una escuela o programa intensivo de codificación, podrás inscribirte en {% data variables.product.prodname_student_pack %} si tu escuela se une al [Programa del campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/schools). + +### Leer más + +- "[Solicitar un paquete de desarrollo para estudiantes](/articles/applying-for-a-student-developer-pack)" +- "[Postularse para un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..357b4ad2f6 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: '¿Por qué mi solicitud para un descuento de educador o de investigador no se aprobó?' +intro: Revisa las razones comunes por las que las solicitudes para un descuento de educador o de investigador no se aprueban y lee las sugerencias para volver a solicitarlo con éxito. +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Sugerencia:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Documentos poco claros de la prueba de afiliación + +Si la imagen que cargaste no identifica claramente tu empleo actual con una escuela o una universidad, debes volver a presentar la solicitud y cargar otra imagen de la identificación de tu facultad o carta de verificación de empleo con información clara. + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico con un dominio no verificado + +Si tu dirección de correo electrónico académica tiene un dominio no verificado, podemos solicitar más pruebas de tu situación académica. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Usar un correo electrónico académico de una escuela con políticas de correo electrónico poco estrictas + +Si los ex alumnos y los profesores retirados de tu escuela tienen acceso vitalicio a las direcciones de correo electrónico suministradas por la escuela, podemos requerir más pruebas de tu situación académica. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +Si tienes otras preguntas o inquietudes acerca del dominio de la escuela, solicita al personal de informática de tu escuela que nos contacte. + +### Personas que no son estudiantes solicitan un paquete de desarrollo para estudiantes + +Los educadores y los investigadores no son elegibles para las ofertas de los socios que vienen con el [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Cuando vuelves a presentar una solicitud, asegúrate de elegir **Profesor** para describir tu situación académica. + +### Leer más + +- "[Solicitar un descuento de educador o de investigador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/es-ES/content/education/guides.md b/translations/es-ES/content/education/guides.md index 683d83afc2..50b347ee8e 100644 --- a/translations/es-ES/content/education/guides.md +++ b/translations/es-ES/content/education/guides.md @@ -1,45 +1,45 @@ --- -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.' -allowTitleToDifferFromFilename: verdadero +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: free-pro-team: '*' --- -### 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) -- [Postularse para un descuento de investigador o educador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Aplicar un paquete de desarrollo para alumnos](/education/teach-and-learn-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) +- [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) -- [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) +- [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/teach-and-learn-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/teach-and-learn-with-github-education/about-campus-experts) -- [Acerca de Asesores de campus](/education/teach-and-learn-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/index.md b/translations/es-ES/content/education/index.md index 88b8be6bac..c5177cc6ab 100644 --- a/translations/es-ES/content/education/index.md +++ b/translations/es-ES/content/education/index.md @@ -1,45 +1,41 @@ --- title: Documentación de GitHub Education shortTitle: Educación -intro: "{% data variables.product.prodname_education %} te permite enseñar o aprender sobre desarrollo de software con las herramientas y el apoyo de la plataforma y la comunidad de {% data variables.product.company_short %}." +intro: '{% data variables.product.prodname_education %} te permite enseñar o aprender sobre desarrollo de software con las herramientas y el apoyo de la plataforma y la comunidad de {% data variables.product.company_short %}.' introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom changelog: - - - title: 'Intenta hacer algo nuevo en el día local del Hack: Aprende' + - title: 'Intenta hacer algo nuevo en el día local del Hack: Aprende' date: '2020-10-15' - href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ - - - title: 'Educación remota: Crear una comunidad mediante las experiencias compartidas' - date: '24-09-2020' - href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ - - - title: 'Educación remota: Una serie de mejores prácticas para las comunidades de campus en línea' - date: '10-09-2020' - href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ - - - title: Bienvenido a la clase de inauguración de MLH Fellows + href: 'https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/' + - title: 'Educación remota: Crear una comunidad mediante las experiencias compartidas' + date: '2020-09-24' + href: 'https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/' + - title: 'Educación remota: Una serie de mejores prácticas para las comunidades de campus en línea' + date: '2020-09-10' + href: 'https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/' + - title: Bienvenido a la clase de inauguración de MLH Fellows date: '2020-06-24' - href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ + href: 'https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/' layout: product-landing versions: free-pro-team: '*' --- - + diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md index f69f997984..beb2e39ab9 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -26,6 +26,6 @@ Predeterminadamente, MakeCode Arcade se encuentra configurado para subir las tar ![Funcionalidad de control de versiones de MakeCode Arcade](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) -### Further reading +### Leer más - "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index 7b64e53af7..3bea3aa51f 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -28,6 +28,6 @@ Predeterminadamente, Repl.it se configura para subir información al repositorio Para obtener más información sobre cómo utilizar Git en Repl.it, consulta el [Tutorial de Repl.it + Git](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) en el sitio web de Repl.it. -### Further reading +### Leer más - "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 19a519d3fc..38c2bac2d9 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -28,6 +28,6 @@ Para obtener más información sobre la terminología de {% data variables.produ Para obtener más información sobre cómo dar clases con {% data variables.product.prodname_classroom %}, consulta la sección "[Dar clases con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)". -### Further reading +### Leer más -- "[Aprende y da clases con {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" +- "[Explore the benefits of teaching and learning with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index b19eccf512..2ce8f3f73a 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -138,8 +138,8 @@ Puedes ver los equipos que están trabajando o que han emitido una tarea en la p - 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)". -### Further reading +### Leer más -- "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[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)" - "[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 %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index bc675f1718..e27eec5a2f 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,9 +11,7 @@ Puedes utilizar un repositorio de plantilla en {% data variables.product.product Para utilizar el repositorio de plantilla para tu tarea, éste debe pertenecer a tu organización, o su visibilidad debe ser pública. -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} Para obtener más información, consulta la sección "[Configurar los ajustes predeterminados para los repositorios de las tareas](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)". - -### Further reading +### Leer más - "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" - "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index 8880a78650..632749e5b1 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -118,7 +118,7 @@ Puedes ver si un alumno se unió al aula y aceptó o emitió una tarea en la pes - 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)". -### Further reading +### Leer más -- "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[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)" - "[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)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md index b7e711bbed..0a08baefa7 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -1,8 +1,8 @@ --- title: Inicia con GitHub Classroom shortTitle: Empezar -intro: Aprende cómo configurar y utilizar {% data variables.product.prodname_classroom %} para administrar tu curso. -mapTopic: verdadero +intro: 'Aprende cómo configurar y utilizar {% data variables.product.prodname_classroom %} para administrar tu curso.' +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md index bee1dc7f7e..b098154814 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/glossary.md @@ -47,6 +47,6 @@ Un registro de alumnos permite a los maestros administrar a los alumnos y emitir --- -### Further reading +### Leer más - "[Glosario de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-glossary)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md index 4b4b6a4f31..616e65ffb0 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md index e0ece3f059..c26b923341 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -1,8 +1,8 @@ --- title: Integrar a GitHub Classroom con un IDE shortTitle: Integrar con un IDE -intro: Puedes ayudar a que tus alumnos escriban, prueben y depuren código si preconfiguras un ambiente de desarrollo para los repositorios de tareas en {% data variables.product.prodname_classroom %}. -mapTopic: verdadero +intro: 'Puedes ayudar a que tus alumnos escriban, prueben y depuren código si preconfiguras un ambiente de desarrollo para los repositorios de tareas en {% data variables.product.prodname_classroom %}.' +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md index f0a0050488..8eecf5d9ea 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -37,6 +37,6 @@ La primera vez que configuras una tarea con un IDE en elínea, debes autorizar l En todos tus repositorios, otorga acceso de **lectura** a la app para metadatos, administración y código, y acceso de **escritura** para administración y código. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". -### Further reading +### Leer más - "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md index 11ad0e7cfa..2c0e0f80ef 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -1,7 +1,7 @@ --- title: Aprende con GitHub Classroom -intro: Puedes participar en el trabajo del curso en {% data variables.product.prodname_classroom %} y ver los resultados de tu maestro. -mapTopic: verdadero +intro: 'Puedes participar en el trabajo del curso en {% data variables.product.prodname_classroom %} y ver los resultados de tu maestro.' +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md index 45b9f657ad..dd7b38798b 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -26,6 +26,6 @@ Para crear y acceder a la solicitud de cambios de retroalimentación, debes habi 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)." -### Further reading +### Leer más - "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index f5deeeb19f..5d697d2605 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ Puedes archuivar un aula que ya no utilices en {% data variables.product.prodnam {% data reusables.classroom.click-settings %} 1. A la derecha de "Borrar esta aula", da clic en **Borrar aula**. ![Botón de "Borrar un repositorio"](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **Lee las advertencias**. -1. Para verificar que estás borrando el aula correcta, teclea el nombre del aula que quieres borrar. ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Para verificar que estás borrando el aula correcta, teclea el nombre del aula que quieres borrar. ![Modo para borrar un aula con advertencias y campo de texto para el nombre del aula](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. Da clic en **Borrar aula**. ![Botón de "Borrar aula"](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 7bb46bc452..e5dbcf02c1 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -1,8 +1,11 @@ --- -title: Enseña con GitHub Classroom -intro: Aprende cómo configurar tu aula y tus tareas. -mapTopic: verdadero +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md index 3b37273b15..afd3a6b81d 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -78,6 +78,6 @@ Puedes agregar, editar o borrar las pruebas de calificación automática para un 1. A la derecha de una emisión, da clic en **Ver prueba**. ![Botón de "Ver tarea" para una emisión de una tarea](/assets/images/help/classroom/assignments-click-view-test.png) 1. Revisa la salida de la prueba. 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)". -### Further reading +### Leer más - [Documentación de {% data variables.product.prodname_actions %}](/actions) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md index a976a29e04..0deeed4460 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -25,6 +25,6 @@ Puedes dar clic en una ejecución de prueba específica para revisar la bitácor ![Las bitácoras de resultados de las pruebas de un "flujo de trabajo de calificación automática de {% data variables.product.prodname_classroom %}" en {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) -### Further reading +### Leer más - "[Acerca de las verificaciones de estado](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/es-ES/content/education/quickstart.md b/translations/es-ES/content/education/quickstart.md index 4a185f18e6..95a8171387 100644 --- a/translations/es-ES/content/education/quickstart.md +++ b/translations/es-ES/content/education/quickstart.md @@ -1,7 +1,7 @@ --- title: Inicio rápido para GitHub Educators -intro: En cerca de 15 minutos, los maestros pueden iniciar con descuentos, capacitación y herramientas para {% data variables.product.company_short %}, posteriormente, pueden crear un aula para los alumnos en un curso de desarrollo de software utilizando {% data variables.product.prodname_classroom %}. -allowTitleToDifferFromFilename: verdadero +intro: 'En cerca de 15 minutos, los maestros pueden iniciar con descuentos, capacitación y herramientas para {% data variables.product.company_short %}, posteriormente, pueden crear un aula para los alumnos en un curso de desarrollo de software utilizando {% data variables.product.prodname_classroom %}.' +allowTitleToDifferFromFilename: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md index c0ebd2c0c2..3bfcd9b5d8 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -44,6 +44,6 @@ Puedes configurar las actualizaciones de versión para los repositorios que cont 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)". -### About notifications for {% data variables.product.prodname_dependabot %} version updates +### Acerca de las notificaciones para las actualizaciones de versión del {% data variables.product.prodname_dependabot %} -You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} version updates. 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)". +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)". diff --git a/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index c79561d405..f183cf5248 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -33,10 +33,10 @@ Puedes filtrar las notificaciones por correo electrónico que recibes para las i {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 5. Escribe hasta dos direcciones de correo electrónico, separadas por espacio en blanco, donde quieras que se envíen las notificaciones. Si quieres enviar los correos electrónicos a más de dos cuentas, configura una de las direcciones de correo electrónico a una dirección de correo electrónico del grupo. ![Cuadro de texto dirección de correo electrónico](/assets/images/help/settings/email_services_addresses.png) -6. Si operas tu propio servidor, puedes verificar la integridad de los correos electrónicos mediante el token **Secreto**. Este token se envía con el correo electrónico como el encabezado `Aprobado`. Si el encabezado `Aprobado` coincide con el token que enviaste, puedes confiar en que el correo electrónico es de {% data variables.product.product_name %}. ![Cuadro de texto correo electrónico secreto](/assets/images/help/settings/email_services_token.png) -7. Haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/help/settings/save_notification_settings.png) +1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}. ![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png) +7. Click **Setup notifications**. ![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png) -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" {% else %} diff --git a/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md index b7ccd20dbb..a9173436e6 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/es-ES/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} +El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-linear-history)".{% endif %} ### Combinar tus confirmaciones de fusión diff --git a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md index 59a03b1954..5c11cdfad7 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md @@ -1,6 +1,6 @@ --- title: Acerca de las ramas protegidas -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.' +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.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/about-protected-branches @@ -21,60 +21,60 @@ versions: github-ae: '*' --- -### 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 %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)." +{% 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.pull_requests.you-can-auto-merge %} -### About branch protection settings +### Acerca de la configuración de protección de rama -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) +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) - [Requerir confirmaciones firmadas](#require-signed-commits) -- [Require linear history](#require-linear-history) -- [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) +- [Requerir un historial linear](#require-linear-history) +- [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) -#### Require pull request reviews before merging +#### Requerir revisiones de solicitudes de cambio antes de fusionarlas {% data reusables.pull_requests.required-reviews-for-prs-summary %} -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 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 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. +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. {% data reusables.repositories.review-policy-overlapping-commits %} -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. +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. ```shell remote: error: GH006: Protected branch update failed for refs/heads/main. remote: error: Changes have been requested. ``` -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. Para obtener información acerca de las ramas base, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." +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 restrict the ability to dismiss pull request reviews to specific people or teams. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". +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 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. +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. -#### Require status checks before merging +#### Requerir verificaciones de estado antes de las fusiones 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)". -Antes de que puedas habilitar las verificaciones de estado requeridas, debes configurar el repositorio para utilizar la API de estado. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation. +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. -After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. 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. +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. {% note %} @@ -82,7 +82,7 @@ After enabling required status checks, all required status checks must pass befo {% endnote %} -Puedes configurar las verificaciones de estado requeridas para que sean "laxas" o "estrictas". 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. +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 | | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -90,7 +90,7 @@ Puedes configurar las verificaciones de estado requeridas para que sean "laxas" | **Flexible** | La casilla **Require branches to be up-to-date before merging** (Las ramas deben estar actualizadas antes de la fusión) **no** está marcada. | 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. | -For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." +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)". #### Requerir confirmaciones firmadas @@ -98,38 +98,38 @@ Cuando habilitas el requerir el firmado de confirmaciones en una rama, los colab {% note %} -**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. +**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. {% endnote %} Siempre puedes subir confirmaciones locales a la rama si estas se firmaron y verificaron. {% if currentVersion == "free-pro-team@latest" %}También puedes fusionar las confirmaciones firmadas y verificadas en la rama si utilizas una solicitud de cambios en {% data variables.product.product_name %}. Sin embargo, no puedes combinar y fusionar una solicitud de cambios en la rama en {% data variables.product.product_name %} a menos de que seas el autor de la misma.{% else %} Sin embargo, no puedes fusionar una solicitud de cambios en la rama en {% data variables.product.product_name %}.{% endif %} Puedes {% if currentVersion == "free-pro-team@latest" %}combinar y {% endif %} fusionar solicitudes de cambios 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)". -{% if currentVersion == "free-pro-team@latest" %} 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 %} +{% if currentVersion == "free-pro-team@latest" %} 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 %} -#### Require linear history +#### Requerir un historial linear -Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. 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. A strictly linear commit history can help teams reverse changes more easily. 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)." +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)." 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)." -#### Include administrators +#### Incluir administradores -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. +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. -#### Restrict who can push to matching branches +#### Restringir quiénes pueden subir a las ramas coincidentes {% if currentVersion == "free-pro-team@latest" %} -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 %}. +Puedes habilitar las 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 %}. {% 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. 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. -#### Allow force pushes +#### Permitir las subidas forzadas -By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. 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. +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. 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. @@ -137,6 +137,6 @@ Habilitar las subidas forzadas no invalidará ninguna otra regla de protección 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 %} -#### Allow deletions +#### Permitir el borrado -Por defecto, no puedes eliminar una rama protegida. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch. +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. diff --git a/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md b/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md index 2d18408607..a366464891 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/es-ES/content/github/administering-a-repository/about-secret-scanning.md @@ -15,9 +15,9 @@ versions: {% 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. -Service providers can partner with +Los proveedores de servicios se pueden asociar con -{% data variables.product.company_short %} to provide their secret formats for scanning.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Secret scanning](/developers/overview/secret-scanning)." +{% data variables.product.company_short %} para proporcionar sus formatos secretos para el escaneo.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Escaneo de secretos](/developers/overview/secret-scanning)". {% endif %} {% data reusables.secret-scanning.about-secret-scanning %} @@ -25,9 +25,9 @@ Service providers can partner with {% if currentVersion == "free-pro-team@latest" %} ### Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios públicos -{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. 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. +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. -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. For an overview of how we work with token-issuing partners, see "[Secret scanning](/developers/overview/secret-scanning)." +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 los socios que emiten tokens, consulta la sección "[Escaneo de secretos](/developers/overview/secret-scanning)". Actualmente, {% data variables.product.product_name %} escanea los repositorios públicos en busca de secretos emitidos por los siguientes proveedores de servicios. @@ -37,28 +37,28 @@ Actualmente, {% data variables.product.product_name %} escanea los repositorios {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} -### About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %} +### Acerca del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.product_name %} -{% 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. +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. {% endif %} -If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %} 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.{% if currentVersion == "free-pro-team@latest" %} {% 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +Si eres un administrador de repositorio o un propietario de organización, puedes habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %} privados{% endif %} que pertenezcan a las organizaciones. Puedes habilitar el {% data variables.product.prodname_secret_scanning %} para todos tus repositorios, o para todos los repositorios nuevos dentro de tu organización.{% if currentVersion == "free-pro-team@latest" %} El {% data variables.product.prodname_secret_scanning_caps %} mp se encuentra disponible para los repositorios privados que pertenezcan a los usuarios individuales.{% endif %} para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" y "[Administrar la configuración de seguridad y análisis para tu organziación](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". -When you push commits to a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. +Cuando subes tus confirmaciones a un repositorio{% if currentVersion == "free-pro-team@latest" %} privado{% endif %} que tenga habilitado el {% data variables.product.prodname_secret_scanning %}, {% data variables.product.prodname_dotcom %} escanea el contenido de las confirmaciones para encontrar secretos. -When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} sends alerts. +Cuando el {% data variables.product.prodname_secret_scanning %} detecta un secreto en un repositorio{% if currentVersion == "free-pro-team@latest" %} privado{% endif %}, {% data variables.product.prodname_dotcom %} envía alertas. - {% 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 %} muestra una alerta en el repositorio. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)". -Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +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)". {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -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 %} +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 %} -{% data variables.product.prodname_dotcom %} currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers. +{% data variables.product.prodname_dotcom %} escanea actualmente los repositorios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} para los secretos que emiten los siguientes proveedores de servicios. {% data reusables.secret-scanning.partner-secret-list-private-repo %} @@ -68,7 +68,7 @@ To monitor results from {% endnote %} -### Further reading +### Leer más - [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" -- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" +- "[Mantener la seguridad en tu cuenta y tus datos](/github/authenticating-to-github/keeping-your-account-and-data-secure)" diff --git a/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md b/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md index 437f1b576d..c47f3bcd40 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md @@ -31,14 +31,14 @@ El primer paso para asegurar un repositorio es configurar quién puede ver y mod {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} - **{% data variables.product.prodname_dependabot_alerts %}** - View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. 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)". + 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)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} - **Las actualizaciones de versión del {% data variables.product.prodname_dependabot %}** -Use +Utiliza - {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. 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)". + el {% data variables.product.prodname_dependabot %} para levantar solicitudes de cambios automáticamente para mantener actualizadas tus dependencias. 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)". {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} @@ -48,9 +48,9 @@ Use 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). - **Secretos detectados** -View any secrets that +Visualiza cualquier secreto que - {% data variables.product.prodname_dotcom %} has found in your code. 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). + haya encontrado el {% data variables.product.prodname_dotcom %} 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). {% endif %} ### Explorar las dependencias diff --git a/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md b/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md index 1607b01f85..88ec96141f 100644 --- a/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md +++ b/translations/es-ES/content/github/administering-a-repository/automation-for-release-forms-with-query-parameters.md @@ -19,12 +19,12 @@ Si creas una URL no válida usando los parámetros de consulta o si no tienen lo | Parámetro de consulta | Ejemplo | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `tag` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1` create un lanzamiento en función de la etiqueta denominada "v1.0.1". | -| `destino` | `https://github.com/octo-org/octo-repo/releases/new?target=release-1.0.1` create un lanzamiento en función de la última confirmación a la rama "release-1.0.1". | +| `etiqueta` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1` create un lanzamiento en función de la etiqueta denominada "v1.0.1". | +| `target` | `https://github.com/octo-org/octo-repo/releases/new?target=release-1.0.1` create un lanzamiento en función de la última confirmación a la rama "release-1.0.1". | | `título` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1&title=octo-1.0.1` crea un lanzamiento denominado "octo-1.0.1" basado en una etiqueta denominada "v1.0.1". | -| `body` | `https://github.com/octo-org/octo-repo/releases/new?body=Adds+widgets+support` crea un lanzamiento con la descripción "Adds widget support" (Agrega soporte de widget) en el cuerpo del lanzamiento. | +| `cuerpo` | `https://github.com/octo-org/octo-repo/releases/new?body=Adds+widgets+support` crea un lanzamiento con la descripción "Adds widget support" (Agrega soporte de widget) en el cuerpo del lanzamiento. | | `lanzamiento previo` | `https://github.com/octo-org/octo-repo/releases/new?prerelease=1` crea un lanzamiento que será identificado como listo para no producción. | -### Further reading +### Leer más - "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" diff --git a/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md b/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md index 486536ab1f..6d28d08199 100644 --- a/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,9 +23,9 @@ Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." +También puedes renombrar la rama predeterminada. Para obtener más información, consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)". {% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index ab50a586b9..18cee356cd 100644 --- a/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/es-ES/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -21,14 +21,14 @@ El archivo *dependabot.yml* debe comenzar con `version: 2`, seguido de un conjun | Opción | Requerido | Descripción | |:-------------------------------------------------------------------------- |:---------:|:--------------------------------------------------------------------------------------------- | | [`package-ecosystem`](#package-ecosystem) | **X** | Administrador de paquetes a utilizar | -| [`directory`](#directory) | **X** | Ubicación de los manifiestos del paquete | +| [`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 | | [`etiquetas`](#labels) | | Las etiquetas a configurar en las solicitudes de extracción | -| [`milestone`](#milestone) | | Hito 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 | @@ -91,7 +91,7 @@ updates: interval: "daily" ``` -### `directory` +### `directorio` **Requerido** Debes definir la ubicación de los manifiestos de paquete para cada administrador de paquete (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`. @@ -336,7 +336,7 @@ updates: - "dependencies" ``` -### `milestone` +### `hito` 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`. diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md b/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md index 55ef3782e1..14524a8c87 100644 --- a/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md +++ b/translations/es-ES/content/github/administering-a-repository/configuring-commit-squashing-for-pull-requests.md @@ -18,7 +18,7 @@ versions: 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) -### Further reading +### Leer más - "[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)" diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md b/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md index e5c512b416..b72ee662ff 100644 --- a/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md +++ b/translations/es-ES/content/github/administering-a-repository/configuring-pull-request-merges.md @@ -1,7 +1,7 @@ --- title: Configurar fusiones de solicitudes de extracción intro: 'Puedes configurar las fusiones de solicitudes de cambio en {% data variables.product.product_location %} para que coincidan con tu flujo de trabajo y con tus preferencias para administrar el historial de Git.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/configuring-pull-request-merges versions: diff --git a/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 77f705197e..255f113219 100644 --- a/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -1,7 +1,7 @@ --- -title: Configuring secret scanning for your repositories -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' -permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +title: Configurar el escaneo de secretos para tus repositorios +intro: 'Puedes configurar la forma en que {% data variables.product.prodname_dotcom %} escanea tus repositorios para encontrar secretos.' +permissions: 'Las personas con permisos administrativos en un repositorio pueden habilitar el {% data variables.product.prodname_secret_scanning %} en éste.' redirect_from: - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories product: '{% data reusables.gated-features.secret-scanning %}' @@ -16,30 +16,30 @@ versions: {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. +**Nota:** El {% data variables.product.prodname_secret_scanning_caps %} se habilita predeterminadamente en los repositorios públicos y no puede apagarse. Puedes configurar el {% data variables.product.prodname_secret_scanning %} solo para tus repositorios privados. {% endnote %} {% endif %} -### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories +### Habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} {% if currentVersion == "free-pro-team@latest" %} -4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) -5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) -6. When you enable -{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} +4. Si no se muestra el "{% data variables.product.prodname_secret_scanning_caps %}" en la página, primero necesitarás habilitar la {% data variables.product.prodname_GH_advanced_security %}. A la derecha de "{% data variables.product.prodname_GH_advanced_security %}", da clic en **Habilitar**. ![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Da clic en **Habilitar la {% data variables.product.prodname_GH_advanced_security %} para este repositorio** para confirmar la acción. ![Confirmar la habilitación de la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. Cuando habilitas +la {% data variables.product.prodname_GH_advanced_security %}, esto podría habilitar el {% data variables.product.prodname_secret_scanning %} automáticamente para el repositorio (esto se controla en la configuración de la organización). Si se muestra "{% data variables.product.prodname_secret_scanning_caps %}" con un botón de **Habilitar**, aún necesitarás habilitar el {% data variables.product.prodname_secret_scanning %} si das clic en **Habilitar**. Si ves un botón de **Inhabilitar**, entonces el {% data variables.product.prodname_secret_scanning %} ya se encuentra habilitado. + ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} -4. To the right of " -{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) +4. A la derecha de " +{% data variables.product.prodname_secret_scanning_caps %}", da clic en **Habilitar**. + ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-ghe.png) {% endif %} -### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories +### Excluir alertas del {% data variables.product.prodname_secret_scanning %} en los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} Puedes utilizar un archivo *secret_scanning.yml* para excluir los directorios de {% data variables.product.prodname_secret_scanning %}. Por ejemplo, puedes excluir directorios que contengan pruebas o contenido generado aleatoriamente. @@ -64,6 +64,6 @@ Puedes utilizar un archivo *secret_scanning.yml* para excluir los directorios de También puedes ignorar alertas individuales de {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)". -### Further reading +### Leer más - "[Administrar la seguridad y la configuración de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md b/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md index 39410f1f99..38a83754e6 100644 --- a/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md +++ b/translations/es-ES/content/github/administering-a-repository/customizing-how-changed-files-appear-on-github.md @@ -20,6 +20,6 @@ Usa un archivo *.gitattributes* para marcar los archivos que coincidan con un "p search/index.json linguist-generated=true ``` -### Further reading +### Leer más - "[Código generado](https://github.com/github/linguist/#generated-code)" en la documentación del lingüista - "[Crear archivos nuevos](/articles/creating-new-files/)" diff --git a/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md b/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md index 576f79cdbe..9a76f260ff 100644 --- a/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md +++ b/translations/es-ES/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md @@ -6,7 +6,7 @@ redirect_from: - /articles/defining-the-mergeability-of-pull-requests - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions product: '{% data reusables.gated-features.protected-branches %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md index 1c448fafbe..6cede3d1e5 100644 --- a/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md +++ b/translations/es-ES/content/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request.md @@ -34,7 +34,7 @@ Puedes restaurar la rama de encabezado de una solicitud de extracción cerrada. 4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas restaurar. 5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Restaurar rama**. ![Botón Restaurar rama eliminada](/assets/images/help/branches/branches-restore-deleted.png) -### Further reading +### Leer más - "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)" - "[Administrar el borrado automático de ramas](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)" diff --git a/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md index 29b2c72d56..2e0fb186bc 100644 --- a/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md @@ -73,6 +73,6 @@ Cualquier usuario que cuente con permisos de administración puede habilitar un {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" - "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md index ecdc7e2800..6fc69075a0 100644 --- a/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -14,7 +14,7 @@ versions: {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} 1. Para inhabilitar los debates, debajo de "Características", deselecciona **Debates**. -### Further reading +### Leer más - "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Administrar debates para tu comunidad](/discussions/managing-discussions-for-your-community)" diff --git a/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md b/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md index 52808817e0..b0f77d360f 100644 --- a/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/es-ES/content/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot.md @@ -44,6 +44,6 @@ updates: 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)". -### Further reading +### Leer más - "[Acerca de GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)" diff --git a/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md b/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md index 095b276bd4..a5afba7a58 100644 --- a/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md +++ b/translations/es-ES/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically.md @@ -1,7 +1,7 @@ --- title: Mantener tus dependencias actualizadas automáticamente intro: 'El {% data variables.product.prodname_dependabot %} puede mantener tus dependencias de repositorio automáticamente.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md index 8780363915..bcdb9fa6a2 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -1,6 +1,6 @@ --- -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.' +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.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/configuring-protected-branches @@ -20,14 +20,14 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: People with admin permissions to a repository can manage branch protection rules. +permissions: Las personas con permisos administrativos en un repositorio pueden administrar las reglas de protección de rama. --- -### About branch protection rules +### Acerca de las reglas de protección de rama {% data reusables.repositories.branch-rules-example %} -You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. 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. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. 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). +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). 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. @@ -35,48 +35,48 @@ Las reglas de rama protegida que mencionen un caracter especial, como `*`, `?` o 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. -For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +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)". -### Creating a branch protection rule +### Crear una regla de protección de rama -When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. +Cuando creas una regla de rama, la rama que especifiques no tendrá que en el repositorio aún. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} {% data reusables.repositories.add-branch-protection-rules %} -1. Optionally, enable required pull request reviews. - - Under "Protect matching branches", select **Require pull request reviews before merging**. ![Casilla de verificación Restricción de revisión de solicitud de extracción](/assets/images/help/repository/PR-reviews-required.png) - - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![Menú desplegable para seleccionar el número de aprobaciones de revisión requeridas](/assets/images/help/repository/number-of-required-review-approvals.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**. ![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) - - 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**. 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) - - 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. 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. Optionally, enable required status checks. +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) - - 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**. ![Casilla de verificación de estado estricta o poco estricta](/assets/images/help/repository/protecting-branch-loose-status.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) -1. Optionally, select **Require signed commits**. ![Opción Requerir confirmaciones firmadas](/assets/images/help/repository/require-signed-commits.png) -1. Optionally, select **Require linear history**. ![Opción para requerir historial linear](/assets/images/help/repository/required-linear-history.png) +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. También puedes seleccionar **Incluir administradores**. ![Casilla de verificación Incluir administradores](/assets/images/help/repository/include-admins-protected-branches.png) -1. Optionally,{% if currentVersion == "free-pro-team@latest" %} 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**. ![Casilla de verificación para restricción de rama](/assets/images/help/repository/restrict-branch.png) +1. Opcionalmente,{% if currentVersion == "free-pro-team@latest" %} 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. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Permitir la opción de subida de información forzada](/assets/images/help/repository/allow-force-pushes.png) -1. Optionally, select **Allow deletions**. ![Opción para habilitar las eliminaciones de ramas](/assets/images/help/repository/allow-branch-deletions.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**. -### Editing a branch protection rule +### Editar una regla de protección de rama {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. To the right of the branch protection rule you want to edit, click **Edit**. ![Botón editar](/assets/images/help/repository/edit-branch-protection-rule.png) -1. Make your desired changes to the branch protection rule. +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) -### Deleting a branch protection rule +### Borrar una regla de protección de rama {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. To the right of the branch protection rule you want to delete, click **Delete**. ![Botón de borrar](/assets/images/help/repository/delete-branch-protection-rule.png) +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) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 8c7065f9fc..659bf2e7b3 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -21,7 +21,7 @@ versions: {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Lista de alertas del escaneo de secretos](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) {% endif %} -1. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert. +1. Opcionalmente, utiliza el menú desplegable de "Marcar como" y da clic en la razón para resolver una alerta. {% if currentVersion == "free-pro-team@latest" %} ![Menú desplegable para resolver una alerta del escaneo de secretos](/assets/images/help/repository/secret-scanning-resolve-alert.png) {% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md index 43f979a206..97977f03c3 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-branches-in-your-repository.md @@ -1,7 +1,7 @@ --- title: Administrar ramas en tu repositorio intro: 'Cada vez que propones un cambio en Git, [creas una nueva rama](/articles/creating-and-deleting-branches-within-your-repository/). La administración de ramas es una parte importante del flujo de trabajo de Git. Después de algún tiempo, tu lista de ramas puede crecer, por lo que es una buena idea eliminar las ramas fusionadas o antiguas.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-branches-in-your-repository versions: diff --git a/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md b/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md index 1354462222..8fcb65ee89 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-repository-settings.md @@ -1,7 +1,7 @@ --- title: Administrar configuraciones de repositorios intro: 'Los administradores de repositorio y propietarios de organización pueden cambiar la configuración de un repositorio, como el nombre, propietario y visibilidad, o bien, borrar el repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-repository-settings versions: diff --git a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 39ac746272..efe02d3e33 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -13,19 +13,19 @@ versions: --- {% if currentVersion == "free-pro-team@latest" %} -### Enabling or disabling security and analysis features for public repositories +### Habilitar o inhabilitar las características de análisis y seguridad para los repositorios públicos -You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning. +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. {% 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**. !["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) +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) {% endif %} -### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %} +### Habilitar o inhabilitar las características de seguridad y análisis{% if currentVersion == "free-pro-team@latest" %} para los repositorios privados{% endif %} -You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository. If your organization or enterprise has a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %} +Puedes administrar las características de seguridad y de análisis para tu repositorio {% if currentVersion == "free-pro-team@latest" %}privado o interno {% endif %}. Si tu organización o empresa tienen una licencia para {% data variables.product.prodname_GH_advanced_security %}, entonces tendrás opciones adicionales disponibles. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -33,7 +33,7 @@ You can manage the security and analysis features for your {% if currentVersion {% 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**. -{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. +{% if currentVersion == "free-pro-team@latest" %}Si no se muestra "{% data variables.product.prodname_secret_scanning_caps %}", puede que primero necesites habilitar la {% data variables.product.prodname_GH_advanced_security %}. ![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-dotcom-private.png) {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} @@ -67,7 +67,7 @@ Los propietarios de organización y administradores de repositorio solo pueden o {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click +4. Debajo de "Acceso a las alertas", a la derecha de la persona o equipo para el cual quieres eliminar el acceso, da clic en {% octicon "x" aria-label="X symbol" %}. {% if currentVersion == "free-pro-team@latest" %} ![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) @@ -76,7 +76,7 @@ Los propietarios de organización y administradores de repositorio solo pueden o ![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) {% endif %} -### Further reading +### Leer más - [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" - "[Administrar la seguridad y la configuración de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index 8064a2d22d..f8e33deecc 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -48,7 +48,7 @@ Para obtener más información acerca de los niveles de permiso en los repositor {% data reusables.repositories.navigate-to-manage-access %} 4. Debajo de "Administrar acceso", encuentra al equipo o persona de quien quieras eliminar el acceso y da clic{% octicon "trashcan" aria-label="The trashcan icon" %}. ![Icono de papelera para eliminar el acceso](/assets/images/help/repository/manage-access-remove.png) -### Further reading +### Leer más - "[Configurar la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility)" - "[Configurar los permisos básicos para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md b/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md index 8d9b586681..f3d81524ae 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-the-automatic-deletion-of-branches.md @@ -15,6 +15,6 @@ Cualquier persona con permisos de administrador a un repositorio puede habilitar {% 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) -### Further reading +### 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/)" diff --git a/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index c33ec496c3..dae5016e31 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -19,7 +19,7 @@ Un propietario de la organización debe permitir las bifurcaciones de repositori {% 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) -### Further reading +### Leer más - "[Acerca de las bifurcaciones](/articles/about-forks)" - "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md b/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md index 7f32b5541b..5d6d069737 100644 --- a/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md +++ b/translations/es-ES/content/github/administering-a-repository/releasing-projects-on-github.md @@ -1,7 +1,7 @@ --- title: Lanzar proyectos en GitHub intro: 'Puedes crear un lanzamiento para consolidad software, notas de lanzamiento y archivos binarios para que los demás lo descarguen.' -mapTopic: verdadero +mapTopic: true redirect_from: - /categories/85/articles/ - /categories/releases/ diff --git a/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md b/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md index 0748625b6b..d4c7ef4943 100644 --- a/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md @@ -1,21 +1,34 @@ --- -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. +title: Renombrar una rama +intro: Puedes cambiar el nombre de una rama en un repositorio. +permissions: Las personas con permisos de escritura en un repositorio pueden renombrar las ramas de éste. Las personas con permisos administrartivos pueden renombrar la rama predeterminada. versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -### 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](/github/collaborating-with-issues-and-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)". -If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. +Si renombras una rama, {% data variables.product.prodname_dotcom %} redireccionará automáticamente los enlaces en{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} que contengan el nombre anterior de la rama al enlace equivalente en la rama que se renombró. {% data variables.product.prodname_dotcom %} también actualizará las políticas de protección de rama, así como la rama base para las solicitudes de cambios y borradores de lanzamientos. -### Renaming a branch +### Renombrar una rama {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} -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) +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) + +### Updating a local clone after a branch name changes + +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. + +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 +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md index 3e3be4f41c..eb2af746cf 100644 --- a/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md @@ -36,6 +36,6 @@ Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o l {% data reusables.user_settings.restore-repo %} {% data reusables.user_settings.restore-confirmation %} -### Further reading +### Leer más - "[Borrar un repositorio](/articles/deleting-a-repository)" diff --git a/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md b/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md index cf73992a83..d1b3be621c 100644 --- a/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md @@ -1,7 +1,7 @@ --- title: Asegurar tu repositorio intro: 'Asegurar las funciones como {% data variables.product.prodname_secret_scanning %} protegen los datos de tu repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/securing-your-repository versions: diff --git a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md index a45e4b87b1..9215b586b3 100644 --- a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,8 +24,8 @@ Te recomendamos revisar las siguientes consideraciones antes de que cambies la v * 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. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}La visibilidad de cualquier bifurcación también cambiará a privada.{% elsif currentVersion == "github-ae@latest" %}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)"{% if currentVersion == "free-pro-team@latest" %} * 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.{% if currentVersion == "free-pro-team@latest" %} 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 %}{% if currentVersion == "free-pro-team@latest" %} -* {% 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} -* {% 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 has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* {% 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 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 %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* 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 tenga una licencia para la {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * 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 %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -47,10 +47,10 @@ Te recomendamos revisar las siguientes consideraciones antes de que cambies la v #### Convertir un repositorio en público * {% 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)"{% if currentVersion == "free-pro-team@latest" %} -* 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. 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. +* 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 %}. -For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} +Para obtener más información sobre cómo mejorar la seguridad del repositorio, consulta la sección "[Acerca de cómo asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)".{% endif %} {% endif %} @@ -102,5 +102,5 @@ For information about improving repository security, see "[About securing your r {% endif %} -### Further reading +### Leer más - "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md index 5ad3fe0d23..226a4dfd7c 100644 --- a/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md +++ b/translations/es-ES/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -1,6 +1,6 @@ --- title: Solución de problemas para verificaciones de estado requeridas -intro: 'You can check for common errors and resolve issues with required status checks.' +intro: 'Puedes verificar si hay errores comunes y resolver problemas con las verificaciones de estado requeridas.' product: '{% data reusables.gated-features.protected-branches %}' versions: free-pro-team: '*' @@ -8,9 +8,9 @@ versions: github-ae: '*' --- -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. Para obtener más información, consulta las "[Verificaciones](/rest/reference/checks)". +Si tienes una verificación y un estado con el mismo nombre y seleccionas dicho nombre como una verificación de estado requerida, tanto la verificación como el estado se requerirán. Para obtener más información, consulta las "[Verificaciones](/rest/reference/checks)". -After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. Esto garantiza que tu rama ha sido probada con el último código desde la rama base. Si tu rama no está actualizada, necesitarás fusionar la rama base en tu rama. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". +Después de que habilitas la verificación de estado requerida, tu rama podría tener que actualizarse con la rama base antes de que se pueda fusionar. Esto garantiza que tu rama ha sido probada con el último código desde la rama base. Si tu rama no está actualizada, necesitarás fusionar la rama base en tu rama. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". {% note %} @@ -26,13 +26,13 @@ remote: error: Required status check "ci-build" is failing ``` {% note %} -**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. Esto se puede hacer sin las verificaciones de estado ejecutándose en la propia confirmación de fusión. +**Nota:** Las solicitudes de extracción que están actualizadas y aprobaron las verificaciones de estado requeridas pueden fusionarse localmente y subirse a la rama protegida. Esto se puede hacer sin las verificaciones de estado ejecutándose en la propia confirmación de fusión. {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Algunas veces, los resultados de las verificaciones de estado para la confirmación de la prueba de fusión y de la confirmación principal entrarán en conflicto. If the test merge commit has a status, the test merge commit must pass. De otra manera, el estado de la confirmación principal deberá pasar antes de que puedas fusionar la rama. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." +Algunas veces, los resultados de las verificaciones de estado para la confirmación de la prueba de fusión y de la confirmación principal entrarán en conflicto. Si la confirmación de fusión de prueba tiene un estado, ésta pasará. De otra manera, el estado de la confirmación principal deberá pasar antes de que puedas fusionar la rama. Para obtener más información sobre las confirmaciones de fusiones de prueba, consulta la sección "[Extracciones](/rest/reference/pulls#get-a-pull-request)". ![Ramas con conflictos en las confirmaciones de fusión](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md index 5d03aa7724..ad238e8a72 100644 --- a/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/viewing-branches-in-your-repository.md @@ -19,7 +19,7 @@ versions: ![La página de ramas para el repositorio Atom](/assets/images/help/branches/branches-overview-atom.png) -### Further reading +### Leer más - "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" - "[Eliminar ramas no utilizadas](/articles/deleting-unused-branches)" diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md index 55014b4023..b6bc1ec512 100644 --- a/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md @@ -24,5 +24,5 @@ También puedes ver información de implementación en la pestaña "Conversation {% data reusables.repositories.navigate-to-repo %} 2. Arriba de la lista de archivos, haz clic en **Environments (Entornos)**. ![Entornos por encima de la página del repositorio](/assets/images/help/repository/environments.png) -### Further reading +### Leer más - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md b/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md index eb0ac18fd5..b5a689c9a8 100644 --- a/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md +++ b/translations/es-ES/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md @@ -31,6 +31,6 @@ versions: {% data reusables.repositories.releases %} 2. En la parte superior de la página de lanzamiento, haz clic en **Tags** (Etiqueta). ![Página de etiquetas](/assets/images/help/releases/tags-list.png) -### Further reading +### Leer más - "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md b/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md index fd4cd3b4ce..61e09f0468 100644 --- a/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md +++ b/translations/es-ES/content/github/authenticating-to-github/about-anonymized-image-urls.md @@ -87,6 +87,6 @@ Si una imagen está siendo proporcionada desde una red privada o desde un servid Para solucionar esto, mueva la imagen a un servicio que esté disponible públicamente. -### Further reading +### Leer más - "[Imágenes de usuarios de conexiones proxy](https://github.com/blog/1766-proxying-user-images)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 65cf92b98f..24c711537a 100644 --- a/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Acerca de la autenticación con el inicio de sesión único de SAML -intro: 'Puedes acceder a {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}una organización que utilice el inicio de sesión único (SSO) de SAML{% endif %} si te autenticas {% if currentVersion == "github-ae@latest" %}con el inicio de sesión único (SSO) de SAML {% endif %}a través de un proveedor de identidad (IdP).{% if currentVersion == "free-pro-team@latest" %}Para autenticarte con la API o con Git en la línea de comandos cuando una organización requiera el SSO de SAML, debes autorizar tu token de acceso personal o llave de SSH.{% endif %}' +intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on @@ -9,6 +9,8 @@ versions: github-ae: '*' --- +### About authentication with SAML SSO + {% if currentVersion == "github-ae@latest" %} El SSO de SAML permite que un propietario de empresa controle centralmente y asegure el acceso a {% data variables.product.product_name %} desde un IdP de SAML. Cuando visitas {% data variables.product.product_location %} en un buscador, {% data variables.product.product_name %} te redireccionará a tu IdP para autenticarte. Después de que te autenticas exitosamente con una cuenta en el IdP, éste te redirigirá de vuelta a {% data variables.product.product_location %}. {% data variables.product.product_name %} valida la respuesta de tu IdP y luego te otorga el acceso. @@ -31,17 +33,21 @@ Si te has autenticado recientemente con tu SAML IdP de la organización en tu na {% data reusables.saml.you-must-periodically-authenticate %} -Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada. Los tokens de acceso {% data variables.product.prodname_oauth_app %} están autorizados por defecto. +Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada. Si no tienes un token de acceso personal ni una clave SSH, puedes crear un token de acceso personal para la línea de comandos o generar una clave SSH nueva. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" o "[Generar una nueva llave SSH y añadirla al agente de ssh](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". -Para usar un token de acceso personal o una clave SSH nuevos o existentes con una organización que implementa SAML SSO, necesitarás autorizar el token o autorizar la clave SSH para usar con una organización de SAML SSO. Para obtener más información, consulta "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. Para obtener más información, consulta "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -Debes tener una sesión activa de SAML cada que autorices un {% data variables.product.prodname_oauth_app %}. +### About {% data variables.product.prodname_oauth_apps %} and SAML SSO + +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO. + +After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). {% endif %} -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %}- "[Acerca de la administración de identidad y de acceso con el inicio de sesión único de SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% if currentVersion == "github-ae@latest" %}- "[Acerca de la administración de identidad y de acceso para tu empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md index d997b1985e..eaad9cd1ad 100644 --- a/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -24,7 +24,7 @@ Los administradores de repositorios pueden implementar la firma de confirmación Puedes comprobar el estado de verificación de tus confirmaciones o etiquetas firmadas en {% data variables.product.product_name %} y ver por qué las firmas de tu confirmación podrían no ser verificadas. Para obtener más información, consulta "[Comprobar la confirmación y el estado de verificación de firma de la etiqueta](/articles/checking-your-commit-and-tag-signature-verification-status)". {% if currentVersion == "free-pro-team@latest" %} -{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. 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. 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)." +{% 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. Opcionalmente, puedes elegir que {% data variables.product.product_name %} firme las confirmaciones que hagas en {% data variables.product.prodname_codespaces %}. 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. 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)". {% endif %} ### Verificación de firma de confirmación GPG @@ -67,7 +67,7 @@ La verificación de firmas para los bots solo funcionará si la solicitud se ver {% data variables.product.prodname_github_app %} o bot y no contiene información personalizada del autor, del confirmante, ni de la firma, tal como la API de confirmaciones. {% endif %} -### Further reading +### Leer más - "[Firmar confirmaciones](/articles/signing-commits)" - "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md b/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md index 85a4c32a88..493e178006 100644 --- a/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md +++ b/translations/es-ES/content/github/authenticating-to-github/about-githubs-ip-addresses.md @@ -20,6 +20,6 @@ De vez en cuando hacemos cambios en nuestras direcciones IP, y mantendremos esta Para que las aplicaciones funcionen, debes habilitar los puertos TCP 22, 80, 443 y 9418 mediante nuestros rangos de IP para `github.com`. -### Further reading +### Leer más - "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" diff --git a/translations/es-ES/content/github/authenticating-to-github/about-ssh.md b/translations/es-ES/content/github/authenticating-to-github/about-ssh.md index 4b1df46214..b63a6c0c87 100644 --- a/translations/es-ES/content/github/authenticating-to-github/about-ssh.md +++ b/translations/es-ES/content/github/authenticating-to-github/about-ssh.md @@ -22,7 +22,7 @@ Si no has utilizado tu llave SSH por un año, entonces Si eres miembro de una organización que provee certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/articles/about-ssh-certificate-authorities)". -### Further reading +### Leer más - "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)" - "[Probar tu conexión SSH](/articles/testing-your-ssh-connection)" diff --git a/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md b/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md index 36dfb30de7..fdfb35113d 100644 --- a/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md +++ b/translations/es-ES/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md @@ -59,7 +59,7 @@ Si pierdes el acceso a tus credenciales de autenticación de dos factores, puede Si tu autenticación falla varias veces, es posible que desees sincronizar el reloj de tu teléfono con tu proveedor móvil. Frecuentemente, esto involucra la verificación de la opción "Establecer automáticamente" en el reloj de tu teléfono, en lugar de brindar tu propia zona horaria. -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" - [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md index a861181de0..8375dd8c05 100644 --- a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md +++ b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account.md @@ -26,7 +26,7 @@ Al verificar una firma, extraemos la firma e intentamos analizar sus id de llave 5. Haz clic en **Add GPG key** (Agregar llave GPG). ![Botón Add key (Agregar llave)](/assets/images/help/settings/gpg-add-key.png) 6. Para confirmar la acción, escribe tu contraseña de {% data variables.product.product_name %}. -### Further reading +### Leer más * "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" * "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" diff --git a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index 62c6011899..402a76e87d 100644 --- a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -38,7 +38,7 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product {% 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. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) +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) {% data reusables.user_settings.sudo-mode-popup %} @@ -65,7 +65,7 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product {% 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. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) +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) @@ -94,14 +94,14 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product {% 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. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) +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) {% endlinux %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[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)" {% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 2545f3cec4..c089d56e49 100644 --- a/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -42,7 +42,7 @@ Si estás usando una llave GPG que coincida con la identidad de la persona que c ``` 10. Carga la llave GPG al [agregarla a tu cuenta GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). -### Further reading +### Leer más - "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" - "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" diff --git a/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md index 5c4dc30cd9..0bd47232ce 100644 --- a/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md @@ -1,7 +1,7 @@ --- title: Autenticación con inicio de sesión único de SAML intro: 'Puedes autenticarte en {% if currentVersion == "free-pro-team@latest" %} una organización de {% data variables.product.product_name %} {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}con el inicio de sesión único (SSO) de SAML{% if currentVersion == "free-pro-team@latest" %} y ver tus sesiones activas{% endif %}.' -mapTopic: verdadero +mapTopic: true product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ diff --git a/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index 4ab56bd18a..db25cb4348 100644 --- a/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -17,7 +17,7 @@ Puedes autorizar un token de acceso personal existente, o [crear un nuevo token 4. Busca la organización para la que deseas autorizar el token de acceso. 4. Da clic en **Autorizar**. ![Botón para autorizar el token](/assets/images/help/settings/token-authorize-button.png) -### Further reading +### Leer más - "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" - "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md index 86a578eedd..e08b21c156 100644 --- a/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md @@ -22,7 +22,7 @@ Puedes autorizar una clave SSH existente, o crear una nueva clave SSH, y luego a 4. Busca la organización para la que deseas autorizar la clave SSH. 5. Da clic en **Autorizar**. ![Botón para autorizar el token](/assets/images/help/settings/ssh-sso-authorize.png) -### Further reading +### Leer más - "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)" - "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md b/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md index 86db9a7cad..afecf10da6 100644 --- a/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md +++ b/translations/es-ES/content/github/authenticating-to-github/authorizing-oauth-apps.md @@ -78,7 +78,7 @@ Cuando autorizas una {% data variables.product.prodname_oauth_app %} para tu cue Si perteneces a cualquier organizacion que imponga el inicio de sesión único de SAML, debes tener una sesión activa de SAML para cada organización cada vez que autorices un {% data variables.product.prodname_oauth_app %}. -### Further reading +### Leer más - "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" - "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" diff --git a/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md index e8abd26dce..ee98c5b2bc 100644 --- a/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ b/translations/es-ES/content/github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -22,7 +22,7 @@ versions: - Para configurar la autenticación de dos factores mediante una app móvil TOTP, haz clic en **Set up using an app** (Configurar mediante una app). - Para configurar la autenticación de dos factores mediante un mensaje de texto (SMS), haz clic en **Set up using SMS** (Configurar mediante SMS). -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" - [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md index 06fc006ac7..2445b88044 100644 --- a/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md +++ b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md @@ -23,7 +23,7 @@ versions: * Si no hay pares de llaves GPG o no quieres usar algunas de las que están disponibles para las confirmaciones y las etiquetas firmadas, [genera una nueva llave GPG](/articles/generating-a-new-gpg-key). * Si existe un nuevo par de llaves GPG existente y quieres usarlo para firmar confirmaciones y etiquetas, [agrega tu llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). -### Further reading +### Leer más * "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" * "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md index e73976e3ad..1d96d10ff6 100644 --- a/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md +++ b/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md @@ -29,7 +29,7 @@ Si la firma de tu confirmación no está verificada, puedes aprender más sobre 3. Junto a la descripción de tu etiqueta, hay un cuadro que muestra si la firma de la etiqueta está verificada o no está verificada. ![firma de etiqueta verificada](/assets/images/help/commits/gpg-signed-tag-verified.png) 4. Para ver información más detallada sobre la firma de la etiqueta, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). Si la firma de tu etiqueta no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Etiqueta firmada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png) -### Further reading +### Leer más - "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" - "[Firmar confirmaciones](/articles/signing-commits)" diff --git a/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md index 90779406ff..2cca7da81e 100644 --- a/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md @@ -103,7 +103,7 @@ Puedes generar un token de recuperación de cuenta y almacenarlo con un proveedo {% endif %} -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" - [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md index ea04a3e471..6ca80989dc 100644 --- a/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md +++ b/translations/es-ES/content/github/authenticating-to-github/configuring-two-factor-authentication.md @@ -94,7 +94,7 @@ La autenticación con una llave de seguridad es *secundaria* a la autenticación 9. Confirma que has descargado tus códigos de recuperación y puedes acceder a ellos. Si aún no lo has hecho, o si deseas generar otro conjunto de códigos, descarga tus códigos y guárdalos en un lugar seguro. Si pierdes el acceso a tu cuenta, puedes usar tus códigos de recuperación para volver a ingresar a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". ![Botón Download recovery codes (Descargar códigos de recuperación)](/assets/images/help/2fa/2fa-recover-during-setup.png) {% data reusables.two_fa.test_2fa_immediately %} -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" - [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" diff --git a/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md b/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md index 531361da90..8a5df0dc7b 100644 --- a/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md +++ b/translations/es-ES/content/github/authenticating-to-github/connecting-to-github-with-ssh.md @@ -10,7 +10,7 @@ redirect_from: - /articles/generating-ssh-keys/ - /articles/generating-an-ssh-key/ - /articles/connecting-to-github-with-ssh -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md b/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md index 39a5b4ed8c..4c0d1f6bb9 100644 --- a/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md +++ b/translations/es-ES/content/github/authenticating-to-github/countries-where-sms-authentication-is-supported.md @@ -129,6 +129,6 @@ Si tu país no está en la lista, significa que actualmente no podemos entregar
  • Venezuela
    • -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md index b99f7b6557..f72c111cb8 100644 --- a/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -46,6 +46,6 @@ Los tokens de acceso personal solo se pueden usar para operaciones HTTPS Git. Si Si no se te solicita tu nombre de usuario y contraseña, tus credenciales pueden estar almacenadas en la caché de tu computadora. Puedes [actualizar tus credenciales en la keychain](/articles/updating-credentials-from-the-osx-keychain) para reemplazar tu contraseña anterior con el token. -### Further reading +### Leer más - "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md index 6a7da79688..2952eafe84 100644 --- a/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/es-ES/content/github/authenticating-to-github/creating-a-strong-password.md @@ -25,7 +25,7 @@ Solo puedes utilizar tu contraseña para ingresar en {% data variables.product.p {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %} -### Further reading +### Leer más - [Almacenar tus credenciales de {% data variables.product.product_name %} en la caché en Git](/github/using-git/caching-your-github-credentials-in-git/)" - "[Preservar la seguridad de tu cuenta y tus datos](/articles/keeping-your-account-and-data-secure/)" diff --git a/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md b/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md index b86e1cd0d6..9fcae509bd 100644 --- a/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md +++ b/translations/es-ES/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md @@ -26,7 +26,7 @@ Para eliminarte a ti mismo de la organización: {% data reusables.user_settings.security %} 3. Da clic en **Inhabilitar**. ![Botón Inhabilitar autenticación de dos factores](/assets/images/help/2fa/disable-two-factor-authentication.png) -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" - [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md b/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md index a04f3b1d26..ce6e54233a 100644 --- a/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md +++ b/translations/es-ES/content/github/authenticating-to-github/error-bad-file-number.md @@ -49,7 +49,7 @@ Si usar HTTPS no es una opción y tu administrador de firewall no permite las co {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" diff --git a/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md b/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md index 95fb2072c9..92afe20df4 100644 --- a/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md +++ b/translations/es-ES/content/github/authenticating-to-github/error-ssh-add-illegal-option----k.md @@ -26,7 +26,7 @@ Para agregar tu llave privada SSH al ssh-agent, puedes especificar la ruta a la {% endnote %} -### Further reading +### Leer más - "[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) diff --git a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md index aacc4b1e52..c26a0102e5 100644 --- a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md +++ b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-gpg-key.md @@ -53,7 +53,7 @@ versions: 11. Copia tu llave GPG, comenzando con `-----BEGIN PGP PUBLIC KEY BLOCK-----` y terminando con `-----END PGP PUBLIC KEY BLOCK-----`. 12. [Agrega la llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). -### Further reading +### Leer más * "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" * "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" diff --git a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index fe3591f96e..1994600e92 100644 --- a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -149,7 +149,7 @@ Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, deb {% endlinux %} -### Further reading +### Leer más - "[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)" diff --git a/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md b/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md index 89f58138f6..fe9efe4ebd 100644 --- a/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md +++ b/translations/es-ES/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md @@ -1,7 +1,7 @@ --- title: Mantener seguros tu cuenta y tus datos intro: 'Para proteger tu información personal, debes mantener seguros tanto tu {% data variables.product.product_name %} cuenta como cualquier dato asociado.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/keeping-your-account-and-data-secure versions: diff --git a/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md index fca2a09913..96a9b664b6 100644 --- a/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md +++ b/translations/es-ES/content/github/authenticating-to-github/managing-commit-signature-verification.md @@ -5,7 +5,7 @@ redirect_from: - /articles/generating-a-gpg-key/ - /articles/signing-commits-with-gpg/ - /articles/managing-commit-signature-verification -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md index ae459bfb7f..d656a1a6c9 100644 --- a/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -85,7 +85,7 @@ Si te es imposible recuperar el acceso a tu cuenta, genera una contraseña de un {% data variables.contact.contact_support %} para hacerles saber que tu token de recuperación de cuenta está listo para revisión. {% endif %} -### Further reading +### Leer más - "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" - [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" diff --git a/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 61db8e71f4..7525466758 100644 --- a/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/es-ES/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ Este artículo te explica cómo hacer confirmaciones con datos confidenciales in #### Usar el BFG -El [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) es una herramienta construida y mantenida por la comunidad de código abierto. Proporciona una alternativa más rápida y simple que `git filter-branch` para eliminar datos no deseados. Por ejemplo, para eliminar tu archivo con datos confidenciales y dejar intacta tu última confirmación, ejecuta lo siguiente: +El [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) es una herramienta construida y mantenida por la comunidad de código abierto. Proporciona una alternativa más rápida y simple que `git filter-branch` para eliminar datos no deseados. Por ejemplo, para eliminar tu archivo con datos confidenciales y dejar intacta tu última confirmación, ejecuta lo siguiente: ```shell $ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA @@ -46,7 +46,7 @@ Después de que se eliminan los datos sensibles, debes subir forzadamente tus ca $ git push --force ``` -Consulta los documentos de [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) para obtener todas las indicaciones para el uso y la descarga. +Consulta los documentos de [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) para obtener todas las indicaciones para el uso y la descarga. #### Utilizar filter-branch @@ -150,7 +150,7 @@ Existen algunos trucos sencillos para evitar confirmar cosas que no quieres conf - Utiliza `git add --interactive` para revisar por separado y preparar los cambios de cada archivo. - Utiliza `git diff --cached` para revisar los cambios que hayas preparado para la confirmación. Esta es la diferencia exacta que `git commit` generará siempre que no utilices la marca `-a`. -### Further reading +### Leer más - [man page de `git filter-branch`](https://git-scm.com/docs/git-filter-branch) - [Pro Git: Herramientas de Git - Rescribir historial](https://git-scm.com/book/en/Git-Tools-Rewriting-History) diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md index bdefee6d98..69082fba5f 100644 --- a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-applications-oauth.md @@ -14,7 +14,7 @@ versions: {% data reusables.user_settings.access_authorized_oauth_apps %} {% data reusables.user_settings.review-oauth-apps %} -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %} - "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} - "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md index a0260c75dc..8244ad56e0 100644 --- a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-authorized-integrations.md @@ -23,7 +23,7 @@ versions: 3. Haz clic en la pestaña **Authorized {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s autorizadas). ![Pestaña de {% data variables.product.prodname_github_app %}s autorizadas](/assets/images/help/settings/settings-authorized-github-apps-tab.png) 3. Revisa las {% data variables.product.prodname_github_app %}s que tienen acceso a tu cuenta. Para las que no reconozcas o las que estén desactualizadas, haz clic en **Revoke** (Revocar). Para revocar todas las {% data variables.product.prodname_github_app %}s, haz clic en **Revoke all** (Revocar todo). ![Lista de {% data variables.product.prodname_github_app %} autorizadas](/assets/images/help/settings/revoke-github-app.png) -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %} - "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} - "[Revisar tus aplicaciones autorizadas (OAuth)](/articles/reviewing-your-authorized-applications-oauth)" diff --git a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md index a56bfe4dbb..01aa0036e4 100644 --- a/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/es-ES/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -1,6 +1,6 @@ --- -title: Revisar tu registro de seguridad -intro: Puedes revisar el registro de seguridad de tu cuenta de usuario para entender mejor las acciones que has realizado y las que otros han realizado, las cuales te involucran. +title: Reviewing your security log +intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you. miniTocMaxHeadingLevel: 4 redirect_from: - /articles/reviewing-your-security-log @@ -10,249 +10,255 @@ versions: github-ae: '*' --- -### Acceder a tu registro de seguridad +### Accessing your security log -La bitácora de seguridad lista todas las acciones realizadas dentro de los últimos 90 días{% if currentVersion ver_lt "enterprise-server@2.20" %}, hasta 50 de ellas{% endif %}. +The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}. {% data reusables.user_settings.access_settings %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -2. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. ![Pestaña de registro de seguridad](/assets/images/help/settings/audit-log-tab.png) +2. In the user settings sidebar, click **Security log**. + ![Security log tab](/assets/images/help/settings/audit-log-tab.png) {% else %} {% data reusables.user_settings.security %} -3. En "Security history" (Historial de seguridad) se muestra tu registro. ![Registro de seguridad](/assets/images/help/settings/user_security_log.png) -4. Haz clic en la entrada para ver más información acerca del evento. ![Registro de seguridad](/assets/images/help/settings/user_security_history_action.png) +3. Under "Security history," your log is displayed. + ![Security log](/assets/images/help/settings/user_security_log.png) +4. Click on an entry to see more information about the event. + ![Security log](/assets/images/help/settings/user_security_history_action.png) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### Buscar tu registro de seguridad +### Searching your security log {% data reusables.audit_log.audit-log-search %} -#### Búsqueda basada en la acción realizada +#### Search based on the action performed {% else %} -### Entender los eventos en tu registro de seguridad +### Understanding events in your security log {% endif %} -Tus acciones activan los eventos que se listan en tu bitácora de seguridad. Las acciones se agrupan en las siguientes categorías: +The events listed in your security log are triggered by your actions. Actions are grouped into the following categories: -| Nombre de la categoría | Descripción | -| -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| [`account_recovery_token`](#account_recovery_token-category-actions) | Contiene todas las actividades relacionadas con [agregar un token de recuperación](/articles/configuring-two-factor-authentication-recovery-methods). | -| [`billing`](#billing-category-actions) | Contiene todas las actividades relacionadas con tu información de facturación. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)". | -| [`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 aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %} -| [`oauth_access`](#oauth_access-category-actions) | Contiene todas las actividades relacionadas con las [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) que hayas conectado con.{% if currentVersion == "free-pro-team@latest" %} -| [`payment_method`](#payment_method-category-actions) | Contiene todas las actividades relacionadas con el pago de tu suscripción de {% data variables.product.prodname_dotcom %}.{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Contiene todas las actividades relacionadas con tu foto de perfil. | -| [`project`](#project-category-actions) | Contiene todas las actividades relacionadas con los tableros de proyecto. | -| [`public_key`](#public_key-category-actions) | Contiene todas las actividades relacionadas con [tus claves SSH públicas](/articles/adding-a-new-ssh-key-to-your-github-account). | -| [`repo`](#repo-category-actions) | Contiene todas las actividades relacionadas con los repositorios que te pertenecen.{% if currentVersion == "free-pro-team@latest" %} -| [`sponsors`](#sponsors-category-actions) | Contiene todos los eventos relacionados con {% data variables.product.prodname_sponsors %} y los botones de patrocinio (consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" y "[Mostrar el botón de patrocinio en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| [`team`](#team-category-actions) | Contiene todas las actividades relacionadas con los equipos de los cuales formas parte.{% endif %}{% if currentVersion != "github-ae@latest" %} -| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contiene todas las actividades relacionadas con la [autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} -| [`user`](#user-category-actions) | Contiene todas las actividades relacionadas con tu cuenta. | +| Category name | Description +|------------------|-------------------{% if currentVersion == "free-pro-team@latest" %} +| [`account_recovery_token`](#account_recovery_token-category-actions) | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods). +| [`billing`](#billing-category-actions) | Contains all activities related to your billing information. +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)." +| [`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 %} +| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) you've connected with.{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture. +| [`project`](#project-category-actions) | Contains all activities related to project boards. +| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account). +| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} +| [`user`](#user-category-actions) | Contains all activities related to your account. {% if currentVersion == "free-pro-team@latest" %} -### Exportar tu registro de seguridad +### Exporting your security log {% data reusables.audit_log.export-log %} {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Acciones de la bitácora de seguridad +### Security log actions -Un resumen de algunas de las acciones más frecuentes que se registran como eventos en la bitácora de seguridad. +An overview of some of the most common actions that are recorded as events in the security log. {% if currentVersion == "free-pro-team@latest" %} -#### acciones de la categoría `account_recovery_token` +#### `account_recovery_token` category actions -| Acción | Descripción | -| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `confirm (confirmar)` | Se activa cuando almacenas [con éxito un nuevo token con un proveedor de recuperación](/articles/configuring-two-factor-authentication-recovery-methods). | -| `recover (recuperar)` | Se activa cuando canjeas [con éxito un token de recuperación de cuenta](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). | -| `recover_error (error de recuperación)` | Se activa cuando se utiliza un token, pero {% data variables.product.prodname_dotcom %} no está disponible para validarlo. | +| Action | Description +|------------------|------------------- +| `confirm` | Triggered when you successfully [store a new token with a recovery provider](/articles/configuring-two-factor-authentication-recovery-methods). +| `recover` | Triggered when you successfully [redeem an account recovery token](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). +| `recover_error` | Triggered when a token is used but {% data variables.product.prodname_dotcom %} is not able to validate it. -#### acciones de la categoría `billing` +#### `billing` category actions -| Acción | Descripción | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| `change_billing_type (cambiar tipo de facturación)` | Se activa cuando [cambias la manera de pagar](/articles/adding-or-editing-a-payment-method) para {% data variables.product.prodname_dotcom %}. | -| `change_email (cambiar correo electrónico)` | Se activa cuando [cambias tu dirección de correo electrónico](/articles/changing-your-primary-email-address). | +| Action | Description +|------------------|------------------- +| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}. +| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address). #### `codespaces` category actions -| Acción | Descripción | -| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | +| Action | Description +|------------------|------------------- +| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). -#### 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 | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `approve` | 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 %} -#### acciones de la categoría `oauth_access` +#### `oauth_access` category actions -| Acción | Descripción | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create (crear)` | Se activa cuando [otorgas acceso a una {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps). | -| `destroy (destruir)` | Se activa cuando [revocas el acceso de una {% data variables.product.prodname_oauth_app %} a tu cuenta](/articles/reviewing-your-authorized-integrations). | +| Action | Description +|------------------|------------------- +| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps). +| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations). {% if currentVersion == "free-pro-team@latest" %} -#### acciones de la categoría `payment_method` +#### `payment_method` category actions -| Acción | Descripción | -| ------------------ | ------------------------------------------------------------------------------------------------------------- | -| `clear (eliminar)` | Se activa cuando se elimina [un método de pago](/articles/removing-a-payment-method) archivado. | -| `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. | -| `update` | Se activa cuando se actualiza un método de pago existente. | +| Action | Description +|------------------|------------------- +| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed. +| `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` +#### `profile_picture` category actions -| Acción | Descripción | -| -------- | ------------------------------------------------------------------------------------------------------ | -| `update` | Se activa cuando [estableces o actualizas tu foto de perfil](/articles/setting-your-profile-picture/). | +| Action | Description +|------------------|------------------- +| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/). -#### acciones de la categoría `project` +#### `project` category actions -| Acción | Descripción | -| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | -| `access (acceder)` | Se activa cuando se modifica la visibilidad de un tablero de proyecto. | -| `create (crear)` | Se activa cuando se crear un tablero de proyecto. | -| `rename (renombrar)` | Se activa cuando se renombra un tablero de proyecto. | -| `update` | Se activa cuando se actualiza un tablero de proyecto. | -| `eliminar` | Se activa cuando se elimina un tablero de proyecto. | -| `enlace` | Se activa cuando un repositorio se vincula a un tablero de proyecto. | -| `unlink (desvincular)` | Se activa cuando se anula el enlace a un repositorio desde un tablero de proyecto. | -| `update_user_permission` | Se activa cuando se agrega o elimina un colaborador externo a un tablero de proyecto o cuando se cambia su nivel de permiso. | +| Action | Description +|--------------------|--------------------- +| `access` | Triggered when a project board's visibility is changed. +| `create` | Triggered when a project board is created. +| `rename` | Triggered when a project board is renamed. +| `update` | Triggered when a project board is updated. +| `delete` | Triggered when a project board is deleted. +| `link` | Triggered when a repository is linked to a project board. +| `unlink` | Triggered when a repository is unlinked from a project board. +| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed. -#### acciones de la categoría `public_key` +#### `public_key` category actions -| Acción | Descripción | -| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | Se activa cuando [agregas una clave SSH pública a tu {% data variables.product.product_name %} cuenta](/articles/adding-a-new-ssh-key-to-your-github-account). | -| `eliminar` | Se activa cuando [eliminas una clave SSH pública para tu {% data variables.product.product_name %} cuenta](/articles/reviewing-your-ssh-keys). | +| Action | Description +|------------------|------------------- +| `create` | Triggered when you [add a new public SSH key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). +| `delete` | Triggered when you [remove a public SSH key to your {% data variables.product.product_name %} account](/articles/reviewing-your-ssh-keys). -#### acciones de la categoría `repo` +#### `repo` category actions -| Acción | Descripción | -| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `access (acceder)` | Se activa cuando un repositorio que te pertenece se [cambia de "privado" a "público"](/articles/making-a-private-repository-public) (o viceversa). | -| `add_member (agregar miembro)` | Se activa cuando un usuario de {% data variables.product.product_name %} recibe [una invitación para tener acceso de colaboración](/articles/inviting-collaborators-to-a-personal-repository){% else %}[un permiso de acceso para colaborar](/articles/inviting-collaborators-to-a-personal-repository){% endif %} en un repositorio. | -| `add_topic (agregar tema)` | Se activa cuando un propietario del repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a un repositorio. | -| `archived (archivado)` | Se activa cuando un propietario del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} -| `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)` | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository). | -| `destroy (destruir)` | Se activa cuando [se borra un repositorio](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} -| `disable` | Se activa cuando un repositorio se inhabilita (por ejemplo, por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `enable` | Se activa cuando se vuelve a habilitar un repositorio.{% endif %} -| `remove_member (eliminar miembro)` | Se activa cuando se elimina {% data variables.product.product_name %} un usuario [de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository). | -| `remove_topic (eliminar tema)` | Se activa cuando un propietario del repositorio elimina un tema de un repositorio. | -| `rename (renombrar)` | Se activa cuando [se renombra un repositorio](/articles/renaming-a-repository). | -| `transfer` | 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)` | Se activa cuando un administrador del repositorio desarchiva un repositorio. | +| Action | Description +|------------------|------------------- +| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa). +| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% if currentVersion == "free-pro-team@latest" %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository. +| `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. +| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} +| `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). +| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable` | Triggered when a repository is re-enabled.{% endif %} +| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). +| `remove_topic` | Triggered when a repository owner removes a topic from a repository. +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). +| `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 owner unarchives a repository. {% if currentVersion == "free-pro-team@latest" %} -#### acciones de la categoría `sponsors` +#### `sponsors` category actions -| Acción | Descripción | -| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo_funding_link_button_toggle (alternar botón de enlace al financiamiento del repositorio)` | Se activa cuando habilitas o inhabilitas un botón de patrocinador en tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | -| `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 "[Patrocinar a un contribuyente de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de un programador patrocinado (consulta "[Administrar tu patrocinio](/articles/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)` | Desencadenado cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta "[Configuración {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_create (creación de programador patrocinado)` | Desencadenado cuando se crea tu cuenta de {% data variables.product.prodname_sponsors %} (consulta "[Configuración de {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Desencadenado cuando editas el perfil de tu desarrollador patrocinado (consulta "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | -| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)` | Desencadenado cuando emites tu aplicación para {% data variables.product.prodname_sponsors %} para su aprobación (consulta "[Configuración {% data variables.product.prodname_sponsors %} pára tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `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 "[Cambiar tus niveles de patrocinio](/articles/changing-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 "[Contactar a tus patrocinadores](/articles/contacting-your-sponsors)") | -| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)` | Desencadenado cuando se te invita a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta "[Configuración de {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `waitlist_join (incorporación a la lista de espera)` | Desencadenado cuando te unes a la lista de espera para convertirte en un desarrollador patrocinado (consulta "[Configuración de {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| Action | Description +|------------------|------------------- +| `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") +| `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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") +| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/articles/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 user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-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 user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") +| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/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 user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") {% endif %} {% if currentVersion == "free-pro-team@latest" %} -#### acciones de la categoría `successor_invitation` +#### `successor_invitation` category actions -| Acción | Descripción | -| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `accept` | Se activa cuando aceptas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | -| `cancel` | Se activa cuando cancelas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | -| `create (crear)` | Se activa cuando creas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | -| `decline` | Se activa cuando rechazas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | -| `revoke` | Se activa cuando retiras una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") | +| Action | Description +|------------------|------------------- +| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") +| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") +| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") +| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") +| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") {% endif %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -#### 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 a la que perteneces te [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 del que eres miembro. | -| `create (crear)` | Se activa cuando se crea un equipo nuevo en una organización a la que perteneces. | -| `destroy (destruir)` | Se activa cuando un equipo del que eres miembro se elimina de la organización. | -| `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) del que eres miembro. | -| `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 you belong to [adds you to a team](/articles/adding-organization-members-to-a-team). +| `add_repository` | Triggered when a team you are a member of is given control of a repository. +| `create` | Triggered when a new team in an organization you belong to is created. +| `destroy` | Triggered when a team you are a member of is deleted from the organization. +| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of. +| `remove_repository` | Triggered when a repository is no longer under a team's control. {% endif %} {% if currentVersion != "github-ae@latest" %} -#### acciones de la categoría `two_factor_authentication` +#### `two_factor_authentication` category actions -| Acción | Descripción | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `enabled (habilitado)` | Se activa cuando se habilita la [autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa). | -| `disabled (inhabilitado)` | Se activa cuando se inhabilita la autenticación de dos factores. | +| Action | Description +|------------------|------------------- +| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled. +| `disabled` | Triggered when two-factor authentication is disabled. {% endif %} -#### acciones de la categoría `user` +#### `user` category actions -| Acción | Descripción | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email (agregar correo electrónico)` | Triggered when you | -| {% if currentVersion != "github-ae@latest" %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% if currentVersion == "free-pro-team@latest" %} | | -| `codespaces_trusted_repo_access_granted` | Triggered when you \[allow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | -| `codespaces_trusted_repo_access_revoked` | Triggered when you \[disallow the codespaces you create for a repository to access other repositories owned by your user account\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %} -| `create (crear)` | Se activa cuando creas una cuenta de usuario nueva.{% if currentVersion != "github-ae@latest" %} -| `change_password (cambiar contraseña)` | Se activa cuando cambias tu contraseña. | -| `forgot_password (olvidé la contraseña)` | Se activa cuando pides [un restablecimiento de contraseña](/articles/how-can-i-reset-my-password).{% endif %} -| `hide_private_contributions_count (ocultar conteo de contribuciones privadas)` | Se activa cuando [ocultas contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | -| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| Action | Description +|--------------------|--------------------- +| `add_email` | Triggered when you {% if currentVersion != "github-ae@latest" %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% if currentVersion == "free-pro-team@latest" %} +| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. +| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %} +| `create` | Triggered when you create a new user account.{% if currentVersion != "github-ae@latest" %} +| `change_password` | Triggered when you change your password. +| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} +| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). +| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} +| `failed_login` | Triggered when you failed to log in successfully. +| `remove_email` | Triggered when you remove an email address. +| `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} +| `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/articles/reporting-abuse-or-spam).{% endif %} +| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} +| `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %} +#### `user_status` category actions -`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | |{% endif %}| | `failed_login` | Triggered when you failed to log in successfully. | `remove_email` | Triggered when you remove an email address. | `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} | `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/articles/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %} - -#### acciones de la categoría `user_status` - -| Acción | Descripción | -| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `update` | Se activa cuando estableces o cambias el estado en tu perfil. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". | -| `destroy (destruir)` | Se activa cuando eliminas el estado de tu perfil. | +| Action | Description +|--------------------|--------------------- +| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." +| `destroy` | Triggered when you clear the status on your profile. diff --git a/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md b/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md index 90ba94465f..1d81cadf01 100644 --- a/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md +++ b/translations/es-ES/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa.md @@ -5,7 +5,7 @@ redirect_from: - /categories/84/articles/ - /categories/two-factor-authentication-2fa/ - /articles/securing-your-account-with-two-factor-authentication-2fa -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/authenticating-to-github/signing-commits.md b/translations/es-ES/content/github/authenticating-to-github/signing-commits.md index cd3cb76f53..de47354efa 100644 --- a/translations/es-ES/content/github/authenticating-to-github/signing-commits.md +++ b/translations/es-ES/content/github/authenticating-to-github/signing-commits.md @@ -45,7 +45,7 @@ Si tienes múltiples llaves o estás intentando firmar confirmaciones o etiqueta {% data reusables.repositories.review-pr-commits %} 5. Para ver información más detallada acerca de la firma verificada, haz clic en Verified (Verificada). ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) -### Further reading +### Leer más * "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" * "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" diff --git a/translations/es-ES/content/github/authenticating-to-github/signing-tags.md b/translations/es-ES/content/github/authenticating-to-github/signing-tags.md index 4095f71b11..898890f204 100644 --- a/translations/es-ES/content/github/authenticating-to-github/signing-tags.md +++ b/translations/es-ES/content/github/authenticating-to-github/signing-tags.md @@ -23,7 +23,7 @@ versions: # Verifies the signed tag ``` -### Further reading +### Leer más - [Ver las etiquetas de tu repositorio](/articles/viewing-your-repositorys-tags)" - "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" diff --git a/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md b/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md index d9f2bc1905..0805973d0f 100644 --- a/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md +++ b/translations/es-ES/content/github/authenticating-to-github/sudo-mode.md @@ -12,6 +12,6 @@ Después de haber realizado una acción sudo-protegida, únicamente se te solici ![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) -### Further reading +### Leer más - [Comando `sudo` Unix](http://en.wikipedia.org/wiki/Sudo) diff --git a/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md index 9090823edf..25a4f918e4 100644 --- a/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md +++ b/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md @@ -103,7 +103,7 @@ Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. {% endlinux %} -### Further reading +### Leer más - "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" - "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" diff --git a/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md b/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md index 9a86c82a46..1413718434 100644 --- a/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md +++ b/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md @@ -1,6 +1,6 @@ --- -title: Probar tu conexión SSH -intro: 'Después de haber configurado tu clave SSH y haberla agregado a tu {% data variables.product.product_name %} cuenta, puedes probar tu conexión.' +title: Testing your SSH connection +intro: 'After you''ve set up your SSH key and added it to your {% data variables.product.product_name %} account, you can test your connection.' redirect_from: - /articles/testing-your-ssh-connection versions: @@ -9,26 +9,26 @@ versions: github-ae: '*' --- -Antes de probar tu conexión SSH, debes haber hecho lo siguiente: -- [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys) -- [Generado una clave SSH nueva](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -- [Agregado una clave SSH nueva a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) +Before testing your SSH connection, you should have: +- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) +- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) +- [Added a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account) -Cuando pruebes tu conexión, tendrás que autenticar esta acción utilizando tu contraseña, que es la contraseña de clave SSH que ya creaste. Para obtener más información acerca de trabajar con contraseñas de clave SSH, consulta ["Trabajar con contraseñas de clave SSH"](/articles/working-with-ssh-key-passphrases). +When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases). {% data reusables.command_line.open_the_multi_os_terminal %} -2. Ingresa lo siguiente: +2. Enter the following: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} # Attempts to ssh to {% data variables.product.product_name %} ``` - Puedes ver una advertencia como la siguiente: + You may see a warning like this: ```shell - > La autenticidad del host '{% data variables.command_line.codeblock %} (DIRECCIÓN IP)' no se puede establecer. - > La clave de huella digital RSA es SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8. - > ¿Estás seguro de que quieres continuar conectado (sí/no)? + > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established. + > RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8. + > Are you sure you want to continue connecting (yes/no)? ``` 3. Verify that the fingerprint in the message you see matches {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %}'s RSA public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`: @@ -39,16 +39,16 @@ Cuando pruebes tu conexión, tendrás que autenticar esta acción utilizando tu {% linux %} - Puede que veas el siguiente mensaje de error: + You may see this error message: ```shell ... - El agente admitió una falla para registrarse utilizando la clave. - debug1: No hay más métodos de autenticación para probar. - Permiso denegado (publickey). + Agent admitted failure to sign using the key. + debug1: No more authentication methods to try. + Permission denied (publickey). ``` - Se trata de un problema conocido con determinadas distribuciones de Linux. Para obtener más información, consulta ["Error: El agente admitió una falla para registrarse"](/articles/error-agent-admitted-failure-to-sign). + This is a known problem with certain Linux distributions. For more information, see ["Error: Agent admitted failure to sign"](/articles/error-agent-admitted-failure-to-sign). {% endlinux %} -4. Comprueba que el mensaje resultante contenga tu nombre de usuario. Si recibes un mensaje de "permiso denegado", consulta ["Error: Permiso denegado (publickey)"](/articles/error-permission-denied-publickey). +4. Verify that the resulting message contains your username. If you receive a "permission denied" message, see ["Error: Permission denied (publickey)"](/articles/error-permission-denied-publickey). diff --git a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md index 07abe10c7f..cd068f7c7d 100644 --- a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md +++ b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md @@ -4,7 +4,7 @@ intro: 'Puede que debas solucionar problemas imprevistos que surgen cuando se fi redirect_from: - /articles/troubleshooting-gpg/ - /articles/troubleshooting-commit-signature-verification -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md index 4245d367cc..cbc87a91d9 100644 --- a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md +++ b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md @@ -1,7 +1,7 @@ --- title: Solucionar problemas de SSH intro: 'Cuando utilizas SSH para conectarte y autenticarte para {% data variables.product.product_name %}, puede que debas solucionar problemas inesperados que surjan.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/troubleshooting-ssh versions: diff --git a/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md index 4210ea0464..80e20cbf03 100644 --- a/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md +++ b/translations/es-ES/content/github/authenticating-to-github/updating-an-expired-gpg-key.md @@ -13,6 +13,6 @@ Si tu clave está vencida, debes [actualizar el vencimiento](https://www.gnupg.o Si tu clave es inválida y no utilizas otra clave válida de tu conjunto de claves, pero en su lugar generas una llave GPG nueva con un conjunto nuevo de credenciales, tus confirmaciones hechas con la clave revocada o vencida se seguirán mostrando como no verificadas. Asimismo, tus credenciales nuevas no podrán volver a firmar o verificar tus confirmaciones y etiquetas antiguas. -### Further reading +### Leer más - "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" diff --git a/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md index cbf04e1efc..74635332ca 100644 --- a/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md +++ b/translations/es-ES/content/github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key.md @@ -17,6 +17,6 @@ Las confirmaciones y etiquetas pueden contener varias direcciones de correo elec Si debes cambiar la dirección de correo electrónico de la persona que confirma el cambio o del etiquetador, consulta "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address/)". -### Further reading +### Leer más - "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" diff --git a/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md b/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md index 193181c338..78fc86d5a5 100644 --- a/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md +++ b/translations/es-ES/content/github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions.md @@ -19,6 +19,6 @@ versions: {% endnote %} -### Further reading +### Leer más - "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" \ No newline at end of file diff --git a/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index c2e0f2a3e3..1a53ee9c4a 100644 --- a/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -107,6 +107,6 @@ De lo contrario, puedes almacenar tu contraseña en la keychain cuando agregues {% endmac %} -### Further reading +### Leer más - "[Acerca de SSH](/articles/about-ssh)" diff --git a/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md b/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md index 37c7dc72a3..2a6239c257 100644 --- a/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md +++ b/translations/es-ES/content/github/building-a-strong-community/about-community-management-and-moderation.md @@ -23,7 +23,7 @@ Como mantenedor de repositorio, puedes crear tus propios lineamientos para contr Los colaboradores pueden reportar el contenido perjudicial en {% data variables.contact.github_support %} siempre que lo deseen. Si decides incluir el contenido reportado para un repositorio público en tu organización, los colaboradores también pueden reportar los comentarios que presenten comportamiento perjudicial directamente a los mantenedores del mismo. Para encontrar más información, visita la sección "[Gestionar contenido reportado en el repositorio de tu organización](/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository)." -### Further reading +### Leer más - "[Tu Código de Conducta](https://opensource.guide/code-of-conduct/)" de las Guías de Código Abierto - "[Construyendo Comunidades de Bienvenida](https://opensource.guide/building-community/)" de las Guías de Código Abierto diff --git a/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md b/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md index 77a5a10a3f..7e354483b8 100644 --- a/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md +++ b/translations/es-ES/content/github/building-a-strong-community/about-community-profiles-for-public-repositories.md @@ -30,7 +30,7 @@ Si un proyecto no tiene un archivo recomendado, puedes hacer clic en **Proponer* ![Lista de verificación del perfil de comunidad con estándares de comunidad recomendados para colaboradores](/assets/images/help/repository/propose-button-community-profile.png) -### Further reading +### Leer más - "[Agregar un código de conducta a tu proyecto](/articles/adding-a-code-of-conduct-to-your-project)" - "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md b/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md index 30f52ef967..fabca14997 100644 --- a/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md +++ b/translations/es-ES/content/github/building-a-strong-community/about-team-discussions.md @@ -37,7 +37,7 @@ Para apagar las notificaciones para los debates del equipo, puedes cancelar la s Para obtener más información, consulta las secciones{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Suscribirte y desuscribirte de las notificaciones](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" y "[Equipos anidados](/articles/about-teams/#nested-teams)". -### Further reading +### Leer más - "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" - [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-ES/content/github/building-a-strong-community/about-wikis.md b/translations/es-ES/content/github/building-a-strong-community/about-wikis.md index 1d4c9919c2..94bd392957 100644 --- a/translations/es-ES/content/github/building-a-strong-community/about-wikis.md +++ b/translations/es-ES/content/github/building-a-strong-community/about-wikis.md @@ -19,7 +19,7 @@ Con las wikis, puedes escribir contenido como en cualquier otro lado en {% data 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 {% if currentVersion == "github-ae@latest" %}un repositorio interno{% else %}un repositorio público{% endif %}. Para obtener más información, consulta "[Cambiar permisos de acceso para wikis](/articles/changing-access-permissions-for-wikis)". -### Further reading +### Leer más - "[Agregar o eliminar páginas wiki](/articles/adding-or-editing-wiki-pages)" - "[Crear un pie de página o barra lateral para tu wiki](/articles/creating-a-footer-or-sidebar-for-your-wiki)" diff --git a/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md b/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md index 3fb12cb6ba..c6c7dd43dd 100644 --- a/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md +++ b/translations/es-ES/content/github/building-a-strong-community/accessing-a-projects-community-profile.md @@ -12,6 +12,6 @@ versions: {% data reusables.repositories.accessing-repository-graphs %} 3. En la barra lateral izquierda, haz clic en **Community** (Comunidad). ![Comunidad en la barra lateral izquierda](/assets/images/help/graphs/graphs-sidebar-community-tab.png) -### Further reading +### Leer más - [Acerca de los perfiles de la comunidad para repositorios públicos](/articles/about-community-profiles-for-public-repositories)" diff --git a/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md b/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md index cd9dcc08bf..807637ab6c 100644 --- a/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md +++ b/translations/es-ES/content/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project.md @@ -43,7 +43,7 @@ Si el código de conducta que quieres utilizar no se encuentra disponible en las 3. En el campo de nombre, teclea el nombre y la extensión del archivo. ![Nombre de archivo del código de conducta nuevo](/assets/images/help/repository/new-code-of-conduct-file-name.png) - Para que tu código de conducta se muestre como visible en el directorio raíz del repositorio, teclea *CODE_OF_CONDUCT* en el campo de nombre de archivo. - Para que tu código de conducta esté visible en los `docs` del repositorio, teclea *docs/CODE_OF_CONDUCT*. - - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*. + - Para que tu código de conducta esté visible en el directorio `.github` del repositorio, teclea *.github/CODE_OF_CONDUCT*. 4. En el archivo nuevo, agrega tu código de conducta personalizado. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md b/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md index 3eeea5ab00..778672021e 100644 --- a/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/adding-a-license-to-a-repository.md @@ -45,6 +45,6 @@ Las licencias de código abierto permiten que otras personas usen, cambien y dis {% endif %} -### Further reading +### Leer más - "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index e675069e0b..694a80f200 100644 --- a/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ Cuando bloqueas a un usuario, puedes elegir bloquearlo indefinidamente o durante {% tip %} -**Sugerencia:** Si estás bloqueando a un usuario por una conversación encendida, considera [bloquear la conversación](/articles/locking-conversations) de manera que solo los colaboradores puedan comentar. +**Tip:** Si bloqueas a un usuario debido a una conversación fuerte, considera bloquear dicha conversación para que solo puedan comentar los colaboradores. Para obtener más información, consulta "[Bloquear conversaciones](/github/building-a-strong-community/locking-conversations)." {% endtip %} Al momento en que bloqueas a un usuario de tu organización: - El usuario deja de ver los repositorios de la organización - Las asignaciones con estrella y las propuestas del usuario se eliminarán de tus repositorios -- Se borrarán las bifurcaciones del usuario para los repositorios de tu organización - Se borrarán los votos del usuario sobre los comentarios y debates en los repositorios de tu organización - El usuario será eliminado como colaborador en los repositorios de tu organización - Las contribuciones del usuario ya no contarán como tales para ellos en los repositorios de tu organización @@ -56,7 +55,7 @@ En los repositorios de tu organización, los usuarios bloqueados tampoco podrán 7. Si deseas establecer un límite de tiempo para el bloqueo, usa el menú desplegable Block options (Bloquear opciones), y selecciona el período que deseas bloquear al usuario. ![Menú desplegable con las opciones de bloqueo](/assets/images/help/organizations/org-block-options-menu.png) 8. Haz clic en **Block user** (Bloquear usuario). ![Botón Block (Bloquear)](/assets/images/help/organizations/org-block-user-button.png) -### Further reading +### Leer más - "[Ver usuarios que están bloqueados en tu organización](/articles/viewing-users-who-are-blocked-from-your-organization)" - "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" diff --git a/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 303a6612a9..11b3b2d6da 100644 --- a/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/es-ES/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### Acerca de bloquear usuarios -Puedes bloquear a un usuario en los parámetros de tu cuenta o desde el perfil del usuario. {% data variables.product.prodname_dotcom %} no notificará al usuario cuando lo bloquees. Si no deseas contribuir en el mismo proyecto que alguien que has bloqueado, puedes [exhibir una advertencia](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings) en cualquier repositorio con contribuciones previas de un usuario bloqueado. Puede que aún veas la actividad de los usuarios bloqueados en los espacios compartidos y los usuarios bloqueados pueden borrar su contenido existente. +Puedes bloquear a un usuario en los parámetros de tu cuenta o desde el perfil del usuario. {% data variables.product.prodname_dotcom %} no notificará al usuario cuando lo bloquees. Si quieres evitar contribuir en el mismo proyecto que alguien que has bloqueado, puedes elegir que se muestre una advertencia en cualquier repositorio que tenga contribuciones previas de los usuarios que has bloqueado. Para obtener más información, consulta la sección "[Bloquear a un usuario en tus ajustes de cuenta](#blocking-a-user-in-your-account-settings)". Puede que aún veas la actividad de los usuarios bloqueados en los espacios compartidos y los usuarios bloqueados pueden borrar su contenido existente. {% tip %} -**Sugerencia:** Si estás bloqueando a un usuario por una conversación encendida, considera [bloquear la conversación](/articles/locking-conversations) de manera que solo los colaboradores puedan comentar. +**Tip:** Si bloqueas a un usuario debido a una conversación fuerte, considera bloquear dicha conversación para que solo puedan comentar los colaboradores. Para obtener más información, consulta "[Bloquear conversaciones](/github/building-a-strong-community/locking-conversations)." {% endtip %} @@ -22,8 +22,6 @@ Cuando bloqueas a un usuario: - El usuario deja de observar y deja de fijar tus repositorios - El usuario no puede unirse a ninguna organización que te pertenezca - Las asignaciones con estrella y las propuestas del usuario se eliminarán de tus repositorios -- Se borran las bifurcaciones del usuario para tus repositorios -- Borras cualquier bifuracación de los repositorios del usuario - Se borran los votos del usuario en los comentarios o debates de tus repositorios - El usuario será eliminado como colaborador en los repositorios de tu organización - Las contribuciones del usuario ya no contarán como tales para ellos en tus repositorios @@ -69,7 +67,7 @@ Utiliza {% data variables.contact.report_abuse %} para contactarnos si te están {% endnote %} -### Further reading +### Leer más - "[Ver usuarios que has bloqueado de tu cuenta personal](/articles/viewing-users-you-ve-blocked-from-your-personal-account)" - "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" diff --git a/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md b/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md index 8dee388baf..f4901f2059 100644 --- a/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md +++ b/translations/es-ES/content/github/building-a-strong-community/changing-access-permissions-for-wikis.md @@ -14,6 +14,6 @@ versions: {% data reusables.repositories.sidebar-settings %} 3. En Features (Características), quita la marca de selección de **Restrict edits to collaborators only** (Restringir ediciones a colaboradores solamente). ![Edición de restricción de wikis](/assets/images/help/wiki/wiki_restrict_editing.png) -### Further reading +### Leer más - "[Inhabilitar wikis](/articles/disabling-wikis)" diff --git a/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md b/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md index aabfc939eb..22d3e478bf 100644 --- a/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md +++ b/translations/es-ES/content/github/building-a-strong-community/collaborating-with-your-team.md @@ -1,7 +1,7 @@ --- title: Colaborar con tu equipo intro: 'Dentro de una organización, tu equipo puede trabajar en varios proyectos usando los debates de equipo.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/collaborating-with-your-team versions: diff --git a/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md index 79a5977b8a..8fe7d567d0 100644 --- a/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md @@ -73,7 +73,7 @@ Tu archivo de configuración personalizará el selector de plantilla cuando el a {% data reusables.files.propose_new_file %} {% endif %} -### Further reading +### Leer más - "[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)" diff --git a/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md index ebe41bf8ca..774fda544e 100644 --- a/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md @@ -36,7 +36,7 @@ Puedes crear plantillas predeterminadas de solicitud de cambios para tu cuenta d {% data reusables.files.choose_commit_branch %} Las plantillas están disponibles para los colaboradores cuando están fusionadas dentro de la rama predeterminada del repositorio. {% data reusables.files.propose_new_file %} -### Further reading +### Leer más - "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" - "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" diff --git a/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md b/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md index 4c336298b3..989f025ae1 100644 --- a/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md +++ b/translations/es-ES/content/github/building-a-strong-community/creating-a-team-discussion.md @@ -19,7 +19,7 @@ versions: 7. También puedes seleccionar si deseas que tu publicación sea privada o pública usando el menú desplegable.![Menú de parámetros de privacidad de los debates del equipo](/assets/images/help/projects/team-discussions-privacy-menu.png) 8. Da clic en **Comentar**. ![Botón Crear nuevo comentario de los debates del equipo](/assets/images/help/projects/team-discussions-comment-button.png) -### Further reading +### Leer más - "[Acerca de los debates del equipo](/articles/about-team-discussions)" - "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md b/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md index 3179a58402..91694fab5b 100644 --- a/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md +++ b/translations/es-ES/content/github/building-a-strong-community/disabling-wikis.md @@ -16,6 +16,6 @@ Cuando desactivas una wiki, su contenido se oculta pero no se borra. Si eliges h {% data reusables.repositories.sidebar-settings %} 3. En Características, quita la marca de selección de **Wiki**. ![Casilla de verificación para inhabilitar wikis](/assets/images/help/wiki/wiki_enable_disable.png) -### Further reading +### Leer más - "[Cambiar los permisos de acceso para las wikis](/articles/changing-access-permissions-for-wikis)" diff --git a/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md b/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md index 726c01c0a8..7185fe46e1 100644 --- a/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md +++ b/translations/es-ES/content/github/building-a-strong-community/documenting-your-project-with-wikis.md @@ -1,12 +1,12 @@ --- title: Documentar tu proyecto con wikis -intro: 'Puedes usar una wiki para compartir información detallada en forma completa acerca de tu proyecto.' +intro: Puedes usar una wiki para compartir información detallada en forma completa acerca de tu proyecto. redirect_from: - /categories/49/articles/ - /categories/wiki/ - /articles/documenting-your-project-with-wikis product: '{% data reusables.gated-features.wikis %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md b/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md index 0a88ab7ab4..34dd798066 100644 --- a/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md +++ b/translations/es-ES/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md @@ -17,7 +17,7 @@ versions: 7. Da clic en **Editar**. También puedes hacer clic en **Eliminar**. ![Botón Editar debate de equipo](/assets/images/help/projects/edit-team-discussions-button.png) 8. Modifica el título y el comentario del debate de equipo según sea necesario, y haz clic en **Actualizar comentario**. ![Botón Actualizar comentario](/assets/images/help/projects/update-comment-button.png) -### Further reading +### Leer más - "[Acerca de los debates del equipo](/articles/about-team-discussions)" - "[Crear un debate de equipo](/articles/creating-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md index e875b2174f..1e5496f590 100644 --- a/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/es-ES/content/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -17,7 +17,7 @@ Puedes aplicar la etiqueta `good first issue` (primera buena propuesta) a las pr {% data reusables.repositories.select-items-in-issue-or-pr-list %} 4. En la esquina superior derecha, haz clic en **Label** (etiqueta), luego escribe `good first issue` (primera buena propuesta). Haz clic en el nombre de la etiqueta para asociarla con los elementos seleccionados. ![Desplegable de la asignación de los hitos de propuestas](/assets/images/help/issues/issues_applying_labels_dropdown.png) -### Further reading +### Leer más - "[Acerca de las etiquetas](/articles/about-labels)" - "[Buscar repositorios](/articles/searching-for-repositories)" diff --git a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md index bf666fe131..ccc25fcab3 100644 --- a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md +++ b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md @@ -33,7 +33,7 @@ Los propietarios de la organización también pueden bloquear a los usuarios por {% data reusables.community.set-interaction-limit %} ![Opciones de límites de interacción temporarios](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) -### Further reading +### Leer más - "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" - "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" - "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" diff --git a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md index 7993af791d..7fc85c4dcb 100644 --- a/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md @@ -28,7 +28,7 @@ También puedes habilitar los límites de actividad en todos los repositorios qu {% data reusables.community.set-interaction-limit %} ![Opciones de límites de interacción temporarios](/assets/images/help/repository/temporary-interaction-limits-options.png) -### Further reading +### Leer más - "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" - "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" - "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" diff --git a/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md b/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md index 7127bf5952..3f43b670d8 100644 --- a/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md +++ b/translations/es-ES/content/github/building-a-strong-community/locking-conversations.md @@ -25,7 +25,7 @@ Para buscar conversaciones bloqueadas en un repositorio que no está archivado, 4. Lee la información acerca de bloquear conversaciones y haz clic en **Lock conversation on this issue** (Bloquear conversación sobre esta propuesta), **Lock conversation on this pull request** (Bloquear conversación sobre esta solicitud de extracción) o **Lock conversation on this commit** (Bloquear conversación sobre esta confirmación). ![Cuadro de diálogo Confirm lock with a reason (Confirmar bloqueo con motivo)](/assets/images/help/repository/lock-conversation-confirm-with-reason.png) 5. Cuando estés listo para desbloquear la conversación, haz clic en **Unlock conversation** (Desbloquear conversación). ![Enlace Unlock conversation (Anular bloqueo de la conversación)](/assets/images/help/repository/unlock-conversation.png) -### Further reading +### Leer más - "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" - [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md b/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md index 1f837e60f7..f85e1a7504 100644 --- a/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md +++ b/translations/es-ES/content/github/building-a-strong-community/maintaining-your-safety-on-github.md @@ -1,7 +1,7 @@ --- title: Mantener tu seguridad en GitHub intro: 'Para construir un ambiente seguro y positivo para ti y para la comunidad de tu proyecto en {% data variables.product.prodname_dotcom %}, puedes bloquear y desbloquear a los usuarios y reportar el contenido ofensivo.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/encouraging-positive-contributions-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/encouraging-positive-contributions-in-your-organization diff --git a/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md b/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md index 398864630f..e5d86210b0 100644 --- a/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository.md @@ -14,7 +14,7 @@ Puedes habilitar o inhabilitar el contenido para los repositorios públicos que {% data reusables.repositories.sidebar-moderation-reported-content %} 4. Selecciona o desselecciona **Aceptar reportes de contenido de los colaboradores recientes y anteriores** debajo de "Contenido reportado". ![Casilla para optar por ingresar o salir del contenido reportado en un repositorio](/assets/images/help/repository/reported-content-opt-in-checkbox.png) -### Further reading +### Leer más - "[Administrar el contenido reportado en el repositorio de tu organización](/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository)" - "[Moderar comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)" diff --git a/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md b/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md index 954ed77e8f..3b1f921441 100644 --- a/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository.md @@ -39,6 +39,6 @@ Cuando termines de moderar el contenido ofensivo, puedes marcar el reporte como {% data reusables.repositories.reported-content-resolved-tab %} 5. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} a la derecha del reporte que quisieras marcar como no resuelto. Posteriormente, da clic en **Marcar como no resuelto**. !["Marcar como no resuelto" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-mark-report-as-unresolved.png) -### Further reading +### Leer más - "[Acerca de la administración y moderación de la comunidad](/github/building-a-strong-community/about-community-management-and-moderation)" diff --git a/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 74ece73aae..a7fc4ead12 100644 --- a/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/es-ES/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ Puede añadir texto preliminar de YAML a cada plantilla de reporte de problemas Aquí hay un ejemplo de texto preliminar de YAML. -``` +```yaml --- nombre: Problema de rastreo acerca de: Utilice esta plantilla para rastrear nuevas características. @@ -63,7 +63,7 @@ asignados: octocat {% data reusables.files.choose_commit_branch %} Las plantillas están disponibles para los colaboradores cuando están fusionadas dentro de la rama predeterminada del repositorio. {% data reusables.files.propose_new_file %} -### Further reading +### Leer más - "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" - "[Configurar las plantillas de reporte de problemas en su repositorio](/articles/configuring-issue-templates-for-your-repository)" diff --git a/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md b/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md index 730a45585a..6cd7310ed1 100644 --- a/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md +++ b/translations/es-ES/content/github/building-a-strong-community/moderating-comments-and-conversations.md @@ -1,7 +1,7 @@ --- title: Moderar comentarios y conversaciones intro: 'Moderar las conversaciones crea una comunidad amigable para todos los colaboradores de tu proyecto al promover la colaboración saludable y disminuir la intensidad del conflicto. Puedes aplicar el código de conducta de tu comunidad a las discusiones viendo el contenido reportado, editando y eliminando comentarios, y fijando conversaciónes.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/moderating-comments-and-conversations versions: diff --git a/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md b/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md index 8cd3150012..0205891526 100644 --- a/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md +++ b/translations/es-ES/content/github/building-a-strong-community/pinning-a-team-discussion.md @@ -15,7 +15,7 @@ versions: {% data reusables.organizations.team-discussions-tab %} 5. Haz clic en {% octicon "pin" aria-label="The pin icon" %} al lado del debate de equipo que deseas anclar. También puedes desanclar un debate al hacer clic en el ícono. ![Anclar un debate](/assets/images/help/projects/pin-discussion-button.png) -### Further reading +### Leer más - "[Acerca de los debates del equipo](/articles/about-team-discussions)" - "[Crear un debate de equipo](/articles/creating-a-team-discussion)" diff --git a/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md b/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md index 730302da6f..290a1518a7 100644 --- a/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md +++ b/translations/es-ES/content/github/building-a-strong-community/reporting-abuse-or-spam.md @@ -54,7 +54,7 @@ Si se ha habilitado la capacidad para reportar contenido en un repositorio públ 3. En la esquina inferior derecha del selector de plantillas, haz clic en **Report Abuse (Reportar abuso)**. ![Enlace para denunciar un abuso](/assets/images/help/repository/template-chooser-report-abuse.png) 4. Completa el formato de contacto para informar a {% data variables.contact.contact_support %} acerca del comportamiento del enlace, posteriormente, da clic en **Enviar solicitud**. -### Further reading +### Leer más - "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" - [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md b/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md index e8f2c5d5f4..6cbd47bf90 100644 --- a/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md +++ b/translations/es-ES/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md @@ -55,7 +55,7 @@ Si estás confundido, aquí hay algunos buenos ejemplos de pautas de contribuci - Pautas de contribución de Ruby on Rails [](https://github.com/rails/rails/blob/master/CONTRIBUTING.md). - Pautas de contribución de Open Government [](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md). -### Further reading +### Leer más - La sección de las Open Source Guides llamada "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)"{% endif %} diff --git a/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md b/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md index d5c4b04c0e..48a257d0f0 100644 --- a/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md +++ b/translations/es-ES/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions.md @@ -1,10 +1,10 @@ --- title: Configurar tu proyecto para contribuciones saludables -intro: 'Los mantenedores del repositorio pueden configurar pautas de contribuciones para ayudar a los colaboradores a hacer contribuciones significativas y útiles a tu proyecto.' +intro: Los mantenedores del repositorio pueden configurar pautas de contribuciones para ayudar a los colaboradores a hacer contribuciones significativas y útiles a tu proyecto. redirect_from: - /articles/helping-people-contribute-to-your-project/ - /articles/setting-up-your-project-for-healthy-contributions -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md b/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md index ac5016be87..98747dbc1b 100644 --- a/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md +++ b/translations/es-ES/content/github/building-a-strong-community/tracking-changes-in-a-comment.md @@ -27,7 +27,7 @@ Cuando eliminas información confidencial del historial de edición del comentar 3. En el margen superior derecho de la ventana del historial de edición, haz clic en **Options** (Opciones). Luego haz clic en **Delete revision from history** (Eliminar revisión del historial) para eliminar la diferencia que muestra el contenido que se agrega. ![Eliminar detalles de edición de un comentario](/assets/images/help/repository/delete-comment-edit-details.png) 4. Para confirmar la eliminación, haz clic en **OK**. -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %}- "[Reportar abuso o spam](/articles/reporting-abuse-or-spam)"{% endif %} - "[Editar un comentario](/articles/editing-a-comment)" diff --git a/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md index 9fb751c4a9..95380fed45 100644 --- a/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md +++ b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-organization.md @@ -31,7 +31,7 @@ Si seleccionaste una cantidad de tiempo específica para bloquear al usuario, se {% data reusables.organizations.block_users %} 5. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). ![Botón Unblock user (Desbloquear usuario)](/assets/images/help/organizations/org-unblock-user-button.png) -### Further reading +### Leer más - "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" - "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" diff --git a/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md index 002b28ee44..ce397fffd0 100644 --- a/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md +++ b/translations/es-ES/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md @@ -31,7 +31,7 @@ Puedes desbloquear un usuario en los parámetros de tu cuenta o desde la página {% endtip %} -### Further reading +### Leer más - "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" - "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" diff --git a/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md b/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md index 0ef775da89..8d737fdd49 100644 --- a/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests.md @@ -1,7 +1,7 @@ --- title: Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles intro: Los mantenedores del repositorio pueden agregar plantillas en un repositorio para ayudar a los contribuyentes a crear propuestas y solicitudes de extracción de alta calidad. -mapTopic: verdadero +mapTopic: true redirect_from: - /github/building-a-strong-community/using-issue-and-pull-request-templates - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository/ diff --git a/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md b/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md index 268d658492..d004335220 100644 --- a/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md +++ b/translations/es-ES/content/github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization.md @@ -13,7 +13,7 @@ versions: {% data reusables.organizations.block_users %} 5. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que fueron bloqueados de tu organización. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users-for-org.png) -### Further reading +### Leer más - "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" - "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" diff --git a/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md b/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md index a98d600660..0d14db57ae 100644 --- a/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md +++ b/translations/es-ES/content/github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account.md @@ -12,7 +12,7 @@ versions: {% data reusables.user_settings.blocked_users %} 3. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que has bloqueado de tu cuenta. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users.png) -### Further reading +### Leer más - "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" - "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index fabf44b6b0..6467d0511a 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -74,10 +74,10 @@ Cuando una rama está protegida: - Si las verificaciones de estado requeridas están activadas en la rama, no podrás fusionar cambios en la rama hasta que todas las pruebas de integración continua (CI) requeridas estén aprobadas. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/articles/about-status-checks)". - Si las revisiones de solicitud de extracción requeridas están activadas en la rama, no podrás fusionar cambios en la rama hasta que se hayan cumplido todos los requisitos en la política de revisión de solicitud de extracción. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)". - Si la revisión requerida de un propietario del código está activada en una rama y una solicitud de extracción modifica un código que tiene un propietario, un propietario del código debe aprobar la solicitud de extracción antes de que se pueda fusionar. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners)." -- Si la firma de confirmación requerida está activada en una rama, no podrás subir ninguna confirmación de cambios a la rama que no esté firmada ni verificada. 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 currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +- Si la firma de confirmación requerida está activada en una rama, no podrás subir ninguna confirmación de cambios a la rama que no esté firmada ni verificada. Para obtener más información, consulta las secciones "[Acerca de la verificación de firmas de las confirmaciones](/articles/about-commit-signature-verification)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-signed-commits)".{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - Si utilizas el editor de conflictos de {% data variables.product.prodname_dotcom %} para arreglar los conflictos de una solicitud de cambios que creaste desde una rama protegida, {% data variables.product.prodname_dotcom %} te ayuda a crear una rama alternativa para la solicitud de cambios para que tu resolución de conflictos se pueda fusionar. Para obtener más información, consulta la sección "[Resolver un conflicto de fusión en {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)".{% endif %} -### Further reading +### Leer más - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" - "[Rama](/articles/github-glossary/#branch)" en el glosario {% data variables.product.prodname_dotcom %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md index 51096417d9..7efb5c8192 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md @@ -20,7 +20,7 @@ Hay dos tipos principales de modelos de desarrollo con los cuales usar las solic En el *modelo de repositorio compartido*, se le otorga a los colaboradores acceso de escritura a un único repositorio compartido y las ramas de tema son creadas cuando es necesario hacer cambios. Las solicitudes de extracción son útiles en este modelo ya que inician la revisión de código y el debate general acerca de un conjunto de cambios antes de que los mismos sean fusionados en la rama de desarrollo principal. Este modelo es más frecuente con las organizaciones y los equipos pequeños que colaboran en proyectos privados. -### Further reading +### Leer más - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" - "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md index fd9fccb66e..f9db88d27b 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md @@ -61,7 +61,7 @@ Para obtener más información acerca de los comandos de Git para comparar los c - Has excedido el límite total de archivos o de ciertos tipos de archivos. Para obtener más información, consulta "[Límites para ver el contenido y las diferencias en un repositorio](/articles/limits-for-viewing-content-and-diffs-in-a-repository/#diff-limits)". - Tus archivos coinciden con una regla en el archivo *.gitattributes* del repositorio para bloquear ese archivo de mostrarse por defecto. Para obtener más información, consulta "[Personalizar cómo aparecen los archivos modificados en GitHub](/articles/customizing-how-changed-files-appear-on-github)". -### Further reading +### Leer más - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" - "[Acerca de las bifurcaciones](/articles/about-forks)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index aaf28586dc..b89b149857 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -39,7 +39,7 @@ Antes de abrir una propuesta o solicitud de extracción, comprueba si el reposit Al igual que las pautas de contribución, el mantenedor del repositorio puede haber incluido una plantilla para información para incluir en una propuesta o solicitud de extracción. Completar las indicaciones desde la plantilla puede ayudarte a obtener una mejor respuesta de los mantenedores. -### Further reading +### Leer más - "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" - [Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md index 9a73afd63d..2dc1b5d8cc 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-forks.md @@ -26,7 +26,7 @@ En proyectos de código abierto, las bifurcaciones suelen iterar en ideas o camb Si quieres crear un repositorio nuevo desde el contenido de uno existente pero no quieres fusionar tus cambios ascendentemente en ocasiones futuras, puedes duplicar el repositorio o, si éste es una plantilla, utilizarlo como plantilla. Para obtener más información, consulta "[Duplicar un repositorio](/articles/duplicating-a-repository)" y [Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". -### Further reading +### Leer más - "[Acerca de los modelos de desarrollo colaborativo](/articles/about-collaborative-development-models)" - "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md index 0163f87538..495d7e49e8 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-merge-conflicts.md @@ -30,7 +30,7 @@ $ git merge BRANCH-NAME > Automatic merge failed; fix conflicts and then commit the result ``` -### Further reading +### Leer más - "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md index c51034324b..a7ec327bc3 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges.md @@ -49,7 +49,7 @@ Si aún quieres cambiar de base las confirmaciones, pero no puedes cambiar de ba Cualquiera con permisos de escritura en el repositorio, entonces puede [fusionar los cambios](/articles/merging-a-pull-request/) usando el botón Cambiar de base y fusionar en {% data variables.product.product_location %}. -### Further reading +### Leer más - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)" - "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index 1179f16b6b..88d89a689e 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -44,7 +44,7 @@ Puedes ver todas las revisiones que ha recibido una solicitud de extracción en ### Revisiones requeridas -{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." +{% data reusables.pull_requests.required-reviews-for-prs-summary %} Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". {% tip %} @@ -52,7 +52,7 @@ Puedes ver todas las revisiones que ha recibido una solicitud de extracción en {% endtip %} -### Further reading +### Leer más - "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[Ver la revisión de una solicitud de extracción](/articles/viewing-a-pull-request-review)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md index f79f242ed0..8770de96bc 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md @@ -61,7 +61,7 @@ Las páginas de comparación y de solicitudes de cambios utilizan métodos difer - Las páginas de comparación muestran el diff entre la punta de la ref de encabezado y el actual ancestro en común (es decir, la base de fusión) del encabezado y de la ref base. - Las páginas de solicitud de cambios muestran el diff entre la punta de la ref de encabezado y el ancestro común del encabezado y la ref base en el momento en el que la solicitud de cambios se crea. Por consecuencia, la base de fusión que se utilizó para la comparación puede ser diferente. -### Further reading +### Leer más - "[Solicitud de extracción](/articles/github-glossary/#pull-request)" en el glosario de {% data variables.product.prodname_dotcom %} - "[Acerca de las ramas](/articles/about-branches)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md index 8de582657c..0f8b7e4540 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md @@ -1,7 +1,7 @@ --- title: Abordar conflictos de fusión intro: 'Si tus cambios tienen conflictos de fusión con la sucursal de base, debes ocuparte de los conflictos de fusión antes de que puedas fusionarlo con tus cambios de solicitud de extracción.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/addressing-merge-conflicts versions: diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md index dff111a472..e1fae6fb19 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -25,6 +25,6 @@ Puedes establecer permisos de confirmación al crear por primera vez una solicit ![allow-maintainers-to-make-edits-sidebar-checkbox](/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png) -### Further reading +### Leer más - "[Confirmar cambios en una rama de la solicitud de extracción creada desde una bifurcación](/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index 4ab397fb19..268018c96a 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -For more information about required reviews, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." +Para obtener más información sobre las revisiones requeridas, consulta la sección "[Acerca de ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". Puedes comentar una solicitud de extracción, aprobar los cambios o solicitar mejoras antes de aprobarlas. 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)." @@ -32,7 +32,7 @@ Puedes comentar una solicitud de extracción, aprobar los cambios o solicitar me {% data reusables.repositories.request-changes-tips %} -### Further reading +### Leer más - "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[Comentar sobre una solicitud de extracción](/articles/commenting-on-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md index 04eb844336..0ab6c9b8e8 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md @@ -27,7 +27,7 @@ versions: {% endtip %} -### Further reading +### Leer más - "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md index d1ebab6857..2c8cbe2b69 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md @@ -32,6 +32,6 @@ Puedes convertir una solicitud de extracción en borrador en cualquier momento. {% endif %} -### Further reading +### Leer más - "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md index d7bc7b7887..323048d8e4 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md @@ -1,7 +1,7 @@ --- title: Colaborar en repositorios con características de calidad de código intro: 'Las características de la calidad del flujo de trabajo como estados, {% if enterpriseServerVersions contains currentVersion %}ganchos de pre-recepción. {% endif %}ramas protegidas y verificación de estado requerida ayudan a los colaboradores a hacer contribuciones que cumplan con las condiciones establecidas por la organización y los administradores del repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/collaborating-on-repositories-with-code-quality-features-enabled/ - /articles/collaborating-on-repositories-with-code-quality-features diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md index 11c3776093..efe2b3a59f 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md @@ -52,7 +52,7 @@ Cualquier persona que observe la solicitud de extracción o el repositorio recib {% data reusables.pull_requests.resolving-conversations %} -### Further reading +### Leer más - [Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)" {% if currentVersion == "free-pro-team@latest" %}- "[Reportar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md index 4d066ab915..d06f3c585b 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md @@ -3,7 +3,7 @@ title: Crear una solicitud de extracción desde una bifurcación intro: Puedes crear una solicitud de extracción para proponer cambios que has hecho a una bifurcación de un repositorio ascendente. redirect_from: - /articles/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: Cualquiera con permisos de escritura en un repositorio puede crear una solicitud de extracción desde una bifurcación propiedad de un usuario. versions: free-pro-team: '*' enterprise-server: '*' @@ -27,7 +27,7 @@ También puedes otorgar permiso a los mantenedores del repositorio ascendente pa {% data reusables.repositories.asking-for-review %} -### Further reading +### Leer más - "[Trabajar con bifurcaciones](/articles/working-with-forks)" - "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md index 2ba418027f..f2804d3c9f 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md @@ -73,7 +73,7 @@ Una vez que tu solicitud de extracción ha sido revisada, esta se puede [fusiona -### Further reading +### Leer más - "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" - "[Cambiar la rama base de una solicitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index a2e1152248..41971dcfc3 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -39,7 +39,7 @@ Si la rama que quieres borrar está asociada con una solicitud de cambios abiert {% endif %} Para obtener más información, consulta "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)." -### Further reading +### Leer más - "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches)" - "[Ver las ramas en tu repositorio](/github/administering-a-repository/viewing-branches-in-your-repository)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index d141027823..a8d575fb47 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: Descartar una revisión de una solicitud de extracción -intro: 'If your repository requires reviews, you can dismiss pull request reviews that are no longer valid or are unable to be approved by the reviewer.' +intro: 'Si tu repositorio requiere revisiones, puedes descartar las revisiones de solicitudes de cambios que ya no son válidas o que el revisor no puede aprobar.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -20,7 +20,7 @@ Esto cambia el estado de la revisión, que pasa a ser un comentario de revisión 4. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego haz clic en **Descartar revisión**. ![Icono de kebab en el cuadro de fusión](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review.png) 5. Escribe la razón por la que descartas la revisión y luego haz clic en **Descartar revisión**. ![Botón Dismiss review (Descartar revisión)](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review-button.png) -### Further reading +### Leer más - "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" - "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md index 81aac64362..1b66fb4dda 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md @@ -24,7 +24,7 @@ Puedes filtrar archivos en una solicitud de cambios por tipo de extensión, tal 4. Usa el menú desplegable para Filtrar archivos y selecciona, elimina la marca de selección o haz clic en los filtros deseados. ![Opción Filtrar archivos sobre la diferencia de la solicitud de extracción](/assets/images/help/pull_requests/file-filter-option.png) 5. Para borrar la selección de filtro en la pestaña **Archivos modificados** puedes hacer clic en **Borrar**. ![Borrar selección de filtro de archivo](/assets/images/help/pull_requests/clear-file-filter.png) -### Further reading +### Leer más - "[Acerca de la comparación de las ramas en una solicitud de extracción](/articles/about-comparing-branches-in-pull-requests)" - "[Encontrar métodos y funciones modificados en una solicitud de extracción](/articles/finding-changed-methods-and-functions-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md index 6a625144b6..ee9f45d3ea 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md @@ -32,7 +32,7 @@ La lista resumida de métodos y funciones se crea a partir de estos tipos de arc 6. Serás redireccionado a la primera línea de la función o el método seleccionado. ![ver la función o el método en los archivos modificados](/assets/images/help/pull_requests/view-selected-function-or-method.png) -### Further reading +### Leer más - "[Acerca de la comparación de las ramas en una solicitud de extracción](/articles/about-comparing-branches-in-pull-requests)" - "[Filtrar archivos en una solicitud de extracción por tipo de archivo](/articles/filtering-files-in-a-pull-request-by-file-type)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index ed9a9a03e8..bebb32a9e9 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -20,6 +20,6 @@ versions: 5. [Fusiona la solicitud de extracción](/articles/merging-a-pull-request) una vez que la rama esté lista para ser fusionada. 6. [Organiza](/articles/deleting-unused-branches) tus ramas utilizando el botón de eliminación de la solicitud de extracción o en la página de ramas. -### Further reading +### Leer más - La guía ilustrada para "[Comprender el flujo de GitHub](https://guides.github.com/introduction/flow/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md index 9eb540945b..5407ff7a45 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md @@ -1,7 +1,7 @@ --- title: Incorporar modificaciones desde una solicitud de extracción intro: 'Puedes proponer modificaciones para tu trabajo en {% data variables.product.product_name %} a través de solicitudes de extracción. Aprende a crear, administrar y fusionar solicitudes de extracción.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/incorporating-changes-from-a-pull-request versions: diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md index fe1add0ff4..7c5ed9905e 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request.md @@ -33,7 +33,7 @@ Cada una de las personas que sugirieron alguna de las modificaciones incluidas e Si alguna persona sugiere cambios para tu solicitud de extracción, y los cambios están fuera del alcance de la solicitud de extracción, puedes abrir una propuesta nueva para hacer el seguimiento de los comentarios. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". -### Further reading +### Leer más - "[Acerca de las revisiones de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" - "[Revisar los cambios propuestos en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index bb802f0070..e2e3d7aeca 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -12,7 +12,7 @@ versions: ### Acerca de las fusiones de las solicitudes de extracción -En una solicitud de extracción, propones que los cambios que hayas hecho en una rama de encabezado se fusionen en una rama base. Por defecto, cualquier solicitud de extracción se puede fusionar en cualquier momento, a menos que la rama de encabezado esté en conflicto con la rama base. However, there may be restrictions on when you can merge a pull request into a specific branch. Por ejemplo, puede que solo puedas fusionar una solicitud de extracción en la rama predeterminada si están pasando las verificaciones de estado requeridas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". +En una solicitud de extracción, propones que los cambios que hayas hecho en una rama de encabezado se fusionen en una rama base. Por defecto, cualquier solicitud de extracción se puede fusionar en cualquier momento, a menos que la rama de encabezado esté en conflicto con la rama base. Sin embargo, puede que existan restricciones sobre cuándo puedes fusionar una solicitud de cambios en una rama específica. Por ejemplo, puede que solo puedas fusionar una solicitud de extracción en la rama predeterminada si están pasando las verificaciones de estado requeridas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". {% data reusables.pull_requests.you-can-auto-merge %} @@ -69,7 +69,7 @@ Las solicitudes de extracción se fusionan utilizando [la opción `--no-ff`](htt {% data reusables.pull_requests.close-issues-using-keywords %} -### Further reading +### Leer más - "[Revertir una solicitud de extracción](/articles/reverting-a-pull-request)" - "[Sincronizar tu rama](/desktop/guides/contributing-to-projects/syncing-your-branch/)" utilizando {% data variables.product.prodname_desktop %} diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md index 76b5468bed..016c413474 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/overview.md @@ -1,7 +1,7 @@ --- title: Resumen intro: 'Aprende sobre el flujo de {% data variables.product.prodname_dotcom %} y las formas diferentes para debatir y colaborar en tus proyectos.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md index 67fa5e0159..f50cf251e7 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md @@ -1,7 +1,7 @@ --- title: Proponer cambios a tu trabajo con solicitudes de extracción intro: 'Después de agregar cambios a una rama de tema o bifurcación, puedes abrir una solicitud de extracción para pedirle a tus colaboradores o al administrador del repositorio que revisen tus cambios antes de fusionarlos con el proyecto.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/proposing-changes-to-your-work-with-pull-requests versions: diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index 40e6b282ae..2893aa9fc8 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -29,6 +29,6 @@ Puedes solicitar una revisión de una persona sugerida o de una persona específ 6. De manera opcional, si conoces el nombre de la persona o el equipo del que quieres una revisión, haz clic en **Reviewers** (Revisores), luego escribe el nombre de usuario de la persona o el nombre del equipo al que le solicitarás que revise tus cambios. Haz clic en su nombre de equipo o nombre de usuario para solicitar una revisión. ![Campo para ingresar el nombre de usuario de un revisor y desplegable con el nombre del revisor](/assets/images/help/pull_requests/choose-pull-request-reviewer.png) 7. Después de que la solicitud de extracción esté revisada y de que hayas hecho los cambios necesarios, le puedes pedir a un revisor que vuelva a revisar tu solicitud de extracción. Navega hasta **Reviewers** (Revisores) en la barra lateral derecha y haz clic en {% octicon "sync" aria-label="The sync icon" %} al lado del nombre del revisor del que quieres la revisión. ![Icono Re-review sync (Sincronización de volver a revisar) en la barra lateral derecha](/assets/images/help/pull_requests/request-re-review.png) -### Further reading +### Leer más - "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md index d6be465eaa..7db96ab6db 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md @@ -56,6 +56,6 @@ Si un administrador de sitio inhabilita el editor de conflicto de fusión para l {% endif %} 1. Para fusionar tu solicitud de extracción, haz clic en **Merge pull request** (Fusionar solicitud de extracción). Para obtener más información acerca de otras opciones de fusión de solicitudes de extracción, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request/)". -### Further reading +### Leer más - "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index f1eb0ff4be..b6282dfa6e 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ Por ejemplo, si usted y otra persona editaron el archivo _styleguide.md_ en las 4. Abre tu editor de texto preferido, como [Atom](https://atom.io/), y navega hasta el archivo que tiene los conflictos de fusión. 5. Para ver el origen de un conflicto de fusión en tu archivo, busca el archivo para el marcador de conflicto `<<<<<<<`. Cuando abras el archivo en tu editor de texto, verás los cambios desde la rama HEAD (encabezado) o base después de la línea `<<<<<<< HEAD`. Luego verás `=======`, que separa tus cambios de los cambios en la otra rama, seguido de `>>>>>>> BRANCH-NAME`. En este ejemplo, una persona escribió "abrir una propuesta" en la rama base o HEAD (encabezado), y otra persona escribió "haz tu pregunta en IRC" en la rama de comparación o `branch-a`. - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}En este ejemplo, ambos cambios se incorporaron en la fusión final: ```shell @@ -119,7 +119,7 @@ Por ejemplo, si editaste un archivo, como *README.md*, y otra persona eliminó e Ahora puedes fusionar las ramas en la línea de comando o [subir tus cambios a tu repositorio remoto](/articles/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [fusionar tus cambios](/articles/merging-a-pull-request/) en una solicitud de extracción. -### Further reading +### Leer más - "[Acerca de los conflictos de fusión](/articles/about-merge-conflicts)" - "[Revisar las solicitudes de extracción de forma local](/articles/checking-out-pull-requests-locally/)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md index 91ab4b46fc..c872d5bc37 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md @@ -4,7 +4,7 @@ redirect_from: - /articles/reviewing-and-discussing-changes-in-pull-requests/ - /articles/reviewing-changes-in-pull-requests intro: 'Después de haber abierto una solicitud de extracción, puedes revisar y opinar sobre el conjunto de cambios propuestos.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index ec61619aeb..f0b43583b1 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ La revisión de dependencias es compatible con los mismos lenguajes de programac ![El menú de filtro de archivo](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. +1. A la derecha del encabezado de un archivo de bloqueo o de manifiesto, muestra la revisión de dependencias dando clic en el botón de diff enriquecido **{% octicon "file" aria-label="The rich diff icon" %}**. ![El botón de diff rica](/assets/images/help/pull_requests/dependency-review-rich-diff.png) diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index b7cc034a47..af685b02d8 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ Si la solicitud de cambios contiene cambios para las dependencias, puedes utiliz {% data reusables.repositories.changed-files %} -1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. +1. A la derecha del encabezado de un archivo de bloqueo o de manifiesto, muestra la revisión de dependencias dando clic en el botón de diff enriquecido **{% octicon "file" aria-label="The rich diff icon" %}**. ![El botón de diff rica](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -65,7 +65,7 @@ Después de que hayas terminado de revisar todos los archivos que quieras de la {% data reusables.repositories.request-changes-tips %} -### Further reading +### Leer más - "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" - "[Filtrar solicitudes de extracción por estado de revisión](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md index 00e2c343fd..fb4a64eaa4 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review.md @@ -17,7 +17,7 @@ Cuando ves una revisión completa, verás la misma versión de la solicitud de e {% data reusables.repositories.choose-pr-review %} 3. En la pestaña "Conversation" (Conversación), desplázate hasta la revisión que deseas ver y luego haz clic en **View changes (Ver cambios)**. ![Encabezado de revisión con el vínculo de revisión completa](/assets/images/help/pull_requests/view-full-review-view-changes.png) -### Further reading +### Leer más - "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" - "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index c84b288684..d10629d9f7 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -72,7 +72,7 @@ Si cambias la visibilidad de un repositorio interno y luego lo borras, las bifur {% endif %} -### Further reading +### Leer más - "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)" - "[Acerca de las bifurcaciones](/articles/about-forks)" diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md index 8eae498f19..2e8692cbfd 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md @@ -1,7 +1,7 @@ --- title: Trabajar con bifurcaciones intro: 'Las bifurcaciones se suelen usar en desarrollo de código abierto en {% data variables.product.product_name %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/working-with-forks versions: diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 02b1c7292a..f07e83a521 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ Los ganchos de pre-recepción ejecutan pruebas en código que se suben a un repo Si no se acepta tu subida, verás un mensaje de error que corresponde al gancho de pre-recepción fallido. -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md index ea6a7051eb..9d450079c4 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/about-commits.md @@ -21,5 +21,5 @@ También puedes crear una confirmación en nombre de una organización. Para obt El rebase te permite cambiar varias confirmaciones y puede modificar el órden de éstas en tu línea de tiempo. Para obtener más información, consulta la sección [Accerca del rebase de Git](/github/using-git/about-git-rebase)". -### Further reading +### Leer más - "[Confirmar y revisar los cambios a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)" en {% data variables.product.prodname_desktop %} diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md b/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md index 0d44701a5a..653041b6fa 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/changing-a-commit-message.md @@ -116,6 +116,6 @@ Si incluiste información sensible en un mensaje de confirmación, el subir dich {% endwarning %} -### Further reading +### Leer más * "[Firmar confirmaciones](/articles/signing-commits)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md b/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md index e815b57862..02fe98d82f 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/commit-branch-and-tag-labels.md @@ -17,7 +17,7 @@ Una vez que la confirmación está en la rama por defecto, todas las etiquetas q ![Commit-main-label](/assets/images/help/commits/Commit-master-label.png) -### Further reading +### Leer más * "[Firmar confirmaciones](/articles/signing-commits)" * "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md index fd4177faf3..da8e627031 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone.md @@ -72,7 +72,7 @@ $ git fetch upstream recover-B Evita los empujes forzados a un repositorio a menos que sea absolutamente necesario. Esto es especialmente cierto si más de una persona puede subir al repositorio. -### Further reading +### Leer más - ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) - ["Recuperación de datos" sde el libro _Pro Git_](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md index 288f224f37..a2e210dc62 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/comparing-commits.md @@ -59,6 +59,6 @@ Puedes usar esta notación para comparar una sola confirmación o rama con sus p Aquí hay un ejemplo de una [comparación usando la notación `^`](https://github.com/octocat/linguist/compare/octocat:96d29b7%5E%5E%5E%5E%5E...octocat:96d29b7). -### Further reading +### Leer más - "[Cambiar la rama base de una solicitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 9ad4f60f0e..048846c97c 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -34,7 +34,7 @@ Las organizaciones pueden usar el correo electrónico `name@organization.com` co ``` {% tip %} - **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 `on-behalf-of:` commit trailer. + **Tip:** Si utilizas un editor de texto en la línea de comandos para teclear tu mensaje de confirmación, asegúrate de que existen dos líneas nuevas entre el final de la descripción de tu confirmación y el indicador `on-behalf-of:`. {% endtip %} @@ -62,7 +62,7 @@ Una vez que hayas realizado los cambios en un archivo usando el editor web en {% La confirmación, el mensaje y el distintivo nuevos aparecerán en {% data variables.product.product_location %}. -### Further reading +### Lecturas adicionales - "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" - "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index 8ca96eb4fd..630367676d 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -77,7 +77,7 @@ Una vez que hayas realizado los cambios en un archivo usando el editor web en {% La confirmación y el mensaje nuevos aparecerán en {% data variables.product.product_location %}. -### Further reading +### Leer más {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} - "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" - "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md index 744b380843..bf6e7dfbf2 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/creating-and-editing-commits.md @@ -1,7 +1,7 @@ --- title: Crear y editar confirmaciones de cambios intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/creating-and-editing-commits versions: diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md b/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md index f17cb5f0d6..e4668307d7 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/differences-between-commit-views.md @@ -23,7 +23,7 @@ Ws posible que esta vista truncada no contenga la información que estás buscan Para obtener más información acerca de cómo Git considera el historial de confirmaciones, consulta la sección [ "Simplificación del historial"](https://git-scm.com/docs/git-log#_history_simplification) del artículo de ayuda de `git log`. -### Further reading +### Leer más - "[Firmar confirmaciones](/articles/signing-commits)" - "[Buscar confirmaciones](/articles/searching-commits)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md index 8d57b5b5f3..fb51d9aae5 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits.md @@ -1,7 +1,7 @@ --- title: Confirmaciones de solución de problemas intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/troubleshooting-commits versions: diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md b/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md index 035327d3b6..913a35b3b7 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits.md @@ -1,7 +1,7 @@ --- title: Ver y comparar confirmaciones de cambios intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/viewing-and-comparing-commits versions: diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md index c0e0a16849..be85318370 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md @@ -49,6 +49,6 @@ Si tu configuración de Git local contiene una dirección de correo electrónico {% endwarning %} -### Further reading +### Leer más * "[Buscar confirmaciones](/articles/searching-commits)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md index 6e58ee62b3..364591b7e7 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md @@ -25,5 +25,5 @@ Cuando se archiva un repositorio, sus propuestas, solicitudes de cambios, còdig Puedes buscar repositorios archivados. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". -### Further reading +### Leer más - "[Archivar repositorios](/articles/archiving-repositories)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 9ffd1f018e..30c3845e18 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -88,7 +88,7 @@ Hay algunas reglas de sintaxis para los archivos de gitignore que no funcionan c -### Further reading +### Leer más - "[Crear archivos nuevos](/articles/creating-new-files)" - "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md index 73daa4f699..a94fdf1057 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md @@ -48,7 +48,7 @@ Muchos proyectos usan un índice al comienzo de un archivo README para dirigir a {% data reusables.repositories.relative-links %} -### Further reading +### Leer más - "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)" - 18F's "[Hacer que los archivos README sean de lectura](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index ac853accb2..c3f10b7d17 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,14 +23,14 @@ Cada persona y organización puede tener repositorios ilimitados e invitar a un {% endif %} Puedes utilizar repositorios para administrar tu trabajo y colaborar con otros. -- Puedes utilizar propuestas para recolectar la retroalimentación de los usuarios, reportar errores de software y organizar las tareas que te gustaría realizar. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- Puedes utilizar propuestas para recolectar la retroalimentación de los usuarios, reportar errores de software y organizar las tareas que te gustaría realizar. Para obtener más información, consulta la sección "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)".{% if currentVersion == "free-pro-team@latest" %} - {% data reusables.discussions.you-can-use-discussions %}{% endif %} - Puedes utilizar las solicitudes de cambios para proponer cambios a un repositorio. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." - Puedes utilizar tableros de proyecto para organizar y priorizar tus propuestas y solicitudes de cambios. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/github/managing-your-work-on-github/about-project-boards)." {% data reusables.repositories.repo-size-limit %} -### Further reading +### Leer más - "[Crear un repositorio nuevo](/articles/creating-a-new-repository)" - "[Colaborar con propuestas y solicitudes de extracción](/categories/collaborating-with-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md index f6dc95dac0..4f24825e89 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md @@ -5,7 +5,7 @@ redirect_from: - /articles/can-i-archive-a-repository/ - /articles/archiving-a-github-repository - /enterprise/admin/user-management/archiving-and-unarchiving-repositories -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md index e0e24e60e3..ce230fbd7a 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/archiving-repositories.md @@ -18,5 +18,5 @@ versions: 5. Escribe el nombre del repositorio que deseas archivar o desarchivar. ![Advertencias para archivar el repositorio](/assets/images/help/repository/archive-repository-warnings.png) 6. Haz clic en **I understand the consequences, archive this repository** (Comprendo las consecuencias, archivar este repositorio). -### Further reading +### Leer más - [Acerca de Archivar repositorios](/articles/about-archiving-repositories)" diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index 08417babd7..9045bb7214 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -28,7 +28,7 @@ Cuando clonas un repositorio o wiki, solo se descargan los datos Git, como archi - [Hitos](/rest/reference/issues#list-milestones) - [Etiquetas](/rest/reference/issues#list-labels-for-a-repository) - [Observadores](/rest/reference/activity#list-watchers) -- [Stargazers](/rest/reference/activity#list-stargazers) +- [Fans](/rest/reference/activity#list-stargazers) - [Proyectos](/rest/reference/projects#list-repository-projects) {% endif %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md index 4ab68eb51e..91390baaae 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md @@ -1,7 +1,7 @@ --- title: Clonar un repositorio desde GitHub intro: 'Puedes clonar un repositorio remoto desde tu máquina local. Si encuentras errores, existen algunas soluciones de problemas comunes.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/cloning-a-repository-from-github versions: diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md index 13f2793d0f..ef88a3abec 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md @@ -68,7 +68,7 @@ Si no puedes clonar un repositorio, revisa que: {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" {% endif %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md index 62692b18bc..f72a7abb67 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md @@ -45,7 +45,7 @@ versions: 9. En la parte inferior de la página de Configuración rápida resultante, en "Importar el código del repositorio anterior", puedes elegir importar un proyecto en tu nuevo repositorio. Para hacerlo, haz clic en **Importar código**. {% endif %} -### Further reading +### Leer más - [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)" - [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md index 4992a55177..01f6d6184d 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md @@ -1,7 +1,7 @@ --- title: Crear un repositorio en GitHub intro: 'Luego de crear tu repositorio en {% data variables.product.product_name %}, puedes personalizar sus parámetros y su contenido.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/creating-a-repository-on-github versions: diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 4ffed65bbd..d48649a460 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -88,7 +88,7 @@ El selector de licencias solo está disponible cuando creas un proyecto nuevo en El objetivo de los esfuerzos de generación de licencias de código abierto de GitHub es proporcionar un punto de partida para ayudarte a hacer una elección informada. GitHub muestra información de licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados y que cometemos errores como todo el mundo. Por ese motivo, GitHub proporciona la información sobre una base hipotética de "cómo es" y no da garantías al respecto de ninguna información o licencia proporcionada en función o a través de esta. Tampoco se hace responsable de los daños que surjan por el uso de la información de la licencia. Si tienes alguna pregunta al respecto de la licencia correcta para tu código o cualquier otro problema legal relacionado con esto, siempre es mejor consultar con un profesional. -### Further reading +### Leer más - La sección de las Open Source Guides llamada "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md index 8eb1d3a125..b627afcb21 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,13 +19,13 @@ Puedes descubrir, buscar e instalar apps y acciones que otros hayan creado en {% {% data reusables.actions.actions-not-verified %} -Cualquiera puede listar una {% data variables.product.prodname_github_app %} o {% data variables.product.prodname_oauth_app %} gratuita en {% data variables.product.prodname_marketplace %}. {% data variables.product.company_short %} verifica a aquellos que publican apps de pago, y los listados de dichas apps se muestran con una insignia de creador verificado {% octicon "verified" aria-label="Verified creator badge" %}. También podrás ver insignias para las apps verificadas y sin verificar. Estas apps se publicaron utilizando el método anterior para verificar apps individuales. Para obtener más información acerca del proceso actual, consulta las secciones "[Acerca de los creadores verificados](/developers/github-marketplace/about-verified-creators)" y "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)". +Cualquiera puede listar una {% data variables.product.prodname_github_app %} o {% data variables.product.prodname_oauth_app %} gratuita en {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. También podrás ver insignias para las apps verificadas y sin verificar. Estas apps se publicaron utilizando el método anterior para verificar apps individuales. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Crear y hacer aparecer una herramienta en {% data variables.product.prodname_marketplace %} Para obtener más información acerca de cómo crear tu propia herramienta para que se liste en {% data variables.product.prodname_marketplace %}, consulta las secciones de "[Aplicaciones](/developers/apps)" y "[{% data variables.product.prodname_actions %}](/actions)". -### Further reading +### Leer más - "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" - "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md index e446564cd0..a6146f3952 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations.md @@ -1,7 +1,9 @@ --- title: Explorar integraciones -intro: "Puedes personalizar y ampliar tu flujo de trabajo de {% data variables.product.product_name %} con herramientas y\n servicios diseñados por la comunidad de {% data variables.product.product_name %}." -mapTopic: verdadero +intro: |- + Puedes personalizar y ampliar tu flujo de trabajo de {% data variables.product.product_name %} con herramientas y + servicios diseñados por la comunidad de {% data variables.product.product_name %}. +mapTopic: true redirect_from: - /articles/exploring-integrations versions: diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md index 072ef1cec3..8873be767d 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-organization.md @@ -41,7 +41,7 @@ Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de factura {% data reusables.marketplace.complete-order-begin-installation %} 8. Revisa la información acerca del acceso de la app a tu cuenta personal, a tus organizaciones y a los datos, luego haz clic en **Authorize application** (Autorizar aplicación). -### Further reading +### Leer más - "[Actualizar el método de pago de tu organización](/articles/updating-your-organization-s-payment-method)" - "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)" diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md index d3c0b92253..9f995a7ce6 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/installing-an-app-in-your-personal-account.md @@ -39,7 +39,7 @@ Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de factura {% data reusables.marketplace.complete-order-begin-installation %} 8. Revisa la información acerca del acceso de la app a tu cuenta personal y a tus datos, luego haz clic en **Authorize application** (Autorizar aplicación). -### Further reading +### Leer más - "[Actualizar el método de pago de tu cuenta personal](/articles/updating-your-personal-account-s-payment-method)" - "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)" diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md b/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md index e791c4f627..307ee3a79a 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace.md @@ -1,7 +1,7 @@ --- title: Comprar e instalar aplicaciones en el Mercado GitHub intro: '{% data variables.product.prodname_marketplace %} incluye apps con planes de precios gratuitos y pagos. Cuando encuentras una aplicación paga que desearías usar para tu cuenta personal u organización, puedes comprar e instalar la app utilizando tu información de facturación existente.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/purchasing-and-installing-apps-in-github-marketplace versions: diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md index 83be3aac78..b3595c95c6 100644 --- a/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/es-ES/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,7 +38,7 @@ Cada desarrollador puede crear uno o más codespaces para cualquier repositorio {% data reusables.codespaces.about-personalization %}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)". -You can configure settings to add encrypted secrets, enable GPG verification, and allow codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." +Puedes configurar los ajustes para agregar secretos cifrados, habilitar la verificación GPG y permitir que los codespaces accedan a otros repositorios. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Administrar la verificación de GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", y "[Ad,omostrar el acceso y la seguridad para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". {% data reusables.codespaces.you-can-see-all-your-codespaces %} diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index 4d33ae113e..0e80a49767 100644 --- a/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/es-ES/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -58,14 +58,14 @@ Puedes utilizar claves de configuración compatibles con {% data variables.produ #### Ajustes generales - `name (nombre)` -- `parámetros` +- `settings` - `extensions` - `forwardPorts` - `postCreateCommand` #### Ajustes de Docker, Dockerfile o de imagen -- `imagen` +- `image` - `dockerFile` - `context` - `containerEnv` diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md index 0de052636d..9278f15f29 100644 --- a/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md +++ b/translations/es-ES/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing access and security for Codespaces -intro: You can manage the repositories that codespaces can access. +title: Administrar el acceso y la seguridad de los Codespaces +intro: Puedes administrar los repositorios a los cuales pueden acceder los codespaces. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,30 +8,30 @@ versions: {% note %} -**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**Nota:** El acceso y la seguridad para los {% data variables.product.prodname_codespaces %} se encuentra actualmente en beta y está sujeta a cambios. {% endnote %} -### Managing security and access for your user account +### Administrar la seguridad y el acceso para tu cuenta de usuario -When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. +Cuando habilitas el acceso y la seguridad para un repositorio que pertenezca a tu cuenta de usuario, cualquier codespace que crees para éste tendrá permisos de lectura y escritura en el resto de los repositorios que te pertenezcan. Puedes habilitar el acceso y la seguridad para que no se aplique en ninguno de tus repositorios, para que se aplique en todos ellos, o solo para algunos específicos. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-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 you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) +1. Debajo de "Acceso y seguridad"; selecciona la configuración que quieras para tu cuenta de usurio. ![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. Si eliges "Repositorios seleccionados", selecciona el menú desplegable y luego da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que te pertenecen. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de tus repositorios. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) -### Managing security and access for your organization +### Administrar la seguridad y el acceso para tu organización -Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. +Los propietarios de las organizaciones pueden administrar la seguridad y el acceso para los {% data variables.product.prodname_codespaces %}. -When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. +Cuando habilitas el acceso y la seguridad para un repositorio que pertenece a tu organización, cualquier codespace que se cree para dicho repositorio tendrá permisos de lectura y escritura en el resto de los repositorios que le pertenezcan a la organización. Puedes habilitar el acceso y la seguridad para que no se aplique en ninguno de los repositorios de la organización, para que se aplique en todos ellos, o solo para algunos específicos. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.click-codespaces %} -5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. - ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.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-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) +5. Para aprobar las [condiciones de servicio del programa de prelanzamientos](/github/site-policy/github-pre-release-program) en nombre de tu organización y habilitar los {% data variables.product.prodname_codespaces %}, debajo de "Permisos de usuario", selecciona **Usuarios seleccionados**, y teclea el nombre de usuario de cada una de las personas a las cuales quieras otorgar acceso. Repite esto para todos los usuarios que quieras que tengan acceso a los codespaces de tu organización. + ![Botón radial para los "Usuarios seleccionados"](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. Debajo de "Acceso y seguridad", selecciona la configuración que quieras para tu organización.![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. Si eliges "Repositorios seleccionados"; entonces selecciona el menú desplegable y da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que pertenecen a tu organización. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de los repositorios. ![Menú desplegable para los "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md index 1986a6630a..4975c0d5c6 100644 --- a/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md +++ b/translations/es-ES/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing encrypted secrets for Codespaces -intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +title: Administrar los secretos cifrados para los Codespaces +intro: Puedes almacenar información sensible, como los tokens, a la cual quieras acceder en tus codespaces en forma de variables de ambiente. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,46 +8,46 @@ versions: {% note %} -**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**Nota:** Los secretos cifrados para los {% data variables.product.prodname_codespaces %} se encuentran actualmente en beta y están sujetos a cambios. {% endnote %} -### About encrypted secrets for {% data variables.product.prodname_codespaces %} +### Acerca de los secretos cifrados para los {% data variables.product.prodname_codespaces %} -You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. +Puedes agregar a tu cuenta de usuario los secretos cifrados que quieras utilizar en tus codespaces. Por ejemplo, puede que quieras almacenar y acceder a la siguiente información sensible en forma de un secreto cifrado. -- Personal access tokens to cloud services -- Service principals -- Subscription identifiers +- Tokens de acceso personal para los servicios en la nube +- Entidades de servicio +- Identificadores de suscripción -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. +Puedes elegir qué repositorios deben tener acceso a cada secreto. Posteriormente, puedes utilizar el secreto en cualquier codespace que crees para un repositorio que tenga acceso a él. -### Adding a secret +### Agregar un secreto {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +1. A la derecha de "Secretos de los codespaces", da clic en **Secreto nuevo**. ![Botón de "Secreto nuevo"](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Debajo de "Nombre", teclea un nombre para tu secreto. ![Caja de texto de "Nombre"](/assets/images/help/settings/codespaces-secret-name-field.png) {% data reusables.user_settings.codespaces-secret-value %} {% data reusables.user_settings.codespaces-secret-repository-access %} 1. Haz clic en **Agregar secreto** (Agregar secreto). -### Editing a secret +### Editar un secreto -You can update the value of an existing secret, and you can change which repositories can access a secret. +Puedes actualizar el valor de un secreto existente y puedes cambiar qué repositorios pueden acceder a un secreto. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +1. Debajo de "Secretos de los codespaces"; a la derecha del secreto que quieras editar, da clic en **Actualizar**. ![Botón de "Actualizar"](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Debajo de "Valor", da clic en **Ingresar un valor nuevo**. ![Enlace de "Ingresar un valor nuevo"](/assets/images/help/settings/codespaces-secret-update-value-text.png) {% data reusables.user_settings.codespaces-secret-value %} {% data reusables.user_settings.codespaces-secret-repository-access %} -1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Opcionalmente, para eliminar el acceso del secreto a un repositorio, deselecciona el repositorio. ![Casillas de verificación para eliminar el acceso a los repositorios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) 1. Haz clic en **Guardar cambios**. -### Deleting a secret +### Borrar un secreto {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Lee la advertencia y da clic en **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) +1. Debajo de "Secretos de los codespaces", a la derecha del secreto que quieras borrar, da clic en **Borrar**. ![Botón de "Borrar"](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Lee la advertencia y da clic en **OK**. ![Confirmación para borrar un secreto](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md index a326f5be89..55140df408 100644 --- a/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/es-ES/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing GPG verification for Codespaces -intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +title: Administrar la verificación de GPG para los Codespaces +intro: Puedes permitir que {% data variables.product.company_short %} utilice automáticamente GPG para firmar las confirmaciones que haces en tus codespaces para que otras personas puedan tener la confianza de que los cambios vienen de una fuente confiable. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,13 +8,13 @@ versions: {% note %} -**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**Nota:** La verificación de GPG para los {% data variables.product.prodname_codespaces %} se encuentra actualmente en beta y está sujeta a cambios. {% endnote %} -After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." +Después de que habilitas la verificación de GPG, {% data variables.product.company_short %} firmará automáticamente las confirmaciones que hagas en los {% data variables.product.prodname_codespaces %} y éstas tendrán un estado de verificado en {% data variables.product.product_name %}. Predeterminadamente, la verificación GPG se encuentra inhabilitada para los codespaces que creas. Puedes elegir permitir la verificación de GPG para todos los repositorios o para repositorios específicos. Habilita la verificación GPG únicamente para los repositorios en los cuales confías. Para obtener más información acerca de las confirmaciones firmadas por {% data variables.product.product_name %}, consulta la sección "[Acerca de la verificación de firmas de las confirmaciones](/github/authenticating-to-github/about-commit-signature-verification)". {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) +1. Debajo de "verificación GPG", selecciona la configuración que quieras para la verificación de GPG. ![Botones radiales para administrar la verificación GPG](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. Si eliges "Repositorios seleccionados"; selecciona el menú desplegable y luego da clic en el repositorio para el cual quieras habilitar la verificación de GPG. Repite esto para todos los repositorios en los cuales quieras habilitar la verificación GPG. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index 71bfb57fb3..3ba0b81e59 100644 --- a/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/es-ES/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,8 +40,8 @@ Para obtener más información, consulta la sección "[Personalizing](https://do {% endnote %} -You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." +También puedes configurar los ajustes para que tu cuenta de usuario agregue secretos cifrados, habilite la verificación de GPG y permita a tus codespaces acceder a otros repositorios. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Administrar la verificación de GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", y "[Ad,omostrar el acceso y la seguridad para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". -### Further reading +### Leer más * "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". diff --git a/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md b/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md index a7d38a6026..9cf68af1cb 100644 --- a/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md +++ b/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md @@ -12,7 +12,7 @@ Para automatizar las tareas comunes, respaldar tus datos, o crear integraciones Para obtener más información acerca de la API, consulta la [API de REST de GitHub](/rest) y la [API de GraphQL de GitHub](/graphql). También puedes mantenerte actualizado respecto de las novedades relacionadas con la API siguiendo el [{% data variables.product.prodname_dotcom %}Blog del programador](https://developer.github.com/changes/). -### Further reading +### Leer más - "[Respaldar un repositorio](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %} - "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} diff --git a/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md index c6c4d4b75c..69eb9129f2 100644 --- a/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -41,6 +41,6 @@ Para evadir estos mensajes, puedes utilizar el almacenamiento de contraseñas en {% endwarning %} -### Further reading +### Leer más - "[Autorizar las Apps de OAuth](/developers/apps/authorizing-oauth-apps)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index e2c5685c74..bdafef2075 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -1,6 +1,6 @@ --- -title: Acerca del escaneo de código -intro: 'Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar vulnerabilidades de seguridad y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.' +title: About code scanning +intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/about-automated-code-scanning @@ -12,39 +12,40 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### Acerca de {% data variables.product.prodname_code_scanning %} +### About {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar, clasificar y priorizar los arreglos a problemas existentes en tu código. {% data variables.product.prodname_code_scanning_capc %} también previene a los desarrolladores de introducir nuevos problemas. Puedes programar días y horas específicos para los escaneos, o activarlos cuando ocurra un evento específico en el repositorio, tal como una carga de información. +You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. -Si {% data variables.product.prodname_code_scanning %} encuentra una vulnerabilidad potencial o un error en tu código, {% data variables.product.prodname_dotcom %} mostrará una alerta en el repositorio. {% data variables.product.prodname_dotcom %} cerrará la alerta una vez que arregles el código que la activó. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". +If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see +"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." -Para comenzar con el {% data variables.product.prodname_code_scanning %}, consulta la sección "[Habilitar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)". +To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." -### Acerca de {% data variables.product.prodname_codeql %} +### About {% data variables.product.prodname_codeql %} -Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). {% data variables.product.prodname_codeql %} trata el código como datos, lo cual te permite encontrar vulenrabilidades potenciales en tu código con más confianza que en los anallizadores estáticos trandicionales. +You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. -{% data variables.product.prodname_ql %}Es el lenguaje de consulta que impulsa a {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} es un lenguaje de programación lógico orientado a objetos. {% data variables.product.company_short %}, los expertos del lenguaje, y los investigadores de seguridad crean las consultas que se utilizan para {% data variables.product.prodname_code_scanning %}, y éstas son de código abierto. La comunidad mantiene y actualiza estas consultas para mejorar el análisis y reducir los falsos positivos. Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) en el sitio web de GitHub Security Lab. +{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. -Para obtener más información acerca de las terminales de la API para {% data variables.product.prodname_code_scanning %}, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)". +{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. {% data reusables.code-scanning.supported-languages %} -Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) en la documentación de {% data variables.product.prodname_codeql %}. +You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. {% if currentVersion == "free-pro-team@latest" %} -### Acerca de la facturación para {% data variables.product.prodname_code_scanning %} +### About billing for {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} utiliza {% data variables.product.prodname_actions %}, y cada ejecución de un flujo de trabajo de {% data variables.product.prodname_code_scanning %} consume minutos para {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". +{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." {% endif %} -### Acerca de las herramientas de escaneo de código de terceros +### About third-party code scanning tools {% data reusables.code-scanning.you-can-upload-third-party-analysis %} @@ -55,6 +56,6 @@ Puedes ver y contribuir con las consultas para {% data variables.product.prodnam ### Further reading {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" +- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) -- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) en el sitio web del Comité OASIS +- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md index 0a82d33ace..c14dbd00cc 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md @@ -19,7 +19,7 @@ Si utilizas una herramienta de análisis estático de terceros que pueda produci Puedes utilizar los webhooks del {% data variables.product.prodname_code_scanning %} para crear o configurar integraciones, tales como [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) o [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), que se suscriban a los eventos de {% data variables.product.prodname_code_scanning %} en tu repositorio. Por ejemplo, puedes crear una integración que cree una propuesta en {% data variables.product.product_location %} o que te envíe una notificación de Slack cuando se agregue una alerta de {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta las secciones "[Crear webhooks](/developers/webhooks-and-events/creating-webhooks)" y "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". -### Further reading +### Leer más * "[Acerca del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" * "[Utilizar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} con tu sistema de IC existente](/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md index b4e5c181a5..3954c5acea 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md @@ -2,7 +2,7 @@ title: Escanear tu código automáticamente para encontrar vulnerabilidades y errores shortTitle: Escanear automáticamente intro: 'Puedes encontrar vulnerabilidades y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.' -mapTopic: verdadero +mapTopic: true product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index d18a99b925..612c2f6227 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -1,8 +1,8 @@ --- -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: 'Las personas con permisos de escritura en un repositorio pueden configurar {% data variables.product.prodname_code_scanning %} para el mismo.' +permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' miniTocMaxHeadingLevel: 4 versions: free-pro-team: '*' @@ -12,47 +12,49 @@ versions: {% 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 %} dentro de {% data variables.product.product_location %} utilizando {% data variables.product.prodname_actions %}, o desde tu sistema de integración continua (IC) utilizando el {% data variables.product.prodname_codeql_runner %}. Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". Para obtener más información acerca del {% data variables.product.prodname_codeql_runner %}, consulta la sección [Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". +You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. 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)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." -Este artìculo es acerca de ejecutar el {% data variables.product.prodname_code_scanning %} dentro de {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. -Antes de que puedas configurar {% data variables.product.prodname_code_scanning %} para un repositorio, debes habilitar {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a dicho repositorio. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo. +Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-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 %}{% if currentVersion ver_gt "enterprise-server@2.21" %} en {% data variables.product.prodname_dotcom_the_website %}{% endif %} contiene otros flujos de trabajo de {% data variables.product.prodname_code_scanning %} que puedes utilizar. {% if currentVersion == "free-pro-team@latest" %}Puedes encontrar una selección de estos en la página de "Iniciar con el {% 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 especificos que se muestran en este artículo se relacionan con el archivo del {% 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 %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}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. You can find the workflow by searching for its file name. 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 enabled 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)." -#### 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. {% if currentVersion ver_gt "enterprise-server@2.21" %}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 "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)". +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. {% if currentVersion ver_gt "enterprise-server@2.21" %}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 "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-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)." -#### 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: @@ -67,47 +69,49 @@ 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: push: + branches: [main, protected] pull_request: + branches: [main] schedule: - cron: '0 15 * * 0' ``` -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 a las 3 P.M. cada domingo +This workflow scans: +* Every push to the default branch and the protected branch +* Every pull request to the default branch +* The default branch at 3 P.M. every Sunday -### 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 %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}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. {% if currentVersion ver_gt "enterprise-server@2.21" %}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: @@ -116,23 +120,23 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% if currentVersion == "free-pro-team@latest" %}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 %} +{% if currentVersion == "free-pro-team@latest" %}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 {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Sintaxis de flujo 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 {% if currentVersion ver_gt "enterprise-server@2.21" %}"[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 %}." -{% if currentVersion ver_gt "enterprise-server@2.21" %}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 %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}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 %} -### 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.supported-languages %} -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 ene l repositorio cuando se habilitó el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se habilitó 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 enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. ```yaml jobs: @@ -145,7 +149,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 @@ -153,15 +157,15 @@ Si tu flujo de trabajo no contiene una matriz que se llame `language`, entonces languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### 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: @@ -195,11 +199,11 @@ jobs: ``` {% endif %} -### Ejecutar consultas adicionales +### Running additional queries {% data reusables.code-scanning.run-additional-queries %} -Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. +To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. ``` yaml - uses: github/codeql-action/init@v1 @@ -207,13 +211,13 @@ Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` queries: COMMA-SEPARATED LIST OF PATHS ``` -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 %} -Puedes ejecutar consultas adicionales si las especificas en un archivo de configuración. So quieres ejecutar el conjunto combinado de consultas adicionales que se especifica aquí y en el archivo de configuración, agrega como prefijo el valor `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 are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `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 `+` se asegura de que las consultas adicionales especificadas se utilicen en conjunto con cualquier otra consulta que se especifique en el archivo de configuración referenciado. +In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. ``` yaml - uses: github/codeql-action/init@v1 @@ -222,11 +226,11 @@ En el siguiente ejemplo, el símbolo `+` se asegura de que las consultas adicion queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main ``` -### Utilizar una herramienta de escaneo de código de terceros +### Using a custom configuration file -Como alternativa para especificar qué consultas se ejecutarán en un archivo de flujo de trabajo, puedes hacer esto en un archivo de configuración diferente. También puedes utilizar un archivo de configuración para inhabilitar las consultas predeterminadas y para especificar qué directorios escanear durante el análisis. +As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration 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 @@ -234,13 +238,13 @@ En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acc config-file: ./.github/codeql/codeql-config.yml ``` -The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. +The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. -La configuración en el archivo se escribe en formato YAML. +The settings in the file are written in YAML format. -#### 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: @@ -249,17 +253,17 @@ queries: - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls ``` -Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración. +Optionally, you can give each array element a name, as shown in the example configuration files below. -Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)". +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 -Para los lenguajes interpretados compatibles con {% data variables.product.prodname_codeql %} (Python y JavaScript/TypeScript), puedes restringir el {% data variables.product.prodname_code_scanning %} para los archivos que estén en directorios específicos si agregas una matriz de `paths` al archivo de configuración. 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 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: @@ -271,32 +275,32 @@ 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)". -* `**` **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)." +* `**` 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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 acerca de cómo configurar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} para los lenguajes compilados, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/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](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." -### Acceder a repositorios privados +### Accessing private repositories -Si tu flujo de trabajo para {% data variables.product.prodname_code_scanning %} accede a repositorios privados en {% data variables.product.prodname_dotcom %}, necesitarás configurar Git para autenticarte con un token de acceso personal. Define el secreto en el ambiente de ejecución utilizando `jobs..steps[*].env` en tu flujo de trabajo antes de cualquier acción de {% data variables.product.prodname_codeql %}. 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)" y "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". +If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. 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)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." -Por ejemplo, la siguiente configuración hace que Git reemplace las URL enteras de los repositorios `ghost/foo`, `ghost/bar`, y `ghost/baz` en {% data variables.product.prodname_dotcom_the_website %} con aquellas que incluyen tu token de acceso personal y que almacenaste en la variable de ambiente `ACCESS_TOKEN`. +For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. {% raw %} ```yaml @@ -311,6 +315,6 @@ steps: ``` {% endraw %} -### 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 1b6831d3b9..1e83e9fea2 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ Para integrar el {% data variables.product.prodname_code_scanning %} en tu siste En general, se invoca el {% data variables.product.prodname_codeql_runner %} de la siguiente manera. -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -39,7 +39,7 @@ El {% data variables.product.prodname_codeql_runner %} detecta automáticamente Para anular la detección automática de lenguajes, ejecuta el comando `init` con el marcador `--languages`, seguido de una lista separada por comas de las palabras clave de los lenguajes. Las palabras clave para los lenguajes compatibles son `cpp`, `csharp`, `go`, `java`, `javascript`, y `python`. -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -55,7 +55,7 @@ Si también estás usando un archivo de configuración para los ajustes personal En el siguiente ejemplo, el símbolo `+` garantiza que el {% data variables.product.prodname_codeql_runner %} utilizará consultas adicionales junto con cualquier otra consulta que se especifique en el archivo de configuración 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 ``` @@ -68,7 +68,7 @@ El archivo de configuración es un archivo de YAML. Utiliza una sintaxis similar Utiliza el marcador `--config-file` del comando `init` para especificar el archivo de configuración. El valor de `--config-file` es la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _.github/codeql/codeql-config.yml_. -``` +```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml ``` @@ -84,7 +84,7 @@ Para varios sistemas de compilación comunes, el {% data variables.product.prodn El proceso de `autobuild` solo intenta siempre compilar _un_ solo lenguaje compilado para un repositorio. El lenguaje que se selecciona automáticamente para su análisis es aquél presente en más archivos. Si quieres elegir un lenguaje explícitamente, utiliza el marcador `--language` del comando `autobuild`. -``` +```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` @@ -148,7 +148,7 @@ Analiza el código en las bases de datos de {% data variables.product.prodname_c | `--debug` | | Ninguno. Imprime una salida más verbosa. | | `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | -#### `upload` +#### `cargar` Carga los archivos SARIF a {% data variables.product.product_location %}. diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index 4c3641a0e5..9ddbfface4 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -1,9 +1,9 @@ --- -title: Habilitar el escaneo de código para un repositorio -shortTitle: Habilitar el escaneo de código -intro: 'Puedes habilitar {% data variables.product.prodname_code_scanning %} para el repositorio de tu proyecto.' +title: Enabling code scanning for a repository +shortTitle: Enabling code scanning +intro: 'You can enable {% data variables.product.prodname_code_scanning %} for your project''s repository.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'Si tienes permiso de escritura en un repositorio, puedes habilitar el {% data variables.product.prodname_code_scanning %} para éste.' +permissions: 'If you have write permissions to a repository, you can enable {% data variables.product.prodname_code_scanning %} for that repository.' redirect_from: - /github/managing-security-vulnerabilities/configuring-automated-code-scanning - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning @@ -15,102 +15,106 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### Opciones para habilitar el {% data variables.product.prodname_code_scanning %} +### Options for enabling {% data variables.product.prodname_code_scanning %} -Tú decides cómo generar las alertas del {% data variables.product.prodname_code_scanning %} y qué herramientas utilizarás a nivel del 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 de{% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)". +You decide how you generate {% data variables.product.prodname_code_scanning %} alerts, and which tools you 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_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)." {% data reusables.code-scanning.enabling-options %} -### Habilitar el {% data variables.product.prodname_code_scanning %} utilizando acciones +### Enabling {% data variables.product.prodname_code_scanning %} using actions -{% if currentVersion == "free-pro-team@latest" %}Si utilizas acciones para ejecutar el {% data variables.product.prodname_code_scanning %} se utilizarán minutos. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". +{% if currentVersion == "free-pro-team@latest" %}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 %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. A la derecha de "{% data variables.product.prodname_code_scanning_capc %}", da clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. ![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. ![Botón de "Configurar este flujo de trabajo" debajo del encabezado de " Iniciar con el {% data variables.product.prodname_code_scanning %}"](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) -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 %}", click **Set up {% data variables.product.prodname_code_scanning %}**. + !["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) +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 %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/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 %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. -### Bulk enabling {% data variables.product.prodname_code_scanning %} +### Bulk enabling {% data variables.product.prodname_code_scanning %} You can enable {% data variables.product.prodname_code_scanning %} in many repositories in bulk using a script. For an example of a script that raises 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. -### 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 habilitar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones conforme se ejecutan. +After enabling {% 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 %}. The text of the entry is the title you gave your commit message. + 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. - ![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) {% 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 habilites para ejecutarse en las soilcitudes de cambios siempre tiene por lo menos dos entradas que se listan en la secciòn de verificaciones de ellas. 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 enable 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, veràs inicialmente un mensaje de "Missing analysis" cuando des clic en la parte de **Detalles** de la verificaciòn "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA". +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 a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. - ![Falta el análisis para el mensaje de confirmación](/assets/images/help/repository/code-scanning-missing-analysis.png) + ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) -#### Razones para recibir un mensaje de "missing analysis" +#### Reasons for the "missing analysis" message -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 das clic en la verificaciòn de los resultados de la solicitud de cambios, veràs el mensaje "Missing analysis for base commit SHA-HASH". +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 "Missing analysis for base commit SHA-HASH" 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. - ![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) - 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 habilitar el {% data variables.product.prodname_code_scanning %} y permitir que sus acciones se completen, puedes: +After enabling {% 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -- Ver cualquier alerta que se genere para una solicitud de cambios que se emita despuès de que habilitaste 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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)". -- 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 %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/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 %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +- View any alerts generated for a pull request submitted after you enabled {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/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)." +- 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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 %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md index 9c8218e679..ea2150c130 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md @@ -2,7 +2,7 @@ title: Integrarse con el escaneo de código shortTitle: Integración intro: 'Puedes integrar las herramientas de análisis de código de terceros con el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_dotcom %} su cargas datos como archivos SARIF.' -mapTopic: verdadero +mapTopic: true product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index de32f24ca5..63170bfc95 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ Puedes configurar el {% data variables.product.prodname_code_scanning %} para qu 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### Acerca de los detalles de las alertas 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 la misma, tales como la severidad y la naturaleza de dicho 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. @@ -122,7 +124,7 @@ Si un proyecto tiene varias alertas que quieras descartar por la misma razón, p {% endif %} -### Further reading +### Leer más - "[Clasificar 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)" - "[Habilitar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index f93a4d2233..029c632e4c 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -32,11 +32,11 @@ El {% data variables.product.prodname_codeql_runner %} es una herramienta de lí **Notas:** {% if currentVersion == "free-pro-team@latest" %} -* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. Se puede utilizar gratuitamente en los repositorios que mantiene {% data variables.product.prodname_dotcom_the_website %}, y está disponible para utilizarse en aquellos que pertenecen a los clientes con una licencia de {% data variables.product.prodname_advanced_security %}. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +* El {% data variables.product.prodname_codeql_runner %} utiliza el CLI de {% data variables.product.prodname_codeql %} para analizar el código y, por lo tanto, tiene las mismas condiciones de licencia. Se puede utilizar gratuitamente en los repositorios que mantiene {% data variables.product.prodname_dotcom_the_website %}, y está disponible para utilizarse en aquellos que pertenecen a los clientes con una licencia de {% data variables.product.prodname_advanced_security %}. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". {% else %} -* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +* El {% data variables.product.prodname_codeql_runner %} se encuentra disponible para los clientes con una licencia de {% data variables.product.prodname_advanced_security %}. {% endif %} -* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +* El {% data variables.product.prodname_codeql_runner %} no debe confundirse con el CLI de {% data variables.product.prodname_codeql %}. El CLI de {% data variables.product.prodname_codeql %}es una interface de línea de comandos que te permite crear bases de datos de {% data variables.product.prodname_codeql %} para la investigación de seguridad y ejecutar consultas de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". {% endnote %} ### Descargar el {% data variables.product.prodname_codeql_runner %} @@ -60,7 +60,7 @@ En Windows, el archivo `codeql-runner-win.exe` habitualmente no necesita que se ### Agregar el {% data variables.product.prodname_codeql_runner %} a tu sistema de IC -Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from GitHub, for example: +Una vez que descargas el {% data variables.product.prodname_codeql_runner %} y verificas que puede ejecutarse, debes poner el ejecutor disponible para cada servidor de IC que pretendas utilizar para el {% data variables.product.prodname_code_scanning %}. Por ejemplo, podrías configurar cada servidor para que copie el ejecutor desde una ubicación interna y central. Como alternativa, podrías utilizar la API de REST para obtener el ejecutor directamente desde GitHub, por ejemplo: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -69,8 +69,8 @@ chmod +x codeql-runner-linux Además, cada servidor de IC necesitará también: -- Un token de acceso personal o de {% data variables.product.prodname_github_app %} para que utilice el {% data variables.product.prodname_codeql_runner %}. You must use an access token with the `security_events` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. Para obtener más información, consulta las secciones "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" y "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". -- Acceso al paquete de {% data variables.product.prodname_codeql %} asociado con este lanzamiento del {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. Para obtener más información, consulta la sección "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +- Un token de acceso personal o de {% data variables.product.prodname_github_app %} para que utilice el {% data variables.product.prodname_codeql_runner %}. Debes utilizar un token de acceso con el alcance `security_events` o una {% data variables.product.prodname_github_app %} con el permiso de escritura de `security_events`. Para obtener más información, consulta las secciones "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" y "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +- Acceso al paquete de {% data variables.product.prodname_codeql %} asociado con este lanzamiento del {% data variables.product.prodname_codeql_runner %}. Este paquete contiene consultas y bibliotecas necesarias para el análisis de {% data variables.product.prodname_codeql %}, adicionado con el CLI de {% data variables.product.prodname_codeql %}, el cual utiliza internamente el ejecutor. Para obtener más información, consulta la sección "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". Las opciones para proporcionar acceso al paquete de {% data variables.product.prodname_codeql %} son: @@ -93,6 +93,8 @@ Puedes configurar la ubicación en la que {% data variables.product.prodname_cod Para ver la referencia de línea de comandos para el ejecutor, utiliza el marcador `-h`. Por ejemplo, para listar todos los comandos, ejecuta: `codeql-runner-OS -h`, o para listar todos los marcadores disponibles para el comando `init`, ejecuta: `codeql-runner-OS init -h` (en donde el `OS` variará de acuerdo con el ejecutable que estés utilizando). Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)". +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Ejemplo básico Este ejemplo ejecuta un análisis de {% data variables.product.prodname_codeql %} en un servidor de IC con Linux para el repositorio de `octo-org/example-repo` en `{% data variables.command_line.git_url_example %}`. El proceso es muy simple, ya que el repositorio contiene únicamente los lenguajes que puede analizar {% data variables.product.prodname_codeql %} directamente, sin que se tenga que compilar (es decir, Go, JavaScript, Python, y TypeScript). @@ -167,7 +169,7 @@ Este ejemplo es similar al anterior, sin embargo, esta vez el repositorio tiene {% endnote %} -### Further reading +### Leer más - "[Configurar el {% data variables.product.prodname_code_scanning %} en tu sistema](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)" - "[Solucionar problemas del {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 755e76c363..b1c62d1323 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -1,7 +1,7 @@ --- -title: Soporte de SARIF para escaneo de código -shortTitle: Soporte de SARIF -intro: 'Para mostrar los resultados de una herramienta de análisis estático de terceros en tu repositorio en {% data variables.product.prodname_dotcom %}, necesitas que éstos se almacenen en un archivo SARIF que sea compatible con un subconjunto del modelo de JSON para SARIF 2.1.0 para el {% data variables.product.prodname_code_scanning %}. Si utilizas el motor de análisis estático predeterminado de {% data variables.product.prodname_codeql %}, tus resultados se mostrarán automáticamente en tu repositorio de {% data variables.product.prodname_dotcom %}.' +title: SARIF support for code scanning +shortTitle: SARIF support +intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for {% data variables.product.prodname_code_scanning %}. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning @@ -12,116 +12,120 @@ versions: {% data reusables.code-scanning.beta %} -### Acerca del soporte de SARIF +### About SARIF support -SARIF (Formato de Intercambio de Resultados de Análisis Estático, por sus siglas en inglés) es un [Estándar de OASIS](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) que define un formato de archivo de salida. El estándar SARIF se utiliza para optimizar la manera en el que las herramientas de análisis estático comparten sus resultados. {% data variables.product.prodname_code_scanning_capc %} es compatible con un subconjunto del modelo SARIF 2.1.0 JSON. +SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) that defines an output file format. The SARIF standard is used to streamline how static analysis tools share their results. {% data variables.product.prodname_code_scanning_capc %} supports a subset of the SARIF 2.1.0 JSON schema. -Para cargar un archivo SARIF desde un motor de análisis estático de código desde un tercero, necesitaras asegurarte de que los archivos cargados utilicen la versión SARIF 2.1.0. {% data variables.product.prodname_dotcom %} analizará el archivo SARIF y mostrará las alertas utilizando los resultados en tu repositorio como parte de la experiencia del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". Para obtener más información acerca del modelo SARIF 2.1.0, consulta [`sari-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json). +To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json). -Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará cuando cargues el archivo SARIF utilizando {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Habilitar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" o "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". +If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." -{% data variables.product.prodname_dotcom %} utiliza propiedades en el archivo SARIF para mostrar alertas. Por ejemplo, la `shortDescription` y `fullDescription` aparecen hasta arriba de una alerta de {% data variables.product.prodname_code_scanning %}. La `location` permite a {% data variables.product.prodname_dotcom %} mostrar anotaciones en tu archivo de código. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". +{% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -Si SARIF es nuevo para ti y quieres aprender más, consulta el repositorio [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) de Microsoft. +If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) repository. -### Prevenir alertas duplicadas utilizando huellas dactilares +### Preventing duplicate alerts using fingerprints -Cada vez que el flujo de trabajo de {{ site.data.variables.product.prodname_actions }} ejecuta un nuevo escaneo de código, los resultados de cada ejecución se procesan y se agregan alertas al repositorio. Para prevenir las alertas duplicadas para el mismo problema, {% data variables.product.prodname_code_scanning %} utiliza huellas dactilares para empatara los resultados a través de diversas ejecuciones para que solo aparezcan una vez en la última ejecución para la rama seleccionada. Esto hace posible empatar las alertas con la línea de código correcta cuando se editan los archivos. +Each time the results of a new code scan are uploaded, the results are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the right line of code when files are edited. -{% data variables.product.prodname_dotcom %} utiliza la propiedad `partialFingerprints` en el estándar OASIS para detectar cuando dos resultados son lógicamente idénticos. Para obtener más información, consulta la sección "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" en la documentación de OASIS. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. -Los archivos SARIF que crea el {% data variables.product.prodname_codeql_workflow %} o los que utilizan el {% data variables.product.prodname_codeql_runner %} incluyen datos de huellas digitales. Si cargas un archivo SARIF utilizando la acción `upload-sarif` y no se encuentran estos datos, {% data variables.product.prodname_dotcom %} intentará poblar el campo `partialFingerprints` desde los archivos de origen. Para obtener más información acerca de cargar los resultados, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)". +SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." -Si cargaste un archivo SARIF sin datos de huella digital utilizando la terminal de la API de `/code-scanning/sarifs`, se procesarán y se mostrarán las alertas del {% data variables.product.prodname_code_scanning %}, pero los usuarios podrían ver alertas duplicadas. Para evitar el ver alertas duplicadas, debes calcular los datos de la huella digital y llenar la propiedad de `partialFingerprints` antes de que cargues el archivo SARIF. Puede que el script que utiliza la acción `upload-sarif` te sea útil como punto de inicio: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. Para obtener más información acerca de la API, consulta la sección "[Cargar un archivo SARIF](/rest/reference/code-scanning#upload-a-sarif-file)". +If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)." -### Validar tu archivo SARIF +### Validating your SARIF file -Puedes verificar si un archivo SARIF es compatible con el {% data variables.product.prodname_code_scanning %} si lo pruebas contra las reglas de ingestión de {% data variables.product.prodname_dotcom %}. Para obtener más información, visita el [Validador de archivos SARIF de Microsoft](https://sarifweb.azurewebsites.net/). +You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). -### Propiedades compatibles de archivo de salida SARIF +{% data reusables.code-scanning.upload-sarif-alert-limit %} -Si utilizas un motor de análisis de código diferente a {% data variables.product.prodname_codeql %}, puedes revisar las propiedades SARIF compatibles para optimizar cómo aparecerán los resultados de tu análisis en {% data variables.product.prodname_dotcom %}. +### Supported SARIF output file properties -Puedes cargar cualquier archivo de salida SARIF 2.1.0 válido, sin embargo, {% data variables.product.prodname_code_scanning %} utilizará únicamente las siguientes propiedades compatibles. +If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}. -#### Objeto `sarifLog` +Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.product.prodname_code_scanning %} will only use the following supported properties. -| Nombre | Descripción | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `$schema` | **Requerido.** la URI del modelo SARIF JSON para la versión 2.1.0. Por ejemplo, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. | -| `version` | **Requerido.**{% data variables.product.prodname_code_scanning_capc %} solo es compatible con la versión `2.1.0` de SARIF. | -| `runs[]` | **Requerido.** Un archivo SARIF contiene un arreglo de una o más ejecuciones. Cada ejecución representa una sola ejecución de una herramienta de análisis. Para obtener más información acerca de una `run`, consulta el [ objeto `run`](#run-object). | +#### `sarifLog` object -#### Objeto `run` +| Name | Description | +|----|----| +| `$schema` | **Required.** The URI of the SARIF JSON schema for version 2.1.0. For example, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. | +| `version` | **Required.** {% data variables.product.prodname_code_scanning_capc %} only supports SARIF version `2.1.0`. +| `runs[]` | **Required.** A SARIF file contains an array of one or more runs. Each run represents a single run of an analysis tool. For more information about a `run`, see the [`run` object](#run-object). -{% data variables.product.prodname_code_scanning_capc %} utiliza el objeto `run` para filtrar los resultados por herramienta y proporcionar información acerca del origen de un resultado. El objeto `run` contienen el objeto componente de herramienta `tool.driver`, el cual contiene información acerca de la herramienta que generó el resultado. Cada `run` puede tener únicamente resultados para la herramienta de análisis. +#### `run` object -| Nombre | Descripción | -| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `tool.driver.name` | **Requerido.** El nombre de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre en {% data variables.product.prodname_dotcom %} para permitirte filtrar los resultados por herramienta. | -| `tool.driver.version` | **Opcional.** La versión de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. | -| `tool.driver.semanticVersion` | **Opcional.** La versión de la herramienta de análisis, especificada por el formato de Semantic Versioning 2.0. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. Para obtener más información, consulta la sección "[Semantic Versioning 2.0.0](https://semver.org/)" en la documentación de Semantic Versioning. | -| `tool.driver.rules[]` | **Requerido.** Un arreglo de objetos `reportingDescriptor` que representen reglas. La herramienta de análisis utiliza reglas para encontrar problemas en el código que se analiza. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | -| `results[]` | **Requerido.** Los resultados de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra los resultados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta el [objeto `result`](#result-object). | +{% data variables.product.prodname_code_scanning_capc %} uses the `run` object to filter results by tool and provide information about the source of a result. The `run` object contains the `tool.driver` tool component object, which contains information about the tool that generated the results. Each `run` can only have results for one analysis tool. -#### Objeto `reportingDescriptor` +| Name | Description | +|----|----| +| `tool.driver.name` | **Required.** The name of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the name on {% data variables.product.prodname_dotcom %} to allow you to filter results by tool. | +| `tool.driver.version` | **Optional.** The version of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. | +| `tool.driver.semanticVersion` | **Optional.** The version of the analysis tool, specified by the Semantic Versioning 2.0 format. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. For more information, see "[Semantic Versioning 2.0.0](https://semver.org/)" in the Semantic Versioning documentation. | +| `tool.driver.rules[]` | **Required.** An array of `reportingDescriptor` objects that represent rules. The analysis tool uses rules to find problems in the code being analyzed. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | +| `results[]` | **Required.** The results of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the results on {% data variables.product.prodname_dotcom %}. For more information, see the [`result` object](#result-object). -| Nombre | Descripción | -| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | **Requerido.** Un identificador único para la regla. El `id` se referencia de otras partes del archivo SARIF y {% data variables.product.prodname_code_scanning %} puede utilizarlo para mostrar las URL en {% data variables.product.prodname_dotcom %}. | -| `name (nombre)` | **Opcional.** El nombre de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre para permitir que se filtren los resultados por regla en {% data variables.product.prodname_dotcom %}. | -| `shortDescription.text` | **Requerido** Una descripción breve de la acción. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción corta en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. | -| `fullDescription.text` | **Requerido** Una descripción de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción completa en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. La cantidad máxma de caracteres se limita a 1000. | -| `defaultConfiguration.level` | **Opcional.** Nivel de severidad predeterminado de la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza niveles de severidad para ayudarte a entender qué tan crítico es el resultado de una regla. El atributo `level` en el objeto `result` anular este valor. Para obtener más información, consulta el [objeto `result`](#result-object). Predeterminado: `warning`. | -| `help.text` | **Requerido.** Documentación para la regla utilizando el formato de texto. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. | -| `help.markdown` | **Recomendado.** Documentación para la regla utilizando el formato Markdown. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. Cuando `help.markdown` está disponible, se muestra en vez de `help.text`. | -| `properties.tags[]` | **Opcional.** Un arreglo de secuencias. {% data variables.product.prodname_code_scanning_capc %} utiliza `tags` para permitirte filtrar los resultados en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes filtrar todos los resultados que tengan la etiqueta `security`. | -| `properties.precision` | **Recomendado.** una secuencia que indica qué tan frecuentemente son verdaderos los resultados que indica esta regla. Por ejemplo, si una regla tiene una tasa alta de falsos positivos, la precisión debería ser `low`. {% data variables.product.prodname_code_scanning_capc %} ordena los resultados de acuerdo con su precisión en {% data variables.product.prodname_dotcom %} para que aquellos con el `level` y la `precision` más altos se muestren primero. Puede ser uno de entre: `very-high`, `high`, `medium`, o `low`. | +#### `reportingDescriptor` object + +| Name | Description | +|----|----| +| `id` | **Required.** A unique identifier for the rule. The `id` is referenced from other parts of the SARIF file and may be used by {% data variables.product.prodname_code_scanning %} to display URLs on {% data variables.product.prodname_dotcom %}. | +| `name` | **Optional.** The name of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the name to allow results to be filtered by rule on {% data variables.product.prodname_dotcom %}. | +| `shortDescription.text` | **Required.** A concise description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the short description on {% data variables.product.prodname_dotcom %} next to the associated results. +| `fullDescription.text` | **Required.** A description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the full description on {% data variables.product.prodname_dotcom %} next to the associated results. The max number of characters is limited to 1000. +| `defaultConfiguration.level` | **Optional.** Default severity level of the rule. {% data variables.product.prodname_code_scanning_capc %} uses severity levels to help you understand how critical the result is for a given rule. This value can be overridden by the `level` attribute in the `result` object. For more information, see the [`result` object](#result-object). Default: `warning`. +| `help.text` | **Required.** Documentation for the rule using text format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. +| `help.markdown` | **Recommended.** Documentation for the rule using Markdown format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. When `help.markdown` is available, it is displayed instead of `help.text`. +| `properties.tags[]` | **Optional.** An array of strings. {% data variables.product.prodname_code_scanning_capc %} uses `tags` to allow you to filter results on {% data variables.product.prodname_dotcom %}. For example, it is possible to filter to all results that have the tag `security`. +| `properties.precision` | **Recommended.** A string that indicates how often the results indicated by this rule are true. For example, if a rule has a known high false-positive rate, the precision should be `low`. {% data variables.product.prodname_code_scanning_capc %} orders results by precision on {% data variables.product.prodname_dotcom %} so that the results with the highest `level`, and highest `precision` are shown first. Can be one of: `very-high`, `high`, `medium`, or `low`. #### `result` object -| Nombre | Descripción | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ruleId` | **Opcional.** El identificador único de la regla (`reportingDescriptor.id`). Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} utiliza el identificador de reglas para filtrar los resultados por regla en {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Opcional.** El índice de la regla asociada (`reportingDescriptor` object) en el arreglo de `rules` del componente de la herramienta. Para obtener más información, consulta el [objeto `run`](#run-object). | -| `rule` | **Opcional.** Una referencia que se utiliza para ubicar la regla (descriptor de reporte) para este resultado. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | -| `level` | **Opcional.** La severidad del resultado. Este nivel invalida la severidad predeterminada que se define en la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza el nivel para filtrar los resultados en {% data variables.product.prodname_dotcom %} por severidad. | -| `message.text` | **Requerido.** Un mensaje que describe el resultado. {% data variables.product.prodname_code_scanning_capc %} muestra el texto del mensaje como el título del resultado. Se mostrará únicamente la primera oración del mensaje cuando el espacio visible esté limitado. | -| `locations[]` | **Requerido.** El conjunto de ubicaciones donde se detectó el resultado. Sólo se deberá incluir una ubicación a menos de que el problema solo pueda corregirse realizando un cambio en cada ubicación especificada. **Nota:** Se requiere por lo menos una ubicación para que {% data variables.product.prodname_code_scanning %} muestre el resultado. {% data variables.product.prodname_code_scanning_capc %} utilizará esta propiedad para decidir qué archivo anotar con el resultado. Únicamente si se utiliza el primer valor de este arreglo. Se ignorará al resto de los otros valores. | -| `partialFingerprints` | **Requerido.** Un conjunto de secuencias utilizadas para rastrear la identidad única del resultado. {% data variables.product.prodname_code_scanning_capc %} utiliza `partialFingerprints` para identificar con exactitud qué resultados son los mismos a través de las confirmaciones y ramas. {% data variables.product.prodname_code_scanning_capc %} intentará utilizar `partialFingerprints` si es que existe. Si estás cargando un archivo SARIF de terceros con el `upload-action`, la acción creará un `partialFingerprints` para ti cuando no se incluya en el archivo SARIF. Para obtener más información, consulta "[Prevenir alertas duplicadas utilizando huellas dactilares](#preventing-duplicate-alerts-using-fingerprints)". **Nota:** {% data variables.product.prodname_code_scanning_capc %} utilizará únicamente el `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Un arreglo de objetos de `location` para un objeto de `threadFlow`, el cual describe el progreso de un programa a través de un hilo de ejecución. Un objeto de `codeFlow` describe un patrón de ejecución de código que se utiliza para detectar un resultado. Si se proporcionan flujos de código, {% data variables.product.prodname_code_scanning %} los expandirá en {% data variables.product.prodname_dotcom %} para el resultado relevante. Para obtener más información, consulta el [objeto `location`](#location-object). | -| `relatedLocations[]` | Un conjunto de ubicaciones relevantes para el resultado. {% data variables.product.prodname_code_scanning_capc %} vinculará las ubicaciones cuando se incorporen en el mensaje de resultado. Para obtener más información, consulta el [objeto `location`](#location-object). | -| `suppressions[].state` | **Opcional.** Cuando el `state` se configura como `accepted`, {% data variables.product.prodname_code_scanning %} actualizará el estado del resultado a `Closed` en {% data variables.product.prodname_dotcom %}. | +{% data reusables.code-scanning.upload-sarif-alert-limit %} -#### Objeto `location` +| Name | Description | +|----|----| +| `ruleId`| **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. +| `ruleIndex`| **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). +| `rule`| **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). +| `level`| **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. +| `message.text`| **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. +| `locations[]`| **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. +| `partialFingerprints`| **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. +| `codeFlows[].threadFlows[].locations[]`| **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). +| `relatedLocations[]`| A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). +| `suppressions[].state`| **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}. -Una ubicación dentro de un artefacto de programación, tal como un archivo en el repositorio o un archivo que se generó durante una compilación. +#### `location` object -| Nombre | Descripción | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| `location.id` | **Opcional.** Un identificador único que distingue esta ubicación del resto de las ubicaciones dentro de un objeto de un único resultado. | -| `location.physicalLocation` | **requerido.** Identifica el artefacto y la región. Para obtener más información, consulta la [`physicalLocation`](#physicallocation-object). | -| `location.message.text` | **Opcional.** Un mensaje relevante para la ubicación. | +A location within a programming artifact, such as a file in the repository or a file that was generated during a build. -#### Objeto `physicalLocation` +| Name | Description | +|----|----| +| `location.id` | **Optional.** A unique identifier that distinguishes this location from all other locations within a single result object. +| `location.physicalLocation` | **Required.** Identifies the artifact and region. For more information, see the [`physicalLocation`](#physicallocation-object). +| `location.message.text` | **Optional.** A message relevant to the location. -| Nombre | Descripción | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `artifactLocation.uri` | **Requerido.** Un URI que indica la ubicación de un artefacto, a menudo un archivo ya sea en el repositorio o generado durante una compilación. Si el URI es relativo, deberá ser relativo a la raíz del repositorio de {% data variables.product.prodname_dotcom %} que se está analizando. Por ejemplo, main.js o src/script.js son relativos a la raíz del repositorio. Si la URI es absoluta, {% data variables.product.prodname_code_scanning %} puede utilizarla para revisar el artefacto y empatar archivos en el repositorio. Por ejemplo, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. | -| `region.startLine` | **Requerido.** El número del línea para el primer caracter en la región. | -| `region.startColumn` | **Requerido.** El número de columna del primer caracter en la región. | -| `region.endLine` | **Requerido.** El número de línea de el último caracter en la región. | -| `region.endColumn` | **Requerido.** El número de columna del caracter que sigue al final de la región. | +#### `physicalLocation` object -### Ejemplos de archivo de salida SARIF +| Name | Description | +|----|----| +| `artifactLocation.uri`| **Required.** A URI indicating the location of an artifact, usually a file either in the repository or generated during a build. If the URI is relative, it should be relative to the root of the {% data variables.product.prodname_dotcom %} repository being analyzed. For example, main.js or src/script.js are relative to the root of the repository. If the URI is absolute, {% data variables.product.prodname_code_scanning %} can use the URI to checkout the artifact and match up files in the repository. For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. +| `region.startLine` | **Required.** The line number of the first character in the region. +| `region.startColumn` | **Required.** The column number of the first character in the region. +| `region.endLine` | **Required.** The line number of the last character in the region. +| `region.endColumn` | **Required.** The column number of the character following the end of the region. -Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles y los valores de ejemplo. +### SARIF output file examples -#### Ejemplo con las propiedades mínimas requeridas +These example SARIF output files show supported properties and example values. -Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedades mínimas requeridas para que los resultados de {% data variables.product.prodname_code_scanning %} funcionen como se espera. Si eliminas cualquier propiedad u omites valores, estos datos no se mostrarán correctamente ni se sincronizarán en {% data variables.product.prodname_dotcom %}. +#### Example with minimum required properties + +This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties or don't include values, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}. ```json @@ -170,9 +174,9 @@ Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedad } ``` -#### Ejemplo que muestra todas las propiedades compatibles con SARIF +#### Example showing all supported SARIF properties -Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}. +This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. ```json { diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 64cb745d45..2c3b1ea2bf 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -132,7 +132,7 @@ En proyectos muy grandes, ### Warning: "git checkout HEAD^2 is no longer necessary" -If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action: +Si estás utilizando un flujo de trabajo de {% data variables.product.prodname_codeql %} antiguo, podrías obtener el siguiente mensaje de advertencia en la salida "inicializar {% data variables.product.prodname_codeql %}" de la acción: ``` Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer @@ -140,7 +140,7 @@ necessary. Please remove this step as Code Scanning recommends analyzing the mer commit for best results. ``` -Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow. +Puedes arreglar esto si eliminas las siguientes líneas del flujo de trabajo de {% data variables.product.prodname_codeql %}. Estas líneas se incluyeron en la sección de `steps` del job `Analyze` en las versiones iniciales del flujo de trabajo de {% data variables.product.prodname_codeql %}. ```yaml with: @@ -154,7 +154,7 @@ Fix this by removing the following lines from the {% data variables.product.prod if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} ``` -The revised `steps` section of the workflow will look like this: +La sección revisada de `steps` en el flujo de trabajo se deberá ver así: ```yaml steps: @@ -168,4 +168,4 @@ The revised `steps` section of the workflow will look like this: ... ``` -For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." \ No newline at end of file +Para obtener más información sobre la edición del archivo de flujo de trabajo de {% data variables.product.prodname_codeql %}, consulta la sección "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)". \ No newline at end of file diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 57609d9122..a697977893 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -39,11 +39,13 @@ La acción `upload-sarif` puede configurarse para ejecutarse cuando ocurren los Si tu archivo SARIF no incluye `partialFingerprints`, la acción `upload-sarif` calculará el campo `partialFingerprints` para ti e intentará prevenir las alertas duplicadas. {% data variables.product.prodname_dotcom %} solo puede crear `partialFingerprints` cuando el repositorio contenga tanto el archivo SARIF como el código fuente utilizado en el análisis estático. Para obtener más información acerca de prevenir alertas duplicadas, consulta la sección "[Acerca de la compatibilidad de SARIF con el escaneo de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)". +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Ejemplo de flujo de trabajo para los archivos SARIF generados fuera de un repositorio Puedes crear un nuevo flujo de trabajo que cargue archivos SARIF después de que los confirmes en tu repositorio. Esto es útil cuando el archivo SARIF se genera como un artefacto fuera de tu repositorio. -Este flujo de trabajo de ejemplo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". +Este ejemplo de flujo de trabajo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". Este flujo de trabajo carga el archivo `results.sarif` ubicado en la raíz del repositorio. Para obtener más información acerca de cómo crear un archivo de flujo de trabajo, consulta la sección "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". @@ -77,7 +79,7 @@ jobs: Si generas tu archivo SARIF de terceros como parte de un flujo de trabajo de integración contínua (IC), puedes agregar la acción `upload-sarif` como un paso después de ejecutar tus pruebas de IC. Si aún no tienes un flujo de trabajo de IC, puedes crearlo utilizando una plantilla de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)". -Este flujo de trabajo de ejemplo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". +Este ejemplo de flujo de trabajo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". El flujo de trabajo muestra un ejemplo de ejecución de la herramienta de análisis estático ESLint como un paso en un flujo de trabajo. El paso `Run ESLint` ejecuta la herramienta ESLint y da como salida el archivo `results.sarif`. El flujo de trabajo entonces carga el archivo `results.sarif` a {% data variables.product.prodname_dotcom %} utilizando la acción `upload-sarif`. Para obtener más información acerca de cómo crear un archivo de flujo de trabajo, consulta la sección "[Introducción a Github Actions](/actions/learn-github-actions/introduction-to-github-actions)". @@ -108,7 +110,7 @@ jobs: sarif_file: results.sarif ``` -### Further reading +### Leer más - "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" - "[Visualizar tu historial de flujos de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md index 9a9d8c28ff..d6af8f475e 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md @@ -2,7 +2,7 @@ title: Utilizar el escaneo de código de CodeQL en tu sistema de IC existente shortTitle: Soporte de CodeQL para sistemas de IC intro: 'El {% data variables.product.prodname_codeql_runner %} te permite utilizar tu sistema de IC existente para ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}.' -mapTopic: verdadero +mapTopic: true product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' diff --git a/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md b/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md index 8310add832..f31d7b2d77 100644 --- a/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md +++ b/translations/es-ES/content/github/finding-talent-with-github-jobs/about-github-jobs.md @@ -30,6 +30,6 @@ Para ayudar a los candidatos a encontrar tu publicación del empleo, verifica ** Puedes usar Markdown para dar formato a tu publicación del empleo. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". -### Further reading +### Leer más - [Cómo funiona {% data variables.product.prodname_jobs %} ](https://jobs.github.com/faq) en {% data variables.product.prodname_jobs %} diff --git a/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md index 90aa71eacd..9d323b08d9 100644 --- a/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md @@ -1,6 +1,6 @@ --- -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. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +title: Acerca de GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} ofrece a sus clientes características de seguridad adicionales bajo una licencia de {% data variables.product.prodname_advanced_security %}. Estas características también se habilitan para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}.' versions: free-pro-team: '*' enterprise-server: '>=3.0' @@ -8,41 +8,41 @@ versions: ### Acerca de {% data variables.product.prodname_GH_advanced_security %} -{% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) +{% data variables.product.prodname_dotcom %} tiene muchas características que te ayudan a mejorar y mantener la calidad de tu código. Algunas de éstas se incluyen en todos los planes, por ejemplo: gráfica de dependencias y {% data variables.product.prodname_dependabot_alerts %}. Otras características de seguridad requieren una licencia para que la {% data variables.product.prodname_GH_advanced_security %} se ejecute en los repositorios independientemente de aquellos públicos en {% data variables.product.prodname_dotcom_the_website %}. (Esto es, los repositorios privados e internos en {% data variables.product.prodname_dotcom_the_website %}, y todos los repositorios en {% data variables.product.prodname_ghe_server %}.) -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +Para obtener un resumen de todas las características de seguridad, consulta la sección "[Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)". Para obtener más información sobre los requisitos de permisos para las acciones que se relacionan con las características de seguridad, consulta la sección "[Niveles de permiso de los repositorios para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)". -### About {% data variables.product.prodname_advanced_security %} features +### Acerca de las características de {% data variables.product.prodname_advanced_security %} -A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: +Una licencia de {% data variables.product.prodname_GH_advanced_security %} proporciona las siguientes características adicionales: -- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. Para obtener más información, consulta la sección "[Acerca de{% 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 %}** - Busca vulnerabilidades de seguridad potenciales y errores dentro de tu código. Para obtener más información, consulta la sección "[Acerca de{% 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 %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)". +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detecta secretos, por ejemplo claves y tokens, que se han dado de alta en el repositorio. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)". {% if currentVersion == "free-pro-team@latest" %} -- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +- **Revisión de dependencias** - Muestra todo el impacto de los cambios a las dependencias y vee los detalles de las versiones vulnerables antes de que fusiones una solicitud de cambios. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% endif %} -For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." +Para obtener más información sobre las características de {% data variables.product.prodname_advanced_security %} que se encuentran en desarrollo, consulta la sección "[Plan de trabajo de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} +### Habilitar las características de {% data variables.product.prodname_advanced_security %} en {% data variables.product.prodname_ghe_server %} -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)." +El administrador de sitio debe habilitar la {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de que puedas utilizar estas características. Para obtener más información, consulta la sección "[Configurar las características de la Seguridad Avanzada](/admin/configuration/configuring-advanced-security-features)". -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](/github/setting-up-and-managing-organizations-and-teams/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)." -For information about purchasing a license for +Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas características a nivel de organización o de repositorio. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +Para obtener más información sobre cómo comprar una licencia para -{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% data variables.product.prodname_GH_advanced_security %}, contacta a {% data variables.contact.contact_enterprise_sales %}. {% endif %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} +### Habilitar las características de {% data variables.product.prodname_advanced_security %} en {% data variables.product.prodname_dotcom_the_website %} -For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. +Para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}, estas características se encuentran activas permanentemente y solo se inhabilitan si cambias la visibilidad del proyecto para que el código ya no sea público. -For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/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)." -For information about purchasing a license for +Para el resto de los repositorios, una vez que tengas una licencia, puedes habilitar e inhabilitar estas características a nivel de repositorio y de organización. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +Para obtener más información sobre cómo comprar una licencia para -{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% data variables.product.prodname_GH_advanced_security %}, contacta a {% data variables.contact.contact_enterprise_sales %}. {% endif %} diff --git a/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md b/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md index 7a882392fa..729297a47a 100644 --- a/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md +++ b/translations/es-ES/content/github/getting-started-with-github/access-permissions-on-github.md @@ -34,6 +34,6 @@ Los *propietarios de empresa* tienen máximo poder sobre la cuenta de la empresa {% endif %} -### Further reading +### Leer más - [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md b/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md index 12e3d5cac9..07220ec25a 100644 --- a/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md +++ b/translations/es-ES/content/github/getting-started-with-github/exploring-projects-on-github.md @@ -1,7 +1,7 @@ --- title: Explorar proyectos en GitHub intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /categories/stars/ - /categories/87/articles/ diff --git a/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md b/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md index 741502244a..b5bb4b5f31 100644 --- a/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md +++ b/translations/es-ES/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md @@ -83,8 +83,8 @@ Los estudiantes y maestros seguirán recibiendo todos los beneficios que reciben Si actualmente eres un cliente que paga por factura, contacta por correo electrónico a tu representante de ventas para recibir más detalles. Si no sabes quién es tu representante de ventas, contacta a tu gerente de facturación o propietario de cuenta. -### ¿Cómo va afectar esto a los usuarios y organizaciones que se encuentran en regiones donde se aplican las sanciones del gobierno de los EE.UU? government sanctions are applied? +### ¿Cómo va afectar esto a los usuarios y organizaciones que se encuentran en regiones donde se aplican las sanciones del gobierno de los EE.UU? -Due to U.S. Debido a los controles de comercio y restricciones legales, GitHub no puede proporcionar servicios para repositorios privados y servicios pagados a cuentas que se encuentren en las zonas sancionadas por los EE.UU. sanctioned regions. Sin embargo, GitHub ha preservado el acceso a los servicios gratuitos para repositorios públicos. Por favor lee sobre [GitHub y los Controles Comerciales](/github/site-policy/github-and-trade-controls) para obtener más información. +Debido a los controles de comercio y restricciones legales de los EE.UU. , GitHub no puede proporcionar servicios para repositorios privados y servicios pagados a cuentas que se encuentren en las zonas sancionadas por los EE.UU. Sin embargo, GitHub ha preservado el acceso a los servicios gratuitos para repositorios públicos. Por favor lee sobre [GitHub y los Controles Comerciales](/github/site-policy/github-and-trade-controls) para obtener más información. -GitHub seguirá fomentando, en conjunto con los reguladores de los EE.UU., el mejor acceso posible a los servicios colaborativos de código abierto para desarrolladores en regiones sancionadas, incluyendo repositorios privados gratuitos. Creemos que, el ofrecer estos servicios gratuitos, apoya la política externa de los EE.UU. de fomentar el flujo libre de información y libertad de expresión en estas regiones. . Consideramos que ofrecer estos servicios gratuitos apoya a EE. UU. foreign policy of encouraging the free flow of information and free speech in those regions. +GitHub seguirá fomentando, en conjunto con los reguladores de los EE.UU. , por contar con el mejor acceso posible a los servicios colaborativos gratuitos de código abierto para los desarrolladores en las regiones sancionadas, incluyendo repositorios privados gratuitos. Creemos que, el ofrecer estos servicios gratuitos, apoya la política externa de los EE.UU. para fomentar el flujo libre de información y libertad de expresión en estas regiones. diff --git a/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md index bafb09e6a9..27cf51f795 100644 --- a/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/es-ES/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -46,7 +46,7 @@ Para configurar tu propio espejo, puedes configurar [un gancho posrecepción](ht Puedes buscar repositorios en función de si tienen un espejo o no. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-a-mirror)". -### Further reading +### Leer más - "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" - "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" diff --git a/translations/es-ES/content/github/getting-started-with-github/following-people.md b/translations/es-ES/content/github/getting-started-with-github/following-people.md index 9a5b52f424..7c7b3eb60b 100644 --- a/translations/es-ES/content/github/getting-started-with-github/following-people.md +++ b/translations/es-ES/content/github/getting-started-with-github/following-people.md @@ -16,7 +16,7 @@ Cuando sigues a las personas, verás su actividad pública en la vista de activi Para dejar de seguir a alguien, visita su página de perfil y haz clic en **Dejar de seguir** debajo de su imagen de perfil. {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)" - "[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)" diff --git a/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md index 2d379f4308..697118294a 100644 --- a/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/es-ES/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ Para familiarizarte con Git, visita el [sitio oficial del proyecto Git](https:// {% endif %} -Adquiere más conocimientos con {% data variables.product.product_name %} a través de nuestros artículos de [seminario intensivo](/categories/bootcamp/). 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. 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. {% data reusables.support.ask-and-answer-forum %} #### Ramas, bifurcaciones y solicitudes de extracción -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 guías de referencia rápida acerca de la [línea de comando](https://hub.github.com) y de [guías de comprobación, hojas de referencia de {% data variables.product.prodname_dotcom %}, y mucho más](https://services.github.com/on-demand/resources). +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 %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). #### Ponte al día @@ -41,9 +39,9 @@ Nuestro {% data variables.product.prodname_dotcom %} [canal con guías y capacit ### Capacitación -#### Clases gratuitas +#### Free courses -{% data variables.product.product_name %} ofrece una serie de cursos de capacitación interactivos a pedido [on-demand training courses](https://services.github.com/on-demand/), entre otros, {% data variables.product.prodname_dotcom %} 101: [Introducción](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %} 102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop) y {% data variables.product.prodname_dotcom %} 103: [Línea de comando](https://services.github.com/on-demand/github-cli). +{% 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 %} @@ -51,7 +49,7 @@ Nuestro {% data variables.product.prodname_dotcom %} [canal con guías y capacit #### Capacitación para tu compañía -{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contáctanos](https://services.github.com/#contact) para que podamos responder tus preguntas relacionadas con la capacitación. +{% 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. ### Extras diff --git a/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md b/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md index cdea80d061..0a3f2c18af 100644 --- a/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/es-ES/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -Aprender todos los comandos de Git disponibles de una sola vez puede resultan una tarea intimidante. Mantén uno de nuestras [Hojas introductorias de Git](https://services.github.com/on-demand/resources/cheatsheets/) cerca para poder consultarla. El uso de Hojas introductorias de Git se encuentra disponible en distintos idiomas. Para obtener más información, consulta la [página de recursos en el sitio web GitHub Services](https://services.github.com/on-demand/resources/). +Aprender todos los comandos de Git disponibles de una sola vez puede resultan una tarea intimidante. Our cheat sheets provide a quick reference for the commands you'll use most often: see "[Git Cheat Sheets](https://training.github.com/)." The "Using Git" cheat sheet is available in several languages. Además, visita nuestra página de [recursos para el aprendizaje de Git y GitHub](/articles/git-and-github-learning-resources/), que tiene enlaces a guías, videos, y mucho más. diff --git a/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md b/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md index ac16c89117..c5c9db5e22 100644 --- a/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md @@ -26,29 +26,29 @@ Para obtener más información sobre las notificaciones de {% data variables.pro Para instalar {% data variables.product.prodname_mobile %} para Android o iOS, consulta la sección [{% data variables.product.prodname_mobile %}](https://github.com/mobile). -### Managing accounts +### Administrar cuentas -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 %}. +Puedes ingresar simultáneamente a la versión móvil con una cuenta de usuario en {% data variables.product.prodname_dotcom_the_website %} y otra en {% data variables.product.prodname_ghe_server %}. {% data reusables.mobile.push-notifications-on-ghes %} -{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. +{% data variables.product.prodname_mobile %} podría no funcionar en tu empresa si se te pide acceso a nuestra empresa a través de una VPN. #### Prerrequisitos -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 %}. +Debes instalar {% data variables.product.prodname_mobile %} 1.4 o posterior en tu dispositivo para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}. -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 "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." +Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. Para obtener más información, consulta las secciones "[Notas de lanzamiento](/enterprise-server/admin/release-notes)" y "[Administrar {% data variables.product.prodname_mobile %} para tu empresa](/admin/configuration/managing-github-for-mobile-for-your-enterprise)". -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 %}. +Durante el beta para {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, debes estar firmado con una cuenta de usuario en {% data variables.product.prodname_dotcom_the_website %}. -#### Adding, switching, or signing out of accounts +#### Agregar, cambiar o cerrar sesión en las cuentas -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. +Puedes ingresar en la versión móvil con una cuenta de usuario en {% data variables.product.product_location %}. En la parte inferior de la app, deja presionado {% octicon "person" aria-label="The person icon" %} **Perfil**, y luego pulsa sobre {% octicon "plus" aria-label="The plus icon" %} **Agregar Cuenta Empresarial**. Sige las indicaciones para iniciar sesión. -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. +Después de que ingreses en la versión móvil con una cuenta de usuario de {% data variables.product.product_location %}, puedes cambiar entre esa cuenta y la cuenta de {% data variables.product.prodname_dotcom_the_website %}. En la parte inferior de la app, deja presionado {% octicon "person" aria-label="The person icon" %} **Perfil**, y luego pulsa sobre la cuenta a la que quieras cambiar. -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**. +Si ya no necesitas acceso a los datos de tu cuenta de usuario en {% data variables.product.product_location %} desde {% data variables.product.prodname_mobile %}, puedes salir de la sesión de la cuenta. En la parte inferior de la app, deja presionado {% octicon "person" aria-label="The person icon" %} **Perfil**, desliza hacia la izquierda en la cuenta para salir de ella y luego pulsa en **Salir de sesión**. ### Idiomas compatibles para {% data variables.product.prodname_mobile %} @@ -57,7 +57,7 @@ If you no longer need to access data for your user account on {% data variables. - Inglés - Japonés - Portugués brasileño -- Simplified Chinese +- Chino simplificado - Español Si configuras el idioma en tu dispositivo para que sea uno de los compatibles, {% data variables.product.prodname_mobile %} estará predeterminadamente en este idioma. Puedes cambiar el idioma de {% data variables.product.prodname_mobile %} en el menú de **Ajustes** de {% data variables.product.prodname_mobile %}. diff --git a/translations/es-ES/content/github/getting-started-with-github/github-glossary.md b/translations/es-ES/content/github/getting-started-with-github/github-glossary.md index 1ae3e191da..0cfda03e6d 100644 --- a/translations/es-ES/content/github/getting-started-with-github/github-glossary.md +++ b/translations/es-ES/content/github/getting-started-with-github/github-glossary.md @@ -17,7 +17,7 @@ versions: --- -### Further reading +### Leer más - [El glosario oficial de Git](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) - [Referencia de Git](http://gitref.org/) diff --git a/translations/es-ES/content/github/getting-started-with-github/githubs-products.md b/translations/es-ES/content/github/getting-started-with-github/githubs-products.md index 86806372cf..5d9fb6ff37 100644 --- a/translations/es-ES/content/github/getting-started-with-github/githubs-products.md +++ b/translations/es-ES/content/github/getting-started-with-github/githubs-products.md @@ -1,6 +1,6 @@ --- title: Productos de GitHub -intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.' +intro: 'Un resumen de los productos de {% data variables.product.prodname_dotcom %} y de los planes de precios.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -85,6 +85,7 @@ Adicionalmente a las características disponibles con {% data variables.product. - {% data variables.contact.enterprise_support %}. Para obtener más información, consulta "{% data variables.product.prodname_ghe_cloud %} soporte" y "{% data variables.product.prodname_ghe_cloud %} Adenda." - 50,000 minutos de {% data variables.product.prodname_actions %} - 50GB de almacenamiento de {% data variables.product.prodname_registry %} +- Control de acceso para los sitios de {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}" - Un acuerdo de nivel de servicio del 99.9% de tiempo activo mensual - La opción de administrar de forma centralizada las políticas y la facturación de múltiples organizaciones {% data variables.product.prodname_dotcom_the_website %} con una cuenta de empresa. Para obtener más información, consulta la sección "Acerca de las cuentas empresariales." @@ -98,7 +99,7 @@ Para obtener más información acerca de hospedar tu propia instancia de [{% dat - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %} +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. 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)".{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". {% endif %} - [{% data variables.product.prodname_learning %} para organizaciones](https://lab.github.com/organizations) -For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}. +Para obtener más información sobre cómo registrarse para {% data variables.product.prodname_ghe_one %}, contacta a {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md index 93afec0bba..1eabfde247 100644 --- a/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -76,7 +76,8 @@ Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror] | control shift p o comando shift p | Alterna entre las pestañas de comentarios **Write** (Escribir) y **Preview** (Vista previa) | | 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 la sección "[Acerca de las respuestas guardadas](/articles/about-saved-replies)".{% if currentVersion == "free-pro-team@latest" %} -| 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 %} +| 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)". | ### Listas de propuestas y solicitudes de extracción @@ -111,7 +112,8 @@ Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror] | 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 cambios presionando `alt` y dando clic en **Mostrar desactualizados** U **Ocultar.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} desactualizados** | -| 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 %} +| 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 %} ### Tableros de proyecto @@ -159,10 +161,10 @@ Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror] | 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 | Go to the workflow file | -| shift + t or T | Toggle timestamps in logs | -| shift + f or F | Toggle fullscreen logs | -| esc | Exit fullscreen logs | +| 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 | Salir de las bitácoras de pantalla completa | {% endif %} @@ -183,7 +185,7 @@ Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror] | shift + m | Silencia el hilo | {% endif %} -### Network graph +### Gráfica de Red | Atajo del teclado | Descripción | | ------------------------------------------- | -------------------------------- | diff --git a/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md b/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md index 08c5c88efe..5614b2a5a7 100644 --- a/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md +++ b/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md @@ -1,7 +1,7 @@ --- title: Obtener información sobre GitHub intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/learning-about-github versions: diff --git a/translations/es-ES/content/github/getting-started-with-github/quickstart.md b/translations/es-ES/content/github/getting-started-with-github/quickstart.md index 178b837936..2a26d72cf7 100644 --- a/translations/es-ES/content/github/getting-started-with-github/quickstart.md +++ b/translations/es-ES/content/github/getting-started-with-github/quickstart.md @@ -1,7 +1,7 @@ --- title: Inicio Rápido intro: 'Inicia rápidamente las tareas comunes en {% data variables.product.prodname_dotcom %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md b/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md index 8153d59dc0..8f7db4ea7f 100644 --- a/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md +++ b/translations/es-ES/content/github/getting-started-with-github/saving-repositories-with-stars.md @@ -48,6 +48,6 @@ En el lateral derecho de la página, puedes filtrar tu lista de repositorios con ![Ver las estrellas de tus amigos](/assets/images/help/stars/stars_jump_to_a_friend.png) -### Further reading +### Leer más - "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md index aef4cfd77b..02669d848b 100644 --- a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -55,6 +55,6 @@ El bajar de categoría a {% data variables.product.prodname_free_team %} en orga 5. Debajo de "{% data variables.product.prodname_ghe_cloud %} Free Trial" (Prueba gratis de {% data variables.product.prodname_ghe_cloud %}), haz clic en **Buy Enterprise** (Comprar empresa) o **Downgrade to Team** (Bajar de categoría a equipo). ![Botones Comprar Enterprise y Bajar de categoría a Team](/assets/images/help/organizations/finish-trial-buttons.png) 6. Sigue las indicaciones para ingresar tu método de pago, a continuación haz clic en **Enviar**. -### Further reading +### Leer más - "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" diff --git a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md index ba4ee7122c..101358e205 100644 --- a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md @@ -56,6 +56,6 @@ Puedes subir la categoría a licencias totales en el [{% data variables.product. Si no has subido la categoría para el último día de tu prueba, recibirás un correo electrónico notificando que tu prueba ha terminado. Si necesitas más tiempo para evaluar {% data variables.product.prodname_enterprise %}, contacta a {% data variables.contact.contact_enterprise_sales %} para solicitar una extensión. -### Further reading +### Leer más - "[Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)" diff --git a/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md b/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md index fde568c151..b77ad9cf46 100644 --- a/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md +++ b/translations/es-ES/content/github/getting-started-with-github/signing-up-for-github.md @@ -1,7 +1,7 @@ --- title: Registrarse en GitHub intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/signing-up-for-github versions: diff --git a/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md b/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md index e9c1d05d88..f28b42b213 100644 --- a/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md +++ b/translations/es-ES/content/github/getting-started-with-github/types-of-github-accounts.md @@ -71,7 +71,7 @@ Con las cuentas de empresa, puedes administrar de forma centralizada la polític {% endif %} -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %}- "[Inicia sesión para crear una cuenta nueva de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" - "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)"{% endif %} diff --git a/translations/es-ES/content/github/getting-started-with-github/using-github.md b/translations/es-ES/content/github/getting-started-with-github/using-github.md index 7d0b9c89ba..96f2794bb1 100644 --- a/translations/es-ES/content/github/getting-started-with-github/using-github.md +++ b/translations/es-ES/content/github/getting-started-with-github/using-github.md @@ -1,7 +1,7 @@ --- title: Utilizar GitHub intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/using-github versions: diff --git a/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md b/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md index 9fc08551dc..b5d4caac47 100644 --- a/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md +++ b/translations/es-ES/content/github/getting-started-with-github/verifying-your-email-address.md @@ -59,6 +59,6 @@ Si haces clic en el enlace del correo electrónico de confirmación dentro de la 3. {% data variables.product.signin_link %} a tu cuenta personal {% data variables.product.prodname_dotcom %}. 4. Haz clic en el enlace de verificación del correo electrónico que te enviamos. -### Further reading +### Leer más - "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md index 62c9d827ac..8e1a45baa8 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md @@ -20,7 +20,7 @@ Durante una importación, dependiendo del sistema de control de la versión del | Mover archivos grandes a [Large File Storage de Git](/articles/about-git-large-file-storage) | **X** | **X** | **X** | | | Eliminar archivos grandes de tu repositorio | **X** | **X** | **X** | | -### Further reading +### Leer más - "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" - "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 0e9dc8d59c..5f8ea1a42e 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,7 +45,7 @@ versions: 7. En la parte superior de la página de Configuración rápida del repositorio de {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. En Terminal, [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -83,7 +83,7 @@ versions: 7. En la parte superior de la página de Configuración rápida del repositorio de {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. En la indicación Command (Comando), [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -121,7 +121,7 @@ versions: 7. En la parte superior de la página de Configuración rápida del repositorio de {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. En Terminal, [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -134,6 +134,6 @@ versions: {% endlinux %} -### Further reading +### Leer más - [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md index 872cf0631f..5c9dc1db18 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-a-repository-with-github-importer.md @@ -31,6 +31,6 @@ Si quieres hacer coincidir las confirmaciones de tu repositorio con las cuentas Recibirás un correo electrónico cuando se haya importado todo el repositorio. -### Further reading +### Leer más - "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md index 0d32b3d823..e02c721991 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github.md @@ -7,7 +7,7 @@ redirect_from: - /articles/importing-an-external-git-repo/ - /articles/importing-your-project-to-github/ - /articles/importing-source-code-to-github -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md index 4ffa5292f8..1cef94e8fb 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md @@ -47,7 +47,7 @@ Recomendamos estas herramientas para mover cambios entre Team Foundation Server {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Acerca del Importador GitHub](/articles/about-github-importer)" - "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md b/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md index 442c890042..1773159b7b 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/support-for-subversion-clients.md @@ -125,6 +125,6 @@ $ svn propget git-commit --revprop -r HEAD https://github.com/user/ Con este SHA de confirmación, puedes, por ejemplo, consultar la correspondiente confirmación Git en GitHub. -### Further reading +### Leer más * "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md index 850dc986e7..81837e381b 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer.md @@ -31,7 +31,7 @@ Si la dirección de correo electrónico del autor no está asociada a su cuenta Si el autor no tiene una cuenta de GitHub, el Importador GitHub atribuirá sus confirmaciones a la dirección de correo electrónico asociada a las confirmaciones. -### Further reading +### Leer más - "[Acerca del Importador GitHub](/articles/about-github-importer)" - "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md b/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md index e2836ba217..c69375aa29 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md @@ -59,7 +59,7 @@ SVN está configurado para suponer que el historial de un proyecto nunca cambia. {% endtip %} -### Further reading +### Leer más - "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)" - ["Branching and Merging" del libro _Git SCM_](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging) diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md b/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md index cdf2466f61..30540ed45a 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github.md @@ -1,7 +1,7 @@ --- title: Trabajar con Subversion en GitHub intro: Puedes usar clientes de Subversion y algunos flujos de trabajo y propiedades de Subversion con GitHub. -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/working-with-subversion-on-github versions: diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md b/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md index 027acd3126..85dc64ea8a 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/3d-file-viewer.md @@ -24,7 +24,7 @@ Cuando miras una confirmación de cambios o un conjunto de cambios que incluyen Por defecto, obtendrás una vista donde todo lo que no ha cambiado está en el esquema de página. Las adiciones aparecen en verde y las partes eliminadas aparecen en rojo. -![wireframe](/assets/images/help/repository/stl_wireframe.png) +![esquema de página](/assets/images/help/repository/stl_wireframe.png) También puedes seleccionar la opción **Control deslizante de la revisión**, que te permite usar un control deslizante en la parte superior del archivo para cambiar entre las revisiones actuales y las anteriores. diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md index f978a50694..2e4de5fbd9 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md @@ -37,7 +37,7 @@ versions: ``` {% data reusables.git.git-push %} -### Further reading +### Leer más - "[Crear archivos nuevos](/articles/creating-new-files)" - [Agregar un proyecto existente a GitHub mediante la línea de comando](/articles/adding-an-existing-project-to-github-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md b/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md index 8c39c6a6f3..4ede0f83ef 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/creating-new-files.md @@ -27,7 +27,7 @@ Cuando crees un archivo en {% data variables.product.product_name %}, ten en cue {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -### Further reading +### Leer más - "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)" - [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md index a0e1589a6a..984acfc099 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -1,6 +1,6 @@ --- -title: Deleting files in a repository -intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +title: Borrar los archivos en un repositorio +intro: 'Puedes borrar un archivo individual{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} o un directorio completo{% endif %} en tu repositorio de {% data variables.product.product_name %}.' redirect_from: - /articles/deleting-files - /github/managing-files-in-a-repository/deleting-files @@ -9,18 +9,18 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +permissions: Las personas con permisos de escritura pueden borrar los archivos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} o directorios{% endif %} de un repositorio. --- -### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion +### Acerca del borrado de archivos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} y directorios{% endif %} -You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. +Puedes borrar un archivo individual en tu repositorio{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} o un directorio completo, incluyendo los archivos de dicho directorio{% endif %}. -If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." +Si borras un archivo{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} o directorio{% endif %} en un repositorio en el que no tengas permisos de escritura, bifurcaremos el proyecto a tu cuenta de usuario y te ayudaremos a enviar una solicitud de cambios al repositorio original después de que confirmas tu cambio. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." -If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. Para obtener más información, consulta "[Eliminar datos confidenciales de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". +Si el archivo{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} o directorio{% endif %} que borraste contiene datos sensibles, éstos aún estarán disponibles en el historial de Git del repositorio. Para eliminar el archivo por completo de {% data variables.product.product_name %}, debes eliminar el archivo del historial de tu repositorio. Para obtener más información, consulta "[Eliminar datos confidenciales de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". -### Deleting a file +### Borrar un archivo 1. Dirígete al archivo que deseas eliminar de tu repositorio. 2. En la parte superior del archivo, da clic en @@ -31,11 +31,11 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_ {% data reusables.files.propose_file_change %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Deleting a directory +### Borrar un directorio -1. Browse to the directory in your repository that you want to delete. -1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) -1. Review the files you will delete. +1. Navega hasta el directorio que deseas borrar en tu repositorio. +1. En la esquina superior derecha, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Borrar directorio**. ![Botón para borrar un directorio](/assets/images/help/repository/delete-directory-button.png) +1. Revisa los archivos que borrarás. {% 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/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md index 7b34393d52..d11a6bcaf0 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-another-users-repository.md @@ -21,6 +21,6 @@ versions: 7. Escribe un título y una descripción para tu solicitud de extracción. ![Página de descripción de la solicitud de extracción](/assets/images/help/pull_requests/pullrequest-description.png) 8. Haz clic en **Create Pull Request** (Crear solicitud de extracción). ![Botón Solicitud de extracción](/assets/images/help/pull_requests/pullrequest-send.png) -### Further reading +### Leer más * "[Editar archivos en un repositorio](/articles/editing-files-in-your-repository)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md index 5e6520ae68..47f956fdd0 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/editing-files-in-your-repository.md @@ -31,6 +31,6 @@ versions: {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -### Further reading +### Leer más * "[Editar archivos en el repositorio de otro usuario](/articles/editing-files-in-another-user-s-repository)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md b/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md index c39a9a0221..383b092053 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md @@ -47,6 +47,6 @@ Buscar de manera manual el SHA de confirmación es muy poco práctico. No obstan Puedes crear un enlace permanente a una línea específica o a un rango de líneas de código en una versión específica de un archivo o de una solicitud de extracción. Para obtener más información, consulta "[Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)". -### Further reading +### Leer más - "[Archivar un repositorio de GitHub](/articles/archiving-a-github-repository)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md index d82bfea379..65a90dfa3e 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-on-github.md @@ -1,7 +1,7 @@ --- title: Administrar archivos en GitHub intro: 'En {% data variables.product.product_name %}, puedes crear, editar, mover y eliminar archivos en un repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-files-on-github versions: diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md index bba985f058..c076c2ce31 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md @@ -1,7 +1,7 @@ --- title: Administrar archivos utilizando la línea de comando intro: 'Utilizando la línea de comando, puedes agregar, renombrar y mover archivos en un repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-files-using-the-command-line versions: diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md index 679ca90635..9e30344799 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line.md @@ -56,7 +56,7 @@ Muchos archivos pueden [moverse directamente en {% data variables.product.produc ``` {% data reusables.git.git-push %} -### Further reading +### Leer más - "[Renombrar un archivo utilizando la línea de comando](/articles/renaming-a-file-using-the-command-line)" - [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md index f3961f3661..4043017d65 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### Acerca de la navegación de código en {% data variables.product.prodname_dotcom %} -Las funciones del código de navegación usan la biblioteca de código abierto [semántica](https://github.com/github/semantic). Los siguientes idiomas son compatibles: +Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). Los siguientes idiomas son compatibles: - C# - CodeQL - Go @@ -38,5 +38,5 @@ Puedes encontrar todas las referencias para una función o método dentro del mi ![Pestaña Find all references (Buscar todas las referencias)](/assets/images/help/repository/find-all-references-tab.png) -### Further reading +### Leer más - "[Buscar código](/github/searching-for-information-on-github/searching-code)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md b/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md index d7b1fa8720..7fd20565a5 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/renaming-a-file-using-the-command-line.md @@ -37,6 +37,6 @@ Muchos archivos se pueden [renombrar directamente en {% data variables.product.p ``` {% data reusables.git.git-push %} -### Further reading +### Leer más - "[Mover un archivo a una ubicación nueva mediante la línea de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)" - [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md index 3a86865725..15c051910a 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md @@ -18,7 +18,7 @@ Puedes generar un enlace a una fila particular haciendo clic en el número de fi ### Buscar datos -Si quieres encontrar un valor determinado en tu conjunto de datos, puedes comenzar escribiendo en la barra de búsqueda directamente arriba del archivo. The rows will filter automatically: +Si quieres encontrar un valor determinado en tu conjunto de datos, puedes comenzar escribiendo en la barra de búsqueda directamente arriba del archivo. Las filas se filtrarán automáticamente: ![Buscar valores](/assets/images/help/repository/searching_csvs.gif) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md index 6e292a3a6c..e15655c99c 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github.md @@ -24,7 +24,7 @@ Si tienes problemas para representar los archivos notebook Jupyter en HTML está $ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb ``` -### Further reading +### Leer más - [Repositorio GitHub de notebook Jupyter](https://github.com/jupyter/jupyter_notebook) - [Galería de notebooks Jupyter](https://github.com/jupyter/jupyter/wiki/A-gallery-of-interesting-Jupyter-Notebooks) diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md index 04afb106f5..c9c017e97f 100644 --- a/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md +++ b/translations/es-ES/content/github/managing-files-in-a-repository/working-with-non-code-files.md @@ -1,7 +1,7 @@ --- title: Trabajar con archivos sin código intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /categories/89/articles/ - /articles/working-with-non-code-files diff --git a/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md index e1b42b0c99..ec860d5483 100644 --- a/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md +++ b/translations/es-ES/content/github/managing-large-files/about-git-large-file-storage.md @@ -50,6 +50,6 @@ Hace un seguimiento de la `version` de {% data variables.large_files.product_nam {% endnote %} -### Further reading +### Leer más - "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index a9d10f7402..d04a513298 100644 --- a/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/es-ES/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -40,7 +40,7 @@ Si utilizas más de {% data variables.large_files.initial_storage_quota %} de al Si usas más de {% data variables.large_files.initial_bandwidth_quota %} de ancho de banda por mes sin comprar un paquete de datos, el soporte de {% data variables.large_files.product_name_short %} se desactiva en tu cuenta hasta el próximo mes. -### Further reading +### Leer más - "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" - "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md index e6a352c510..e993c54457 100644 --- a/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md +++ b/translations/es-ES/content/github/managing-large-files/collaboration-with-git-large-file-storage.md @@ -38,6 +38,6 @@ Puedes subir {% data variables.large_files.product_name_short %} objetos a las b {% endif %} -### Further reading +### Leer más - "[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)" diff --git a/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md index 79c36fb386..fd7684062c 100644 --- a/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/es-ES/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -57,7 +57,7 @@ Si hay archivos existentes en tu repositorio con los que te gustaría usar {% da > 64.74 MB / 81.04 MB 79.21 % 3s ``` -### Further reading +### Leer más - "[Colaboraciones con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - "[Administrar 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)"{% endif %} diff --git a/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md index 959d37d5b9..7712bff324 100644 --- a/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md +++ b/translations/es-ES/content/github/managing-large-files/installing-git-large-file-storage.md @@ -109,6 +109,6 @@ versions: {% endlinux %} -### Further reading +### Leer más - "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md index eaa8a44ac4..c10a907c74 100644 --- a/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md +++ b/translations/es-ES/content/github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md @@ -22,7 +22,7 @@ Después de instalar {% data variables.large_files.product_name_short %} y confi 1. Elimina el archivo del historial del repositorio de Git utilizando el comando `filter-branch` o BFG Repo-Cleaner. Para obtener información detallada sobre sus usos, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". 2. Configura el rastreo para tu archivo y súbelo a {% data variables.large_files.product_name_short %}. Para obtener más información sobre este procedimiento, consulta "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)." -### Further reading +### Leer más - "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" - "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md index 4389b8002c..b60efb6855 100644 --- a/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md +++ b/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md @@ -46,7 +46,7 @@ Para eliminar los objetos de {% data variables.large_files.product_name_short %} {% endnote %} -### Further reading +### Leer más - "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" - "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/es-ES/content/github/managing-large-files/versioning-large-files.md b/translations/es-ES/content/github/managing-large-files/versioning-large-files.md index 0fb017ea41..56975152c8 100644 --- a/translations/es-ES/content/github/managing-large-files/versioning-large-files.md +++ b/translations/es-ES/content/github/managing-large-files/versioning-large-files.md @@ -1,7 +1,7 @@ --- title: Control de versiones de archivos grandes intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/versioning-large-files versions: diff --git a/translations/es-ES/content/github/managing-large-files/working-with-large-files.md b/translations/es-ES/content/github/managing-large-files/working-with-large-files.md index afe4bf5a85..5f9563241c 100644 --- a/translations/es-ES/content/github/managing-large-files/working-with-large-files.md +++ b/translations/es-ES/content/github/managing-large-files/working-with-large-files.md @@ -1,7 +1,7 @@ --- title: Trabajar con archivos de gran tamaño intro: 'Un repositorio Git contiene cada versión de cada archivo. Pero para algunos tipos de archivos, esto no es práctico. Las revisiones múltiples de archivos de gran tamaño incrementan los tiempos de clonación y extracción para otros usuarios de un repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/working-with-large-files versions: diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 86d5eaaf8c..3fc6ba15b3 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -47,6 +47,8 @@ Para encontrar una lista de ecosistemas para las cuales {% data variables.produc 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +Para obtener más información sobre los requisitos de permisos para las acciones que se relacionan con las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Niveles de permiso del repositorio para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-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)". {% endif %} @@ -88,7 +90,7 @@ Enviamos alertas de seguridad para las personas con permisos de administrador en {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obtener más información, consulta la sección "[Elegir el método de entrega para tus notificaciones](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)".{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".{% endif %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" - "[Ver y actualizar las dependencias vulnerables en tu repositorio](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index f192d428f8..eb940075ce 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -16,7 +16,7 @@ Las {% data variables.product.prodname_dependabot_security_updates %} te facilit {% note %} -**Note** +**Nota** 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)". @@ -34,6 +34,6 @@ Cuando fusionas una solicitud de cambios que contiene una actualización de segu Las {% data variables.product.prodname_dependabot_security_updates %} podrían incuir puntuaciones de compatibilidad para hacerte saber si el actualizar una vulnerabilidad 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 notifications for {% data variables.product.prodname_dependabot %} security updates +### Acerca de las notificaciones para las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} -You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. 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)". \ No newline at end of file +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)". \ No newline at end of file diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md index 9b8bc0a5a3..4e2ad3658e 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory.md @@ -27,7 +27,7 @@ Los colaboradores tienen permisos de escritura para el aviso de seguridad. Para 5. En la parte derecha de la página, debajo de "Colaboradores", teclea el nombre de usuario o equipo que quieras añadir a la asesoría de seguridad.![Campo para escribir el nombre del equipo o el usuario](/assets/images/help/security/add-collaborator-field.png) 6. Da clic en **Agregar**. ![Botón Add (Agregar)](/assets/images/help/security/security-advisory-add-collaborator-button.png) -### Further reading +### Leer más - "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" - "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md index cf3b2f7985..6f4a25def3 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository.md @@ -35,7 +35,7 @@ Después de que alguien reporte una vulnerabilidad de seguridad en tu proyecto, {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -### Further reading +### Leer más - [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" - "[Configurar tu proyecto para contribuciones positivas](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index e5705ebe34..5f4d7dd049 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -19,9 +19,9 @@ La {% data variables.product.prodname_advisory_database %} contiene una lista se Cada asesoría de seguridad contiene información acerca de la vulnerabilidad, incluyendo la descripción, severidad, paquete afectado, paquete de ecosistema, versiones afectadas y versiones parchadas, impacto, e información opcional tal como referencias, soluciones alternas, y créditos. Adicionalmente, las asesorías de la National Vulnerability Database contiene un enlace al registro de CVE, en donde puedes leer más sobre los detalles de la vulnerabilidad, su puntuación de CVSS y su nivel de severidad cualitativo. Para obtener más información, consulta la "[National Vulnerability Database](https://nvd.nist.gov/)" del Instituto Nacional de Estándares y Tecnología. El nivel de gravedad es uno de cuatro niveles posibles definidos en el [Sistema de clasificación de vulnerabilidades comunes (CVSS), Sección 2.12](https://www.first.org/cvss/specification-document): -- Low -- Moderate -- High +- Bajo +- Moderado +- Alto - Crítico La {% data variables.product.prodname_advisory_database %} utiliza estándares de CVSS versión 3.0 y los niveles de CVSS descritos anteriormente. {% data variables.product.product_name %} no publica los puntajes de CVSS. @@ -60,6 +60,6 @@ Puedes buscar coincidencias exactas en la base de datos y utilizar calificadores | `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) mostrará únicamente las asesorías creadas en esta fecha. | | `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) mostrará únicamente asesorías actualizadas en esta fecha. | -### Further reading +### Leer más - [Definición de MITRE de "vulnerabilidad"](https://cve.mitre.org/about/terminology.html#vulnerability) diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md index 3f11765c5e..d2f94c326a 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md @@ -69,7 +69,7 @@ Antes de que puedas fusionar cambios en una asesoría de seguridad, cada solicit Después de que fusiones cambios en una asesoría de seguridad, puedes publicarla para alertar a tu comunidad sobre las vulnerabilidades de seguridad en versiones previas de tu proyecto. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". -### Further reading +### Leer más - "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" - "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index 5cd5d1734e..fcfd604eb8 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -42,20 +42,20 @@ Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sab ### Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios -You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). +Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual (ver a continuación). 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](/github/setting-up-and-managing-organizations-and-teams/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)". -#### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository +#### Habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -1. Under "Configure security and analysis features", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**. !["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) +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) -### Further reading +### Leer más - "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/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)". diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index 7f46458ff3..b1097a9342 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -1,58 +1,56 @@ --- -title: Configurar las notificaciones para las dependencias vulnerables -shortTitle: Configurar notificaciones -intro: 'Optimiza la forma en la que recibes las notificaciones sobre las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}.' +title: Configuring notifications for vulnerable dependencies +shortTitle: Configuring notifications +intro: 'Optimize how you receive notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.' versions: free-pro-team: '*' enterprise-server: '>=2.21' --- -### Acerca de las notificaciones para las dependencias vulnerables +### About notifications for vulnerable dependencies -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}Cuando el {% data variables.product.prodname_dependabot %} detecta dependencias vulnerables en tus repositorios, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad del repositorio. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con sus preferencias de notificación.{% else %}Cuando{% data variables.product.product_name %} detecta dependencias vulnerables en tus repositorios, manda alertas de seguridad.{% endif %}{% if currentVersion == "free-pro-team@latest" %} El {% data variables.product.prodname_dependabot %} se habilita predeterminadamente en todos los repositorios públicos. En el caso de las {% data variables.product.prodname_dependabot_alerts %}, predeterminadamente, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico, agrupadas por la vulnerabilidad específica. -{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. +{% endif %} -{% if currentVersion == "free-pro-team@latest" %}Si eres un propietario de organización, puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios en tu organización con un clic. También puedes configurar si se habilitará o inhabilitará la detección de dependencias vulnerables para los repositorios recién creados. Para obtener más información, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)". +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} -Tu administrador de sitio necesita habilitar las alertas de seguridad para las dependencias vulnerables de -{% data variables.product.product_location %} antes de que puedas utilizar la característica. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} +Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %} -Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para notificaciones en tu empresa, recibirás -{% if currentVersion ver_gt "enterprise-server@2.21" %}Alertas de {% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} por correo electrónico.{% endif %} +By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %} -{% if currentVersion ver_gt "enterprise-server@2.21" %}Los administradores de sitio también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} -{% if currentVersion ver_lt "enterprise-server@2.22" %}Los administradores de sitio también pueden habilitar las alertas de seguridad sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las alertas de seguridad para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} +{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} -### Configurar notificaciones para las {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} +### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} -Puedes configurar los ajustes de notificaciones para ti mismo o para tu organización desde el menú desplegable de administrar notificaciones {% octicon "bell" aria-label="The notifications bell" %} que se muestra en la parte superior de cada página. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". +You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} {% data reusables.notifications.vulnerable-dependency-notification-options %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - ![Opciones de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/notifications-v2/dependabot-alerts-options.png) + ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png) {% else %} - ![Opciones de alertas de seguridad](/assets/images/help/notifications-v2/security-alerts-options.png) + ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png) {% endif %} {% note %} -**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. 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)". +**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." {% endnote %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} Para obtener más información, consulta la sección"[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}".{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %} -### Cómo reducir el ruido de las notificaciones para las dependencias vulnerables +### How to reduce the noise from notifications for vulnerable dependencies -Si te preocupa recibir demasiadas notificaciones para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}las {% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %}, te recomendamos que decidas ingresar en el resúmen semanal por correo electrónico, o apagar las notificaciones mientras aún tienes {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} las {% else %}alertas de seguridad{% endif %} de las {% data variables.product.prodname_dependabot_alerts %} habilitadas. Aún puedes navegar para ver tus {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} en la pestaña de seguridad de tu repositorio.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %} +If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} ### Further reading -- "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" -- "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" +- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" +- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md index aa5db66eee..3b7a8b0633 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/editing-a-security-advisory.md @@ -28,6 +28,6 @@ Si alguien acepta el crédito, el nombre de usuario de la persona aparecerá en 9. Da clic en **Actualizar asesoría de seguridad**". ![Botón Add (Agregar)](/assets/images/help/security/update-advisory-button.png) 10. Las personas listadas en la sección de "Créditos" recibirán una notificación web o por correo electrónico que los invita a aceptar el crédito. Si la persona acepta, su nombre de usuario estará visible al público una vez que la asesoría de seguridad se publique. -### Further reading +### Leer más - "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md index 18adffef97..70a16e168b 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project.md @@ -1,7 +1,7 @@ --- title: Administrar las vulnerabilidades de seguridad en tu proyecto intro: 'Puedes descubrir, discutir, reparar y divulgar vulnerabilidades de seguridad en tus repositorios.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-security-vulnerabilities-in-your-project versions: diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md index 5247a91ffa..eb5e533a0c 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md @@ -1,7 +1,7 @@ --- title: Administrar vulnerabilidades en las dependencias de tus proyectos intro: 'Puedes rastrear las dependencias de tu repositorio y recibir{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% endif %}cuando {% data variables.product.product_name %} detecta dependencias vulnerables.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/updating-your-project-s-dependencies/ - /articles/updating-your-projects-dependencies/ diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md b/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md index dda4d6350d..e5fe1f8243 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/permission-levels-for-security-advisories.md @@ -26,7 +26,7 @@ versions: | Cerrar el borrador de la asesoría de seguridad | | X | | Publicar la asesoría de seguridad (consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)") | | X | -### Further reading +### Leer más - "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" - "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index 185394feb7..a1c1cc2bd2 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ Cuando publicas una asesoría de seguridad, notificas a tu comunidad acerca de l Antes de que publiques una asesoría de seguridad, puedes hacer una colaboración privada para arreglar la vulnerabilidad en una bifurcación privada. Para obtener más información, consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". +{% warning %} + +**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to. + +We recommend you take the following steps in these different situations: + +- If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready. +- If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication. +- If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue. + +{% endwarning %} + Cuando publicas un borrador de asesoría desde un repositorio público, todos pueden ver: - La versión actual de los datos de la asesoría. @@ -66,6 +78,6 @@ El publicar una asesoría de seguridad borra la bifurcación temporal privada pa {% data reusables.repositories.github-reviews-security-advisories %} -### Further reading +### Leer más - "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md index ad5638a9da..e70866ec80 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory.md @@ -18,7 +18,7 @@ Las personas con permisos administrativos en una asesoría de seguridad pueden e 5. En el lado derecho de la página, debajo de "Colaboradores", encuentra el nombre del usuario o equipo al que quieres eliminar de la asesoría de seguridad. ![Colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-collaborator.png) 6. Al lado del colaborador que deseas eliminar, haz clic en el icono **X**. ![Icono X para eliminar al colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-remove-collaborator-x.png) -### Further reading +### Leer más - "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" - "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index c8c86912cf..feba19b01d 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -78,15 +78,15 @@ La mejor forma de resolver este error es fusionar o cerrar algunas de las solici #### El {% data variables.product.prodname_dependabot %} no puede resolver tus archivos de dependencia -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 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`. -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. +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. -**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. 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)". +**Ú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)". ### Activar una solicitud de cambios del {% data variables.product.prodname_dependabot %} manualmente Si desbloqueas al {% data variables.product.prodname_dependabot %}, puedes activar manualmente un nuevo intento de crear una solicitud de cambios. - **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 %}**. -- **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**. +- **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**. diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md index f4837cbe6d..0834a57ac9 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -93,7 +93,7 @@ Cuando das clic para mostrar los detalles de la alerta puedes ver cuántas vulne **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. -### Further reading +### Leer más - "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/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)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 4e14d8cfd8..cb941d9d77 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -30,7 +30,7 @@ Puedes habilitar las alertas de seguridad automáticas para cualquier repositori 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, utiliza el menú desplegable de "Descartar" y da 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) -### Further reading +### Leer más - "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" - "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)" diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md b/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md index 68364d6830..62f0166eed 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/withdrawing-a-security-advisory.md @@ -7,6 +7,6 @@ versions: Si publicas una asesoría de seguridad por error, puedes retirarla contactando a {% data variables.contact.contact_support %}. -### Further reading +### Leer más - [Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory) diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index 7bc70494e0..8a970e376c 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -54,7 +54,7 @@ Para darte de baja de las conversaciones a las cuales estás suscrito automátic ### Personalizar notificaciones y suscripciones -You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. +Puedes elegir ver tus notificaciones a través de la bandeja de notificaciones en [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} y en la app de {% data variables.product.prodname_mobile %}{% endif %}, a través de tu correo electrónico o con cualquier combinación de estas opciones. Para personalizar los tipos de actualizaciones que deseas recibir y el lugar a donde quieras que se envíen, modifica tu configuración de notificaciones. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". @@ -93,7 +93,7 @@ También puedes clasificar varias notificaciones al mismo tiempo desde tu bandej ### Personalizar tu bandeja de entrada de notificaciones -To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. Por ejemplo, puedes crear un filtro personalizado para un proyecto de código abierto en el que contribuyes y únicamente ver notificaciones para el repositorio en el que se te mencione. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para ver más ejemplos de cómo personalizar tu flujo de trabajo de clasificaciones, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)". +Para enfocarte en un grupo de notificaciones en tu bandeja de entrada en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} o {% data variables.product.prodname_mobile %}{% endif %}, puedes crear filtros personalizados. Por ejemplo, puedes crear un filtro personalizado para un proyecto de código abierto en el que contribuyes y únicamente ver notificaciones para el repositorio en el que se te mencione. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para ver más ejemplos de cómo personalizar tu flujo de trabajo de clasificaciones, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)". ### Política de retención de notificaciones diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 7730050202..41b253879c 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -27,9 +27,9 @@ versions: Puedes recibir notificaciones de actividad en {% data variables.product.product_name %} en las siguientes ubicaciones. - - The notifications inbox in the {% data variables.product.product_name %} web interface{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} + - La bandeja de notificaciones en la interface web de {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - La bandeja de notificaciones en {% data variables.product.prodname_mobile %}, la cual sesincroniza con aquella de {% data variables.product.product_name %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} + - Un cliente de correo electrónico que utiliza una dirección de correo electrónico verificada, la cual también se sincroniza con la bandeja de notificaciones en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} y en {% data variables.product.prodname_mobile %}{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obtener más información, consulta la sección "[Escoger tu configuración de notificaciones](#choosing-your-notification-settings)". @@ -39,7 +39,7 @@ Puedes recibir notificaciones de actividad en {% data variables.product.product_ #### Beneficios de la bandeja de entrada de notificaciones -The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: +La bandeja de notificaciones en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} y en {% data variables.product.prodname_mobile %}{% endif %} incluye las opciones de clasificación que se diseñan específicamente para tu flujo de notificaciones de {% data variables.product.product_name %}, incluyendo opciones para: - Clasificar varias notificaciones al mismo tiempo. - Marcar las notificaciones como **Completadas** y eliminarlas de tu bandeja de entrada. Para ver todas tus notificaciones marcadas como **Completadas**, utiliza el query `is:done`. - Guardar una notificación para revisarla más tarde. Las notificaciones se resaltan en tu bandeja de entrada y se mantienen indefinidamente. Para ver todas tus notificaciones guardadas, utiliza el query `is:saved`. @@ -81,7 +81,7 @@ Puedes personalizar las notificaciones de un repositorio, por ejemplo, puedes el #### Participar en conversaciones Siempre que comentes en una conversación, o cuando alguien @menciona tu nombre de usuario, estarás _participando_ en una conversación. Predeterminadamente, estás suscrito automáticamente a una conversación cuando participas en ella. Puedes desuscribirte manualmente de una conversación en la que hayas participado si das clic en **Desuscribir** en el informe de problemas o solicitud de extracción, o a través de la opción de **Desuscribir** en la bandeja de notificaciones. -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %}. +Para las conversaciones que estás observando o en las que estás participando, puedes elegir si quieres recibir notificaciones por correo electrónico o mediante la bandeja de notificaciones en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} y en {% data variables.product.prodname_mobile %}{% endif %}. ![Opciones de notificación para observar y participar](/assets/images/help/notifications-v2/participating-and-watching-options.png) @@ -89,7 +89,7 @@ Por ejemplo: - Si no quieres que se te envíen notificaciones a tu correo electrónico, deselecciona **email** de la opción en participar y seguir de cerca las notificaciones. - Si quieres recibir notificaciones por correo electrónico cuando hayas participado en una conversación, entonces puedes seleccionar **email** debajo de "Participando". -If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}, then your notifications inbox will not have any updates. +Si no habilitas las notificaciones web para los lugares que observas o en los que participas{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} y las móviles{% endif %}, entonces tu bandeja de notificaciones no tendrá ninguna actualización. ### Personalizar tus notificaciones de correo electrónico @@ -133,7 +133,8 @@ Las notificaciones por correo electrónico de {% data variables.product.product_ | campo `Para` | Este campo se conecta directamente al hilo.{% if currentVersion != "github-ae@latest" %} Si respondes al correo electrónico, agregarás un comentario nuevo a la conversación.{% endif %} | dirección `Cc` | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son:
    • `assign`: Te asignaron a una propuesta o solicitud de extracción.
    • `author`: Creaste una propuesta o solicitud de extracción.
    • `comment`: Comentaste una propuesta o solicitud de extracción.
    • `manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.
    • `mention`: Te mencionaron en una propuesta o solicitud de extracción.
    • `push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.
    • `review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.
      • {% if currentVersion != "github-ae@latest" %}
    • `security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.
      • {% endif %}
    • `state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.
    • `subscribed`: Hubo una actualización en un repositorio que estás mirando.
    • `team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.
    • `your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.
    | | Campo `mailing list` (lista de correos) | Este campo identifica el nombre del repositorio y su propietario. El formato de esta dirección siempre es `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| Campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    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)". |{% endif %} +| Campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    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)". +{% endif %} ### Escoger tu configuración de notificaciones diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 0862dd1995..cfcbf0fa0a 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: Administrar las notificaciones en tu bandeja de entrada -intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' +intro: 'Utiliza tu bandeja de entrada para clasificar y sincronizar tus notificaciones rápidamente a través de tu correo electrónico{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} y dispositivo móvil{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -90,16 +90,16 @@ Los filtros personalizados no son compatibles actualmente con: ### Queries compatibles para filtros personalizados -These are the types of filters that you can use: +Estos son los tipos de filtro que puedes utilizar: - Filtrar por repositorio con `repo:` - Filtrar por tipo de debate con `is:` - - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} - - Filter by notification author with `author:` - - Filter by organization with `org:`{% endif %} + - Filtrar por razón de la notificación con `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filtrar por autor de la notificación con `author:` + - Filtrar por organización con `org:`{% endif %} -#### Supported `repo:` queries +#### Consultas de `repo:` compatibles -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. +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. #### Queries de tipo `is:` compatibles @@ -148,38 +148,38 @@ Para filtrar las notificaciones de acuerdo con la razón por la cual recibiste u | `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. | {% if currentVersion == "free-pro-team@latest" %} -#### Supported `author:` queries +#### Consultas de `author:` compatibles -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`. +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`. -#### Supported `org:` queries +#### Consultas de `org:` compatibles -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. +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. -For example, to see notifications from the octo-org organization, use `org:octo-org`. +Por ejemplo, para ver las notificaciones de la organización octo-org, utiliza `org:octo-org`. {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -### {% data variables.product.prodname_dependabot %} custom filters +### Filtros personalizados del {% data variables.product.prodname_dependabot %} {% if currentVersion == "free-pro-team@latest" %} -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. -For more information about +Si utilizas +al {% data variables.product.prodname_dependabot %} para mantener actualizadas tus dependencias, puedes usar 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. +Para obtener más información sobre -{% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +el {% data variables.product.prodname_dependabot %}, consulta la sección[Acerca de administrar las dependencias vulnerables](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)". {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} -If you use -{% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. -For more information about +Si utilizas +el {% data variables.product.prodname_dependabot %} para mantener actualizadas tus dependencias, puedes utilizar y guardar el filtro personalizado `is:repository_vulnerability_alert` para mostrar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}. +Para obtener más información sobre -{% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +el {% 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)". {% endif %} {% endif %} diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md index a472d79a81..016e1d5873 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md @@ -1,7 +1,7 @@ --- title: Administrar suscripciones de actividades en GitHub intro: 'Para mantener notificaciones de flujo de trabajo sostenibles, entender y revisar frecuentemente tus suscripciones.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '>=2.21' diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 0086b2abae..d68c18d805 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ Cuando te desuscribes de las notificaciones en tu bandeja de entrada, desaparece {% data reusables.notifications.access_notifications %} 1. Desde la bandeja de notificaciones, selecciona aquellas de las cuales deseas darte de baja. -2. Utiliza el menú desplegable de **seleccionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para dar clic en **Desuscribirse**. ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Utiliza el menú desplegable de **seleccionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para dar clic en **Desuscribirse**. ![Opción para darse de baja de una bandeja principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### Darse de baja de las notificaciones en la página de suscripciones diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md index a9b9122fb3..dc60e8ca82 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md @@ -1,7 +1,7 @@ --- title: Configurar las notificaciones intro: 'Para mejorar la relevancia de tus notificaciones y simplificar tu flujo de trabajo de clasificación, configura tus notificaciones para que empaten con tus prioridades.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/getting-started-with-notifications versions: diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md index 6368ea9a2a..fac02e75b2 100644 --- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md +++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md @@ -1,7 +1,7 @@ --- title: Ver y clasificar las notificaciones intro: 'Para optimizar el flujo de trabajo de tus notificaciones, puedes personalizar como las visualizas y clasificas.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-notifications/ - /articles/managing-your-notifications diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md index af03c580d9..8d6c3c6d92 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md @@ -25,11 +25,11 @@ Si creas una URL no válida usando los parámetros de consulta o si no tienen lo | Parámetro de consulta | Ejemplo | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `body` | `https://github.com/octo-org/octo-repo/compare/main...pull-request-test?quick_pull=1&body=Fixes+the+problem.` creates a pull request, comparing the branches `main` and `pull-request-test`, with the comment "Fixes the problem" in the pull request body. | +| `cuerpo` | `https://github.com/octo-org/octo-repo/compare/main...pull-request-test?quick_pull=1&body=Fixes+the+problem.` creates a pull request, comparing the branches `main` and `pull-request-test`, with the comment "Fixes the problem" in the pull request body. | | `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". | | `etiquetas` | `https://github.com/octo-org/octo-repo/compare/main...pull-request-test?quick_pull=1&labels=bug` creates a pull request, comparing the branches `main` and `pull-request-test`, with the label "bug." | -| `template` | `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. | -| `milestone` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` crea una propuesta con el hito "probando hitos". | +| `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. | +| `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. | @@ -43,6 +43,6 @@ Si un repositorio contiene solo la solicitud de extracción o la plantilla de pr Para obtener más información, consulta "[Crear una plantilla de solicitud de extracción para tu repositorio](/articles/creating-a-pull-request-template-for-your-repository)" o "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". -### Further reading +### Leer más - "[Automatización para formularios de lanzamiento con parámetros de consulta](/articles/automation-for-release-forms-with-query-parameters)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md index a558a2c496..2fac9c6578 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-project-boards.md @@ -35,6 +35,6 @@ Puedes rastrear el progreso en tu tablero de proyecto. Las tarjetas en las colum Para obtener más información, consulta la sección "[Rastrear el progreso en tu tablero de proyecto](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)". -### Further reading +### Leer más - "[Configurar la automatización para los tableros de proyecto](/articles/configuring-automation-for-project-boards)"{% if currentVersion == "free-pro-team@latest" %} - "[Copying a project board](/articles/copying-a-project-board)"{% endif %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md b/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md index 1ed5c7d26a..a412414716 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-milestones.md @@ -35,7 +35,7 @@ Puedes priorizar propuestas y solicitudes de extracción abiertas en un hito hac ![Hito reordenado](/assets/images/help/issues/milestone-reordered.gif) -### Further reading +### Leer más - "[Crear y editar hitos para propuestas y solicitudes de extracción](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)" - "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md index 451e4292f2..ae40c43952 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-project-boards.md @@ -57,7 +57,7 @@ Para obtener más información, consulta "[Acerca de la automatización para tab {% data reusables.project-management.copy-project-boards %} -### Further reading +### Leer más - "[Crear un tablero de proyecto](/articles/creating-a-project-board)" - "[Editar un tablero de proyecto](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md b/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md index dd5434fba7..ee4f20e50a 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/about-task-lists.md @@ -27,6 +27,6 @@ Puedes volver a ordenar las listas de tareas dentro de un comentario único haci ![Volver a ordenar lista de tareas](/assets/images/help/writing/task-list-reordered.gif) -### Further reading +### Leer más * [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md index 35372c797d..960dfbd5ba 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board.md @@ -58,7 +58,7 @@ Puedes poner un máximo de 2500 tarjetas en cada columna del proyecto. Si una co 4. Selecciona uno o más tableros de proyecto en donde quieras agregar la propuesta o solicitud de cambios. ![Tablero de proyecto seleccionado](/assets/images/help/projects/sidebar-select-project.png) 5. Haz clic en {% octicon "triangle-down" aria-label="The down triangle icon" %}, luego haz clic en la columna en la que quieras colocar tu propuesta o solicitud de extracción. La tarjeta se moverá al final de la columna del tablero de proyecto que selecciones. ![Menú Move card to column (Mover tarjeta a la columna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) -### Further reading +### Leer más - "[Acerca de los tablero de proyecto](/articles/about-project-boards)" - "[Editar un tablero de proyecto](/articles/editing-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md index 0fe2fed0e8..058fe8052f 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/adding-notes-to-a-project-board.md @@ -62,7 +62,7 @@ Cuando conviertes una nota en una propuesta, la propuesta se crea automáticamen 3. Para editar los contenidos de la nota, haz clic en **Edit note** (Editar nota). ![Botón para editar notas](/assets/images/help/projects/edit-note.png) 4. Para eliminar los contenidos de las notas, haz clic en **Delete note** (Eliminar nota). ![Botón para eliminar notas](/assets/images/help/projects/delete-note.png) -### Further reading +### Leer más - "[Acerca de los tablero de proyecto](/articles/about-project-boards)" - "[Crear un tablero de proyecto](/articles/creating-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md index e39271fab7..71a4ee078f 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.md @@ -19,6 +19,6 @@ Puedes asignar hasta 10 personas a cada propuesta o solicitud de cambios, incluy 4. En el margen superior derecho, haz clic en **Assignee** (Asignatario). 5. Para asignar los elementos a un usuario, comienza escribiendo su nombre de usuario, luego haz clic en su nombre cuando aparezca. Puedes seleccionar y asignar hasta 10 asignatarios a una propuesta o solicitud de extracción. ![Desplegable de la asignación de propuestas](/assets/images/help/issues/issues_assigning_dropdown.png) -### Further reading +### Leer más * "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md index e2504b19d2..6f4f5b0ad4 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests.md @@ -20,7 +20,7 @@ A medida que trabajas en las propuestas y las solicitudes de extracción, puedes {% endtip %} -### Further reading +### Leer más - "[Acerca de los hitos](/articles/about-milestones)" - "[Crear y editar hitos para propuestas y solicitudes de extracción](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md index 5699f8e509..f1ce295f8a 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Cambiar la visibilidad del tablero de proyecto -intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.' +intro: 'Como propietario de una organización o administrador del tablero de proyecto, puedes convertir dicho tablero de proyecto en {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} o privado.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,13 +13,13 @@ versions: {% tip %} -**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. Puedes brindar a los miembros de la organización permisos de escritura o administración específicos al brindar acceso al tablero de proyecto a los equipos en los que están y al agregarlos en un tablero de proyecto como colaboradores. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". +**Tip:** Cuando conviertas tu tablero de proyecto en {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}, se les otorgará acceso de lectura a los miembros de la organización predeterminadamente. Puedes brindar a los miembros de la organización permisos de escritura o administración específicos al brindar acceso al tablero de proyecto a los equipos en los que están y al agregarlos en un tablero de proyecto como colaboradores. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". {% endtip %} -1. Navigate to the project board you want to make +1. Navega hasta el tablero de proyecto que quieres convertir en -{% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. +{% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} o privado. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.choose-visibility %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md index b84512128e..7603963f8e 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/closing-a-project-board.md @@ -18,7 +18,7 @@ Si vuelves a abrir un tablero de proyecto, tienes la opción de *sincronizar* la 2. En la lista de proyectos, junto al tablero de proyectos que deseas cerrar, haz clic en {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Icono de comillas angulares a la derecha del nombre del tablero de proyecto](/assets/images/help/projects/project-list-action-chevron.png) 3. Da clic en **Cerrar**. ![Menú desplegable para cerrar elementos en el tablero de proyecto](/assets/images/help/projects/close-project.png) -### Further reading +### Leer más - "[Acerca de los tablero de proyecto](/articles/about-project-boards)" - "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md index 9489ebccca..ba8deb6f3f 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/configuring-automation-for-project-boards.md @@ -28,5 +28,5 @@ versions: 5. Selecciona las automatizaciones del flujo de trabajo que deseas configurar para la columna. ![Lista de opciones para automatizar la columna](/assets/images/help/projects/select-automation-options-existing-column.png) 6. Haz clic en **Update automation** (Actualizar automatización). -### Further reading +### Leer más - "[Acerca de la automatización de los tableros de proyecto](/articles/about-automation-for-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md index 2a7f7b5aef..b692f7808b 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet.md @@ -28,7 +28,7 @@ Este tipo de enlace permanente se presentará como un fragmento de código únic 5. Dirígete a la conversación en la que deseas enlazar el fragmento de código. 6. Pega tu enlace permanente en un comentario y haz clic en **Comentar**. ![Enlace permanente pegado en un comentario en el mismo repositorio](/assets/images/help/repository/code-snippet-permalink-in-comment.png) -### Further reading +### Leer más - [Crear una propuesta](/articles/creating-an-issue/)" - "[Abrir una propuesta desde el código](/articles/opening-an-issue-from-code/)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md index 8307023197..7dded559d2 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -66,7 +66,7 @@ También puedes configurar automatizaciones de flujo de trabajo para mantener tu ### Crear un tablero de proyecto para un repositorio {% data reusables.repositories.navigate-to-repo %} -2. Under your repository name, click +2. Debajo del nombre de tu repositorio, da clic en {% octicon "project" aria-label="The project board icon" %} **Proyectos**. ![Pestaña Project (Proyecto)](/assets/images/help/projects/repo-tabs-projects.png) {% data reusables.project-management.click-new-project %} @@ -82,7 +82,7 @@ También puedes configurar automatizaciones de flujo de trabajo para mantener tu {% data reusables.project-management.edit-project-columns %} -### Further reading +### Leer más - "[Acerca de los tableros de proyectos](/articles/about-project-boards)" - "[Editar un tablero de proyecto](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md index b63c4d2c00..8157b959e4 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-an-issue.md @@ -44,6 +44,6 @@ Si utilizas un tablero de proyecto para rastrear y priorizar tu trabajo, puedes {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -### Further reading +### Leer más - "[Crear un enlace permanente a un fragmento de código](/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet)". diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md index e8f78b59b5..6c49bf0b5c 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md @@ -27,7 +27,7 @@ Cuando eliminas hitos, las propuestas y las solicitudes de extracción no se ven {% data reusables.project-management.milestones %} 4. Junto al hito que deseas eliminar, haz clic en **Eliminar**. ![Opción Eliminar hito](/assets/images/help/repository/delete-milestone.png) -### Further reading +### Leer más - "[Acerca de los hitos](/articles/about-milestones)" - "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md index a585656496..cd836fcc41 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/deleting-a-project-board.md @@ -22,7 +22,7 @@ versions: 4. Haz clic en **Eliminar proyecto**. ![Botón Eliminar proyecto](/assets/images/help/projects/delete-project-button.png) 5. Para confirmar que deseas eliminar el tablero de proyecto, haz clic en **Aceptar**. -### Further reading +### Leer más - "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" - "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md b/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md index 0f4b2a74d4..1c8075bfef 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/deleting-an-issue.md @@ -19,6 +19,6 @@ Los colaboradores no reciben una notificación cuando eliminas una propuesta. Cu 3. En la barra lateral derecha, debajo de "Notificaciones", da clic en **Borrar informe de problemas**. ![Texto de "Borrar informe de problemas" resaltado al final de la barra lateral derecha de la página del informe de problemas](/assets/images/help/issues/delete-issue.png) 4. Para confirmar la eliminación, haz clic en **Eliminar esta propuesta**. -### Further reading +### Leer más - "[Enlazar una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md index d5be330ad3..e24f199097 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md @@ -25,7 +25,7 @@ Cuando inhabilitas tableros de proyecto, ya no ves su información de manera cro {% data reusables.organizations.disable_project_board_results %} -### Further reading +### Leer más - "[Acerca de los tablero de proyecto](/articles/about-project-boards)" - "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md index b18fde040c..a97d360282 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/editing-a-project-board.md @@ -22,7 +22,7 @@ versions: {% data reusables.project-management.click-edit-sidebar-menu-project-board %} 4. Modifica el nombre y la descripción del tablero de proyecto según sea necesario y luego haz clic en **Guardar proyecto**. ![Campos con el nombre y la descripción del tablero de proyecto y botón Guardar proyecto](/assets/images/help/projects/edit-project-board-save-button.png) -### Further reading +### Leer más - "[Acerca de los tablero de proyecto](/articles/about-project-boards)" - "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md index 7e6d0df42e..863ea4be7b 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md @@ -34,7 +34,7 @@ También puedes usar la barra de búsqueda "Filtrar tarjetas" en la parte superi {% endtip %} -### Further reading +### Leer más - "[Acerca de los tablero de proyecto](/articles/about-project-boards)" - "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md index 43ce98e4d4..b61c982be0 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees.md @@ -22,7 +22,7 @@ Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda {% endtip %} -### Further reading +### Leer más - [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" - [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md index 4821fd80f1..25352ad48e 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels.md @@ -22,7 +22,7 @@ versions: {% endtip %} -### Further reading +### Leer más - [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" - [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md index 13f32f4f17..f306fa439b 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone.md @@ -24,7 +24,7 @@ versions: 3. Selecciona **Hitos** para ver una lista de todos los hitos disponibles para el repositorio. ![Botón Hitos](/assets/images/help/issues/issues_milestone_button.png) 4. Selecciona el hito que te interesa en la lista. En la página del hito puedes ver información relevante sobre el hito, incluidas todas las propuestas y solicitudes de extracción asociadas con él. Para obtener más información, consulta "[Acerca de los hitos](/articles/about-milestones)". -### Further reading +### Leer más - [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" - [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md index d0c97871ce..da0705480d 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md @@ -23,7 +23,7 @@ Puedes filtrar propuestas y solicitudes de extracción para buscar: {% 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) -### Further reading +### Leer más - "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)" - "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 7e252d5c05..43936e0b32 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -22,7 +22,7 @@ Puedes filtrar la lista de solicitudes de extracción de un repositorio para bus 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) -### Further reading +### Leer más - "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" - "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md b/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md index 0cf9f3f735..f701c18cf9 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/finding-information-in-a-repository.md @@ -1,7 +1,7 @@ --- title: Buscar información en un repositorio intro: 'Para buscar información detallada acerca de un repositorio en GitHub, puedes filtrar, clasificar y buscar propuestas y solicitudes de extracción que son relevantes para el repositorio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/finding-information-in-a-repository versions: diff --git a/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md index ce3a07566d..026a00bde0 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md @@ -50,7 +50,7 @@ Puedes vincular una solicitud de cambios con una propuesta si utilizas una palab * fix * fixes * fixed -* resolve +* resolver * resuelve * resuelto @@ -66,6 +66,6 @@ La sintaxis para palabras clave de cierre dependerá de si el informe de problem 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. -### Further reading +### Leer más - "[URL y referencias auto-enlazadas](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md index 7f7ba6d977..216d9680ad 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/linking-a-repository-to-a-project-board.md @@ -27,6 +27,6 @@ Cualquiera con permisos de escritura en un tablero de proyecto puede enlazar rep 6. Busca el repositorio que quieras vincular. ![Campo de búsqueda en la ventana Link a repository (Vincular un repositorio)](/assets/images/help/projects/search-to-link-repository.png) 7. Da clic en **Enlace**. Para desvincular, haz clic en **Unlink** (Desvincular). ![Botón Link (Vincular)](/assets/images/help/projects/link-button.png) -### Further reading +### Leer más - "[Acerca de los tableros de proyectos](/articles/about-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md index c497d5a058..a9b8b98eb2 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md @@ -27,7 +27,7 @@ versions: Puedes administrar tu trabajo en {% data variables.product.product_name %} creando etiquetas para clasificar las propuestas y las solicitudes de extracción. Puedes aplicar etiquetas en el repositorio en el que éstas se hayan creado. Una vez que existe una etiqueta, puedes utilizarla en cualquier propuesta o solicitud de cambios dentro del repositorio en cuestión. -Cualquiera con acceso de lectura a un repositorio puede ver y buscar las etiquetas del repositorio. Anyone with triage access to a repository can apply/dismiss existing labels. Para crear, editar, aplicar o eliminar una etiqueta, debes tener acceso de escritura al repositorio. +Cualquiera con acceso de lectura a un repositorio puede ver y buscar las etiquetas del repositorio. Cualquiera con acceso de clasificación en un repositorio puede aplicar/descartar las etiquetas existentes. Para crear, editar, aplicar o eliminar una etiqueta, debes tener acceso de escritura al repositorio. ### Acerca de las etiquetas predeterminadas @@ -90,7 +90,7 @@ El borrar una etiqueta la eliminará de las propuestas y soilcitudes de cambios. {% data reusables.project-management.labels %} {% data reusables.project-management.delete-label %} -### Further reading +### Leer más - "[Filtrar propuestas y solicitudes de cambios por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - "[Administrar las etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} - "[Fomentar las contribuciones sanas a tu proyecto con etiquetas](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md index 1ce9ca4c9c..df88315d7e 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-project-boards.md @@ -1,7 +1,7 @@ --- title: Administrar tableros de proyecto intro: Puedes usar tableros de proyecto para organizar propuestas y solicitudes de extracción y administrar tu flujo de trabajo a través de un repositorio u organización. -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-project-boards versions: diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md index 9d7994d118..b67f21b84d 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md @@ -1,7 +1,7 @@ --- title: Administrar tu trabajo con propuestas y solicitudes de cambios intro: 'Puedes administrar tu trabajo en {% data variables.product.product_name %} al crear propuestas para rastrear ideas, mejoras, tareas o errores.' -mapTopic: verdadero +mapTopic: true redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues - /articles/managing-your-work-with-issues diff --git a/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md index 0f875a62c7..cbb11decd0 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-a-comment.md @@ -21,6 +21,6 @@ Cuando abres un informe de problemas desde un comentario, este informe contiene 6. Haz clic en **Create issue** (Crear propuesta). ![Botón para crear la nueva propuesta](/assets/images/help/pull_requests/create-issue.png) {% data reusables.repositories.assign-an-issue-as-project-maintainer %} -### Further reading +### Leer más - [Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md index 954e71dad6..e4093e87b7 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/opening-an-issue-from-code.md @@ -28,7 +28,7 @@ Cuando abres una propuesta desde el código, la propuesta contiene un fragmento {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -### Further reading +### Leer más - [Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)" - "[Obtener enlaces permanentes a los archivos](/github/managing-files-in-a-repository/getting-permanent-links-to-files)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md b/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md index 09185f7d7c..d5699fdd01 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/reopening-a-closed-project-board.md @@ -19,6 +19,6 @@ Cuando reabres un tablero de proyecto, tienes la opción de *sync* (sincronizar) - Para reabrir tu tablero de proyecto y sincronizar la automatización, haz clic en **Reopen and sync project** (Reabrir y sincronizar proyecto). ![Selecciona el botón "Reopen and resync project" (Reabrir y resincronizar proyecto)](/assets/images/help/projects/reopen-and-sync-project.png) - Para reabrir tu tablero de proyecto sin sincronizar la automatización, utilizando el menú desplegable, haz clic en **Reopen only** (Solo reabrir). Luego, haz clic en **Reopen only** (Solo reabrir). ![Menú desplegable para reabrir tablero de proyecto cerrado](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png) -### Further reading +### Leer más - "[Configurar la automatización para los tableros de proyecto](/articles/configuring-automation-for-project-boards)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md b/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md index 35cd810297..114b9ab36b 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/sharing-filters.md @@ -17,7 +17,7 @@ Por ejemplo, si filtras propuestas asignadas a Hubot, y clasificas las propuesta /issues?q=state:open+type:issue+assignee:hubot+sort:created-asc ``` -### Further reading +### Leer más * [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" * [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md index d4d3e3e97a..3e7c2a67d7 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md @@ -25,7 +25,7 @@ Puedes clasificar cualquier vista filtrada por: Para borrar tu selección de clasificación, haz clic en **Sort** > (Clasificar); **Newest** (Más reciente). -### Further reading +### Leer más * [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" * "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md index 00b600730d..35a9b08171 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md @@ -1,7 +1,7 @@ --- title: Rastrear el progreso de tu trabajo con hitos intro: 'Puedes hacer el seguimiento de tu trabajo en {% data variables.product.product_name %} creando hitos con propuestas y solicitudes de extracción asociadas.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/tracking-the-progress-of-your-work-with-milestones versions: diff --git a/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md index ea56d41f8b..26c927a1bc 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md @@ -4,7 +4,7 @@ intro: 'Puedes hacer el seguimiento y priorizar tu trabajo en {% data variables. redirect_from: - /articles/tracking-the-progress-of-your-work-with-projects/ - /articles/tracking-the-progress-of-your-work-with-project-boards -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 7fe090d54d..6c1d0d3d10 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: Para transferir una propuesta abierta a otro repositorio, debes tener permisos de escritura sobre el repositorio en el que está la propuesta y sobre el repositorio al que le estás transfiriendo la propuesta. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". -Solo puedes transferir propuestas entre repositorios que pertenezcan a la misma cuenta de usuario o de organización.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}No puedes transferir una propuesta desde un repositorio privado a un repositorio público.{% endif %} +Solo puedes transferir propuestas entre repositorios que son propiedad del mismo usuario o de la misma cuenta de la organización. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} Cuando transfieres un informe de problemas, se retendrá tanto los comentarios como las personas asignadas. No se retendrán los hitos y etiquetas de la propuesta. Esta propuesta se mantendrá en cualquier tablero de proyecto que pertenezca al usuario o que se encuentre en la organización y se eliminará de cualquier tablero de proyecto de los repositorios. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)." @@ -26,7 +26,7 @@ Las personas o equipos que se mencionan en la propuesta recibirán una notificac 5. Utiliza el menú desplegable **Choose a repository** (Elegir un repositorio) y selecciona el repositorio al que quieres transferir la propuesta. ![Elige una selección de repositorio](/assets/images/help/repository/choose-a-repository.png) 6. Haz clic en **Transfer issue** (Transferir propuesta). ![Botón Transfer issue (Transferir propuesta)](/assets/images/help/repository/transfer-issue-button.png) -### Further reading +### Leer más - "[Acerca de las propuestas](/articles/about-issues)" - "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 88c4087fe3..f87b23cf9f 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -44,7 +44,7 @@ Para las solicitudes de cambios, también puedes utilizar la búsqueda para: - Filtra las solicitudes de cambios de acuerdo con el equipo al que se le solicitó la revisión: `state:open type:pr team-review-requested:github/atom`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} - Filtrar por las solicitudes de extracción enlazadas con un informe de problemas que se pudiera cerrar con dicha solicitud: `linked:issue`{% endif %} -### Further reading +### Leer más - "[Buscar propuestas](/articles/searching-issues)" - [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md index d671ee6ac8..bf27c1e368 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md @@ -14,6 +14,6 @@ Tus tableros de propuestas y solicitudes de extracción están disponibles en la 1. En la partes superior de cualquier página, haz clic en **Pull requests (Solicitudes de extracción)** o **Issues (Propuestas)**. ![Tableros de solicitudes de extracción o propuestas globales](/assets/images/help/overview/issues_and_pr_dashboard.png) 2. Como alternativa, elige un filtro o [utiliza la barra de búsqueda para filtrar resultados más específicos](/articles/using-search-to-filter-issues-and-pull-requests). ![Lista de solicitudes de extracción con el filtro "Created" (Creado) seleccionado](/assets/images/help/overview/pr_dashboard_created.png) -### Further reading +### Leer más - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listar los repositorios que estás observando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" diff --git a/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md b/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md index ac00fc6c58..ba8709f095 100644 --- a/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md +++ b/translations/es-ES/content/github/managing-your-work-on-github/viewing-your-milestones-progress.md @@ -19,7 +19,7 @@ versions: Para administrar mejor tu proyecto, puedes priorizar propuestas o solicitudes de extracción dentro de un hito. Para obtener más información, consulta "[Acerca de los hitos](/articles/about-milestones#prioritizing-issues-and-pull-requests-in-milestones)." -### Further reading +### Leer más * "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" * "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index 1145697312..5bb5a86e1b 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,9 +25,10 @@ Las notificaciones por correo electrónico de {% data variables.product.product_ | campo `Para` | Este campo se conecta directamente con el hilo de correo. Si respondes al correo electrónico, agregarás un nuevo comentario a la conversación. | | dirección `Cc` | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son:
    • `assign`: Te asignaron a una propuesta o solicitud de extracción.
    • `author`: Creaste una propuesta o solicitud de extracción.
    • `comment`: Comentaste una propuesta o solicitud de extracción.
    • `manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.
    • `mention`: Te mencionaron en una propuesta o solicitud de extracción.
    • `push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.
    • `review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.
    • `security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.
    • `state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.
    • `subscribed`: Hubo una actualización en un repositorio que estás mirando.
    • `team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.
    • `your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.
    | | Campo `mailing list` (lista de correos) | Este campo identifica el nombre del repositorio y su propietario. El formato de esta dirección siempre es `..{% data variables.command_line.backticks %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| Campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    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)". |{% endif %} +| Campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    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)". +{% endif %} -### Further reading +### Leer más - "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" - "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md index f73dcc3b0e..f42fe613ab 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-notifications.md @@ -47,7 +47,7 @@ Recibirás una notificación si: También puedes explorar las actividades de las personas que sigues, los repositorios que miras y las organizaciones de las que eres miembro en tu tablero. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". -### Further reading +### Leer más - "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" - "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md index 75331687da..8fd3f8ef5b 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/about-web-notifications.md @@ -17,7 +17,7 @@ Desde la página de notificaciones, también puedes marcar las notificaciones co - "[Guardar las notificaciones para después](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later)" - "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" -### Further reading +### Leer más - "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" - "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md index dc1b8bf64f..e9a062d1ae 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/accessing-your-notifications.md @@ -17,7 +17,7 @@ Para acceder a las notificaciones web en {% data variables.product.product_name Si tienes configuradas las notificaciones por correo electrónico, puedes acceder a tus notificaciones a través de tu cliente de correo electrónico. Para obtener más información sobre habilitar las notificaciones por correo electrónico, consulta la sección "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" y "[Elegir el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md index f5f1584d50..cdf5c8d8ee 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications.md @@ -37,7 +37,7 @@ Para las cuentas personales, los correos electrónicos de notificación se enví - Si seleccionas **Email each time a vulnerabilidad is found** (Enviar un correo electrónico cada vez que se encuentra una vulnerabilidad) se envía un correo electrónico a tu correo electrónico predeterminado. - Si seleccionas **Email a digest summary of vulnerabilities** (Enviar un correo electrónico con un resumen de vulnerabilidades) envía un correo electrónico condensado con un resumen de hasta 10 alertas de seguridad de los repositorios. Usa el menú desplegable para recibir correos electrónicos condensados diariamente o semanalmente. -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md index 1e6192e925..ec59510c44 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications.md @@ -1,7 +1,7 @@ --- title: Comenzar con las notificaciones intro: 'Las notificaciones te ayudan a hacer un seguimiento de las conversaciones y las actualizaciones que te interesan. Puedes recibir notificaciones en {% data variables.product.product_name %} o a través de tu cliente de correo electrónico sobre conversaciones en las que estás participando o actualizaciones que estás observando.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: <2.21 --- diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md index 3043d7f5e6..00b237146f 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching.md @@ -9,7 +9,7 @@ versions: 2. Haz clic en **Watching** (Ver) para ver la lista de repositorios que estás observando. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) 3. Da clic en **Dejar de Seguir** o en **Dejar de seguir los lanzamientos** junto al repositorio del que ya no quieras recibir notificaciones. -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md index f39203f163..a96d312f68 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications.md @@ -1,7 +1,7 @@ --- title: Administrar tus notificaciones intro: 'Para que sea más sencillo recibir las notificaciones que te interesan, puedes marcar notificaciones como leer, suscribir y cancelar la suscripción de notificaciones y ver y dejar de ver repositorios.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: <2.21 --- diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md index 8a464227ba..68bed2229e 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read.md @@ -31,7 +31,7 @@ Para obtener más información acerca de cómo acceder a tus notificaciones web, 1. En la barra lateral izquierda, haz clic en el nombre del repositorio para el cual desearías marcar todas las notificaciones como leídas. 1. En la lista de notificaciones, en el lateral derecho del nombre del repositorio, haz clic en {% octicon "check" aria-label="The check symbol" %}. ![Botón para marcar todas las notificaciones de un repositorio como leídas](/assets/images/help/notifications/notifications_repositories_mark_all_as_read.png) -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md index 7e3cc9477c..fc5af7dabf 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later.md @@ -23,7 +23,7 @@ Cuando guardas una notificación, se mueve a la pestaña Saved for later (Guarda 1. En tu lista de notificaciones guardadas, encuentra la notificación guardada que desearías eliminar. 1. En el lateral derecho de la notificación guardada, haz clic en {% octicon "bookmark" aria-label="The bookmark button" %}. ![Botón para eliminar una notificación guardada](/assets/images/help/notifications/remove-saved-notification.png) -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Acceder a tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md index 768aacdc14..1e429131fd 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications.md @@ -34,7 +34,7 @@ versions: 5. En la página del equipo, encuentra el debate del que deseas cancelar la suscripción. 6. En el ángulo superior derecho del debate, haz clic en {% octicon "mute" aria-label="The unsubscribe symbol" %} para cancelar la suscripción al debate. ![Botón para suscribirse a un debate de equipo](/assets/images/help/notifications/team-discussion-unsubscribe-button.png) -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Acerca de los debates en {% data variables.product.product_name %}](/articles/about-conversations-on-github)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md index 7e27d9655f..e6b7a86db6 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository.md @@ -15,7 +15,7 @@ versions: {% data reusables.repositories.navigate-to-repo %} 2. En el ángulo superior derecho, haz clic en **Not watching (Dejar de ver)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para lanzamientos](/assets/images/help/notifications/unwatch-repository.png) -### Further reading +### Leer más - "[Acerca de los lanzamientos](/articles/about-releases)" - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md index adf23fb6f8..4095e578b5 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories.md @@ -37,7 +37,7 @@ También puedes observar y dejar de observar los lanzamientos en un repositorio. {% endnote %} -### Further reading +### Leer más - "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" - "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md index d71c61a2a8..a4230eed00 100644 --- a/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md +++ b/translations/es-ES/content/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions.md @@ -55,7 +55,7 @@ Si no deseas recibir de forma automática las notificaciones de debates de equip {% endnote %} -### Further reading +### Leer más - "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" - "[Acerca de los debates del equipo](/articles/about-team-discussions)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md index 768f15d728..0ef9322653 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -70,7 +70,7 @@ Si tu administrador de sitio habilita la {% data variables.product.prodname_unified_search %} en los repositorios privados, solo podrás hacer búsquedas en los repositorios privados para los cuales el administrador haya habilitado la {% data variables.product.prodname_unified_search %} y a los cuales tengas acceso en la organización de {% data variables.product.prodname_dotcom_the_website %} conectada. Los administradores de {% data variables.product.prodname_enterprise %} y los propietarios de la organización en {% data variables.product.prodname_dotcom_the_website %} no pueden buscar en repositorios privados que son propiedad de tu cuenta. Para buscar los repositorios privados aplicables, debes activar la búsqueda de repositorio privado para tus cuentas personales en {% data variables.product.prodname_dotcom_the_website %} y {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Activar la búsqueda de repositorio privado de {% data variables.product.prodname_dotcom_the_website %} en tu cuenta de {% data variables.product.prodname_enterprise %} account](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)". {% endif %} -### Further reading +### Leer más - "[Comprender la sintaxis de búsqueda](/articles/understanding-the-search-syntax)" - "[Búsqueda en GitHub](/articles/searching-on-github)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md index aa1fc669bb..88663a707d 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/finding-files-on-github.md @@ -27,7 +27,7 @@ versions: 3. En el campo de búsqueda, escribe el nombre del archivo que deseas buscar. ![Campo de búsqueda Buscar archivo](/assets/images/help/search/find-file-search-field.png) 4. En la lista de resultados, haz clic en el archivo que deseas buscar. -### Further reading +### Leer más - "[Acerca de buscar en GitHub](/articles/about-searching-on-github)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md index bfcea12d25..1ac54725e5 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md @@ -1,6 +1,6 @@ --- title: Comenzar con la búsqueda en GitHub -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/getting-started-with-searching-on-github versions: diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md index 1b8eb9ee1a..d631df7245 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md @@ -100,7 +100,7 @@ El calificador `extension` (extensión) encuentra archivos de código con una de | 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". | -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" - "[Buscar en las bifurcaciones](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md index 10ca313fb0..47f36a8005 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-commits.md @@ -48,10 +48,10 @@ Utiliza los calificadores `author-date` y `committer-date` para encontrar confir {% 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) matches commits committed after 2016-01-01. | +| 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. | ### Filtrar confirmaciones de fusión @@ -102,6 +102,6 @@ El calificador `is` coincide con las confirmaciones de los repositorios con la v | Calificador| Ejemplo | ------------- | ------------- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `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. -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md index 8585bb03e4..2a1ffc0882 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-discussions.md @@ -105,6 +105,6 @@ Ambos calificadores toman la fecha como parámetro. {% data reusables.time_date. | created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) coincide con debates que se crearon después del 15 de noviembre de 2020. | | updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) coincide con debates que tengan la palabra "weird" en el cuerpo y que se hayan actualizado después de diciembre de 2020. | -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md index e8a975b653..160abbea42 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-for-repositories.md @@ -179,7 +179,7 @@ Puedes buscar repositorios que tienen una cantidad mínima de propuestas etiquet {% endif %} -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" - "[Búsqueda en bifurcaciones](/articles/searching-in-forks)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md index dfc299fe9c..81db46e29f 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-github-marketplace.md @@ -26,7 +26,7 @@ Cada vez que buscas en todo {% data variables.product.prodname_dotcom_the_websit 2. Teclea cualquier palabra clave y presiona **Enter**. ![campo buscar](/assets/images/help/search/search-field.png) 3. En la barra lateral, da clic en **Mercado**. ![Buscar resultados para linter con la opción del menú lateral del Mercado resaltada](/assets/images/help/search/marketplace-left-side-navigation.png) -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" - "[Utilizar acciones de {% data variables.product.prodname_marketplace %} en tu flujo de trabajo](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md index 0aa8f3bfa1..e7719c9e70 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-in-forks.md @@ -22,7 +22,7 @@ El calificador `fork:true` encuentra todos los resultados que coinciden con tu c | `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](/articles/about-searching-on-github)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 02fe2056eb..a29f359027 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ Puedes acotar tus resultados para que solo incluyan informes de problemas que se | `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 %} +| `-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 %} ### Buscar por etiqueta @@ -325,6 +326,6 @@ Puedes acotar tu búsqueda a propuestas y solicitudes de extracción que tienen | `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." | -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md index e5c1d3a875..9fbe3f000d 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-on-github.md @@ -1,6 +1,6 @@ --- title: Buscar en GitHub -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/searching-on-github versions: diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md index 51480cdb89..9535632009 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-topics.md @@ -47,5 +47,5 @@ Puedes filtrar temas en base a cuándo se crearon utilizando el parámetro de fe Puedes utilizar el calificador `topic:` (tema) para encontrar cada repositorio conectado a un tema particular. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-topic)." -### Further reading +### Leer más - "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md index eab9871d48..6802ea9bde 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-users.md @@ -85,6 +85,6 @@ Puedes filtrar usuarios en base a la cantidad de seguidores que tienen, utilizan | followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) coincidirá con los usuarios con 1,000 o más seguidores. | | | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) encuentra usuarios entre 1 y 10 seguidores, con la palabra "sparkle" en su nombre. | -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md index dc8f652fd5..4adc8f67ac 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-wikis.md @@ -42,6 +42,6 @@ El calificador `updated` (actualizada) empareja páginas wiki que fueron actuali | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) coincidirá con las páginas de wiki con la palabra "uso" que se actualizaron por última vez después del 2016-01-01. | -### Further reading +### Leer más - "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md b/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md index bc2bf4d64a..2e5f13bd47 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/sorting-search-results.md @@ -65,7 +65,7 @@ El calificador `sort:updated` clasifica según qué tan recientemente se actuali | `sort:updated` or `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) encuentra repositorios que contienen la palabra "feature," clasificados por la fecha de actualización más reciente. | | `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) encuentra repositorios que contienen la palabra "feature," clasificados por la fecha de actualización menos reciente. | -### Further reading +### Leer más - [Acerca de la búsqueda en GitHub](/articles/about-searching-on-github) - [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests/) diff --git a/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md b/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md index 54f5d76f91..c3fef764ea 100644 --- a/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md +++ b/translations/es-ES/content/github/searching-for-information-on-github/troubleshooting-search-queries.md @@ -24,6 +24,6 @@ Existen algunos límites en la longitud de las consultas cuando se busca en {% d Los tipos de búsqueda específicos, como la búsqueda de código, pueden tener más limitaciones. Revisa la documentación de estos tipos de búsqueda para obtener más información. -### Further reading +### Leer más - "[Acerca de buscar en GitHub](/articles/about-searching-on-github)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md index 99972f4c43..184a6b5c3c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage.md @@ -23,7 +23,7 @@ La compra de paquetes de datos para {% data variables.large_files.product_name_s Si bajas de categoría tu cantidad de paquetes de datos adicionales, tus cambios entrarán en vigencia en tu próxima fecha de facturación. -### Further reading +### Leer más - "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" - "[Instalar {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md index 615ac1badd..fdc9468f10 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace.md @@ -48,7 +48,7 @@ Si cancelas una app en un plan gratuito, tu suscripción terminará de inmediato Si cancelas un prueba gratuita en un plan pago, tu suscripción se cancela de inmediato y perderás el acceso a la app. Para obtener más información, consulta [Cancelar una app de {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app)". -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)" - "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 1375602251..92a241a7ee 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -28,8 +28,8 @@ Todos los datos de transferencia saliente, cuando se desencadenan mediante {% da | | Hospedado | Auto-Hospedado | | --------------------------------------------- | --------- | -------------- | -| Acceso utilizando un `GITHUB_TOKEN` | Free | Free | -| Acceso utilizando un token de acceso personal | Free | $ | +| Acceso utilizando un `GITHUB_TOKEN` | Gratis | Gratis | +| Acceso utilizando un token de acceso personal | Gratis | $ | El uso de almacenamiento se comparte con los artefactos de compilación que produce {% data variables.product.prodname_actions %} para los repositorios que pertenecen a tu cuenta. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index 26736be77e..a2ff97d406 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -13,7 +13,7 @@ versions: {% data reusables.dotcom_billing.view-all-subscriptions %} -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" - "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md index 85bf3d9a0a..c75e76ec75 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github.md @@ -23,7 +23,7 @@ Debes administrar los parámetros de facturación, el método de pago y las cara Para obtener más información, consulta "[Administrar tus parámetros de facturación {% data variables.product.prodname_dotcom %}](/articles/managing-your-github-billing-settings)". -### Further reading +### Leer más - "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)" - "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md index e552b00e9d..a3b31395cf 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies.md @@ -25,7 +25,7 @@ Aceptamos pagos mediante tarjeta de crédito y PayPal. No aceptamos pagos median Para una compra más fácil y más eficaz, recomendamos que las empresas de contratación configuren una facturación anual para las organizaciones de sus clientes. -### Further reading +### Leer más - "[Crear una organización y pagar por ella en nombre de un cliente](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)" - "[Actualizar o bajar de categoría la organización paga de tu cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md index bfc68632b7..08b7b92789 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing.md @@ -31,6 +31,6 @@ Puedes actualizar o bajar de categoría entre planes pagos heredados en los par Cuando bajas de categoría a un plan pago heredado con menos repositorios privados, tu nuevo plan entrará en vigencia en tu próxima fecha de facturación. Si tienes más repositorios privados de los que permite tu nuevo plan, tus repositorios privados se bloquearán cuando tu nuevo plan entre en vigencia. Para reducir la cantidad de repositorios privados, puedes hacer que algunos de tus repositorios privados sean públicos o puedes clonar tus repositorios privados localmente y eliminar las copias en {% data variables.product.prodname_dotcom %}. -### Further reading +### Leer más - "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md index e161f6d645..6da7c397ba 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md @@ -89,7 +89,7 @@ Si ya posees una cuenta de usuario de {% data variables.product.prodname_dotcom 2. Si deseas que la tarjeta de crédito de tu organización se elimine de la organización para que no vuelvan a hacerse cargos en ella, ponte en contacto con {% data variables.contact.contact_support %}. 3. Cuando sea el momento de renovar la suscripción paga de tu cliente, consulta "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)". -### Further reading +### Leer más - "[Acerca de las organizaciones para empresas de contratación](/articles/about-organizations-for-procurement-companies)" - "[Actualizar o bajar de categoría la organización paga de tu cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 068e8c5831..4f1306773f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -1,6 +1,6 @@ --- -title: Suscripciones con descuentos para cuentas GitHub -intro: '{% data variables.product.product_name %} ofrece descuentos a estudiantes, educadores, instituciones educativas, bibliotecas y organizaciones sin fines de lucro.' +title: Discounted subscriptions for GitHub accounts +intro: '{% data variables.product.product_name %} provides discounts to students, educators, educational institutions, nonprofits, and libraries.' redirect_from: - /articles/discounted-personal-accounts/ - /articles/discounted-organization-accounts/ @@ -12,24 +12,24 @@ versions: {% tip %} -**Sugerencia**: Los descuentos para {% data variables.product.prodname_dotcom %} no se tienen vigencia para las suscripciones de otros productos y características pagos. +**Tip**: Discounts for {% data variables.product.prodname_dotcom %} do not apply to subscriptions for other paid products and features. {% endtip %} -### Descuentos para cuentas personales +### Discounts for personal accounts -Además del número ilimitado de repositorios públicos y privados para estudiantes y miembros del cuerpo docente con {% data variables.product.prodname_free_user %}, los estudiantes validados pueden solicitar el {% data variables.product.prodname_student_pack %} para recibir beneficios adicionales ofrecidos por los socios de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Postularse para un paquete de desarrollo para estudiantes](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)". +In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)." -### Descuentos para escuelas y universidades +### Discounts for schools and universities -Los miembros del cuerpo docente validados pueden solicitar {% data variables.product.prodname_team %} para la enseñanza y la investigación académica. Para obtener más información, consulta la sección "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)". Para obtener más información, consulta "[Usar {{ site.data.variables.product.prodname_dotcom }} en tu clase y en tu investigación](/articles/using-github-in-your-classroom-and-research)". Para obtener más información, visita [{% data variables.product.prodname_education %}](https://education.github.com/). +Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[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)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/). -### Descuentos para bibliotecas y organizaciones sin fines de lucro +### Discounts for nonprofits and libraries -{% data variables.product.product_name %}proporciona {% data variables.product.prodname_team %} gratuito para organizaciones y cuenta con repositorios privados ilimitados, colaboradores ilimitados, y un juego completo de características a organizaciones y bibliotecas que califiquen como 501(c)3 (o equivalentes). Puedes solicitar un descuento para tu organización en [nuestra página de organizaciones sin fines de lucro](https://github.com/nonprofit). +{% data variables.product.product_name %} provides free {% data variables.product.prodname_team %} for organizations with unlimited private repositories, unlimited collaborators, and a full feature set to qualifying 501(c)3 (or equivalent) organizations and libraries. You can request a discount for your organization on [our nonprofit page](https://github.com/nonprofit). -Si tu organización ya tiene una suscripción paga, la última transacción de tu organización se reembolsará una vez que se haya aplicado tu descuento para organizaciones sin fines de lucro. +If your organization already has a paid subscription, your organization's last transaction will be refunded once your nonprofit discount has been applied. ### Further reading -- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)" +- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md index 0f958087f5..f66724d20d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md @@ -35,6 +35,6 @@ Cuando bajas de categoría una app, tu suscripción permanece activa hasta el fi {% data reusables.marketplace.choose-new-quantity %} {% data reusables.marketplace.issue-plan-changes %} -### Further reading +### Leer más - "[Cancelar una app {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md index 9402449613..6f6a9937cc 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md @@ -81,7 +81,7 @@ Para reducir el número de asientos pagos que usa tu organización, puedes elimi 1. En "Eliminar asientos" selecciona el número de asientos pagos de la categoría a la que deseas bajar. ![opción de eliminar plazas](/assets/images/help/billing/remove-seats-amount.png) 1. Revisa la información sobre tu nuevo pago en tu siguiente fecha de facturación, posteriormente, da clic en **Eliminar plazas**. ![botón de eliminar plazas](/assets/images/help/billing/remove-seats-button.png) -### Further reading +### Leer más - "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" - "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md index c90e7a3291..190781b774 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process.md @@ -27,7 +27,7 @@ La organización de Mada paga por 25 asientos el día 15 de cada mes. Si el 4 de La organización de Stefan paga por 50 asientos el 20 de mayo de cada año. Si Stefan elimina 20 asientos y baja de categoría a un nuevo total de 30 asientos pagos el 30 de septiembre, su organización puede seguir accediendo a sus 50 asientos pagos hasta el final de su ciclo de facturación actual, el 19 de mayo. El 20 de mayo, entrará en vigor la categoría más baja, la organización de Stefan pagará por 30 asientos y tendrá acceso a 30 asientos pagos. -### Further reading +### Leer más - "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)" - "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md index 4ef890bef0..35fcfb4523 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage.md @@ -6,7 +6,7 @@ redirect_from: - /articles/managing-large-file-storage-and-bandwidth-for-your-organization/ - /articles/managing-storage-and-bandwidth-usage/ - /articles/managing-billing-for-git-large-file-storage -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md index cdb1e6f876..a4f54b99a6 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions.md @@ -1,7 +1,7 @@ --- title: Administrar la facturación para GitHub Actions intro: 'Puedes ver el uso y configurar un límite de gastos para {% data variables.product.prodname_actions %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md index 91c2d7bff3..7da59d1120 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps.md @@ -5,7 +5,7 @@ redirect_from: - /articles/managing-your-personal-account-s-apps/ - /articles/managing-your-organization-s-apps/ - /articles/managing-billing-for-github-marketplace-apps -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md index 92c9bbefed..c5272b8ee9 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages.md @@ -1,7 +1,7 @@ --- title: Administrar la facturación para GitHub Packages intro: 'Puedes ver tu uso de {% data variables.product.prodname_registry %} y configurar un límite de gastos para {% data variables.product.prodname_registry %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md index 570ec8d09d..66115f48e8 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors.md @@ -1,7 +1,7 @@ --- title: Administrar la facturación de Patrocinadores de GitHub intro: Puedes actualizar o bajar de categoría el nivel de cada uno de tus patrocinadores. -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-billing-for-github-sponsors versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md index de6c392bbd..b2d1c58e50 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account.md @@ -11,7 +11,7 @@ redirect_from: - /categories/3/articles/ - /articles/managing-your-organization-s-paid-seats/ - /articles/managing-billing-for-your-github-account -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md index 0f1b620dad..c894b25113 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings.md @@ -9,7 +9,7 @@ redirect_from: - /categories/paying-for-organization-accounts/articles/ - /categories/99/articles/ - /articles/managing-your-github-billing-settings -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md index ae8e4f7e05..5c63ee5813 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies.md @@ -5,7 +5,7 @@ redirect_from: - /articles/setting-up-and-paying-for-organizations-for-resellers/ - /articles/setting-up-and-paying-for-organizations-for-procurement-companies/ - /articles/setting-up-paid-organizations-for-procurement-companies -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md index f5a10b7de4..d5da772cf5 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md @@ -31,7 +31,7 @@ versions: {% data reusables.large_files.pack_selection %} {% data reusables.large_files.pack_confirm %} -### Further reading +### Leer más - "[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)" - "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 24fb616898..c9e94ae09e 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -93,7 +93,7 @@ Si quisieras que usuarios adicionales tengan acceso a los repositorios privados {% data reusables.dotcom_billing.500-error %} -### Further reading +### Leer más - "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" - "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md index 94de153401..6997803966 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md @@ -34,6 +34,6 @@ Cuando cancelas un cambio pendiente, tu suscripción no cambiará en tu próxima {% data reusables.dotcom_billing.cancel-pending-changes %} {% data reusables.dotcom_billing.confirm-cancel-pending-changes %} -### Further reading +### Leer más - "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md index 5116bdce86..52d02f2ff6 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md @@ -29,7 +29,7 @@ versions: {% data reusables.user_settings.subscriptions-tab %} {% data reusables.dotcom_billing.lfs-data %} -### Further reading +### Leer más - "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" - "[Actualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md index 9c8243ac91..cd99d70eda 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md @@ -27,6 +27,6 @@ versions: {% data reusables.organizations.billing %} {% data reusables.dotcom_billing.next_billing_date %} -### Further reading +### Leer más - "[Acerca de la facturación para las cuentas de {% data variables.product.product_name %}](/articles/about-billing-for-github-accounts)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 0c876f5bb8..7d32a2b33f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: Después de configurar el SSO de SAML, los miembros de tu organización de {% data variables.product.prodname_dotcom %} continuarán ingresando en sus cuentas de usuario en {% data variables.product.prodname_dotcom %}. Cuando un miembro accede a recursos dentro de tu organización que utiliza el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redirecciona a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización. -Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. Para obtener más información, consulta la sección "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +Los propietarios de las organizaciones pueden requerir el SSO de SAML para una organización individual o para todas las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% data reusables.saml.outside-collaborators-exemption %} @@ -52,7 +52,7 @@ Si tu IdP admite SCIM, {% data variables.product.prodname_dotcom %} puede invita {% data reusables.saml.saml-single-logout-not-supported %} -### Further reading +### Lecturas adicionales - "[Acerca de la autenticación de dos factores y el inicio de sesión único de SAML ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" - "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md index a397122bec..47a5327ddd 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions.md @@ -45,7 +45,7 @@ Cuando una organización elimina el acceso de una {% data variables.product.prod Si una organización desactiva las restricciones de aplicación de acceso de {% data variables.product.prodname_oauth_app %}, y más tarde las vuelve a activar, automáticamente se le otorga acceso a los recursos de la organización a la {% data variables.product.prodname_oauth_app %} previamente aprobada . -### Further reading +### Leer más - "[Activar las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" - "[Aprobar {% data variables.product.prodname_oauth_app %}s para tu organización](/articles/approving-oauth-apps-for-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 7c92512bed..a4f00a9770 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,9 +17,9 @@ Estos proveedores de identidad son compatibles con la API de SCIM de {% data var - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.scim.enterprise-account-scim %} Para obtener más información, consulta la sección "[Acerca de el aprovisionamiento de usuarios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". -### Further reading +### Lecturas adicionales - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" - "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md index 04635026b3..d08a004a70 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-teams.md @@ -69,7 +69,7 @@ En la parte superior de la jerarquía del equipo, deberías otorgar permisos de 3. Crear todos los equipos nuevos que quieras, elegir un padre para cada equipo nuevo y otorgarles acceso a los repositorios. 4. Agregar las personas directamente a los equipos. -### Further reading +### Leer más - "[Crear un equipo](/articles/creating-a-team)" - "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md index a7f1811aac..c805b14b61 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on.md @@ -17,6 +17,6 @@ Si tanto la 2FA como SAML SSO están activados, los miembros de la organización - Usar el inicio de sesión único para acceder a la organización. - Usar un token autorizado para el acceso a Git o a la API y usar el inicio de sesión único para autorizar el token. -### Further reading +### Leer más - "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md index 918f8e0db2..f69ae86d4d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -22,6 +22,6 @@ Los administradores de la organización pueden usar [uno de los códigos de reup Una vez que has usado un código de verificación, asegúrate de anotar que ya no es válido. No podrás volver a usar el código de recuperación. -### Further reading +### Leer más - [Acerca de la administración de acceso e identidad con SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md index 8decbfec7c..8952ddc034 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization.md @@ -32,7 +32,7 @@ Para más información sobre los permisos del administrador de {% data variables 1. En "App managers" (Administradores de la app), escribe el nombre de usuario de la persona a quien deseas designar como administrador de la App GitHub para la app, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %} para una app específica](/assets/images/help/organizations/add-github-app-manager-for-app.png) {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" {% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md index 2953a8cbfa..6f932e17ac 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team.md @@ -22,7 +22,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %}{% data reusables.organizations.cancel_org_invite %}{% endif %} -### Further reading +### Leer más - [Acerca de los equipos](/articles/about-teams)" - "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md index 68ecb487ab..51db0222ac 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -32,7 +32,7 @@ Si tu organización [requiere miembros y colaboradores externos para usar la aut 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) {% endif %} -### Further reading +### Leer más - "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" - "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md index 08abb354b0..da1961c9c5 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization.md @@ -24,5 +24,5 @@ Si tu organización[requiere que los miembros usen autenticación de dos factore {% data reusables.organizations.add-user-to-teams %} {% data reusables.organizations.send-invitation %} -### Further reading +### Leer más - "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md index 07dad39f41..d2058a4fff 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization.md @@ -17,6 +17,6 @@ Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_ap 5. Junto a la aplicación que quieres aprobar, haz clic en **Review** (Revisar). ![Enlace de revisión de solicitud](/assets/images/help/settings/settings-third-party-approve-review.png) 6. Una vez que revises la información sobre la aplicación solicitada, haz clic en **Grant access** (Otorgar acceso). ![Botón para otorgar acceso](/assets/images/help/settings/settings-third-party-approve-grant.png) -### Further reading +### Leer más - "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md index bab61a1805..dcde38802c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -16,4 +16,4 @@ Para cada colaborador pendiente, puedes cancelar al mismo tiempo todas las invit {% data reusables.organizations.people_tab_outside_collaborators %} 5. Da clic en **colaboradores pendientes**. ![Botón de "Colaboradores pendientes"](/assets/images/help/organizations/pending-collaborator-list.png) 6. A la derecha de la persona para la cual quieres cancelar las invitaciones, da clic en **Cancelar invitaciones**. ![Botón de "Cancelar invitación"](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Da clic en **Cancelar invitaciones para los colaboradores pendientes**. ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) +7. Da clic en **Cancelar invitaciones para los colaboradores pendientes**. ![Botón para confirmar la cancelación](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md index 93c5fab621..47cfa5f1a1 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -18,7 +18,7 @@ versions: - Para editar la invitación del usuario, selecciona un rol o equipo diferente, luego haz clic en **Update invitation** (Actualizar invitación). - Para cancelar la invitación del usuario para unirte a tu organización, haz clic en **Cancel invitation** (Cancelar invitación). -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %} - "[Invitar a usuarios para que se unan a nuestra organización](/articles/inviting-users-to-join-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md index 79cb563313..7f4a986b5d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations.md @@ -4,7 +4,7 @@ intro: Los grupos de personas pueden colaborar en muchos proyectos a la vez en c redirect_from: - /articles/creating-a-new-organization-account/ - /articles/collaborating-with-groups-in-organizations -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md index 384c2957f2..404b936168 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -68,7 +68,7 @@ Después de que habilites SCIM, las siguientes características de aprovisionami {% data reusables.saml.okta-save-provisioning %} {% data reusables.saml.okta-edit-provisioning %} -### Further reading +### Leer más - "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)" - "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md index dbc6146519..2379442e1f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization.md @@ -24,7 +24,7 @@ Puedes buscar los detalles de la implementación de SAML y SCIM para tu IdP en s {% endnote %} -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" - "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md index 8afa122fbb..d5308b9737 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator.md @@ -33,7 +33,7 @@ Cuando conviertes a un miembro de la organización en colaborador externo, sus p 5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Convert to outside collaborator** (Convertir en colaborador externo). ![Menú desplegable con la opción para convertir miembros en colaboradores externos](/assets/images/help/teams/user-bulk-management-options.png) 6. Lee la información sobre cómo convertir miembros en colaboradores externos, luego haz clic en **Convert to outside collaborator** (Convertir en colaborador externo). ![Información sobre permisos de colaboradores externos y botón Convert to outside collaborators (Convertir en colaboradores externos)](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) -### Further reading +### Leer más - "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" - "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md index e8bd5ebbc8..e7ca3c2f27 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member.md @@ -35,6 +35,6 @@ Si tu organización [requiere que los miembros utilicen autenticación bifactori {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} {% endif %} -### Further reading +### Leer más - "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md index 2dde0c1f98..a3bfa75663 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch.md @@ -17,7 +17,7 @@ Cuando creas una organización nueva desde cero, esta no tiene ningún repositor {% data reusables.organizations.new-organization %} 4. Sigue las propuestas para crear tu organización. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información acerca de los planes disponibles para tu equipo, consulta la sección "[productos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)".{% endif %} -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %} - "[Establecer tu correo electrónico de facturación](/articles/setting-your-billing-email)"{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md index eaace35036..512b75fee0 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/creating-a-team.md @@ -27,7 +27,7 @@ Solo los propietarios y mantenedores de la organización en un equipo padre pued {% data reusables.organizations.create_team %} 9. También puede [darle acceso al equipo a los repositorios de la organización](/articles/managing-team-access-to-an-organization-repository). -### Further reading +### Leer más - [Acerca de los equipos](/articles/about-teams)" - "[Cambiar la visibilidad del equipo](/articles/changing-team-visibility)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md index b7bbf21190..c4516d2ce5 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -26,7 +26,7 @@ Los códigos de recuperación no se deben compartir ni distribuir. Te recomendam 7. Una vez que usas un código de recuperación para obtener acceso nuevamente a {% data variables.product.product_name %}, no puedes volver a usarlo. El acceso a {% data variables.product.product_name %} solo estará disponible durante 24 horas antes de que se te solicite que inicies sesión usando inicio de sesión único. -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" - "[Acceder a tu organización cuando tu proveedor de identidad no está disponible](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 2327158b72..daa6345260 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -43,6 +43,6 @@ Antes de exigir SAML SSO en tu organización, verifica que ya tengas configurado 12 Haz clic en **Save ** (guardar). ![Botón para guardar la configuración de SAML SSO](/assets/images/help/saml/saml_save.png) -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md index e85dca6a03..5e9699b18f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization.md @@ -22,6 +22,6 @@ Si tu organización le pertenece a una cuenta de empresa, al habilitar SAML para 2. Luego de seleccionar **Requerir autenticación del inicio de sesión único de SAML para todos los miembros de la organización SAML SSO Org**, se mostrarán los miembros de la organización que no se hayan autenticado mediante tu IdP. Si haces cumplir el inicio de sesión único de SAML, estos miembros se eliminarán de la organización. 3. Haz clic en **Hacer cumplir el inicio de sesión único de SAML** para hacer cumplir el inicio de sesión único de SAML y eliminar a los miembros de la organización que figuren en la lista. -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md index 71591b185c..43916162fb 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on.md @@ -1,7 +1,7 @@ --- title: Conceder acceso a tu organización con el inicio de sesión único SAML intro: 'Los administradores de la organización pueden conceder acceso con el inicio de sesión único SAML. Este acceso se les puede conceder a los miembros de la organización, a los bots y a las cuentas de servicio.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/granting-access-to-your-organization-with-saml-single-sign-on versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md index 55c803083b..01b7147acd 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md index 02cf661e1c..b7a67fd9fe 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board.md @@ -19,7 +19,7 @@ versions: 9. En **Organization owned applications** (Aplicaciones propiedad de la organización), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png) {% data reusables.user_settings.jira_help_docs %} -### Further reading +### Leer más - ["Integrar Jira a tus proyectos personales"](/articles/integrating-jira-with-your-personal-projects) - Conectar Jira Cloud a GitHub (Documentación de Atlassian) diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md index 15e5ffea04..30121047c3 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md @@ -28,5 +28,5 @@ versions: {% data reusables.organizations.send-invitation %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -### Further reading +### Leer más - "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md index ff977966b1..4d980d9b06 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure.md @@ -4,7 +4,7 @@ redirect_from: - /articles/preventing-unauthorized-access-to-organization-information/ - /articles/keeping-your-organization-secure intro: 'Los propietarios de la organización tienen varias funciones que los ayudan a mantener seguros los proyectos y los datos. Si eres el propietario de una organización, deberás revisar frecuentemente las bitácoras de auditoría de la misma{% if currentVersion != "github-ae@latest" %}, los estados de 2FA de los miembros,{% endif %} y la configuración de las aplicaciones para garantizar que no haya ocurrido ningún tipo de actividad maliciosa o no autorizada.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md index 3b931c6df3..2f3bcf0eda 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members.md @@ -28,7 +28,7 @@ Por defecto, los miembros de una organización tienen acceso de escritura a sus 8. Debajo de "Organization member permission" (Permiso para miembro de la organización), elige un nivel base de permiso para todos los miembros de la organización: **Read** (Lectura), **Write** (Escritura), **Administrar** o **None** (Ninguno). ![Opciones de permiso base a un tablero de proyecto para todos los miembros de una organización](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) 9. Haz clic en **Save ** (guardar). -### Further reading +### Leer más - "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" - "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md index 0fd7e23690..1a61e05823 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps.md @@ -4,7 +4,7 @@ intro: 'Como propietario de la organización, puedes permitir a los miembros ind redirect_from: - /articles/managing-access-to-your-organization-s-apps - /articles/managing-access-to-your-organizations-apps -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md index 5421cdf9cf..4e6e436b00 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards.md @@ -4,7 +4,7 @@ intro: 'Como propietario de la organización o administrador de un tablero de pr redirect_from: - /articles/managing-access-to-your-organization-s-project-boards - /articles/managing-access-to-your-organizations-project-boards -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md index 46026bf2cd..ce2cea00e0 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories.md @@ -5,7 +5,7 @@ redirect_from: - /articles/permission-levels-for-an-organization-repository/ - /articles/managing-access-to-your-organization-s-repositories - /articles/managing-access-to-your-organizations-repositories -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md index 78c2b50d37..de6be14489 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board.md @@ -55,6 +55,6 @@ Cuando eliminas a un colaborador de un tablero de proyecto, es posible que conse {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %} -### Further reading +### Leer más - [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md index ce45b95e39..996488cbc2 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository.md @@ -29,7 +29,7 @@ Cuando eliminas a un colaborador de un repositorio en tu organización, el colab 6. En la página "Manage access" (Administrar el acceso), al lado del repositorio, haz clic en **Manage access (Administrar el acceso)**. ![Botón de administración de acceso a un repositorio](/assets/images/help/organizations/repository-manage-access.png) 7. Revisa el acceso de la persona a un repositorio determinado, como si fuera un colaborador o si tuviera acceso a un repositorio por medio de una membresía de equipo. ![Matriz de acceso a repositorio para el usuario](/assets/images/help/organizations/repository-access-matrix-for-user.png) -### Further reading +### Leer más {% if currentVersion == "free-pro-team@latest" %}- "[Limitar las interacciones con tu repositorio](/articles/limiting-interactions-with-your-repository)"{% endif %} - "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md index 1a08d79297..2d7db53a53 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -16,6 +16,6 @@ Para conservar el acceso a los bot y a las cuentas de servicio, los administrado {% endwarning %} -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md index 230e47b254..643f56020a 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization.md @@ -58,6 +58,6 @@ Las etiquetas predeterminadas se incluirán en todos los repositorios nuevos de {% data reusables.project-management.delete-label %} {% data reusables.project-management.confirm-label-deletion %} -### Further reading +### Leer más - "[Acerca de las etiquetas](/articles/about-labels)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md index 041367a88c..52d5e3b2d0 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -19,7 +19,7 @@ Predeterminadamente, los miembros de la organización que tengan acceso de lectu 5. Debajo de "Debates del repositorio", selecciona o deselecciona **Permitir que los usuarios con acceso de lectura creen debates**. ![Casilla de verificación para permitir que las personas con acceso de lectura creen debates](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) 6. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración de debates](/assets/images/help/discussions/click-save.png) -### Further reading +### Leer más - "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Administrar debates para tu comunidad](/discussions/managing-discussions-for-your-community)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md index bf0641ab90..33e888ed7b 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories.md @@ -1,7 +1,7 @@ --- title: Administrar el acceso de Git a los repositorios de tu organización intro: Puedes agregar una autoridad de certificados (CA) SSH a tu organización y permitir que los miembros accedan a los repositorios de la organización sobre Git mediante claves firmadas por la CA SSH. -mapTopic: verdadero +mapTopic: true product: '{% data reusables.gated-features.ssh-certificate-authorities %}' redirect_from: - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities/ diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md index 562096b051..81c5d00aa0 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization.md @@ -4,7 +4,7 @@ intro: 'Después de que creas tu organización, puedes {% if currentVersion == " redirect_from: - /articles/removing-a-user-from-your-organization/ - /articles/managing-membership-in-your-organization -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md index 9350a93c05..d371867ba1 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings.md @@ -1,7 +1,7 @@ --- title: Administrar configuraciones de la organización intro: 'Los administradores de la organización pueden cambiar diversas configuraciones, incluidos los nombres de los repositorios que pertenecen a la organización y la membresía de equipo de los propietarios. Además, los administradores de la organización pueden eliminar a la organización y a todos sus repositorios.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-organization-settings versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md index 6d571356c5..9fcab3a651 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles.md @@ -4,7 +4,7 @@ intro: 'El rol de una persona en tu organización define su nivel de acceso a tu redirect_from: - /articles/managing-people-s-access-to-your-organization-with-roles - /articles/managing-peoples-access-to-your-organization-with-roles -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md index 29b8c0086e..4520330d9e 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization.md @@ -1,7 +1,7 @@ --- title: Administrar el inicio de sesión único de SAML para tu organización intro: Los administradores de la organización pueden administrar las identidades y el acceso a la organización de los miembros con el inicio de sesión único (SSO) de SAML. -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on/ - /articles/managing-saml-single-sign-on-for-your-organization diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md index f145541606..b146893106 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization.md @@ -53,7 +53,7 @@ Los propietarios de la organización pueden programar un recordatorio para uno m ![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) {% data reusables.reminders.delete %} -### Further reading +### Leer más - "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" - "[Administrar los recordatorios programados para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md index e1dc1c80ad..05876025af 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team.md @@ -57,7 +57,7 @@ Los mantenedores de equipo y propietarios de organización pueden configurar rec ![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) {% data reusables.reminders.delete %} -### Further reading +### Leer más - "[Administrar los recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" - "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index fa9c18a924..8fcefb9f34 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -11,7 +11,7 @@ versions: ### Acerca de la administración de los parámetros de seguridad y análisis -{% 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. {% if currentVersion == "free-pro-team@latest" %}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 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. {% if currentVersion == "free-pro-team@latest" %}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 reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -23,20 +23,20 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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. +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. {% if currentVersion == "free-pro-team@latest" %}Si tu organización, o la empresa a la que pertenece, 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 %}. -![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +![Características de la {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} ### Habilitar o inhabilitar una característica para todos los repositorios existentes -You can enable or disable features for all repositories. {% if currentVersion == "free-pro-team@latest" %}The impact of your changes on repositories in your organization is determined by their visibility: +Puedes habilitar o inhabilitar las características para todos los repositorios. {% if currentVersion == "free-pro-team@latest" %}El impacto de tus cambios en los repositorios de tu organización se determina de acuerdo con su visibilidad: -- **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 %} +- **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 %} {% data reusables.advanced-security.note-org-enable-uses-seats %} @@ -63,11 +63,11 @@ You can enable or disable features for all repositories. {% if currentVersion == ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} -### Enabling or disabling a feature automatically when new repositories are added +### Habilitar o inhabilitar una característica automáticamente cuando se agregan repositorios nuevos 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. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories -{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. +1. 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 +{% if currentVersion == "free-pro-team@latest" %}, o para todos los repositorios privados nuevos,{% endif %} en tu organización. {% if currentVersion == "free-pro-team@latest" %} ![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) {% endif %} @@ -83,7 +83,7 @@ You can enable or disable features for all repositories. {% if currentVersion == {% data reusables.dependabot.beta-note %} -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. 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. +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. Predeterminadamente, el {% data variables.product.prodname_dependabot %} no puede actualizar las dependencias que se ubican en los repositorios 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. Para obtener más información, incluyendo los detalles de las limitaciones para el soporte de la dependencia privada, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". @@ -93,10 +93,10 @@ Predeterminadamente, el {% data variables.product.prodname_dependabot %} no pued 1. Da clic en **Seleccionar repositorios**. {% endif %} -### Further reading +### Leer más - [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" -- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} -- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} +- "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Mantener tus dependencias actualizacas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - "[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)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md index ee001422a1..2c288a4a1c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository.md @@ -44,6 +44,6 @@ Puedes eliminar el acceso de un equipo a un repositorio si el equipo tiene acces 6. Encima de la lista de repositorios, utiliza el menú desplegable, y haz clic en **Remove from team (Eliminar del equipo)**. ![Menú desplegable con la opción de eliminar un repositorio de un equipo](/assets/images/help/teams/remove-team-repo-dropdown.png) 7. Revisa el o los repositorios que serán eliminados del equipo, después haz clic en **Remove repositories (Eliminar repositorios)**. ![Casilla modal con una lista de repositorios a los que el equipo ya no tiene acceso](/assets/images/help/teams/confirm-remove-team-repos.png) -### Further reading +### Leer más - "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md index b75b08fd4d..585140a45f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -26,6 +26,6 @@ Si un propietario de la empresa requirió una política para el nombre de la ram 4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/organizations/repo-default-name-text.png) 5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/organizations/repo-default-name-update.png) -### Further reading +### Leer más - "[Administrar el nombre de la rama predeterminada para tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md index fbf902e05d..bf80c80693 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization.md @@ -24,7 +24,7 @@ Si permites que se bifurquen los repositorios privados{% if currentVersion == "f 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). -### Further reading +### Leer más - "[Acerca de las bifurcaciones](/articles/about-forks)" - "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..162aec289f --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Administrar la publicación de sitios de GitHub Pages de tu organización +intro: 'Puedes controlar si los miembros de tu organización pueden publicar sitios de {% data variables.product.prodname_pages %} desde los repositorios que le pertenecen{% if currentVersion == "free-pro-team@latest" %} y restringir las visibilidades que estos eligen para dichos sitios{% endif %}.' +permissions: 'Los propietarios de las organizaciones pueden administrar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios que les pertenezcan.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization +--- + +{% if currentVersion == "free-pro-team@latest" %} +Si tu organización utiliza +{% data variables.product.prodname_ghe_cloud %}, puedes elegir el permitir a los miembros de la organización crear sitios que se publican al público en general, privados, ambos o ninguno. De lo contrario, puedes elegir permitir o dejar de permitir las publicaciones al público en general. Para obtener más información acerca del control de accesos de los sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% endif %} + +Si dejas de permitir la publicación de sitios de {% data variables.product.prodname_pages %}, cualquier sitio que ya se haya publicado permanecerá así. Puedes anular la publicación del sitio manualmente. Para obtener más información, consulta la sección "[Anular la publicación de un sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/unpublishing-a-github-pages-site)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Debajo de "Creación de páginas", selecciona las visibilidades que quieras permitir y deselecciona aquellas que quieres dejar de permitir. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Debajo de "Creación de páginas", selecciona y deselecciona **Permitir a los miembros publicar sitios**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Haz clic en **Save ** (guardar). + +### Leer más + +- "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md index ac3876f1fd..59dc822364 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -15,9 +15,9 @@ También puedes inhabilitar las actualizaciones de las cuentas que tu organizaci {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} -1. Debajo de "correo electrónico de actualización de patrocinios (Privado)", teclea la dirección de correo electrónico de la cual deseas recibir actualizaciones sobre las cuentas que patrocina tu organización. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. Debajo de "correo electrónico de actualización de patrocinios (Privado)", teclea la dirección de correo electrónico de la cual deseas recibir actualizaciones sobre las cuentas que patrocina tu organización. ![Casilla de texto para ingresar una dirección de correo electrónico para recibir actualizaciones de las cuentas patrocinadas](/assets/images/help/sponsors/organization-update-email-textbox.png) 1. Haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/organizations/update-profile-button.png) -### Further reading +### Leer más - "[Apoyar a la comunidad de código abierto con {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" \ No newline at end of file diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md index 447439fd04..58a7b292db 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions.md @@ -1,7 +1,7 @@ --- title: Migrar a permisos de organización mejorados intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización incluye los permisos de la organización mejorados por defecto. Es posible que las organizaciones creadas antes de septiembre de 2015 necesiten migrar a los antiguos equipos de administradores para el modelo mejorado de permisos de la organización.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/improved-organization-permissions/ - /articles/github-direct-organization-membership-pre-release-guide/ diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md index 175875daba..9599504158 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -33,6 +33,6 @@ Los propietarios de la organización pueden cambiar el padre de cualquier equipo {% data reusables.repositories.changed-repository-access-permissions %} 9. Haz clic en **Confirm new parent team (Confirmar nuevo equipo padre)**. ![Casilla modal para información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) -### Further reading +### Leer más - [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md index c04c48ba04..ae581e4bf7 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams.md @@ -11,7 +11,7 @@ redirect_from: - /articles/maintaining-teams-improved-organization-permissions/ - /articles/maintaining-teams/ - /articles/organizing-members-into-teams -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index df95492015..e1981db0b8 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ Los miembros de la organización pueden tener roles de *propietario*{% if curren {% if currentVersion == "free-pro-team@latest" %} -| Acción de organización | Propietarios | Miembros | Gerentes de facturación | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:------------:|:--------:|:--------------------------------------------------:| -| 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** | | -| 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](/github/setting-up-and-managing-organizations-and-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](/articles/about-your-organization-s-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 de correo electrónico a los dominios verificados (consulta la sección "[Restringir las notificaciones de correo electrónico a un dominio aprobado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" para obtener 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** | | -| [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** | | -| 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** | | -| 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** | | -| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/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](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | -| Editar y eliminar debates de equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **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** | | |{% if currentVersion == "free-pro-team@latest" %} -| 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** | | |{% endif %} -| 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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para obener más detalles) | **X** | **X** | | -| Administrar las actualizaciones de las cuentas patrocinadas (consulta la sección "[Administrar las actualizaciones de los patrocinadores de tu organización](/github/setting-up-and-managing-organizations-and-teams/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](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obtener más detalles) | **X** | | | -| Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios en la organización (consulta "[Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para encontrar 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles) | **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](/github/setting-up-and-managing-organizations-and-teams/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** | | |{% if currentVersion != "github-ae@latest" %} -| 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** | | | -| 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** | | |{% endif %} -| [Administrar la política de bifurcación](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Limitar la actividad en repositorios públicos en una organización](/articles/limiting-interactions-in-your-organization) | **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 el nombre de la rama predeterminada (consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" para obtener más detalles) | **X** | | | +| Acción de organización | Propietarios | Miembros | Gerentes de facturación | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------:|:--------:|:-----------------------:| +| 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** | | +| 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](/github/setting-up-and-managing-organizations-and-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](/articles/about-your-organization-s-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 de correo electrónico a los dominios verificados (consulta la sección "[Restringir las notificaciones de correo electrónico a un dominio aprobado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" para obtener 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** | | +| [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** | | +| 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** | | +| 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** | | +| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/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](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | +| Editar y eliminar debates de equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | +| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para obener más detalles) | **X** | **X** | | +| Administrar las actualizaciones de las cuentas patrocinadas (consulta la sección "[Administrar las actualizaciones de los patrocinadores de tu organización](/github/setting-up-and-managing-organizations-and-teams/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](/github/supporting-the-open-source-community-with-github-sponsors/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](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles) | **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](/github/setting-up-and-managing-organizations-and-teams/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** | | | +| 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** | | | +| [Administrar la política de bifurcación](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limitar la actividad en repositorios públicos en una organización](/articles/limiting-interactions-in-your-organization) | **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 el nombre de la rama predeterminada (consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" para obtener más detalles) | **X** | | | {% 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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| 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](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} -| 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](/articles/about-your-organization-s-profile)" para obtener 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** | -| 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](/articles/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](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | -| Editar y eliminar debates del equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/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** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios en la organización (consulta "[Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para encontrar 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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |{% endif %} +| 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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| 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](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| 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](/articles/about-your-organization-s-profile)" para obtener 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** | +| 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](/articles/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](/articles/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](/articles/managing-disruptive-comments)) | **X** | | | +| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/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** | | |{% if currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} {% endif %} @@ -132,7 +135,7 @@ Cuando designas un usuario como administrador de {% data variables.product.prodn 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 %} -### Further reading +### Leer más - "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" - [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md index 4fe1d60f49..5531cd617d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -18,6 +18,6 @@ Antes de aplicar un SSO de SAML en tu organización, deberías: {% data reusables.saml.outside-collaborators-exemption %} -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index 8a143c011a..ae74feecab 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,9 +30,9 @@ Por ejemplo, si el propietario de la organización ha otorgado a todos los miemb ### Visibilidad del tablero de proyecto -{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". +{% data reusables.project-management.project-board-visibility %} puedes cambiar la visibilidad del tablero de proyecto de privado a {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} y de vuelta. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". -### Further reading +### Leer más - "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)." - "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md index 3e1242777b..30d38a2363 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization.md @@ -54,6 +54,6 @@ Si tu organización tiene una suscripción de pago por usuario, debes de contar {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} {% endif %} -### Further reading +### Leer más - "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md index fa39ab39a7..e43305992c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization.md @@ -51,6 +51,6 @@ Para ayudar con la transición de la persona que estás eliminando de tu organiz 5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Remove from organization** (Eliminar de la organización). ![Menú desplegable con la opción para eliminar miembros](/assets/images/help/teams/user-bulk-management-options.png) 6. Revisa el miembro o los miembros que se eliminarán de la organización, luego haz clic en **Remove members** (Eliminar miembros). ![Lista de miembros que se eliminarán y botón Remove members (Eliminar miembros)](/assets/images/help/teams/confirm-remove-members-bulk.png) -### Further reading +### Leer más - "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md index eecac1cfb0..325fb9166c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository.md @@ -47,7 +47,7 @@ Si solo quieres eliminar un colaborador externo de determinados repositorios de 7. Para eliminar por completo el acceso del colaborador externo al repositorio, en la esquina superior derecha, haz clic en **Remove access to this repository** (Eliminar acceso a este repositorio). ![Botón Remove access to this repository (Eliminar acceso a este repositorio)](/assets/images/help/organizations/remove-access-to-this-repository.png) 8. Para confirmar, haz clic en **Remove access** (Eliminar acceso). ![Confirmar el colaborador externo que se eliminará del repositorio](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) -### Further reading +### Leer más - "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" - "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md index fc6865b487..c595d8822d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization.md @@ -32,7 +32,7 @@ Para más información sobre los permisos del administrador de {% data variables 1. En "App managers" (Administradores de app), encuentra el nombre de usuario de la persona para la que quieres eliminar {% data variables.product.prodname_github_app %} los permisos de administrador, luego haz clic en **Revoke** (Revocar). ![Revocar {% data variables.product.prodname_github_app %} permisos de administrador](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" {% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md index a25c410fcf..41b57b99ba 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization.md @@ -40,7 +40,7 @@ Después de cambiar el nombre de tu organización: {% data reusables.organizations.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) -### Further reading +### Leer más * "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)" * "[¿Por qué mis confirmaciones están vinculadas al usuario incorrecto?](/articles/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 94595eee7b..4ff360d9b1 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: Niveles de permiso del repositorio para una organización intro: 'Puedes personalizar el acceso a cada repositorio de tu organización con niveles de permiso granulares, dándoles a las personas acceso a las funciones y tareas que necesitan.' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,97 +43,126 @@ Además de administrar los parámetros al nivel de la organización, los propiet {% endwarning %} ### Acceso al repositorio para cada nivel de permiso +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} -| Acción del repositorio | Read | Triage | Escritura | Mantenimiento | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:---------:|:-------------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| -| 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 abrieron ellos mismos | **X** | **X** | **X** | **X** | **X** | -| Reabrir propuestas que cerraron ellos mismos | **X** | **X** | **X** | **X** | **X** | -| Recibir la asignación de una propuesta | **X** | **X** | **X** | **X** | **X** | -| Enviar solicitudes de extracción desde bifurcaciones de repositorios asignados del equipo | **X** | **X** | **X** | **X** | **X** | -| Enviar revisiones o solicitudes de extracción | **X** | **X** | **X** | **X** | **X** | -| Ver lanzamientos publicados | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 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 wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Informar contenido abusivo o de spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Apply/dismiss labels | | **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** |{% if currentVersion == "free-pro-team@latest" %} -| [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** | -| 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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversaciones](/articles/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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [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** | -| [Borrar paquetes](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} -| Limitar las [interacciones en un repositorio](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" %} -| 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 %} -| Administrar webhooks y desplegar llaves | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Habilitar el gráfico de dependencias](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) de un repositorio privado | | | | | **X** | -| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en un repositorio | | | | | **X** | -| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para las dependencias vulnerables | | | | | **X** | -| [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** | -| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [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 %} -| [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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %} +**Nota:** Los permisos del repositorio que se requieren para utilizar las características de seguridad se listan en la sección "[Requisitos de los permisos para las características de seguridad](#permission-requirements-for-security-features)" que se encuentra más adelante. -### Further reading +{% endnote %} +| +{% endif %} +| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:---------:|:-------------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| 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 wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Informar contenido abusivo o de spam](/articles/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** |{% if currentVersion == "free-pro-team@latest" %} +| [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** | +| 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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversaciones](/articles/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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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** | +| [Borrar paquetes](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} +| Limitar las [interacciones en un repositorio](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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** |{% if currentVersion == "free-pro-team@latest" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Requisitos de permisos para características de seguridad + +En esta sección, puedes encontrar los niveles de permisos de repositorios que se requieren para las características de seguridad, tales como las del {% data variables.product.prodname_dependabot %} y de {% data variables.product.prodname_advanced_security %}. + +| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:---------:|:-------------:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en un repositorio | | | | | **X** | +| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para las dependencias vulnerables | | | | | **X** | +| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [Habilitar el gráfico de dependencias](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) de un repositorio privado | | | | | **X** | +| [Ver las revisiones de las dependencias](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [Ver las alertas del {% data variables.product.prodname_secret_scanning %} en un repositorio](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Eliminar, revocar o reabrir las alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [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 %} +{% endif %} + +### Leer más - [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)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md index 547b93fae9..ff66757125 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team.md @@ -25,7 +25,7 @@ Si eres propietario de una organización o tienes permisos de mantenedor del equ {% data reusables.repositories.changed-repository-access-permissions %} 9. Haz clic en **Confirm changes** (Confirmar cambios) para enviar una solicitud para agregar al equipo hijo. ![Casilla modal para información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) -### Further reading +### Leer más - [Acerca de los equipos](/articles/about-teams)" - "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md index 2cb0d48a7e..cc0c80e7bd 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team.md @@ -25,7 +25,7 @@ Si eres propietario de la organización o tienes permisos de mantenedor del equi {% data reusables.repositories.changed-repository-access-permissions %} 9. Haz clic en **Confirm changes** (Confirmar cambios) para enviar una solicitud para agregar o modificar el padre de tu equipo. ![Casilla modal para información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) -### Further reading +### Leer más - [Acerca de los equipos](/articles/about-teams)" - "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md index 1dcdefd7e7..68d1cc0012 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.md @@ -68,7 +68,7 @@ Para ver las personas que se eliminaron automáticamente de tu organización por Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización. -### Further reading +### Leer más - "[Ver si los usuarios de tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" - "[Proteger tu cuenta con autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md index 9d5ff5279a..8f96e3795b 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data.md @@ -4,7 +4,7 @@ intro: '{% data variables.product.prodname_oauth_app %} las restricciones de acc redirect_from: - /articles/restricting-access-to-your-organization-s-data - /articles/restricting-access-to-your-organizations-data -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md index ea8c106e59..a0f389a997 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization.md @@ -25,6 +25,6 @@ Puedes restringir la habilidad de cambiar la visibilidad de un repositorio para 5. En "Repository visibility change" (Cambio en la visibilidad de los repositorios), anula la selección de **Allow members to change repository visibilities for this organization** (Permitir que los miembros cambien las visibilidades de los repositorios para esta organización). ![Casilla para permitir que los miembros cambien la visibilidad de los repositorios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) 6. Haz clic en **Save ** (guardar). -### Further reading +### Leer más - "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index a586ebf70c..762350ace5 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -27,46 +27,46 @@ La bitácora de auditoría lista los eventos que activan las actividades, los cu 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: -| Nombre de la categoría | Descripción | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| [`account`](#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)". | -| [`billing`](#billing-category-actions) | Contiene todas las actividades relacionadas con la facturación 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)". | +| Nombre de la categoría | Descripción | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`account`](#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)". | +| [`billing`](#billing-category-actions) | Contiene todas las actividades relacionadas con la facturación 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 publicados en una página de equipo. | -| [`hook`](#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. | -| [`issue`](#issue-category-actions) | Contiene las actividades relacionadas con borrar una propuesta. |{% if currentVersion == "free-pro-team@latest" %} -| [`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 a listar apps en {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contiene todas las actividades relacionadas con inhabilitar 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 "[Restringir la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". |{% 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 publicados en una página de equipo. | +| [`hook`](#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. | +| [`issue`](#issue-category-actions) | Contiene las actividades relacionadas con borrar una propuesta. |{% if currentVersion == "free-pro-team@latest" %} +| [`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 listar aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". |{% endif %} | [`org`](#org-category-actions) | Contiene las actividades relacionadas con la membrecía de la organización.{% if currentVersion == "free-pro-team@latest" %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contiene todas las actividades relacionadas con autorizar credenciales para su uso con el inicio de sesión único de SAML.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} | [`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. |{% if currentVersion == "free-pro-team@latest" %} +| [`oauth_application`](#oauth_application-category-actions) | Contiene todas las actividades relacionadas con las Apps de OAuth. |{% if currentVersion == "free-pro-team@latest" %} | [`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. | +| [`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.{% if currentVersion == "free-pro-team@latest" %} -| [`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_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 %}{% if currentVersion != "github-ae@latest" %} -| [`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 {% if currentVersion == "free-pro-team@latest" %}privado{% endif %}. 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)".{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | -| [`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). |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`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 {% if currentVersion == "free-pro-team@latest" %}privado{% endif %}. 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)".{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | +| [`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). |{% endif %}{% if currentVersion != "github-ae@latest" %} | [`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 %}{% if currentVersion == "free-pro-team@latest" %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contiene las actividades de configuración a nivel de repositorio para las alertas del {% data variables.product.prodname_dependabot %}. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [`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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contiene las actividades de configuración a nivel de repositorio para las alertas del {% data variables.product.prodname_dependabot %}. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [`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 %} -| [`team`](#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. | +| [`team`](#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. | Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: @@ -128,7 +128,7 @@ Para garantizar una IP segura y mantener el cumplimiento para tu organización, {% data reusables.audit_log.audit-log-api-info %} {% if currentVersion == "free-pro-team@latest" %} -Ten en cuenta que no puedes recuperar los eventos de Git utilizando la API de GraphQL. +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)". {% endif %} La respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. @@ -141,7 +141,7 @@ Por ejemplo, puedes hacer una solicitud de GraphQL para ver todos los miembros n {% note %} -**Nota**: La API de bitácora de auditoría de REST se encuentra disponible como un beta limitado únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para unirse al beta, habla con tu contacto de servicios o de ventas en {% data variables.product.company_short %}. +**Note:** The audit log REST API is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. {% endnote %} @@ -198,7 +198,7 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos | Acción | Descripción | | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `disable` | Se activa cuando el propietario de una organización inhabilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | +| `enable` | Se activa cuando un propietario de organización habilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}nuevos. | #### Acciones de la categoría `dependabot_security_updates` @@ -250,7 +250,7 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos {% 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. Esta funcionalidad se encuentra disponible como un beta limitado únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para unirse al beta, habla con tu contacto de servicios o de ventas en {% data variables.product.company_short %}. +**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. This functionality is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. Para obtener más información sobre la API de bitácora de auditoría de REST, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)" en la documentación de la API de REST. @@ -308,11 +308,11 @@ Para obtener más información sobre la API de bitácora de auditoría de REST, {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} #### Acciones de la categoría `members_can_create_pages` -Para obtener más información, consulta la sección "[Restringir la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". +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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". | Acción | Descripción | |:--------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -325,8 +325,8 @@ Para obtener más información, consulta la sección "[Restringir la publicació | Acción | Descripción | | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest"%} -| `advanced_security_disabled` | Triggered when an organization admin disables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | -| `advanced_security_enabled` | Triggered when an organization admin enables {% data variables.product.prodname_GH_advanced_security %} for all existing private and internal repositories. | +| `advanced_security_disabled` | Se activa cuando un administrador de organización inhabilita la {% data variables.product.prodname_GH_advanced_security %} para todos los repositorios privados e internos existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". | +| `advanced_security_enabled` | Se activa cuando un administrador de organización habilita la {% data variables.product.prodname_GH_advanced_security %} para todos los repositorios internos y privados. | | `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](/articles/blocking-a-user-from-your-organization). | | `cancel_invitation` | Se activa cuando se revocó una invitación de la organización. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} @@ -345,7 +345,8 @@ Para obtener más información, consulta la sección "[Restringir la publicació | `oauth_app_access_requested` | Se activa cuando un miembro de la organización solicita que un propietario otorgue un acceso de una {% data variables.product.prodname_oauth_app %} para tu organización.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `register_self_hosted_runner` | Se activa cuando un propietario de la organización [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | | `remove_actions_secret` | Se activa cuando el administrador de una organización elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %}{% if currentVersion == "free-pro-team@latest"%} -| `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_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/){% if currentVersion != "github-ae@latest" %} 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{% if currentVersion != "github-ae@latest" %} 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 %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_self_hosted_runner` | Se activa cuando un propietario de la organización [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). |{% endif %}{% if currentVersion == "free-pro-team@latest" %} @@ -419,10 +420,10 @@ Para obtener más información, consulta la sección "[Restringir la publicació | Acción | Descripción | | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `create (crear)` | Se activa cuando se crear un tablero de proyecto. | -| `enlace` | Se activa cuando un repositorio se vincula a 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. | | `update` | Se activa cuando se actualiza un tablero de proyecto. | -| `eliminar` | Se activa cuando se elimina 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. | @@ -450,17 +451,17 @@ Para obtener más información, consulta la sección "[Restringir la publicació #### acciones de la categoría `repo` -| 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. | -| `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.{% if currentVersion == "free-pro-team@latest" %} -| `advanced_security_disabled` | Triggered when a repository owner disables {% data variables.product.prodname_GH_advanced_security %}. 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` | Triggered when a repository owner enables {% data variables.product.prodname_GH_advanced_security %}.{% endif %} +| 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. | +| `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)` | Se activa cuando un administrador de repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a un repositorio.{% if currentVersion == "free-pro-team@latest" %} +| `advanced_security_disabled` | Se activa cuando un propietario de repositorio inhabilita la {% data variables.product.prodname_GH_advanced_security %}. 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 propietario de repositorio habilita la {% data variables.product.prodname_GH_advanced_security %}.{% endif %} | `archived (archivado)` | Se activa cuando un administrador del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} -| `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.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)` | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `create_actions_secret` | Se activa cuando un administrador de repositorio [crea un secreto de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).{% endif %} @@ -469,12 +470,12 @@ Para obtener más información, consulta la sección "[Restringir la publicació | `enable` | Se activa cuando se rehabilita un repositorio{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_actions_secret` | Se activa cuando un administrador de repositorio elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %} | `remove_member (eliminar miembro)` | Se activa cuando un usuario se [elimina de su puesto de colaborador en un repositorio](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `register_self_hosted_runner` | Se activa cuando un administrador del repositorio [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `remove_self_hosted_runner` | Se activa cuando un administrador del repositorio [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} -| `remove_topic (eliminar tema)` | Se activa cuando un administrador del repositorio elimina un tema de un repositorio. | -| `rename (renombrar)` | Se activa cuando [se renombra un repositorio](/articles/renaming-a-repository). | -| `transfer` | 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. | +| `register_self_hosted_runner` | Se activa cuando un administrador del repositorio [registra un ejecutor auto-hospedado nuevo](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | +| `remove_self_hosted_runner` | Se activa cuando un administrador del repositorio [elimina un ejecutor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} +| `remove_topic (eliminar tema)` | Se activa cuando un administrador del repositorio elimina un tema de un repositorio. | +| `rename (renombrar)` | Se activa cuando [se renombra un repositorio](/articles/renaming-a-repository). | +| `transfer` | 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)` | Se activa cuando un administrador de repositorio deja de archivar un repositorio.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `update_actions_secret` | Se activa cuando un administrador de repositorio actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %} @@ -564,7 +565,7 @@ Para obtener más información, consulta la sección "[Restringir la publicació | `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de una cuenta patrocinada (consulta "[Administrar tu patrocinio](/articles/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 "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | -| `sponsored_developer_create (creación de programador patrocinado)` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create (creación de programador patrocinado)` | Se activa cuando la cuenta de {% data variables.product.prodname_sponsors %} se crea (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | | `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Se activa cuando editas tu perfil de organización patrocinada (consulta "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-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 "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-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 "[Cambiar tus niveles de patrocinio](/articles/changing-your-sponsorship-tiers)") | @@ -575,16 +576,16 @@ Para obtener más información, consulta la sección "[Restringir la publicació #### acciones de la categoría `team` -| 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)` | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| 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.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `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. +`demote_maintainer` | Se activa cuando se baja de categoría a un usuario de mantenedor de equipo a miembro de equipo. Para obtener más información, consulta la sección "[Otorgar permisos de "mantenedor de equipo" a un miembro de la organización](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Se activa cuando se borra un equipo de la organización.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Se activa cuando se promueve a un usuario de miembro de equipo a mantenedor de equipo. Para obtener más información, consulta la sección "[Otorgar permisos de "mantenedor de equipo" a un miembro de la organización](/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Se activa cuando un miembro de una organización se [elimina de un equipo](/articles/removing-organization-members-from-a-team). | `remove_repository` | Se activa cuando un repositorio ya no está bajo el control de un equipo. #### acciones de la categoría `team_discussions` @@ -593,6 +594,6 @@ Para obtener más información, consulta la sección "[Restringir la publicació | `disable` | 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)". | | `enable` | Se activa cuando un propietario de la organización habilita los debates de equipo para una organización. | -### Further reading +### Leer más - "[Mantener segura tu organización](/articles/keeping-your-organization-secure)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md index b7fe5cccbf..8c9e684f2a 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization.md @@ -25,7 +25,7 @@ Si alguien con permisos administrativos en un repositorio de la organización ot 5. Debajo de "Permisos Base", utiliza el menú desplegable para seleccionar los nuevos permisos base. ![Selección de nuevo nivel de permiso desde el menú desplegable de "permisos base"](/assets/images/help/organizations/base-permissions-drop-down.png) 6. Revisa los cambios. Da clic en **Cambiar el permiso predeterminado por PERMISO** para confirmar. ![Revisar y confirmar el cambio de permisos base](/assets/images/help/organizations/base-permissions-confirm.png) -### Further reading +### Leer más - "[Niveles de permisopara una organización en un repositorio](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" - "[Añadir colaboradores externos a los repositorios de tu organización](/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index fcca3f5725..bf4de328f8 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,7 +15,7 @@ versions: Puedes conectar hasta cinco grupos de IdP a un equipo de {% data variables.product.prodname_dotcom %}. Un grupo de IdP puede asignarse a varios equipos de {% data variables.product.prodname_dotcom %} sin restricción. -Team synchronization does not support IdP groups with more than 5000 members. +La sincronización de equipos no es compatible con grupos de IdP que tengan más de 5000 miembros. Una vez que un equipo de {% data variables.product.prodname_dotcom %} se conecta a un grupo de IdP, tu administrador de IdP debe hacer cambios en la membrecía del equipo a través del proveedor de identidad. No puedes administrar la membrecía del equipo en {% data variables.product.product_name %} ni utilizando la API. @@ -29,22 +29,22 @@ También puedes administrar la sincronización de equipos con la API. Para obten ### Requisitos para los miembros de los equipos sincronizados -After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.prodname_dotcom %} only if: -- The person is a member of the organization on {% data variables.product.prodname_dotcom %}. -- The person has already logged in with their user account on {% data variables.product.prodname_dotcom %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. -- The person's SSO identity is a member of the IdP group. +Después de que conectas un equipo a un grupo de IdP, la sincronización de equipos agregará a cada miembro del grupo de IdP al equipo correspondiente en {% data variables.product.prodname_dotcom %} únicamente si: +- La persona es un miembro de la organización en {% data variables.product.prodname_dotcom %}. +- La persona ya ingresó con su cuenta de usuario en {% data variables.product.prodname_dotcom %} y se autenticó en la cuenta organizacional o empresarial a través del inicio de sesión único de SAML por lo menos una vez. +- La identidad de SSO de la persona es miembro del grupo de IdP. -Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.prodname_dotcom %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." +Los equipos o miembros del grupo existentes que no cumplan con estos criterios se eliminarán automáticamente del equipo en {% data variables.product.prodname_dotcom %} y perderán acceso a los repositorios. El revocar la identidad ligada a un usuario también eliminará a dicho usuario de cualquier equipo que se encuentre mapeado en los grupos de IdP. Para obtener más información, consulta las secciones "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" y [Visualizar y administrar el acceso de SAML de un usuario a tu empresa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)". Puedes volver a agregar automáticamente a aquellos miembros del equipo que hayas eliminado una vez que se autentiquen en la cuenta empresarial u organizacional utilizando el SSO y así se migren al grupo de IdP conectado. -Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. Para obtener más información, consulta las secciones "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" y "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". -Si tu organización pertenece a una cuenta empresarial, habilitar la sincronización de equipos para la cuenta empresarial anulará la configuración de sincronización de equipos a nivel organizacional. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Si tu organización pertenece a una cuenta empresarial, habilitar la sincronización de equipos para la cuenta empresarial anulará la configuración de sincronización de equipos a nivel organizacional. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". ### Prerrequisitos -Antes de poder conectar a un equipo con un grupo de proveedor de identidad, un propietario de organización o de empresa debe habilitar la sincronización de equipos para tu organización o cuenta empresarial. For more information, see "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Antes de poder conectar a un equipo con un grupo de proveedor de identidad, un propietario de organización o de empresa debe habilitar la sincronización de equipos para tu organización o cuenta empresarial. Para obtener más información, consulta las secciones "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" y "[Administrar la sincronización de equipos para las orgnizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". Para evitar el eliminar miembros del equipo accidentalmente, visita el protal administrativo para tu IdP y confirma que cada miembro actual del equipo también se encuentre en los grupos de IdP que quieras conectar a este equipo. Si no tienes este acceso a tu proveedor de identidad, puedes comunicarte con tu administrador de IdP. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md index f4a1a8f6eb..5b2b8c5fc4 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service.md @@ -18,5 +18,5 @@ Los Términos de servicio estándar son un acuerdo entre {% data variables.produ 5. Escribe el nombre de la empresa, organización sin fines de lucro o grupo al que le pertenece la cuenta de la organización. Esta es la entidad que celebrará el acuerdo con {% data variables.product.prodname_dotcom %}. ![Campo del nombre de la empresa](/assets/images/help/organizations/business-name-field.png) 6. Para aceptar los Términos de servicio corporativos en nombre de tu entidad, haz clic en **Accept terms** (Aceptar términos). ![Botón Accept terms (Aceptar términos)](/assets/images/help/organizations/accept-terms-button.png) -### Further reading +### Leer más - "[Términos de servicio corporativos de GitHub](/articles/github-corporate-terms-of-service/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index ad8b1be621..046b054212 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -54,7 +54,7 @@ Puedes ver y revocar la identidad vinculada de cada miembro, sesiones activas y {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} -### Further reading +### Leer más - "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" - "[Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md index b2f1f5c534..7b03534165 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization.md @@ -40,7 +40,7 @@ Con la información sobre las dependencias puedes ver vulnerabilidades, licencia 7. Puedes hacer clic en {% octicon "package" aria-label="The package icon" %} **dependents (dependientes)** al lado de cada vulnerabilidad para ver qué dependiente en tu organización está usando cada biblioteca. ![Dependientes vulnerables de mis organizaciones](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) - ### Further reading + ### Leer más - "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" - "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md index f5e3691604..92cf7c9adf 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -21,6 +21,6 @@ versions: 5. Para ver los colaboradores externos en tu organización, dentro de la pestaña "People" (Personas), haz clic en **Outside collaborators (Colaboradores externos)**. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) 6. Para ver qué colaboradores externos han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) -### Further reading +### Leer más - "[Ver los roles de las personas en un organización](/articles/viewing-people-s-roles-in-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index e4fb6eda76..02c7a169cf 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -1,31 +1,31 @@ --- -title: About identity and access management for your enterprise account -intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +title: Acerca de la administración de accesos e identidades para tu cuenta empresarial +intro: Puedes administrar centralmente el acceso a los recursos de tu empresa, membrecía de tu organización y de tu equipo utilizando a tu proveedor de identidad (IdP). product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' --- -### About identity and access management for your enterprise account +### Acerca de la administración de accesos e identidades para tu cuenta empresarial -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} Para obtener más información, consulta la sección "[Habilitar el inicio de sesión único para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". -After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. +Después de que habilites el SSO de SAML, dependiendo del IdP que utilizas, debes poder habilitar las características de administración de acceso y de identidad adicionales. -{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.about-user-provisioning-enterprise-account %} Para obtener más información, consulta la sección "[Acerca del aprovisionamiento de usurios para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". -If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Si utilizas Azure AD como tu IdP, puedes utilizar la sincronización de equipos para administrar la membresía del equipo dentro de cada organización. {% data reusables.identity-and-permissions.about-team-sync %} Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". -### Supported IdPs +### IdP compatibles -We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. Para obtener más información, consulta la sección [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio web de OASIS. +Probamos y damos compatibilidad oficial de los siguientes IdP. Para el SSO de SAML, ofrecemos soporte limitado para todos los proveedores de identidad que implementan el SAML 2.0 estándar. Para obtener más información, consulta la sección [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio web de OASIS. -| IdP | SAML | User provisioning | Sincronización de equipos | -| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | Aprovisionamiento de usuarios | Sincronización de equipos | +| -------------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md index ea52a2c463..a89921c52e 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: About user provisioning for organizations in your enterprise account -intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +title: Acerca del aprovisionamiento de usuarios para las organizaciones en tu cuenta empresarial +intro: Puedes administrar la membrecía organizacional en una cuenta empresarial directamente desde un proveedor de identidad (IdP). product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' @@ -12,7 +12,7 @@ versions: {% data reusables.scim.enterprise-account-scim %} Opcionalmente, puedes habilitar el aprovisionamiento de SAML y, por separado, el desaprovisionamiento. -If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. Si habilitas el aprovisionamiento de SAML, cada que un miembro de la empresa acceda a un recurso que protege tu configuración de SAML en la cuenta de la empresa, esa aserción de SAML activará el aprovisionamiento. +Si configuras el SCIM para la aplicación de {% data variables.product.product_name %} en tu IdP, cada vez que hagas cambios a la membrecía de grupo de tu IdP, éste hará un llamado de SCIM a {% data variables.product.prodname_dotcom %} para actualizar la membrecía organizacional correspondiente. Si habilitas el aprovisionamiento de SAML, cada que un miembro de la empresa acceda a un recurso que protege tu configuración de SAML en la cuenta de la empresa, esa aserción de SAML activará el aprovisionamiento. Para cada llamada de SCIM o aserción de SAML, {% data variables.product.product_name %} verificará los grupos de IdP a los cuales pertenece el usuario y realizará las siguientes operaciones: diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md index 3dd5bdf2ae..2e1d9a2c7b 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -1,8 +1,8 @@ --- title: Configuring identity and access management for your enterprise account -intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index 0448ef0e0f..0218c119af 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -1,13 +1,13 @@ --- title: Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta de empresa -intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +intro: 'Puedes controlar y asegurar el acceso a los recursos tales como repositorios, propuestas y solicitudes de cambios si habilitas el inicio de sesión único (SSO) de SAML y la autenticación centralizada mediante un IdP a través de todas las organizaciones que pertenezcan al acuenta emprearial.' product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +permissions: Los propietarios de la empresa pueden habilitar el inicio de sesión único de SAML para las organizaciones en una cuenta empresarial. versions: free-pro-team: '*' --- -### About SAML single sign-on for enterprise accounts +### Acerca del inicio de sesión único de SAML para las cuentas empresariales {% data reusables.saml.dotcom-saml-explanation %}Para obtener más información, consulta "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". @@ -17,9 +17,9 @@ versions: {% data reusables.saml.saml-supported-idps %} -{% data reusables.scim.enterprise-account-scim %}Si no estás participando en el beta privado, SCIM no será compatible para las cuentas empresariales. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.scim.enterprise-account-scim %}Si no estás participando en el beta privado, SCIM no será compatible para las cuentas empresariales. Para obtener más información, consulta la sección "[Acerca del aprovisionamiento de usurios para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". -### Enabling SAML single-sign on for organizations in your enterprise account +### Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta de empresa {% note %} @@ -35,8 +35,8 @@ Para obtener información más detallada sobre cómo habilitar el SAML utilizand 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} 5. En "inicio de sesión único SAML", selecciona **Habilitar autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) 6. En el campo **URL de inicio de sesión**, escribe el extremo HTTPS de tu IdP para las solicitudes de inicio de sesión único. Este valor se encuentra en la configuración de tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png) +7. Opcionalmente, en el campo **Emisor**, teclea tu URL de emisor de SAML para verificar la autenticidad de los mensajes enviados. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png) 8. En **Certificado público**, pega un certificado para verificar las respuestas de SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png) -9. Para verificar la integridad de las solicitudes de tu emisor de SAML, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png) +9. Para verificar la integridad de las solicitudes de tu emisor de SAML, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. Posteriormente, en los menús desplegables de "Método de firma" y "Método de resumen", elige el algoritmo de hash que utiliza tu emisor de SAML. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png) 10. Antes de habilitar SAML SSO para tu empresa, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_test.png) 11. Haz clic en **Save ** (guardar). diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 40db124930..3e3f567a89 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -113,6 +113,6 @@ La eliminación de un CA no se puede deshacer. Si deseas usar la misma CA en el {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} -### Further reading +### Leer más -- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" +- "[Configurar la administración de accesos e identidades para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index 4b987ae478..da672d8e5c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -15,9 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} es una oferta combinada de Microsoft que permite a los suscriptores utilizar tanto {% data variables.product.prodname_enterprise %} como {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} se encuentra disponible desde Microsoft bajo las condiciones del Acuerdo Empresarial de Microsoft. Para obtener más información, consulta la sección [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) en el sitio web de {% data variables.product.prodname_vs %}. -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 account 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 %}. +Después de que asignes una licencia para {% data variables.product.prodname_vss_ghe %} a un suscriptor, éste utilizará la porción de {% data variables.product.prodname_enterprise %} de la licencia al unirse a una organización en tu cuenta empresarial con una cuenta de usuario de {% data variables.product.prodname_dotcom_the_website %}. Si la dirección de correo electrónico para la cuent de usuario de un miembro de la empresa en {% data variables.product.prodname_dotcom_the_website %} coincide con el Nombre Primario de Usuario (UPN) para un suscriptor de tu cuenta de {% data variables.product.prodname_vs %}, dicho suscriptor de {% data variables.product.prodname_vs %} consumirá una licencia de {% data variables.product.prodname_vss_ghe %} automáticamente. -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. +La cantidad total de licencias para tu empresa en {% data variables.product.prodname_dotcom %} es la suma de todas las licencias estándar de {% data variables.product.prodname_enterprise %} y de la cantidad de licencias de suscripción de {% data variables.product.prodname_vs %} que incluyan acceso a {% data variables.product.prodname_dotcom %}. Si la cuenta de usuario de un miembro de la empresa no corresponde con la dirección de correo electrónico de un suscriptor de {% data variables.product.prodname_vs %}, la licencia que consuma esa cuenta de usuario no estará disponible para un suscriptor de {% data variables.product.prodname_vs %}. Para obtener más información acerca de {% data variables.product.prodname_enterprise %}, consulta los productos de "[{% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)." Para obtener más información acerca de las cuentas en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)". @@ -31,11 +31,13 @@ Para obtener más información acerca de {% data variables.product.prodname_ente ### Invitar a un suscriptor para que utilice {% data variables.product.prodname_enterprise %} -To use the {% data variables.product.prodname_enterprise %} portion of the license, the 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 %}. +Para utilizar la porción de {% data variables.product.prodname_enterprise %} de la licencia, la cuenta de usuario del suscriptor de {% data variables.product.prodname_dotcom_the_website %} debe ser o convertirse en miembro de una organización que pertenezca a tu empresa en {% data variables.product.prodname_dotcom_the_website %}. -Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an 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. +Los propietarios de las organizaciones pueden invitar a miembros nuevos a una organización por correo electrónico. El suscriptor puede aceptar la invitación con una cuenta de usuario existente en {% data variables.product.prodname_dotcom_the_website %} o crear una cuenta nueva. -For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." +While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. + +Para obtener más información, consulta las secciones "[Invitar a usuarios para que se unan a tu organización](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)", "[Registrarse para {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)", y "[Administrar las preferencias de correo electrónico](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)". ### Visualizar el licenciamiento de {% data variables.product.prodname_enterprise %} @@ -43,6 +45,6 @@ Después de asignar una licencia para {% data variables.product.prodname_vss_ghe También puedes ver las invitaciones pendientes de {% data variables.product.prodname_enterprise %} para los suscriptores en {% data variables.product.prodname_vss_admin_portal_with_url %}. La lista de invitaciones pendientes incluye a los suscriptores que aún no son miembros de por lo menos una organización en tu cuenta empresarial. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)". -### Further reading +### Leer más - [Introducir las suscripciones de Visual Studio con GitHub enterprise](https://docs.microsoft.com/visualstudio/subscriptions/access-github) en los documentos de Microsoft diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md index de9fdeb9b6..d69751b9a9 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account.md @@ -1,7 +1,7 @@ --- title: Administrar organizaciones en tu cuenta de empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index dea1d2cf35..42265b4695 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -1,15 +1,15 @@ --- title: Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial -intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +intro: 'Puedes habilitar la sincronización de equipos entre un proveedor de identidad (IdP) y {% data variables.product.product_name %} para permitir que las organizaciones que pertenezcan a tu cuenta empresarial administren la membrecía de equipo a través de grupos de IdP.' product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Enterprise owners can manage team synchronization for an enterprise account. +permissions: Los propietarios de las empresas pueden administrar la sincronización de equipos para una cuenta empresarial. versions: free-pro-team: '*' --- -### About team synchronization for enterprise accounts +### Acerca de la sincronización de equipos para las cuentas empresariales -If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. +Si utilizas Azure AD como tu IdP, puedes habilitar la sincronización de equipos para tu cuenta empresarial para permitir que los propietarios de la organización y mantenedores de equipo sincronicen equipos en las organizaciones que pertenezcan a tus cuentas empresariales con grupos de IdP. {% data reusables.identity-and-permissions.about-team-sync %} @@ -37,5 +37,5 @@ Debes autenticarte en tu cuenta empresarial utilizando el SSO de SAML y el IdP c {% data reusables.identity-and-permissions.team-sync-confirm-saml %} {% data reusables.identity-and-permissions.enable-team-sync-azure %} {% data reusables.identity-and-permissions.team-sync-confirm %} -7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png) +7. Revisa los detalles del organismo de IdP que quieres conectar a tu cuenta empresarial y luego da clic en **Aprovar**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png) 8. Para inhabilitar la sincronización de equipos, da clic en **Inhabilitar la sincronización de equipos**. ![Inhabilita la sincronización de equipo](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index 3c3ea187fc..126ae5ed9c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -Si habilitas el desaprovisionamiento de usuarios para administrar las membrecías organizacionales en tu cuenta empresarial, podrías terminar teniendo una organización que no tiene propietarios. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +Si habilitas el desaprovisionamiento de usuarios para administrar las membrecías organizacionales en tu cuenta empresarial, podrías terminar teniendo una organización que no tiene propietarios. Para obtener más información, consulta la sección "[Acerca del aprovisionamiento de usuarios para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". {% data reusables.enterprise-accounts.access-enterprise %} 2. A la derecha del campo de búsqueda, da clic en **X sin propietario**. ![Botón para ver las organizaciones sin propietario](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md index 8094618c1f..22c09cecc0 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise.md @@ -1,7 +1,7 @@ --- title: Administrar los usuarios en tu empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: verdadero +mapTopic: true redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md index 45fa8db88a..132e3d7011 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account.md @@ -1,7 +1,7 @@ --- title: Administrar tu cuenta de empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-your-enterprise-account versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 299ab8364e..0e13245594 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -54,7 +54,7 @@ Los gerentes de facturación solo tienen acceso a la configuración de facturaci Los gerentes de facturación no tienen acceso a las organizaciones o repositorios de tu empresa y no pueden agregar o eliminar propietarios de la misma. Los gerentes de facturación deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}. -### Further reading +### Leer más - "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md index b5235864ce..3f7a5cd4b2 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account.md @@ -1,7 +1,7 @@ --- title: Establecer políticas para organizaciones en tu cuenta de empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/setting-policies-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 7235d6935c..641112b34c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -49,6 +49,6 @@ Cuando habilitas el inicio de sesión único de SAML para tu cuenta empresarial, {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} -### Further reading +### Leer más - "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md index aaf59f61fc..7b5fcb96ae 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise.md @@ -33,6 +33,6 @@ Puedes ver {% if currentVersion == "free-pro-team@latest" %}todas las organizaci {% if currentVersion == "free-pro-team@latest" %}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 %} -### Further reading +### Leer más - "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 34bd29c347..6c11b6a96d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -26,4 +26,4 @@ Para obtener más información acerca de administrar a los gerentes de facturaci "{% if currentVersion == "free-pro-team@latest" %}Licencias{% else %}licencias{% endif %}de usuario", visualiza el total de tus licencias, cantidad de licencias utilizadas, y la fecha de vencimiento de tu suscripción. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Información de licencia y suscripción en las configuraciones de facturación de la empresa](/assets/images/enterprise/enterprises/enterprise-server-billing-license-info.png){% endif %} -1. Optionally, to view details for license usage or download a {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} +1. Opcionalmente, para ver los detalles del uso de licencia o para descargar un archivo {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %} de JSON{% endif %} con los detalles de la licencia{% if currentVersion == "free-pro-team@latest" %}, a la derecha de "Licencias de Usuario"{% endif %}, da clic en **Ver {% if currentVersion == "free-pro-team@latest" %} detalles{% elsif enterpriseServerVersions contains currentVersion %}usuarios{% endif %}** o {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Exportar uso de licencia**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index a2c854f530..89bc0fad7c 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -19,6 +19,6 @@ Opcionalmente, puedes optar por agregar una descripción, una ubicación, un sit ![Muestra de la página de perfil de una organización](/assets/images/help/profile/org_profile.png) {% endif %} -### Further reading +### Leer más - "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md index 67b00dd7a4..9ebc96d451 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md @@ -32,7 +32,7 @@ Las personas que visitan tu perfil también pueden ver la siguiente información También puedes establecer un estado en tu perfil para brindar información sobre tu disponibilidad. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". -### Further reading +### Leer más - "[¿Cómo configuro mi foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)" - "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md index c6cab2efbe..a36a961eef 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md @@ -1,7 +1,7 @@ --- title: Personalizar tu perfil intro: Puedes personalizar tu perfil para que los demás usuarios puedan comprender mejor quién eres y qué trabajo realizas. -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/customizing-your-profile versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md index 7e3757c63b..cb8c3f028f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md @@ -1,7 +1,7 @@ --- title: Administrar los gráficos de contribución en tu perfil intro: 'Tus contribuciones, incluidas las confirmaciones de cambios, las solicitudes de extracción propuestas y las propuestas abiertas, se muestran en tu perfil para que las personas puedan ver fácilmente el trabajo que has realizado.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-contribution-graphs-on-your-profile versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 1b91eed783..7eb9b50241 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ GitHub mostrará el README de tu perfil en tu página de perfil si cuentas con t El archivo de README que se ha generado está pre-llenado con una plantilla para que te inspires en completarlo. ![Archivo README con la plantilla pre-llenada](/assets/images/help/repository/personal-repository-readme-template.png) +Para encontrar un resumen de todos los emojis disponibles y de sus códigos, consulta el [Directorio de Emojis](http://www.emoji-cheat-sheet.com/)". + ### Eliminar un README de perfil El README de tu perfil se eliminará de tu perfil de {% data variables.product.prodname_dotcom %} si sucede cualquiera de los siguientes escenarios: @@ -59,6 +61,6 @@ El README de tu perfil se eliminará de tu perfil de {% data variables.product.p The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. Para encontrar los pasos de cómo hacer tu repositorio privado, consulta la sección ["Cambiar la visibilidad de un repositorio".](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility) -### Further reading +### Leer más - [Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md index e057a41793..6f0bc741ed 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md @@ -119,6 +119,6 @@ Puedes inhabilitar algunas de las insignias de los programas de {% data variable {% endif %} -### Further reading +### Leer más - "[Acerca de tu perfil](/articles/about-your-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md index 7fc3328dcb..05536d1325 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile.md @@ -24,6 +24,6 @@ Puedes reordenar los elementos en la sección "Anclados". En el ángulo superior 5. Selecciona una combinación de hasta seis repositorios o gists para mostrar. ![Seleccionar elementos](/assets/images/help/profile/select-items-to-pin.png) 6. Haz clic en **Save pins (Guardar anclados)**. ![Botón guardar elementos anclados](/assets/images/help/profile/save-pinned-repositories.png) -### Further reading +### Leer más - "[Acerca de tu perfil](/articles/about-your-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index c38c300057..a5039034de 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -20,7 +20,7 @@ Por defecto, los visitantes únicamente ven las contribuciones públicas en tu p - Para publicitar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y selecciona **Private contributions** (Contribuciones privadas). Los visitantes verán tus recuentos de contribuciones privadas sin más detalles. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-on.png) - Para ocultar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y anula la selección de **Private contributions** (Contribuciones privadas). Los visitantes únicamente verán tus contribuciones públicas. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-off.png) -### Further reading +### Leer más - "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" - "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 54dfe0ab7e..3d9300e27d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -70,7 +70,7 @@ Las marcas horarias se calculan de forma diferente para las confirmaciones y las - **Confirmaciones** utilizan la información de la zona horaria en la marca de tiempo de la confirmación. Para obtener más información, consulta "[Solución de problemas con confirmaciones en tu cronología](/articles/troubleshooting-commits-on-your-timeline)." - **Las solicitudes de extracción** y **las propuestas** abiertas en {% data variables.product.product_name %} utilizan la zona horaria de tu navegador. Aquellas abiertas a través de API utilizan la marca horaria o la zona horaria [especificada en la llamada de API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). -### Activity overview +### Resumen de la actividad {% data reusables.profile.activity-overview-summary %} 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)." @@ -91,7 +91,7 @@ Si tu administrador de sitio habilitó {% data variables.product.prodname_unified_contributions %}, puedes enviar un conteo de contribuciones de {% data variables.product.prodname_enterprise %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Enviar tus contribuciones {% data variables.product.prodname_ghe_server %} a tu {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)." {% endif %} -### Further reading +### Leer más - "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" - "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 6318f14a70..386ff35a15 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### Contribuciones que se cuentan -#### Issues, pull requests and discussions +#### Propuestas, solicitudes de cambios y debates -Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. +Las propuestas, solicitudes de cambios y debates aparecerán en tu gráfica de contribuciones si se abrieron en un repositorio independiente y no en una bifurcación. #### Confirmaciones Las confirmaciones aparecerán en tu gráfico de contribución si cumplen **todas** las condiciones a continuación: @@ -82,7 +82,7 @@ Las confirmaciones que se hicieron en una bifurcación no contarán para tus con - [Abre una solicitud de extracción](/articles/creating-a-pull-request) para que se fusionen tus cambios en el repositorio padre. - Para desconectar la bifurcación y convertirla en un repositorio independiente en {% data variables.product.product_name %}, contacta {% data variables.contact.contact_support %}. Si la bifurcación tiene a su vez más bifurcaciones, indica a {% data variables.contact.github_support %} si éstas deberán moverse junto con tu repositorio a una nueva red o permanecer en la actual. Para obtener más información, consulta "[Acerca de las bifurcaciones](/articles/about-forks/)." -### Further reading +### Leer más - "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" - "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md index abc2ade79c..61737465dc 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-organization-membership.md @@ -41,7 +41,7 @@ Si tu organización pertenece a una cuenta de empresa, automáticamente eres un Puedes dejar una organización en cualquier momento. Para obtener más información, consulta "[Cómo eliminarte de una organización](/articles/removing-yourself-from-an-organization)". -### Further reading +### Leer más - "[Acerca de las organizaciones](/articles/about-organizations)" - "[Administrar tu membresía en organizaciones](/articles/managing-your-membership-in-organizations)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md index 7947154617..770e503987 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md @@ -51,6 +51,6 @@ Para obtener más información acerca de cómo destacar repositorios y seguir pe Puedes explorar los repositorios recomendados en tus comunidades en la sección "Explorar repositorios" en el costado derecho de tu tablero. Las recomendaciones se basan en los repositorios que hayas visitado o marcado como favoritos, las personas que sigues, y la actividad dentro de los repositorios a los que tienes acceso.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Encontrar formas para contribuir con los proyectos de código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".{% endif %} -### Further reading +### Leer más - "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md index 0810465d58..d02766a458 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account.md @@ -23,6 +23,6 @@ versions: {% data reusables.user_settings.add_and_verify_email %} {% data reusables.user_settings.select_primary_email %} -### Further reading +### Leer más - "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md index 19a13beb1a..3c548cfbad 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -16,6 +16,6 @@ Cuando subes las confirmaciones de la línea de comando, la dirección de correo {% data reusables.user_settings.keeping_your_email_address_private %} 4. Para que tu dirección de correo electrónico siga siendo privada en las confirmaciones desde la línea de comando, selecciona **Block command line pusses that expose my email** (Bloquear inserciones de la línea de comando que expone mi correo electrónico). ![Opción para bloquear las inserciones de la línea de comando que expone tus correos electrónicos](/assets/images/help/settings/email_privacy_block_command_line_pushes.png) -### Further reading +### Leer más - "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md index f0f8024bef..e8d29a93e2 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md @@ -50,7 +50,7 @@ Luego de cambiar tu nombre de usuario, los enlaces a tu página de perfil anteri 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) {% endif %} -### Further reading +### Leer más - "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)" - "[¿Por qué se enlazan mis confirmaciones a un usuario incorrecto?](/articles/why-are-my-commits-linked-to-the-wrong-user)"{% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md index a2181369a0..4158902630 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md @@ -25,6 +25,6 @@ versions: características de {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". {% endif %} -### Further reading +### Leer más - "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index f5e03724bb..90455b2913 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -54,7 +54,7 @@ Puedes convertir tu cuenta de usuario personal directamente en una organización {% endtip %} -### Further reading +### Leer más - "[Configurar equipos](/articles/setting-up-teams)" {% if currentVersion == "free-pro-team@latest" %}- "[Invitar usuarios para que se unan a tu organización](/articles/inviting-users-to-join-your-organization)"{% endif %} - "[Acceder a una organización](/articles/accessing-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md index 1d8cf2bc67..77a6bbfb58 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects.md @@ -19,7 +19,7 @@ versions: 8. En **Developer applications** (Aplicaciones del programador), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png) {% data reusables.user_settings.jira_help_docs %} -### Further reading +### Leer más - ["Integrar Jira al tablero de proyecto de tu organización"](/articles/integrating-jira-with-your-organization-project-board) - Conectar Jira Cloud a GitHub (Documentación de Atlassian) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index 1a249d97aa..d406ae6756 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -48,7 +48,7 @@ Los repositorios que son propiedad de una organización pueden conceder acceso m 9. El usuario recibirá un correo electrónico invitándolo al repositorio. Una vez que acepte la invitación, tendrá acceso de colaborador a tu repositorio. {% endif %} -### Further reading +### Leer más - "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" - "[Eliminar un colaborador de un repositorio personal](/articles/removing-a-collaborator-from-a-personal-repository)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md index f974caf14d..8ea1d3bc4a 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md @@ -6,7 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators/ - /articles/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md index de47363f4b..7f50d2c76d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md @@ -4,7 +4,7 @@ intro: 'Puedes agregar o cambiar las direcciones de correo electrónico asociada redirect_from: - /categories/managing-email-preferences/ - /articles/managing-email-preferences -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md index 86c49a8733..dd0e24579f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github.md @@ -20,7 +20,7 @@ versions: 3. Dentro de *Email preferences (Preferencias de correo electrónico)*, selecciona **Only receive account related emails, and those I subscribe to (Recibir únicamente correos electrónicos relacionados con la cuenta y aquellos a los cuales me suscribo)**. ![Captura de pantalla de la cancelación de la suscripción de un correo electrónico de marketing](/assets/images/help/notifications/email_preferences.png) 4. Haz clic en **Save email preferences (Guardar preferencias de correo electrónico)**. ![Botón para guardar las preferencias de correo electrónico](/assets/images/help/notifications/save_email_preferences.png) -### Further reading +### Leer más - "[Tipos de correos electrónicos que envía GitHub](/articles/types-of-emails-github-sends)" - "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md index 78528c1cf8..465ade75bd 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account.md @@ -31,7 +31,7 @@ Para encontrar un resumen de la seguridad a nivel de repositorio, consulta la se {% 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) -### Further reading +### Leer más - "[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)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index a5bb049098..1f7d217d42 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -21,6 +21,6 @@ Cuando creas un repositorio nuevo en {% data variables.product.product_location 4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/settings/repo-default-name-text.png) 5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/settings/repo-default-name-update.png) -### Further reading +### Leer más - "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md index 1c17795cb0..5fe227c9fd 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md @@ -5,7 +5,7 @@ redirect_from: - /categories/29/articles/ - /categories/user-accounts/ - /articles/managing-user-account-settings -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md index cec417616f..c2f990fc8d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md @@ -1,7 +1,7 @@ --- title: Administrar tu membresía en organizaciones intro: 'Si eres un miembro de una organización, puedes publicar u ocultar tu membresía, ver los roles de otras personas y eliminarte de una organización.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/managing-your-membership-in-organizations versions: diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index 2f77eb4cc1..fe6689eb92 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -44,7 +44,7 @@ Puedes configurar recordatorios programados para solicitudes de revisión a nive 3. Da clic en **Editar** a un costado de la organización para la cual quieres borrar un recordatorio. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) {% data reusables.reminders.delete %} -### Further reading +### Leer más - "[Administrar los recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" - "[Administrar los recordatorios programados para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md index 080a8328c2..589ef58102 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -14,9 +14,9 @@ versions: 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 dos temas, claro y oscuro, o puedes configurar a {% data variables.product.product_name %} para que siga la configuración de tu sistema. Algunos desarrolladores utilizan el tema oscuro por sus preferencias personales, para reducir el consumo de energía en algunos dispositivos, o para reducir el cansancio de los ojos en las condiciones de iluminación baja. {% data reusables.user_settings.access_settings %} -1. En la barra lateral de configuración de usuario, da clic en **Apariencia**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +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) 1. Debajo de "Tema", selecciona una preferencia de tema. ![Botones radiales para la configuración de tema](/assets/images/help/settings/theme-settings-radio-buttons.png) -### Further reading +### Leer más - "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md index 43849d1e3e..08058cd819 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts.md @@ -19,6 +19,6 @@ versions: 2. [Actualiza las URL remotas](/articles/changing-a-remote-s-url) en cualquier clon local de los repositorios que se movieron. 3. [Elimina la cuenta](/articles/deleting-your-user-account) que ya no deseas utilizar. -### Further reading +### Leer más - [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index f25fe10ba8..c27f0ad497 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,20 +30,23 @@ El propietario del repositorio tiene control completo del repositorio. Adicional | {% if currentVersion == "free-pro-team@latest" %}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)" |{% if currentVersion == "free-pro-team@latest" %} -| Limitar las interacciones con el repositorio | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Limitar las interacciones con el repositorio | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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)" |{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} -| Borrar paquetes | "[Borrar un paquete](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| Borrar paquetes | "[Borrar un paquete](/github/managing-packages-with-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)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | Recibir | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %} para las dependencias vulnerables | "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 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 %} +| 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 | "[Acerca de archivar los repositorios](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Crear asesorías de seguridad | "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | @@ -64,8 +67,9 @@ Los colaboradores también pueden realizar las siguientes acciones. | Acción | Más información | |:-------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Bifurcar el repositorio | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Bifurcar el repositorio | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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 perturbadores](/github/building-a-strong-community/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)" | @@ -79,9 +83,10 @@ Los colaboradores también pueden realizar las siguientes acciones. | Crear y editar un wiki para el repositorio | "[Acerca de los wikis](/github/building-a-strong-community/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Publicar, ver o instalar paquetes | "[Publicar y mantener paquetes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| 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)" | -### Further reading +### Leer más - "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index 199ddc2263..54fea2831d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ Hay tres niveles de permisos para los colaboradores de un tablero de proyecto: El propietario del tablero de proyecto y los colaboradores con acceso de administrador tienen control completo del tablero de proyecto. Además de todos los permisos admitidos por los colaboradores del tablero de proyecto, un propietario y un colaborador de un tablero de proyecto con acceso de administrador pueden: - [Administrar, ver y agregar colaboradores](/articles/managing-access-to-your-user-account-s-project-boards) -- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility) +- [Configurar un tablero de proyecto como {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} o privado](/articles/changing-project-board-visibility) - [Eliminar un tablero de proyecto](/articles/deleting-a-project-board/) - [Cerrar un tablero de proyecto](/articles/closing-a-project-board/) - [Volver a abrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board) @@ -51,8 +51,8 @@ Los colaboradores con acceso de escritura a un tablero de proyecto propiedad del ### Visibilidad del tablero de proyecto -You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. Por defecto, los tableros de proyecto propiedad del usuario son privados. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". +Puedes cambiar la visibilidad del tablero de proyecto de privada a {% if currentVersion == "github-ae@latest" %}interna{% else %}pública{% endif %} y de vuelta. Por defecto, los tableros de proyecto propiedad del usuario son privados. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". -### Further reading +### Leer más - "[Administrar el acceso a los tableros de proyectos de tu cuenta de usuario](/articles/managing-access-to-your-user-account-s-project-boards)" diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md index 867b5254d1..51752bfa5e 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email.md @@ -63,7 +63,7 @@ origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME Sobornar a funcionarios del gobierno u otras personas para obtener una ventaja injusta y tomar sobornos de cualquier persona. -Eso significa que no solo se debe administrar dinero en efectivo o equivalente en efectivo de ningún tipo, sino no entregar nada de valor a nadie (incluyendo los empleados públicos, funcionarios del gobierno o cualquier persona en una posición de poder o autoridad, así como personas que no estén en cualquiera de esas posiciones privilegiadas) con el fin de influir en ellos o de que cualquier persona pueda influir en GitHub. Such activity is prohibited by the U.S. Se prohíbe dicha actividad por la ley de prácticas corruptas extranjeras de los EE. UU. y las leyes antisoborno del Reino Unido, que rigen las acciones de GitHub en todo el mundo. +Eso significa que no solo se debe administrar dinero en efectivo o equivalente en efectivo de ningún tipo, sino no entregar nada de valor a nadie (incluyendo los empleados públicos, funcionarios del gobierno o cualquier persona en una posición de poder o autoridad, así como personas que no estén en cualquiera de esas posiciones privilegiadas) con el fin de influir en ellos o de que cualquier persona pueda influir en GitHub. Se prohíbe dicha actividad por la ley de prácticas corruptas extranjeras de los EE.UU. y las por las leyes antisoborno del Reino Unido, que rigen las acciones de GitHub en todo el mundo. ### Ejemplos de regalos aceptables e inaceptables -Entonces, ¿Qué significa "de valor"? Ten en cuenta que no se aceptan regalos a funcionarios del gobierno (ok, tal vez calcomanías). Siempre debes preguntarles qué permiten y qué prohíben sus políticas. Pero si tienes dudas, por favor, consulta la ley para asegurarte. For example, many U.S. Por ejemplo, muchos legisladores estadounidenses no te permitirán llevarlos a cenar y pagar. +Entonces, ¿Qué significa "de valor"? Ten en cuenta que no se aceptan regalos a funcionarios del gobierno (ok, tal vez calcomanías). Siempre debes preguntarles qué permiten y qué prohíben sus políticas. Pero si tienes dudas, por favor, consulta la ley para asegurarte. Por ejemplo, muchos legisladores estadounidenses no te permitirán llevarlos a cenar y pagar. En cuanto a otros clientes o clientes potenciales, ciertas cosas pueden parecer triviales pero tienen un gran valor para otra persona. Por ejemplo, si bien puede que no parezca una gran cosa para ti lograr que se contrate a la hija de tu amigo como pasante, puede ser de gran valor para ellos. Pero si no está calificada y mueves influencias para hacer que suceda, entonces no está bien. Además, si la intención es influir de manera inadecuada, cualquier cosa, por pequeña que sea, se puede considerar "de valor". diff --git a/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md b/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md index fe973510ca..6b67b755b5 100644 --- a/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md +++ b/translations/es-ES/content/github/site-policy/github-marketplace-developer-agreement.md @@ -1,5 +1,5 @@ --- -title: GitHub Marketplace Developer Agreement +title: Acuerdo de Desarrollador de GitHub Marketplace redirect_from: - /articles/github-marketplace-developer-agreement versions: @@ -8,7 +8,7 @@ versions: **ESTOS TÉRMINOS Y CONDICIONES (EL "ACUERDO") REGULAN TU PARTICIPACIÓN EN EL PROGRAMA DEL MERCADO DE GITUB. AL INSCRIBIRTE PARA PARTICIPAR EN EL PROGRAMA DE MERCADO O AL HACER CLIC EN "ACEPTO" A CONTINUACIÓN, CONFIRMAS QUE ENTIENDES EL PRESENTE ACUERDO Y QUE ACEPTAS TODOS SUS TÉRMINOS Y CONDICIONES. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS.** -Effective Date: January 1, 2021 +Fecha de entrada en vigor: 1 de enero de 2021 ### 1. DEFINICIONES @@ -62,12 +62,12 @@ Independientemente de cualquiera de los requisitos establecidos en la sección 2 - 2\. Contiene o instala cualquier malware o exploits activos, o utiliza nuestra plataforma para la entrega de exploits (como parte de un sistema de comando y control); - 3\. Interfiere, altera, interrumpe, daña o accede de manera no autorizada a las máquinas, los sistemas, el hardware, los servidores, las redes, los dispositivos, los datos u otras propiedades o servicios de cualquier tercero; - 4\. Incluye contenido falso o engañoso; -- 5\. Infringes on any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity, or other rights; -- 6\. Is libelous, defamatory, or fraudulent; +- 5\. Infrinja cualquier derecho de propiedad de cualquier parte, incluyendo patentes, marcas registradas, secretos comerciales, propiedad intelectual, derecho de publicidad u otros derechos; +- 6\. Sea calumnioso, difamatorio o fraudulento; - 7\. Habilita la descarga no autorizada de contenido de streaming o medios; - 8\. Muestra o vincula a contenido ilegal; - 9\. Acosa, abusa, amenaza o incita a cualquier persona o grupo, incluyendo los empleados, los funcionarios y los agentes de GitHub, o cualquier usuario final; -- 10\. Is or contains sexually obscene content; +- 10\. Sea o incluya contenido obsceno o sexual; - 11\. Sea discriminatorio o abusivo hacia cualquier persona o grupo; - 12\. Desvía a los usuarios finales o proporciona enlaces a cualquier otro sitio que imita al mercado o se hace pasar a sí mismo como mercado. @@ -193,7 +193,7 @@ Las partes son contratistas independientes. El presente acuerdo no crea una rela ### 15. AVISOS -Todas las notificaciones que GitHub debe proporcionar al Programador conforme a lo dispuesto en el presente acuerdo pueden entregarse por escrito (i) por el servicio de entrega a domicilio ("Courier") reconocido a nivel nacional o por correo electrónico a la dirección de correo electrónico de contacto proporcionada por el programador a GitHub; o (ii) correo electrónico a la dirección de correo electrónico proporcionada por el Programador. mail to the contact mailing address provided by Developer to GitHub; or (ii) electronic mail to the electronic mail address provided by Developer. El programador debe dar aviso a GitHub por escrito por mensajería o EE. UU. GitHub, Inc., en atención al: Departamento Jurídico, 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107 EE. UU. Todas las notificaciones se considerarán entregadas inmediatamente después de la entrega por correo electrónico, o si se entregan de otra manera al recibirlo o, si son anteriores, dos (2) días hábiles después de haber sido depositadas por correo o con un mensajero como se permitió anteriormente. +Todas las notificaciones que GitHub debe proporcionar al Programador conforme a lo dispuesto en el presente acuerdo pueden entregarse por escrito (i) por el servicio de entrega a domicilio de un solo día ("Courier") o por correo nacional de los EE.UU. a la dirección de correo de contacto que haya proporcionado el programador a GitHub; o (ii) correo electrónico a la dirección de correo electrónico que proporcionó el Programador. El programador debe dar aviso a GitHub por escrito por mensajería o EE. UU. GitHub, Inc., en atención al: Departamento Jurídico, 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107 EE. UU. Todas las notificaciones se considerarán entregadas inmediatamente después de la entrega por correo electrónico, o si se entregan de otra manera al recibirlo o, si son anteriores, dos (2) días hábiles después de haber sido depositadas por correo o con un mensajero como se permitió anteriormente. ### 16. LEGISLACIÓN APLICABLE @@ -250,7 +250,7 @@ El presente anexo de protección de datos (este "Anexo") se adjunta y forma part - i. A petición, el Programador hará su declaración de privacidad, política de privacidad, aviso de privacidad o cualquier documentación similar disponible. El Programador también proporcionará un aviso de cualquier informe de cumplimiento relevante, incluyendo el cumplimiento del escudo de la privacidad. - ii. El Programador cumplirá con las obligaciones de seguridad de la información y auditoría en la sección 3.7 del acuerdo del Programador del mercado de GitHub. -**A1-7. Termination** +**A1-7. Terminación** - a. Suspensión. En el caso de que el Programador incumpla con sus obligaciones de mantener un nivel adecuado de protección de la privacidad, GitHub puede suspender de forma temporal la transferencia de datos protegidos o prohibir la recopilación y el procesamiento de datos protegidos en nombre de GitHub hasta que se repare el incumplimiento o se termine el acuerdo. - b. Terminación con causa. GitHub puede rescindir el Acuerdo sin perjuicio de cualquier otra reclamación en derecho o en equidad en el caso de que: diff --git a/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md b/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md index 9729f3b5fd..3b245f55d1 100644 --- a/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md +++ b/translations/es-ES/content/github/site-policy/github-open-source-applications-terms-and-conditions.md @@ -28,7 +28,7 @@ La concesión de licencia incluida con el software no es para las marcas comerci Los nombres GitHub, GitHub Desktop, GitHub para Mac, GitHub para Windows, Atom, The Octocat y los logotipos de GitHub relacionados y/o los nombres estilizados son marcas comerciales de GitHub. Aceptas no mostrar o usar estas marcas comerciales de ninguna manera sin el permiso previo por escrito de GitHub, excepto según lo permitido por los logotipos y la política de uso de GitHub: https://github.com/logos. -### Privacy +### Privacidad El software puede recopilar información personal. Puedes controlar qué información recopila el software en el panel de configuraciones. Si el software recopila información personal en nombre de GitHub, GitHub procesará esa información de acuerdo con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/). @@ -52,7 +52,7 @@ GitHub se reserva el derecho en cualquier momento y de vez en cuando de modifica 2. Acuerdo completo. Estos términos de la aplicación, junto con cualquier aviso de privacidad aplicable, constituyen el acuerdo completo entre tú y GitHub y rigen tu uso del software, reemplazando cualquier acuerdo anterior entre tú y GitHub (incluyendo, entre otras, cualquier versión anterior de los términos de la aplicación). -3. Governing Law. Aceptas que estos términos de la aplicación y tu uso del software están regidos por la ley de California y cualquier disputa relacionada con el software debe ser llevada a un tribunal de jurisdicción competente ubicado en o cerca de San Francisco, California. +3. Legislación aplicable. Aceptas que estos términos de la aplicación y tu uso del software están regidos por la ley de California y cualquier disputa relacionada con el software debe ser llevada a un tribunal de jurisdicción competente ubicado en o cerca de San Francisco, California. 4. Paquetes de terceros. El software admite "paquetes" de terceros que pueden modificar, agregar, eliminar o alterar la funcionalidad del software. Estos paquetes no están cubiertos por los presentes términos de la aplicación y pueden incluir su propia licencia que rige tu uso de ese paquete en particular. diff --git a/translations/es-ES/content/github/site-policy/github-pre-release-program.md b/translations/es-ES/content/github/site-policy/github-pre-release-program.md index e249c7a9de..62ea0eab92 100644 --- a/translations/es-ES/content/github/site-policy/github-pre-release-program.md +++ b/translations/es-ES/content/github/site-policy/github-pre-release-program.md @@ -62,7 +62,7 @@ El presente acuerdo es un acuerdo legal entre tú ("tú", "tu") y GitHub, Inc. ( Ninguna parte del presente acuerdo perjudicará nuestro derecho a desarrollar, adquirir, licenciar, comercializar, promocionar o distribuir productos, software o tecnologías que puedan competir con tus productos. -### 11. Privacy +### 11. Privacidad Como parte del desarrollo y la evaluación de nuestros programas de evaluación, GitHub necesita recopilar información sobre cómo tu uso de los servicios y los programas y cómo GitHub puede mejorarlos. Al aceptar participar en los programas de prelanzamiento de GitHub, aceptas que has leído y has dado tu consentimiento a nuestra [Política de privacidad completa](/articles/github-privacy-statement/). diff --git a/translations/es-ES/content/github/site-policy/github-privacy-statement.md b/translations/es-ES/content/github/site-policy/github-privacy-statement.md index 5dadba7ee4..30297c84ba 100644 --- a/translations/es-ES/content/github/site-policy/github-privacy-statement.md +++ b/translations/es-ES/content/github/site-policy/github-privacy-statement.md @@ -1,5 +1,5 @@ --- -title: GitHub Privacy Statement +title: Declaración de Privacidad de GitHub redirect_from: - /privacidad/ - /privacy-policy/ @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: December 19, 2020 +Fecha de entrada en vigor: 19 de diciembre de 2020 Gracias por confiar a GitHub Inc. (“GitHub”, “nosotros”) tu código fuente, tus proyectos y tu información personal. Mantener tu información privada es una responsabilidad importante, y queremos que sepas cómo lo hacemos. @@ -26,26 +26,26 @@ Por supuesto, la versión corta y el Resumen que aparecen a continuación no inf ### Resumen -| Sección | ¿Qué puedes encontrar allí? | -| ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Qué información recopila GitHub](#what-information-github-collects) | GitHub recopila información directamente a partir de tu registro, tus pagos, tus transacciones y del perfil del usuario. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. Puede que GitHub también recopile Información personal del usuario a partir de terceros. Solo recopilamos la mínima cantidad de información personal necesaria a través de ti, a menos que decidas proporcionar más. | -| [Qué información GitHub _no_ recopila](#what-information-github-does-not-collect) | No recopilamos intencionalmente información de niños menores de 13 años y no recopilamos [Información personal sensible](https://gdpr-info.eu/art-9-gdpr/). | -| [Cómo utiliza GitHub tu información](#how-github-uses-your-information) | En esta sección, describimos las formas en las que utilizamos tu información, incluyendo el proporcionarte el Servicio, comunicarnos contigo, para propósitos de seguridad y cumplimiento, y para mejorar nuestro Servicio. También describimos la base legal sobre la cual procesamos tu información personal, cuando se exige legalmente. | -| [Cómo compartimos la información que recopilamos](#how-we-share-the-information-we-collect) | Puede que compartamos tu información con terceros en una de las siguientes circunstancias: con tu consentimiento, con nuestros proveedores de servicio, por motivos de seguridad, para cumplir con nuestras obligaciones legales o cuando exista un cambio de control o venta de las entidades corporativas o unidades de negocios. En GitHub, no vendemos tu información personal y no alojamos publicidad. Puedes consultar una lista de los proveedores de servicio que acceden a tu información. | -| [Otra información importante](#other-important-information) | Proporcionamos más información específica sobre los contenidos del repositorio, la información pública y las Organizaciones de GitHub. | -| [Servicios adicionales](#additional-services) | Proporcionamos información sobre las ofertas de servicio adicionales, incluso aplicaciones de terceros, Páginas de GitHub y aplicaciones de GitHub. | -| [Cómo puedes acceder y controlar la información que recopilamos](#how-you-can-access-and-control-the-information-we-collect) | Proporcionamos formas para que accedas, modifiques o elimines tu información personal. | -| [Uso de cookies y seguimiento](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. Ofrecemos una página que hace que esto sea muy transparente. Consulta esta sección para obtener más información. | -| [Cómo asegura GitHub tu información](#how-github-secures-your-information) | Tomamos todas las medidas razonablemente necesarias para proteger la confidencialidad, integridad y disponibilidad de tu información personal en GitHub y para proteger la resistencia de nuestros servidores. | -| [Prácticas de privacidad mundiales de GitHub](#githubs-global-privacy-practices) | Proporcionamos el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo entero. | -| [Cómo nos comunicamos contigo](#how-we-communicate-with-you) | Nos comunicamos contigo por correo electrónico. Puedes controlar la manera en que te contactamos en las configuraciones de la cuenta o poniéndote en contacto con nosotros. | -| [Resolver reclamos](#resolving-complaints) | En el caso improbable de que no podamos resolver una inquietud sobre la privacidad de forma rápida y exhaustiva, proporcionaremos un medio de resolución por medio de una disputa. | -| [Cambios en tu Declaración de privacidad](#changes-to-our-privacy-statement) | Te notificamos los cambios importantes en esta Declaración de privacidad 30 días antes de que cualquier cambio entre en vigencia. Puedes rastrear los cambios en nuestro repositorio de Políticas del sitio. | -| [Licencia](#license) | La presente Declaración de privacidad está autorizada por la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). | -| [Contactarse con GitHub](#contacting-github) | Siéntete libre de contactarnos si tienes preguntas acerca de nuestra Declaración de privacidad. | -| [Traducciones](#translations) | Proporcionamos enlaces a algunas traducciones de la Declaración de privacidad. | +| Sección | ¿Qué puedes encontrar allí? | +| ---------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [Qué información recopila GitHub](#what-information-github-collects) | GitHub recopila información directamente a partir de tu registro, tus pagos, tus transacciones y del perfil del usuario. También, cuando es necesario, recopilamos automáticamente información de tu uso, cookies e información de dispositivo sujetos, cuando sea necesario, a tu consentimiento. Puede que GitHub también recopile Información personal del usuario a partir de terceros. Solo recopilamos la mínima cantidad de información personal necesaria a través de ti, a menos que decidas proporcionar más. | +| [Qué información GitHub _no_ recopila](#what-information-github-does-not-collect) | No recopilamos intencionalmente información de niños menores de 13 años y no recopilamos [Información personal sensible](https://gdpr-info.eu/art-9-gdpr/). | +| [Cómo utiliza GitHub tu información](#how-github-uses-your-information) | En esta sección, describimos las formas en las que utilizamos tu información, incluyendo el proporcionarte el Servicio, comunicarnos contigo, para propósitos de seguridad y cumplimiento, y para mejorar nuestro Servicio. También describimos la base legal sobre la cual procesamos tu información personal, cuando se exige legalmente. | +| [Cómo compartimos la información que recopilamos](#how-we-share-the-information-we-collect) | Puede que compartamos tu información con terceros en una de las siguientes circunstancias: con tu consentimiento, con nuestros proveedores de servicio, por motivos de seguridad, para cumplir con nuestras obligaciones legales o cuando exista un cambio de control o venta de las entidades corporativas o unidades de negocios. En GitHub, no vendemos tu información personal y no alojamos publicidad. Puedes consultar una lista de los proveedores de servicio que acceden a tu información. | +| [Otra información importante](#other-important-information) | Proporcionamos más información específica sobre los contenidos del repositorio, la información pública y las Organizaciones de GitHub. | +| [Servicios adicionales](#additional-services) | Proporcionamos información sobre las ofertas de servicio adicionales, incluso aplicaciones de terceros, Páginas de GitHub y aplicaciones de GitHub. | +| [Cómo puedes acceder y controlar la información que recopilamos](#how-you-can-access-and-control-the-information-we-collect) | Proporcionamos formas para que accedas, modifiques o elimines tu información personal. | +| [Uso de cookies y seguimiento](#our-use-of-cookies-and-tracking) | Solo utilizamos las cookies estrictamente necesarias para proporcionar, asegurar y mejorar nuestro servicio. Ofrecemos una página que hace que esto sea muy transparente. Consulta esta sección para obtener más información. | +| [Cómo asegura GitHub tu información](#how-github-secures-your-information) | Tomamos todas las medidas razonablemente necesarias para proteger la confidencialidad, integridad y disponibilidad de tu información personal en GitHub y para proteger la resistencia de nuestros servidores. | +| [Prácticas de privacidad mundiales de GitHub](#githubs-global-privacy-practices) | Proporcionamos el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo entero. | +| [Cómo nos comunicamos contigo](#how-we-communicate-with-you) | Nos comunicamos contigo por correo electrónico. Puedes controlar la manera en que te contactamos en las configuraciones de la cuenta o poniéndote en contacto con nosotros. | +| [Resolver reclamos](#resolving-complaints) | En el caso improbable de que no podamos resolver una inquietud sobre la privacidad de forma rápida y exhaustiva, proporcionaremos un medio de resolución por medio de una disputa. | +| [Cambios en tu Declaración de privacidad](#changes-to-our-privacy-statement) | Te notificamos los cambios importantes en esta Declaración de privacidad 30 días antes de que cualquier cambio entre en vigencia. Puedes rastrear los cambios en nuestro repositorio de Políticas del sitio. | +| [Licencia](#license) | La presente Declaración de privacidad está autorizada por la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). | +| [Contactarse con GitHub](#contacting-github) | Siéntete libre de contactarnos si tienes preguntas acerca de nuestra Declaración de privacidad. | +| [Traducciones](#translations) | Proporcionamos enlaces a algunas traducciones de la Declaración de privacidad. | -## GitHub Privacy Statement +## Declaración de privacidad de GitHub ### Qué información recopila GitHub @@ -75,7 +75,7 @@ Si tienes una Cuenta paga con nosotros, vendes una aplicación detallada en el [ Si accedes a nuestro Servicio o Sitio web, automáticamente recopilamos la misma información básica que recopila la mayoría de los servicios, sujeto a tu consentimiento cuando resulte necesario. Esto incluye información acerca de cómo utilizas el Servicio, por ejemplo, las páginas que miras, el sitio referido, tu dirección IP e información de sesión, y la fecha y hora de cada solicitud. Recopilamos esta información de todos los visitantes del Sitio web, tengan o no una Cuenta. Esta información puede incluir Información personal del usuario. ##### Cookies -As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service. +De acuerdo a como se describe a continuación, recolectamos automáticamente la información de las cookies (tales como la ID y configuración de éstas) para mantenerte con una sesión iniciada, para recordar tus preferencias, para identificarte tanto a ti como a tu dispositivo y para analizar tu uso de nuestro servicio. ##### Información de dispositivo Puede que recopilemos determinada información acerca de tu dispositivo, como la dirección IP, el navegador o información de la aplicación del cliente, preferencias de idioma, sistema operativo y versión de la aplicación, tipo e ID del dispositivo y modelo y fabricante del dispositivo. Esta información puede incluir Información personal del usuario. @@ -235,11 +235,11 @@ Una vez dicho esto, la dirección de correo electrónico que suministraste [a tr #### Cookies -GitHub only uses strictly necessary cookies. Las cookies son pequeños archivos de texto que los sitios web almacenan a menudo en discos duros o dispositivos móviles de los visitantes. +GitHub solo utiliza las cookies estrictamente necesarias. Las cookies son pequeños archivos de texto que los sitios web almacenan a menudo en discos duros o dispositivos móviles de los visitantes. -We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers. +Utilizamos cookies únicamente para proporcionar, asegurar y mejorar nuestro servicio. Por ejemplo, las utilizamos para mantenerte firmado, recordar tus preferencias, identificar tu dispositivo para propósitos de seguridad, analizar tu uso de nuestro servicio, compilar reportes estadísticos y proporcionar información para el desarrollo futuro de GitHub. Utilizamos nuestras propias cookies para propósitos de analítica, pero no utilizamos ningún proveedor de servicios de analítica tercero. -By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service. +Al usar nuestro servicio, aceptas que podamos colocar este tipo de cookies en tu computadora o dispositivo. Si desactivas la capacidad de tu navegador o dispositivo para aceptar estas cookies, no podrás ingresar o utilizar nuestro servicio. Proporcionamos más información acerca de las [cookies en GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) en nuestra página de [Subprocesadores y cookies de GitHub](/github/site-policy/github-subprocessors-and-cookies), en la cual se describen las cookies que configuramos, las necesidades que tenemos para utilizarlas, y la vigencia de las mismas. diff --git a/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md b/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md index 132d15cada..68356e035e 100644 --- a/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/es-ES/content/github/site-policy/github-registered-developer-agreement.md @@ -56,7 +56,7 @@ Este Acuerdo es un acuerdo legal entre tú (“tú”) y GitHub, Inc. (“GitHub 7. **Cuotas y pago** - Pueden haber honorarios asociados con la participación en el programa. Te diremos cuáles son esas tarifas en los términos del programa, ya que las actualizamos de vez en cuando (las "tarifas del programa"). Si nos proporcionaste tu información de pago antes, aceptas que podemos cobrar la misma tarjeta de crédito o cuenta de PayPal como parte del presente acuerdo. De lo contrario, deberás otortarnos una cuenta de pago válida y otra información de respaldo. Excepto que se disponga expresamente lo contrario en la sección 8, cualquier pago que nos realices para el programa no es reembolsable. Nos otorgas permiso para cobrar automáticamente tu cuenta de pago en el aniversario de tu primera fecha de pago para cubrir todas las tarifas del programa del año que viene, a menos que canceles el presente acuerdo de acuerdo con la sección 8. All fees are due in U.S. Todas las tarifas se deben pagar en dólares estadounidenses y son exclusivas de todos los impuestos, gravámenes o deberes impuestos por las autoridades fiscales (eres responsable de todos ellos, a excepción de los impuestos basados en nuestros ingresos). + Pueden haber honorarios asociados con la participación en el programa. Te diremos cuáles son esas tarifas en los términos del programa, ya que las actualizamos de vez en cuando (las "tarifas del programa"). Si nos proporcionaste tu información de pago antes, aceptas que podemos cobrar la misma tarjeta de crédito o cuenta de PayPal como parte del presente acuerdo. De lo contrario, deberás otortarnos una cuenta de pago válida y otra información de respaldo. Excepto que se disponga expresamente lo contrario en la sección 8, cualquier pago que nos realices para el programa no es reembolsable. Nos otorgas permiso para cobrar automáticamente tu cuenta de pago en el aniversario de tu primera fecha de pago para cubrir todas las tarifas del programa del año que viene, a menos que canceles el presente acuerdo de acuerdo con la sección 8. Todas las tarifas se deben pagar en dólares estadounidenses y son exclusivas de todos los impuestos, gravámenes o deberes impuestos por las autoridades fiscales (eres responsable de todos ellos, a excepción de los impuestos basados en nuestros ingresos). 8. **Plazo y terminación** diff --git a/translations/es-ES/content/github/site-policy/github-research-program-terms.md b/translations/es-ES/content/github/site-policy/github-research-program-terms.md index 3379af805f..b95d2be422 100644 --- a/translations/es-ES/content/github/site-policy/github-research-program-terms.md +++ b/translations/es-ES/content/github/site-policy/github-research-program-terms.md @@ -28,7 +28,7 @@ Las obligaciones de la presente sección 2 no se aplicarán a la información qu Toda la información confidencial sigue siendo propiedad exclusiva y propiedad de GitHub. Ninguna de las partes adquiere ningún derecho de propiedad intelectual conforme a lo dispuesto en el presente acuerdo, salvo que se especifique expresamente aquí. -### D. Privacy +### D. Privacidad Al participar en este programa, aceptas el uso de tu información personal con fines de investigación y para ningún otro propósito. Como parte del programa, es posible que uses tu información personal para contactarte o conservar tu información, para contactarte en una fecha posterior. La información personal no incluye información agregada, que no identifiques personalmente. Es posible que uses la información de identificación personal o agregada que se recopila a través del programa para operar, analizar y mejorar nuestros productos y servicios. diff --git a/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md b/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md index 4699d8b2b9..f20c2acb35 100644 --- a/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md +++ b/translations/es-ES/content/github/site-policy/github-sponsors-additional-terms.md @@ -50,7 +50,7 @@ Bajo ninguna circunstancia recibirás pagos o recabarás fondos que involucren: * actividades con países, regiones, gobiernos, personas o entidades que no estén permitidas conforme a las sanciones impuestas por los EE. UU. y demás sanciones económicas que imponga la ley correspondiente, o actividades dentro de ellos o que los involucren. Y otras sanciones económicas bajo la legislación aplicable. -#### 2.2. GitHub Sponsors Matching Fund +#### 2.2. Fondo Compensatorio para Patrocinios de GitHub El Fondo Compensatorio para Patrocinios de GitHub pretende alentar a la comunidad que participa en el ecosistema de Software de Código Abierto (OSS, por sus siglas en inglés) para contribuir con fondos sostenibles para los individuos elegibles con Cuentas de Desarrollador Patrocinado. Todos los individuos que apliquen al Programa antes del 1 de enero de 2020 se revisarán para elegibilidad para el fondo Compensatorio, pero no todas las Cuentas de Desarrollador Patrocinado elegibles se escogerán. Las organizaciones no pueden participar en el Fondo Compensatorio para Patrocinios de GitHub, y no se escogerán las Cuentas de Desarrollador Patrocinadas elegibles que ya se encuentren patrocinadas por una organización. Encuentra las reglas adicionales a continuación. ##### 2.2.1. Condiciones para el Fondo Compensatorio. @@ -158,7 +158,7 @@ ACEPTAS DE MANERA EXPLÍCITA QUE LAS SECCIONES O (DESCARGO DE GARANTÍAS), P (LI Los presentes Términos adicionales comienzan en la fecha de entrada en vigor y seguirán rigiendo siempre que participes del Programa. #### 6.2. Suspensión. -GitHub puede suspender tu Cuenta de programador patrocinado de inmediato si violas de cualquier manera los presentes Términos adicionales o el Acuerdo, o si eres colocado o ubicado en una lista comercial restringida, o si eres residente habitual de un país o territorio sujeto a las sanciones generales que administra la Oficina de Control de Activos Extranjeros (OFAC, por sus siglas en inglés) de los EE. UU. Office of Foreign Assets Control (OFAC). No poder corregir o solucionar el motivo de la suspensión puede dar lugar a la terminación de tu Cuenta de programador patrocinado. +GitHub puede suspender tu Cuenta de programador patrocinado de inmediato si violas de cualquier manera los presentes Términos adicionales o el Acuerdo, o si eres colocado o ubicado en una lista comercial restringida, o si eres residente habitual de un país o territorio sujeto a las sanciones generales que administra la Oficina de Control de Activos Extranjeros (OFAC, por sus siglas en inglés) de los EE.UU. No poder corregir o solucionar el motivo de la suspensión puede dar lugar a la terminación de tu Cuenta de programador patrocinado. #### 6.4. Terminación. Cualquiera de las partes podrá rescindir estos Términos Adicionales y tu Cuenta de Desarrollador Patrocinado en cualquier momento con o sin causa, con o sin previo aviso. Si incumples los presentes Términos adicionales o el Acuerdo, podemos ofrecerte un período para solucionar el incumplimiento, aunque no estamos obligados a hacerlo. diff --git a/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md index 26166ac119..7baf1bc132 100644 --- a/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,70 +10,68 @@ versions: free-pro-team: '*' --- -Effective date: **January 6, 2021** +Fecha de entrada en vigor: **29 de enero de 2021** -GitHub ofrece una gran cantidad de transparencia en cuanto a cómo usamos tus datos, cómo recopilamos tus datos y con quién los compartimos. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). +GitHub ofrece una gran cantidad de transparencia en cuanto a cómo usamos tus datos, cómo recopilamos tus datos y con quién los compartimos. Para este propósito, proporcionamos esta página, la cual detalla [nuestros subprocesadores](#github-subprocessors) y cómo utilizamos las [cookies](#cookies-on-github). ### Subprocesadores de GitHub Cuando compartimos tu información con subprocesadores de terceros, como nuestros vendedores y proveedores de servicios, seguimos siendo responsables de ella. Trabajamos arduamente para mantener tu confianza cuando traemos nuevos proveedores y exigimos que todos los proveedores celebren acuerdos de protección de datos con nosotros que restrinjan su procesamiento de la información personal de los usuarios (tal como se define en la [Declaración de Privacidad](/articles/github-privacy-statement/)). -| Nombre del subprocesador | Descripción del procesamiento | Ubicación del procesamiento | Ubicación Corporativa | -|:------------------------ |:----------------------------------------------------------- |:--------------------------- |:--------------------- | -| Automattic | Servicio de alojamiento | Estados Unidos | Estados Unidos | -| AWS Amazon | Alojamiento de datos | Estados Unidos | Estados Unidos | -| Braintree (PayPal) | Procesador de pagos de suscripción con tarjeta de crédito | Estados Unidos | Estados Unidos | -| Clearbit | Servicio de enriquecimiento de datos de marketing | Estados Unidos | Estados Unidos | -| Discourse | Proveedor de software del foro de la comunidad | Estados Unidos | Estados Unidos | -| Eloqua | Automatización de campañas de marketing | Estados Unidos | Estados Unidos | -| Google Apps | Infraestructura interna de la empresa | Estados Unidos | Estados Unidos | -| Google Analytics | Analítica y rendimiento | Estados Unidos | Estados Unidos | -| MailChimp | Proveedor de servicios de correo de billetaje de clientes | Estados Unidos | Estados Unidos | -| Mailgun | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | -| Microsoft | Servicios de Microsoft | Estados Unidos | Estados Unidos | -| Monday.com | Plataforma de colaboración en equipo y gestión de proyectos | Estados Unidos | Israel | -| Nexmo | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | -| Salesforce.com | Gestión de relaciones con clientes | Estados Unidos | Estados Unidos | -| Sendgrid | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | -| Sentry.io | Proveedor de monitoreo de aplicaciones | Estados Unidos | Estados Unidos | -| Stripe | Proveedor de pagos | Estados Unidos | Estados Unidos | -| Twilio | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | -| Zendesk | Sistema de tickets de soporte al cliente | Estados Unidos | Estados Unidos | -| Zuora | Sistema de facturación corporativa | Estados Unidos | Estados Unidos | +| Nombre del subprocesador | Descripción del procesamiento | Ubicación del procesamiento | Ubicación Corporativa | +|:------------------------ |:----------------------------------------------------------------------------------------------- |:--------------------------- |:--------------------- | +| Automattic | Servicio de alojamiento | Estados Unidos | Estados Unidos | +| AWS Amazon | Alojamiento de datos | Estados Unidos | Estados Unidos | +| Braintree (PayPal) | Procesador de pagos de suscripción con tarjeta de crédito | Estados Unidos | Estados Unidos | +| Clearbit | Servicio de enriquecimiento de datos de marketing | Estados Unidos | Estados Unidos | +| Discourse | Proveedor de software del foro de la comunidad | Estados Unidos | Estados Unidos | +| Eloqua | Automatización de campañas de marketing | Estados Unidos | Estados Unidos | +| Google Apps | Infraestructura interna de la empresa | Estados Unidos | Estados Unidos | +| MailChimp | Proveedor de servicios de correo de billetaje de clientes | Estados Unidos | Estados Unidos | +| Mailgun | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | +| Microsoft | Servicios de Microsoft | Estados Unidos | Estados Unidos | +| Monday.com | Plataforma de colaboración en equipo y gestión de proyectos | Estados Unidos | Israel | +| Nexmo | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | +| Salesforce.com | Gestión de relaciones con clientes | Estados Unidos | Estados Unidos | +| Sentry.io | Proveedor de monitoreo de aplicaciones | Estados Unidos | Estados Unidos | +| Stripe | Proveedor de pagos | Estados Unidos | Estados Unidos | +| Twilio & Twilio Sendgrid | Proveedor de notificaciones por SMS & proveedor de servicio de correo electrónico transaccional | Estados Unidos | Estados Unidos | +| Zendesk | Sistema de tickets de soporte al cliente | Estados Unidos | Estados Unidos | +| Zuora | Sistema de facturación corporativa | Estados Unidos | Estados Unidos | Cuando traemos un nuevo subprocesador que maneja la información personal de nuestros usuarios o eliminas un subprocesador, o cambiamos la manera en que usamos un subprocesador, actualizaremos esta página. Si tienes preguntas o inquietudes acerca de un nuevo subprocesador, estaremos encantados de ayudarte. Ponte en contacto con nosotros vía{% data variables.contact.contact_privacy %}. ### Cookies en GitHub -GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Por favor, echa un vistazo a nuestra [Declaración de privacidad](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) si te gustaría obtener más información sobre las cookies y sobre cómo y por qué las utilizamos. +GitHub utiliza cookies para proporcionar y asegurar nuestros sitios web, así como para analizar el uso de los mismos, para poder ofrecerte una gran experiencia de usuario. Por favor, echa un vistazo a nuestra [Declaración de privacidad](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) si te gustaría obtener más información sobre las cookies y sobre cómo y por qué las utilizamos. -Ya que la cantidad y los nombres de las cookies podrían cambiar, la siguiente tabla podría actualizarse de vez en cuándo. +Ya que la cantidad de nombres y cookies puede cambiar, la tabla siguiente se podría actualizar a menudo. -| Proveedor de servicios | Nombre de la Cookie | Descripción | Vencimiento* | -|:---------------------- |:------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------ | -| GitHub | `app_manifest_token` | Esta cookie se utiliza durante el flujo del manifiesto de la app para mantener su estado durante la redirección para obtener una sesión de usuario. | cinco minutos | -| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | un año | -| GitHub | `dotcom_user` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | un año | -| GitHub | `_gh_ent` | Esta cookie se utiliza para la aplicación temporal y el estado del marco de trabajo entre las páginas como en qué paso se encuentra el cliente dentro de un formulario de varios pasos. | dos semanas | -| GitHub | `_gh_sess` | Esta cookie se usa para la aplicación temporal y el estado del marco entre las páginas copara indicar en qué paso está el usuario en un formulario de múltiples pasos. | session | -| GitHub | `gist_oauth_csrf` | Esta cookie se establece por Gist para asegurar que el usuario que inició el flujo OAuth sea el mismo usuario que lo completa. | se borra al validar el estado de oauth | -| GitHub | `gist_user_session` | Esta cookie es usada por Gist cuando se ejecuta en un host por separado. | dos semanas | -| GitHub | `has_recent_activity` | Esta cookie se utiliza para prevenir que se muestre la seguridad que es intersticial a los usuarios que han visitado la app recientemente. | una hora | -| GitHub | `__Host-gist_user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub. | dos semanas | -| GitHub | `__Host-user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub. | dos semanas | -| GitHub | `logged_in` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | un año | -| GitHub | `marketplace_repository_ids` | Esta cookie se utiliza para el flujo de instalación de marketplace. | una hora | -| GitHub | `marketplace_suggested_target_id` | Esta cookie se utiliza para el flujo de instalación de marketplace. | una hora | -| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | un año | -| GitHub | `org_transform_notice` | Esta cookie se utiliza para proporcionar notificaciones durante las transformaciones de las organizaciones. | una hora | -| GitHub | `private_mode_user_session` | Esta cookie se utiliza para las solicitudes de autenticación empresarial. | dos semanas | -| GitHub | `saml_csrf_token` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | -| GitHub | `saml_csrf_token_legacy` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | -| GitHub | `saml_return_to` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | -| GitHub | `saml_return_to_legacy` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | -| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | session | -| GitHub | `user_session` | Esta cookie se utiliza para que inicies sesión. | dos semanas | +| Proveedor de servicios | Nombre de la Cookie | Descripción | Vencimiento* | +|:---------------------- |:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------ | +| GitHub | `app_manifest_token` | Esta cookie se utiliza durante el flujo del manifiesto de la app para mantener su estado durante la redirección para obtener una sesión de usuario. | cinco minutos | +| GitHub | `_device_id` | Esta cookie se utiliza para rastrear los dispositivos reconocidos para propósitos de seguridad. | un año | +| GitHub | `dotcom_user` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | un año | +| GitHub | `_gh_ent` | Esta cookie se utiliza para la aplicación temporal y el estado del marco de trabajo entre las páginas como en qué paso se encuentra el cliente dentro de un formulario de varios pasos. | dos semanas | +| GitHub | `_gh_sess` | Esta cookie se usa para la aplicación temporal y el estado del marco entre las páginas copara indicar en qué paso está el usuario en un formulario de múltiples pasos. | sesión | +| GitHub | `gist_oauth_csrf` | Esta cookie se establece por Gist para asegurar que el usuario que inició el flujo OAuth sea el mismo usuario que lo completa. | se borra al validar el estado de oauth | +| GitHub | `gist_user_session` | Esta cookie es usada por Gist cuando se ejecuta en un host por separado. | dos semanas | +| GitHub | `has_recent_activity` | Esta cookie se utiliza para prevenir que se muestre la seguridad que es intersticial a los usuarios que han visitado la app recientemente. | una hora | +| GitHub | `__Host-gist_user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub. | dos semanas | +| GitHub | `__Host-user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub. | dos semanas | +| GitHub | `logged_in` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | un año | +| GitHub | `marketplace_repository_ids` | Esta cookie se utiliza para el flujo de instalación de marketplace. | una hora | +| GitHub | `marketplace_suggested_target_id` | Esta cookie se utiliza para el flujo de instalación de marketplace. | una hora | +| GitHub | `_octo` | Esta cookie se utiliza para la administración de sesiones, incluyendo el almacenamiento en caché del contenido dinámico, el acceso de características condicionales, los metadatos de solicitud de soporte y la analítica de las primeras partes. | un año | +| GitHub | `org_transform_notice` | Esta cookie se utiliza para proporcionar notificaciones durante las transformaciones de las organizaciones. | una hora | +| GitHub | `private_mode_user_session` | Esta cookie se utiliza para las solicitudes de autenticación empresarial. | dos semanas | +| GitHub | `saml_csrf_token` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `saml_csrf_token_legacy` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `saml_return_to` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `saml_return_to_legacy` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML. | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación | +| GitHub | `tz` | Esta cookie nos permite personalizar las marcas de tiempo a tu zona horaria. | sesión | +| GitHub | `user_session` | Esta cookie se utiliza para que inicies sesión. | dos semanas | _*_ Las fechas de **vencimiento** para las cookies que se listan a continuación generalmente se aplican permanentemente. -(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. Por ejemplo, es posible que insertamos contenido, como vídeos, desde otro sitio que establezca una cookie. Si bien tratamos de minimizar estas cookies de terceros, no siempre podemos controlar qué cookies establece este contenido de terceros. +(i) Por favor, ten encuenta que si bien limitamos nuestro uso de cookies de terceros a aquellas necesarias para proporcionar una funcionalidad externa cuando interpretamos el contenido externo, algunas páginas en nuestro sitio web podrían configurar otras cookies de terceros. Por ejemplo, es posible que insertamos contenido, como vídeos, desde otro sitio que establezca una cookie. Si bien tratamos de minimizar estas cookies de terceros, no siempre podemos controlar qué cookies establece este contenido de terceros. diff --git a/translations/es-ES/content/github/site-policy/github-terms-of-service.md b/translations/es-ES/content/github/site-policy/github-terms-of-service.md index 8376e86b84..756e229a2e 100644 --- a/translations/es-ES/content/github/site-policy/github-terms-of-service.md +++ b/translations/es-ES/content/github/site-policy/github-terms-of-service.md @@ -69,7 +69,7 @@ Tenemos unas cuantas reglas simples para cuentas de usuario en el servicio de Gi - Una persona o entidad legal no puede mantener más de una cuenta gratuita (si también decide controlar una cuenta de máquina, está bien, pero sólo se puede utilizar para ejecutar una máquina). - Debes ser mayor de 13 años. Si bien estamos encantados de ver a los geniales programadores jóvenes entusiasmados aprendiendo a programar, debemos cumplir con la ley de los Estados Unidos. GitHub no dirige nuestro Servicio a niños menores de 13 años y no permitimos ningún Usuario menor de 13 años en nuestro Servicio. Si tenemos conocimiento de algún usuario menor de 13 años, [daremos por terminada inmediatamente la cuenta del usuario](#l-cancellation-and-termination). Si estás ubicado en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. - Su inicio de sesión sólo puede usarse por una persona — es decir, un único inicio de sesión no puede ser compartido por varias personas. Una Organización de pago sólo puede proporcionar acceso a tantas cuentas de usuario como su suscripción lo permita. -- No puedes usar GitHub en violación de las leyes de control de exportación o sanciones de los Estados Unidos o de cualquier otra jurisdicción aplicable. No puedes usar GitHub si estás trabajando o en nombre de un [Nacional Especialmente Diseñado (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o una persona sujeta a prohibiciones similares de bloqueo o denegadas por una agencia gubernamental de EE. UU. government agency. GitHub puede permitir que personas en ciertos países o territorios sancionados accedan a ciertos servicios de GitHub de conformidad con las autorizaciones del gobierno de los Estados Unidos. government authorizations. For more information, please see our [Export Controls policy](/articles/github-and-export-controls). +- No puedes usar GitHub en violación de las leyes de control de exportación o sanciones de los Estados Unidos o de cualquier otra jurisdicción aplicable. No puedes utilizar GitHub si eres o estás trabajando en nombre de un [Nacional Especialmente Diseñado (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o de una persona sujeta a prohibiciones de bloqueo de partes o denegadas similares que administre una agencia gubernamental de los EE.UU. GitHub puede permitir que las personas en ciertos países o territorios sancionados accedan a ciertos servicios de GitHub de conformidad con las autorizaciones del gobierno de los EE.UU. Para obtener más información, consulta nuestra[Política de Controles de Exportación](/articles/github-and-export-controls). #### 4. Seguridad de la cuenta de usuario Eres responsable de mantener tu Cuenta segura mientras utilizas nuestro Servicio. Ofrecemos herramientas como autenticación de dos factores para ayudarte a mantener la seguridad de tu cuenta pero el contenido de tu Cuenta y su seguridad depende de ti. diff --git a/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index 7887d2229e..41fb827813 100644 --- a/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/es-ES/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -62,7 +62,7 @@ Aunque la siguiente tabla contiene información acerca de las categorías de inf | Cualquier categoría de información personal descrita en la subdivisión (e) de Cal. Civ. Code §1798.80 (la cual define a la "información personal" como "cualquier tipo de información que identifica, relaciona, describe, o es capaz de asociarse con un individuo en particular" — con ejemplos que incluyen nombre, dirección, número de tarjeta de crédito o débito—y excluye la información disponible al público en general) | Información que el consumidor proporciona directamente | Perseguir a aquellos responsables por actividades malignas, engañosas, fraudulentas o ilegales.

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | | Las características de las clasificaciones protegidas bajo la ley federal de California (tales como género, edad) | Información que el consumidor decida proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | | Información comercial (tal como aquella acerca de la compra, obtención, consideración de bienes o servicios, u otro tipo de historial o tendencia de compra o consumo) | Información que proporciona el consumidor directamente o automáticamente a través de su interacción con nuestros Servicios | Depuración para identificar y reparar errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para propósitos comerciales o de negocios | | Información de actividad en internet o en otra red electrónica (tal como historial de internet, historial de búsqueda, e información relacionada con la interacción de un cliente con una aplicación o sitio web de internet) | Información que el cliente proporciona automáticamente a través de su interacción con nuestros Servicios | Detectar incidentes de seguridad, proteger contra la actividad maligna, engañosa, fraudulenta, o ilegal, y perseguir a los responsables de dicha actividad

    Depurar para identificar y reparar errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios

    Realizar investigación interna sobre demostraciones y desarrollo tecnológico

    Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | - Datos de Geolocalización (tales como la dirección IP) | Información que el consumidor proporciona automáticamente a través de su interacción con nuestros servicios | Detectar incidentes de seguridad, proteger contra actividades malignas, engañosas fraudulentas o ilegales, y perseguir a los responsables de dicha actividad

    Depurar para identificar y reparar los errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios

    Realizar investigación interna sobre demostraciones y desarrollo tecnológico

    Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios |Información de audio, electrónica, visual o similar | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Información profesional o relacionada con el empleo | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Infomración de la educación que no está disponible públicamente ni identifica a las personas | Esta categoría de información personal se ha divulgado con fines comerciales o de negocios | Información como se define en la Ley de Privacidad y Derechos Educacionales Familiares (20 U. S.C. Sec. Sección 1232g; 34 C. F.R. Parte 99) | Información que el consumidor pudiera proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Inferencias extraídas de cualquier información identificada en esta tabla para crear un perfil acerca de un consumidor, el cual refleje las preferencias del mismo | Información que el consumidor proporciona directamente o automáticamente a través de su interacción con nuestros Servicios | Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | + Datos de Geolocalización (tales como la dirección IP) | Información que el consumidor proporciona automáticamente a través de su interacción con nuestros servicios | Detectar incidentes de seguridad, proteger contra actividades malignas, engañosas fraudulentas o ilegales, y perseguir a los responsables de dicha actividad

    Depurar para identificar y reparar los errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios

    Realizar investigación interna sobre demostraciones y desarrollo tecnológico

    Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios |Información de audio, electrónica, visual o similar | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Información profesional o relacionada con el empleo | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Infomración de la educación que no está disponible públicamente ni identifica a las personas | Esta categoría de información personal se ha divulgado con fines comerciales o de negocios | Información como se define en la Ley de Privacidad y Derechos Educacionales Familiares (20 U. S.C. Sec. 1232g; 34 C. F.R. Parte 99) | Información que el consumidor pudiera proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Inferencias extraídas de cualquier información identificada en esta tabla para crear un perfil acerca de un consumidor, el cual refleje las preferencias del mismo | Información que el consumidor proporciona directamente o automáticamente a través de su interacción con nuestros Servicios | Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | ## Ejemplos bajo la CCPA diff --git a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md index 9e3571eae2..c38fcf93d8 100644 --- a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md +++ b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md @@ -16,14 +16,13 @@ Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profe ### Antes de comenzar -***Di la Verdad.*** La DMCA requiere que jures tu contra notificación *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [Código de Estados Unidos, Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Code, Title 18, Section 1621.) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. +***Di la Verdad.*** La DMCA requiere que jures tu contra notificación *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [el Código de lso EE.UU. , Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. ***Investiga.*** Enviar una contra notificación DMCA puede tener consecuencias legales reales. Si la parte que denuncia no está de acuerdo en que tu notificación de retiro fue errónea, podrían decidir presentar una demanda contra ti para mantener el contenido deshabilitado. Deber llevar a cabo una investigación exhaustiva sobre las acusaciones hechas en la notificación de retiro y probablemente hablar con un abogado antes de enviar una contra notificación. -***Debes tener una razón fundada para emitir una contranotificación.*** Para emitir una contranotificación, deberás tener una "certeza de buena fe de que el material se eliminó o inhabilitó como resultado de un error o mala identificación del material que se quiere eliminar o inhabilitar". (U.S. ([Título 17 del Código de los EEUU, Sección 512(g)](https://www.copyright.gov/title17/92chap5.html#512)). Ya sea que decidas explicar o no el por qué crees que hubo un error, dependerá de ti y de tu abogado, pero *sí* necesitas identificar un error antes de emitir una contranotificación. En el pasado, recibimos contra notificaciones que citan errores en la notificación de retiro, tales como: La parte que reclama no tiene el derecho de autor; tengo una licencia; el código se liberó bajo una licencia de código abierto que permite mi uso; o la queja no tiene en cuenta el hecho de que mi uso está protegido por la doctrina del uso legal. Por supuesto, podría haber otros defectos con la notificación de retiro.

    +***Debes tener una razón fundada para emitir una contranotificación.*** Para emitir una contranotificación, deberás tener una "certeza de buena fe de que el material se eliminó o inhabilitó como resultado de un error o mala identificación del material que se quiere eliminar o inhabilitar". ([Código de los EE.UU. Título 17, Sección 512(g)](https://www.copyright.gov/title17/92chap5.html#512)). Ya sea que decidas explicar o no el por qué crees que hubo un error, dependerá de ti y de tu abogado, pero *sí* necesitas identificar un error antes de emitir una contranotificación. En el pasado, recibimos contra notificaciones que citan errores en la notificación de retiro, tales como: La parte que reclama no tiene el derecho de autor; tengo una licencia; el código se liberó bajo una licencia de código abierto que permite mi uso; o la queja no tiene en cuenta el hecho de que mi uso está protegido por la doctrina del uso legal. Por supuesto, podría haber otros defectos con la notificación de retiro. ***Las leyes de derechos de autor son complicadas.*** En ocasiones una notificación de retiro podría hacer referencia a una infracción que parece extraña o indirecta. Las leyes de derechos de autor son complicadas y pueden dar lugar a resultados inesperados. En algunos casos una notificación de retiro podría señalar que su código fuente infringe por lo que puede ocasiones posteriormente que se compile y ejecute. Por ejemplo: - - La notificación podrá reclamar que tu software se utiliza para [evitar los controles de acceso](https://www.copyright.gov/title17/92chap12.html) a los trabajos con derechos de autor. - [Algunas veces](https://www.copyright.gov/docs/mgm/) la distribución de software puede considerarse como una infracción a los derechos de autor, si induces a los usuarios finales a utilizar el software para infringir el trabajo con derechos de autor. - Una queja de derechos de autor también podría basarse en [copia no literal](https://en.wikipedia.org/wiki/Substantial_similarity) de elementos de diseño en el software, en lugar del código fuente en sí mismo, en otras palabras, alguien envió una notificación diciendo que piensa que tu *diseño* es demasiado similar al de ellos. @@ -38,8 +37,6 @@ Estos son sólo algunos ejemplos de la complejidad de la legislación sobre dere ***Recursos Adicionales.*** Si necesitas ayuda adicional, hay muchos recursos de autoayuda en línea. Lumen tiene un conjunto informativo de guías sobre [copyright](https://www.lumendatabase.org/topics/5) y [puerto seguro de DMCA](https://www.lumendatabase.org/topics/14). Si estás implicado con un proyecto de código abierto que necesita asesoramiento legal, puedes ponerse en contacto con el [Centro de asesoramiento legal sobre software libre](https://www.softwarefreedom.org/about/contact/). Y si consideras que tienes un caso especialmente desafiante, organizaciones sin fines de lucro como la [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) también pueden estar dispuestas a ayudarte directamente o a referirte a un abogado. - - ### Tu contra notificación debe... 1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una contra notificación DMCA.** No nos negaremos a procesar una contra notificación completa si no incluye esta declaración; sin embargo, sabremos que no has leído estas directrices y podríamos solicitarte que lo hagas. @@ -54,8 +51,6 @@ Estos son sólo algunos ejemplos de la complejidad de la legislación sobre dere 6. **Incluye tu firma física o electrónica.** - - ### Cómo enviar tu contra notificación La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}. @@ -64,8 +59,6 @@ También puedes enviar una notificación por correo electrónico a .) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. La DMCA por sí misma [proporciona daños](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) contra cualquier persona que, a sabiendas, tergiversa materialmente dicha actividad o material infractor. +***Di la Verdad.*** La DMCA requiere que prestes atención a los hechos en tu queja de derechos de autor *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [el Código de lso EE.UU. , Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. La DMCA por sí misma [proporciona daños](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) contra cualquier persona que, a sabiendas, tergiversa materialmente dicha actividad o material infractor. ***Investiga.*** Millones de usuarios y organizaciones se esfuerzan demasiado en los proyectos que crean y contribuyen en GitHub. La presentación de una queja de DMCA contra un proyecto de este tipo es una acusación legal seria que conlleva consecuencias reales para las personas reales. Por eso, te pedimos que realices una investigación exhaustiva y consultes con un abogado antes de enviar una solicitud de retiro para asegurarte que el uso no sea realmente permisible. diff --git a/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 09b7c27243..d50e423296 100644 --- a/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ Tenga en cuenta que la información disponible variará de un caso a otro. Parte ### Reembolso de costes -Nos reservamos el derecho de solicitar el reembolso de los gastos administrativos asociados con la respuesta a las solicitudes de información, de acuerdo con lo permitido por la ley. +Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. + +While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: + +- Initial search of up to 25 identifiers: Free +- Production of subscriber information/data for up to 5 accounts: Free +- Production of subscriber information/data for more than 5 accounts: $20 per account +- Secondary searches: $10 per search ### Conservación de datos @@ -176,7 +183,7 @@ Por favor, espera al menos dos semanas para que podamos examinar tu solicitud. ### Solicitudes de aplicación de la ley extranjera -Como empresa de Estados Unidos con sede en California, GitHub no está obligada a proporcionar datos a los gobiernos extranjeros en respuesta al proceso legal emitido por autoridades extranjeras. Los funcionarios encargados de hacer cumplir la ley extranjera que deseen solicitar información a GitHub deben ponerse en contacto con la Oficina de Asuntos Internacionales del Departamento de Justicia de los Estados Unidos. GitHub responderá rápidamente a las solicitudes que se emitan a través del tribunal de los Estados Unidos mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory. +Como empresa de Estados Unidos con sede en California, GitHub no está obligada a proporcionar datos a los gobiernos extranjeros en respuesta al proceso legal emitido por autoridades extranjeras. Los funcionarios encargados de hacer cumplir la ley extranjera que deseen solicitar información a GitHub deben ponerse en contacto con la Oficina de Asuntos Internacionales del Departamento de Justicia de los Estados Unidos. GitHub responderá rápidamente a las solicitudes que se emitan a través del tribunal de los Estados Unidos mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto. mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto. ### Preguntas diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 2b7dfe96ad..1a45b7cd17 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -32,5 +32,5 @@ Puedes configurar una meta para tus patrocinios. Para obtener más información, Para obtener más información, consulta "[Administrar tus pagos de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)". -### Further reading +### Leer más - "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index 61b97f9b7d..103e9b9e60 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -37,7 +37,7 @@ Para ser elegible para el {% data variables.product.prodname_matching_fund %}, d Este es sólo el inicio — nos encantaría tener tu opinión para garantizar que {% data variables.product.prodname_sponsors %} siga satisfaciendo tus necesidades. Por favor, envíanos tu retroalimentación o sugerencias contactando a [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). -### Further reading +### Leer más - "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" - "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)". - "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index c28562af82..90682588f5 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -29,7 +29,7 @@ Puedes elegir si una cuenta que patrocinas puede enviarte actualizaciones por co {% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### Further reading +### Leer más - "[Mejorar un patrocinio](/articles/upgrading-a-sponsorship)" - "[Degradar un patrocinio](/articles/downgrading-a-sponsorship)" \ No newline at end of file diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md index 56bffa7b93..5da0e465b7 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/overview.md @@ -1,7 +1,7 @@ --- title: Resumen intro: 'Aprende sobre {% data variables.product.prodname_sponsors %} y sobre cómo puedes involucrarte como patrocinador o como colaborador de código abierto.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md index 9c42775755..a16bebd266 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors.md @@ -2,7 +2,7 @@ title: Recibir patrocinios a través de patrocinadores de GitHub shortTitle: Recibir patrocinios intro: 'Tu organización o tú pueden convertirse en un colaborador de código abierto para recibir pagos por su trabajo, actualizar sus detalles de patrocinio y ver y contactar a sus patrocinadores.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/receiving-sponsorships-as-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 3312db091b..6192ba6cd7 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -80,6 +80,6 @@ Antes de que tu organización pueda convertirse en patrocinada, deberás habilit {% data reusables.sponsors.github-review-app %} -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" - "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)". diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 1cb9b5d5c3..756ce1e42b 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -22,7 +22,7 @@ Puedes patrocinar una cuenta en nombre de tu cuenta de usuario para invertir en - Desarrollar una conciencia de marca como una organización que valora el código abierto - Agradecer a los desarrolladores de código abierto por crear bibliotecas que complementan el producto que ofrece tu organización -Puedes utilizar una tarjeta de crédito para patrocinar una cuenta en {% data variables.product.product_name %}. Si tu organización necesita que se le emita una factura, [contáctanos](https://support.github.com/contact/org-sponsors-waitlist). +Puedes utilizar una tarjeta de crédito para patrocinar una cuenta en {% data variables.product.product_name %}. Si tu organización quiere pagar por factura, [contáctanos](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md index 2b155ba87a..b30bc01b63 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors.md @@ -1,7 +1,7 @@ --- title: Patrocinar a colaboradores de código abierto intro: 'Puedes patrocinar colaboradores, recibir actualizaciones sobre los programadores y las organizaciones que patrocinas, y mostrar una insignia de patrocinador en todo {% data variables.product.product_name %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/sponsoring-open-source-developers - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md index c7f2bf2e9a..abe3984c7e 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors.md @@ -16,6 +16,6 @@ Si eres contribuyente en los Estados Unidos y ganas más de $600 en un año fisc {% data reusables.sponsors.sponsorships-not-tax-deductible %} -### Further reading +### Leer más - [Ver tus patrocinadores y patrocinios](/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 3bd17927c7..63fd25f9e7 100644 --- a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -23,9 +23,9 @@ Puedes ver la analítica de tus patrocinios actuales y pasados, los pagos que ha ### Exportar tus datos de patrocinio -You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. Después de que se complete la exportación, puedes exportar otor mes de datos. Puedes exportar hasta 10 conjuntos de datos por hora para cualquiera de tus cuentas patrocinadas. +Puedes exportar tus transacciones de patrocinio mensualmente. {% data variables.product.company_short %} te enviará un correo electrónico con los datos de las transacciones de todos tus patrocinadores para el mes que selecciones. Después de que se complete la exportación, puedes exportar otor mes de datos. Puedes exportar hasta 10 conjuntos de datos por hora para cualquiera de tus cuentas patrocinadas. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.activity-tab %} -1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Botón de exportar](/assets/images/help/sponsors/export-all.png) +1. Da clic en {% octicon "download" aria-label="The download icon" %} **Exportar**. ![Botón de exportar](/assets/images/help/sponsors/export-all.png) 1. Elige un formato y periodo de tiempo para los datos que quieres exportar. Posteriormente, da clic en **Comenzar exportación**. ![Opciones para exportar datos](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index decb95e352..3721e0982f 100644 --- a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -23,7 +23,7 @@ Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a {% 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 el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) -### Further reading +### Leer más - "[Acerca del uso de tus datos de {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)" - "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md index 285c8a2302..f678adbda4 100644 --- a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md +++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md @@ -14,5 +14,5 @@ Si rechazas el ingreso de un repositorio al {% data variables.product.prodname_a {% data reusables.repositories.sidebar-settings %} 3. Debajo de "Características", selecciona o deselecciona **Preservar este repositorio**. ![Casilla para permitir a {% data variables.product.prodname_dotcom %} incluir tu código en el {% data variables.product.prodname_archive %}](/assets/images/help/repository/github-archive-program-checkbox.png) -### Further reading +### Leer más - [{% data variables.product.prodname_archive %} Preguntas Frecuentes](https://archiveprogram.github.com/faq/) diff --git a/translations/es-ES/content/github/using-git/about-git-rebase.md b/translations/es-ES/content/github/using-git/about-git-rebase.md index 333a436305..ed8be85ebf 100644 --- a/translations/es-ES/content/github/using-git/about-git-rebase.md +++ b/translations/es-ES/content/github/using-git/about-git-rebase.md @@ -52,7 +52,7 @@ Hay seis comandos disponibles mientras se cambia la base:
    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.
    -
    editar
    +
    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.
    squash
    @@ -97,14 +97,14 @@ Desglosando esta información, de principio a fin, vemos que: - 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. The changes you make are *rebased* onto your repository. +- 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. -### Further reading +### Leer más - "[Usar 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) +- [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 %} diff --git a/translations/es-ES/content/github/using-git/about-git-subtree-merges.md b/translations/es-ES/content/github/using-git/about-git-subtree-merges.md index 419ad7bc71..dcfeeb0561 100644 --- a/translations/es-ES/content/github/using-git/about-git-subtree-merges.md +++ b/translations/es-ES/content/github/using-git/about-git-subtree-merges.md @@ -103,7 +103,7 @@ Para el ejemplo de más arriba, esto sería: $ git pull -s subtree spoon-knife main ``` -### Further reading +### Leer más - [El capítulo de "Fusión Avanzada" del libro de _Pro Git_](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) - "[Cómo usar la estrategia de fusión de subárbol](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)" diff --git a/translations/es-ES/content/github/using-git/adding-a-remote.md b/translations/es-ES/content/github/using-git/adding-a-remote.md index 0a2df5c632..318bee896a 100644 --- a/translations/es-ES/content/github/using-git/adding-a-remote.md +++ b/translations/es-ES/content/github/using-git/adding-a-remote.md @@ -47,6 +47,6 @@ Para arreglar esto, puedes * [Renombrar el remoto existente](/articles/renaming-a-remote) * [Eliminar el remoto existente](/articles/removing-a-remote) -### Further reading +### Leer más - "[Trabajar con remotos" desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md b/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md index 4156e631b4..ef5d43c060 100644 --- a/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md +++ b/translations/es-ES/content/github/using-git/caching-your-github-credentials-in-git.md @@ -96,7 +96,7 @@ Activa tu ayudante de credenciales de manera que Git guarde tu contraseña en la {% endlinux %} -### Further reading +### Leer más - "[Actualizar credenciales desde la Keychain OSX](/articles/updating-credentials-from-the-osx-keychain/)" - "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/es-ES/content/github/using-git/changing-a-remotes-url.md b/translations/es-ES/content/github/using-git/changing-a-remotes-url.md index 2a7d5ee07f..1942528aef 100644 --- a/translations/es-ES/content/github/using-git/changing-a-remotes-url.md +++ b/translations/es-ES/content/github/using-git/changing-a-remotes-url.md @@ -92,6 +92,6 @@ $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/ Comprueba que escribiste correctamente el nombre del remoto. -### Further reading +### Leer más - ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md b/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md index abad70e410..bad5c597c7 100644 --- a/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md +++ b/translations/es-ES/content/github/using-git/configuring-git-to-handle-line-endings.md @@ -122,7 +122,7 @@ Para garantizar que todos los fines de línea en tu repositorio concuerdan con t $ git commit -m "Normalize all the line endings" ``` -### Further reading +### Leer más - [Personalizar Git - Atributos de Git](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) en el libro de Pro Git - [git-config](https://git-scm.com/docs/git-config) en las páginas man para Git diff --git a/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md b/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md index 3f9a975d01..18e28e66ec 100644 --- a/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md +++ b/translations/es-ES/content/github/using-git/getting-changes-from-a-remote-repository.md @@ -69,7 +69,7 @@ $ git pull remotename branchname 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. -### Further reading +### Leer más - ["Trabajar con remotos" del libro de _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% if currentVersion == "free-pro-team@latest" %} - "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)"{% endif %} diff --git a/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md b/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md index 5e352611f2..c51e95bfb4 100644 --- a/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md +++ b/translations/es-ES/content/github/using-git/getting-started-with-git-and-github.md @@ -1,7 +1,7 @@ --- title: Comenzar con Git y GitHub intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/getting-started-with-git-and-github versions: diff --git a/translations/es-ES/content/github/using-git/learning-about-git.md b/translations/es-ES/content/github/using-git/learning-about-git.md index 126ff7773d..918fae6654 100644 --- a/translations/es-ES/content/github/using-git/learning-about-git.md +++ b/translations/es-ES/content/github/using-git/learning-about-git.md @@ -1,7 +1,7 @@ --- title: Obtener información sobre Git intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/learning-about-git versions: diff --git a/translations/es-ES/content/github/using-git/managing-remote-repositories.md b/translations/es-ES/content/github/using-git/managing-remote-repositories.md index cc017ba8e3..b45539f1db 100644 --- a/translations/es-ES/content/github/using-git/managing-remote-repositories.md +++ b/translations/es-ES/content/github/using-git/managing-remote-repositories.md @@ -1,7 +1,7 @@ --- title: Administrar repositorios remotos intro: 'Aprende a trabajar con tus repositorios locales en tu computadora y repositorios remotos alojados en {% data variables.product.product_name %}.' -mapTopic: verdadero +mapTopic: true redirect_from: - /categories/18/articles/ - /remotes/ diff --git a/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md b/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md index 1fb3bf250e..4441ce44ef 100644 --- a/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/es-ES/content/github/using-git/pushing-commits-to-a-remote-repository.md @@ -92,7 +92,7 @@ Cuando hayas finalizado tus cambios locales, puedes subir tu rama local a GitHub Para obtener más información sobre cómo trabajar con bifurcaciones, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". -### Further reading +### Leer más - [El capítulo "Remotos" del libro "Pro Git"](https://git-scm.com/book/ch5-2.html) - [Documentación en línea sobre `git remote`](https://git-scm.com/docs/git-remote.html) diff --git a/translations/es-ES/content/github/using-git/removing-a-remote.md b/translations/es-ES/content/github/using-git/removing-a-remote.md index 54acf55be7..65d9c6dc07 100644 --- a/translations/es-ES/content/github/using-git/removing-a-remote.md +++ b/translations/es-ES/content/github/using-git/removing-a-remote.md @@ -54,6 +54,6 @@ $ git remote rm sofake Comprueba que escribiste correctamente el nombre del remoto. -### Further reading +### Leer más - ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/renaming-a-remote.md b/translations/es-ES/content/github/using-git/renaming-a-remote.md index 211300d9cb..d9c4e19762 100644 --- a/translations/es-ES/content/github/using-git/renaming-a-remote.md +++ b/translations/es-ES/content/github/using-git/renaming-a-remote.md @@ -54,6 +54,6 @@ $ git remote -v Este error significa que el nombre del remoto que quieres utilizar ya existe. Para resolverlo, utiliza un nombre de remoto diferente o renombra el remoto original. -### Further reading +### Leer más - ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-ES/content/github/using-git/setting-your-username-in-git.md b/translations/es-ES/content/github/using-git/setting-your-username-in-git.md index 56331e37d1..af04b63a91 100644 --- a/translations/es-ES/content/github/using-git/setting-your-username-in-git.md +++ b/translations/es-ES/content/github/using-git/setting-your-username-in-git.md @@ -45,7 +45,7 @@ Cambiar el nombre asociado con tus confirmaciones de Git utilizando `git config` > Mona Lisa ``` -### Further reading +### Leer más - "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" - ["Configuración de Git" del libro _Pro Git_](https://git-scm.com/book/en/Customizing-Git-Git-Configuration) diff --git a/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md b/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md index 6db041bab5..642f39fb2a 100644 --- a/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/es-ES/content/github/using-git/updating-credentials-from-the-macos-keychain.md @@ -32,6 +32,6 @@ protocol=https Si resulta exitoso, no se imprimirá nada. Para probar su funcionamiento, trata de clonar un repositorio desde {% data variables.product.product_location %}. Si se te pide una contraseña, la entrada de keychain se borró. -### Further reading +### Leer más - [Almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git/)" diff --git a/translations/es-ES/content/github/using-git/using-advanced-git-commands.md b/translations/es-ES/content/github/using-git/using-advanced-git-commands.md index 48b246fa58..5e8870934e 100644 --- a/translations/es-ES/content/github/using-git/using-advanced-git-commands.md +++ b/translations/es-ES/content/github/using-git/using-advanced-git-commands.md @@ -1,7 +1,7 @@ --- title: Utilizar comandos de Git avanzados intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /categories/52/articles/ - /categories/advanced-git/ diff --git a/translations/es-ES/content/github/using-git/using-common-git-commands.md b/translations/es-ES/content/github/using-git/using-common-git-commands.md index ee40fb8c0a..9051864927 100644 --- a/translations/es-ES/content/github/using-git/using-common-git-commands.md +++ b/translations/es-ES/content/github/using-git/using-common-git-commands.md @@ -1,7 +1,7 @@ --- title: Utilizar comandos de Git comunes intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/using-common-git-commands versions: diff --git a/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md index 170a9e7c3c..a744b10b50 100644 --- a/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/es-ES/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -137,6 +137,6 @@ El cargar forzadamente tiene implicaciones serias ya que cambia la secuencia del {% endwarning %} -### Further reading +### Leer más * "[Resolver conflictos de fusión después de una rebase de Git](/articles/resolving-merge-conflicts-after-a-git-rebase)" diff --git a/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md b/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md index 7abbd8f830..2f4af7fad0 100644 --- a/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/es-ES/content/github/using-git/which-remote-url-should-i-use.md @@ -65,6 +65,6 @@ También puedes acceder a los repositorios en {% data variables.product.prodname_dotcom %} desde los clientes de Subversion. Para obtener más información, consulta la sección "[Soporte para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". {% endif %} -### Further reading +### Leer más - [Trabajar con URL Remotas](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) del sitio del libro de _Pro Git_ diff --git a/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md b/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md index 48f4763a55..1b3ec05e18 100644 --- a/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md +++ b/translations/es-ES/content/github/using-git/why-is-git-always-asking-for-my-password.md @@ -15,7 +15,7 @@ Utilizar una URL remota de tipo HTTPS tiene algunas ventajas comparadas con el u Puedes evitar que se te solicite tu contraseña si configuras Git para que [almacene tus credenciales en el caché](/github/using-git/caching-your-github-credentials-in-git). Ya que hayas configurado el almacenamiento de credenciales en caché, Git utilizará to token de acceso personal almacenado en caché automáticamente cada que extraigas o subas información a un repositorio utilizando HTTPS. -### Further reading +### Leer más * "[¿Qué URL remota debería utilizar?](/articles/which-remote-url-should-i-use/#cloning-with-https-urls)" * "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md index 909416e68b..46af2ecce7 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md @@ -26,7 +26,7 @@ Todos los otros gráficos del repositorio están disponibles en todos los reposi {% endif %} -### Further reading +### Leer más - "[Acceso a datos básicos del repositorio](/articles/accessing-basic-repository-data)" - "[Analizar cambios en el contenido de un repositorio](/articles/analyzing-changes-to-a-repository-s-content)" diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index 13b26a1b0d..1a66878f1a 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -1,90 +1,89 @@ --- -title: Acerca del gráfico de dependencias -intro: 'Información detallada sobre la gráfica de dependencias, el ecosistema con el que es compatible, y sobre cómo determina de qué paquetes depende un repositorio.' +title: About the dependency graph +intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' versions: free-pro-team: '*' enterprise-server: '*' --- -### Disponibilidad de la gráfica de dependencias +### Dependency graph availability -La gráfica de dependencias se encuentra disponible para cada{% if currentVersion == "free-pro-team@latest" %} repositorio público{% endif %} que define las dependencias en un ecosistema de paquetes compatible utilizando un formato de archivo compatible.{% if currentVersion == "free-pro-team@latest" %} Los administradores del repositorio también pueden configurar la gráfica de dependencias para los repositorios privados.{% endif %} +The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} {% data reusables.repositories.enable-security-alerts %} -### 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{% if currentVersion == "free-pro-team@latest" %}: +The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: -- 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.prodname_ghe_server %} 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.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} -Cuando subes una confirmación a {% data variables.product.product_name %} que cambia o agrega un archivo bloqueado o de manifiesto compatible a la rama predeterminada, la gráfica de dependencias se actualiza automáticamente.{% if currentVersion == "free-pro-team@latest" %} Adicionalmente, la gráfica se actualiza cuando cualquiera carga un cambio al repositorio de una de tus dependencias.{% endif %} Para obtener más información sobre los archivos de manifiesto y ecosistemas compatibles, consulta la sección "[Ecosistemas de paquetes compatibles](#supported-package-ecosystems)" más adelante. +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.{% if currentVersion == "free-pro-team@latest" %} 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. {% if currentVersion == "free-pro-team@latest" %} -Cuando creas una solicitud de cambios que contenga cambios para las dependencias que apunten a la rama predeterminada, -{% data variables.product.prodname_dotcom %} utilizará la gráfica de dependencias para agregar revisiones de dependencias a la soicitud 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 "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +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 "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." {% 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 las dependencias indirectas{% if currentVersion == "free-pro-team@latest" %} ya sea explícitamente desde un archivo bloqueado o mediante la verificación de las 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{% if currentVersion == "free-pro-team@latest" %} 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 %}. {% if currentVersion == "free-pro-team@latest" %} -### 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{% if currentVersion == "free-pro-team@latest" %} y aquellos que dependen de él{% 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)". {% if currentVersion == "free-pro-team@latest" %} -- 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](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".{% if currentVersion == "free-pro-team@latest" %} -- 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{% if currentVersion == "free-pro-team@latest" %}, 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)." {% if currentVersion == "free-pro-team@latest" %} +- 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](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} +- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %} -### Habilitar la gráfica de dependencias +### Enabling the dependency graph -{% if currentVersion == "free-pro-team@latest" %}Para generar una gráfica de dependencias, {% data variables.product.product_name %} necesita acceso de solo lectura a los archivos bloqueados y de manifiesto de la dependencia para el repositorio en cuestión. 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)." +{% if currentVersion == "free-pro-team@latest" %}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 %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}Si la gráfica de dependencias no se encuentra disponible en tu sistema, tu administrador de sitio puede habilitarla junto con las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Si la gráfica de dependencias no está disponible en tu sistema, tu administrador de sitio puede habilitarla, así como puede habilitar las alertas de seguridad. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." {% 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 habilite, la gráfica se actualiza automáticamente con cada subida al repositorio{% if currentVersion == "free-pro-team@latest" %} y con cada subida a otros repositorios en 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{% if currentVersion == "free-pro-team@latest" %} 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 la gráfica de dependencias para reportar vulnerabilidades tanto en las dependencias directas como en las indirectas.{% if currentVersion == "free-pro-team@latest" %} Las dependencias directas que se infieran de un archivo de manifiesto (o de su equivalente) se excluirán de las verificaciones para las 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.{% if currentVersion == "free-pro-team@latest" %} 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` | -| 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.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| 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` | +| 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.lock`, `setup.py`* | +| 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 %} ### Further reading -- "[Gráfica de dependencias](https://en.wikipedia.org/wiki/Dependency_graph)" en Wikipedia -- "[Explorando las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Visualizar las perspectivas para tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[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)"{% endif %} +- "[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)"{% if currentVersion == "free-pro-team@latest" %} +- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[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)"{% endif %} diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md index 717db538ec..ea84333a95 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md @@ -1,7 +1,7 @@ --- title: Acceso a datos básicos del repositorio intro: 'Puedes ver la información básica de un repositorio, tal como la actividad del mismo{% if currentVersion == "free-pro-team@latest" %}, su tráfico,{% endif %} y la actividad de las contribuciones.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/accessing-basic-repository-data versions: diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md index b03d193a6b..a40708229c 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md @@ -5,7 +5,7 @@ redirect_from: - /articles/viewing-commit-frequency-in-a-repository/ - /articles/analyzing-changes-to-a-repository-s-content - /articles/analyzing-changes-to-a-repositorys-content -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index 660520b06b..a4ff5bc576 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -67,7 +67,7 @@ Se listará cualquier dependencia directa e indirecta que se especifique en los 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. -![Dependents graph](/assets/images/help/graphs/dependents_graph.png) +![Gráfica de dependientes](/assets/images/help/graphs/dependents_graph.png) ### Habilitar e inhabilitar la gráfica de dependencias para un repositorio privado @@ -82,22 +82,22 @@ También puedes habilitar o inhabilitar la gráfica de dependencias para todos l 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. -### Changing the "Used by" package +### Cambiar el paquete "Utilizado por" -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)." +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)". -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. +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. -!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png) +![Sección de "Utilizado por" en la barra lateral](/assets/images/help/repository/used-by-section.png) -Clicking any item in this section takes you to the **Dependents** tab of the dependency graph. +Dar clic en cualquier elemento de esta sección te lleva a la pestaña de **Dependientes** de la gráfica de dependencias. -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. +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". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -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) +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) {% endif %} @@ -111,7 +111,7 @@ usuario de {% data variables.product.prodname_enterprise %}. Este procesa hasta 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. -### Further reading +### Leer más - "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} - "[Visualizar las perspectivas para tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md index cccf34fada..27d205b8d4 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md @@ -1,7 +1,7 @@ --- title: Entender las conexiones entre repositorios intro: 'Puedes entender mejor las conexiones que existen entre repositorios si ves la red de un repositorio{% if currentVersion == "free-pro-team@latest" %}, los proyectos que dependen de él,{% endif %} y sus bifurcaciones.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/understanding-connections-between-repositories versions: diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md index fbc7970545..746d82c08a 100644 --- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md +++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md @@ -12,7 +12,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -![Code frequency graph](/assets/images/help/graphs/repo_code_frequency_graph_dotcom.png) +![Gráfico de frecuencia de código](/assets/images/help/graphs/repo_code_frequency_graph_dotcom.png) {% endif %} diff --git a/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md index 7371163e2e..1d0cb59b9e 100644 --- a/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md +++ b/translations/es-ES/content/github/working-with-github-pages/about-custom-domains-and-github-pages.md @@ -58,6 +58,6 @@ Existen algunos motivos por los que tu sitio pueda estar inhabilitado automátic - 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)". -### Further reading +### Leer más - "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index 267b71e05b..7d24900c05 100644 --- a/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ Puedes configurar la mayoría de los parámetros de Jekyll, como los temas y los Algunos parámetros de configuración no pueden cambiarse para los sitios {% data variables.product.prodname_pages %} sites. -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ Por defecto, los bloques de código en su sitio serán resaltados por Jekyll. Je Si quieres usar otro resaltador, como `highlight.js`, debes desactivar el resaltador de sintaxis de Jekyll actualizando el archivo de tu proyecto *_config.yml*. -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md index 1ff28543c5..edb188e0f3 100644 --- a/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/es-ES/content/github/working-with-github-pages/about-github-pages.md @@ -25,11 +25,15 @@ Puedes hospedar 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)". {% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% 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 %}](/github/working-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)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 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 "[Inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". +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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". {% endif %} ### Tipos de sitios {% data variables.product.prodname_pages %} @@ -40,6 +44,10 @@ Para publicar un sitio de usuario, debes crear un repositorio que pertenezca a t Los archivos fuente para un sitio de proyecto se almacenan en el mismo repositorio que su proyecto. {% if currentVersion == "free-pro-team@latest" %}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 currentVersion == "github-ae@latest" %}Los sitios de proyecto se encuentran disponibles en `http(s)://pages.///` o `http(s)://pages.///`.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +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 %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} 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)". {% endif %} @@ -57,7 +65,7 @@ La URL en donde tu sitio está disponible dependerá de si habilitaste o no el a `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 "[Habilitar el aislamiento del subdominio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" o comunícate con el administrador del sitio. +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. {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -84,15 +92,15 @@ Si eliges la carpeta `/docs` de cualquier rama como tu fuente de publicación, { {% else %} -La fuente de publicación predeterminada para los sitios de usuario y organización es la rama `principal`. Si el repositorio para tu sitio de usuario u organización tiene una rama `principal`, tu sitio se publicará automáticamente desde esa rama. No puedes elegir una fuente de publicación diferente para sitios de usuario u organización. +La fuente de publicación predeterminada para los sitios de usuario y organización es la rama `master`. Si el repositorio para tu sitio de usuario u organización tiene una rama `master`, tu sitio se publicará automáticamente desde esa rama. No puedes elegir una fuente de publicación diferente para sitios de usuario u organización. La fuente de publicación predeterminada para un sitio de proyecto es la rama `gh-pages`. Si el repositorio para tu sitio de proyecto tiene una rama `gh-pages`, tu sitio se publicará automáticamente desde esa rama. -Los sitios del proyecto también pueden publicarse desde la rama `principal` o una carpeta `/docs` en la rama `master`. Para publicar tu sitio desde una de estas fuentes, debes configurar una fuente de publicación diferente. 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)". +Los sitios del proyecto también pueden publicarse desde la rama `master` o una carpeta `/docs` en la rama `master`. Para publicar tu sitio desde una de estas fuentes, debes configurar una fuente de publicación diferente. 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)". - Si eliges la carpeta `/docs` de la rama `master` como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% if currentVersion == "free-pro-team@latest" %}, incluyendo el archivo de _CNAME_,{% endif %} de la carpeta `/docs`. {% if currentVersion == "free-pro-team@latest" %} 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 %} +Si eliges la carpeta `/docs` de la rama `master` como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% if currentVersion == "free-pro-team@latest" %}, incluyendo el archivo de _CNAME_,{% endif %} de la carpeta `/docs`. {% if currentVersion == "free-pro-team@latest" %} 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 %} - No puedes publicar tu sitio de proyecto desde ninguna otra rama, aún si la rama predeterminada es diferente a `master` o `gh-pages`. +No puedes publicar tu sitio de proyecto desde ninguna otra rama, aún si la rama predeterminada es diferente a `master` o `gh-pages`. {% endif %} @@ -149,7 +157,7 @@ Un tipo MIME es un encabezado que un servidor envía a un navegador, proporciona 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). -### Further reading +### Leer más - [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) en {% data variables.product.prodname_learning %} - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index bc2073bcde..17ee5b28c6 100644 --- a/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/es-ES/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ Puedes ver errores de compilación (pero no advertencias de compilación) para t Puedes configurar un servicio externo como [Travis CI](https://travis-ci.org/) para que muestre mensajes de error después de cada confirmación. 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: - ``` + ```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: - ``` + ```yaml language: ruby rvm: - 2.3 diff --git a/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index a03c22c8eb..19b8ef1ee8 100644 --- a/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ Las personas con permisos de escritura para un repositorio pueden agregar un tem {% data reusables.pages.navigate-publishing-source %} 1. Crea un archivo nuevo denominado _/assets/css/style.scss_. 2. Agrega el siguiente contenido en la parte superior del archivo: - ``` + ```scss --- --- @@ -63,6 +63,6 @@ Las personas con permisos de escritura para un repositorio pueden agregar un tem 7. Pega el contenido del diseño personalizado que copiaste anteriormente. 8. Personaliza el diseño como desees. -### Further reading +### Leer más - "[Crear archivos nuevos](/articles/creating-new-files)" diff --git a/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md index b806021667..a25e7d940b 100644 --- a/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md +++ b/translations/es-ES/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -37,6 +37,6 @@ Si antes agregaste manualmente un tema de Jekyll a tu repositorio, puede que eso El tema elegido se aplicará automáticamente a los archivos markdown de tu repositorio. Para aplicar el tema a los archivos HTML de tu repositorio, debes agregar el texto preliminar de YAML que especifica un diseño para cada archivo. Para obtener más información, consulta "[Texto preliminar](https://jekyllrb.com/docs/front-matter/)" en el sitio de Jekyll. -### Further reading +### Leer más - [Temas](https://jekyllrb.com/docs/themes/) en el sitio de Jekyll diff --git a/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 7393b9fada..41ce6f1c30 100644 --- a/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,7 +62,7 @@ Tu tema incluye diseños predeterminados, inclusiones y hojas de estilos que se {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. +¡Ahora tu publicación debería estar disponible en tu sitio! Si la URL base de tu sitio es `https://octocat.github.io`, entonces tu publicación nueva se ubicará en `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. ### Pasos siguientes diff --git a/translations/es-ES/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..5c5c3409fe --- /dev/null +++ b/translations/es-ES/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: Cambiar la visibilidad de tu sitio de GitHub Pages +intro: 'Puedes administrar el control de acceso para tu sitio de proyecto si lo publicas de forma pública o privada.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: Las personas con permisos administrativos en un repositorio pueden cambiar la visibilidad de un sitio de {% data variables.product.prodname_pages %}. +--- + +### Acerca del control de acceso para los sitios de {% data variables.product.prodname_pages %} + +Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. Con el control de acceso puedes elegir publicar el sitio de forma pública para cualquiera en internet o de forma privada para las personas con acceso de lectura en tu repositorio. Un sitio que se publica de forma privada puede utilizarse para compartir tu documentación o base de conocimientos internos con los miembros de tu empresa. No puedes administrar el control de accesos para el sitio de una organización. Para obtener más información sobre los tipos de sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Acerca de GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". + +Los sitios que se publican de forma privada se encuentran disponibles en un subdominio diferente que el de aquellos sitios que se publican de forma pública. Puedes ver la URL de tu sitio en la configuración del repositorio. Si estás utilizando un generador estático que se configuró para compilar el sitio con el nombre de repositorio como ruta, podrías necesitar actualizar la configuración para el generador de sitio estático cuando cambies el sitio a privado. Para obtener más información, consulta la sección "[Configurar a Jekyll en 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)" o la documentación de tu generador de sitio estático. + +### Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Debajo de "{% data variables.product.prodname_pages %}", selecciona el menú desplegable de **visibilidad de {% data variables.product.prodname_pages %}** y luego da clic en una visibilidad. ![Menú desplegable para elegir la visibilidad para tu sitio](/assets/images/help/pages/public-or-private-visibility.png) +4. Para ver tu sitio publicado, debajo de "{% data variables.product.prodname_pages %}", da clic en la URL del mismo. ![URL de tu sitio publicado de forma privada](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md index 2ebfa9cda0..8debf95d73 100644 --- a/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md +++ b/translations/es-ES/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site.md @@ -11,7 +11,7 @@ redirect_from: - /articles/setting-up-a-custom-domain-with-github-pages/ - /articles/configuring-a-custom-domain-for-your-github-pages-site product: '{% data reusables.gated-features.pages %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 992cbab2a0..cc006b66bf 100644 --- a/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. En el campo para el nombre de archivo, escribe `404.html` o `404.md`. ![Campo File name (Nombre de archivo)](/assets/images/help/pages/404-file-name.png) 4. Si denominaste tu archivo `404.md`, agrega el siguiente texto preliminar de YAML al comienzo del archivo: - ``` + ```yaml --- permalink: /404.html --- @@ -27,6 +27,6 @@ versions: {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -### Further reading +### Leer más - [Texto preliminar](http://jekyllrb.com/docs/frontmatter) en la documentación de Jekyll diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index b6a0a4ae7e..29a0b888d6 100644 --- a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,6 +11,8 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### Prerrequisitos Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product.prodname_pages %}, debes instalar Jekyll y Git. Para obtener más información, consulta [Instalación](https://jekyllrb.com/docs/installation/) en la documentación de Jekyll y "[Configurar Git](/articles/set-up-git)". @@ -95,7 +97,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md`. +Puedes agregar más páginas a tu sitio creando más archivos nuevos. Cada archivo estará disponible en tu sitio en la misma estructura de directorios que tu fuente de publicación. Por ejemplo, si la fuente de publicación para tu sitio de proyecto es la rama `gh-pages`, y creas un archivo nuevo que se llama `/about/contact-us.md` en la rama `gh-pages`, el archivo estará disponible en {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. También puedes agregar un tema para personalizar la apariencia de tu sitio. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el seleccionador de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} utilizando Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}". Para personalizar aún más tu sitio, puedes usar Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %}. 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)". -### Further reading +### Leer más - "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" - "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" diff --git a/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md index cfa0f90ba3..85f071db13 100644 --- a/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md +++ b/translations/es-ES/content/github/working-with-github-pages/getting-started-with-github-pages.md @@ -6,7 +6,7 @@ redirect_from: - /articles/additional-customizations-for-github-pages/ - /articles/getting-started-with-github-pages product: '{% data reusables.gated-features.pages %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/working-with-github-pages/index.md b/translations/es-ES/content/github/working-with-github-pages/index.md index e64dac4e1d..79863647a0 100644 --- a/translations/es-ES/content/github/working-with-github-pages/index.md +++ b/translations/es-ES/content/github/working-with-github-pages/index.md @@ -1,6 +1,6 @@ --- title: Trabajar con Páginas de GitHub -shortTitle: GitHub Pages +shortTitle: Páginas de GitHub intro: 'Puedes crear un sitio web directamente desde un repositorio de {% data variables.product.product_name %}.' redirect_from: - /categories/20/articles/ @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md index f6f7206dd8..e6eab94904 100644 --- a/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md +++ b/translations/es-ES/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md @@ -87,6 +87,6 @@ Para configurar un dominio apex, como `example.com`, debes configurar un archivo {% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %} -### Further reading +### Leer más - "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md index 8e3bbe1d09..da023e8543 100644 --- a/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -27,7 +27,7 @@ Puedes usar Flavored Markdown de {% data variables.product.prodname_dotcom %} co {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -### Further reading +### Leer más - [Documentación de kramdown](https://kramdown.gettalong.org/documentation.html) - [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) diff --git a/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md index 6c707304a3..9b9adb80ac 100644 --- a/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll.md @@ -6,7 +6,7 @@ redirect_from: - /articles/using-jekyll-as-a-static-site-generator-with-github-pages - /articles/setting-up-a-github-pages-site-with-jekyll product: '{% data reusables.gated-features.pages %}' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md index 7362c9c95b..78d693eef3 100644 --- a/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll.md @@ -53,6 +53,6 @@ Jekyll es un proyecto de código abierto activo que se actualiza de manera frecu - Si instalaste Bundler, ejecuta `bundle update github-pages`. - Si no tienes instalado Bundler, ejecuta `gem update github-pages`. -### Further reading +### Leer más - [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) en la documentación de Jekyll diff --git a/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 2d34e77141..636e76b5da 100644 --- a/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/es-ES/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -78,7 +78,7 @@ Este error significa que tu código hace referencia a un archivo simbólico que Este error significa que usaste caracteres no latinos, como `日本語`, sin decirle a la computadora que esperara estos símbolos. Para solucionar el problema, fuerza la codificación en UTF-8 agregando la siguiente línea a tu archivo *_config.yml*: -``` +```yaml codificación: UTF-8 ``` diff --git a/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index d263d3d344..b96be4ad16 100644 --- a/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/es-ES/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: Anular la publicación de un sitio de Páginas de GitHub -intro: 'Puedes dejar de publicar tu sitio de {% data variables.product.prodname_pages %} para que éste ya no esté disponible para el {% if currentVersion == "free-pro-team@latest" %}público{% else %}todos si utilizas {% data variables.product.product_location %}{% endif %}.' +intro: 'Puedes publicar tu sitio de {% data variables.product.prodname_pages %} para que éste deje de estar disponible.' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md b/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md index 194b034dde..bd378cc4a7 100644 --- a/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md +++ b/translations/es-ES/content/github/working-with-github-pages/using-submodules-with-github-pages.md @@ -15,7 +15,7 @@ Solo puedes usar submódulos que apunten a los repositorios públicos, porque el Utiliza la URL de solo lectura `https://` para tus submódulos, incluidos los submódulos anidados. Puedes hacer este cambio en tu archivo _.gitmodules_. -### Further reading +### Leer más - "[Heramientas Git - Submódulos](https://git-scm.com/book/en/Git-Tools-Submodules)" del libro _Pro Git_ - "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md index aeecc73d6c..2574e17877 100644 --- a/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md +++ b/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md @@ -64,6 +64,6 @@ Si usas un complemento personalizado o no compatible, módulo o código personal {% data reusables.support.accessing-premium-content %} -### Further reading +### Leer más - "[Enviar un ticket](/articles/submitting-a-ticket)" 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 d8333d387a..1db335d889 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 @@ -23,9 +23,9 @@ Para ver si actualmente hay algún incidente que afecte los servicios en {% data ### Contactar a {% data variables.contact.github_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 %}. +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 %}. -To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. +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 %}. ### Otorgar a {% data variables.contact.github_support %} acceso temporal a un repositorio privado diff --git a/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md b/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md index a6210ccb97..d0941cecf3 100644 --- a/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md +++ b/translations/es-ES/content/github/working-with-github-support/github-marketplace-support.md @@ -17,7 +17,7 @@ Todas las apps de {% data variables.product.prodname_marketplace %} incluyen un 3. En la barra lateral izquierda, dentro de "Developer tools" (Herramientas del programador), haz clic en **Support** (Asistencia). 4. En la página de asistencia de la app, sigue las instrucciones de la página de la app para contactarte con el equipo de asistencia de la app. -### Further reading +### Leer más - "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)" - "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" 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 7d7149ba5d..77cfc46cc4 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 @@ -31,7 +31,7 @@ Si utilizas {% data variables.product.prodname_ghe_server %}, {% data variables. {% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} {% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} -### Further reading +### 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)." diff --git a/translations/es-ES/content/github/writing-on-github/about-saved-replies.md b/translations/es-ES/content/github/writing-on-github/about-saved-replies.md index cce9b27807..62ff8e54d8 100644 --- a/translations/es-ES/content/github/writing-on-github/about-saved-replies.md +++ b/translations/es-ES/content/github/writing-on-github/about-saved-replies.md @@ -19,7 +19,7 @@ Puedes crear un máximo de 100 respuestas guardadas. Si has alcanzado el límite También puedes usar la respuesta guardada "Duplicar propuesta" proporcionada por {% data variables.product.product_name %} para marcar una propuesta como un duplicado y hacerle un seguimiento con una propuesta similar. -### Further reading +### Leer más - "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" - "[Usar respuestas guardadas](/articles/using-saved-replies)" diff --git a/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md b/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md index 5b016da2b5..375c8c862c 100644 --- a/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md +++ b/translations/es-ES/content/github/writing-on-github/about-writing-and-formatting-on-github.md @@ -21,7 +21,7 @@ Cada campo de comentario en {% data variables.product.product_name %} contiene u ![Barra de herramientas de Markdown](/assets/images/help/writing/markdown-toolbar.gif) -### Further reading +### Leer más - [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) - [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md index eb39a46d74..45e2343eb4 100644 --- a/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md +++ b/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md @@ -52,6 +52,6 @@ Las referencias a un hash SHA de confirmación se convertirán automáticamente {% data reusables.repositories.autolink-references %} -### Further reading +### Leer más - [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 944511f8d9..df3d23dbca 100644 --- a/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -13,7 +13,7 @@ versions: 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. -``` +```markdown # El encabezado más largo ## El segundo encabezado más largo ###### El encabezado más pequeño @@ -37,7 +37,7 @@ Puedes indicar énfasis con texto en negrita, cursiva o tachado. Puedes citar texto con un `>`. -``` +```markdown Tal como dice Abraham Lincoln: > Con perdón de la expresión @@ -55,7 +55,7 @@ Tal como dice Abraham Lincoln: Puedes indicar un código o un comando dentro de un enunciado con comillas simples. El texto dentro de las comillas simples no será formateado. -``` +```markdown Usa `git status` para enumerar todos los archivos nuevos o modificados que aún no han sido confirmados. ``` @@ -102,7 +102,7 @@ Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes Puedes realizar una lista desordenada al anteceder una o más líneas de texto con `-` o `*`. -``` +```markdown - George Washington - John Adams - Thomas Jefferson @@ -112,7 +112,7 @@ Puedes realizar una lista desordenada al anteceder una o más líneas de texto c Para ordenar tu lista, antecede cada línea con un número. -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams @@ -126,7 +126,7 @@ Puedes crear una lista anidada al dejar sangría en uno o más elementos de la l 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. -``` +```markdown 1. Primer elemento de la lista - Primer elemento de la lista anidado - Segundo elemento de la lista anidado @@ -140,7 +140,7 @@ Para crear una lista anidada en el editor de comentarios en {% data variables.pr 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`. -``` +```markdown 100. Primer elemento de la lista - Primer elemento de la lista anidada ``` @@ -149,7 +149,7 @@ En este ejemplo, puedes agregar un elemento de la lista anidada debajo del eleme Puedes crear múltiples niveles de listas anidadas mediante el mismo método. Por ejemplo, dado que el primer elemento de la lista tiene siete espacios (`␣␣␣␣␣-␣`) antes del contenido de la lista anidada `Primer elemento de la lista anidada`, deberías colocar sangría en el primer elemento de la lista anidada por siete espacios. -``` +```markdown 100. Primer elemento de la lista - Primer elemento de la lista anidada - Segundo elemento de la lista anidada @@ -215,7 +215,7 @@ Puedes agregar emojis a tu escritura al escribir `:EMOJICODE:`. 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. -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). +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). ### Párrafos @@ -231,7 +231,7 @@ Puedes pedirle a {% data variables.product.product_name %} que ignore (o evada) Para obtener más información, consulta "[Sintaxis de Markdown" de Daring Fireball](https://daringfireball.net/projects/markdown/syntax#backslash), -### Further reading +### Leer más - [{% 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)" diff --git a/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md index f58824426b..6757641855 100644 --- a/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md +++ b/translations/es-ES/content/github/writing-on-github/creating-a-saved-reply.md @@ -16,7 +16,7 @@ versions: 5. Para revisar tu respuesta, haz clic en **Vista previa**. ![Agregar una respuesta guardada](/assets/images/help/settings/saved-replies-preview.png) 6. Haz clic en **Agregar respuesta guardada**. ![Agregar una respuesta guardada](/assets/images/help/settings/saved-replies-add-button.png) -### Further reading +### Leer más - "[Usar respuestas guardadas](/articles/using-saved-replies)" - "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" diff --git a/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md index ffc04fcce7..c55711b7de 100644 --- a/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md +++ b/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md @@ -46,7 +46,7 @@ Por ejemplo, para resaltar la sintaxis del código Ruby: Usamos [Lingüista](https://github.com/github/linguist) para realizar la detección del idioma y seleccionar [gramáticas independientes](https://github.com/github/linguist/blob/master/vendor/README.md) para el resaltado de la sintaxis. Puedes conocer las palabra clave válidas en [el archivo YAML de idiomas](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). -### Further reading +### Leer más - [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) - [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/creating-gists.md b/translations/es-ES/content/github/writing-on-github/creating-gists.md index 54a31d4894..5732551eae 100644 --- a/translations/es-ES/content/github/writing-on-github/creating-gists.md +++ b/translations/es-ES/content/github/writing-on-github/creating-gists.md @@ -1,6 +1,6 @@ --- title: Crear gists -intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' +intro: 'Puedes crear dos tipos de gists: {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} y secretos. Crea un gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} si estás listo para compartir tus ideas con {% if currentVersion == "github-ae@latest" %}los miembros de la emrpesa{% else %}el mundo{% endif %} o, de lo contrario, un gist secreto.' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -14,11 +14,11 @@ versions: ### Acerca de los gists -Todo gist es un repositorio Git, lo que significa que se puede bifurcar y clonar. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}. +Todo gist es un repositorio Git, lo que significa que se puede bifurcar y clonar. {% if currentVersion != "github-ae@latest" %}Si iniciaste sesión en {% data variables.product.product_name %} cuando{% else %}Cuando{% endif %} creas un gist, este se asociará con tu cuenta y lo verás en tu lista de gists cuando navegues a tu {% data variables.gists.gist_homepage %}. -Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. También se los puede buscar, para que puedas usarlos si deseas que otras personas encuentren tu trabajo y lo vean. +Los gists pueden ser {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} o secretos. Los gists {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} se muestran en {% data variables.gists.discover_url %}, en donde {% if currentVersion == "github-ae@latest" %}los miembros empresariales{% else %}las personas{% endif %} pueden buscar gists nuevos conforme estos se creen. También se los puede buscar, para que puedas usarlos si deseas que otras personas encuentren tu trabajo y lo vean. -Los gists secretos no se muestran en {% data variables.gists.discover_url %} y no se pueden buscar. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. Si deseas mantener tu código a salvo de las miradas curiosas, puedes optar por [crear un repositorio privado](/articles/creating-a-new-repository) en lugar de un gist. +Los gists secretos no se muestran en {% data variables.gists.discover_url %} y no se pueden buscar. Los gists no son privados. Si envías la URL de un gist secreto a {% if currentVersion == "github-ae@latest" %}otro miembro de la empresa{% else %}un amigo {% endif %}, podrán verlo. Sin embargo, si {% if currentVersion == "github-ae@latest" %}cualquier otro miembro de la empresa{% else %}alguien que no conozcas{% endif %} descubre la URL, también podrán ver tu gist. Si deseas mantener tu código a salvo de las miradas curiosas, puedes optar por [crear un repositorio privado](/articles/creating-a-new-repository) en lugar de un gist. {% data reusables.gist.cannot-convert-public-gists-to-secret %} @@ -41,7 +41,7 @@ Puedes fijar los gists a tu perfil para que otras personas los puedan ver fácil {% endif %} -You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. Esto te llevará a una página en la que aparecen todos los gists clasificados y presentados por fecha de creación o actualización. También puedes buscar los gists por idioma con {% data variables.gists.gist_search_url %}. La búsqueda de gists usa la misma sintaxis de búsqueda que la [búsqueda de código](/articles/searching-code). +Puedes descubrir gists {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} que hayan creado otras personas si vas a la {% data variables.gists.gist_homepage %} y das clic en **Todos los gists**. Esto te llevará a una página en la que aparecen todos los gists clasificados y presentados por fecha de creación o actualización. También puedes buscar los gists por idioma con {% data variables.gists.gist_search_url %}. La búsqueda de gists usa la misma sintaxis de búsqueda que la [búsqueda de código](/articles/searching-code). Dado que los gists son repositorios Git, puedes ver su historial de confirmaciones completo, que incluye todas las diferencias que existan. También puedes bifurcar o clonar gists. Para obtener más información, consulta "[Bifurcar y clonar gists"](/articles/forking-and-cloning-gists). @@ -71,6 +71,6 @@ También puedes crear un gist si utilizas el {% data variables.product.prodname_ 4. Escribe el texto de tu gist en el cuadro de texto para el gist. ![Cuadro de texto para el gist](/assets/images/help/gist/gist_text_box.png) -5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} +5. Opcionalmente, para crear un gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}, da clic en {% octicon "triangle-down" aria-label="The downwards triangle icon" %} y luego en **Crear gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}**. ![Menú desplegable para seleccionar la visibilidad de un gist]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %} -6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png) +6. Da clic en **Crear Gist Secreto** o en **Crear gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}**. ![Botón para crear gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md index e45bf48764..ced157c5e3 100644 --- a/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md +++ b/translations/es-ES/content/github/writing-on-github/editing-a-saved-reply.md @@ -17,7 +17,7 @@ versions: 4. En "Editar una respuesta guardada", puedes editar el título y el contenido de la respuesta guardada. ![Editar título y contenido](/assets/images/help/settings/saved-replies-edit-existing-content.png) 5. Haz clic en **Actualizar una respuesta guardada**. ![Actualizar una respuesta guardada](/assets/images/help/settings/saved-replies-save-edit.png) -### Further reading +### Leer más - "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" - "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md index 89a6332bdb..63d06647bc 100644 --- a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md +++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists.md @@ -1,7 +1,7 @@ --- title: Editar y compartir contenido con gists intro: '' -mapTopic: verdadero +mapTopic: true redirect_from: - /categories/23/articles/ - /categories/gists/ diff --git a/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md index b901cecd21..dbf8b69c8a 100644 --- a/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/es-ES/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Bifurcar gists -Each gist indicates which forks have activity, making it easy to find interesting changes from others. +Cada gist indica qué bifurcaciones tiene actividad, haciéndo más fácil el encontrar cambios interesantes de otras personas. ![Bifurcaciones del gist](/assets/images/help/gist/gist_forks.png) diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md index 7fbb9e2f3a..b29eb5eee4 100644 --- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md +++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github.md @@ -5,7 +5,7 @@ redirect_from: - /articles/things-you-can-do-in-a-text-area-on-github/ - /articles/getting-started-with-writing-and-formatting-on-github intro: 'Puedes usar características simples para darles formato a tus comentarios e interactuar con otros en propuestas, solicitudes de extracción y wikis en GitHub.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md b/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md index 2f24e8bcd8..ad370bda12 100644 --- a/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/es-ES/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: Puede crear tablas con barras verticales `|` y guiones `-`. Los guiones se usan para crear el encabezado de cada columna, mientras que las barras verticales separan cada columna. Debes incluir una línea en blanco antes de tu tabla para que se representen correctamente. -``` +```markdown | Primer encabezado | Segundo encabezado | | ------------- | ------------- | @@ -27,7 +27,7 @@ Las barras verticales en cada lado de la tabla son opcionales. Las celdas pueden variar en el ancho y no es necesario que estén perfectamente alineadas dentro de las columnas. Debe haber al menos tres guiones en cada columna de la línea de encabezamiento. -``` +```markdown | Comando | Descripción | | --- | --- | | git status | Enumera todos los archivos nuevos o modificados | @@ -40,7 +40,7 @@ Las celdas pueden variar en el ancho y no es necesario que estén perfectamente Puedes utilizar [formato](/articles/basic-writing-and-formatting-syntax) como enlaces, bloques de códigos insertados y el estilo de texto dentro de tu tabla: -``` +```markdown | Comando | Descripción | | --- | --- | | `git status` | Enumera todos los archivos *nuevos o modificados* | @@ -51,7 +51,7 @@ Puedes utilizar [formato](/articles/basic-writing-and-formatting-syntax) como en Puedes alinear el texto a la izquierda, la derecha o en el centro de una columna al incluir dos puntos `:` a la izquierda, la derecha, o en ambos lados de los guiones dentro de la línea de encabezamiento. -``` +```markdown | Alineado a la izquierda | Alineado en el centro | Alineado a la derecha | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ Puedes alinear el texto a la izquierda, la derecha o en el centro de una columna Para incluir una barra vertical `|` como contenido dentro de tu celda, utiliza una `\` antes de la barra: -``` +```markdown | Nombre | Símbolo | | --- | --- | | Comilla simple | ` | @@ -71,7 +71,7 @@ Para incluir una barra vertical `|` como contenido dentro de tu celda, utiliza u ![Tabla presentada con una barra vertical liberada](/assets/images/help/writing/table-escaped-character-rendered.png) -### Further reading +### Leer más - [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) - [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-ES/content/github/writing-on-github/using-saved-replies.md b/translations/es-ES/content/github/writing-on-github/using-saved-replies.md index 3b0b823c48..d1d0f4e829 100644 --- a/translations/es-ES/content/github/writing-on-github/using-saved-replies.md +++ b/translations/es-ES/content/github/writing-on-github/using-saved-replies.md @@ -23,7 +23,7 @@ versions: {% endtip %} -### Further reading +### Leer más - "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" - "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md index 34a24c3e57..6ce3ec040c 100644 --- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md +++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting.md @@ -1,7 +1,7 @@ --- 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.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/working-with-advanced-formatting versions: diff --git a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md index c211c9df3e..b83cce9e9d 100644 --- a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md +++ b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies.md @@ -1,7 +1,7 @@ --- title: Trabajar con respuestas guardadas intro: 'Para ahorrar tiempo y asegurarte de enviar un mensaje consistente, puedes agregar respuestas guardadas a las propuestas y los comentarios de la solicitud de extracción.' -mapTopic: verdadero +mapTopic: true redirect_from: - /articles/working-with-saved-replies versions: diff --git a/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md b/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md index d6ae97f9fa..0303754b8c 100644 --- a/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/es-ES/content/graphql/guides/forming-calls-with-graphql.md @@ -402,7 +402,7 @@ Para obtener más información acerca de la diferencia entre enumeradores y cade {% endnote %} -### Further reading +### Leer más Puedes hacer mucho _más_ cuando conformes llamados de GraphQL. Aquí hay algunos lugares que te pueden interesar posteriormente: diff --git a/translations/es-ES/content/graphql/guides/introduction-to-graphql.md b/translations/es-ES/content/graphql/guides/introduction-to-graphql.md index c730421fef..b4eee06e7b 100644 --- a/translations/es-ES/content/graphql/guides/introduction-to-graphql.md +++ b/translations/es-ES/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ GraphQL es [introspectivo](https://graphql.github.io/learn/introspection/). Esto * Consulta `__schema` para listar todos los tipos definidos en el modelo y obtener detalles de cada uno: ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* Consulta `__type` para obtener detalles de cualquier tipo: + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* Consulta `__type` para obtener detalles de cualquier tipo: - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * También puedes ejecutar una _consulta de introspección_ del modelo a través de la solicitud `GET`: diff --git a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md index 88f494c030..57b47857e9 100644 --- a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md @@ -51,7 +51,7 @@ Para encontrar algunas consultas de ejemplo, visita la sección "[Una consulta d 2. Porporciona permisos de control total a tu token de acceso personal para las áreas de GHES a las que quisieras acceder. Para tener permiso total a los repositorios privados, organizaciones, equipos, datos de usuario y acceso a la facturación empresarial y datos de perfil, te recomendamos que selecciones estos alcances para tu token de acceso personal: - `repo` - `admin:org` - - `user` + - `usuario` - `admin:enterprise` Los alcances específicos para la cuenta empresarial son: diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md index b28d0946b3..6be7acbfd6 100644 --- a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md +++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md @@ -33,7 +33,7 @@ Puedes filtrar los datos incluidos en las métricas o los informes clave por equ {% data reusables.github-insights.filter-reports %} {% data reusables.github-insights.view-events %} -### Further reading +### Leer más - "[Administrar colaboradores y equipos](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)" - "[Administrar repositorios](/insights/installing-and-configuring-github-insights/managing-repositories)" diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md index 2520272e32..6df74a5be7 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md @@ -17,6 +17,6 @@ Puedes elegir qué colaboradores se incluirán en las métricas y crear equipos {% data reusables.github-insights.events %} Para obtener más información, consulta "[Administrar eventos](/insights/installing-and-configuring-github-insights/managing-events)". -### Further reading +### Leer más - "[Métricas disponibles con {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)" - "{% data variables.product.prodname_insights %} y protección de datos para tu organización" \ No newline at end of file diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md index 6f2f43f62b..df24ba153e 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md @@ -22,7 +22,7 @@ Las personas con permisos de administrador para {% data variables.product.prodna Puedes recibir soporte para {% data variables.product.prodname_insights %} de {% data variables.contact.github_support %}. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Emitir un ticket](/github/working-with-github-support/submitting-a-ticket)".{% else %}"[Contactar a {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/reaching-github-support)".{% endif %} -### Further reading +### Leer más - "[Instalar {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/installing-github-insights)" - "[Configurar {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/configuring-github-insights)" diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md index a473d34dc3..a197db333d 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-github-insights.md @@ -2,7 +2,7 @@ title: Configurar información de GitHub shortTitle: Configuración intro: 'Puedes administrar la conexión entre {% data variables.product.prodname_insights %} Y {% data variables.product.prodname_enterprise %}, y administrar permisos para los usuarios de {% data variables.product.prodname_insights %}.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 3a1fd3aa85..c8605e1674 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -14,7 +14,7 @@ Una vez que habilitas el enlace, cada usuario puede navegar directamente desde { 1. Conéctate al shell administrativo de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." 2. Ejecuta el siguiente comando. - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. Regresa a diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md index 1b60b5dc95..e0dde80446 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-and-updating-github-insights.md @@ -2,7 +2,7 @@ title: Instalar y actualizar la información de GitHub shortTitle: Instalar y actualizar intro: 'Puedes instalar a aplicación de {% data variables.product.prodname_insights %} y actualizarla a la última versión.' -mapTopic: verdadero +mapTopic: true versions: enterprise-server: '*' --- diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index fb96c9f9d6..8b6beda354 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - Debes instalar dependencias en el servidor de aplicaciones. - [Docker](https://docs.docker.com/install/) 1.13.0 + - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/), disponible por apt para [Debian](https://packages.debian.org/search?keywords=netcat) y [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} @@ -96,7 +97,7 @@ Para configurar {% data variables.product.prodname_insights %} para conectarse a 12. Haz clic en **Log in with (inicia sesión con) {% data variables.product.prodname_dotcom %}**. 13. Para autorizar el {% data variables.product.prodname_github_app %} y acceder a {% data variables.product.prodname_insights %}, haz clic en **Authorize (autorizar) {% data variables.product.prodname_github_app %}**. -### Further reading +### Leer más - "[Administrar repositorios](/insights/installing-and-configuring-github-insights/managing-repositories)" - "{% data variables.product.prodname_insights %} y protección de datos para tu organización" diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md index f512c60d89..8e98d085ff 100644 --- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md +++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-data-in-github-insights.md @@ -2,7 +2,7 @@ title: Administrar datos en GitHub Insights shortTitle: Administrar datos intro: 'Puedes elegir qué métricas se muestran en {% data variables.product.prodname_insights %} y qué organizaciones, repositorios y personas están incluidas en esas métricas. Puedes configurar objetivos y agregar contexto a las métricas.' -mapTopic: verdadero +mapTopic: true redirect_from: - /github/installing-and-configuring-github-insights/managing-data-in-github-insights versions: diff --git a/translations/es-ES/content/packages/guides/about-github-container-registry.md b/translations/es-ES/content/packages/guides/about-github-container-registry.md index 8cb24fb210..7a6984309c 100644 --- a/translations/es-ES/content/packages/guides/about-github-container-registry.md +++ b/translations/es-ES/content/packages/guides/about-github-container-registry.md @@ -1,8 +1,8 @@ --- -title: Acerca del Registro Contenedor de GitHub -intro: 'Puedes utilizar el {% data variables.product.prodname_github_container_registry %} para hospedar y mantener contínuamente las imágenes de contenedor de Docker en tu cuenta de organización o de usuario personal de {% data variables.product.prodname_dotcom %}. El {% data variables.product.prodname_github_container_registry %} te permite configurar quién puede administrar y acceder a los paquetes utilizandopermisos específicos.' +title: About GitHub Container Registry +intro: 'You can use {% data variables.product.prodname_github_container_registry %} to seamlessly host and manage Docker container images in your organization or personal user account on {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_github_container_registry %} allows you to configure who can manage and access packages using fine-grained permissions.' product: '{% data reusables.gated-features.packages %}' -redirect_from: +redirect_from: - /packages/getting-started-with-github-container-registry/about-github-container-registry - /packages/managing-container-images-with-github-container-registry versions: @@ -11,84 +11,85 @@ versions: {% note %} -**Nota:** El {% data variables.product.prodname_github_container_registry %} se encuentra actualmente en su fase de beta público y está sujeto a cambios. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. Para utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitar la característica para tu cuenta. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/guides/enabling-improved-container-support)". +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} -### Acerca de {% data variables.product.prodname_github_container_registry %} +### About {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.container-registry-feature-highlights %} -Para compartir el contexto sobre el uso de tu paquete, puedes vincular un repositorio a tu imagen de contenedor en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Conectar un repositorio a una imagen de contenedor](/packages/guides/connecting-a-repository-to-a-container-image)". +To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/guides/connecting-a-repository-to-a-container-image)." -El {% data variables.product.prodname_github_container_registry %} tiene ubicaciones de hospedaje, permisos y visibilidades diferentes a las de otros registros de paquete. +{% data variables.product.prodname_github_container_registry %} has different hosting locations, permission, and visibility than other package registries. -| | Registros de los paquetes | {% data variables.product.prodname_github_container_registry %} -| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Ubicaciones de hospedaje | Puedes hospedar paquetes múltiples en un repositorio. | Puedes hospedar imagenes de contenedor múltiples en una cuenta de organización o de usuario. | -| Permisos | {{ site.data.reusables.package_registry.public-or-private-packages }} Puedes utilizar los roles y equipos de {{ site.data.variables.product.prodname_dotcom }} para limitar quién puede instalar o publicar cada paquete, ya que los paquetes heredan los permisos del repositorio. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | Para cada imagen de contenedor, puedes elegir el nivel de acceso que tienen los demás. Los permisos para acceso a la imagen de contenedor son independientes de aquellos para tu organización y repositorio. | - Visibilidad | {% data reusables.package_registry.public-or-private-packages %} | Puedes configurar la visibilidad de cada una de tus imagenes de contenedor. Solo las personas y equipos a las cuales se les haya otorgado acceso dentro de tu organización podrán ver las imágenes de contenedor privadas. Cualquiera puede ver las imágenes de contenedor públicas. | Acceso anónimo | N/A | Puedes acceder anónimamente a las imágenes de contenedor públicas. +| | Package registries | {% data variables.product.prodname_github_container_registry %} | +|----|----|----| +| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. | +| Permissions | Each package inherits the permissions of the repository where the package is hosted.

    For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. +Visibility | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | +Anonymous access | N/A | You can access public container images anonymously. -Para obtener más información, consulta la sección "[Acerca de los alcances y permisos para {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)". +For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." -### Formatos compatibles +### Supported formats -El {% data variables.product.prodname_container_registry %} es actualmente compatible con los siguientes formatos de contenedores de imagen: +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: -* [Docker Image Manifest V2, Modelo 2](https://docs.docker.com/registry/spec/manifest-v2-2/) -* [Especificaciones de Open Container Initiavie (OCI)](https://github.com/opencontainers/image-spec) +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) -El {% data variables.product.prodname_github_container_registry %} hospeda los contenedores en `ghcr.io/OWNER/IMAGE-NAME`. +The {% data variables.product.prodname_github_container_registry %} hosts containers at `ghcr.io/OWNER/IMAGE-NAME`. -| Cliente del paquete | Lenguaje | Formato del paquete | Descripción | -| ------------------- | -------- | ------------------- | ----------------------- | -| docker | N/A | `Dockerfile` | Gestor de paquetes Node | +| Package client | Language | Package format | Description | +| --- | --- | --- | --- | +| Docker CLI | N/A | `Dockerfile` | Docker container support. | -#### Índices de Listas/Imágenes de Manifiesto +#### Manifest Lists/Image Indexes -El {% data variables.product.prodname_github_container_registry %} también es compatible con los formatos de la [Lista de Manifiestos de Docker](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/el [Índice de Imágenes de OCI](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) que se definen en las especificaciones de Docker V2, Modelo 2, y de la Imágen de OCI. +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. -### Permisos de visibilidad y acceso para las imágenes de contenedor +### Visibility and access permissions for container images -Si tienes permisos administratibos en una imagen de contenedor, puedes configurar la imagen de la misma como privada o pública. Las imágenes públicas permiten el acceso anónimo y pueden extraerse sin autenticación o ingresar a ellas através del CLI. +If you have admin permissions to a container image, you can set the container image to private or public. Public images allow anonymous access and can be pulled without authentication or signing in via the CLI. -Como administrador, también puedes otorgar permisos de acceso para una imagen de contenedor que esté separada de los permisos que configuraste a nivel de organización y de repositorio. +As an admin, you can also grant access permissions for a container image that are separate from the permissions you've set at the organization and repository levels. -Puedes otorgar un rol de acceso a cualquier persona en el caso de las imagenes de contenedor que pertenecen a, o que publica una cuenta de usuario. Puedes otorgar un rol de acceso a cualquier persona o equipo en la organización para las imágenes de contenedor que pertenecen a, o que publica una cuenta de usuario. +For container images published and owned by a user account, you can give any person an access role. For container images published and owned by an organization, you can give any person or team in the organization an access role. -| Rol de permisos | Descripción del acceso | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Read | Puede descargar el paquete.
    Puede leer los metadatos del paquete. | -| Escritura | Puede cargar y descargar este paquete.
    Puede leer y escribir metadatos del paquete. | -| Admin | Puede cargar, descargar, borrar y administrar este paquete.
    Puede leer y escribir metadatos del paquete.
    Puede otorgar permisos del paquete. | +| Permission role | Access description | +|-----|----| +| Read | Can download package.
    Can read package metadata. | +| Write | Can upload and download this package.
    Can read and write package metadata. | +| Admin | Can upload, download, delete, and manage this package.
    Can read and write package metadata.
    Can grant package permissions. -Para obtener más información, consulta la sección "[Configurar el control de accesos y la visibilidad para las imagenes de contenedor](/packages/guides/configuring-access-control-and-visibility-for-container-images)". +For more information, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." -### Sobre tokens +### About scopes and permissions for {% data variables.product.prodname_github_container_registry %} -Para instalar o publicar un paquete, debes usar un token con el ámbito adecuado, y tu cuenta de usuario debe tener los permisos pertinentes para ese repositorio. +To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. -| Ámbito | Descripción | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `read:packages` | Descarga e instala las imágenes de contenedor desde {% data variables.product.prodname_github_container_registry %} -| `write:packages` | Carga y publica las imágenes de contenedor a {% data variables.product.prodname_github_container_registry %} -| `delete:packages` | Borra versiones específicas de imágenes de contenedor privadas o públicas del {% data variables.product.prodname_github_container_registry %}. Para obtener más información, consulta la sección "[Borrar una imagen de contenedor](/packages/guides/deleting-a-container-image)". | +| Scope | Description | +| --- | --- | +|`read:packages`| Download and install container images from {% data variables.product.prodname_github_container_registry %} | +|`write:packages`| Upload and publish container images to {% data variables.product.prodname_github_container_registry %} | +| `delete:packages` | Delete specified versions of private or public container images from {% data variables.product.prodname_github_container_registry %}. For more information, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." | -Para aprender más sobre los alcances y permisos disponibles para las imágenes de contenedor, consulta la sección "[Configurar el control de accesos y la visibilidad para las imagenes de contenedor](/packages/guides/configuring-access-control-and-visibility-for-container-images)". +To learn about available scopes and permissions for container images, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." -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 "[Alcances disponibles](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)". +For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)" and "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)." -### Acerca de la facturación para {% data variables.product.prodname_github_container_registry %} +### About billing for {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.billing-for-container-registry %} -### Contactar con soporte técnico +### Contacting support -Si tienes retroalimentación o solicitudes de características para el {% data variables.product.prodname_github_container_registry %}, utiliza el [formato de retroalimentación](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). +If you have feedback or feature requests for {% data variables.product.prodname_github_container_registry %}, use the [feedback form](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). -Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_github_container_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si: +Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_github_container_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if: -* Experimentas alguna cosa que contradice la documentación. -* Encuentras errores vagos o poco claros. -* Tu paquete publicado contiene datos sensibles, tales como violaciones del RGPD, Claves de la API, o información de identificación personal. +* You experience anything that contradicts the documentation. +* You encounter vague or unclear errors. +* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally-identifying information. diff --git a/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index 494b574592..611796d76a 100644 --- a/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/es-ES/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ Si deseas interactuar con múltiples repositorios, puedes agregar cada repositor Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). {% endif %} -``` +```xml {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} -These examples assume your instance has subdomain isolation enabled. +Estos ejemplos asumen que tu instancia tiene habilitado el aislamiento de subdominios. {% endif %} @@ -279,6 +279,6 @@ $ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME {% endnote %} -### Further reading +### Leer más - "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index 3aa43b0c58..9224b99c8d 100644 --- a/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/es-ES/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -79,12 +79,12 @@ Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo r ### Publicar un paquete -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. +Puedes publicar un paquete en el {% data variables.product.prodname_registry %} si te autenticas con un archivo de *nuget.config*{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, o si utilizas la opción de línea de comandos `--api-key` con tu token de acceso personal (PAT) de {% data variables.product.prodname_dotcom %}{% endif %}. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### Publishing a package using a GitHub PAT as your API key +#### Publicar un paquete utilizando el PAT de GitHub como tu clave de la API -If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +Si aún no tienes un PAT para utilizar con tu cuenta de {% data variables.product.prodname_dotcom %}, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". 1. Crear un proyecto nuevo. ```shell @@ -95,7 +95,7 @@ If you don't already have a PAT to use for your {% data variables.product.prodna dotnet pack--lanzamiento de configuración ``` -3. Publish the package using your PAT as the API key. +3. Publicar el paquete utilizando tu PAT como la clave de la API. ```shell dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" ``` @@ -104,7 +104,7 @@ If you don't already have a PAT to use for your {% data variables.product.prodna {% endif %} -#### Publishing a package using a *nuget.config* file +#### Publicar un paquete utilizando un archivo *nuget.config* Al publicar, debes usar el mismo valor para `OWNER` en tu archivo *csproj* que usas en tu archivo de autenticación *nuget.config*. Especifica o incrementa el número de versión en tu archivo *.csproj* y luego usa el comando `dotnet pack` para crear un archivo *.nuspec* para esa versión. Para obtener más información sobre cómo crear tu paquete, consulta la sección "[Crear y publicar un paquete](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" en la documentación de Microsoft. @@ -219,6 +219,6 @@ El uso de paquetes desde {% data variables.product.prodname_dotcom %} en tu proy restaurar dotnet ``` -### Further reading +### Leer más - "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md index 07e25e9988..0f5d2c15b1 100644 --- a/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md +++ b/translations/es-ES/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -209,7 +209,7 @@ Puedes instalar un paquete agregando el paquete como una dependencia a tu proyec $ gradle install ``` -### Further reading +### Leer más - "[Configurar Apache Maven para usar con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" - "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md index 9adea8a612..591ff8346d 100644 --- a/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/es-ES/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -17,13 +17,13 @@ versions: **Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### Limits for published npm versions +### Límites para las versiónes de npm publicadas -If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage. +Si estableces más de 1,000 versiones de paquetes de npm en el {% data variables.product.prodname_registry %}, podrías notar que ocurren problemas de rendimiento y de tiempos excedidos durante el uso. -To reduce the number of versions you have published for your npm package, consider deleting package versions. Para obtener más información, consulta "[Eliminar un paquete](/packages/manage-packages/deleting-a-package)". +En el futuro, para mejorar el rendimiento del servicio, no podrás publicar más de 1,000 versiones de un paquete en {% data variables.product.prodname_dotcom %}. Cualquier versión que se publique antes de llegar a este límite aún será legible. -In the future, {% data variables.product.company_short %} will enforce a hard limit on publishing more than 1,000 versions of an npm package. When we start enforcing the 1,000 versions limit for each npm package hosted on {% data variables.product.prodname_registry %}, we will offer more guidance on how to manage your package versions. +Si llegas a este límite, considera borrar las versiones del paquete o contacta a soporte para recibir ayuda. Cuando se aplique este límite, actualizaremos nuestra documentación con una forma de dar soluciones para él. Para obtener más información, consulta la sección "[Borrar un paquete](/packages/manage-packages/deleting-a-package)" o "[Contactar a soporte](/packages/learn-github-packages/about-github-packages#contacting-support)". {% endif %} @@ -166,7 +166,7 @@ También debes agregar el archivo *.npmrc* a tu proyecto por lo que todas las so {% data reusables.package_registry.add-npmrc-to-repo-step %} 4. Configura *package.json* en tu proyecto para usar el paquete que estás instalando. Para agregar las dependencias de tu paquete al archivo *package.json* para {% data variables.product.prodname_registry %}, especifica el nombre del paquete de alcance completo, como `@my-org/server`. Para paquetes de *npmjs.com*, especifica el nombre completo, como `@babel/core` o `@lodash`. Por ejemplo, el archivo *package.json* a continuación utiliza el paquete `@octo-org/octo-app` como una dependencia. - ``` + ```json { "name": "@my-org/server", "version": "1.0.0", @@ -210,11 +210,11 @@ registry=https://HOSTNAME/_registry/npm/OWNER {% endif %} {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} -### Using the official NPM registry +### Utilizar el registro oficial de NPM -{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +El {% data variables.product.prodname_registry %} te permite acceder al registro oficial de NPM en `registry.npmjs.com`, si tu administrador de {% data variables.product.prodname_ghe_server %} habilitó esta característica. Para obtener más información, consulta la sección [Conectarse al registro oficial de NPM](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). {% endif %} -### Further reading +### Leer más - "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md index 5d3d783021..4b2465e06d 100644 --- a/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md +++ b/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -108,7 +108,7 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem Para publicar múltiples gemas en el mismo repositorio, puedes incluir la URL al repositorio {% data variables.product.prodname_dotcom %} en el campo `github_repo` en `gem.metadata`. Si incluyes este campo, {% data variables.product.prodname_dotcom %} empatará el repositorio con base en este valor en vez de utilizar el nombre de la gema.{% if enterpriseServerVersions contains currentVersion %} Reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} -``` +```ruby gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` @@ -119,7 +119,7 @@ Puedes usar gemas desde {% data variables.product.prodname_registry %} al igual {% data reusables.package_registry.authenticate-step %} 2. Para Bundler, agrega tu usuario u organización {% data variables.product.prodname_dotcom %} como fuente en tu *Gemfile* para extraer gemas de esta nueva fuente. Por ejemplo, puedes agregar un bloque nuevo de `source` al *Gemfile* que utiliza el {% data variables.product.prodname_registry %} únicamente para los paquetes que especifiques, reemplzando *GEM NAME* con el paquete que quieres instalar desde el {% data variables.product.prodname_registry %} y *OWNER* con el usuario u organización al que pertenece el repositorio que contienen la gema que quieres instalar.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -131,7 +131,7 @@ Puedes usar gemas desde {% data variables.product.prodname_registry %} al igual 3. Para las versiones de Bundler anteriores a 1.7.0, debes agregar una nueva `fuente` global. Para obtener más información acerca del uso de Bundler, consulta la [documentación bundler.io](http://bundler.io/v1.5/gemfile.html). - ``` + ```ruby source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" @@ -144,6 +144,6 @@ Puedes usar gemas desde {% data variables.product.prodname_registry %} al igual $ gem install octo-gem --version "0.1.1" ``` -### Further reading +### Leer más - "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md b/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md index af43d1e1e7..c0273be969 100644 --- a/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md +++ b/translations/es-ES/content/packages/guides/container-guides-for-github-packages.md @@ -2,7 +2,7 @@ title: Guías de contenedor para GitHub Packages shortTitle: Guías de contenedor para GitHub Packages intro: 'Puedes publicar y recuperar las imágenes de Docker utilizando {% data variables.product.prodname_registry %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/es-ES/content/packages/guides/deleting-a-container-image.md b/translations/es-ES/content/packages/guides/deleting-a-container-image.md index f71cfa7e82..30c71b577c 100644 --- a/translations/es-ES/content/packages/guides/deleting-a-container-image.md +++ b/translations/es-ES/content/packages/guides/deleting-a-container-image.md @@ -1,6 +1,6 @@ --- title: Borrar una imagen de contenedor -intro: 'You can delete a specific version or all versions of a private or public container image on {% data variables.product.prodname_dotcom %}.' +intro: 'Puedes borrar una versión específica o todas las versiones de una imagen de contenedor privada o púb lica en {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image @@ -20,34 +20,34 @@ Cuando borres paquetes públicos, toma en cuenta que podrías dañar proyetos qu ### Borrar una versión de una imagen de contenedor que pertenezca a un usuario en {% data variables.product.prodname_dotcom %} -To only delete specific versions of a container image, you can use these steps. To delete an entire package, see "[Deleting all versions of a user-owned container image on {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-a-user-owned-container-image-on-github)." +Para borrar únicamente versiones específicas de una imagen de contenedor, puedes utilizar estos pasos. Para borrar un paquete entero, consulta la sección "[Borrar todas las versiones de una imagen de contenedor que pertenece a un usuario de {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-a-user-owned-container-image-on-github)". {% data reusables.package_registry.package-settings-from-user-level %} 5. A la izquierda, da clic en **Administrar versiones**. -6. Optionally, to ensure you're seeing all of your package versions, use the "Type" drop down menu and select **All**. ![Package version type drop down menu showing option to list all versions](/assets/images/help/package-registry/make-all-container-versions-visible.png) -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. Opcionalmente, para garantizar que estás viendo todas las versiones de tu paquete, utiliza el menú desplegable de "Tipo" y selecciona **Todos**. ![Menú desplegable del tipo de versión de un paquete que muestra la opción para listar todas las versiones](/assets/images/help/package-registry/make-all-container-versions-visible.png) +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) ### Borrar una versión de una imagen de contenedor que pertenezca a una organización en {% data variables.product.prodname_dotcom %} -To only delete specific versions of a container image that you have admin , you can use these steps. To delete an entire package, see "[Deleting all versions of an organization-owned container image on {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-an-organization-owned-container-image-on-github)." +Para borrar únicamente las versiones específicas de una imagen de contenedor en la que tengas permisos administrativos, puedes utilizar estos pasos. Para borrar un paquete completo, consulta la sección "[Borrar todas las versiones de una imagen de contenedor propiedad de una organización en {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-an-organization-owned-container-image-on-github)". {% data reusables.package_registry.package-settings-from-org-level %} 5. A la izquierda, da clic en **Administrar versiones**. -6. Optionally, to ensure you're seeing all of your package versions, use the "Type" drop down menu and select **All**. ![Package version type drop down menu showing option to list all versions](/assets/images/help/package-registry/make-all-container-versions-visible.png) -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. 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)**. ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) +6. Opcionalmente, para garantizar que estás viendo todas las versiones de tu paquete, utiliza el menú desplegable de "Tipo" y selecciona **Todos**. ![Menú desplegable del tipo de versión de un paquete que muestra la opción para listar todas las versiones](/assets/images/help/package-registry/make-all-container-versions-visible.png) +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) -### Deleting all versions of a user-owned container image on {% data variables.product.prodname_dotcom %} +### Borrar todas las versiones de una imagen de contenedor propiedad de un usuario en {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-user-level %} -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) +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) -### Deleting all versions of an organization-owned container image on {% data variables.product.prodname_dotcom %} +### Borrar todas las versiones de una imagen de contenedor propiedad de una organización en {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-org-level %} -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**. ![Botón para eliminar paquete](/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**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-container-package-deletion.png) +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) diff --git a/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md b/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md index bff856b307..e4f75f1d5c 100644 --- a/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md +++ b/translations/es-ES/content/packages/guides/package-client-guides-for-github-packages.md @@ -2,7 +2,7 @@ title: Las guías de cliente de paquetes para GitHub Packages shortTitle: Las guías de cliente de paquetes para GitHub Packages intro: 'Puedes publicar y recuperar imágenes de cliente de paquetes utilizando {% data variables.product.prodname_registry %}.' -mapTopic: verdadero +mapTopic: true versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md b/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md index a2c07cb78d..8f9a3f5c6d 100644 --- a/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/es-ES/content/packages/guides/using-github-packages-with-github-actions.md @@ -1,6 +1,6 @@ --- -title: Usar GitHub Packages con GitHub Actions -intro: 'Puedes configurar un flujo de trabajo en {% data variables.product.prodname_actions %} para publicar o instalar automáticamente un paquete desde {% data variables.product.prodname_registry %}.' +title: Using GitHub Packages with GitHub Actions +intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions @@ -12,30 +12,30 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -### Acerca de {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %} +### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} -{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." -Puedes ampliar las capacidades de CI y CD de tu repositorio publicando o instalando paquetes como parte de tu flujo de trabajo. +You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. {% if currentVersion == "free-pro-team@latest" %} -#### Autenticarte en {% data variables.product.prodname_github_container_registry %} +#### Authenticating to {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.container-registry-beta %} {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} -Para ver un ejemplo de autenticación, consulta la sección "[Autenticarse con el {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)". +For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)." {% endif %} -#### Autenticarse en los registros de paquetes en {% data variables.product.prodname_dotcom %} +#### Authenticating to package registries on {% data variables.product.prodname_dotcom %} -{% if currentVersion == "free-pro-team@latest" %}Si quieres que tu flujo de trabajo se autentique en {% data variables.product.prodname_registry %} para acceder a un registro de paquetes diferente al {% data variables.product.prodname_container_registry %} en {% data variables.product.product_name %}, entonces{% else %}Para autenticarse en los registros de paquetes de {% data variables.product.product_name %},{% endif %} te recomendamos utilizar el `GITHUB_TOKEN` que {% data variables.product.product_name %} crea automáticamente para tu repositorio cuando habilitas las {% data variables.product.prodname_actions %} en vez de un token de acceso personal para autenticación. El `GITHUB_TOKEN` tiene ámbitos `read:packages` y `write:packages` en el repositorio actual. Para las bifurcaciones, el token también tiene el ámbito `read:packages` para el repositorio padre. +{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. -Puedes hacer referencia al `GITHUB_TOKEN` en tu archivo de flujo de trabajo mediante el contexto {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." -### Publicar un paquete mediante una acción +### Publishing a package using an action You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}. @@ -106,7 +106,9 @@ The following example demonstrates how you can use {% data variables.product.pro ``` {% endraw %} - The relevant settings are explained in the following table:
    actividadradiodifusiónalerta-círculoalerta-octágonoactivityairplayalert-circlealert-octagon
    alerta-triánguloalinear-centroalinear-justificaralinear-izquierdaalert-trianglealign-centeralign-justifyalign-left
    alinear-derechaanclaaperturaarchivoalign-rightanchoraperturearchive
    flecha-abajo-círculoflecha-abajo-izquierdaflecha-abajo-derechaflecha-abajoarrow-down-circlearrow-down-leftarrow-down-rightarrow-down
    flecha-izquierda-círculoflecha-izquierdaflecha-derecha-círculoflecha-derechaarrow-downarrow-leftarrow-leftarrow-right
    flecha-arriba-círculoflecha-arriba-izquierdaflecha-arriba-derechaflecha-arribaarrow-up-circlearrow-up-leftarrow-up-rightarrow-up
    en-cartelpremiobarra-cuadro-2barra-cuadroat-signawardbar-chart-2bar-chart
    batería-cargabateríacampana-apagadocampanabattery-chargingbatterybell-offbell
    bluetoothnegritalibro-abiertolibroboldbook-openbook
    marcadorcajamaletíncalendariobookmarkboxbriefcasecalendar
    cámara-apagadocámaramoldeverificar-círculocamera-offcameracastcheck-circle
    verificar-cuadradoverificarcomilla angular-abajocomilla angular-izquierdacheck-squarecheckchevron-downchevron-left
    comillas angulares-derehcacomilla angular- arribacomillas angulares-abajocomillas angulares-izquierdachevron-rightchevron-upchevrons-downchevrons-left
    comillas angulares-derechacomillas angulares- arribacírculoportapapeleschevrons-rightchevrons-upcircleclipboard
    relojnube-lloviznanube-rayonube-apagadoclockcloud-drizzlecloud-lightningcloud-off
    nube-lluvianube-nievenubecódigocloud-raincloud-snowcloudcode
    comandobrújulacopiarángulo-abajo-izquierdocommandcompasscopycorner-down-left
    ángulo-abajo-derechoángulo-izquierdo-abajoángulo-arriba-izquierdoángulo-derecho-abajocorner-down-rightcorner-left-downcorner-left-upcorner-right-down
    ángulo-derecho-arribaángulo-arriba-izquierdoángulo-arriba-derechacorner-right-upcorner-up-leftcorner-up-right cpu
    tarjeta-de-créditocortarpunto de mirabase de datoscredit-cardcropcrosshairdatabase
    eliminardiscodólar-signodescargar-nubedeletediscdollar-signdownload-cloud
    descargargotaeditar-2editar-3downloaddropletedit-2edit-3
    editarexterno-enlacedesviar la miradaojoeditexternal-linkeye-offeye
    facebookavance-rápidoplumaarchivo-menosfast-forwardfeatherfile-minus
    archivo-másarchivo-textoarchivopelículafile-plusfile-textfilefilm
    filtrobanderacarpeta-menoscarpeta-másfilterflagfolder-minusfolder-plus
    carpetaobsequiogit-ramagit-confirmarfoldergiftgit-branchgit-commit
    git-fusionargit-solicitud-extracciónglobocuadrículagit-mergegit-pull-requestglobegrid
    disco-durohard-drive hashauricularescorazónheadphonesheart
    ayuda-círculohogarimagenbandeja de entradahelp-circlehomeimageinbox
    infocursivacapasdiseñoitaliclayerslayout
    vida-boyaenlace-2enlacelistalife-buoylink-2linklist
    cargadorbloqueariniciar-sesióncerrar-sesiónloaderlocklog-inlog-out
    correoasignar-pinasignarmaximizar-2mailmap-pinmapmaximize-2
    maximizar -menúmensaje-círculomensaje-cuadradomaximizemenumessage-circlemessage-square
    mic-apagadomic-off micminimizar-2minimizarminimize-2minimize
    menos-círculomenos-cuadradomenosminus-circleminus-squareminus monitor
    lunamás-horizontalmás-verticalmovermoonmore-horizontalmore-verticalmove
    músicanavegación-2navegaciónoctágonomusicnavigation-2navigationoctagon
    paquetesujetapapelespausa-círculopausarpackagepaperclippause-circlepause
    porcentajellamada-telefónicateléfono-transferenciateléfono-entrantepercentphone-callphone-forwardedphone-incoming
    teléfono-perdidoteléfono-apagadoteléfono-salidateléfonophone-missedphone-offphone-outgoingphone
    gráfico-circularreproducir-círculoreproducirmás-círculopie-chartplay-circleplayplus-circle
    más-cuadradomásbolsillopotenciaplus-squarepluspocketpower
    impresoraprinter radioactualizar-ccwactualizar-cwrefresh-ccwrefresh-cw
    repetirrebobinarrotar-ccwrotar-cwrepeatrewindrotate-ccwrotate-cw
    rssguardartijerasbuscarsavescissorssearch
    enviarservidorparámetroscompartir-2sendserversettingsshare-2
    compartirescudo-apagarescudobolsa-de-comprasshareshield-offshieldshopping-bag
    carro-de-comprasaleatoriobarra lateralomitir-atrásshopping-cartshufflesidebarskip-back
    omitir-adelantebarradeslizadoresskip-forwardslashsliders smartphone
    parlantecuadradoestrelladetener-círculospeakersquarestarstop-circle
    solamaneceratardecersunsunrisesunset tablet
    etiquetadestinotagtarget terminaltermómetrothermometer
    pulgares-abajopulgares-arribaalternar-izquierdaalternar-derechathumbs-downthumbs-uptoggle-lefttoggle-right
    papelera-2papeleratendencia-abajotendencia-arribatrash-2trashtrending-downtrending-up
    triángulocamiónTVtriangletrucktv type
    paraguassubrayardesbloquearcargar-nubeumbrellaunderlineunlockupload-cloud
    cargarusuario-comprobarusuario-menosusuario-másuploaduser-checkuser-minususer-plus
    usuario-xusuariouser-xuser usersvideo-apagarvideo-off
    videocorreo de vozvolumen-1volumen-2voicemailvolume-1volume-2
    volumen-xvolumenobservarwifi-apagarvolume-xvolumewatchwifi-off
    wifivientox-círculox-cuadradowindx-circlex-square
    xdestruir-apagadodestruiracercarsezap-offzapzoom-in
    alejarsezoom-out - Agrupa todos los pasos que se ejecutan en el job check-bats-version. Cada línea anidada bajo esta sección es una acción por separado. + Agrupa todos los pasos que se ejecutan en el job check-bats-version. Cada elemento anidado bajo esta sección es un comando de shell o acción separada.
    - La palabra clave run le dice al job que ejecute un comando en el ejecutor. Ene ste caso, estás utilizando npm para instalar el paquete de pruebas del software bats. + La palabra clave run le dice al job que ejecute un comando en el ejecutor. Ene ste caso, estás utilizando npm para instalar el paquete de pruebas del software bats.
    - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +```
    - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +```
    - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +```
    - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - name: demo-workflow - on: - push: - jobs: - test: - runs-on: ${{ matrix.os }} - strategy: - fail-fast: false - matrix: - os: [macos-latest, ubuntu-latest] - steps: - - uses: actions/checkout@v1 - - uses: actions/setup-node@v1 - with: - node-version: 12 - - run: npm install -g bats - - run: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %}
    - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +```
    {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %}
    + The relevant settings are explained in the following table: + +
    @@ -158,7 +160,7 @@ YAML 構文を使用してワークフローファイルを作成する方法を ``` @@ -180,7 +182,7 @@ YAML 構文を使用してワークフローファイルを作成する方法を ``` @@ -198,24 +200,24 @@ YAML 構文を使用してワークフローファイルを作成する方法を #### ワークフローファイルの視覚化 -この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 Each step executes a single action or shell command. ステップ 1 と 2 は、ビルド済みのコミュニティアクションを使用します。 Steps 3 and 4 run shell commands directly on the runner. ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。 +この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 各ステップは、単一のアクションまたはシェルコマンドを実行します。 ステップ 1 と 2 は、ビルド済みのコミュニティアクションを使用します。 ステップ 3 と 4 では、ランナーで直接シェルコマンドを実行します。 ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。 ![ワークフローの概要](/assets/images/help/images/overview-actions-event.png) ### ジョブのアクティビティを表示する -Once your job has started running, you can {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}. +ジョブの実行が開始されると、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}実行の進行状況{% endif %}の視覚化グラフが表示され、{% data variables.product.prodname_dotcom %} での各ステップのアクティビティが表示されます。 {% data reusables.repositories.navigate-to-repo %} 1. リポジトリ名の下で**Actions（アクション）**をクリックしてください。 ![リポジトリに移動](/assets/images/help/images/learn-github-actions-repository.png) 1. 左サイドバーで、表示するワークフローをクリックします。 ![ワークフロー結果のスクリーンショット](/assets/images/help/images/learn-github-actions-workflow.png) 1. [Workflow runs] で、表示する実行の名前をクリックします。 ![ワークフロー実行のスクリーンショット](/assets/images/help/images/learn-github-actions-run.png) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -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) +1. [**Jobs**] または視覚化グラフで、表示するジョブをクリックします。 ![ジョブを選択](/assets/images/help/images/overview-actions-result-navigate.png) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -1. View the results of each step. ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated-2.png) +1. 各ステップの結果を表示します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated-2.png) {% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. ジョブ名をクリックして、各ステップの結果を確認します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated.png) {% else %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md index 898837ae91..2fdabc0ddd 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md @@ -1,11 +1,13 @@ --- title: 複雑なワークフローを管理する shortTitle: 複雑なワークフローを管理する -intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} environments,{% endif %} and labels.' +intro: 'このガイドでは、シークレット管理、依存ジョブ、キャッシング、ビルドマトリックス、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}環境、{% endif %}ラベルなど、{% data variables.product.prodname_actions %} の高度な機能を使用する方法を説明します。' versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'ワークフロー' --- {% data reusables.actions.enterprise-beta %} @@ -111,7 +113,7 @@ jobs: ### データベースとサービスコンテナの利用 -ジョブにデータベースまたはキャッシュサービスが必要な場合は、[`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) キーワードを使用して、サービスをホストするための一時コンテナを作成できます。 この例は、ジョブが `services` を使用して `postgres` コンテナを作成し、`node` を使用してサービスに接続する方法を示しています。 +ジョブにデータベースまたはキャッシュサービスが必要な場合は、[`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) キーワードを使用して、サービスをホストするための一時コンテナを作成できます。そして、作成されたコンテナはそのジョブ内のすべてのステップで利用でき、ジョブが完了すると削除されます。 この例は、ジョブが `services` を使用して `postgres` コンテナを作成し、`node` を使用してサービスに接続する方法を示しています。 ```yaml jobs: @@ -137,7 +139,7 @@ jobs: ### ラベルを使用してワークフローを転送する -この機能は、特定のセルフホストランナーにジョブを割り当てるのに役立ちます。 特定のタイプのランナーがジョブを処理することを確認したい場合は、ラベルを使用してジョブの実行場所を制御できます。 セルフホストランナーにラベルを割り当ててから、YAML ワークフローでこれらのラベルを参照して、ジョブが予測可能な方法で転送されるようにすることができます。 +この機能は、特定のセルフホストランナーにジョブを割り当てるのに役立ちます。 特定のタイプのランナーがジョブを処理するようにしたい場合は、ラベルを使用してジョブの実行場所を制御できます。 セルフホストランナーにラベルを割り当ててから、YAML ワークフローでこれらのラベルを参照して、ジョブが予測可能な方法で転送されるようにすることができます。 この例は、ワークフローがラベルを使用して必要なランナーを指定する方法を示しています。 @@ -150,9 +152,9 @@ jobs: 詳しい情報については、「[セルフホストランナーでのラベルの利用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)」を参照してください。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Using environments +### 環境の使用 -You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +保護のルールとシークレットを持つ環境を設定できます。 ワークフロー内の各ジョブは、1つの環境を参照できます。 この環境を参照するとジョブがランナーに送信される前に、環境に設定された保護ルールをパスしなければなりません。 詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 {% endif %} ### ワークフロー テンプレートの使用 diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 5ddafbb92a..4cbff691f8 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Azure Pipelines + - 移行 + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -62,16 +67,16 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: scripts - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in the default shell" - - bash: echo "This step runs in bash" - - pwsh: Write-Host "This step runs in PowerShell Core" - - task: PowerShell@2 - inputs: - script: Write-Host "This step runs in PowerShell" + - job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" ``` {% endraw %} @@ -82,13 +87,13 @@ jobs: scripts: runs-on: windows-latest steps: - - run: echo "This step runs in the default shell" - - run: echo "This step runs in bash" - shell: bash - - run: Write-Host "This step runs in PowerShell Core" - shell: pwsh - - run: Write-Host "This step runs in PowerShell" - shell: powershell + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell ``` {% endraw %} @@ -123,11 +128,11 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_command - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in CMD on Windows by default" + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} @@ -138,9 +143,9 @@ jobs: run_command: runs-on: windows-latest steps: - - run: echo "This step runs in PowerShell on Windows by default" - - run: echo "This step runs in CMD on Windows explicitly" - shell: cmd + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %} @@ -171,12 +176,12 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: conditional - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This step runs with str equals 'ABC' and num equals 123" - condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) + - job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) ``` {% endraw %} @@ -187,8 +192,8 @@ jobs: conditional: runs-on: ubuntu-latest steps: - - run: echo "This step runs with str equals 'ABC' and num equals 123" - if: ${{ env.str == 'ABC' && env.num == 123 }} + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %} @@ -217,29 +222,29 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: initial - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This job will be run first." -- job: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout2." -- job: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout1." -- job: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - steps: - - script: echo "This job will run after fanout1 and fanout2 have finished." + - job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." + - job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." + - job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." + - job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -247,29 +252,25 @@ jobs: {% raw %} ```yaml jobs: -- job: initial - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This job will be run first." - - job: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout2." - - job: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout1." - - job: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - steps: - - script: echo "This job will run after fanout1 and fanout2 have finished." + initial: + runs-on: ubuntu-latest + steps: + - run: echo "This job will be run first." + fanout1: + runs-on: ubuntu-latest + needs: initial + steps: + - run: echo "This job will run after the initial job, in parallel with fanout2." + fanout2: + runs-on: ubuntu-latest + needs: initial + steps: + - run: echo "This job will run after the initial job, in parallel with fanout1." + fanin: + runs-on: ubuntu-latest + needs: [fanout1, fanout2] + steps: + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -298,15 +299,15 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_python - pool: - vmImage: 'ubuntu-latest' - steps: - - task: UsePythonVersion@0 - inputs: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} @@ -317,11 +318,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index b59a5885b3..049883a486 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -1,12 +1,17 @@ --- title: CircleCIからGitHub Actionsへの移行 -intro: 'GitHub ActionsとCircleCIには設定に相似点があるので、GitHub Actionsへの移行は比較的単純明快です。' +intro: GitHub ActionsとCircleCIには設定に相似点があるので、GitHub Actionsへの移行は比較的単純明快です。 redirect_from: - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CircleCI + - 移行 + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -28,7 +33,7 @@ CircleCIと{% data variables.product.prodname_actions %}は、どちらも自動 CircleCIから移行する際には、以下の差異を考慮してください。 - CircleCIの自動テストの並列性は、ユーザが指定したルールもしくは過去のタイミングの情報に基づいて、自動的にテストをグループ化します。 この機能は{% data variables.product.prodname_actions %}には組み込まれていません。 -- コンテナはユーザのマッピングが異なるので、Dockerコンテナ内で実行されるアクションは、権限の問題に敏感です。 これらの問題の多くは、*Dockerfile*中で`USER`命令を使わなければ回避できます。 Dockerのファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %}ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 +- コンテナはユーザのマッピングが異なるので、Dockerコンテナ内で実行されるアクションは、権限の問題に敏感です。 これらの問題の多くは、*Dockerfile*中で`USER`命令を使わなければ回避できます。 {% data variables.product.product_name %}ホストランナー上のDockerのファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %}ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 ### ワークフローとジョブの移行 @@ -38,7 +43,7 @@ CircleCIと{% data variables.product.prodname_actions %}は、どちらも似た ### orbsからアクションへの移行 -CircleCIと{% data variables.product.prodname_actions %}は、どちらもワークフロー中のタスクを再利用し、共有するための仕組みを提供しています。 CircleCIはorbsという概念を利用します。これはYAMLで書かれ、ワークフロー中で再利用できるタスクを提供します。 {% data variables.product.prodname_actions %}はアクションと呼ばれる協力で柔軟な再利用できるコンポーネントを持っており、これはJavaScriptファイルもしくはDockerイメージで構築できます。 {% data variables.product.product_name %}の API やパブリックに利用可能なサードパーティAPIとのインテグレーションなど、好きな方法でリポジトリを操作するカスタムコードを書いて、アクションを作成することができます。 たとえば、アクションでnpmモジュールを公開する、緊急のIssueが発生したときにSMSアラートを送信する、本番対応のコードをデプロイすることなどが可能です。 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。 +CircleCIと{% data variables.product.prodname_actions %}は、どちらもワークフロー中のタスクを再利用し、共有するための仕組みを提供しています。 CircleCIはorbsという概念を利用します。これはYAMLで書かれ、ワークフロー中で再利用できるタスクを提供します。 {% data variables.product.prodname_actions %}はアクションと呼ばれる強力で柔軟な再利用できるコンポーネントを持っており、これはJavaScriptファイルもしくはDockerイメージで構築できます。 {% data variables.product.product_name %}の API やパブリックに利用可能なサードパーティAPIとのインテグレーションなど、好きな方法でリポジトリを操作するカスタムコードを書いて、アクションを作成することができます。 たとえば、アクションでnpmモジュールを公開する、緊急のIssueが発生したときにSMSアラートを送信する、本番対応のコードをデプロイすることなどが可能です。 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。 CircleCIは、YAMLのアンカーとエイリアスでワークフローの部分を再利用できます。 {% data variables.product.prodname_actions %}はビルドマトリックスを使って、再利用性についての一般的な要求のほとんどをサポートします。 ビルドマトリックスに関する詳細な情報については「[複雑なワークフローを管理する](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)」を参照してください。 @@ -53,7 +58,7 @@ CircleCIは、共通の依存関係を持つ一連のビルド済みのイメー Dockerのファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %}ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 -{% data variables.product.prodname_dotcom %}ホストの仮想環境で利用できるツールとパッケージに関する詳しい情報については「[{% data variables.product.prodname_dotcom %} ホストランナーにインストールされているソフトウェア](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 +{% data variables.product.prodname_dotcom %}ホストの仮想環境で利用できるツールとパッケージに関する詳しい情報については「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 ### 変数とシークレットの利用 @@ -102,7 +107,7 @@ GitHub Actions
    @@ -303,15 +305,14 @@ tag_with_ref: true - This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. - A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)." -### Instalar un paquete mediante una acción +### Installing a package using an action -Puedes instalar paquetes como parte de tu flujo de CI mediante {% data variables.product.prodname_actions %}. Por ejemplo, podrías configurar un flujo de trabajo para que cada vez que un programador suba código a una solicitud de extracción, el flujo de trabajo resuelva las dependencias al descargar e instalar paquetes alojados por el {% data variables.product.prodname_registry %}. Luego, el flujo de trabajo puede ejecutar pruebas de CI que requieran las dependencias. +You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. -El instalar paquetes que hospeda el {% data variables.product.prodname_registry %} a través de las {% data variables.product.prodname_actions %} requiere una configuración mínima o autenticación adicional cuando utilizas un `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} También, la transferencia de datos es gratuita cuando una acción instala un paquete. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". +Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} {% if currentVersion == "free-pro-team@latest" %} -`GITHUB_TOKEN` no puede instalar paquetes desde ningún repositorio privado además del repositorio donde se ejecuta la acción. Actualmente, no puedes utilizar `GITHUB_TOKEN` para autenticarte en el -{% data variables.product.prodname_github_container_registry %}. +`GITHUB_TOKEN` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. {% endif %} {% data reusables.package_registry.actions-configuration %} diff --git a/translations/es-ES/content/packages/index.md b/translations/es-ES/content/packages/index.md index 552e59ec0b..28a5124fd3 100644 --- a/translations/es-ES/content/packages/index.md +++ b/translations/es-ES/content/packages/index.md @@ -12,25 +12,23 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - - - title: Los nombres de contenedor ghcr.io redireccionan a la página de dicho contenedor + - title: modo de mantenimiento de ghcr.io en 2021-01-09 + date: '2021-01-08' + href: 'https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/' + - title: Los nombres de contenedor ghcr.io redireccionan a la página de dicho contenedor date: '2020-12-14' - href: https://github.blog/changelog/2020-12-14-ghcr-io-container-names-redirect-to-the-container-page/ - - - title: Filtrar para contenedores etiquetados y no etiquetados + href: 'https://github.blog/changelog/2020-12-14-ghcr-io-container-names-redirect-to-the-container-page/' + - title: Filtrar para contenedores etiquetados y no etiquetados date: '2020-12-14' - href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: El soporte para los contenedores de los paquetes es un beta al que puedes decidir ingresar - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + href: 'https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md b/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md index 4aad622c8d..203df83f4e 100644 --- a/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/es-ES/content/packages/learn-github-packages/about-github-packages.md @@ -1,6 +1,6 @@ --- -title: Acerca de GitHub Packages -intro: '{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquete de software que te permite alojar tus paquetes de software de forma privada o pública y usar paquetes como dependencias en tus proyectos.' +title: About GitHub Packages +intro: '{% data variables.product.prodname_registry %} 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.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/about-github-package-registry @@ -14,13 +14,13 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -### Acerca de {% data variables.product.prodname_registry %} +### About {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquetes, totalmente integrado con {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combina tu código fuente y tus paquetes en un solo lugar para proporcionar facturación y gestión de permisos integrada, para que puedas centralizar tu desarrollo de software en {% data variables.product.product_name %}. +{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management and billing, so you can centralize your software development on {% data variables.product.product_name %}. -Puedes integrar {% data variables.product.prodname_registry %} con las API de {% data variables.product.product_name %}, {% data variables.product.prodname_actions %} y webhooks para crear un flujo de trabajo de DevOps de extremo a extremo que incluya tu código, CI y soluciones de implementación. +You can integrate {% data variables.product.prodname_registry %} with {% data variables.product.product_name %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. -Puedes alojar múltiples paquetes en un repositorio y ver más información acerca de cada paquete al ver el README del paquete, las estadísticas de descarga, el historial de la versión y mucho más. +{% data variables.product.prodname_registry %} offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget. {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -30,7 +30,7 @@ Puedes alojar múltiples paquetes en un repositorio y ver más información acer {% endif %} {% if currentVersion == "free-pro-team@latest" %} -Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)". +{% data variables.product.prodname_registry %} also offers a {% data variables.product.prodname_container_registry %} designed to support the unique needs of container images. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% data reusables.package_registry.container-registry-beta %} @@ -38,136 +38,136 @@ Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions % {% endif %} -#### Visualizar paquetes +#### Viewing packages -Puedes revisar el README del paquete, algunos metadatos como los detalles de la licencia, las estadísticas de descarga, el historial de versiones y más en {% data variables.product.product_name %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/manage-packages/viewing-packages)". +You can review the package's README, some metadata like licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)." -#### Acerca de los permisos y la visibilidad de los paquetes +#### About package permissions and visibility -| | Registros de los paquetes | -| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Ubicaciones de hospedaje | Puedes hospedar paquetes múltiples en un repositorio. | -| Permisos | {{ site.data.reusables.package_registry.public-or-private-packages }} Puedes utilizar los roles y equipos de {{ site.data.variables.product.prodname_dotcom }} para limitar quién puede instalar o publicar cada paquete, ya que los paquetes heredan los permisos del repositorio. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | -| Visibilidad | {% data reusables.package_registry.public-or-private-packages %} +| | Package registries | +|----|----| +| Hosting locations | You can host multiple packages in one repository. | +| Permissions | Each package inherits the permissions of the repository where the package is hosted.

    For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | +| Visibility | {% data reusables.package_registry.public-or-private-packages %} | {% if currentVersion == "free-pro-team@latest" %} -### Acerca de la facturación para {% data variables.product.prodname_registry %} +### About billing for {% data variables.product.prodname_registry %} -{% data reusables.package_registry.packages-billing %}{% data reusables.package_registry.packages-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". +{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." {% data reusables.package_registry.container-registry-beta-billing-note %} {% endif %} -### Formatos y clientes admitidos +### Supported clients and formats -{% data variables.product.prodname_registry %} usa los comandos de herramientas del paquete nativo con los que ya estás familiarizado para publicar e instalar versiones del paquete. -#### Soporte para los registros de paquetes +{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions. +#### Support for package registries {% if currentVersion == "free-pro-team@latest" %} -Los registros de paquetes utilizan a `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` como la URL de hospedaje de paquetes, reemplazando `PACKAGE-TYPE` con el espacio de nombre de paquete. Por ejemplo, tu Gemfile se hospedará en `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`. +Package registries use `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL, replacing `PACKAGE-TYPE` with the Package namespace. For example, your Gemfile will be hosted at `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`. {% else %} -Los tipos de paquete compatibles en {% data variables.product.product_location %} pueden variar ya que tu administrador de sitio puede habilitar o inhabilitar el soporte para diferentes tipos de paquetes. Para obtener más informacón, consulta la sección "[Administrar GitHub Packages para tu empresa](/enterprise/admin/packages)". +The package types supported on {% data variables.product.product_location %} may vary since your site administrator can enable or disable support for different package types. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." -Si {% data variables.product.product_location %} tiene habilitado el aislamiento de subdominio, entonces los registros de paquete utilizarán `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` como la URL de hospedaje de paquetes, reemplazando a `PACKAGE-TYPE` con el espacio de nombre del paquete. Por ejemplo, tu Dockerfile se hospedará en `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME`. +If {% data variables.product.product_location %} has subdomain isolation enabled, then package registries will use `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL, replacing `PACKAGE-TYPE` with the Package namespace. For example, your Dockerfile will be hosted at `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME`. -Si se inhabilitó el aislamiento de subdominios en {% data variables.product.product_location %}, entonces los registros de paquete utilizarán `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` como la URL de hospedaje de pquetes. Por ejemplo, tu Gemfile se hospedaría en `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME`, reemplazando *HOSTNAME* con el nombre del host de tu instancia de {% data variables.product.prodname_ghe_server %}. |{% endif %} +If {% data variables.product.product_location %} has subdomain isolation disabled, then package registries will use `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL. For example, your Gemfile will be hosted at `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME`, replacing *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance. + +{% endif %} {% if currentVersion == "free-pro-team@latest" %} -| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Nombre de espacio del paquete | -| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | ----------------------------------------------------- | -| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | + +| Language | Description | Package format | Package client | Package namespace | +| --- | --- | --- | --- | --- | +| JavaScript | Node package manager | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` +| Ruby | RubyGems package manager | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` +| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` +| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` +| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` {% else %} -Con el aislamiento de subdominios habilitado en {% data variables.product.product_location %}: +With subdomain isolation enabled on {% data variables.product.product_location %}: -| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Nombre de espacio del paquete | -| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | ----------------------------------------------- | -| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| N/A | Plataforma de administración del contenedor Docker | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Language | Description | Package format | Package client | Package namespace | +| --- | --- | --- | --- | --- | +| JavaScript | Node package manager | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` +| Ruby | RubyGems package manager | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` +| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` +| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` +| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` +| N/A | Docker container management | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` -Con el aislamiento de subdominios inhabilitado en {% data variables.product.product_location %}: +With subdomain isolation disabled on {% data variables.product.product_location %}: -| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Nombre de espacio del paquete | -| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | --------------------------------------------------------- | -| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | +| Language | Description | Package format | Package client | Package namespace | +| --- | --- | --- | --- | --- | +| JavaScript | Node package manager | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` +| Ruby | RubyGems package manager | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` +| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` +| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` +| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` {% note %} -**Nota:** Docker no es compatible cuando inhabilitas el aislamiento de subdominios. +**Note:** Docker is not supported when subdomain isolation is disabled. {% endnote %} -Para obtener más información acerca del aislamiento de subdominios, consulta la sección "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". +For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." {% endif %} -Para obtener más información sobre cómo configurar tu cliente de paquetes para utilizarlo con el {% data variables.product.prodname_registry %}, consulta la sección "[Guías del cliente de paquetes para el {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)". +For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Package client guides for {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)." {% if currentVersion == "free-pro-team@latest" %} -Para obtener más información acerca de Docker y del -{% data variables.product.prodname_github_container_registry %}, consulta la sección "[Guías de contenedor para {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)". +For more information about Docker and {% data variables.product.prodname_github_container_registry %}, see "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)." {% endif %} -### Autenticarte en {% data variables.product.prodname_registry %} +### Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -### Administrar paquetes +### About scopes and permissions for package registries -Para instalar o publicar un paquete, debes usar un token con el ámbito adecuado, y tu cuenta de usuario debe tener los permisos pertinentes para ese repositorio. +To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. -Por ejemplo: -- Para descargar e instalar paquetes desde un repositorio, tu token debe tener el ámbito `read:packages`, y tu cuenta de usuario debe tener permisos de lectura para el repositorio. -- Para eliminar una versión especificada de un paquete privado en {% data variables.product.product_name %}, tu token debe tener los ámbitos `delete:packages` y `repo`. Los paquetes públicos no se pueden eliminar. Para obtener más información, consulta "[Eliminar un paquete](/packages/manage-packages/deleting-a-package)". +For example: +- To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permissions for the repository. +- To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)." -| Ámbito | Descripción | Permisos de repositorio | -| ----------------- | ------------------------------------------------------------------------------------------------------ | ----------------------- | -| `read:packages` | Descarga e instala paquetes de {% data variables.product.prodname_registry %} | lectura | -| `write:packages` | Carga y publica paquetes en {% data variables.product.prodname_registry %} | escritura | -| `delete:packages` | Elimina versiones especificadas de paquetes privados de {% data variables.product.prodname_registry %} | admin | -| `repo` | Carga y borra los paquetes (junto con los `write:packages`, o los `delete:packages`) | escritura o admin | +| Scope | Description | Repository permissions | +| --- | --- | --- | +|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read | +|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write | +| `delete:packages` | Delete specified versions of private packages from {% data variables.product.prodname_registry %} | admin | +| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or admin | -Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal. +When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. -Para obtener más información, consulta: -- Encuentras algo que contradice la documentación -- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token/)" -- Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal +For more information, see: +- "[Using {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}](/packages/using-github-packages-with-your-projects-ecosystem/)" +- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)" +- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)" -### Administrar paquetes +### Managing packages -You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. Cuando usas la API de GraphQL para consultar y eliminar paquetes privados, debes usar el mismo token que usas para autenticarte en {% data variables.product.prodname_registry %}. Para obtener más información, consulta las secciones "[Borrar un paquete](/packages/manage-packages/deleting-a-package)" y "[Formar llamadas con GraphQL](/graphql/guides/forming-calls-with-graphql)". +You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." -Puedes configurar webhooks para suscribirte a eventos relacionados con paquetes, como cuando se publica o se actualiza un paquete. Para obtener más información, consulta el "[evento de webhook de `package`](/webhooks/event-payloads/#package)". +You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." -### Contactar con soporte técnico +### Contacting support {% if currentVersion == "free-pro-team@latest" %} -Si tienes retroalimentación o solicitudes de características para -{% data variables.product.prodname_registry %}, utiliza el [formato de retroalimentación para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). +If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use the [feedback form for {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). -Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si: +Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if: -* Experimentas alguna cosa que contradice la documentación -* Encuentras errores vagos o poco claros -* Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal +* You experience anything that contradicts the documentation +* You encounter vague or unclear errors +* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information {% else %} -Si necesitas soporte para -{% data variables.product.prodname_registry %}, por favor, contacta a tus administradores de sistema. +If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators. {% endif %} diff --git a/translations/es-ES/content/packages/manage-packages/deleting-a-package.md b/translations/es-ES/content/packages/manage-packages/deleting-a-package.md index b15ffde2d1..f3956d5c2e 100644 --- a/translations/es-ES/content/packages/manage-packages/deleting-a-package.md +++ b/translations/es-ES/content/packages/manage-packages/deleting-a-package.md @@ -54,7 +54,7 @@ Usa la mutación `deletePackageVersion` en la API de GraphQL. Debes usar un toke Aquí hay un comando cURL de ejemplo para eliminar una versión de paquete con el ID de versión del paquete de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, mediante un token de acceso personal. {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/es-ES/content/packages/manage-packages/viewing-packages.md b/translations/es-ES/content/packages/manage-packages/viewing-packages.md index 5adf88e588..90ff88f535 100644 --- a/translations/es-ES/content/packages/manage-packages/viewing-packages.md +++ b/translations/es-ES/content/packages/manage-packages/viewing-packages.md @@ -33,7 +33,7 @@ Puedes ver todos los paquetes instalados en una organización y buscar un paquet {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} -3. Under your organization name, click +3. Debajo del nombre de tu organización, da clic en {% octicon "package" aria-label="The package icon" %} **Paquetes**. {% data reusables.package_registry.navigate-to-packages %} @@ -45,6 +45,6 @@ Puedes ver todos los paquetes que has instalado y buscar uno específico en toda 2. En la zona de navegación principal, sobre la página de perfil, da clic en **Paquetes**. ![Pestaña Project (Proyecto)](/assets/images/help/package-registry/user-packages-tab.png) {% data reusables.package_registry.navigate-to-packages %} -### Further reading +### Leer más - "[Buscar paquetes](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md index 61fdddedb3..1af428af85 100644 --- a/translations/es-ES/content/packages/quickstart.md +++ b/translations/es-ES/content/packages/quickstart.md @@ -1,7 +1,7 @@ --- title: Guía de inciio rápido para GitHub Packages intro: 'Publica en el {% data variables.product.prodname_registry %} en 5 minutos o menos con {% data variables.product.prodname_actions %}.' -allowTitleToDifferFromFilename: verdadero +allowTitleToDifferFromFilename: true versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/es-ES/content/rest/index.md b/translations/es-ES/content/rest/index.md index 6ad3c6e619..3ece64b268 100644 --- a/translations/es-ES/content/rest/index.md +++ b/translations/es-ES/content/rest/index.md @@ -1,6 +1,6 @@ --- title: API de REST de GitHub -shortTitle: REST API +shortTitle: API de REST intro: 'Puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %} para crear llamadas y obtener los datos que necesitas para integrar con GitHub.' redirect_from: - /v3 diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md index 4d13ab2415..f58efb6702 100644 --- a/translations/es-ES/content/rest/overview/libraries.md +++ b/translations/es-ES/content/rest/overview/libraries.md @@ -73,12 +73,16 @@ Nombre de biblioteca | Repositorio |---|---| **Cliente PHP de GitHub **|[tan-tan ### Python -Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Nombre de la Biblioteca | Repositorio |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby Nombre de biblioteca | Repositorio |---|---| **Gema de la API de GitHub API**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +### Rust + +Nombre de la biblioteca | Repositorio |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) + ### Scala Nombre de biblioteca | Repositorio |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) diff --git a/translations/es-ES/content/rest/overview/media-types.md b/translations/es-ES/content/rest/overview/media-types.md index dfc49e01dc..6f500a9281 100644 --- a/translations/es-ES/content/rest/overview/media-types.md +++ b/translations/es-ES/content/rest/overview/media-types.md @@ -104,7 +104,7 @@ Devuelve los datos del blob sin procesar. La [API de confirmaciones](/rest/reference/repos#commits) y la [API de solicitudes de cambios](/rest/reference/pulls) soportan los formatos de [diff][git-diff] y de [parche][git-patch]: -#### diff +#### diferencia application/vnd.github.VERSION.diff diff --git a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md index 7d7d98298c..6f6e6e75f0 100644 --- a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md @@ -215,7 +215,7 @@ Todos los objetos de error tienen propiedades de campo y de recurso para que tu | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | `missing` | Un recurso no existe. | | `missing_field` | No se ha configurado un campo requerido en un recurso. | -| `no válida` | El formato de un campo es inválido. Review the documentation for more specific information. | +| `no válida` | El formato de un campo es inválido. Revisa la documentación para encontrar información más específica. | | `already_exists` | Otro recurso tiene el mismo valor que este campo. Esto puede suceder en recursos que deben tener claves únicas (tales como nombres de etiqueta). | | `unprocessable` | Las entradas proporcionadas son inválidas. | @@ -236,14 +236,14 @@ Podrían utilizarse otros códigos de estado de redirección de acuerdo con la e Cuando sea posible, la API v3 intentará utilizar los verbos HTTP adecuados para cada acción. -| Verbo | Descripción | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `HEAD` | Puede emitirse contra cualquier recurso para obtener solo la información del encabezado HTTP. | -| `GET` | Se utiliza para recuperar recursos. | -| `POST` | Se utiliza para crear recursos. | -| `PATCH` | Se utiliza para actualizar los recursos con datos parciales de JSON. Por ejemplo, un recurso de emisión tiene los atributos `title` y `body`. A `PATCH` request may accept one or more of the attributes to update the resource. | -| `PUT` | Se utiliza para reemplazar recursos o colecciones. Para las solicitudes de `PUT` sin el atributo `body`, asegúrate de configurar el encabezado `Content-Length` en cero. | -| `DELETE` | Se utiliza para borrar recursos. | +| Verbo | Descripción | +| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `HEAD` | Puede emitirse contra cualquier recurso para obtener solo la información del encabezado HTTP. | +| `GET` | Se utiliza para recuperar recursos. | +| `POST` | Se utiliza para crear recursos. | +| `PATCH` | Se utiliza para actualizar los recursos con datos parciales de JSON. Por ejemplo, un recurso de emisión tiene los atributos `title` y `body`. Una solicitud de `PATCH` podría aceptar uno o más de los atributos para actualizar el recurso. | +| `PUT` | Se utiliza para reemplazar recursos o colecciones. Para las solicitudes de `PUT` sin el atributo `body`, asegúrate de configurar el encabezado `Content-Length` en cero. | +| `DELETE` | Se utiliza para borrar recursos. | ### Hypermedia diff --git a/translations/es-ES/content/rest/reference/activity.md b/translations/es-ES/content/rest/reference/activity.md index 5970c20616..8668b03539 100644 --- a/translations/es-ES/content/rest/reference/activity.md +++ b/translations/es-ES/content/rest/reference/activity.md @@ -142,11 +142,11 @@ Hay una lista potencial de `reason` para recibir una notificación: | Nombre de la razón | Descripción | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `assign` | Se te asignó al informe de problemas. | -| `author` | Creaste el hilo. | -| `comment` | Comentaste en el hilo. | -| `invitation` | Aceptaste una invitación para colaborar en el repositorio. | +| `autor` | Creaste el hilo. | +| `comentario` | Comentaste en el hilo. | +| `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). | -| `mention` | Se te **@mencionó** específicamente en el contenido. | +| `mención` | Se te **@mencionó** específicamente en el contenido. | | `review_requested` | Se te solicitó, o se solicitó a un equipo del cual eres miembro, revisar una solicitud de extracción.{% if currentVersion == "free-pro-team@latest" %} | `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). | diff --git a/translations/es-ES/content/rest/reference/checks.md b/translations/es-ES/content/rest/reference/checks.md index a90c4d0f27..ea4b17d173 100644 --- a/translations/es-ES/content/rest/reference/checks.md +++ b/translations/es-ES/content/rest/reference/checks.md @@ -20,7 +20,7 @@ La API de Verificaciones te permite crear GitHub Apps que ejecuten verificacione {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %} {% endfor %} -## Check Suites +## Conjuntos de Verificaciones {% note %} diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md index 8d9183043e..1f8fda8b12 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 -allowTitleToDifferFromFilename: verdadero +title: GitHub Enterprise administration +allowTitleToDifferFromFilename: true redirect_from: - /v3/enterprise-admin - /v3/enterprise @@ -10,46 +10,49 @@ versions: github-ae: '*' --- -You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. +You can use these endpoints to administer your enterprise. {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Nota:** Este artículo aplica a {% data variables.product.prodname_ghe_cloud %}. Si quieres ver la versión para {% 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_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{% if enterpriseServerVersions contains currentVersion %}—excepto las terminales de la API de [Consola de Administración](#management-console)—{% endif %} se prefijan con la siguiente URL: +REST API endpoints{% if enterpriseServerVersions contains currentVersion %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: ```shell http(s)://hostname/api/v3/ ``` {% if enterpriseServerVersions contains currentVersion %} -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 %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -### 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/)** {% if enterpriseServerVersions contains currentVersion %}(los cuales se pueden crear utilizando la [API de autorizciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}o la **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} 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/)** {% if enterpriseServerVersions contains currentVersion %}(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)**. {% if enterpriseServerVersions contains currentVersion %} +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{% if enterpriseServerVersions contains currentVersion %}, 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{% if enterpriseServerVersions contains currentVersion %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -### 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 %} @@ -59,7 +62,7 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% if currentVersion == "free-pro-team@latest" %} -## Registro de auditoría +## Audit log {% for operation in currentRestOperations %} {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} @@ -68,7 +71,7 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% endif %} {% if currentVersion == "free-pro-team@latest" %} -## Facturación +## Billing {% for operation in currentRestOperations %} {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %} @@ -88,46 +91,46 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% if currentVersion == "free-pro-team@latest" %} ## SCIM -### Aprovisionamiento de SCIM para Empresas +### SCIM Provisioning for Enterprises -Los Proveedores de Identidad (IdPs) con SCIM habilitado pueden utilizar la API de SCIM para automatizar el aprovisionamiento de la membresía empresarial. La API de {% data variables.product.product_name %} se basa en la versión 2.0 del [estándar de SCIM](http://www.simplecloud.info/). +SCIM-enabled Identity Providers (IdPs) can use the SCIM API to automate the provisioning of enterprise membership. The {% data variables.product.product_name %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). -El IdP debe utilizar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{enterprise}/` como la terminal de SCIM. +The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/{enterprise}/` as the SCIM endpoint. {% note %} -**Nota:** La API empresarial de SCIM solo se encuentra disponible para las empresas en [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) que cuenten con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." {% endnote %} -### Autenticar las llamadas a la API de SCIM +### Authenticating calls to the SCIM API -Debes autenticarte como un propietario de una empresa de {% data variables.product.product_name %} para utilizar su API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También podrías utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu SSO empresarial de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). +You must authenticate as an owner of a {% data variables.product.product_name %} enterprise to use its SCIM API. The API expects an [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) token to be included in the `Authorization` header. You may also use a personal access token, but you must first [authorize it for use with your SAML SSO enterprise](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). -### Mapeo de los datos de SAML y de SCIM +### Mapping of SAML and SCIM data -El IdP de SAML y el cliente de SCIM deben utilizar valores coincidentes de `NameID` y `userName` para cada usuario. Esto le permite al usuario que se autentica mediante SAML el poder enlazarse con su identidad aprovisionada de SCIM. +The SAML IdP and the SCIM client must use matching `NameID` and `userName` values for each user. This allows a user authenticating through SAML to be linked to their provisioned SCIM identity. -Los grupos de SCIM se empatan con las organizaciones de {% data variables.product.product_name %} que tienen exactamente el mismo nombre, y que son propiedad de la cuenta empresarial. +SCIM groups are matched with {% data variables.product.product_name %} organizations that have the exact same name, and are owned by the enterprise account. -El IdP de SAML y el cliente de SCIM deben configurarse para empatar exactamente el `displayName` del grupo de SCIM con el nombre correspondiente de la organización de {% data variables.product.product_name %}. Esto le permite a {% data variables.product.product_name %} enlazar el grupo de SCIM con la membrecía organizacional de {% data variables.product.product_name %}. +The SAML IdP and SCIM client must be configured to exactly match the `displayName` of the SCIM group with the name of the corresponding {% data variables.product.product_name %} organization. This allows {% data variables.product.product_name %} to link the SCIM group with the {% data variables.product.product_name %} organization membership. -### Atributos de Usuario de SCIM compatibles +### Supported SCIM User attributes -| Nombre | Type | Descripción | -| ---------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `userName` | `secuencia` | El nombre de usuario para el usuario. | -| `name.givenName` | `secuencia` | El primer nombre del usuario. | -| `name.lastName` | `secuencia` | El apellido del usuario. | -| `emails` | `arreglo` | Lista de correos electrónicos del usuario. | -| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` para un usuario ya sea con el proveedor de SAML, o utilizar la terminal de [Listar las identidades aprovisionadas de SCIM para una empresa](#list-scim-provisioned-identities-for-an-enterprise) y filtrar otros atributos conocidos, tales como el nombre de usuario o la dirección de correo electrónico de un usuario de GitHub. | -| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. | -| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). | -| `groups` | `arreglo` | Lista opcional de las ID del grupo de SCIM del cual el usuario es miembro. | +Name | Type | Description +-----|------|-------------- +`userName`|`string` | The username for the user. +`name.givenName`|`string` | The first name of the user. +`name.lastName`|`string` | The last name of the user. +`emails` | `array` | List of user emails. +`externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities for an enterprise](#list-scim-provisioned-identities-for-an-enterprise) endpoint and filtering on other known attributes, such as a user's GitHub username or email address. +`id` | `string` | Identifier generated by the GitHub SCIM endpoint. +`active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false). +`groups` | `array` | Optional list of SCIM group IDs the user is a member of. {% note %} -**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula: +**Note:** Endpoint URLs for the SCIM API are case sensitive. For example, the first letter in the `Users` endpoint must be capitalized: ```shell GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} @@ -135,12 +138,12 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} {% endnote %} -### Atributos del Grupo de SCIM compatibles +### Supported SCIM Group attributes -| Nombre | Type | Descripción | -| ------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `displayName` | `secuencia` | El nombre del grupo de SCIM, el cual debe empatar exactamente con el nombre de la organización de {% data variables.product.product_name %} correspondiente. Por ejemplo, si la URL de la organización es `https://github.com/octo-org`, el nombre del grupo debe ser `octo-org`. | -| `members` | `arreglo` | Lista de IDs de usuario de SCIM que son miembros del grupo. | +Name | Type | Description +-----|------|-------------- +`displayName` | `string` | The name of the SCIM group, which must exactly match the name of the corresponding {% data variables.product.product_name %} organization. For example, if the URL of the organization is `https://github.com/octo-org`, the group name must be `octo-org`. +`members`| `array` | List of SCIM user IDs that are members of the group. {% for operation in currentRestOperations %} {% if operation.subcategory == 'scim' %}{% include rest_operation %}{% endif %} @@ -150,9 +153,10 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} {% if currentVersion == "github-ae@latest" %} -## Cifrado estático +## Encryption at rest -Puedes utilizar la API de cifrado estático para administrar la llave que cifra tus datos en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Configurar el cifrado de datos para tu empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)". +You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. +For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %} @@ -161,9 +165,9 @@ Puedes utilizar la API de cifrado estático para administrar la llave que cifra {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## 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 %} @@ -173,9 +177,9 @@ La API de estadísticas de los administradores proporciona diversas métricas so {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@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 %} @@ -185,11 +189,11 @@ La API de anuncios te permite administrar el letrero de anuncios globales en tu {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## 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 %} @@ -201,9 +205,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. Nota 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 %} @@ -213,9 +217,9 @@ Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## 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 %} @@ -225,31 +229,31 @@ La API de licencias proporciona información sobre tu licencia empresarial. *Sol {% if enterpriseServerVersions contains currentVersion %} -## Consola de administración +## Management console -La API de la Consola de Administración te ayuda a administrar tu {% data variables.product.product_name %} instalación. +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. -También necesitas 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' @@ -262,9 +266,9 @@ $ curl -L 'https://api_key:your-amazing-password@hostname: {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## 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 %} @@ -274,22 +278,25 @@ La API de Administración Organizacional te permite crear organizaciones en tu e {% if enterpriseServerVersions contains currentVersion %} -## 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 %} @@ -299,31 +306,31 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% if enterpriseServerVersions contains currentVersion %} -## 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. | -| `descargar` | `object` | 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 %} @@ -332,24 +339,26 @@ Los valores posibles para `state` son `not_started`, `in_progress`, `success`, ` {% endif %} {% if enterpriseServerVersions contains currentVersion %} -## 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` | `object` | El repositorio de GitHub en donde se mantiene el script. | -| `environment` | `object` | 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 %} @@ -359,21 +368,22 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% if enterpriseServerVersions contains currentVersion %} -## 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 %} @@ -382,9 +392,9 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## Usuarios +## Users -La API de Administración de Usuarios te permite suspender{% if enterpriseServerVersions contains currentVersion %}, dejar de suspender, promover, y degradar{% endif %}{% if currentVersion == "github-ae@latest" %} 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{% if enterpriseServerVersions contains currentVersion %}, unsuspend, promote, and demote{% endif %}{% if currentVersion == "github-ae@latest" %} 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/git.md b/translations/es-ES/content/rest/reference/git.md index 8218605968..c7f9115b30 100644 --- a/translations/es-ES/content/rest/reference/git.md +++ b/translations/es-ES/content/rest/reference/git.md @@ -1,6 +1,6 @@ --- title: Base de datos de Git -allowTitleToDifferFromFilename: verdadero +allowTitleToDifferFromFilename: true redirect_from: - /v3/git versions: diff --git a/translations/es-ES/content/rest/reference/interactions.md b/translations/es-ES/content/rest/reference/interactions.md index a2f1426673..e97ce45d12 100644 --- a/translations/es-ES/content/rest/reference/interactions.md +++ b/translations/es-ES/content/rest/reference/interactions.md @@ -12,7 +12,7 @@ Los usuarios interactuan con los repositorios al comentar, abrir informes de pro {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Organization +## Organización La API de Interacciones Organizacionales permite a los propietarios el restringir temporalmente qué tipo de usuariopuede comentar, abrir propuestas, o crear solicitudes de cambios en los repositorios públicos de la organización. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}: diff --git a/translations/es-ES/content/rest/reference/migrations.md b/translations/es-ES/content/rest/reference/migrations.md index 1fed26a508..d836cb8ac5 100644 --- a/translations/es-ES/content/rest/reference/migrations.md +++ b/translations/es-ES/content/rest/reference/migrations.md @@ -12,7 +12,7 @@ versions: {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Organization +## Organización La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)." y "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)". diff --git a/translations/es-ES/content/rest/reference/orgs.md b/translations/es-ES/content/rest/reference/orgs.md index d0cf4b632c..832bce40ac 100644 --- a/translations/es-ES/content/rest/reference/orgs.md +++ b/translations/es-ES/content/rest/reference/orgs.md @@ -1,6 +1,6 @@ --- title: Organizaciones -allowTitleToDifferFromFilename: verdadero +allowTitleToDifferFromFilename: true redirect_from: - /v3/orgs versions: diff --git a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md index 887979effd..8963fa30aa 100644 --- a/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md @@ -107,7 +107,7 @@ _Search_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permiso sobre las "acciones" - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _Ramas_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Colaboradores_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _Ramas_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Comentarios sobre confirmación de cambios_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -836,6 +842,9 @@ _Equipos_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/es-ES/content/rest/reference/pulls.md b/translations/es-ES/content/rest/reference/pulls.md index 1da9f91900..8b02dacc09 100644 --- a/translations/es-ES/content/rest/reference/pulls.md +++ b/translations/es-ES/content/rest/reference/pulls.md @@ -37,7 +37,7 @@ Las solicitudes de extracción tienen estas posibles relaciones de enlaces: | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `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. | -| `issue` | La ubicación de la API para el [informe de problemas](/rest/reference/issues) de 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. | diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md index 67c361165c..3ea95867a0 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 -allowTitleToDifferFromFilename: verdadero +allowTitleToDifferFromFilename: true redirect_from: - /v3/repos versions: diff --git a/translations/es-ES/content/rest/reference/search.md b/translations/es-ES/content/rest/reference/search.md index eb0314b471..2dca6484d6 100644 --- a/translations/es-ES/content/rest/reference/search.md +++ b/translations/es-ES/content/rest/reference/search.md @@ -1,5 +1,5 @@ --- -title: Search +title: Buscar redirect_from: - /v3/search versions: @@ -94,7 +94,7 @@ Cuando proporcionas el tipo de medios `text-match`, recibirás una clave extra e | `object_url` | La URL del recurso que contiene una propiedad de secuencia que empata con uno de los términos de búsqueda. | | `object_type` | El nombre del tipo de recurso que existe en la `object_url` específica. | | `property` | El nombre de la propiedad del recurso que existe en la `object_url`. Esa propiedad es una secuencia que empata con uno de los términos de la búsqueda. (En el JSON que se devuelve de la `object_url`, el contenido entero para el `fragment` se encontrará en la propiedad con este nombre.) | -| `fragment` | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda. | +| `fragmento` | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda. | | `matches` | Una matriz de uno o más términos de búsqueda presentes en el `fragment`. Los índices (es decir, "intervalos") son relativos al fragmento. (No son relativos al contenido _completo_ de `property`.) | #### Ejemplo diff --git a/translations/es-ES/data/glossaries/candidates.yml b/translations/es-ES/data/glossaries/candidates.yml index 32ca2e6c9b..c3c46ec185 100644 --- a/translations/es-ES/data/glossaries/candidates.yml +++ b/translations/es-ES/data/glossaries/candidates.yml @@ -1,203 +1,203 @@ --- - - term: Premium Support + term: Soporte prémium - - term: Standard Support + term: Soporte estándar - - term: Incident + term: Incidente - - term: submit + term: enviar - - term: contact person + term: persona de contacto - - term: Severity + term: Gravedad - - term: Service Level Agreement + term: Acuerdo de nivel de servicio - - term: credit + term: crédito - - term: account management team + term: equipo de gestión de cuentas - term: ticket - - term: Enterprise Support + term: Soporte empresarial - - term: support portal + term: portal de soporte - - term: Urgent + term: Urgente - - term: High + term: Alto - - term: Moderate + term: Moderado - - term: Low + term: Bajo - - term: extended support bundle + term: paquete de soporte extendido - - term: company name + term: nombre de la empresa - - term: privacy mode + term: modo de privacidad - - term: Authentication method + term: Método de autenticación - - term: hours of operation + term: horas de operación - - term: leadership + term: liderazgo - - term: Escalate to Management + term: Escalar a la administración - - term: missed ticket responses + term: respuestas de tickets perdidos - - term: Geo-replication + term: Replicación geográfica - - term: production system + term: sistema de producción - - term: de-identified of sensitive data + term: datos confidenciales no identificados - - term: business justification + term: justificación comercial - - term: Qualifying credits + term: Créditos de calificación - - term: Contacting sales + term: Contacto de ventas - - term: Contacting training + term: Contacto de capacitación - - term: Outbound + term: Saliente - - term: alphanumeric + term: alfanumérico - - term: quotation + term: presupuesto - - term: pricing plan + term: plan de precios - - term: unit plan + term: plan unitario - - term: role + term: rol - - term: redeem coupon + term: canjear cupón - - term: free plan + term: plan gratuito - term: gratis - - term: discount + term: descuento - - term: stale review + term: revisión en espera - - term: contribution credit + term: crédito de contribución - - term: conflict marker + term: marcador de conflicto - - term: Work-in-progress commit + term: Confirmación de trabajo en curso - - term: ancestor commit + term: confirmación de ancestro - - term: contribution graph + term: gráfico de contribución - - term: approve + term: aprobar - - term: dismiss + term: descartar - - term: stage + term: etapa - - term: invitation + term: invitación - - term: uptime + term: tiempo de actividad - - term: discussion + term: debate - - term: service and privacy policy + term: política de servicio y privacidad - - term: reinstate + term: reinstaurar - - term: admin center + term: centro de administración - - term: academic role + term: rol académico - - term: educational discount + term: descuento educativo - - term: disposable domain + term: dominio deshechable - - term: roll over + term: volver a lanzar - - term: quota + term: cuota - - term: private key + term: llave privada - - term: public key + term: llave pública - term: hotpaching - - term: feature release + term: característica de lanzamiento - - term: co-authored commit + term: confirmación conjunta - - term: subdomain isolation + term: aislamiento de subdominio - - term: built-in authentication + term: autenticación incorporada - - term: abuse rate limits + term: límites de tasa de abuso - - term: load average + term: carga promedio - - term: ephemeral + term: efímero - - term: pre-flight check + term: control de prevuelo - - term: account representative + term: representante de cuenta - - term: unified search + term: búsqueda unificada - - term: dormant user + term: usuario inactivo - - term: delivery + term: entrega - - term: legal hold + term: titular legal - - term: unsolicited response SSO + term: SSO de respuesta no solicitada - - term: IdP initiated SSO + term: SSO iniciado por IdP - - term: authenticity of messages + term: autenticidad de los mensajes - - term: All rights reserved + term: Todos los derechos reservados - - term: Campus Advisors + term: Asesores de campus - - term: Campus Experts + term: Expertos en campus - - term: collaborative development models + term: modelos de desarrollo colaborativo - - term: unified view + term: vista unificada - - term: three-dot diff + term: diferenciación de tres puntos - - term: rich diff + term: diff enriquecido - - term: conversation + term: conversación - - term: public gist / secret gist + term: gist público/secreto - - term: extension + term: extensión - - term: procurement companies + term: empresas de contratación - - term: renewal orders + term: pedidos de renovación - - term: per-user pricing + term: precio por usuario - - term: watcher + term: observador - - term: Required commit signing + term: Firma de confirmación requerida - - term: Check Suites + term: Conjuntos de Verificaciones - - term: classroom discount + term: descuento para aulas - - term: student developer pack + term: paquete de desarrollador estudiante - - term: academic research discount + term: descuento de investigación académica - - term: Stargazers + term: Fans - - term: spam unflagging + term: dejar de marcar el spam diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml index cef46fb9e1..bcfb64ba59 100644 --- a/translations/es-ES/data/glossaries/external.yml +++ b/translations/es-ES/data/glossaries/external.yml @@ -1,143 +1,143 @@ --- - - term: '@mention' + term: '@mención' description: para notificar a una persona en GitHub usando "@" antes de su nombre de usuario. Los usuarios en una organización en GitHub también pueden ser parte de un equipo que puede ser mencionado. - - term: access token + term: token de acceso description: >- Un token que se usa en lugar de una contraseña cuando se realizan operaciones Git a través de HTTPS con Git en la línea de comandos o la API. También denominado un token de acceso personal. - - term: account recovery token + term: token de recuperación de cuenta description: >- La credencial de autenticación almacenada como parte de la configuración de recuperación de una cuenta denominada Recuperar cuentas en otro lugar que te permite almacenar esta credencial de respaldo. - - term: API preview + term: Vista previa de API description: >- Una manera de probar nuevas API y cambiar a métodos API existentes antes de que se vuelvan parte de la API de GitHub oficial. - - term: appliance + term: aplicativo description: >- Una aplicación de software combinada con Sólo lo Necesario de un Sistema Operativo (JeOS) para funcionar de manera óptima en el hardware estándar de la industria (generalmente, un servidor) o en una máquina virtual. - term: asignatario description: El usuario que es asignado a una propuesta. - - term: authentication code + term: código de autenticación description: >- Un código que suministrarás, además de tu contraseña GitHub, cuando inicias sesión con 2FA a través del buscador. Este código se genera ya sea mediante una aplicación o se envía a tu teléfono mediante un mensaje de texto. También denominado "Código de autenticación 2FA". - term: rama base description: La rama en la que los cambios se combinan cuando fusionas una solicitud de extracción. Cuando creas una solicitud de extracción, puedes cambiar la rama base desde la rama predeterminada del repositorio a otra rama si lo requieres. - - term: basic authentication + term: autenticación básica description: >- Un método de autenticación en donde las credenciales se envían como texto sin cifrar. - - term: bio + term: biografía description: >- - La descripción generada por el usuario encontrada en un perfil: https://help.github.com/articles/adding-a-bio-to-your-profile/ + The user-generated description found on a profile: [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile) - - term: billing cycle + term: ciclo de facturación description: El intervalo de tiempo para tu plan de facturación específico. - - term: billing email + term: correo electrónico de facturación description: >- La dirección de correo electrónico de la organización donde GitHub envía los recibos, los cargos de tarjeta de crédito o PayPal y otras comunicaciones relacionadas a la facturación. - - term: billing manager + term: gerente de facturación description: El miembro de la oranización que administra los parámetros de facturación para una organización. - - term: billing plan + term: plan de facturación description: >- Los planes de pago para usuarios y organizaciones que incluyen características establecidas para cada tipo de plan. - - term: blame + term: último responsable description: >- La función "último responsable" en Git describe las últimas modificaciones para cada línea e un archivo, que generalmente muestra la revisión, el autor y la hora. Esto es útil, por ejemplo, para detectar cuándo se agregó una función o qué confirmación de cambios llevó a un error en particular. - - term: block + term: bloquear description: >- Eliminar la posibilidad de un usuario de colaborar con los repositorios de una organización. - - term: branch + term: rama description: >- Una rama es una versión paralela de un repositorio. El repositorio la contiene, pero no afecta la rama primaria o principal, lo que te permite trabajar libremente sin interrumpir la versión "activa". Una vez que haz hecho las modificaciones que deseabas, puedes fusionar tu rama de nuevo en la rama principal para publicar tus modificaciones. - - term: branch restriction + term: restricción de rama description: >- Una restricción que los administradores de repositorio pueden activar para que solo ciertos usuarios o equipos puedan subir o hacer ciertas modificaciones en la rama. - - term: Business plan + term: Plane de negocios description: >- Un plan de facturación de la organización donde puedes colaborar en repositorios públicos y privados ilimitados, permitir o solicitar a los miembros de la organización autenticar GitHub usando SSO de SAML y aprovisionar y desaprovisionar acceso con SAML o SCIM. - - term: CA certificate + term: Certificado CA description: >- Un certificado digital emitido por una entidad de certificación (CA) que garantiza que hay conexiones válidas entre dos máquinas, como el equipo de un usuario y GitHub.com y que verifica la titularidad de un sitio. - - term: card + term: tarjeta description: Un cuadrado móvil dentro del tablero de proyecto asociado con una propuesta o una solicitud de extracción. - term: Verificación description: >- Una revisión es un tipo de revisión de estado en {% data variables.product.product_name %}. Ver "[Revisiones de estado](#status-checks)." - - term: checkout + term: control description: >- Puedes usar el "control Git" en la línea de comandos para crear una nueva rama, modificar tu rama de trabajo actual a una rama diferente o incluso cambiar a una versión diferente de un archivo desde una rama diferente con "control git [branchname] [path to file]". La acción "control" actualiza todo a parte del árbol de trabajo con un objeto de árbol o blob desde la base de datos de objetos y actualiza el índice y HEAD si todo el árbol de trabajo apunta a una rama nueva. - - term: cherry-picking + term: selección minusciosa description: >- Para elegir un subconjunto de modificaciones de una serie de modificaciones (generalmente, confirmaciones de cambios) y registrarlas como una nueva serie de modificaciones además de un código base diferente. En Git, esto lo realiza el comando "cherry-pick Git" para extraer el cambio introducido por una confirmación de cambios en otra rama y para registrarlo en función de la sugerencia de la rama actual como una confirmación de cambios nueva. - - term: child team + term: equipo hijo description: >- Dentro de los equipos anidados, el subequipo que hereda los permisos de acceso y las @menciones del equipo padre. - - term: clean + term: limpio description: >- Un árbol de trabajo está limpio si corresponde a la revisión referenciada en el HEAD actual. Consulta también "sucio". - - term: clone + term: clon description: >- Un clon es una copia de un repositorio que vive en tu equipo en vez de en algún lugar del servidor del sitio web o el acto de realizar dicha copia. Cuando haces un clon, puedes editar los archivos en tu editor preferido y usar Git para hacer un seguimiento de tus modificaciones sin tener que estar en línea. El repositorio que clonas sigue conectado a la versión remota para que puedas subir tus modificaciones locales al remoto para mantenerlos sincronizados cuando estás en línea. - - term: clustering + term: agrupar description: >- La posibilidad de ejecutar los servicios GitHub Enterprise en varios nodos y equilibrar la carga de las solicitudes entre ellos. - - term: Code frequency graph + term: Gráfico de frecuencia de código description: >- Un gráfico del repositorio que muestra las adiciones y las eliminaciones de contenido para cada semana en el historial de un repositorio. - - term: code of conduct + term: código de conducta description: Documento que define las normas para participar en una comunidad. - - term: code owner + term: propietario del código description: >- Persona designada como propietario de una parte del código del repositorio. Se le solicita automáticamente al propietario del código que realice una revisión cuando alguien abre una solicitud de extracción (no en el modo borrador) que introduce cambios en el código que posee el propietario. - - term: collaborator + term: colaborador description: >- Un colaborador es una persona con acceso de escritura a un repositorio que ha sido invitada a contribuir a dicho repositorio por su propietario. - - term: commit + term: confirmación description: >- - A commit, or "revision", is an individual change to a file (or set of files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a commit message which is a brief description of what changes were made. + Una confirmación de cambios o "revisión", es una modificación individual a un archivo (o conjunto de archivos). Cuando realizas una confirmación de cambios para guardar tu trabajo, Git crea un ID único (también conocido como, "SHA" o "hash") que te permite mantener un registro de los cambios específicos confirmados junto con quién los realizó y cuándo. Las confirmaciones de cambios generalmente contienen un mensaje de confirmación que es una descripción breve de las modificaciones que fueron realizadas. - - term: commit author + term: autor de la confirmación description: El usuario que realiza la confirmación de cambios. - - term: Commit graph + term: Gráfico de confirmación description: >- Un gráfico del repositorio que muestra todas las confirmaciones de cambios realizadas a un repositorio durante en el último año. - - term: commit ID + term: ID de confirmación description: También conocido como SHA. Un hash de suma de comprobación de 40 caracteres que identifica la confirmación de cambios. - - term: commit message + term: mensaje de confirmación description: >- - Short, descriptive text that accompanies a commit and communicates the change the commit is introducing. + Texto corto y descriptivo que acompaña una confirmación de cambios y comunica el cambio que presenta la confirmación de cambios. - term: rama de comparación description: >- @@ -147,25 +147,25 @@ description: >- También conocida como CI. Un proceso que ejecuta pruebas y compilaciones automatizadas una vez que una persona confirma los cambios para un repositorio configurado en GitHub. La CI es una buena práctica común en el desarrollo de software que ayuda a detectar errores. - - term: contribution graph + term: gráfico de contribución description: >- La parte del perfil de un usuario que muestra sus contribuciones en un período de hasta un año, día a día. - - term: contribution guidelines + term: pautas de contribución description: Un documento que explica cómo las persona deberían contribuir con tu proyecto. - - term: contributions + term: contribuciones description: >- - Actividades específicas en GitHub que: - Agregarán un cuadrado al gráfico de contribuciones de un usuario: "[Que cuenta como una contribución](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Agregarán actividades a la cronología de un usuario en su perfil: "[Actividad de contribución](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" + Specific activities on GitHub that will: - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - - term: contributor + term: contribuyente description: >- Un colaborador es alguien que no tiene acceso de colaborador a un repositorio, pero ha contribuido en un proyecto y tenía una solicitud de extracción que había abierto fusionada en el repositorio. - - term: Contributors graph + term: Gráfico de contribuyentes description: Un gráfico del repositorio que muestra los principales 100 colaboradores de un repositorio. - - term: coupon + term: cupón description: >- Un código proporcionado por GitHub que los usuarios o las organizaciones pueden usar para pagar el total o parte de su suscripción. - @@ -179,11 +179,11 @@ description: >- Tu tablero personal es el concentrador principal para tu actividad en GitHub. Desde éste, puedes llevar el control de incidentes y solicitudes de extracción en los que estás trabajando o a los que estás siguiendo, navegar a tus repositorios y páginas de equipo principales, y aprender sobre la actividad reciente en los repositorios que estás observando o en los que estás participando. También puedes descubrir nuevos repositorios, los cuales se recomiendan con base en los usuarios que sigues y en los repositorios que has marcado con una estrella. Para ver únicamente la actividad de una organización específica, visita tu tablero de organización. Para obtener más información, consulta la sección "[Acerca de tu tablero profesional](/articles/about-your-personal-dashboard)" o "[Acerca de tu tablero de organización](/articles/about-your-organization-dashboard)." - - term: default branch + term: rama predeterminada description: >- La rama base para las solicitudes de cambios nuevas y las confirmaciones de código en un repositorio. Cada repositorio tiene por lo menos una rama, la cual crea Git cuando lo inicializas. Habitualmente, la primera rama se llama `main`, y a menudo es la predeterminada. - - term: Dependents graph + term: Gráfico de dependencias description: >- Un gráfico del repositorio que muestra los paquetes, los proyectos y los repositorios que dependen de un repositorio público. - @@ -191,68 +191,68 @@ description: >- Un gráfico del repositorio que muestra los paquetes y los proyectos de los que depende el respositorio. - - term: deploy key + term: clave de despliegue description: >- Una clave de implementación es una clave SSH que se almacena en tu servidor y concede acceso a un único repositorio GitHub. Esta clave se adjunta directamente al repositorio en lugar de a una cuenta de usuario personal. - - term: detached HEAD + term: HEAD separado description: >- Git te advertirá si estás trabajando en un HEAD separado, lo que significa que Git no apunta a una rama y que cualquier confirmación de cambios que realices, no aparecerá en el historial de confirmaciones de cambios. Por ejemplo, cuando revisas una confirmación de cambios arbitraria que no es la última confirmación de cualquier rama en particular, estás trabajando en un "HEAD separado". - - term: diagnostics + term: diagnóstico description: Una descripción de los parámetros y el entorno de una instancia de GitHub Enterprise. - - term: diff + term: diferencia description: >- Una diferencia es la diferencia en cambios entre dos confirmaciones de cambios o los cambios guardados. La diferencia describirá visualmente lo que se agregó o se eliminó de un archivo desde su última confirmación de cambios. - - term: dirty + term: sucio description: >- Un árbol de trabajo se considera "sucio" si contiene modificaciones que no han sido confirmadas en la rama actual. - - term: email notifications + term: notificaciones por correo electrónico description: Las notificaciones enviadas a la dirección de correo electrónico de un usuario. - - term: Enterprise account + term: Cuenta empresarial description: Las cuentas empresariales te permiten administrar centralmente las políticas y facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.enterprise-accounts %} - term: Explorer description: >- Una instancia de GraphiQL, que es una "IDE GraphQL en el explorador interactiva gráfica". - - term: fast-forward + term: avance rápido description: >- Un avance rápido es un tipo especial de fusión donde tienes una revisión y se "fusionan" los cambios de otra rama que resulta ser un descendiente de lo que tienes. En este caso, no realizas una confirmación de cambios de fusión nueva, si no que, en cambio, solo actualizas esta revisión. Esto sucederá con frecuencia en una rama de seguimiento remoto de un repositorio remoto. - - term: feature branch + term: rama de característica description: >- Una rama usada para experimentar con una nueva función o corregir una propuesta que no está en producción. También llamada rama de tema. - - term: fenced code block - description: 'Un bloque de código sangrado que puedes crear con el formato Markdown de GitHub utilizando triple diagonal inversa \`\`\` antes y después del mismo. Consulta el [example](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' + term: bloque de código cercado + description: 'An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' - - term: fetch + term: recuperar description: >- Cuando usas `git fetch`, estás agregando cambios desde el repositorio remoto a tu rama de trabajo local sin confirmarlos. A diferencia de `git pull`, la recuperación te permite revisar los cambios antes de confirmarlos en tu rama local. - - term: following (users) + term: siguiendo (usuarios) description: Obtener notificaciones acerca de la actividad y las contribuciones de otros usuarios. - - term: force push + term: subida forzada description: >- Un empuje Git que sobreescribe el repositorio remoto con los cambios locales sin tener en cuenta los conflictos. - - term: fork + term: bifurcación description: >- Una bifurcación es una copia personal del repositorio de otro usuario que vive en tu cuenta. Las bifurcaciones te permiten realizar cambios libremente en un proyecto sin afectar el repositorio ascendente original. También puedes abrir una solicitud de extracción en el repositorio ascendente y mantener tu bifurcación sincronizada con los últimos cambios ya que ambos repositorios aún están conectados. - - term: Free plan + term: Plan gratuito description: >- El plan de facturación de la cuenta de un usuario que es gratuito. Los usuarios pueden colaborar en repositorios públicos ilimitados con colaboradores ilimitados. - term: Gist description: >- - A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL. + Un gist es un archivo que se puede compartir y que editas, clonas y bifurcas en GitHub. Puedes hacer que un gist sea {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} o secreto, aunque los gists secretos estarán disponibles para {% if currentVersion == "github-ae@latest" %}cualquier miembro de la empresa{% else %}cualquiera{% endif %} que tenga la URL. - term: Git description: >- @@ -262,14 +262,14 @@ description: >- Las Apps GitHub ofrecen un servicio a toda una organización y usan su propia identidad cuando desempeñan su función. Pueden ser instaladas directamente en las cuentas de usuario y de las organizaciones y pueden garantizar acceso a repositorios específicos. Vienen con permisos exhaustivos y webhooks integrados. - - term: GitHub Flavored Markdown + term: Lenguaje de Marcado Enriquecido de GitHub description: Markdown específico de GitHub usado para dar formato a la prosa y al código en GitHub. Consulta [Formato Markdown específico de GitHub](https://github.github.com/gfm/) o [Introducción a la escritura y el formato en GitHub](/articles/getting-started-with-writing-and-formatting-on-github). - - term: GitHub Importer + term: Importador GitHub description: >- Una herramienta que importa de forma rápida repositorios de código fuente, incluido el historial de revisiones y confirmaciones de cambios, a GitHub para los usuarios. - - term: GitHub Jobs + term: Empleos GitHub description: >- Un sitio de GitHub donde los empleadores pueden publicar empleos en los que los usuarios de GitHub pueden estar interesados. - @@ -277,14 +277,14 @@ description: >- Un subsitio para que los usuarios y las organizaciones de GitHub compren e instalen aplicaciones que extiendan y complementen su flujo de trabajo. - - term: GitHub Pages + term: Páginas de GitHub description: >- También se las conoce como Páginas. Un servicio de alojamiento del sitio estático diseñado para alojar tus páginas del proyecto, de la organización o personales directamente desde un repositorio de GitHub. - - term: GitHub Wiki + term: Wiki de GitHub description: Una sección para alojar documentación de estilo wiki en un repositorio de GitHub. - - term: gitfile + term: archivo git description: >- Un archivo `.git` simple, que siempre está en la raíz de un árbol de trabajo y apunta al directorio de Git, que tiene el repositorio completo de Git y sus meta datos. Puedes ver este archivo para tu repositorio en la línea de comandos con `git rev-parse --git-dir`. que es el repositorio real. - @@ -306,11 +306,11 @@ description: >- Un sistema o componente que está continuamente operativo por un conveniente largo período de tiempo. - - term: hook + term: gancho description: >- Durante la ejecución normal de varios comandos Git, se realizan llamadas a scripts opcionales que le permiten a un programador agregar funcionalidad o comprobación. Generalmente, los ganchos permiten que un comando sea preverificado y potencialmente interrumpido y permite una notificación posterior una vez realizada la operación. - - term: hostname + term: nombre del host description: >- Sobrenombres en lenguaje natural que corresponden a la dirección de un dispositivo conectado a una red. - @@ -318,39 +318,39 @@ description: >- Una imagen autogenerada usada como foto de perfil predeterminada cuando el usuario inicia sesión en GitHub. Los usuarios pueden reemplazar su identicon con su propia foto de perfil. - - term: identity provider + term: proveedor de identidad description: >- También conocido como IdP. Un proveedor de confianza que te permite usar el inicio de sesión único (SSO) de SAML para acceder a otros sitios web. - - term: instance + term: instancia description: >- La copia privada de GitHub de una organización contenida dentro de una máquina virtual que ellos configuran y controlan. - - term: integration + term: integración description: >- Una aplicación de terceros que se integra con GitHub. Estas pueden ser Apps GitHub, Apps OAuth o webhooks. - - term: issue + term: propuesta description: >- Las propuestas son preguntas, tareas o mejoras sugeridas relacionadas al repositorio. Las propuestas pueden ser creadas por cualquiera (para repositorios públicos) y son moderadas por los colaboradores del repositorio. Cada propuesta contiene su propio hilo de debate. También puedes categorizar una propuesta con etiquetas y asignársela a alguien. - term: Jekyll description: Un generador de sitio estático para sitios de una organización, de un proyecto o personales. - - term: Jekyll Theme Chooser + term: selector de tema de Jekyll description: >- Una manera automatizada de seleccionar un tema visual para tu sitio Jekyll sin editar ni copiar archivos CSS. - - term: key fingerprint + term: clave de huella digital description: Una secuencia corta de bytes usados para identificar una clave pública más larga. - term: keychain description: Un sistema de administración de contraseñas en macOS. - - term: keyword + term: palabra clave description: Una palabra específica que cierra una propuesta cuando se usa dentro de una solicitud de extracción. - - term: label + term: etiqueta description: >- Una etiqueta en una propuesta o solicitud de extracción. Los repositorios vienen con una serie de etiquetas predeterminadas, pero los usuarios pueden crear etiquetas personalizadas. - @@ -358,26 +358,26 @@ description: >- Large File Storage de Git. Una extensión de Git de código abierto para controlar las versiones de archivos de gran tamaño. - - term: license + term: licencia description: >- Un documento que puedes incluir con tu proyecto para hacerle saber a las personas qué pueden y qué no pueden hacer con tu código fuente. - - term: Linguist + term: Lingüista description: >- Una biblioteca usada en GitHub para detectar lenguajes blob, ignorar archivos binarios o vendorizado, suprimir los archivos generados en diffs y generar gráficos de desglose del lenguaje. - - term: line comment + term: comentario en la línea description: Un comentario dentro de una solicitud de extracción es una línea de código específica. - - term: line ending + term: fin de línea description: >- Un caracter o caracteres invisibles que simbolizan el final de una línea en un archivo de texto. - - term: locked personal account + term: cuenta personal bloqueada description: >- Una cuenta personal a la que el usuario no puede acceder. Las cuentas se bloquean cuando los usuarios degradan su cuenta paga a una gratis o si su plan de pago se venció. - - term: Management Console + term: Consola de administración description: >- Una sección dentro de la interfaz GitHub Enterprise que contiene funciones administrativas. - @@ -392,64 +392,64 @@ description: >- La rama predeterminada de desarrollo. Cuando creas un repositorio de Git, se crea una rama que se llama `main` y se convierte en la rama activa. En la mayoría de los casos, esta contiene el desarrollo local, aunque esto es puramente por convención y no es forzoso. - - term: master + term: principal description: >- La rama predeterminada en muchos de los repositorios de Git. Predeterminadamente, cuando creas un repositorio de Git nuevo en la línea de comandos, se crea una rama que se llama `master`. Muchas de las herramientas ahora utilizan un nombre alterno para la rama predeterminada. Por ejemplo, cuando creas un repositorio nuevo en GitHub, la rama predeterminada se llama `main`. - - term: Members graph + term: Gráfico de miembros description: Un gráfico del repositorio que muestra todas las bifurcaciones de un repositorio. - - term: mention + term: mención description: >- Una notificación enviada a un usuario anteponiendo el símbolo @ al nombre de usuario. Los usuarios de una organización de GitHub también pueden ser parte de un equipo que puede ser mencionado. - - term: merge + term: fusionar description: >- La fusión toma los cambios de una rama (en el mismo repositorio o de una bifurcación) y los aplica en otra. Esto suele suceder como una "solicitud de extracción" (que puede considerarse como una solicitud a fusionar) o mediante la línea de comandos. Una fusión se puede realizar mediante una solicitud de extracción a través de la interfaz web GitHub.com si no hay cambios conflictivos o bien siempre se puede realizar a través de la línea de comandos. - - term: merge conflict + term: conflicto de fusión description: >- Una diferencia que ocurre entre ramas fusionadas. Los conflictos de fusión suceden cuando las personas realizan diferentes cambios en la misma línea del mismo archivo o cuando una persona edita un archivo y otra persona elimina el mismo archivo. El conflicto de fusión se debe resolver antes de que puedas fusionar las ramas. - - term: milestone + term: hito description: >- Una manera de hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. - - term: mirror + term: espejo description: Una copia nueva de un repositorio. - - term: nested team + term: equipo anidado description: >- Un equipo hijo de un equipo padre. Puedes tener varios equipos hijo (o anidados). - - term: Network graph + term: Gráfico de red description: >- Un gráfico del repositorio que muestra el historial de la rama de toda la red del repositorio, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones de cambios únicas para la red. - - term: News Feed + term: Fuente de noticias description: >- Una vista de la actividad de los repositorios o de las personas que ves. Las Noticias de una organización muestran la actividad en los repositorios que son propiedad de la organización. - - term: non-fast-forward + term: sin avance rápido description: >- Cuando la copia local de un repositorio no está sincronizada con el repositorio ascendente y necesitas extraer los cambios ascendentes antes de subir tus cambios locales. - - term: notification + term: notificación description: >- - Updates, delivered by either the web or email depending on your settings, that give you information about the activities you're interested in. + Actualizaciones que se entregan ya sea por la web o por correo electrónico, dependiendo de tus parámetros, las cuales te brindan información acerca de las actividades en las que estás interesado. - - term: OAuth App + term: App OAuth description: >- Una aplicación de terceros que usa tokens de acceso en lugar de contraseñas para acceder a información para usuarios. - - term: OAuth token + term: token de OAuth description: El token de acceso usado en Apps OAuth para acceder a información para usuarios. - - term: outside collaborator + term: colaborador externo description: >- Un usuario al que se le ha dado acceso a uno o más repositorios de una organización, pero no tiene otro acceso a la organización y no es un miembro de la organización. - - term: open source + term: código abierto description: >- El software de código abierto es un software que se puede usar, modificar y compartir (tanto de la forma modificada como no modificada) libremente por cualquiera. Hoy en día el concepto de "código abierto" suele extenderse más allá del software, para representar una filosofía de colaboración en la cual se facilitan los materiales de trabajo en línea para que cualquiera los bifurque, los modifique y debata y contribuya con ellos. - @@ -457,100 +457,100 @@ description: >- Las organizaciones son un grupo de dos o más usuarios que generalmente imitan a organizaciones del mundo real. Son administradas por usuarios y pueden contener tanto repositorios como equipos. - - term: organization owner + term: propietario de la organización description: Usuarios que tienen un acceso administrativo completo a la organización que poseen. - - term: origin + term: origen description: >- El repositorio ascendente predeterminado. La mayoría de los proyectos tienen al menos un proyecto ascendente al que le hacen un seguimiento. Por defecto, el origen se usa con ese fin. - - term: owner + term: propietario description: >- Miembros de una organización que tienen acceso administrativo completo a la organización. - - term: parent team + term: equipo padre description: >- Dentro de los equipos anidados, el equipo principal desde el cual los equipos hijo heredan los permisos de acceso y @menciones. - - term: participating notifications + term: notificaciones de participación description: >- Una notificación acerca de una actualización en una conversación en una propuesta o solicitud de extracción donde tu nombre de usuario o equipo fue mencionado o donde previamente has respondido a un comentario. - - term: permalink + term: enlace permanente description: Un hipervínculo estático permanente a una página web en particular. - - term: personal account + term: cuenta personal description: >- Una cuenta de GitHub que pertenece a un usuario individual. - - term: primary email address + term: dirección principal de correo electrónico description: >- La dirección principal de correo electrónico donde GitHub envía los recibos, los cargos de tarjeta de crédito o PayPal y otras comunicaciones relacionadas a la facturación. - - term: pinned repository + term: repositorio anclado description: >- Un repositorio que un usuario ha decidido mostrar de forma prominente en su perfil. - - term: pre-receive hooks + term: ganchos de pre-recepción description: >- Los scripts que se ejecutan en el servidor GitHub Enterprise que puedes usar para implementar controles de calidad. - - term: private contributions + term: contribuciones privadas description: Contribuciones hechas a un repositorio privado (vs. público). - - term: private repository + term: repositorio privado description: >- Los repositorios privados solo son visibles para el propietario del repositorio y los colaboradores que el propietario especifique. - - term: production branch + term: rama productiva description: >- Una rama con cambios finales que está lista para ser usada o implementada en una aplicación o un sitio. - - term: profile + term: perfil description: La página que muestra información acerca de la actividad de un usuario. - - term: profile photo + term: foto de perfil description: >- Una imagen personalizada que los usuarios suben a GitHub para identificar su actividad, generalmente junto con su nombre de usuario. También se lo conoce como un avatar. - - term: project board + term: tablero de proyecto description: >- Los tableros dentro de GitHub que están hechos de propuestas, solicitudes de extracción y notas que son categorizados como tarjetas en columnas. - - term: protected branch + term: rama protegida description: >- Las ramas protegidas bloquean varias funciones de Git en una rama la cual un administrador de repositorio elige proteger. No pueden tener un empuje forzado, ni ser eliminadas, ni fusionarles cambios sin la aprobación de controles requerida ni las revisiones aprobadas requeridas ni cargarle archivos a esta desde la interfaz web de GitHub. Una rama protegida generalmente es la rama por defecto. - - term: public contributions + term: contribuciones públicas description: Contribuciones hechas a un repositorio público (vs. privado). - - term: public repository + term: repositorio público description: >- Un repositorio público puede ser visto por cualquiera, incluso por personas que no son usuarios de GitHub. - - term: pull + term: extraer description: >- Extraer se refiere a cuando se recuperan cambios y se fusionan. Por ejemplo, si alguien ha editado el archivo remoto en el que ambos están trabajando, querrás extraer esos cambios para tu copia local para que esté actualizado. También consulta recuperar. - - term: pull access + term: acceso de lectura description: Un sinónimo para acceso de lectura. - term: solicitud de cambios description: >- Las solicitudes de extracción son cambios propuestos para un repositorio enviado por un usuario y aceptado o rechazado por los colaboradores de un repositorio. Como las propuestas, las solicitudes de extracción tienen sus propios foros de debate. - - term: pull request review + term: revisión de solicitud de cambios description: >- Los comentarios de los colaboradores en una solicitud de extracción que aprueban los cambios o solicitan otros cambios antes de fusionar la solicitud de extracción. - - term: Pulse graph + term: Gráfico de pulso description: Un gráfico del repositorio que te brinda una descripción de la actividad de un repositorio. - - term: Punch graph + term: Gráfico de perforado description: >- Un gráfico del repositorio que muestra la frecuencia de las actualizaciones para un repositorio en función del día de la semana y la hora del día. - - term: push + term: subir description: >- Subir significa enviar tus cambios confirmados a un repositorio remoto en GitHub.com. Por ejemplo, si cambias algo de forma local, puedes subir esos cambios para que otros puedan acceder a ellos. - @@ -558,10 +558,10 @@ description: >- Cuando subes una rama a un repositorio remoto, actualizas la rama remota con cambios de tu rama local. Cuando "subes una rama", Git buscará el HEAD ref en el repositorio remoto y verificará que sea un ancestro directo de el HEAD ref local de la rama. Una vez que se verifique, Git extrae todos los objetos (alcanzables desde el HEAD ref local y que no estén en el repositorio remoto) en la base de datos de objetos remotos y después actualiza el HEAD ref remoto. Si el HEAD remoto no es un ancestro del HEAD local, la subida fallará. - - term: push access + term: acceso de escritura description: Un sinónimo para acceso de escritura. - - term: read access + term: acceso de lectura description: >- Un nivel de permiso en un repositorio que permite al usuario extraer o leer información desde el repositorio. Todos los repositorios públicos otorgan acceso de lectura a todos los usuarios de GitHub. Un sinónimo para acceso de lectura. - @@ -572,29 +572,29 @@ description: >- Volver a aplicar una serie de cambios de una rama a una base diferente y restablecer el HEAD de esa rama al resultado. - - term: Recover Accounts Elsewhere + term: Recuperar cuentas en otro lugar description: >- Le permite a los usuarios agregar un factor de seguridad extra a su cuenta de GitHub en caso de que pierdan acceso a su método de autenticación de dos factores o a sus códigos de recuperación. Los usuarios pueden asociar su cuenta de GitHub con su cuenta de Facebook almacenando una credencial de autenticación en forma de token de recuperación de cuenta para su cuenta de GitHub con Facebook. - - term: recovery code + term: código de recuperación description: Un código que te ayuda a volver a tener acceso a tu cuenta de GitHub. - - term: release + term: lanzamiento description: El modo que tiene GitHub de empaquetar y proporcionar el software a tus usuarios. - - term: remote + term: remoto description: >- Esta es la versión de un repositorio o rama que está alojada en un servidor, probablemente GitHub.com. Las versiones remotas se pueden conectar a clones locales para poder sincronizar los cambios. - - term: remote repository + term: repositorio remoto description: >- Un repositorio que se usa para hacer un seguimiento del mismo proyecto, pero reside en otro lugar. - - term: remote URL + term: URL remota description: >- El lugar donde se almacena tu código: un repositorio en GitHub, la bifurcación de otro usuario o incluso un servidor diferente. - - term: replica + term: réplica description: >- Una instancia de GitHub Enterprise que ofrece redundancia para la instancia principal de GitHub Enterprise. - @@ -602,81 +602,81 @@ description: >- Un repositorio es el elemento más básico de GitHub. Son más fáciles de imaginar como la carpeta de un proyecto. Un repositorio contiene todos los archivos del proyecto (incluida la documentación) y almacena el historial de revisión de cada archivo. Los repositorios pueden tener varios colaboradores y pueden ser públicos o privados. - - term: repository graph + term: gráfico del repositorio description: Una representación visual de los datos de tu repositorio. - - term: repository maintainer + term: mantenedor del repositorio description: >- Alguien que administra un repositorio. Esta persona puede ayudar a evaluar prioridades de las propuestas y usar etiquetas y otras funciones para administrar el funcionamiento del repositorio. Esta persona también puede ser responsable de mantener los archivos README y de contribución actualizados. - - term: required pull request review + term: revisión de solicitud de extracción requerida description: >- Las revisiones requeridas garantizan que las solicitudes de extracción tengan, al menos, una revisión aprobada antes de que los colaboradores puedan realizar cambios en una rama protegida. - - term: required status check + term: verificación de estado requerida description: >- Verificaciones de las solicitudes de extracción que 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. - - term: resolve + term: resolver description: La acción de solucionar de forma manual lo que dejó una fusión automática fallida. - - term: revert + term: revertir description: >- Cuando reviertes una solicitud de extracción en GitHub, automáticamente se abre una solicitud de extracción nueva, que tiene una confirmación de cambios que revierte la confirmación de fusión de la solicitud de extracción original fusionada. En Git, puedes revertir las confirmaciones de cambio con `revertir git`. - - term: review + term: revisar description: >- Las revisiones le permiten a otros con acceso a tu repositorio comentar los cambios propuestos en las solicitudes de extracción, aprobar los cambios o solicitar más cambios antes de que se fusione la solicitud de extracción. - - term: root directory + term: directorio raíz description: El primer directorio en jerarquía. - - term: root filesystem + term: sistema de archivos raíz description: El sistema operativo base y el entorno de la aplicación GitHub Enterprise. - - term: saved reply + term: respuesta guardada description: >- Un comentario que puedes guardar y agregar a tu cuenta de usuario de GitHub para que puedas usar en GitHub en las propuestas y en las solicitudes de extracción. - - term: scope + term: alcance description: >- Grupos de permisos con nombre que una App OAuth puede solicitar para acceder tanto a los datos públicos como los no públicos. - - term: seat + term: plaza description: >- Un usuario dentro de la organización de GitHub Enterprise. Se lo puede conocer como "cómputo de asientos". - - term: secret team + term: equipo secreto description: >- Un equipo que solo es visible para otras personas del equipo y personas con premisos de propietario. - - term: security log + term: bitácora de seguridad description: >- Un registro que enumera las últimas 50 acciones o las realizadas dentro de los últimos 90 días. - - term: service hook + term: gancho de servicio description: >- También llamado "webhook". Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. - - term: single sign-on + term: inicio de sesión único description: >- También llamado SSO. Le permite a los usuarios iniciar sesión en una única ubicación - un proveedor de identidad (IdP)- que luego le da acceso al usuario a otros proveedores de servicios. - - term: snapshot + term: captura de pantalla description: Un punto de control de una máquina virtual a partir de un momento específico. - - term: squash + term: combinar description: Combinar varias confirmaciones de cambios en una única confirmación. También un comando Git. - term: Llave SSH description: >- Las claves SSH son una manera de identificarte a ti mismo en un servidor en línea, usando un mensaje cifrado. Es como si tu computadora tuviera su propia contraseña única para otro servicio. {% data variables.product.product_name %} utiliza claves SSH para transferir información de forma segura a tu computadora. - - term: staging instance + term: instancia de preparación description: >- Un modo de evaluar modificaciones antes de que sean aplicadas a tu instancia actual de GitHub Enterprise. - - term: status + term: estado description: >- Una representación visual dentro de una solicitud de extracción de que tus confirmaciones cumplen las condiciones establecidas para el repositorio con el que estás contribuyendo. - @@ -684,70 +684,70 @@ description: >- Las verificaciones de estado son procesos externos, como compilaciones de integración continua, que se ejecutan para cada confirmación que realices en un repositorio. Para obtener más información, consulta "[acerca de las verificaciones de Estado] (/articles/about-status-checks)." - - term: star + term: estrella description: >- Un marcador o una muestra de reconocimiento para un repositorio. Las estrellas son un modo manual de clasificar la popularidad de los proyectos. - - term: subscription + term: suscripción description: Un plan GitHub de un usuario o una organización. - - term: team + term: equipo description: >- Un grupo de miembros de una organización que refleja la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. - - term: team maintainer + term: mantenedor del equipo description: >- Miembros de la organización que tienen un subconjunto de permisos disponibles para los propietarios de la organización para administrar equipos. - - term: Team plan + term: Plan de equipo description: >- El plan de facturación de una organización que te da repositorios públicos y privados ilimitados. - - term: timeline + term: cronología description: Una serie de eventos en una solicitud de extracción o en el perfil de un usuario. - - term: topic branch + term: rama de tema description: >- Una rama Git normal que usa un programador para identificar una línea conceptual de desarrollo. Como las ramas son muy fáciles de usar y económicas, suele ser conveniente tener varias ramas pequeñas y que cada una contenga conceptos muy bien definidos o cambios pequeños incrementales pero relacionados. También se puede denominar rama de característica. - - term: topics + term: temas description: >- Un modo de explorar repositorios en una área temática en particular, encontrar proyectos a los cuales contribuir y descubrir nuevas soluciones para un problema específico en GitHub. - - term: Traffic graph + term: Gráfico de tráfico description: >- Un gráfico del repositorio que muestra el tráfico de un repositorio, incluso clones completos (no recuperaciones), los visitantes de los últimos 14 días, sitios de referencia y contenido popular. - - term: transfer + term: transferencia description: >- Transferir un repositorio significa cambiar el propietario de un repositorio. El nuevo propietario podrá administrar de inmediato los contenidos, las propuestas, las solicitudes de extracción, los lanzamientos y los parámetros del repositorio. - - term: upstream + term: ascendente description: >- Cuando se habla de una rama o una bifurcación, la rama principal en el repositorio original suele conocerse como "ascendente", ya que es el lugar principal desde donde vendrán otros cambios. La rama/bifurcación en la que estás trabajando entonces se llama "descendente ". También llamada origen. - - term: upstream branch + term: rama ascendente description: >- La rama por defecto que se fusiona en la rama en cuestión (o la rama en cuestión en la que es rebasada). Se configura mediante `branch..remote` y `branch..merge`. Si la rama ascendente de A es la origen/B, a veces, decimos "A hace un seguimiento de la origen/B". - - term: user + term: usuario description: >- Los usuarios son personas con cuentas personales de GitHub. Cada usuario tiene un perfil personal y puede poseer varios repositorios, públicos o privados. Pueden crear o ser invitados a unirse a organizaciones o colaborar con el repositorio de otro usuario. - - term: username + term: nombre de usuario description: El identificador de un usuario en GitHub. - - term: visible team + term: equipo visible description: Un equipo que puede ser visto y @mencionado por cada miembro de la organización. - - term: watch + term: observar description: >- Puedes ver un repositorio o una propuesta para recibir notificaciones cuando se realizan actualizaciones a una propuesta o una solicitud de extracción. - - term: watching notifications + term: ver notificaciones description: Una notificación acerca de la actividad en un repositorio al que se ha subscripto un usuario. - - term: web notifications + term: notificaciones web description: >- Las notificaciones que se muestran en la interfaz web en GitHub: https://github.com/notifications - @@ -755,9 +755,9 @@ description: >- Los webhooks te permiten generar o configurar Apps GitHub que se suscriben a ciertos eventos en GitHub.com. Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. También llamado gancho de servicio. - - term: Works with GitHub + term: Compatible con GitHub description: Un listado de integraciones que son compatibles con GitHub. - - term: write access + term: acceso de escritura description: >- Un nivel de permiso en un repositorio que le permite al usuario subir o escribir cambios para un repositorio. diff --git a/translations/es-ES/data/glossaries/internal.yml b/translations/es-ES/data/glossaries/internal.yml index 2653ed0dd8..e6b3d761ca 100644 --- a/translations/es-ES/data/glossaries/internal.yml +++ b/translations/es-ES/data/glossaries/internal.yml @@ -3,7 +3,7 @@ term: 2-up description: El modo predeterminado de ver imágenes en GitHub. - - term: alternate object database + term: base de datos de objetos alterna description: >- A través de mecanismos alternativos, un repositorio puede heredar parte de su base de datos de objetos de otra base de datos de objetos, que se denomina "alternativa". - @@ -11,18 +11,18 @@ description: >- Imagen de máquina de Amazon. Un aparato virtual para usar con la Amazon Elastic Compute Cloud. - - term: anonymized image URL + term: URL de imagen anonimizada description: >- Un proxy URL anónimo para cada imagen que oculta los detalles del navegador y la información relacionada de otros usuarios. - - term: apex domain + term: dominio apex description: Un dominio de raíz que no contiene una parte de subdominio. - term: API description: >- Interfaz de programación de la aplicación. Un conjunto de métodos de comunicación claramente definidos entre varios componentes de software. - - term: API token + term: Token de la API description: >- Un token que se usa en lugar de una contraseña en scripts y en la línea de comando. - @@ -30,24 +30,24 @@ description: >- Servicio de terceros que se integra con GitHub. Por lo general, esto se refiere a las aplicaciones OAuth o a las Apps GitHub. También se las conoce como app. - - term: application + term: aplicación description: >- Servicio de terceros que se integra con GitHub. Por lo general, esto se refiere a las aplicaciones OAuth o a las Apps GitHub. También se las conoce como app. - - term: argument + term: argumento description: 'En GraphQL, un conjunto de pares de clave-valor que se adjunta a un campo específico.' - term: AsciiDoc description: >- Un formato de documento de texto para escribir notas, documentación, artículos, libros, libros electrónicos, diapositivas, páginas web, páginas de manual y blogs. - - term: assets + term: activos description: 'Archivos individuales como imágenes, fotos, videos y archivos de texto.' - - term: Atom feed + term: Fuente Atom description: Un formato XML ligero que permite una fácil sindicación del contenido web. - - term: audit log + term: bitácora de auditoría description: >- En una organización, el registro de auditoría incluye detalles acerca de las actividades realizadas en la organización, como quién realizó la acción, cuál fue la acción y cuándo fue realizada. - @@ -61,14 +61,14 @@ term: Azure description: Una plataforma de informática en la nube de Microsoft. - - term: bare repository + term: repositorio en blanco description: >- Normalmente, un repositorio en blanco es un directorio con un nombre apropiado con un sufijo .git que no tiene una copia revisada localmente de ninguno de los archivos bajo control de revisión. Es decir, todos los archivos de control y administrativos Git que normalmente estarían presentes en el subdirectorio .git oculto están presentes directamente en el directorio del repositorio.git y ningún otro archivo está presente y revisado. Generalmente, quienes publican los repositorios públicos ponen a disposición los repositorios en blanco. - - term: BFG repo cleaner + term: Limpiador para repositorio BFG description: BFG. Una herramienta de terceros que limpia datos del historia de tu repositorio Git. - - term: blob object + term: objeto blob description: 'Objeto sin tipo, p. ej., los contenidos de un archivo.' - term: bot @@ -77,40 +77,40 @@ term: Bundler description: Una manera de administrar las Ruby gems de las que depende una aplicación. - - term: camo + term: camuflaje description: >- Un proxy de imagen SSL para evitar advertencias de contenido mixto en páginas seguras proporcionadas desde GitHub. - - term: chain + term: cadena description: >- Una lista de objetos, donde cada objeto en la lista contiene una referencia para su sucesor (por ejemplo, el sucesor de una confirmación de cambios podría ser uno de sus padres). - - term: CIDR notation + term: notación CIDR description: Una representación compacta de una dirección IP y su prefijo de enrutamiento asociado. - term: CLI description: Interfaz de línea de comandos. - - term: CNAME record + term: registro CNAME description: >- Registro de nombre canónico. Un tipo de registro de recursos en el Sistema de nombres de dominio (DNS) usado para especificar que el nombre de un dominio es un alias para otro dominio (el dominio 'canónico'). - - term: conditional request + term: solicitud condicional description: >- En la API REST, un método HTTP que solo se responde en ciertas circunstancias. - - term: connection + term: conexión description: 'En GraphQL, una manera de consultar objetos relacionados como parte de la misma llamada.' - - term: core Git + term: Git principal description: >- Utilidades y estructuras de datos fundamentales de Git. Expone solo herramientas de administración de código fuente limitadas. - term: CPU description: Unidad de procesamiento central. - - term: credential helper - description: A program that stores and fetches Git credentials. + term: ayudante de credenciales + description: Un programa que almacena y extrae credenciales Git. - term: creole description: >- @@ -123,11 +123,11 @@ description: >- Gráfico acíclico dirigido. Los objetos de confirmación de cambios forman un gráfico acíclico dirigido, porque tienen padres (dirigidos) y el gráfico de objetos de confirmación de cambios es acíclico (no hay cadena que comience y termine con el mismo objeto). - - term: dangling object + term: objeto inalcanzable description: >- Un objeto inaccesible que no es accesible incluso desde otros objetos inaccesibles; un objeto inalcanzable no tiene referencias a él desde ninguna referencia ni objeto en el repositorio. - - term: data pack + term: paquete de datos description: >- Paquete de ancho de banda y de almancenamiento que los usuarios pueden comprar. Cada paquete de datos ofrece 50 GB de ancho de banda y 50 GB para almacenamiento. - @@ -138,28 +138,28 @@ description: >- Protocolo de configuración dinámica de host (DHCP). Un servidor de cliente/protocolo que proporciona automáticamente un host de protocolo de Internet con su dirección IP y otra información de configuración relacionada, como la máscara de subred y la puerta de enlace predeterminada. - - term: directive + term: directiva description: >- En GraphQL, un modo de afectar la ejecución de una consulta de la manera que el servidor lo desee. - - term: directory + term: directorio description: La lista que obtienes con el comando "ls". - - term: disaster recovery + term: recuperación de desastres description: >- También conocido como DR. Herramientas y procesos que recuperan los sistemas y la infraestructura tecnológica después de una catástrofe natural o de origen humano. - - term: DNS provider + term: proveedor DNS description: >- Una empresa que le permite a los usuarios comprar y registrar un nombre de dominio único y conectar ese nombre a una dirección IP (Protocolo de Internet) indicando tu nombre de dominio a una dirección IP o a un nombre de dominio diferente. - term: DSA description: Algoritmo de firma digital. Un estándar de procesamiento para las firmas digitales. - - term: DSA key + term: llave DSA description: Claves públicas y privadas usadas en DSA. - - term: Early Access Program + term: Programa de acceso temprano description: >- Un programa de GitHub al que ingresan individuos y organizaciones para recibir funciones prelanzadas. - @@ -171,7 +171,7 @@ description: >- Amazon Elastic Compute Cloud. Un servicio web que ofrece capacidad de cálculo redimensionable y segura en la nube. - - term: edge + term: borde description: 'En GraphQL, las conexiones entre nodos.' - term: EIP @@ -180,11 +180,11 @@ term: ElasticSearch description: Un motor de búsqueda basado en Lucene. - - term: evil merge + term: fusión maliciosa description: >- Un unión maliciosa es una fusión que introduce cambios que no aparecen en ningún padre. - - term: exclude + term: excluir description: >- Una vez que una ruta coincide con cualquier pathspec no excluido, será ejecutada a través de todo pathspec excluido (firma especial: ! o su sinónimo ^). Si coincide, la ruta se ignora. Si no hay pathspec no excluido, la exclusión se aplica al resultado establecido como invocado sin ningún pathspec. - @@ -192,23 +192,23 @@ description: >- Un estándar de autenticación abierta que refuerza y simplifica la autenticación de dos factores usando dispositivos NFC y USB especializados basado en una tecnología de seguridad similar encontrada en las tarjetas inteligentes. - - term: field + term: campo description: 'En GraphQL, una unidad de datos que puedes recuperar de un objeto.' - - term: file system + term: sistema de archivos description: >- Linus Torvalds originalmente diseñó Git para ser un sistema de archivos de espacio para usuarios, es decir, la infraestructura para mantener archivos y directorios. Esto garantizó la eficacia y la velocidad de Git. - - term: flame war + term: discusión encendida description: Un debate fuerte y agresivo en línea entre usuarios. - - term: fragment + term: fragmento description: 'En GraphQL, unidades reusables que te permiten crear conjuntos de campos.' - term: GCE description: Google Compute Engine. - - term: gem + term: gema description: Una herramienta de línea de comandos que puede instalar bibliotecas y administrar RubyGems. - term: Gemfile @@ -220,70 +220,70 @@ term: geoJSON description: Un formato para codificar una variedad de estructuras de datos geográficos. - - term: GitHub Marketplace Developer Agreement + term: Acuerdo de Desarrollador de GitHub Marketplace description: Un acuerdo que firman los usuarios cuando usan Mercado GitHub. - term: GPG description: >- GNU Privacy Guard. Software de cifrado que puedes usar para cifrar (y descifrar) archivos que contengan datos confidenciales. - - term: GPG key + term: llave GPG description: Una clave de cifrado usada con GPG. - term: hash description: Sinónimo para nombre del objeto. - - term: head + term: encabezado description: >- Una referencia con nombre para la confirmación de cambios en el extremo de una rama. Los encabezados se almacenan en un archivo en el directorio $GIT_DIR/refs/heads/, excepto cuando usan refs empaquetados. - term: HEAD description: Un tipo de método en la API REST. - - term: headers + term: encabezados description: >- En la API REST, un componente del mensaje requerido que define los metadatos de la tranasacción. - - term: health check + term: revisión de estado description: >- Un modo de permitir un balanceador de carga para detener el tráfico que se envía a un nodo que no está respondiendo si falla una revisión configurada previamente en ese nodo. - - term: HTTP verb + term: verbo HTTP description: Un método HTTP. - term: Hyper-V description: >- Un producto de Microsoft que crea máquinas virtuales en sistemas x86-64 con Windows. - - term: hypermedia + term: hipermedios description: 'En la API REST, enlaces desde un estado de recurso a otro.' - term: icase description: Coincidencia que no distingue mayúsculas de minúsculas. - - term: implementation + term: implementación description: 'En GraphQL, cómo un objeto hereda de una interfaz.' - - term: index + term: índice description: >- Un conjunto de archivos con información estadística, cuyos contenidos se almacenan como objetos. El índice es una versión almacenada de tu árbol de trabajo. A decir verdad, también puede contener una segunda, e incluso una tercer versión de un árbol de trabajo, que se usan cuando se fusiona. - - term: index entry + term: entrada de índice description: >- La información respecto a un archivo en particular, almacenada en el índice. Una entrada de índice puede ser no configurada, si se inició una fusión, pero aún no se finalizó (es decir, si el índice contiene varias versiones de ese archivo). - - term: introspection + term: introspección description: >- También se la conoce como "introspectiva". Un modo de solicitar al esquema GraphQL información acerca de las consultas que admite. - - term: iPython notebook + term: notebook iPython description: >- Una aplicación basada en la web que captura todo el proceso de cálculo: desarrollo, documentación y código de ejecución, así como también comunica los resultados. - term: JIRA description: Un producto de Atlassian que hace un seguimiento de las propuestas. - - term: Jupyter notebook + term: notebook Jupyter description: Notebook que contiene tanto elementos de texto enriquecido como de código. - term: kernel @@ -295,17 +295,17 @@ term: LDAP description: Protocolo ligero de acceso a directorios. - - term: linter + term: limpiador description: Un programa que verifica la calidad del código. - term: Liquid description: Un lenguaje de plantillas que se usa para cargar contenido dinámico. - - term: load balancer + term: balanceador de carga description: >- Un dispositivo que actúa como un proxy inverso y distribuye tráfico de aplicación o de red a través de una cantidad de servidores. - - term: media type + term: tipo de medios description: Un identificador de dos partes para los formatos de archivo y los contenidos de formato. - term: MediaWiki @@ -315,18 +315,18 @@ term: Mercurial description: 'Una herramienta de administración de control de código fuente con distribución y gratuita.' - - term: metadata + term: metadatos description: Un conjunto de datos que describen y brindan información acerca de otros datos. - - term: MIME-type + term: de tipo MIME description: >- Extensiones de correo de Internet multipropósitos. Una manera de identificar archivos según su naturaleza y formato. - - term: mutations + term: mutaciones description: >- En GraphQL, una manera de definir las operaciones GraphQL que modifican datos en el servidor. - - term: nameserver + term: servidor de nombres description: >- Un servidor en Internet especializado en manejar consultas respecto a la ubicación de varios servicios de un nombre de dominio. - @@ -334,76 +334,76 @@ description: >- Transmisión de datos en proximidad. Un conjunto de protocolos de comunicación que le permite a dos dispositivos electrónicos, uno de los cuales generalmente es un dispositivo portátil como un smartphone, establecer comunicación llevándolos dentro de un cierto rango uno de otro. - - term: node + term: nodo description: >- Un dispositivo electrónico activo que se conecta a una red y es capaz de crear, recibir o transmitir información en un canal de comunicaciones. - - term: node + term: nodo description: 'En GraphQL, un término genérico para un objeto.' - term: NTP description: Protocolo de tiempo de la red. - - term: object + term: objeto description: >- La unidad de almacenamiento en Git. Se identifica de forma unívoca mediante el SHA-1 de sus contenidos. Por consiguiente, un objeto no se puede modificar. - - term: object database + term: base de datos de objetos description: >- Almacena un conjunto de "objetos" y el nombre del objeto identifica un objeto individual. Los objetos generalmente viven en $GIT_DIR/objects/. - - term: object identifier + term: identificador de objeto description: Sinónimo para nombre del objeto. - - term: object name + term: nombre del objeto description: >- El identificador único de un objeto. El nombre del objeto generalmente se representa con una cadena hexadecimal de 40 caracteres. Coloquialmente también se lo llama SHA-1. - - term: object type + term: tipo de objeto description: >- Uno de los identificadores "confirmación de cambios", "árbol", "etiqueta" o "blob" que describe el tipo de un objeto. - - term: octopus + term: fusión múltiple description: Fusionar más de dos ramas. - - term: onion skin + term: visualizar por transparencia description: >- Una manera de ver imágenes en GitHub disminuyendo la opacidad de una imagen de reemplazo superpuesta. - term: OOM description: Sin memoria. - - term: Open Stack + term: Plataforma abierta description: Una plataforma de software para informática en la nube. - term: OpenSSH description: >- Un conjunto de utilidades a nivel de red relacionado con la seguridad basado en el protocolo Secure Shell (SSH). - - term: ordered list + term: lista ordenada description: Una lista enumerada. - term: Org description: >- Un sistema de texto simple para mantener las notas, mantener las listas TODO, planificar proyectos y autorizar documentos. - - term: pack + term: paquete description: >- Un conjunto de objetos que han sido comprimidos en un archivo (para ahorrar espacio o para transmitirlos de forma eficiente). - - term: pack index + term: índice del paquete description: >- La lista de identificadores, y otra información, de los objetos en un paquete, para ayudar a acceder de forma eficiente a los contenidos de un paquete. Los pathspec se usan en la línea de comandos de "git ls-files", "git ls-tree", "git add", "git grep", "git diff", "git checkout", y muchos otros comandos para limitar el alcance de las operaciones para algún subconjunto del árbol o del árbol de trabajo. - - term: parameter + term: parámetro description: >- En la API REST, datos que son enviados en la solicitud o recibidos en la respuesta como parte de un parámetro de entrada o salida. - - term: parent + term: padre description: >- Un objeto de confirmación de cambios contiene una lista (posiblemente vacía) de el/los predecesor/es lógico/s en la línea de desarrollo, es decir, sus padres. - - term: passphrase + term: frase de ingreso description: >- Una secuencia de palabras u otro texto usado para controlar el acceso a un sistema del equipo, programa o datos. - @@ -416,7 +416,7 @@ term: PEM description: Correo con privacidad mejorada - - term: persistent identifier + term: identificador persistente description: >- También conocidos como identificadores de objetos digitales (DOI). Cadenas de caracteres y/o números únicos a nivel global que hacen referencia a un objeto digital. Los identificadores persistentes pueden ser prácticos ya que le permiten a un usuario acceder al recurso digital mediante un enlace persistente. - @@ -430,28 +430,28 @@ term: Pod description: Documentación antigua simple. Un lenguaje mark-up usado por los programadores perl. - - term: pointer file + term: archivo puntero description: Una referencia que apunta a un archivo real. - - term: port + term: puerto description: Un punto final de comunicación en un sistema operativo. - - term: priority question + term: pregunta prioritaria description: >- Preguntas para el soporte técnico de GitHub de organizaciones en el Plan Business. Las preguntas deben cumplir con los criterios establecidos por GitHub para calificar como una pregunta prioritaria. - - term: priority response + term: respuesta prioritaria description: >- Respuestas del soporte técnico de GitHub para las preguntas prioritarias de organizaciones en el Plan Business. - - term: polling + term: sondeo description: >- Controles automáticos regulares de otros programas o dispositivos hechos por un programa o dispositivo para ver en qué estado están. - term: POST description: Un tipo de método en la API REST. - - term: Pre-release Program + term: Programa de prelanzamiento description: >- Un programa de GitHub que le permite a los usuarios aplicar nuevas funciones y funcionalidad antes de ser lanzados oficialmente. - @@ -461,20 +461,20 @@ term: QCOW2 description: Un formato de imagen. - - term: QR code + term: código QR description: >- Código de respuesta rápida. Un código de barras es la etiqueta óptica de lectura mecánica que contiene información acerca del elemento al que está conectado. - - term: queries + term: consultas description: 'En GraphQL, una manera de preguntar por campos específico en los objetos.' - - term: rate limit + term: límite de tasa description: El proceso por el cual una API rechaza solicitudes. - term: RDoc description: Un generador de documentación incrustada para el lenguaje de programación Ruby. - - term: reachable + term: accesible description: >- Se dice que todos los ancestros de una confirmación de cambios dada son "accesibles" desde esa confirmación. En términos más generales, un objeto es accesible desde otro si podemos alcanzarlos de unos a otros mediante una cadena que sigue etiquetas para lo que sea que etiqueten, confirmaciones de cambios a sus padres o árboles, y árboles a los árboles o blobs que contengan. - @@ -489,33 +489,33 @@ description: >- Un "refspec" es usado por recuperar y subir para describir la asignación entre ref remoto y ref local. - - term: relative link + term: enlace relativo description: Un enlace que es relativo para el archivo actual. - - term: remote-tracking branch + term: rama de seguimiento remoto description: Un ref que se usa para seguir los cambios desde otro repositorio. - - term: REST API + term: API de REST description: >- Una API que define un conjunto de funciones para que los programadores puedan realizar solicitudes y recibir respuestas mediante HTTP. - - term: reStructured text + term: texto reestructurado description: Un sistema analizador y de sintaxis Markup de texto simple Lo que ves es lo que obtienes. - - term: revision + term: revisión description: Sinónimo para confirmación de cambios. - - term: rewind + term: retroceder description: >- Descartar parte del desarrollo, es decir, asignar el encabezado a una revisión anterior. - - term: root endpoint + term: terminal raíz description: 'En la API REST, el directorio en los que todos los puntos finales están debajo.' - term: RSA description: Algoritmo usado para cifrar los datos de usuario usando una clave pública y una clave privada. - - term: RSA key + term: llave RSA description: Una clave privada basada en el algoritmo RSA. - term: SAML @@ -528,7 +528,7 @@ term: Sass description: Un lenguaje de extensión CSS. - - term: schema + term: modelo description: Metadatos que nos dicen cómo están estructurados nuestros datos. - term: SCIM @@ -541,7 +541,7 @@ term: SCSS description: Un lenguaje de extensión CSS. - - term: service account + term: cuenta de servicio description: >- Una cuenta de usuario especial que una aplicación o servicio usa para interactuar con el sistema operativo. - @@ -552,7 +552,7 @@ term: shell description: Una interfaz de usuarios para acceder a los servicios de un sistema operativo. - - term: shallow repository + term: repositorio superficial description: >- Un repositorio superficial tiene un historial incompleto y algunas de sus confirmaciones de cambios tienen padres cauterizados aparte (en otras palabras, se le pide a Git que haga como si esas confirmaciones no tuvieran padres, aunque se graban en el objeto de la confirmación). Esto, a veces, es útil cuando solo te interesa el historial reciente de un proyecto aunque el historial real grabado en el ascendente sea mucho más grande. Un repositorio superficial se crea dando la --opción de profundidad para git-clone(1) y su historial puede ser profundizado más tarde con git-fetch(1). - @@ -575,62 +575,62 @@ description: >- Secure Shell (SSH) es un protocolo de red criptográfico para operar servicios de red de forma segura en una red no segura. - - term: ssh-agent + term: agente ssh description: Un programa para retener claves privadas usadas para la autenticación de claves públicas. - - term: SSH Key + term: Llave SSH description: >- Las claves SSH son una manera de identificarte en un servidor en línea, usando un mensaje cifrado. Es como si tu equipo tuviera su propia contraseña única para otro servicio. GitHub usa las claves SSH para transferir información de forma segura desde GitHub.com a tu equipo. - - term: SSH key fingerprint + term: huella digital de la llave SSH description: >- Identifica y verifica el host al que te estás conectando y está basada en la clave pública del host. - term: SSL description: Capa de sockets seguros. - - term: static site generator + term: generador de sitio estático description: >- Un programa que genera un sitio web solo HTML usando datos sin procesar (como archivos Markdown) y plantillas. - - term: String + term: Secuencia description: Un tipo de objeto que denota texto simple. - - term: STL file + term: archivo STL description: >- STL (STereoLithography) es un formato de archivo nativo para el software CAD de estereolitografía creado por los sistemas 3D. - - term: subdomain + term: subdominio description: >- Una parte personalizable y opcional del nombre de un dominio ubicada antes de la raíz o del dominio apex que se ve como el prefijo de un dominio. - - term: submodule + term: submódulo description: >- Un repositorio que contiene el historial de un proyecto independiente dentro de otro repositorio (este último se denomina superproyecto). - - term: subproject + term: subproyecto description: >- Un proyecto que se desarrolla y se administra fuera de tu proyecto principal. - term: Subversion description: Un sistema de control de versión de código abierto. - - term: sudo mode + term: modo sudo description: >- Una manera en que los usuarios ejecutan programas con los privilegios de seguridad de otro usuario. Los usuarios proporcionan su propia contraseña y son autenticados. - - term: superproject + term: superproyecto description: >- Un repositorio que hace referencia a repositorios de otros proyectos en su árbol de trabajo como submódulos. El superproyecto conoce los nombres de (pero no guarda copias de) los objetos de confirmación de cambios de los submódulos contenidos. - - term: support bundle + term: paquete de soporte description: >- Un archivo tar comprimido en gzip que contiene registros importantes de tu instancia de GitHub Enterprise. - - term: swipe + term: deslizar description: Una manera de ver porciones de tu imagen de GitHub de lado a lado. - - term: symlink + term: enlace simbólico description: >- Un archivo que contiene una referencia a otro archivo o directorio en la forma de una ruta absoluta o relativa y que afecta la resolución del nombre de ruta. - @@ -638,11 +638,11 @@ description: >- Referencia simbólica: en lugar de contener el propio id SAH-1, es del formato ref: refs/some/thing y cuando se le hace referencia, recurrentemente se desreferencia de esta referencia. - - term: tag + term: etiqueta description: >- Una ref en el espacio de nombres refs/tags/ que apunta a un objeto de un tipo arbitrario (generalmente, una etiqueta apunta ya sea a una etiqueta o a un objeto de confirmación de cambios). Una etiqueta se usa principalmente para marcar un punto en particular en la cadena de ascendencia de la confirmación. - - term: tag object + term: objeto de etiqueta description: >- Un objeto que contiene una ref apuntando a otro objeto, que puede contener un mensaje como un objeto de confirmación de cambios. También puede contener una firma (PGP), en cuyo caso se llama un "objeto de etiqueta firmado". - @@ -664,35 +664,35 @@ term: topoJSON description: Una extensión de GeoJSON que codifica topología. - - term: TOTP application + term: aplicación TOTP description: >- Contraseña de un solo uso y duración definida. Este tipo de aplicación genera automáticamente un código de autenticación que cambia después de cierto período de tiempo. - - term: tree + term: árbol description: >- Ya sea un árbol de trabajo o un objeto de árbol junto con el blob dependiente y objetos de árbol (es decir, una representación almacenada de un árbol de trabajo). - - term: tree object + term: objeto de árbol description: >- Un objeto que contiene una lista de nombres de archivo y modos, junto con refs para el blob o los objetos de árbol asociados. Un árbol es equivalente a un directorio. - term: TSV description: Archivos separados por tabulaciones. - - term: two-factor authentication + term: autenticación bifactorial description: >- También denominada 2FA. Una capa extra de seguridad que no solo requiere de un procedimiento de inicio de sesión estándar con nombre de usuario y contraseña, si no que también de un código de autenticación que es generado por una aplicación en el smartphone del usuario o enviado como un mensaje de texto (SMS). - term: UFW description: Herramienta de configuración de firewall predeterminada de Ubuntu. - - term: unmerged index + term: índice sin fusionar description: Un índice que contiene entradas de índice no configuradas. - - term: unordered list + term: lista desordenada description: Un lista con viñetas. - - term: unreachable object + term: objeto inaccesible description: 'Un objeto que no es accesible desde una rama, etiqueta ni ninguna otra referencia.' - term: URI @@ -705,14 +705,14 @@ term: variable description: 'En GraphQL, una manera de realizar consultas más dinámicas y eficaces.' - - term: VAT ID + term: ID de impuestos description: Un número de identificación del impuesto al valor agregado para fines impositivos en la UE. - - term: verified email address + term: dirección de correo electrónico verificada description: >- Una dirección de correo electrónico asociado a una cuenta personal que el usuario ha verificado que es válida con un proceso de confirmación de seguridad. - - term: virtual machine + term: máquina virtual description: >- Un entorno de aplicación que se instala en software e imita al hardware dedicado. También llamado una VM. - @@ -730,16 +730,16 @@ description: >- Una lista o registro de entidades a las que se les brinda un reconocimiento, acceso, movilidad, servicio o privilegio en particular. Las entidades en la lista serán aceptadas, aprobadas o reconocidas. - - term: working directory + term: directorio de trabajo description: El directorio de archivos en el que estás trabajando actualmente. - - term: working tree + term: árbol de trabajo description: >- El árbol de archivos revisados reales. El árbol de trabajo generalmente contiene los contenidos del árbol de la confirmación de cambios del HEAD, además de cualquier cambio local que hayas realizado pero aún no confirmado. - term: WYSIWYG description: >- - What You See Is What You Get. An acronym meaning the text on the screen looks exactly as it will when it's rendered. + Lo que ves es lo que obtienes. Unas siglas que significan que el texto en pantalla se ve exactamente como será cuando sea procesado. - term: XenServer description: Una plataforma de virtualización. @@ -748,8 +748,8 @@ description: >- Un lenguaje de serialización de datos natural que comúnmente se usa para archivos de configuración. - - term: Continuous Integration + term: Integración continua description: También abreviada como CI. - - term: Continuous Delivery + term: Entrega continua description: También abreviada como CD. diff --git a/translations/es-ES/data/learning-tracks/README.md b/translations/es-ES/data/learning-tracks/README.md new file mode 100644 index 0000000000..ec0f70309e --- /dev/null +++ b/translations/es-ES/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Learning Tracks (aka Learning Paths) + +Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. \ No newline at end of file diff --git a/translations/es-ES/data/learning-tracks/actions.yml b/translations/es-ES/data/learning-tracks/actions.yml index ead26c879a..69c1fc1d11 100644 --- a/translations/es-ES/data/learning-tracks/actions.yml +++ b/translations/es-ES/data/learning-tracks/actions.yml @@ -1,7 +1,7 @@ --- getting_started: title: 'Inicia con {% data variables.product.prodname_actions %}' - description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + description: 'Descubre las posibilidades de las {% data variables.product.prodname_actions %} creando tu primer flujo de trabajo.' guides: - /actions/learn-github-actions/introduction-to-github-actions - /actions/learn-github-actions/finding-and-customizing-actions @@ -9,8 +9,8 @@ getting_started: - /actions/learn-github-actions/managing-complex-workflows - /actions/learn-github-actions/security-hardening-for-github-actions continuous_integration: - title: 'Build and test code' - description: 'You can create custom continuous integration (CI) workflows right in your repository.' + title: 'Crea y prueba tu código' + description: 'Puedes crear flujos de trabajo de integración contínua (IC) justo en tu repositorio.' guides: - /actions/guides/about-continuous-integration - /actions/guides/setting-up-continuous-integration-using-workflow-templates @@ -23,16 +23,23 @@ continuous_integration: - /actions/guides/building-and-testing-java-with-gradle - /actions/guides/building-and-testing-java-with-ant continuous_deployment: - title: 'Automate your deployments' - description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + title: 'Automatiza tus despliegues' + description: 'Aprende cómo automatizar la publicación de lanzamientos de tus proyectos con un flujo de trabajo de integración contínua (IC) personalizado en {% data variables.product.prodname_actions %}.' guides: - /actions/guides/about-packaging-with-github-actions - /actions/guides/publishing-nodejs-packages - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Desplegar en la red' + description: 'Aprende a utilizar las {% data variables.product.prodname_actions %} para crear una aplicación y desplegarla en diversas plataformas basadas en la nube.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine hosting_your_own_runners: - title: 'Host your own runners' + title: 'Hospeda tus propios ejecutores' description: 'Puedes crear ejecutores autohospedados para ejecutar flujos de trabajo en un entorno altamente personalizable.' guides: - /actions/hosting-your-own-runners/about-self-hosted-runners @@ -44,8 +51,8 @@ hosting_your_own_runners: - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners create_actions: - title: 'Create an action' - description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + title: 'Crea una acción' + description: '¿Tienes una idea para crear una acción nueva? ¿Has creado algo personalizado para tu proyecto? Aprende cómo crear acciones que se pueden compartir y publícalas en GitHub Marketplace.' guides: - /actions/creating-actions/about-actions - /actions/creating-actions/creating-a-docker-container-action diff --git a/translations/es-ES/data/products.yml b/translations/es-ES/data/products.yml index 6f39705793..e4d28b80e7 100644 --- a/translations/es-ES/data/products.yml +++ b/translations/es-ES/data/products.yml @@ -7,7 +7,7 @@ productsInOrder: - admin - debates - acciones - - packages + - paquetes - developers - rest - graphql diff --git a/translations/es-ES/data/release-notes/2-20/11.yml b/translations/es-ES/data/release-notes/2-20/11.yml index 58c9d5e5cb..f76f87c961 100644 --- a/translations/es-ES/data/release-notes/2-20/11.yml +++ b/translations/es-ES/data/release-notes/2-20/11.yml @@ -1,5 +1,4 @@ ---- -date: '09-07-2020' +date: '2020-07-09' sections: security_fixes: - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/12.yml b/translations/es-ES/data/release-notes/2-20/12.yml index 84a499fe65..548dc7d854 100644 --- a/translations/es-ES/data/release-notes/2-20/12.yml +++ b/translations/es-ES/data/release-notes/2-20/12.yml @@ -1,5 +1,4 @@ ---- -date: '21-07-2020' +date: '2020-07-21' sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/15.yml b/translations/es-ES/data/release-notes/2-20/15.yml index ea9c2f763c27eccfae882ab3f05bc6cac0e8155d..aa3c664487d3ed9e6eec19ea4fa1d5deaa039dd4 100644 GIT binary patch literal 5369 zcmbtY+iu%N5Pi>A3=9-%4O0?n%aRPVMdG-rfd(z&qL$gYhhgE(cGXOloDcyLv)|&y7{}`u#%POaBc~ zKtBceiT_SduV3B1zP*0>+tukQJtZqkQ%g!rDoNgBFCRq9rqI%gSQR*lR>F}=rLNUN z$&{3)7pnfXiRllKNk?@qY8=oMDaCw9RTx!c-71%w;zkvz(iw^EO%6+j^u|dWBu3ZP z6a}{6<3eSP72XQ7z}b=-ol0A*`H)Ij>~PdLERNUPN3Numq)kn(Su9kdU~sX9gRZtJ zVS|KDsT6Qj)l?bhR9r}^P3JcUp)9e+5hB1BcV6D;TH4AgC+SYwrL>5EtA$SBz-!*^ z9mWpjwgY#D8%fl)NIqiI%11~`7*a`FD%{Wa7)q=}O1*VHTKhuv7?XDFAhB2gAsm6C zAUMD`!^_1NJ%nT1frqsXQteZvVt@q6fa$wFlh48@Xo*doBVY)j#_enGW}REpWcjB- zzUyF1&zg*$nMMP5l{J|a<&fS=%Ec0SV=Gd+{_`gA@DIn6a5kiWzVoR=zUjMvDX;6w zU5!SWs`DluBB|ZSQN?f_RZUThqS@^H?8v3_adhm`+5F<@rPJyEE)6nSw)RfP&KP|Rn?E}f6($1a`C!=snZj*r@G&gqsqCtkiGpsQJ1)P^$%ImsdUo^H zZJ*wG2wQ|^#_R4_`+DUd#nPc9nW|d@_g?U5mSC@p>XqChexSgu+QUpB*gc&sI;v^BouudK~|Oe&HLd=R6^O&@Q*{E>p8Qh^y94uD7u~&bu19hCI@M5-;U@YaqRAh!pT9_-Q5w+qk}xQyCcFS zhlpp-j&MHSn~k{1HUet!lu*|WdGT_HWkzAL41n`8hYKsqC2JW7m_Sq&S{?YuGfys3 zS}3htj^(z|n!6{jmM#ECm;e$2y5n227lnu0$v&^A;a;ydoc_j1$iC4F#f z2gg6aA&93|^_c{clNCy?vOEw=p^9EQqAUxr8uVkU<-i!FuuuUAkYWjip3Yp>?kS+C zj;+5v9z~Z2YjDqwFuM3+3{IYlTEqgX&&t3-ws92Tq+o(&r#kN!aFXe)i&6oV=9-)UZfXFpq00?vb?Mo(;ZwH4(mNznW-z z`u1)!)lj{zBs9p^S0V`YvAram9)RU545>?az*cvVLi1~AjmzIrs}@ zp*wtVJtuq}NLq_W;cSnX->9H#gxZvRqg;V8K`jL+NpvH=uSQfPK#}6P14#qBHWkLj z^ecNvXH+zcc7eDt3do?}ez_yy3f#_JosD`2o;0|a0s1i5u4LTKy$g}Z2hG`%njcGJ zG}2LoAvS0a2>fvY1i{)gmYHfZEBxR+S2{7)VwC4O+Shc7@c4f_Ww_b1K0Y-a&2|Bp zTwKn++!P15-9v!TEP?RelN5#@W7_`SP8`S!FvyP_qEPxH4+w(bEXTvwu!FGwbW8!2 zBCjpL&_yc2PX-Rs1H9gK&S)|r5Iy4lxB}dEE*wv%=LclZTYj=SdE+O&1c(C3*d*`j zhjVtqcA*R4cAeWQTh(VLl%pPl*#kO!}M0PN9>ycP}P2fNzy z_^$qT)N)hQk02dipDZddQA!Zps88)7#kYBY5rwq%gKdl`KUn#GS2Zs0)S%ZvEkM`( W^Ar!|>@L#&h%)>vM;GV&1^It-{!$PC literal 4546 zcmbtXO>Y}F5bZg?f-n%MF|v|&ZCSE`wg?h83E;Fq+>b+0*xX%e&6G=S`Qcb8`eSbjCoHz64%`i!lMiXM4U2xpkoyu=y2G&qaNQfM!yvY3B<$`oh#L9s^ITKf4X&Nx%XvETx?5)V9h zT3*1|(Uvff+Ig-E$?@Hjo#r+gX;bG`#AQ}A#z}AD9*vdf(Ow(c4=+D1w&O(*7Jk8L z=7M9dUoai&`K85)uFqb`;_Mbi?9#d`=bxES3zXM32MjHBHUFZSmyKD(MQDk`2nNtx z^RecR{S^e9U@eS3I|R&|@#Rw_4##rlO$if)zjI+7a@hiZDgCREvqO!@05{@&EG$+q zPH&{4_#nibW&JE;GfId;qMWRBi{{<)-wu;Vm2@~t$A5f#=6&N127}^U^pPVg`o>m+ zqLN82HNDlm7JYpGfgZlQZvLdtj&6a#nS|YTKrBC>UsBc-d)HV~Szc3Wv8FI}BeVlX ztY*U6=stdGQLcQ;P0)VUucSWP#e1iK(m--ZW~)TIqoq_$b~(-#lc9RtcAo$|T~V z!6pw$V3v;WB;)M_!XjM@oFu(>s8Cc9EudWhmOMA?jFXg-j@jajUYxp_Q>Hp)O+W|? znuC?7KF#d>vQZ?A1i6&1Fa{QsZe(!fn~J;FFFD5lsntonXJt)TDY!OgAHM$M7G5o>?+@tFbNtHQGCgP zH8iKG#jU20SPh*SbC7yLN>AOaHf^)7srPCbqkvJPl@?H|jRq9trnWq!G$0v!n=v8X z-CZx1q#0Y!Do6&ek$q>VXA98TwnG|GJfdGsWN$|tL&e)ste8w%wBT`Hy9jO@wGLrVq&%eB&>OMYxg?~9sbDX%2 zE|Dv-m|JwYNH&dhvPOY>p0`2cl?@GVxe$Z*@+%YD!$P;eX;+?%*OTB+Z9eD|>0G#3 zLfsU$X4b^yCg+#Xg4i!nVhEFydN~qz^6``+$2~8oJ{AhX3M-%=C?9Gb(94C^@Diz` zPL18{{|iowVvtTI`)idVHpwGo9+amVN1_W*o==0Qz;sOg&geMI(d><$h9aiohPKV8FyyBuK=-JM3UqaTmSbr7q)QV900;I@hr zXpJ@(y^Ixr8D`20!9Iw5HB7g%N>lV8#~d)oa1lr#^oEzoR4R-&7;a`JSQ5+bmL=R1 z3I@mxu^|1E8j%AJFcr+u^y3rF;#fmN$imLtKSZ6{cR3vG?oGbl(0i0b)MNwF`ZiT~ z#Kn^pXwclkRm>_>@NMd-TWLj+pqm{>Hpx+nAyvt~OVFr}w4N2sMIfG5=x4 z0Uu_#tKfb$8le}WyCB8_SIPVK_Ukay;ds1r$3*vh*-Xyj9UMMv5jB?g=MHur9GoGC z!3tauDZ5)y;M(u(xzQTgYJ1z2$iad-|CNkUV7vP?v<-o>G$pjffUK)9qi`+ET)<$s zy1VD|FAkbm#tYucmHUS$ssN4FxXcP&h{1vncg?-T2Cf7uIo9;@a@BcF;P4yBv5ck* mIf1*DgdswNq|ZNTR2~ThcmtsKhjJs+yF2SIE&l;-06wVz diff --git a/translations/es-ES/data/release-notes/2-20/16.yml b/translations/es-ES/data/release-notes/2-20/16.yml index fbab7d0c79..c660f62685 100644 --- a/translations/es-ES/data/release-notes/2-20/16.yml +++ b/translations/es-ES/data/release-notes/2-20/16.yml @@ -1,9 +1,8 @@ ---- -date: '08-09-2020' +date: '2020-09-08' sections: bugs: - 'Una revisión de salud del servicio causó un crecimiento de sesión que resultó en el agotamiento del sistema de archivos en el nodo. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Hacer mejoras utilizando hotpatches podría fallar con un error de `'libdbi1' was not found`{% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + - 'Hacer mejoras utilizando hotpatches podría fallar con un error de `''libdbi1'' was not found`{% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' known_issues: - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/17.yml b/translations/es-ES/data/release-notes/2-20/17.yml index 153edb5399..fa9a189fff 100644 --- a/translations/es-ES/data/release-notes/2-20/17.yml +++ b/translations/es-ES/data/release-notes/2-20/17.yml @@ -1,5 +1,4 @@ ---- -date: '23-09-2020' +date: '2020-09-23' sections: security_fixes: - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/18.yml b/translations/es-ES/data/release-notes/2-20/18.yml index cca5eda8b8..ea8259cf20 100644 --- a/translations/es-ES/data/release-notes/2-20/18.yml +++ b/translations/es-ES/data/release-notes/2-20/18.yml @@ -1,12 +1,11 @@ ---- -date: '09-10-2020' +date: '2020-10-09' sections: security_fixes: - 'El usuario cuyo nombre de usuario del directorio de LDAP se estandarice a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'El guardar las configuraciones a través de la [consola de administración](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) añadirá una línea nueva en los archivos de la [llave y certificado TLS/SSL](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls), lo cual activó la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - 'Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/5.yml b/translations/es-ES/data/release-notes/2-20/5.yml index f196773ea1..69aede8d38 100644 --- a/translations/es-ES/data/release-notes/2-20/5.yml +++ b/translations/es-ES/data/release-notes/2-20/5.yml @@ -1,5 +1,4 @@ ---- -date: '07-04-2020' +date: '2020-04-07' sections: security_fixes: - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/7.yml b/translations/es-ES/data/release-notes/2-20/7.yml index 79ee352ed5..9ed217f7af 100644 --- a/translations/es-ES/data/release-notes/2-20/7.yml +++ b/translations/es-ES/data/release-notes/2-20/7.yml @@ -1,5 +1,4 @@ ---- -date: '05-05-2020' +date: '2020-05-05' sections: security_fixes: - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/0.yml b/translations/es-ES/data/release-notes/2-21/0.yml index fce0ca85e9..5d2184d668 100644 --- a/translations/es-ES/data/release-notes/2-21/0.yml +++ b/translations/es-ES/data/release-notes/2-21/0.yml @@ -1,5 +1,4 @@ ---- -date: '09-06-2020' +date: '2020-06-09' sections: features: - 'Los usuarios pueden [administrar las notificaciones](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) en las propuestas, solicitudes decambios y otros temas cuando navegan desde una notificación web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' @@ -14,13 +13,13 @@ sections: security_fixes: - 'Se identificó una vulnerabilidad de control de accesos impropia en la API de GitHub Enterprise Server que permitió a un miembro de una organización escalar los permisos y obtener acceso a repositorios no autorizados dentro de la organización. Dicha vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 2.21. Hemos emitido el [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) como respuesta a este problema. La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' bugs: - - "Si un usuario con acceso de subida minimiza el comentario de otro usuairio, el autor del comentario podría dejar de minimizarlo aún si tuviese privilegios insuficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Si un usuario con acceso de subida minimiza el comentario de otro usuairio, el autor del comentario podría dejar de minimizarlo aún si tuviese privilegios insuficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}' - 'Los usuarios podrían fusionar accidentalmente hacia la rama principal desde el editor de plantillas de propuesta y de blobs. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - 'Cuando un usuario borró una cuenta de GitHub, los registros de la bitácora de auditoría no mostraron correctamente los registros de eliminación de la organización. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - 'El avatar de gist para el usuario actual enlazó a una URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - 'La pestaña de repositorios de la organización no incluyó los repositorios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - 'Dar clic en el botón de "Mostrar todos los equipos" cuando se transfiere un repositorio causó un error 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - "Los nombres de archivo grandes causan problemas de desbordamiento cuando se muestra la etiqueta 'Cambió desde la última vista' o la alternación de diff de 'Mostrar enriquecido' en la vista de archivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Los nombres de archivo grandes causan problemas de desbordamiento cuando se muestra la etiqueta ''Cambió desde la última vista'' o la alternación de diff de ''Mostrar enriquecido'' en la vista de archivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}' - 'Las tarjetas de visita virtual para los equipos de la organización reportó mal su capacidad de miembros. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - 'La ventana emergente del comentario de la revisión de solicitudes de cambios tenía un problema desplazamiento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - 'Haproxy podría saturarse y causar una ralentización en las opreaciones de git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/2.yml b/translations/es-ES/data/release-notes/2-21/2.yml index 501875fbb3..8724dd1fba 100644 --- a/translations/es-ES/data/release-notes/2-21/2.yml +++ b/translations/es-ES/data/release-notes/2-21/2.yml @@ -1,5 +1,4 @@ ---- -date: '09-07-2020' +date: '2020-07-09' sections: security_fixes: - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/3.yml b/translations/es-ES/data/release-notes/2-21/3.yml index 0a50eda8ea..b8c345580b 100644 --- a/translations/es-ES/data/release-notes/2-21/3.yml +++ b/translations/es-ES/data/release-notes/2-21/3.yml @@ -1,12 +1,11 @@ ---- -date: '21-07-2020' +date: '2020-07-21' sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' bugs: - 'Las gráficas de monitoreo de la consola de adminsitración a veces no se muestra correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - 'El flujo de creación de un manifiesto de una GitHub App no se pudo utilizar en algunos escenarios en donde la política de SameSite Cookie se aplicó. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - "En algunas circunstancias, acceder a la página de 'Explorar' arrojó un error de aplicación. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + - 'En algunas circunstancias, acceder a la página de ''Explorar'' arrojó un error de aplicación. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}' known_issues: - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/6.yml b/translations/es-ES/data/release-notes/2-21/6.yml index a703831785aaf25fd6f7574b130bbe330236fb64..8638d1d9cdc19d41df282981117dbb7b1bdc36a6 100644 GIT binary patch literal 5795 zcmbtYZExGQ8vVXsK?E4Q29a$kaV!VehAhpx04r8B?d^wRs40n-h)SeDigvt<``_<* zD9Nd7*K^YLi|z2`c{}Gh4>R6~D>jJ6(Kr~#L3BCz!HTqzTG^`~7{h00WV8OXkPpKD z!dSq53GgTScY1pB_U_%?&GnyGr>E?i8Bys*uvBM)i3jYZgV@rQN*JEV5+|`0w@hY2 zHF6lneSu7c{_g0u7 z)v7VNEU^V27czH-dn@z;XA9<3CQP}eLuziY!!l>FI9YEWxe`V&r5k45Vj)urgUdA> zw2hG|8N^k_Dh@|w!)k4yriXBBJMgg9A=N%rGC`3b88Cgkb~4Se~B<4G6~*?)iZsYAZm zkN;yu)718AG|FXDxMYZ=b{|JImFuW>WjTuCI66CW>1=%T(s*`p?5Xi|`malaTvV;S z)A9JML-4Ww&HnZHJ`}T~m(IrL$DcYrerb60()fbXEmTHeZ8PrU60pJP>Fe8QcxJ>oV4jYXdIlg6WCF!qNd+ze zXcVsi6fAR!_G=^m!Di6Ml0a?*h(|W~6^nAY1VdtzG)%clfTnoK?p|7g-`8ZqGMRaH z^VV&j-gyXHxFW{u?pS-gQjij10ZF3j*1)|NJeeiPD{UwQ(J+cUvJ13|M8GQ!ddn3& z|G0(L>EA!~^_womu#$}tLv8X=n#&-OYJ^`Yf*m4d^BC1 z`5N?;D_Dsy7JaVg%%0MZw;n~&^|YvCfiRvN#P+@&QGCef-5pUlImnN@JHlCXkVbZQ zL{WG!6MJ@qv+>?+Bre|wsKGS@t}XK7bX?Pg*T(0FKZBBm{KF_hc^$r%%qsG~DYo$;H9#16dA!@?LJby)u&TPPEsg^%!`08xh#9>2w0Y2HR#7y%YiW}ZlD4XAW0GmJ)O9$-BUtQ z9gDv`d5kWf9D``Lo%A?7dC41|aHu{b0t?wjQGk=22$r1cykEdwwu0CI0Wx8XHdk!^ z3iVNw?gRHqlnGd}z@G;dfB4k3mrw2A2lMZ7`8+zPO?HDc9$)TK&q+@`cZykEA+K=T zvdnou(YC1fF;GzNbIS1xA~6|{TbF?Xs)xR~dpICWLRk?w4;-5sSvSY0c$+k%%k$~C z3--OG^vnrWm4s?Ui=ChOMlk1DHunON^na_uea=9prA|M$32nPFW*r(@oIi}5mw@h_xhQlf*@dN$nzLQvbcvF+kzZAaxQex6{#Pjw#KTnP5t&F z#&%H=4;YLpPGVhoY*sWC`iSgso8jvCaO{?0I6W+X_w2a1*w4}wi<1vx0Iou&!LZiV zqy^Z5vCtFUVrr*?3EygF(#T?HCK+CIk zioe}xfquSCOJ|`EzB4w5XQ4eAj;H%G{8{Oh`qYk~o9h3Is(*p$zCfq7;8|CH+aaQ7 z?HVtSy^h}=&D%EC&EXXMg*4DtKDeIyo>wHT#iKBeXL|wdQGA0?>xym^D|7}>XbI}& z-BX4~BM^zA$ndO#q@jzr8U&X;vsZRTMRBxSh<)oDpfcE>zuz;|6?zz{7c%N2`hmv9 zRG^Oo{7NM4e81qSc+}P{srm6cfnXR#7}kUKfWRLYK=`b+GsIMzndpW0T&h$XgC`4m zFYuVo5FY=vQ^1=&>*G_?(QFrh$;IWKS#lGByY9h*E0TJ6*GfxGk4~+QX(ub>1vN;I zIlPqWGYvwV!C8uj$FRi!^W``ODn(w~0z3N#X`2K~H`+S}A1WtbL1tu2Y-Y zmfCCo(DUdu4Z3|bBd?{S`oXUDJi4pD9awf{^90iI_$2X+$ytElMty1zDcj9M6EB5n z9&MwF@&lyrceS$xq0OiCvDo@&IC^{_caiod!0@XaU7UYw@bJWN?J}Sc(6Q*rYbrrJ zB^r8sBLHd^M$_RK|3gF*Y>gSCdz(P%IJ_fRU<>;C?hQc*u|;5i>gUMz^(+j=(Tiub Nzn(-e`0f+X{|BA6;3@zB literal 5014 zcmbtYU2hXd6zwy=ViXCvAlCM7;@FAQRtQo+g0>?4ct91N-5qZRW@onZ5inJM439kU z#2c^vV?B3vZRf*@ViJV1v1fMgx%b?2&uo$;cS`QXA?szsY?uruNw(j+<3!=5(eCgL zW4I1h`uXdbd@tfBj3w;H1Ygn5cl6U;C#-k>{)?l>&mJD$zt8^AoSg=xh2^KS3Y}*23tsBfz|vUp_m+qLN82HGQgiE&BNTC%X9I{Puf&_WTkEJd?274v6Kai%(QF#a=bmRF>CNTC6Ed z-3aY~5v!T7HinO{T9oV9auc+l_bcg7Lf*$VJon$bsA^q8sMWYAtNe>Fj= zK{`qgCi@R=zIvSQ(u0I9*U##$o8_2#z=PmmoCU?G>hbfQ8} zqN8q(13#%IvkxjPSk)@-(?RKOG*>JlZS(aW~lgl`=^kBHLE_tX{ z3fKE3>X8+dbl!sfK{L?B@i!2$z%@D*lmsKAh*c*dflAC|mGGufbJj`^wt;=38_pX-Z!|(Z3>vBZ;^n2fwxQoB&oDCux4B-RGuaX z2oyz%Hj(Tfvgs4!(ecGw;aM)L3PS8pxMsbYzkiL5=A9^Cx8L`s6yI7#t`VUPgx}4w z?V4&h+`lYcJ5jobDVlLr1r6M&w{e)%xNH*vaNT%jWr(!~O}cDoEDsLpSfye#9I{#> zVhi4MeS$P8<_aqtA3Fx5Lf?r5JF6{t(Fu5`+}Zx__{s|R9x4_*ObT?EO{q(3i9rJ| zFnvJ5Anmc?r@Snuv7|H&HOrNOTDN%4%}s|j;cx&Ze=XkHPb6$62PP8Ua@~egOgu#YyTB>pxeeAhMb@o zM{~S3t<6DFVc%q|KTK9Dsz_SP10?ODs@^x*B1e@wb|eEbx@a`Lg9x*YQ{S7Pbdbh#`xnORvw z+C0zOr18pzhPPaZ$$N5zSG`^84z~3plksK}yw&ENel48~7h9j>RA4&JJI?56W9ig^X^tkQ=7z9CB})J$AS5oecw;QTRg~Ez zyG-WRRbw`uI*QwY|O{aWrbH&0Qg_FWA}d;62CtxS)Kh@NafTHlrmmpF2>0@j3EgbJ5N4d0fI z=CoFn2|CkqRFeWFdLjckjX;uf>1uN}cKWL!66t57_7k2n5w%I1+M*@Ju+IO zTJ3B*lR4}l&vT|?l-TY~0<;Z@vgD82WaRn!w>ZkYkli7jgo3Wsee (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**Nota**: {% data variables.product.prodname_dependabot %} también es compatible con los siguientes administradores de paquetes: +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn` (solo v1) (especificar `npm`) +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --Archivos de `.gradle.kts`, para proyectos de Kotlin (especificar `gradle`) - --`pipenv`, `pip-compile`, y `poetry` (especificar `pip`) - -Por ejemplo, si utilizas `poetry` para administrar tus dependencias de Python y quieres que el {% data variables.product.prodname_dependabot %} monitoree el archivo de manifiesto de tu dependencia para encontrar versiones nuevas, utiliza `package-ecosystem: "pip"` en tu archivo de *dependabot.yml*. - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. Por ejemplo, si utilizas `poetry` para administrar tus dependencias de Python y quieres que el {% data variables.product.prodname_dependabot %} monitoree el archivo de manifiesto de tu dependencia para encontrar versiones nuevas, utiliza `package-ecosystem: "pip"` en tu archivo de *dependabot.yml*. diff --git a/translations/es-ES/data/reusables/desktop/delete-tag.md b/translations/es-ES/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..fcae2dbbf8 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Da clic derecho en la confirmación. + + - Si la confirmación solo tiene una etiqueta, da clic en **Borrar la etiqueta NOMBRE DE ETIQUETA**. ![Selecciona el elemento del menú de borrado de etiqueta](/assets/images/help/desktop/select-delete-tag.png) + - Si una confirmación tiene etiquetas múltiples, pasa el ratón sobre **Borrar Etiqueta...** y luego da clic en aquella que quieras borrar. ![Pasa el ratón sobre el menú de borrado de etiqueta](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/education/about-github-education-link.md b/translations/es-ES/data/reusables/education/about-github-education-link.md index 7cbac2c001..872fa5dd7a 100644 --- a/translations/es-ES/data/reusables/education/about-github-education-link.md +++ b/translations/es-ES/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_education %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)". +Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_education %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)". diff --git a/translations/es-ES/data/reusables/education/apply-for-team.md b/translations/es-ES/data/reusables/education/apply-for-team.md index fdb25ed5b4..7dc56203f3 100644 --- a/translations/es-ES/data/reusables/education/apply-for-team.md +++ b/translations/es-ES/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Solicita gratis [{% data variables.product.prodname_team %}](/articles/github-s-products), que permite tener ilimitados usuarios y repositorios privados. Para obtener más información, consulta la sección "[Postularse para un descuento para educador o investigador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)". +- Solicita gratis [{% data variables.product.prodname_team %}](/articles/github-s-products), que permite tener ilimitados usuarios y repositorios privados. Para obtener más información, consulta la sección "[Postularse para un descuento para educador o investigador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)". diff --git a/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md b/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md index 774a79532c..65aff86226 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/pages-policies-save.md @@ -1 +1 @@ - 6. Haz clic en **Save ** (guardar). ![Save button](/assets/images/enterprise/business-accounts/pages-policies-save-button.png) + 6. Haz clic en **Guardar**. ![Botón de guardar](/assets/images/enterprise/business-accounts/pages-policies-save-button.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md index 5d9fb29f64..668a587d55 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/pages-tab.md @@ -1 +1 @@ -1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Pages**. ![Pages tab in the enterprise sidebar](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file +1. Debajo de "{% octicon "law" aria-label="The law icon" %} Políticas", da clic en **Páginas**. ![Pestaña de páginas en la barra lateral de la empresa](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index 5c89ca67cf..762aab135e 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. Para solicitar acceso al beta, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). +**Nota:** El aprovisionamiento de usuarios para las organizaciones de tus cuentas empresariales, el cual solo son compatibles con Okta por el momento, se encuentra en beta y está sujeto a cambios. Para solicitar acceso al beta, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). {% endnote %} diff --git a/translations/es-ES/data/reusables/enterprise-managed/about-billing.md b/translations/es-ES/data/reusables/enterprise-managed/about-billing.md index 9e7ed843b2..494547eccb 100644 --- a/translations/es-ES/data/reusables/enterprise-managed/about-billing.md +++ b/translations/es-ES/data/reusables/enterprise-managed/about-billing.md @@ -1 +1 @@ -You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file +Recibirás una factura mensual para {% data variables.product.prodname_ghe_managed %} con los cambios que se calculan por usuario con licencia por día. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 50d5b70a0d..84e8d11c99 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,6 @@ -- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Optional features](#optional-features){% endif %} +- [Requisitos mínimos](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Características beta en {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Caracteristicas opcionales](#optional-features){% endif %} - [Almacenamiento](#storage) - [CPU y memoria](#cpu-and-memory) @@ -8,7 +8,7 @@ Te recomendamos utilizar configuraciones de hardware diferentes dependiendo de la cantidad de licencias de usuario que tengas para {% data variables.product.product_location %}. Si aprovisionaste más recursos que los de los requisitos mínimos, tu instancia funcionrá y escalará mejor. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} Si habilitas {% if currentVersion == "enterprise-server@2.22" %}el beta para {% endif %}{% data variables.product.prodname_actions %}, revisa los siguientes requisitos y recomendaciones. - Debes configurar por lo menos un ejecutor para los flujos de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)." - Debes configurar un almacenamiento externo de blobs. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". @@ -31,7 +31,7 @@ Tu instancia requiere un disco de datos persistentes independiente del disco ra {% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". +Si habilitas{% if currentVersion == "enterprise-server@2.22" %} el beta de {% endif %} {% data variables.product.prodname_actions %}, necesitarás configurar un almacenamiento de blobs externo. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md index 662b594a56..0664207a3d 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md @@ -2,7 +2,7 @@ {% note %} -**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." +**Nota**: Si habilitas las {% data variables.product.prodname_actions %} o el {% data variables.product.prodname_registry %}, tu instancia requerirá de recursos de hardware adicionales. Los requisitos mínimos para una instancia con características {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}opcionales{% endif %} habilitadas se encuentran en **negritas** en la siguiente tabla. Para obtener más información, consulta la sección "{% if currentVersion == "enterprise-server@2.22" %}[Características beta en {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Características opcionales](#optional-features){% endif %}". {% endnote %} {% endif %} @@ -40,10 +40,10 @@ Si habilitas las características beta para {% data variables.product.prodname_g {% elsif currentVersion ver_gt "enterprise-server@2.22" %} -#### Optional features +#### Características opcionales -You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +Puedes habilitar las características opcionales para {% data variables.product.prodname_ghe_server %}, tales como las {% data variables.product.prodname_actions %} y el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" o "[Iniciar con el {% data variables.product.prodname_registry %} para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". -If you enable optional features, your instance requires additional hardware resources. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". +Si habilitas las características opcionales, tu instancia requerirá recursos de hardware adicionales. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md index 44b21c113c..cc637934c0 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/es-ES/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. SSH en {% data variables.product.product_location %}. +1. SSH en {% data variables.product.product_location %}. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/es-ES/data/reusables/enterprise_management_console/actions.md b/translations/es-ES/data/reusables/enterprise_management_console/actions.md index 90b04ef08f..ca4f295dc2 100644 --- a/translations/es-ES/data/reusables/enterprise_management_console/actions.md +++ b/translations/es-ES/data/reusables/enterprise_management_console/actions.md @@ -1 +1 @@ -1. En la barra lateral izquierda, da clic en **Acciones**. ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) +1. En la barra lateral izquierda, da clic en **Acciones**. ![Pestaña de acciones en la barra lateral de configuración](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md index 0e86b7b604..2e64f5c01d 100644 --- a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md +++ b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md @@ -1 +1 @@ -If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. La licencia de {% data variables.product.prodname_advanced_security %} te permite acceder, a ti y a tus usuarios, a las características que te permiten añadir seguridad a tus repositorios ya tu código. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} +Si no puedes ver la **{% data variables.product.prodname_advanced_security %}** en la barra lateral, esto significa que tu licencia no incluye soporte para las características de {% data variables.product.prodname_advanced_security %}, incluyendo el {% data variables.product.prodname_code_scanning %} y el {% data variables.product.prodname_secret_scanning %}. La licencia de {% data variables.product.prodname_advanced_security %} te permite acceder, a ti y a tus usuarios, a las características que te permiten añadir seguridad a tus repositorios ya tu código. {% if currentVersion ver_gt "enterprise-server@2.22" %}Para obtener más información, consulta la sección "[Acerca de GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" o contacta a {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 924da690a0..9afc8bf9b1 100644 --- a/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/es-ES/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. Para importar los datos de migración archivados a una instancia de {% data variables.product.prodname_ghe_server %} , consulta "[Importando datos de migración a {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)". +1. Para preparar los datos de migración archivados para importarlos a la instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Prepararse para migrar los datos a tu empresa](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md index 4e1057532c..918341c752 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-ssh-access.md @@ -1 +1 @@ -SSH access allows you to run the {% data variables.product.product_name %} command line utilities to troubleshoot, run backups, and configure replication. \ No newline at end of file +El acceso por SSH te permite ejecutar las utilidades de línea de comandos de {% data variables.product.product_name %} para solucionar los problemas, ejecutar los respaldos y configurar la replicación. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md index 8c622226c6..d165f87f97 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-management-console.md @@ -1 +1 @@ -You can use the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL. \ No newline at end of file +Puedes utilizar la {% data variables.enterprise.management_console %} para administrar configuraciones del aplicativo virtual tales como el dominio, la autenticación y SSL. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md index bab0827c40..281103178b 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md @@ -1 +1 @@ -You can use the site admin dashboard to manage users, organizations, and repositories in your enterprise directly in {% data variables.product.product_name %}. \ No newline at end of file +Puedes utilizar el tablero administrativo del sitio para administrar usuarios, organizaciones y repositorios en tu empresa directamente en {% data variables.product.product_name %}. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md index eed05a84c9..02efcb4433 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -1,2 +1,2 @@ -1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Opcionalmente, para prever tu mensaje, da clic en **Vista previa**. ![Botón de mensaje de vista previa](/assets/images/enterprise/site-admin-settings/message-preview-button.png) 1. Haz clic en **Guardar cambios**. ![Botón Editar mensaje](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md index 6afb5ae6da..c4bac62704 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/repository-search.md @@ -1 +1 @@ -1. En el campo de búsqueda, teclea el nombre del repositorio y da clic en **Buscar**. ![Site admin settings search field](/assets/images/enterprise/site-admin-settings/search-for-things.png) +1. En el campo de búsqueda, teclea el nombre del repositorio y da clic en **Buscar**. ![Campo de búsqueda en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md index 97356743fc..37dcc4eda4 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user-or-org.md @@ -1 +1 @@ -1. En el campo de búsqueda, teclea el nombre del usuario u organización y da clic en **Buscar**. ![Site admin settings search field](/assets/images/enterprise/site-admin-settings/search-for-things.png) +1. En el campo de búsqueda, teclea el nombre del usuario u organización y da clic en **Buscar**. ![Campo de búsqueda en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md index 22e56e3340..97baa394b2 100644 --- a/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md +++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/search-user.md @@ -1 +1 @@ -1. En el campo de búsqueda, teclea el nombre de usuario y da clic en **Buscar**. ![Site admin settings search field](/assets/images/enterprise/site-admin-settings/search-for-things.png) +1. En el campo de búsqueda, teclea el nombre de usuario y da clic en **Buscar**. ![Campo de búsqueda en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-ES/data/reusables/gated-features/actions-shared.md b/translations/es-ES/data/reusables/gated-features/actions-shared.md index f10d9ef470..57b1ab7a7d 100644 --- a/translations/es-ES/data/reusables/gated-features/actions-shared.md +++ b/translations/es-ES/data/reusables/gated-features/actions-shared.md @@ -1 +1 @@ -{{ site.data.variables.product.prodname_actions }} se encuentra disponible con {{ site.data.variables.product.prodname_free_user }}, {{ site.data.variables.product.prodname_pro }}, {{ site.data.variables.product.prodname_free_team }} para organizaciones, {{ site.data.variables.product.prodname_team }}, {{ site.data.variables.product.prodname_ghe_cloud }}, y {{ site.data.variables.product.prodname_ghe_one }}. {% data variables.product.prodname_actions %} no se encuentra disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. +{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_one %}. {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. diff --git a/translations/es-ES/data/reusables/gated-features/code-scanning.md b/translations/es-ES/data/reusables/gated-features/code-scanning.md index 69e6abf27f..bb9250bab9 100644 --- a/translations/es-ES/data/reusables/gated-features/code-scanning.md +++ b/translations/es-ES/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}El {% data variables.product.prodname_code_scanning_capc %} se encuentra disponible para todos los repositorios públicos y para aquellos privados que pertenezcan a organizaciones en donde se ha habilitado la {% data variables.product.prodname_GH_advanced_security %}.{% else %}El{% data variables.product.prodname_code_scanning_capc %} se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/es-ES/data/reusables/gated-features/private-pages.md b/translations/es-ES/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..f772530816 --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +El control de accesos para los sitios de {% data variables.product.prodname_pages %} se encuentra disponible en los repositorios privados con {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/es-ES/data/reusables/gated-features/protected-branches.md b/translations/es-ES/data/reusables/gated-features/protected-branches.md index ffae769bab..63f96900ff 100644 --- a/translations/es-ES/data/reusables/gated-features/protected-branches.md +++ b/translations/es-ES/data/reusables/gated-features/protected-branches.md @@ -1 +1 @@ -{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Las ramas protegidas se encuentran disponibles en los repositorios internos y privados con {% data variables.product.prodname_ghe_managed %}, {% else%}Las ramas protegidas se encuentran disponibles {% endif %}en los repositorios públicos con {% data variables.product.prodname_free_user %} y en {% data variables.product.prodname_free_team %} para las organizaciones, y en los repositorios privados y públicos con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/repository-insights.md b/translations/es-ES/data/reusables/gated-features/repository-insights.md index 71016e9f96..9f61530596 100644 --- a/translations/es-ES/data/reusables/gated-features/repository-insights.md +++ b/translations/es-ES/data/reusables/gated-features/repository-insights.md @@ -1 +1 @@ -This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %},{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."{% endif %} +Esta gráfica de perspectivas de repositorio se encuentra disponible en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Acerca de las gráficas de repositorio](/articles/about-repository-graphs)" y "[Productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)".{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/saml-sso.md b/translations/es-ES/data/reusables/gated-features/saml-sso.md index 9fb5fe8f92..9de5126084 100644 --- a/translations/es-ES/data/reusables/gated-features/saml-sso.md +++ b/translations/es-ES/data/reusables/gated-features/saml-sso.md @@ -1 +1 @@ -SAML single sign-on is available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} and {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". +El inicio de sesión único de SAML se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} y {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md b/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md index 7dd434920d..82b53923d7 100644 --- a/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md +++ b/translations/es-ES/data/reusables/gated-features/ssh-certificate-authorities.md @@ -1 +1 @@ -Support for SSH certificate authorities is available with {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 2.19+. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". +La compatibilidad para las autoridades de certificados SSH se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y con {% data variables.product.prodname_ghe_server %} 2.19+. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md index 535fa5cd9d..2d83bd0bcd 100644 --- a/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/es-ES/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. +Después de crear un gist, no podrás convertirlo de {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} a secreto. diff --git a/translations/es-ES/data/reusables/github-actions/actions-billing.md b/translations/es-ES/data/reusables/github-actions/actions-billing.md index e966816a37..c727e59086 100644 --- a/translations/es-ES/data/reusables/github-actions/actions-billing.md +++ b/translations/es-ES/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -El uso de las {% data variables.product.prodname_actions %} es gratuito para los repositorios públicos y para los ejecutores auto-hospedados. Para los repositorios privados, cada cuenta de {% data variables.product.prodname_dotcom %} recibe una cantidad determinada de minutos y almacenamiento gratuitos dependiendo del producto que se utilice con la cuenta. Cualquier uso que no se contemple en las cantidades incluidas se controla con los límites de gasto. +El uso de {% data variables.product.prodname_actions %} es gratuito tanto para los repositorios públicos como para los ejecutores auto-hospedados. Para los repositorios privados, cada cuenta de {% data variables.product.prodname_dotcom %} recibe una cantidad determinada de minutos y almacenamiento gratuitos dependiendo del producto que se utilice con la cuenta. Cualquier uso que no se contemple en las cantidades incluidas se controla con los límites de gasto. diff --git a/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md b/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md index 3e9f3df57f..37239ed971 100644 --- a/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -By default, {% if currentVersion ver_gt "enterprise-server@2.21" %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. Puedes elegir inhabilitar las {% data variables.product.prodname_actions %} o limitarlas para las acciones privadas únicamente, lo cual significa que las personas solo podrá utilizar las acciones que existan en tu repositorio. +Predeterminadamente, {% if currentVersion ver_gt "enterprise-server@2.21" %}después de que se habilita {% data variables.product.prodname_actions %} en {% data variables.product.product_location %}, este {% elsif currentVersion == "free-pro-team@latest" %} las {% data variables.product.prodname_actions %}{% endif %} se habilita en todos los repositorios y organizaciones. Puedes elegir inhabilitar las {% data variables.product.prodname_actions %} o limitarlas para las acciones privadas únicamente, lo cual significa que las personas solo podrá utilizar las acciones que existan en tu repositorio. diff --git a/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md b/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md index 0043c8e960..3d71ec7045 100644 --- a/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md +++ b/translations/es-ES/data/reusables/github-actions/enabled-local-github-actions.md @@ -1 +1 @@ -When you enable local actions only, workflows can only run actions located in your repository, organization, or enterprise. +Cuando habilitas únicamente las acciones locales, los flujos de trabajo solo pueden ejecutar acciones ubicadas en tu repositorio, organización o empresa. diff --git a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md index 86c5d9e0c0..a148c339ce 100644 --- a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ La plantilla inicial de flujo de trabajo configura el `PATH` para que contenga O Por ejemplo, para utilizar la versión 9.0.4 del JDK para una plataforma x64, puedes utilizar la acción `setup-java` y configurar los parámetros `java-version` y `architecture` en `'9.0.4'` y `x64`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md b/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md index e021cbc3ec..558bd719d2 100644 --- a/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Nota:** El ambiente virtual macOS 11.0 se proporciona actualmente solo como vista previa. La etiqueta de flujo de trabajo de YAML `macos-latest` aún utiliza el ambiente virtual de macOS 10.15. +**Nota:** El ambiente virtual macOS 11.0 se proporciona actualmente solo como vista previa privada. Cualquier usuario u organización que ya utilice este ejecutor puede seguir utilizándolo, pero no aceptaremos a ningún usuario u organización subsecuentes en en este momento. La etiqueta de flujo de trabajo de YAML `macos-latest` aún utiliza el ambiente virtual de macOS 10.15. {% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 51361f604a..e64c6a9bd2 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -3,7 +3,7 @@ {% warning %} - **Warning** + **Advertencia** {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md index 046dda6af7..09fd362076 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md @@ -1,4 +1,4 @@ -A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. Para administrar un ejecutor auto-hospedado, debes tener los siguientes permisos, dependiendo de donde se agregó éste: +Un ejecutor auto-hospedado puede ubicarse ya sea en la configuración de tu repositorio, cuenta de organización, o {% if currentVersion == "free-pro-team@latest" %}cuenta de empresa en {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} configuración de tu cuenta de empresa en {% data variables.product.product_location %}{% endif %}. Para administrar un ejecutor auto-hospedado, debes tener los siguientes permisos, dependiendo de donde se agregó éste: - **Repositorio de usuario**: debes ser el propietario del repositorio. - **Organización**: Debes ser un propietario de la organización. - **Repositorio de la organización**: Debes ser un propietario de la organización, o tener acceso administrativo al repositorio. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 21d5b4bb77..dc8d434546 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -1,6 +1,6 @@ 1. Navega a donde está registrado tu ejecutor auto-hospedado: * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**: + * {% if currentVersion == "free-pro-team@latest" %}**Si utilizas una cuenta de empresa**: navega hasta tu cuenta empresarial visitando `https://github.com/enterprises/ENTERPRISE-NAME`, reemplaza `ENTERPRISE-NAME` con el nombre de tu cuenta de empresa.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**Si utilizas un ejecutor a nivel empresarial**: 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. 1. En la barra lateral izquierda, da clic en **Resumen empresarial**. @@ -9,4 +9,4 @@ * **En un repositorio de organización**: da clic en **Acciones** en la barra lateral izquierda. ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies". + * {% if currentVersion == "free-pro-team@latest" %}**Si utilizas una cuenta de empresa**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**Si utilizas un ejecutor a nivel empresarial**{% endif %}: da clic en **Acciones** debajo de "Políticas{% octicon "law" aria-label="The law icon" %}". diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md index b5c9a384a2..2cb3d30d4b 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-public-repo-access.md @@ -1,5 +1,5 @@ {% note %} -**Note:** For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. 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#changing-the-access-policy-of-a-self-hosted-runner-group)". +**Nota:** Por razones de seguridad, los repositorios públicos no pueden utilizar ejecutores en un grupo de ejecutores predeterminadamente, pero puedes anular esto en la configuración del grupo de ejecutores. 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#changing-the-access-policy-of-a-self-hosted-runner-group)". {% endnote %} diff --git a/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md b/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md index bfe161ec4c..5dc6815850 100644 --- a/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md +++ b/translations/es-ES/data/reusables/github-actions/using-context-or-environment-variables.md @@ -1,9 +1,9 @@ -{% data variables.product.prodname_actions %} includes a collection of variables called _contexts_ and a similar collection of variables called _default environment variables_. These variables are intended for use at different points in the workflow: +{% data variables.product.prodname_actions %} incluye una colección de variables que se llama _contextos_ y una recopilación de variables similar que se llaman _variables de ambiente predeterminadas_. Estas variables se pretenden utilizar en puntos diferentes del flujo de trabajo: -- **Default environment variables:** These variables exist only on the runner that is executing your job. Para obtener más información, consulta la sección "[Variables de ambiente predeterminadas](/actions/reference/environment-variables#default-environment-variables)." -- **Contexts:** You can use most contexts at any point in your workflow, including when _default environment variables_ would be unavailable. For example, you can use contexts with expressions to perform initial processing before the job is routed to a runner for execution; this allows you to use a context with the conditional `if` keyword to determine whether a step should run. Once the job is running, you can also retrieve context variables from the runner that is executing the job, such as `runner.os`. Para obtener más información, consulta "[Contextos](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)". +- **Variables de ambiente predeterminadas:** Estas variables existen únicamente en el ejecutor que está ejecutando tu job. Para obtener más información, consulta la sección "[Variables de ambiente predeterminadas](/actions/reference/environment-variables#default-environment-variables)." +- **Contextos:** Puedes utilizar la mayoría de los contextos en cualquier punto de tu flujo de trabajo, incluyendo cuando no estén disponibles las _variables de ambiente predeterminadas_. Por ejemplo, puedes utilizar contextos con expresiones para llevar a cabo un procesamiento inicial antes de que el job se enrute a un ejecutor para su exclusión; esto te permite utilizar un contexto con la palabra clave condicional `if` para determinar si se debería ejecutar un paso. Una vez que el job se esté ejecutando, también debes recuperar las variables de contexto para el ejecutor que está ejecutando el trabajo, tal como `runner.os`. Para obtener más información, consulta "[Contextos](/actions/reference/context-and-expression-syntax-for-github-actions#contexts)". -The following example demonstrates how these different types of environment variables can be used together in a job: +El siguiente ejemplo ilustra cómo estos tipos de variables de ambiente diferentes pueden utilizarse juntas en el job: {% raw %} ```yaml @@ -18,4 +18,4 @@ jobs: ``` {% endraw %} -In this example, the `if` statement checks the [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data variables.product.prodname_actions %}, and the job is only sent to the runner if the result is `true`. Once the job is sent to the runner, the step is executed and refers to the [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) environment variable from the runner. +En este ejemplo, el contexto de la declaración `if` verifica el contexto de [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) para determinar el nombre de rama actual; si el nombre es `refs/heads/main`, entonces los siguientes pasos subsecuentes se ejecutarán. El `if` verifica que se encuentre procesado por {% data variables.product.prodname_actions %}, y que el job solo se envíe al ejecutor si el resultado es `Verdadero`. Una vez que se envía el job al ejecutor, se ejecuta el paso y se refiere al ambiente de variables [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables) para el ejecutor. diff --git a/translations/es-ES/data/reusables/github-ae/about-billing.md b/translations/es-ES/data/reusables/github-ae/about-billing.md index 9e7ed843b2..494547eccb 100644 --- a/translations/es-ES/data/reusables/github-ae/about-billing.md +++ b/translations/es-ES/data/reusables/github-ae/about-billing.md @@ -1 +1 @@ -You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file +Recibirás una factura mensual para {% data variables.product.prodname_ghe_managed %} con los cambios que se calculan por usuario con licencia por día. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md b/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md index dd699d9ad6..c514db8ffe 100644 --- a/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md +++ b/translations/es-ES/data/reusables/github-ae/github-ae-enables-you.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_managed %} enables you to move your software development to the cloud while meeting the most stringent security and compliance requirements. +{% data variables.product.prodname_ghe_managed %} te habilita para mover tu desarrollo de software a la nube mientras cumple con los requisitos de seguridad y cumplimiento más estrictos. diff --git a/translations/es-ES/data/reusables/github-insights/contributors-tab.md b/translations/es-ES/data/reusables/github-insights/contributors-tab.md index 68450baca6..5d7e26c048 100644 --- a/translations/es-ES/data/reusables/github-insights/contributors-tab.md +++ b/translations/es-ES/data/reusables/github-insights/contributors-tab.md @@ -1 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Contributors**. ![Pestaña de colaboradores](/assets/images/help/insights/contributors-tab.png) +1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Colaboradores**. ![Pestaña de colaboradores](/assets/images/help/insights/contributors-tab.png) diff --git a/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md index b2c935e893..3b2872e027 100644 --- a/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md +++ b/translations/es-ES/data/reusables/identity-and-permissions/revoking-identity-team-sync.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** If your organization uses team synchronization, revoking a person's SSO identity will remove that person from any teams mapped to IdP groups. For more information, see "[Synchronizing a team with an identity provider](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." +**Advertencia:** Si tu organización utiliza la sincronización de equipos, el revocar la identidad de SSO de una persona eliminará a dicha persona de los equipos que se mapearon en los grupos de IdP. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". {% endwarning %} diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md index 744b90ab28..a6b59f2d0f 100644 --- a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. Confirm team synchronization. +5. Confirma la sincronización de equipos. - Si tienes acceso IdP, haz clic en **Enable team synchronization (Habilitar sincronización de equipo)**. Serás redireccionado a la página de SSO de SAML de tu proveedor de identidad y se te solicitará que selecciones tu cuenta y revises los permisos requeridos. - Si no tienes acceso de IdP, copia el vínculo de redirección de IdP y compártelo con tu administrador de IdP para continuar habilitando la sincronización de equipo. ![Botón para habilitar el redireccionamiento de la sincronización de equipo](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/es-ES/data/reusables/interactions/interactions-detail.md b/translations/es-ES/data/reusables/interactions/interactions-detail.md index 187a3e7307..7d16f0f5f3 100644 --- a/translations/es-ES/data/reusables/interactions/interactions-detail.md +++ b/translations/es-ES/data/reusables/interactions/interactions-detail.md @@ -1 +1 @@ -When restrictions are enabled, only the specified type of {% data variables.product.product_name %} user will be able to participate in interactions. Restrictions automatically expire after a defined duration. +Cuando se habilitan las restricciones, solo el tipo de usuario de {% data variables.product.product_name %} que hayas especificado podrá participar en las interacciones. Las restricciones expiran automáticamente después de una duración definida. diff --git a/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md b/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md index 3942f79701..11e71fc04c 100644 --- a/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/es-ES/data/reusables/issue-events/issue-event-common-properties.md @@ -3,7 +3,7 @@ | `id` | `número` | El identificador único del evento. | | `node_id` | `secuencia` | La [ID de Nodo Global](/graphql/guides/using-global-node-ids) del evento. | | `url` | `secuencia` | La URL de la API de REST para recuperar el evento. | -| `actor (actor)` | `object` | La persona que generó el evento. | +| `actor (actor)` | `objeto` | La persona que generó el evento. | | `event` | `secuencia` | Identifica el tipo de evento real que ocurrió. | | `commit_id` | `secuencia` | EL SHA de la confirmación que referenció este informe de problemas. | | `commit_url` | `secuencia` | El enlace a la API de REST de GitHub para la confirmación que referenció a este informe de problemas. | diff --git a/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md index b3b2ae85de..defbfa8298 100644 --- a/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/es-ES/data/reusables/large_files/can-include-lfs-objects-archives.md @@ -1,4 +1,4 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Puedes elegir si -{% data variables.large_files.product_name_short %} objects are included in source code archives, such as ZIP files and tarballs, that {% data variables.product.product_name %} creates for your repository. 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)". +Los objetos de {% data variables.large_files.product_name_short %} se incluyen en los archivos de código fuente, tales como los archivos ZIP y las tarballs, que {% data variables.product.product_name %} crea para tu repositorio. 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)". {% endif %} diff --git a/translations/es-ES/data/reusables/large_files/rejected_pushes.md b/translations/es-ES/data/reusables/large_files/rejected_pushes.md index 4d04d4d367..10c62296b1 100644 --- a/translations/es-ES/data/reusables/large_files/rejected_pushes.md +++ b/translations/es-ES/data/reusables/large_files/rejected_pushes.md @@ -1 +1 @@ -Users cannot push {% data variables.large_files.product_name_short %} assets to {% data variables.product.product_name %} if {% data variables.large_files.product_name_short %} is disabled on the enterprise or repository. +Los usuarios no pueden subir activos {% data variables.large_files.product_name_short %} a {% data variables.product.product_name %} si {% data variables.large_files.product_name_short %} está inhabilitado en la empresa o repositorio. diff --git a/translations/es-ES/data/reusables/large_files/storage_assets_location.md b/translations/es-ES/data/reusables/large_files/storage_assets_location.md index cb76cf1bcf..3c3bd959db 100644 --- a/translations/es-ES/data/reusables/large_files/storage_assets_location.md +++ b/translations/es-ES/data/reusables/large_files/storage_assets_location.md @@ -1,4 +1,4 @@ {% if enterpriseServerVersions contains currentVersion %} -By default, the -{% data variables.large_files.product_name_long %} client stores large assets on the same server that hosts the Git repository. When {% data variables.large_files.product_name_short %} is enabled on {% data variables.product.product_location %}, large assets are stored on the data partition in `/data/user/storage`. +Predeterminadamente, el +cliente de {% data variables.large_files.product_name_long %} almacena activos grandes en el mismo servidor que hospeda el repositorio de Git. Cuando se habilita {% data variables.large_files.product_name_short %} en {% data variables.product.product_location %}, los activos grandes se almacenan en la partición de datos en `/data/user/storage`. {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md b/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md index e261918072..9288de4d96 100644 --- a/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md +++ b/translations/es-ES/data/reusables/marketplace/downgrade-marketplace-only.md @@ -1 +1 @@ -Canceling an app or downgrading an app to free does not affect your [other paid subscriptions](/articles/about-billing-on-github) on {% data variables.product.prodname_dotcom %}. Si deseas cancelar todas tus suscripciones pagas en {% data variables.product.prodname_dotcom %}, debes bajar de categoría cada suscripción paga por separado. +El cancelar una app o bajarla de categoría a la versión gratuita no afecta tus [otras suscripciones pagadas](/articles/about-billing-on-github) en {% data variables.product.prodname_dotcom %}. Si deseas cancelar todas tus suscripciones pagas en {% data variables.product.prodname_dotcom %}, debes bajar de categoría cada suscripción paga por separado. diff --git a/translations/es-ES/data/reusables/marketplace/launch-with-free.md b/translations/es-ES/data/reusables/marketplace/launch-with-free.md index 85d90751fd..33edc40bf2 100644 --- a/translations/es-ES/data/reusables/marketplace/launch-with-free.md +++ b/translations/es-ES/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -Puedes solicitar la publicación con o sin verificación. El solicitar una publicación sin verificación te permite lanzar una versión gratuita de tu app rápidamente. Si posteriormente solicitas la publicación con verificación, tu listado se actualizará e incluirá la insignia de creador verificado y cualquier precio de plan de pago cuando completes la verificación y la incorporación financiera. +Puedes solicitar la publicación con o sin verificación. El solicitar una publicación sin verificación te permite lanzar una versión gratuita de tu app rápidamente. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/es-ES/data/reusables/mobile/about-mobile.md b/translations/es-ES/data/reusables/mobile/about-mobile.md index 3f4846f7a9..dbf8301402 100644 --- a/translations/es-ES/data/reusables/mobile/about-mobile.md +++ b/translations/es-ES/data/reusables/mobile/about-mobile.md @@ -1 +1 @@ -{% data variables.product.prodname_mobile %} is available as an Android and iOS app. {% data variables.product.prodname_mobile %} is generally available for {% data variables.product.prodname_dotcom_the_website %} users and in public beta for users of {% data variables.product.prodname_ghe_server %} 3.0+. +{% data variables.product.prodname_mobile %} se encuentra disponible como una app tanto de Android como de iOS. {% data variables.product.prodname_mobile %} se encuentra generalmente disponible para los usuarios de {% data variables.product.prodname_dotcom_the_website %} y está en beta público para {% data variables.product.prodname_ghe_server %} 3.0+. diff --git a/translations/es-ES/data/reusables/mobile/ghes-release-phase.md b/translations/es-ES/data/reusables/mobile/ghes-release-phase.md index 57edb6b54a..e1a33094db 100644 --- a/translations/es-ES/data/reusables/mobile/ghes-release-phase.md +++ b/translations/es-ES/data/reusables/mobile/ghes-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_mobile %} is currently in beta for {% data variables.product.prodname_ghe_server %} 3.0 and subject to change. +**Nota:** {% data variables.product.prodname_mobile %} se encuentra actualmente en beta para {% data variables.product.prodname_ghe_server %} 3.0 y está sujeto a cambios. {% endnote %} diff --git a/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md b/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md index 94535c20d3..0425f3a49f 100644 --- a/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md +++ b/translations/es-ES/data/reusables/mobile/push-notifications-on-ghes.md @@ -1 +1 @@ -For {% data variables.product.prodname_ghe_server %}, push notifications for direct mentions are currently supported on iOS and coming soon to Android. {% data variables.product.prodname_ghe_server %} uses background fetch to support push notifications without sending your information to a third-party service, so you may experience a delay in receiving push notifications. \ No newline at end of file +Para {% data variables.product.prodname_ghe_server %}, las notificaciones push para las menciones directas actualmente son compatibles con iOS y pronto lo serán para Android. {% data variables.product.prodname_ghe_server %} utiliza búsquedas de segundo plano para ser compatible con las notificaciones push sin enviar tu información a ningún servicio de terceros, así que podrías experimentar un retraso en recibir las notificaciones push. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md index cd123cd86f..daa4d747a0 100644 --- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,10 +1,10 @@ {% if currentVersion == "free-pro-team@latest" %} -By default, you will receive notification of new -{% data variables.product.prodname_dependabot_alerts %}: -- by email, an email is sent every time a vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option) -- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option) -- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option) -- in your inbox, as web notifications for new vulnerabilities with a critical or high severity (**Web** option) +Predeterminadamente, recibirás notificaciones de +las {% data variables.product.prodname_dependabot_alerts %} nuevas: +- por correo electrónico, se envía un correo electrónico cada vez que se encuentra una vulnerabilidad con una severidad crítica o alta (Opción de **Enviar un correo electrónico cada vez que se encuentra una vulnerabilidad**) +- en la interface de usuario, se muestra una advertencia en tu archivo de repositorio y vistas de código si hay dependencias vulnerables (opción de **Alertas de la IU**) +- en la línea de comandos, las advertencias se muestran como rellamados cuando subes información a los repositorios con dependencias vulnerables (opción de **Línea de comandos**) +- en tu bandeja de entrada como notificaciones web para vulnerabilidades nuevas con una severidad alta o crítica (opción **Web**) Puede spersonalizar la forma en que se te notifica sobre {% data variables.product.prodname_dependabot_alerts %}. Por ejemplo, puedes recibir un correo electrónico semanal con el resúmen de las alertas de hasta 10 de tus repositorios si utilizas las opciones "**Enviar un resumen de vulnerabilidades por correo electrónico** y **Resumen semanal de seguridad por correo electrónico**. @@ -12,10 +12,10 @@ Puede spersonalizar la forma en que se te notifica sobre {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para recibir notificaciones en tu instancia, recibirás -{% data variables.product.prodname_dependabot_alerts %}: +las {% data variables.product.prodname_dependabot_alerts %} nuevas: - por correo electrónico, se envia un correo electrónico cada vez que se enecuentre una vulnerabilidad {% if currentVersion ver_gt "enterprise-server@2.23" %}con severidad alta o crítica{% endif %} (opción **Enviar un correo electrónico cada que se encuentre una vulnerabilidad**) -- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option) -- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option) +- en la interface de usuario, se muestra una advertencia en tu archivo de repositorio y vistas de código si hay dependencias vulnerables (opción de **Alertas de la IU**) +- en la línea de comandos, las advertencias se muestran como rellamados cuando subes información a los repositorios con dependencias vulnerables (opción de **Línea de comandos**) - en tu bandeja de entrada, como notificaciones web {% if currentVersion ver_gt "enterprise-server@2.23" %}para vulnerabilidades nuevas con severidad alta o crítica {% endif %}(opción **Web**) Puede spersonalizar la forma en que se te notifica sobre diff --git a/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md b/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md index 1ed5f3afb9..fde3a2f545 100644 --- a/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/es-ES/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. +Puedes solicitar que los miembros usen certificados SSH para acceder a los recursos de la organización, a menos que el acceso por SSH esté inhabilitado en tu repositorio. diff --git a/translations/es-ES/data/reusables/organizations/click-codespaces.md b/translations/es-ES/data/reusables/organizations/click-codespaces.md index 6a15dd7757..3e41713050 100644 --- a/translations/es-ES/data/reusables/organizations/click-codespaces.md +++ b/translations/es-ES/data/reusables/organizations/click-codespaces.md @@ -1 +1 @@ -1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) +1. En la barra lateral izquierda, da clic en **Codespaces**. ![Pestaña de "Codespaces" en la barra lateral izquierda](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md index 70a6fe26d9..29620e32dc 100644 --- a/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ b/translations/es-ES/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -1 +1 @@ -Si no eres un gerente de facturación para la organización, pide a tu cliente que solicite a un *propietario* de la misma[añadirte a la organización como gerente de facturación](/articles/adding-a-billing-manager-to-your-organization). +If you're not a billing manager for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/es-ES/data/reusables/organizations/team-synchronization.md b/translations/es-ES/data/reusables/organizations/team-synchronization.md index 874da7f527..ed017c9319 100644 --- a/translations/es-ES/data/reusables/organizations/team-synchronization.md +++ b/translations/es-ES/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -You can use team synchronization to automatically add and remove organization members to teams through an identity provider. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". +Puedes utilizar la sincronización de equipos para eliminar y agregar automáticamente a los miembros de la organización a los equipos mediante un proveedor de identidad. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". {% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-packages.md b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md index c85cb7bd74..64b208d748 100644 --- a/translations/es-ES/data/reusables/package_registry/authenticate-packages.md +++ b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md @@ -1,11 +1,9 @@ -Necesitas de un token de acceso para publicar, instalar, y borrar paquetes en {{ site.data.variables.product.prodname_registry }}. Puedes utilizar un token de acceso personal para autenticarte con tu nombre de usuario directamente en {% data variables.product.prodname_registry %} o en la API de {% data variables.product.prodname_dotcom %}. Cuando creas un token de acceso personal, puedes asignar al token diferentes ámbitos en función de tus necesidades. +You need an access token to publish, install, and delete packages. You can use a personal access token to authenticate with your username directly to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs. {% if currentVersion == "free-pro-team@latest" %} -Para autenticarte utilizando un -flujo de trabajo de {% data variables.product.prodname_actions %}: -- Para los registros de paquete (`PACKAGE-REGISTRY.pkg.github.com`), puedes utilizar un `GITHUB_TOKEN`. -- Para el registro de contenedor (`ghcr.io/OWNER/IMAGE-NAME`), debes utilizar un token de acceso personal. +To authenticate using a {% data variables.product.prodname_actions %} workflow: +- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`. +- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you must use a personal access token. {% else %} -Para autenticarte en el -{% data variables.product.prodname_registry %} utilizando un flujo de trabajo de {% data variables.product.prodname_actions %}, debes utilizar `GITHUB_TOKEN`. +To authenticate to {% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`. {% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md index e1733916de..b39d3e8f69 100644 --- a/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md +++ b/translations/es-ES/data/reusables/package_registry/enable-enterprise-github-packages.md @@ -1,3 +1,3 @@ {% if currentVersion ver_gt "enterprise-server@2.22" %} -1. Under "GitHub Packages", select **Enable GitHub Packages**. ![Checkbox to enable GitHub Packages from Enterprise Management Console menu](/assets/images/help/package-registry/enable-github-packages.png) +1. Debajo de "GitHub Packages", selecciona **Habilitar GitHub Packages**. ![Casilla de verificación para habilitar GitHub Packages desde el menú de la consola de administración de Enterprise](/assets/images/help/package-registry/enable-github-packages.png) {% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md index f9080682a0..e0e9eb7ce3 100644 --- a/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md +++ b/translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -1,3 +1,3 @@ -As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.product.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." +Como paso siguiente, puedes personalizar qué ecosistemas de paquetes quisieras hacer disponibles para los usuarios finales en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Configurar la compatibilidad de ecosistemas de paquetes para tu empresa](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". -For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +Para encontrar un resumen de cómo iniciar con el {% data variables.product.prodname_registry %} en {% data variables.product.prodname_dotcom %}, consulta la sección "[Iniciar con GitHub Packages para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". diff --git a/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md b/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md index cb1e4bbb4e..41425901b8 100644 --- a/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md +++ b/translations/es-ES/data/reusables/package_registry/packages-cluster-support.md @@ -1,7 +1,7 @@ {% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note:** {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering. +**Nota:** El {% data variables.product.prodname_registry %} en {% data variables.product.product_name %} no es compatible con el clústering actualmente. {% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md index 06105e439d..d02fc241b9 100644 --- a/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/es-ES/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ {% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Nota:** El {% data variables.product.prodname_registry %} se encuentra actualmente en beta para {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). +**Nota:** El {% data variables.product.prodname_registry %} se encuentra actualmente en beta para {% data variables.product.prodname_ghe_server %} 2.22. Para unirte al beta para tu {% data variables.product.product_location %}, utiliza el [formato de alta](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/pages/about-private-publishing.md b/translations/es-ES/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..e83f86ecda --- /dev/null +++ b/translations/es-ES/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. diff --git a/translations/es-ES/data/reusables/pages/choose-visibility.md b/translations/es-ES/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..809229a819 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Opcionalmente, si estás publicando un sitio de proyecto desde un repositorio interno o privado que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, elige la visibilidad de tu sitio. Debajo de "{% data variables.product.prodname_pages %}", selecciona el menú desplegable de **visibilidad de {% data variables.product.prodname_pages %}** y luego da clic en una visibilidad. Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Menú desplegable para seleccionar la visibilidad de tu sitio](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..5d8a8f5019 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Nota:** Los propietarios de la organización pueden restringir la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios que le pertenezcan a dicha organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %}](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md b/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md index 0dfaa7f40b..848bce56e7 100644 --- a/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **Advertencia**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Si tu administrador de sitio habilitó las Páginas Públicas, {% endif %}Los sitios de {% data variables.product.prodname_pages %} estarán disponibles al público general en la internet, aún si el repositorio del sitio es privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %}. Si tienes datos sensibles en el repositorio de tu sitio, tal vez quieras eliminarlos antes de publicarlo. Para obtener más información, consulta las secciones{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configurar {% data variables.product.prodname_pages %} para tu empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" y {% endif %} "[Acerca de la visibilidad del repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". +**Advertencia**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Si tu administrador de sitio habilitó las Páginas Públicas, {% endif %}Los sitios de {% data variables.product.prodname_pages %} estarán disponibles al público general en la internet{% if currentVersion == "free-pro-team@latest" %} predeterminadamente{% endif %}, aún si el repositorio del sitio es privado o interno.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} De otra forma, si {% else %} Si{% endif %} tienes datos sensibles en el repositorio de tu sitio, puede que quieras eliminarlos antes de publicarlos. Para obtener más información, consulta las secciones{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configurar {% data variables.product.prodname_pages %} para tu empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" y{% endif %} "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" y "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)".{% else %}".{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md b/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..f75ae4f047 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**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 %}. Si no ves los cambios reflejados en tu buscador después de una hora, consulta la sección "[Acerca de los errores de compilación de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pages/visit-site.md b/translations/es-ES/data/reusables/pages/visit-site.md index 8333125c37..3cf05fc531 100644 --- a/translations/es-ES/data/reusables/pages/visit-site.md +++ b/translations/es-ES/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% 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 %}. Si no ves los cambios reflejados en tu buscador después de una hora, consulta la sección "[Acerca de los errores de compilación de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/es-ES/data/reusables/project-management/choose-visibility.md b/translations/es-ES/data/reusables/project-management/choose-visibility.md index a9c327e7ac..5d8a76b170 100644 --- a/translations/es-ES/data/reusables/project-management/choose-visibility.md +++ b/translations/es-ES/data/reusables/project-management/choose-visibility.md @@ -1 +1 @@ -1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. Para obtener más información, consulta "[Cambiar la visibilidad del tablero de proyecto](/github/managing-your-work-on-github/changing-project-board-visibility)". ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} +1. Debajo de "Visibilidad", elige hacer tu tablero de proyecto {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} o privado. Para obtener más información, consulta "[Cambiar la visibilidad del tablero de proyecto](/github/managing-your-work-on-github/changing-project-board-visibility)". ![Botones radiales para elegir la visibilidad del tablero de proyecto]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %} diff --git a/translations/es-ES/data/reusables/project-management/project-board-visibility.md b/translations/es-ES/data/reusables/project-management/project-board-visibility.md index a39023f3f8..e86cb97031 100644 --- a/translations/es-ES/data/reusables/project-management/project-board-visibility.md +++ b/translations/es-ES/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -Por defecto, tu tablero de proyecto es privado y solo está visible para las personas con permisos de lectura, escritura o administración para el tablero de proyecto. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. +Por defecto, tu tablero de proyecto es privado y solo está visible para las personas con permisos de lectura, escritura o administración para el tablero de proyecto. {% if currentVersion == "github-ae@latest" %}Un tablero de proyecto interno{% else %}público{% endif %} será visible para {% if currentVersion == "github-ae@latest" %}cualquier miembro de la empresa{% else %}cualquiera{% endif %} con la URL de dicho tablero de proyecto. diff --git a/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md index 1c7d07ad87..48c1a05b07 100644 --- a/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/es-ES/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ Cuando seleccionas la opción **Rebase and merge** (Cambiar de base y fusionar) Para cambiar de base y fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) en el repositorio, y el repositorio debe [permitir la fusión de cambio de base](/articles/configuring-commit-rebasing-for-pull-requests/). -El comportamiento de cambio de base y de fusión en {% data variables.product.product_name %} varía levemente con respecto a `git rebase`. El cambio de base y la fusión en {% data variables.product.prodname_dotcom %} siempre actualizarán la información de la persona que confirma el cambio y crearán nuevas SHA de confirmación, mientras que el `git rebase` externo a {% data variables.product.prodname_dotcom %} no cambia la información de la persona que confirma el cambio cuando ocurre el cambio de base superponiendo un compromiso de antepasado. Para obtener más información sobre `git rebase`, consulta [el capítulo "Git rebase" del libro _Pro Git_](https://git-scm.com/docs/git-rebase). +El comportamiento de cambio de base y de fusión en {% data variables.product.product_name %} varía levemente con respecto a `git rebase`. El cambio de base y la fusión en {% data variables.product.prodname_dotcom %} siempre actualizarán la información de la persona que confirma el cambio y crearán nuevas SHA de confirmación, mientras que el `git rebase` externo a {% data variables.product.prodname_dotcom %} no cambia la información de la persona que confirma el cambio cuando ocurre el cambio de base superponiendo un compromiso de antepasado. For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). Para obtener una representación visual de `git rebase`, consulta [el capítulo "Ramas de Git - Cambio de base" del libro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md index 3526e39a78..4d9ffbdc17 100644 --- a/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/es-ES/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1 +1 @@ -Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. +Los administradores de repositorio pueden requerir que las solicitudes de cambios reciban una cantidad específica de revisiones de aprobación antes de que alguien fusione la solicitud de extracción en una rama protegida. Puedes requerir revisiones de aprobación de personas con permisos de escritura en el repositorio o de un propietario de código designado. diff --git a/translations/es-ES/data/reusables/repositories/branch-rules-example.md b/translations/es-ES/data/reusables/repositories/branch-rules-example.md index ea81704455..35e7d82708 100644 --- a/translations/es-ES/data/reusables/repositories/branch-rules-example.md +++ b/translations/es-ES/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. +Puedes crear una regla de protección de rama en un repositorio para la rama específica, todas las ramas, o cualquier rama que coincida con un patrón de nombre que especifiques con la sintaxis `fnmatch`. Por ejemplo, para proteger cualquier rama que contenga la palabra `release`, puedes crear una regla de rama de `*release*`. diff --git a/translations/es-ES/data/reusables/repositories/reaction_list.md b/translations/es-ES/data/reusables/repositories/reaction_list.md index 7851fb8b55..e7f34abc15 100644 --- a/translations/es-ES/data/reusables/repositories/reaction_list.md +++ b/translations/es-ES/data/reusables/repositories/reaction_list.md @@ -4,7 +4,7 @@ | `-1` | :-1: | | `risa` | :smile: | | `confundido` | :confused: | -| `corazón` | :heart: | +| `heart` | :heart: | | `viva` | :tada: | | `cohete` | :rocket: | | `ojos` | :eyes: | diff --git a/translations/es-ES/data/reusables/repositories/return-to-source-diff.md b/translations/es-ES/data/reusables/repositories/return-to-source-diff.md index 89edde383e..6a33c18cbc 100644 --- a/translations/es-ES/data/reusables/repositories/return-to-source-diff.md +++ b/translations/es-ES/data/reusables/repositories/return-to-source-diff.md @@ -1,5 +1,5 @@ -1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review. +1. Puede que también quieras revisar el diff origen, ya que podría haber cambios en el archivo de bloqueo o de manifiesto que no cambian de dependencia o podrían haber dependencias que {% data variables.product.prodname_dotcom %} no puede procesar, las cuales, como resultado, no aparecen en la revisión de dependencias. - To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button. + Para regresar a la vista de diff orígen, da clic en el botón **{% octicon "code" aria-label="The source diff icon" %}**. ![El botón de diff origen](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md index cfe413d8a0..cb3cd9456e 100644 --- a/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/es-ES/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. +Incluso después de que todos los revisores hayan aprobado una solicitud de cambios, los colaboradores no pueden fusionar la solicitud de cambios si hay otra solicitud de cambios abierta que tenga una rama de encabezado que apunte a la misma confirmación y tenga revisiones rechazadas o pendientes. Alguien con permisos de escritura debe aprobar o descartar primero la revisión que está causando el bloqueo en el resto de las solicitudes de cambios. diff --git a/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 60b005a4e7..355550e15d 100644 --- a/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}Si existe una regla de rama protegida en tu repositorio, la cual requiera un historial de confirmaciones linear, debes permitir la fusión por combinación, la fusión por rebase, o ambas. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}Si existe una regla de rama protegida en tu repositorio, la cual requiera un historial de confirmaciones linear, debes permitir la fusión por combinación, la fusión por rebase, o ambas. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)".{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/workflow-notifications.md b/translations/es-ES/data/reusables/repositories/workflow-notifications.md index 12184e589e..5bdeaa220a 100644 --- a/translations/es-ES/data/reusables/repositories/workflow-notifications.md +++ b/translations/es-ES/data/reusables/repositories/workflow-notifications.md @@ -1,5 +1,5 @@ Si habilitas las notificaciones web o por correo electrónico para {% data variables.product.prodname_actions %}, recibirás una notificación cuando alguna ejecución de flujo de trabajo que hayas activado se complete. La notificación incluirá el estado de la ejecución de flujo de trabajo (que incluye ejecuciones exitosas, fallidas, neutrales y canceladas). También puedes elegir recibir una notificación solo cuando falle una ejecución de flujo de trabajo. -Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} +Las notificaciones par alos flujos de trabajo programados se envían al usuario que creó el flujo de trabajo inicialmente. Si un usuario diferente actualiza la sintaxis de cron en el archivo de flujo de trabajo, las notificaciones subsecuentes se enviarán a este usuario en vez de al otro.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Si se inhabilita un flujo de trabajo y luego se rehabilita, las notificaciones se enviarán a aquél usuario que haya rehabilitado el flujo de trabajo en vez de al que modificó la sintaxis de cron por última vez.{% endif %} También puedes ver el estado de las ejecuciones de flujo de trabajo en la pestaña Actions (Acciones) de un repositorio. 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)". diff --git a/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md index ba92edc2a7..462d548e3e 100644 --- a/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/es-ES/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -Si utilizas a Okta como tu IdP, puedes utilizar SCIM para adminsitrar la membrecía de tu organización en tu cuenta empresarial. SCIM invita a las personas o las elimina de una organización en tu cuenta empresarial automáticamente con base en si son miembros del grupo que corresponde a cada organización en tu IdP o no. +If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM invita a las personas o las elimina de una organización en tu cuenta empresarial automáticamente con base en si son miembros del grupo que corresponde a cada organización en tu IdP o no. diff --git a/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md b/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md index be784eeb4f..5b92a97ddc 100644 --- a/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/es-ES/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +El inicio de sesión único (SSO) de SAML proporciona a los propietarios de las organizaciones y empresas en {% data variables.product.prodname_dotcom %} una forma de controlar y asegurar el acceso a los recursos organizacionales como los repositorios, propuestas y solicitudes de cambios. diff --git a/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md b/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md index 51b8c7a7d1..f9b18267cb 100644 --- a/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md +++ b/translations/es-ES/data/reusables/secret-scanning/about-secret-scanning.md @@ -1 +1 @@ -If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. +Si alguien registra un secreto de un socio de {% data variables.product.company_short %} en un repositorio {% if currentVersion == "free-pro-team@latest" %}público o privado{% endif %} de {% data variables.product.product_name %}, el {% data variables.product.prodname_secret_scanning %} captura el secreto de acuerdo a como se haya registrado y te ayuda a mitigar el impacto de la fuga. Se notifica a los administradores de repositorio sobre cualquier confirmación que contenga un secreto y pueden ver rápidamente todos los secretos en la pestaña de seguridad de éste. diff --git a/translations/es-ES/data/reusables/secret-scanning/beta.md b/translations/es-ES/data/reusables/secret-scanning/beta.md index 82fdadded9..b19f26a8c8 100644 --- a/translations/es-ES/data/reusables/secret-scanning/beta.md +++ b/translations/es-ES/data/reusables/secret-scanning/beta.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. +**Nota:** El {% data variables.product.prodname_secret_scanning_caps %} para los repositorios{% if currentVersion ver_gt "enterprise-server@2.22" %} públicos y{% endif %} privados que pertenecen a las organizaciones se encuentra acutalmente en beta y está sujeto a cambios. {% endnote %} diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 8e221eef6d..a7569fd7ba 100644 --- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -1,70 +1,70 @@ -| Partner | Supported secret | API slug | -| ------------------------- | -------------------------------------- | ---------------------------------------- | -| n/a | JSON Web Token | json_web_token | -| n/a | OAuth Client Credential | api_credential_assignment | -| Adafruit IO | Adafruit IO Key | adafruit_io_key | -| Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | -| Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret | -| Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id | -| Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key | -| Atlassian | Atlassian API Token | atlassian_api_token | -| Atlassian | Atlassian JSON Web Token | atlassian_jwt | -| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | -| Azure | Azure SAS Token | azure_sas_token | -| Azure | Azure Service Management Certificate | azure_management_certificate | -| Azure | Azure SQL Connection String | azure_sql_connection_string | -| Azure | Azure Storage Account Key | azure_storage_account_key | -| Clojars | Clojars Deploy Token | clojars_deploy_token | -| CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential | -| Databricks | Databricks Access Token | databricks_access_token | -| Discord | Discord Bot Token | discord_bot_token | -| Doppler | Doppler Personal Token | doppler_personal_token | -| Doppler | Doppler Service Token | doppler_service_token | -| Doppler | Doppler CLI Token | doppler_cli_token | -| Doppler | Doppler SCIM Token | doppler_scim_token | -| Dropbox | Dropbox Access Token | dropbox_access_token | -| Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token | -| Dynatrace | Dynatrace Access Token | dynatrace_access_token | -| Dynatrace | Dynatrace Internal Token | dynatrace_internal_token | -| Finicity | Finicity App Key | finicity_app_key | -| Frame.io | Frame.io JSON Web Token | frameio_jwt | -| Frame.io | Frame.io Developer Token | frameio_developer_token | -| GitHub | GitHub SSH Private Key | github_ssh_private_key | -| GitHub | GitHub Personal Access Token | github_personal_access_token | -| GitHub | GitHub App Installation Access Token | github_app_installation_access_token | -| GoCardless | GoCardless Live Access Token | gocardless_live_access_token | -| GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token | -| Google Cloud | Google API Key | google_api_key | -| Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id | -| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | -| Hubspot | Hubspot API Key | hubspot_api_key | -| Mailchimp | Mailchimp API Key | mailchimp_api_key | -| Mailgun | Mailgun API Key | mailgun_api_key | -| npm | npm Access Token | npm_access_token | -| NuGet | NuGet API Key | nuget_api_key | -| Palantir | Palantir JSON Web Token | palantir_jwt | -| Postman | Postman API Key | postman_api_key | -| Proctorio | Proctorio Consumer Key | proctorio_consumer_key | -| Proctorio | Proctorio Linkage Key | proctorio_linkage_key | -| Proctorio | Proctorio Registration Key | proctorio_registration_key | -| Proctorio | Proctorio Secret Key | proctorio_secret_key | -| Pulumi | Pulumi Access Token | pulumi_access_token | -| Samsara | Samsara API Token | samsara_api_token | -| Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | -| 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 | -| Stripe | Stripe Live API Secret Key | stripe_live_secret_key | -| Stripe | Stripe Test API Secret Key | stripe_test_secret_key | -| Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key | -| Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key | -| Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id | -| Twilio | Twilio Account String Identifier | twilio_account_sid | -| Twilio | Twilio API Key | twilio_api_key | +| Socio | Secreto compatible | Slug de la API | +| ------------------------- | --------------------------------------------------- | ---------------------------------------- | +| n/a | Token Web de JSON | json_web_token | +| n/a | Credencial de Cliente de OAuth | api_credential_assignment | +| Adafruit IO | Clave de IO de Adafruit | adafruit_io_key | +| Alibaba Cloud | ID de Clave de Acceso a la Nube de Alibaba | alibaba_cloud_access_key_id | +| Alibaba Cloud | Secreto de Clave de Acceso a la Nube de Alibaba | alibaba_cloud_access_key_secret | +| Amazon Web Services (AWS) | ID de Clave de Acceso de AWS de Amazon | aws_access_key_id | +| Amazon Web Services (AWS) | Clave de Acceso Secreta de AWS de Amazon | aws_secret_access_key | +| Atlassian | Token de API de Atlassian | atlassian_api_token | +| Atlassian | Token Web de JSON de Atlassian | atlassian_jwt | +| Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token | +| Azure | Token de Azure SAS | azure_sas_token | +| Azure | Certificado de Administración de Servicios de Azure | azure_management_certificate | +| Azure | Secuencia de Conexión de Azure SQL | azure_sql_connection_string | +| Azure | Clave de Cuenta de Almacenamiento de Azure | azure_storage_account_key | +| Clojars | Token de Despliegue de Clojars | clojars_deploy_token | +| CloudBees CodeShip | Credencial de Codeship de CloudBees | codeship_credential | +| Databricks | Token de Acceso de Databricks | databricks_access_token | +| Discord | Token de Bot de Discord | discord_bot_token | +| Doppler | Token Personal de Doppler | doppler_personal_token | +| Doppler | Token de Servicio de Doppler | doppler_service_token | +| Doppler | Token de CLI de Doppler | doppler_cli_token | +| Doppler | Token de SCIM de Doppler | doppler_scim_token | +| Dropbox | Token de Acceso de Dropbox | dropbox_access_token | +| Dropbox | Token de Acceso de Vida Corta de Dropbox | dropbox_short_lived_access_token | +| Dynatrace | Token de Acceso de Dynatrace | dynatrace_access_token | +| Dynatrace | Token Interno de Dynatrace | dynatrace_internal_token | +| Finicity | Clave de App de Finicity | finicity_app_key | +| Frame.io | Token Web de JSON de Frame.io | frameio_jwt | +| Frame.io | Token de Desarrollador de Frame.io | frameio_developer_token | +| GitHub | Clave Privada de SSH de GitHub | github_ssh_private_key | +| GitHub | Token de Acceso Personal de GitHub | github_personal_access_token | +| GitHub | Token de Acceso a la Instalación de GitHub App | github_app_installation_access_token | +| GoCardless | Token de Acceso en Vivo a GoCardless | gocardless_live_access_token | +| GoCardless | Token de Acceso de GoCardless Sandbox | gocardless_sandbox_access_token | +| Google Cloud | Clave de API de Google | google_api_key | +| Google Cloud | ID de Clave Privada de Google Cloud | google_cloud_private_key_id | +| Hashicorp Terraform | Token de API de Terraform Cloud / Enterprise | terraform_api_token | +| Hubspot | Clave de API de Hubspot | hubspot_api_key | +| Mailchimp | Clave de API de Mailchimp | mailchimp_api_key | +| Mailgun | Clave de API de Mailgun | mailgun_api_key | +| npm | Token de Acceso de npm | npm_access_token | +| NuGet | Clave de API de NuGet | nuget_api_key | +| Palantir | Token Web de JSON de Palantir | palantir_jwt | +| Postman | Clave de API de Postman | postman_api_key | +| Proctorio | Clave de Consumidor de Proctorio | proctorio_consumer_key | +| Proctorio | Clave de Enlace de Proctorio | proctorio_linkage_key | +| Proctorio | Clave de Registro de Proctorio | proctorio_registration_key | +| Proctorio | Clave de Secreto de Proctorio | proctorio_secret_key | +| Pulumi | Token de Acceso de Pulumi | pulumi_access_token | +| Samsara | Token de API de Samsara | samsara_api_token | +| Samsara | Token de Acceso de OAuth de Samsara | samsara_oauth_access_token | +| Shopify | Secreto Compartid de la App de Shopify | shopify_app_shared_secret | +| Shopify | Token de Acceso de Shopify | shopify_access_token | +| Shopify | Token de Acceso de la App Personalizada de Shopify | shopify_custom_app_access_token | +| Shopify | Contraseña de la App Privada de Shopify | shopify_private_app_password | +| Slack | Token de la API de Slack | slack_api_token | +| Slack | URL Entrante de Webhook de Slack | slack_incoming_webhook_url | +| Slack | URL de Flujo de Trabajo de Webhook de Slack | slack_workflow_webhook_url | +| SSLMate | Clave de API de SSLMate | sslmate_api_key | +| SSLMate | Secreto de Agrupamiento de SSLMate | sslmate_cluster_secret | +| Stripe | Clave de API de Stripe | stripe_api_key | +| Stripe | Clave de Secreto Stripe Live | stripe_live_secret_key | +| Stripe | Clave Secreta de API de Pruebas de Stripe | stripe_test_secret_key | +| Stripe | Clave Restringida de API de Stripe Live | stripe_live_restricted_key | +| Stripe | Clave Restringida de API de Pruebas de Stripe | stripe_test_restricted_key | +| Tencent Cloud | ID de Secreto de Tencent Cloud | tencent_cloud_secret_id | +| Twilio | Identificador de Secuencia de Cuenta de Twilio | twilio_account_sid | +| Twilio | Clave de API de Twilio | twilio_api_key | diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md index c6d391e3b6..75dbd8cac0 100644 --- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -1,69 +1,69 @@ -| Partner | Supported secret | -| ------------------------- | --------------------------------------------------------------------------- | -| Adafruit IO | Adafruit IO Key | -| Alibaba Cloud | Alibaba Cloud Access Key ID and Access Key Secret pair | -| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair | -| Atlassian | Atlassian API Token | -| Atlassian | Atlassian JSON Web Token | -| Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token | -| Azure | Azure SAS Token | azure_sas_token | -| Azure | Azure Service Management Certificate | azure_management_certificate | -| Azure | Azure SQL Connection String | azure_sql_connection_string | -| Azure | Azure Storage Account Key | azure_storage_account_key | -| Clojars | Clojars Deploy Token | -| CloudBees CodeShip | CloudBees CodeShip Credential | -| Databricks | Databricks Access Token | -| Datadog | Datadog API Key | -| Discord | Discord Bot Token | -| Doppler | Doppler Personal Token | -| Doppler | Doppler Service Token | -| Doppler | Doppler CLI Token | -| Doppler | Doppler SCIM Token | -| Dropbox | Dropbox Access Token | -| Dropbox | Dropbox Short Lived Access Token | -| Dynatrace | Dynatrace Access Token | -| Dynatrace | Dynatrace Internal Token | -| Finicity | Finicity App Key | -| Frame.io | Frame.io JSON Web Token | -| Frame.io | Frame.io Developer Token | -| GitHub | GitHub SSH Private Key | -| GitHub | GitHub Personal Access Token | -| GitHub | GitHub App Installation Access Token | -| GoCardless | GoCardless Live Access Token | -| GoCardless | GoCardless Sandbox Access Token | -| Google Cloud | Google API Key | -| Google Cloud | Google Cloud Private Key ID | -| Hashicorp Terraform | Terraform Cloud / Enterprise API Token | -| Hubspot | Hubspot API Key | -| Mailchimp | Mailchimp API Key | -| Mailchimp | Mandrill API Key | -| Mailgun | Mailgun API Key | -| MessageBird | MessageBird API Key | -| npm | npm Access Token | -| NuGet | NuGet API Key | -| Palantir | Palantir JSON Web Token | -| Plivo | Plivo Auth Token | -| Postman | Postman API Key | -| Proctorio | Proctorio Consumer Key | -| Proctorio | Proctorio Linkage Key | -| Proctorio | Proctorio Registration Key | -| Proctorio | Proctorio Secret Key | -| Pulumi | Pulumi Access Token | -| Samsara | Samsara API Token | -| Samsara | Samsara OAuth Access Token | -| Shopify | Shopify App Shared Secret | -| Shopify | Shopify Access Token | -| Shopify | Shopify Custom App Access Token | -| Shopify | Shopify Private App Password | -| Slack | Slack API Token | -| Slack | Slack Incoming Webhook URL | -| Slack | Slack Workflow Webhook URL | -| SSLMate | SSLMate API Key | -| SSLMate | SSLMate Cluster Secret | -| Stripe | Stripe Live API Secret Key | -| Stripe | Stripe Test API Secret Key | -| Stripe | Stripe Live API Restricted Key | -| Stripe | Stripe Test API Restricted Key | -| Tencent Cloud | Tencent Cloud Secret ID | -| Twilio | Twilio Account String Identifier | -| Twilio | Twilio API Key | +| Socio | Secreto compatible | +| ------------------------- | ------------------------------------------------------------------------------------ | +| Adafruit IO | Clave de IO de Adafruit | +| Alibaba Cloud | Par de ID y Secreto de Clave de Acceso a la Nube de Alibaba | +| Amazon Web Services (AWS) | Par de ID y Secreto de Clave de Acceso a AWS de Amazon | +| Atlassian | Token de API de Atlassian | +| Atlassian | Token Web de JSOn de Atlazzian | +| Azure | Token de Acceso Personal para Azure DevOps | azure_devops_personal_access_token | +| Azure | Token de Azure SAS | azure_sas_token | +| Azure | Certificado de Administración de Servicios de Azure | azure_management_certificate | +| Azure | Secuencia de Conexión de SQL de Azure | azure_sql_connection_string | +| Azure | Clave de Cuenta de Almacenamiento de Azure | azure_storage_account_key | +| Clojars | Token de Despliegue de Clojars | +| CloudBees CodeShip | Credencial de Codeship de CloudBees | +| Databricks | Token de Acceso de Databricks | +| Datadog | Clave de API de Datadog | +| Discord | Token de Bot de Discord | +| Doppler | Token Personal de Doppler | +| Doppler | Token de Servicio de Doppler | +| Doppler | Token de CLI de Doppler | +| Doppler | Token de SCIM de Doppler | +| Dropbox | Token de Acceso de Dropbox | +| Dropbox | Token de Acceso de Vida Corta de Dropbox | +| Dynatrace | Token de Acceso de Dynatrace | +| Dynatrace | Token Interno de Dynatrace | +| Finicity | Clave de App de Finicity | +| Frame.io | Token Web de JSON de Frame.io | +| Frame.io | Token de Desarrollador de Frame.io | +| GitHub | Clave Privada de SSH de GitHub | +| GitHub | Token de Acceso Personal de GitHub | +| GitHub | Token de Acceso a la Instalación de GitHub App | +| GoCardless | Token de Acceso en Vivo a GoCardless | +| GoCardless | Token de Acceso de GoCardless Sandbox | +| Google Cloud | Clave de API de Google | +| Google Cloud | ID de Clave Privada de Google Cloud | +| Hashicorp Terraform | Token de API de Terraform Cloud / Enterprise | +| Hubspot | Clave de API de Hubspot | +| Mailchimp | Clave de API de Mailchimp | +| Mailchimp | Clave de API de Mandrill | +| Mailgun | Clave de API de Mailgun | +| MessageBird | Clave de API de MessageBird | +| npm | Token de Acceso de npm | +| NuGet | Clave de API de NuGet | +| Palantir | Token Web de JSON de Palantir | +| Plivo | Token de Plivo Auth | +| Postman | Clave de API de Postman | +| Proctorio | Clave de Consumidor de Proctorio | +| Proctorio | Clave de Enlace de Proctorio | +| Proctorio | Clave de Registro de Proctorio | +| Proctorio | Clave de Secreto de Proctorio | +| Pulumi | Token de Acceso de Pulumi | +| Samsara | Token de API de Samsara | +| Samsara | Token de Acceso de OAuth de Samsara | +| Shopify | Secreto Compartid de la App de Shopify | +| Shopify | Token de Acceso de Shopify | +| Shopify | Token de Acceso de la App Personalizada de Shopify | +| Shopify | Contraseña de la App Privada de Shopify | +| Slack | Token de la API de Slack | +| Slack | URL Entrante de Webhook de Slack | +| Slack | URL de Flujo de Trabajo de Webhook de Slack | +| SSLMate | Clave de API de SSLMate | +| SSLMate | Secreto de Agrupamiento de SSLMate | +| Stripe | Clave de Secreto Stripe Live | +| Stripe | Clave Secreta de API de Pruebas de Stripe | +| Stripe | Clave Restringida de API de Stripe Live | +| Stripe | Clave Restringida de API de Pruebas de Stripe | +| Tencent Cloud | ID de Secreto de Tencent Cloud | +| Twilio | Identificador de Secuencia de Cuenta de Twilio | +| Twilio | Clave de API de Twilio | diff --git a/translations/es-ES/data/reusables/support/ghae-priorities.md b/translations/es-ES/data/reusables/support/ghae-priorities.md index 5bdbffd39e..16761120b0 100644 --- a/translations/es-ES/data/reusables/support/ghae-priorities.md +++ b/translations/es-ES/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | Prioridad | Descripción | Ejemplos | |:---------------------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | No se puede acceder a {% data variables.product.product_name %} o hay un fallo total, y dicho fallo impacta directamente en la operación de tu negocio.

    _Después de que emitas un ticket de soporte, llama a {% data variables.contact.github_support %} por teléfono_ |
    • Errores o suspensiones que afectan la funcionalidad central de Git o de la aplicación web para todos los usuarios
    • Degradación severa del rendmimiento o de la red para la mayoría de los usuarios
    • Almacenamiento agotado, o que se llena muy rápidamente
    • Incidentes de seguridad conocidos o una violación de acceso
    | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falla en un ambiente productivo, con un impacto limitado a tus procesos de negocio, o afectando únicamente a ciertos clientes. |
    • Degradación del rendimiento que reduce la productividad para muchos usuarios
    • Preocupaciones de redundancia reducida ocasionada por los fallos o la degradación del servicio
    • Errores o fallos que impactan a los ambientes productivos
    • {% data variables.product.product_name %} configuration security concerns
    | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falla en un ambiente productivo, con un impacto limitado a tus procesos de negocio, o afectando únicamente a ciertos clientes. |
    • Degradación del rendimiento que reduce la productividad para muchos usuarios
    • Preocupaciones de redundancia reducida ocasionada por los fallos o la degradación del servicio
    • Errores o fallos que impactan a los ambientes productivos
    • Problemas de seguridad en la configuración de {% data variables.product.product_name %}
    | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} está presentando problemas moderados o limitados y errores con {% data variables.product.product_name %}, o tienes problemas o preguntas en general sobre la operación de {% data variables.product.product_name %}. |
    • Consejos sobre como utilizar las API y las características de {% data variables.product.prodname_dotcom %}, o preguntas sobre cómo integrar los flujos de trabajo de negocios
    • Problemas con las herramientas de usuario y los métodos de recolección de datos
    • Actualizaciones
    • Reportes de errores, preguntas generales sobre la seguridad, u otras preguntas relacionadas con las características
      • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} funciona de acuerdo a lo esperado, sin embargo, tienes una pregunta o sugerencia sobre {% data variables.product.product_name %} que no es urgente o que no bloquea de otra forma la productividad de tu equipo. |
      • Solicitudes de características y retroalimentación sobre el producto
      • Las preguntas generales sobre la configuración o el uso general de {% data variables.product.product_name %}
      • Notificar a {% data variables.contact.github_support %} de cualquier cambio planeado
      | diff --git a/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md b/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md index 8fbdcdb4c6..0cdd78fbf0 100644 --- a/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/es-ES/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. Desplázate hacia abajo a la sección de Marketplace y da clic en **Editar listado de Marketplace**. La sección de Marketplace solo se encuentra visible si permites que cualquier usuario u organización instale tu app cuando la registras. Para obtener más información, consulta la lista de [Requisitos de Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![enlace para editar tu listado de GitHub Marketplace](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. La sección de Marketplace solo se encuentra visible si permites que cualquier usuario u organización instale tu app cuando la registras. Para obtener más información, consulta la lista de [Requisitos de Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![enlace para editar tu listado de GitHub Marketplace](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md index ae43f35c1f..250d772614 100644 --- a/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md +++ b/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md @@ -1 +1 @@ -1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file +1. Selecciona el menú desplegable de "Acceso al repositorio" y luego da clic en aquél a cuyo secreto quieras acceder. Repite esto para cada repositorio del cual quieras tener acceso al secreto. ![Menú desplegable de "Acceso al repositorio"](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md b/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md index 82cb0fbffe..246e6ab228 100644 --- a/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md +++ b/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md @@ -1 +1 @@ -1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file +1. Debajo de "Valor", teclea el valor de tu secreto. ![Caja de texto de "Valor"](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md index e4908fcf75..69002607f8 100644 --- a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md +++ b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md @@ -1 +1 @@ -1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file +1. En la barra lateral izquierda, da clic en **Codespaces**. ![Pestaña de Codespaces en la barra lateral de la configuración de usuario](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/webhooks/check_run_properties.md b/translations/es-ES/data/reusables/webhooks/check_run_properties.md index 52cd67ae99..5d195e8601 100644 --- a/translations/es-ES/data/reusables/webhooks/check_run_properties.md +++ b/translations/es-ES/data/reusables/webhooks/check_run_properties.md @@ -1,11 +1,11 @@ | Clave | Type | Descripción | | --------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
      • `created` - Se creó una ejecución de verificación.
      • `completed` - El `status` de la ejecución de verificación es `completed`.
      • `rerequested` - Alguien volvió a solicitar que se volviera a ejecutar tu ejecución de verificación desde la IU de la solicitud de extracción. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub. Cuando recibes una acción de tipo `rerequested`, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó volver a ejecutar la verificación recibirá la carga útil de `rerequested`.
      • `requested_action` - Alguien volvió a solicitar que se tome una acción que proporciona tu app. Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó llevar a cabo una acción recibirá la carga útil de `requested_action`. Para aprender más sobre las ejecuciones de verificación y las acciones solicitadas, consulta la sección "[Ejecuciones de ferificación y acciones solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
      | -| `check_run` | `object` | La [check_run](/rest/reference/checks#get-a-check-run). | +| `check_run` | `objeto` | La [check_run](/rest/reference/checks#get-a-check-run). | | `check_run[status]` | `secuencia` | El estado actual de la ejecución de verificación. Puede ser `queued`, `in_progress`, o `completed`. | | `check_run[conclusion]` | `secuencia` | El resultado de la ejecución de verificación que se completó. Puede ser uno de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | | `check_run[name]` | `secuencia` | El nombre de la ejecución de verificación. | | `check_run[check_suite][id]` | `número` | La id de la suite de verificaciones de la cual es parte esta ejecución de verificación. | | `check_run[check_suite][pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de extracción que empata con una suite de verificaciones si tienen el mismo `head_sha` y `head_branch`. Cuando la `head_branch` de la suite de verificaciones está en un repositorio bifurcado, este será `null` y la matriz de `pull_requests` estará vacía. | -| `requested_action` | `object` | La acción que solicitó el usuario. | +| `requested_action` | `objeto` | La acción que solicitó el usuario. | | `requested_action[identifier]` | `secuencia` | La referencia del integrador de la acción que solicitó el usuario. | diff --git a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md index 2788d1bb49..25fb9138e2 100644 --- a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md +++ b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md @@ -1,7 +1,7 @@ | Clave | Type | Descripción | | ---------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción realizada. Puede ser:
      • `completed` - Todas las ejecuciones de verificación en una suite de verificación se completaron.
      • `requested` - Ocurre cuando se carga código nuevo al repositorio de la app. Cuando recibes un evento de acción de tipo `requested`, necesitarás [Crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run).
      • `rerequested` - Ocurre cuando alguien solicita volver a ejecutar toda la suite de verificaciones desde la IU de la solicitud de extracción. Cuando recibes los eventos de una acción de tipo `rerequested, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub.
      | -| `check_suite` | `object` | La [check_suite](/rest/reference/checks#suites). | +| `check_suite` | `objeto` | La [check_suite](/rest/reference/checks#suites). | | `check_suite[head_branch]` | `secuencia` | El nombre de la rama principal en la cual están los cambios. | | `check_suite[head_sha]` | `secuencia` | El SHA de la confirmación más reciente para esta suite de verificaciones. | | `check_suite[status]` | `secuencia` | El estado de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser `requested`, `in_progress`, o `completed`. | diff --git a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md index 6e32e080ef..9441931186 100644 --- a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md +++ b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md @@ -1,6 +1,6 @@ | Clave | Type | Descripción | | ------------ | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Este puede ser uno de entre `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, o `reopened`. | -| `alert` | `object` | La alerta de escaneo de código involucrada en el evento. | +| `alerta` | `objeto` | La alerta de escaneo de código involucrada en el evento. | | `ref` | `secuencia` | La referencia de Git de la alerta de escaneo de código. Cuando la acción es `reopened_by_user` o `closed_by_user`, el `sender` es quien activó el evento y este valor estará vacío. | | `commit_oid` | `secuencia` | El SHA de la confirmación de la alerta del escaneo de código. Cuando la acción es `reopened_by_user` o `closed_by_user`, el `sender` es quien activó el evento y este valor estará vacío. | diff --git a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md index a612edded1..5a09adfbf2 100644 --- a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md +++ b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | -| --------- | ----------- | ------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. | -| `comment` | `object` | El recurso de [comentario de la confirmación](/rest/reference/repos#get-a-commit-comment). | +| Clave | Type | Descripción | +| ------------ | ----------- | ------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. | +| `comentario` | `objeto` | El recurso de [comentario de la confirmación](/rest/reference/repos#get-a-commit-comment). | diff --git a/translations/es-ES/data/reusables/webhooks/create_properties.md b/translations/es-ES/data/reusables/webhooks/create_properties.md index 987b737e98..5b3220dab6 100644 --- a/translations/es-ES/data/reusables/webhooks/create_properties.md +++ b/translations/es-ES/data/reusables/webhooks/create_properties.md @@ -3,4 +3,4 @@ | `ref` | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference). | | `ref_type` | `secuencia` | El tipo de objeto de Git ref que se creó en el repositorio. Puede ser `branch` o `tag`. | | `master_branch` | `secuencia` | El nombre de la rama predeterminada del repositorio (habitualmente {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" %}`main`{% else %}`master`{% endif %}). | -| `description` | `secuencia` | La descripción actual del repositorio. | +| `descripción` | `secuencia` | La descripción actual del repositorio. | diff --git a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md index f359bc37f4..d1e29d86b4 100644 --- a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md +++ b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md @@ -1,4 +1,4 @@ | Clave | Type | Descripción | | -------- | ----------- | ------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`. | -| `clave` | `object` | El recurso [`deploy key`](/rest/reference/repos#get-a-deploy-key). | +| `clave` | `objeto` | El recurso [`deploy key`](/rest/reference/repos#get-a-deploy-key). | diff --git a/translations/es-ES/data/reusables/webhooks/fork_properties.md b/translations/es-ES/data/reusables/webhooks/fork_properties.md index 1480462d77..a00605b049 100644 --- a/translations/es-ES/data/reusables/webhooks/fork_properties.md +++ b/translations/es-ES/data/reusables/webhooks/fork_properties.md @@ -1,3 +1,3 @@ | Clave | Type | Descripción | | -------- | -------- | --------------------------------------------------------------------------------- | -| `forkee` | `object` | El recurso de [`repository`](/rest/reference/repos#get-a-repository) que se creó. | +| `forkee` | `objeto` | El recurso de [`repository`](/rest/reference/repos#get-a-repository) que se creó. | diff --git a/translations/es-ES/data/reusables/webhooks/membership_properties.md b/translations/es-ES/data/reusables/webhooks/membership_properties.md index 44c7354e38..eb5e6b565c 100644 --- a/translations/es-ES/data/reusables/webhooks/membership_properties.md +++ b/translations/es-ES/data/reusables/webhooks/membership_properties.md @@ -1,6 +1,6 @@ -| Clave | Type | Descripción | -| -------- | ----------- | --------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser `added` o `removed`. | -| `scope` | `secuencia` | El alcance de la membrecía. Acutalmente, solo puede ser `team`. | -| `member` | `object` | El [usuario](/rest/reference/users) que se agregó o se eliminó. | -| `team` | `object` | El [equipo](/rest/reference/teams) para la membrecía. | +| Clave | Type | Descripción | +| --------- | ----------- | --------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser `added` o `removed`. | +| `alcance` | `secuencia` | El alcance de la membrecía. Acutalmente, solo puede ser `team`. | +| `miembro` | `objeto` | El [usuario](/rest/reference/users) que se agregó o se eliminó. | +| `equipo` | `objeto` | El [equipo](/rest/reference/teams) para la membrecía. | diff --git a/translations/es-ES/data/reusables/webhooks/milestone_properties.md b/translations/es-ES/data/reusables/webhooks/milestone_properties.md index 06486c0027..e875f5bc69 100644 --- a/translations/es-ES/data/reusables/webhooks/milestone_properties.md +++ b/translations/es-ES/data/reusables/webhooks/milestone_properties.md @@ -1,8 +1,8 @@ | Clave | Type | Descripción | | ---------------------------- | ----------- | ------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre: `created`, `closed`, `opened`, `edited`, o `deleted`. | -| `milestone` | `object` | El hito mismo. | -| `changes` | `object` | Los cambios al hito si la acción se encuentra como `edited`. | +| `hito` | `objeto` | El hito mismo. | +| `changes` | `objeto` | Los cambios al hito si la acción se encuentra como `edited`. | | `changes[description][from]` | `secuencia` | La versión previa de la descripción si la acción está como `edited`. | | `changes[due_on][from]` | `secuencia` | La versión previa de la fecha límite si la acción se puso como `edited`. | | `changes[title][from]` | `secuencia` | La versión previa del título si la acción se puso como `edited`. | diff --git a/translations/es-ES/data/reusables/webhooks/package_properties.md b/translations/es-ES/data/reusables/webhooks/package_properties.md index 6771591f64..0ed44ec297 100644 --- a/translations/es-ES/data/reusables/webhooks/package_properties.md +++ b/translations/es-ES/data/reusables/webhooks/package_properties.md @@ -1,4 +1,4 @@ | Clave | Type | Descripción | | --------- | ----------- | ------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Puede ser `published` o `updated`. | -| `package` | `object` | La información sobre el paquete. | +| `paquete` | `objeto` | La información sobre el paquete. | diff --git a/translations/es-ES/data/reusables/webhooks/project_card_properties.md b/translations/es-ES/data/reusables/webhooks/project_card_properties.md index 37ceb89f5c..d094490cdb 100644 --- a/translations/es-ES/data/reusables/webhooks/project_card_properties.md +++ b/translations/es-ES/data/reusables/webhooks/project_card_properties.md @@ -1,7 +1,7 @@ | Clave | Type | Descripción | | --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción llevada a cabo en la tarjeta del proyecto. Puede ser `created`, `edited`, `moved`, `converted`, o `deleted`. | -| `changes` | `object` | Los cambios a la tarjeta del proyecto si la acción se puso como `edited` o `converted`. | +| `changes` | `objeto` | Los cambios a la tarjeta del proyecto si la acción se puso como `edited` o `converted`. | | `changes[note][from]` | `secuencia` | La versión previa de la nota si la acción se puso como `edited` o `converted`. | | `after_id` | `número` | La id de la tarjeta a la cual sigue esta tarjeta ahora si la acción se "movió". Será `null` si es la primera tarjeta en una columna. | -| `project_card` | `object` | La [tarjeta de proyecto](/rest/reference/projects#cards) misma. | +| `project_card` | `objeto` | La [tarjeta de proyecto](/rest/reference/projects#cards) misma. | diff --git a/translations/es-ES/data/reusables/webhooks/project_column_properties.md b/translations/es-ES/data/reusables/webhooks/project_column_properties.md index 25cf36d585..fba0041ffb 100644 --- a/translations/es-ES/data/reusables/webhooks/project_column_properties.md +++ b/translations/es-ES/data/reusables/webhooks/project_column_properties.md @@ -1,7 +1,7 @@ | Clave | Type | Descripción | | --------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó en la columna de proyecto. Puede ser una de entre `created`, `edited`, `moved` o `deleted`. | -| `changes` | `object` | Los cambios a la columna del proyecto si la acción se puso como `edited`. | +| `changes` | `objeto` | Los cambios a la columna del proyecto si la acción se puso como `edited`. | | `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | | `after_id` | `número` | La id de la columna a la cual sigue ahora esta coumna si la acción se "movió". Será `null` si es la primera columna en un proyecto. | -| `project_column` | `object` | La [columna de proyecto](/rest/reference/projects#columns) misma. | +| `project_column` | `objeto` | La [columna de proyecto](/rest/reference/projects#columns) misma. | diff --git a/translations/es-ES/data/reusables/webhooks/project_properties.md b/translations/es-ES/data/reusables/webhooks/project_properties.md index 74323f9c8d..41f15ed400 100644 --- a/translations/es-ES/data/reusables/webhooks/project_properties.md +++ b/translations/es-ES/data/reusables/webhooks/project_properties.md @@ -1,7 +1,7 @@ | Clave | Type | Descripción | | --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó en el proyecto. Puede ser uno de entre: `created`, `edited`, `closed`, `reopened`, o `deleted`. | -| `changes` | `object` | Los cambios al proyecto si la acción se puso como `edited`. | +| `changes` | `objeto` | Los cambios al proyecto si la acción se puso como `edited`. | | `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | | `changes[body][from]` | `secuencia` | La versión previa del cuerpo si la acción se puso como `edited`. | -| `project` | `object` | El [proyecto](/rest/reference/projects) mismo. | +| `project` | `objeto` | El [proyecto](/rest/reference/projects) mismo. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md index 4871b22562..8505fcdce2 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | Clave | Type | Descripción | | ---------------------- | ----------- | ------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
      • `submitted` - Se emitió una solicitud de extracción en un estado no pendiente.
      • `edited` - el cuerpo de una revisión se editó.
      • `dismissed` - Se descartó una revisión.
      | -| `solicitud_extracción` | `object` | La [solicitud de extracción](/rest/reference/pulls) a la cual pertenece la revisión. | -| `review` | `object` | La revisión que se afectó. | +| `solicitud_extracción` | `objeto` | La [solicitud de extracción](/rest/reference/pulls) a la cual pertenece la revisión. | +| `revisar` | `objeto` | La revisión que se afectó. | | `changes[body][from]` | `secuencia` | La versión previa del cuerpo si la acción se puso como `edited`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md index 99319e4126..d704b5188f 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | -| -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, o `reopened`. Si la acción se muestra como `closed` y la llave `merged` es `false`, esto significa que la solicitud de extracción se cerró con las confirmaciones sin fusionar. Si la acción se muestra como `closed` y la llave `merged` es `true`, la solicitud de extracción se fusionó. | +| Clave | Type | Descripción | +| -------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. Si la acción se muestra como `closed` y la llave `merged` es `false`, esto significa que la solicitud de extracción se cerró con las confirmaciones sin fusionar. Si la acción se muestra como `closed` y la llave `merged` es `true`, la solicitud de extracción se fusionó. | diff --git a/translations/es-ES/data/reusables/webhooks/repository_import_properties.md b/translations/es-ES/data/reusables/webhooks/repository_import_properties.md index 99b3bc9b4a..b695be300b 100644 --- a/translations/es-ES/data/reusables/webhooks/repository_import_properties.md +++ b/translations/es-ES/data/reusables/webhooks/repository_import_properties.md @@ -1,3 +1,3 @@ | Clave | Type | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------------------- | -| `status` | `secuencia` | El estado final de la importación. Este puede ser alguno de entre: `success`, `cancelled`, o `failure`. | +| `estado` | `secuencia` | El estado final de la importación. Este puede ser alguno de entre: `success`, `cancelled`, o `failure`. | diff --git a/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md index 423ee34b5e..62f800c9ca 100644 --- a/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md +++ b/translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_properties.md @@ -1,4 +1,4 @@ | Clave | Type | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Este puede ser alguno de entre: `create`, `dismiss`, o `resolve`. | -| `alert` | `object` | La alerta de seguridad de la dependencia vulnerable. | +| `alerta` | `objeto` | La alerta de seguridad de la dependencia vulnerable. | diff --git a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md index a3ff7ef929..8c9ab1fa16 100644 --- a/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md +++ b/translations/es-ES/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -1,4 +1,4 @@ | Clave | Type | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Esta puede ser ya sea `created`, `resolved`, o `reopened`. | -| `alert` | `object` | La alerta del escaneo de secretos involucrada en el evento. | +| `alerta` | `objeto` | La alerta del escaneo de secretos involucrada en el evento. | diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml index 8a8200d9d2..c6b10f8c07 100644 --- a/translations/es-ES/data/ui.yml +++ b/translations/es-ES/data/ui.yml @@ -4,7 +4,7 @@ header: contact: Contacto notices: ghae_silent_launch: GitHub AE está actualmente en un lanzamiento limitado. Por favor, contacta a nuestro equipo de ventas para conocer más sobre esto. - release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' + release_candidate: '# El nombre de la versión se interpreta antes del texto siguiente a través de '' includes/header-notification.html '' se encuentra disponible actualmente como un candidato de lanzamiento. Para obtener más información, consulta la sección "Acerca de las mejoras para los lanzamientos nuevos".' localization_complete: Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos. localization_in_progress: '¡Hola, explorador! Esta página está bajo desarrollo activo o todavía está en la etapa de traducción. Para obtener información más actualizada y precisa, visita nuestra documentación en inglés.' early_access: '📣 Por favor, no compartas esta URL públicamente. Esta página tiene contenido sobre una característica de acceso temprano.' @@ -91,9 +91,9 @@ products: see_preview_notices: Ver avisos de previsualización preview_header_is_required: El encabezado es requerido footer: - all_rights_reserved: All rights reserved + all_rights_reserved: Todos los derechos reservados terms: Términos - privacy: Privacy + privacy: Privacidad security: Seguridad product: heading: Producto @@ -133,14 +133,24 @@ product_landing: reference_guides: Guías de referencia overview: Resumen product_sublanding: - start: Start - start_path: Start path - learning_paths: Learning paths - learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + start: Inicio + start_path: Ruta de inicio + learning_paths: Ruta de aprendizaje + learning_paths_desc: Las rutas de aprendizaje son una recopilación de guías que te ayudan a dominar un tema en particular. more_guides: más guías - guideTypes: + load_more: Carga más guías + all_guides: Todas las guías + no_result: Lo sentimos, no hay una guía que coincida con tu filtro. + filters: + type: Type + topic: Topic + all: Todas + guide_types: overview: Resumen quick_start: Inicio Rápido tutorial: Tutorial - how_to: How-to guide + how_to: Guía instruccional reference: Referencia +learning_track_nav: + prevGuide: Previous guide + nextGuide: Next guide diff --git a/translations/es-ES/data/variables/action_code_examples.yml b/translations/es-ES/data/variables/action_code_examples.yml index 90a7b96cf9..b44db3d5ea 100644 --- a/translations/es-ES/data/variables/action_code_examples.yml +++ b/translations/es-ES/data/variables/action_code_examples.yml @@ -144,7 +144,7 @@ languages: 'TypeScript, Shell, JavaScript' href: trilom/file-changes-action tags: - - workflow + - flujo de trabajo - repositorio - title: Acciones privadas en cualquier flujo de trabajo @@ -152,7 +152,7 @@ languages: 'TypeScript, JavaScript, Shell' href: InVisionApp/private-action-loader tags: - - workflow + - flujo de trabajo - tools - title: Etiqueta tus propuestas utilizando sus contenidos @@ -160,7 +160,7 @@ languages: 'JavaScript, TypeScript' href: damccorm/tag-ur-it tags: - - workflow + - flujo de trabajo - tools - etiquetas - propuestas @@ -170,7 +170,7 @@ languages: 'JavaScript' href: author/action-rollback tags: - - workflow + - flujo de trabajo - releases - title: Bloquear propuestas y solicitudes de cambios cerradas @@ -180,16 +180,16 @@ tags: - propuestas - solicitudes de extracción - - workflow + - flujo de trabajo - title: Obtiene un conteo de diferencias en confirmaciones entre dos ramas description: Esta GitHub Action compara dos ramas y te proporciona el conteo de confirmaciones entre ellas languages: 'JavaScript, Shell' href: jessicalostinspace/commit-difference-action tags: - - commit - - diff - - workflow + - confirmación + - diferencia + - flujo de trabajo - title: Genera notas de lanzamiento con base en las referencias de Git description: GitHub Action para generar registros de cambios y notas de lanzamiento @@ -198,7 +198,7 @@ tags: - cicd - notas de lanzamiento - - workflow + - flujo de trabajo - bitácora de Cambios - title: Requiere políticas en las confirmaciones y repositorios de GitHub @@ -208,7 +208,7 @@ tags: - docker - build-automation - - workflow + - flujo de trabajo - title: Auto Etiquetado Basado en Propuestas description: Etiqueta automáticamente una propuesta con base en su descripción @@ -216,7 +216,7 @@ href: Renato66/auto-label tags: - etiquetas - - workflow + - flujo de trabajo - automatización - title: Actualiza las GitHub Actions configuradas a sus últimas versiones @@ -226,7 +226,7 @@ tags: - versions - cli - - workflow + - flujo de trabajo - title: Crear Rama de Propuesta description: GitHub Action que automatiza la creación de ramas de propuestas @@ -243,7 +243,7 @@ href: c-hive/gha-remove-artifacts tags: - artefactos - - workflow + - flujo de trabajo - title: Sincroniza los archivos/binarios definidos a un Wiki o a repositorios externos description: GitHub Action para sincronizar automáticamente los cambios a los repositorios externos, como el wiki, por ejemplo @@ -252,7 +252,7 @@ tags: - wiki - sync - - workflow + - flujo de trabajo - title: Crea/Actualiza/Borra una página de Wiki de GitHub con base en cualquier archivo description: Actualiza tu wiki de GitHub utilizando rsync, lo cual permite la exclusión de archivops y directorios y el borrado real de los archivos @@ -261,7 +261,7 @@ tags: - wiki - docker - - workflow + - flujo de trabajo - title: GitHub Actions de Prow description: Automatización del requerimiento de políticas, chat-ops y fusión automática de PR @@ -270,16 +270,16 @@ tags: - chat-ops - prow - - workflow + - flujo de trabajo - title: Verifica el estado de GitHub en tu flujo de trabajo description: Verifica el estado de GitHub en tu flujo de trabajo languages: 'TypeScript, JavaScript' href: crazy-max/ghaction-github-status tags: - - status + - estado - supervisar - - workflow + - flujo de trabajo - title: Administra etiquetas en GitHub como código description: GitHub Action para administrar etiquetas (create/rename/update/delete) @@ -287,7 +287,7 @@ href: crazy-max/ghaction-github-labeler tags: - etiquetas - - workflow + - flujo de trabajo - automatización - title: Distribuir los fondos en los proyectos gratuitos y de código abierto @@ -316,7 +316,7 @@ tags: - codeowners - validar - - workflow + - flujo de trabajo - title: Acción Copybara description: Mueve y transfora el código entre los repositorios (ideal para mantener varios repositorios fuera de un mono-repositorio) @@ -325,7 +325,7 @@ tags: - monorepo - copybara - - workflow + - flujo de trabajo - title: Despliega archivos estáticos a GitHub Pages description: GitHub Action para publcar un sitio web en GitHub Pages automáticamente diff --git a/translations/es-ES/data/variables/enterprise.yml b/translations/es-ES/data/variables/enterprise.yml index b4884d8468..1b338f51c1 100644 --- a/translations/es-ES/data/variables/enterprise.yml +++ b/translations/es-ES/data/variables/enterprise.yml @@ -1,2 +1,2 @@ --- -management_console: 'Management Console' +management_console: 'Consola de administración' diff --git a/translations/es-ES/data/variables/gists.yml b/translations/es-ES/data/variables/gists.yml index 12c745fd3c..d41dfedd9a 100644 --- a/translations/es-ES/data/variables/gists.yml +++ b/translations/es-ES/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[página principal del gist](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}página principal del gist, `http(s)://gist.[hostname)`,{% else %}página principal del gist, `http(s)://[hostname]/gist` o `http(s)://gist.[hostname]` si se habilitan los subdominios{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Búsqueda de Gists](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Búsqueda de Gists, `http(s)://gist.[hostname]/search`,{% else %}Búsqueda de Gists, `http(s)://[hostname]/gist/search` o `http(s)://gist.[hostname]/search` si se habilitaron los subdominios{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Descubre, `http(s)://gist.[hostname]/discover`,{% else %}Descubre, `http(s)://[hostname]/gist/discover` o `http(s)://gist.[hostname]/discover` si se habilitaron los subdominios{% endif %} diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml index 47951b5530..c55d444783 100644 --- a/translations/es-ES/data/variables/product.yml +++ b/translations/es-ES/data/variables/product.yml @@ -32,8 +32,8 @@ prodname_enterprise_backup_utilities: 'Utilidades de respaldo del servidor de Gi #GitHub Connect (enterprise accounts, other unified features) ## Phrase content so that the uncapitalized unified contributions or unified search variables are not used at the start of a sentence. prodname_github_connect: 'GitHub Connect' -prodname_unified_contributions: 'unified contributions' -prodname_unified_search: 'unified search' +prodname_unified_contributions: 'contribuciones unificadas' +prodname_unified_search: 'búsqueda unificada' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: 'Education Community' @@ -52,7 +52,7 @@ prodname_mobile: 'GitHub para móviles' prodname_ios: 'GitHub para iOS' prodname_android: 'GitHub para Android' #GitHub Pages -prodname_pages: 'GitHub Pages' +prodname_pages: 'Páginas de GitHub' #CodeQL prodname_codeql: 'CodeQL' prodname_ql: 'QL' @@ -60,7 +60,8 @@ prodname_ql: 'QL' prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub App' prodname_github_apps: 'GitHub Apps' -prodname_oauth_app: 'OAuth App' +prodname_oauth_app: 'App OAuth' +prodname_oauth_apps: 'OAuth Apps' #API and developer docs prodname_enterprise_api: 'las API de {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %}' prodname_support_forum_with_url: '[Foro de desarrollo y soporte de la API de GitHub](https://github.community/c/github-api-development-and-support/37)' @@ -82,7 +83,7 @@ prodname_container_registry: 'registro de contenedores' prodname_insights: 'GitHub Insights' #GitHub Sponsors prodname_sponsors: 'Patrocinadores de GitHub' -prodname_matching_fund: 'GitHub Sponsors Matching Fund' +prodname_matching_fund: 'Fondo Compensatorio para Patrocinios de GitHub' #GitHub Advanced Security prodname_GH_advanced_security: 'GitHub Advanced Security' prodname_advanced_security: 'Advanced Security' @@ -93,7 +94,7 @@ prodname_github_codespaces: 'Acerca de GitHub Codespaces' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'Soporte de la Comunidad de GitHub' prodname_blog: 'el blog de GitHub' -prodname_jobs: 'GitHub Jobs' +prodname_jobs: 'Empleos GitHub' prodname_learning: 'Laboratorio de aprendizaje de GitHub' prodname_learning_link: 'https://lab.github.com/' prodname_roadmap: 'Itinerario público de GitHub' @@ -102,10 +103,10 @@ prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap' premium_support_plan: 'Plan prémium' premium_plus_support_plan: 'Premium Plus Plan/GitHub Engineering Direct' microsoft_premium_plus_support_plan: 'GitHub Engineering Direct' -support_ticket_priority_urgent: 'Urgent' -support_ticket_priority_high: 'High' +support_ticket_priority_urgent: 'Urgente' +support_ticket_priority_high: 'Alto' support_ticket_priority_normal: 'Normal' -support_ticket_priority_low: 'Low' +support_ticket_priority_low: 'Bajo' #Security features / code scanning platform / Security Lab prodname_security: 'GitHub Security Lab' prodname_security_link: 'https://securitylab.github.com/' diff --git a/translations/ja-JP/content/actions/creating-actions/about-actions.md b/translations/ja-JP/content/actions/creating-actions/about-actions.md index e63b6a950d..1b7dc050ef 100644 --- a/translations/ja-JP/content/actions/creating-actions/about-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/about-actions.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Action development + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ steps: #### コミットの SHA を使用したリリース管理 -各 Git コミットは、計算された SHA 値を受け取ります。これは一意で不変のものです。 アクションのユーザは、コミットの SHA 値に依存することを好む場合があります。削除や移動ができるタグを指定するよりこの方法のほうが信頼できるためです。 ただし、これは、ユーザがアクションに対して行われた更新をそれ以上受け取らないことを意味しています。 省略された値の代わりにコミットの完全な SHA 値を使用すると、同じ省略形を使用する悪意のあるコミットの使用を防ぐことができます。 +各 Git コミットは、計算された SHA 値を受け取ります。これは一意で不変のものです。 アクションのユーザは、コミットの SHA 値に依存することを好む場合があります。削除や移動ができるタグを指定するよりこの方法のほうが信頼できるためです。 ただし、これは、ユーザがアクションに対して行われた更新をそれ以上受け取らないことを意味しています。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}コミットのSHA値は、短縮値ではなく完全な値を使わなければなりません。{% else %}コミットのSHA値として短縮値でなく完全な値を使うことで、同じ短縮値を使う悪意あるコミットを使ってしまうことを回避しやすくなります、{% endif %} ```yaml steps: diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md index d4cbafbf51..f86f93ab21 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -1,11 +1,13 @@ --- title: 複合実行ステップ アクションの作成 -intro: 'このガイドでは、複合実行ステップ アクションを構築する方法について説明します。' +intro: このガイドでは、複合実行ステップ アクションを構築する方法について説明します。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Action development --- {% data reusables.actions.enterprise-beta %} @@ -65,12 +67,12 @@ type: 'tutorial' required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -122,7 +124,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md index 5f50de09d5..7fa0eb5b8f 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md @@ -1,6 +1,6 @@ --- title: Docker コンテナのアクションを作成する -intro: 'このガイドでは、Docker コンテナのアクションを作成するために最低限必要なステップを案内します。' +intro: このガイドでは、Docker コンテナのアクションを作成するために最低限必要なステップを案内します。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Action development + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ type: 'tutorial' 1. ターミナルから、ディレクトリを新しいリポジトリに変更します。 - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ type: 'tutorial' 新しい`hello-world-docker-action`ディレクトリ内に、新たに`Dockerfile`というファイルを作成してください。 詳しい情報については「[{% data variables.product.prodname_actions %}のためのDockerfileサポート](/actions/creating-actions/dockerfile-support-for-github-actions)」を参照してください。 **Dockerfile** -```dockerfile +```dockerfile{:copy} # コードを実行するコンテナイメージ FROM alpine:3.10 @@ -65,7 +68,7 @@ ENTRYPOINT ["/entrypoint.sh"] {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ runs: 1. `hello-world-docker-action` ディレクトリに、新しい `entrypoint.sh` を作成します。 -1. `entrypoint.sh`ファイルを実行可能にしてください。 - - ```shell - chmod +x entrypoint.sh - ``` - 1. `entrypoint.sh`ファイルに次のコードを追加します。 **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" time=$(date) echo "::set-output name=time::$time" ``` - `entrypoint.sh`がエラーなく実行できたら、アクションのステータスは`success`に設定されます。 アクションのコード中で明示的に終了コードを設定して、アクションのステータスを提供することもできます。 詳しい情報については「[アクションの終了コードの設定](/actions/creating-actions/setting-exit-codes-for-actions)」を参照してください。 +1. 以下のコマンドをシステムで実行して、`entrypoint.sh`ファイルを実行可能にしてください。 + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### READMEの作成 アクションの使用方法を説明するために、README ファイルを作成できます。 README はアクションの公開を計画している時に非常に役立ちます。また、アクションの使い方をあなたやチームが覚えておく方法としても優れています。 @@ -130,7 +132,7 @@ runs: - ワークフローでアクションを使う使用方法の例 **README.md** -```markdown +```markdown{:copy} # Hello world docker action このアクションは"Hello World"もしくは"Hello" + ログに挨拶する人物名を出力します。 @@ -160,7 +162,7 @@ with: アクションのリリースにはバージョンタグを加えることもベストプラクティスです。 アクションのバージョン管理の詳細については、「[アクションについて](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)」を参照してください。 -```shell +```shell{:copy} git add action.yml entrypoint.sh Dockerfile README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1 @@ -175,11 +177,11 @@ git push --follow-tags #### パブリックアクションを使用する例 -次のワークフローコードでは、[`actions/hello-world-docker-container-action`](https://github.com/actions/hello-world-docker-action)というパブリックリポジトリにある完成した hello world アクションを使っています。 次のワークフローサンプルコードを `.github/workflows/main.yml` にコピーし、`actions/hello-world-docker-action` をあなたのリポジトリとアクション名に置き換えてください。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 +以下のワークフローのコードは、パブリックの[`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action)リポジトリ内の完成した_hello world_アクションを使います。 次のワークフローサンプルコードを `.github/workflows/main.yml` にコピーし、`actions/hello-world-docker-action` をあなたのリポジトリとアクション名に置き換えてください。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% if currentVersion == "free-pro-team@latest" %}パブリックなアクションは、{% data variables.product.prodname_marketplace %}に公開されていなくても使うことができます。 詳しい情報については「[アクションの公開](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)」を参照してください。 {% endif %} {% raw %} **.github/workflows/main.yml** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### プライベートアクションを使用する例 -次のワークフローコードサンプルを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 +次のワークフローコードサンプルを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% if currentVersion == "free-pro-team@latest" %}このプライベートのアクションは{% data variables.product.prodname_marketplace %}に公開する事はできず、このリポジトリ内でのみ利用できます。{% endif %} {% raw %} **.github/workflows/main.yml** -```yaml +```yaml{:copy} on: [push] jobs: diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md index 79e6e352ae..4f7f16789d 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md @@ -1,6 +1,6 @@ --- title: JavaScript アクションを作成する -intro: 'このガイドでは、アクションツールキットを使って JavaScript アクションをビルドする方法について学びます。' +intro: このガイドでは、アクションツールキットを使って JavaScript アクションをビルドする方法について学びます。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-javascript-action @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Action development + - JavaScript --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md index d4ecebaaa2..6e43dbdfa6 100644 --- a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -1,14 +1,14 @@ --- title: GitHub ActionsのためのDockerfileサポート shortTitle: Docker -intro: 'Dockerコンテナアクション用の`Dockerfile`を作成する際には、いくつかのDockerの命令がGitHub Actionsやアクションのメタデータファイルとどのように関わるのかを知っておく必要があります。' +intro: Dockerコンテナアクション用の`Dockerfile`を作成する際には、いくつかのDockerの命令がGitHub Actionsやアクションのメタデータファイルとどのように関わるのかを知っておく必要があります。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/building-actions/dockerfile-support-for-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} @@ -48,20 +48,21 @@ Dockerの`ENTRYPOINT`命令には、_shell_形式と_exec_形式があります _exec_形式の`ENTRYPOINT`命令を使うようにコンテナを設定した場合、アクションのメタデータファイル中に設定された`args`はコマンドシェル内では実行されません。 アクションの`args`に環境変数が含まれている場合、その変数は置換されません。 たとえば、以下の_exec_形式は`$GITHUB_SHA`に保存された値を出力せず、代わりに`"$GITHUB_SHA"`を出力します。 -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` 変数の置換をさせたい場合は、_shell_形式を使うか、直接シェルを実行してください。 たとえば、以下の_exec_形式を使えば、シェルを実行して環境変数`GITHUB_SHA`に保存された値を出力できます。 -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` アクションのメタデータファイルに定義された`args`を、`ENTRYPOINT`中で_exec_形式を使うDockerコンテナに渡すには、`ENTRYPOINT`命令から呼ぶ`entrypoint.sh`というシェルスクリプトを作成することをおすすめします。 ##### *Dockerfile*の例 -``` + +```dockerfile # コードを実行するコンテナイメージ FROM debian:9.5-slim diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 0ff1beeb29..283774b155 100644 --- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,7 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md index 4da8f5878f..0a54adb520 100644 --- a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,11 +41,13 @@ try { Docker コンテナアクションを作成している場合、失敗終了コードを `entrypoint.sh` スクリプトで設定できます。 例: +{% raw %} ``` if ; then echo "Game over!" exit 1 fi ``` +{% endraw %} 詳しい情報については「[Docker コンテナアクションを作成する](/articles/creating-a-docker-container-action)」を参照してください。 diff --git a/translations/ja-JP/content/actions/guides/about-continuous-integration.md b/translations/ja-JP/content/actions/guides/about-continuous-integration.md index 43db3e7bd0..3507945e90 100644 --- a/translations/ja-JP/content/actions/guides/about-continuous-integration.md +++ b/translations/ja-JP/content/actions/guides/about-continuous-integration.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md b/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md index db817ec6bf..ccb3dee2f2 100644 --- a/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - パッケージ化 --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/about-service-containers.md b/translations/ja-JP/content/actions/guides/about-service-containers.md index d177f529dd..b1bf02b1a3 100644 --- a/translations/ja-JP/content/actions/guides/about-service-containers.md +++ b/translations/ja-JP/content/actions/guides/about-service-containers.md @@ -1,6 +1,6 @@ --- title: サービスコンテナについて -intro: 'サービスコンテナを使って、データベース、Webサービス、メモリキャッシュ、あるいはその他のツールをワークフローに接続できます。' +intro: サービスコンテナを使って、データベース、Webサービス、メモリキャッシュ、あるいはその他のツールをワークフローに接続できます。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/automating-your-workflow-with-github-actions/about-service-containers @@ -8,7 +8,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ type: 'overview' 以下の例は、`container-job`というジョブの中に`redis`というサービスを作成します。 この例でのDockerホストは`node:10.18-jessie`コンテナです。 {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -89,7 +92,7 @@ Dockerホストのポートを指定して、コンテナのポートを指定 以下の例は、サービスコンテナ`redis`のポート6379を、Dockerホストのポート6379にマップします。 {% raw %} -```yaml +```yaml{:copy} name: Redis Service Example on: push diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md index 350380014f..d3e6149ace 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Java + - Ant --- {% data reusables.actions.enterprise-beta %} @@ -15,7 +19,7 @@ type: 'tutorial' ### はじめに -このガイドは、Antビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、プルリクエストに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ワークフローの実行による成果物をアップロードするようにもできます。 +このガイドは、Antビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ワークフローの実行による成果物をアップロードするようにもできます。 {% data variables.product.prodname_dotcom %}ホストランナーは、Java Development Kits（JDKs）及びAntを含むプリインストールされたソフトウェアを伴うツールキャッシュを持ちます。 JDK および Ant のソフトウェアとプリインストールされたバージョンのリストについては、「[{% data variables.product.prodname_dotcom %} でホストされているランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 @@ -38,7 +42,7 @@ Java及びAntフレームワークの基本的な理解をしておくことを リポジトリの`.github/workflows`に新しいファイルを作成して、手作業でこのワークフローを追加することもできます。 {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ jobs: プロジェクトのビルドに異なるコマンドを使ったり、異なるターゲットを実行したいのであれば、それらを指定できます。 たとえば、_build-ci.xml_ファイル中で設定された`jar`ターゲットを実行したいこともあるでしょう。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ steps: Antは通常、JAR、EAR、WARのような出力ファイルを`build/jar`ディレクトリに作成します。 このディレクトリの内容は`upload-artifact`アクションを使ってアップロードできます。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md index 368eb41645..89e7f13f71 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -15,7 +19,7 @@ type: 'tutorial' ### はじめに -このガイドは、Gradleビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、プルリクエストに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。 +このガイドは、Gradleビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。 {% data variables.product.prodname_dotcom %}ホストランナーは、Java Development Kits（JDKs）及びGradleを含むプリインストールされたソフトウェアを伴うツールキャッシュを持ちます。 JDK および Gradle のソフトウェアとプリインストールされたバージョンのリストについては、「[{% data variables.product.prodname_dotcom %} でホストされているランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 @@ -38,7 +42,7 @@ Java及びGradleフレームワークの基本的な理解をしておくこと リポジトリの`.github/workflows`に新しいファイルを作成して、手作業でこのワークフローを追加することもできます。 {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ jobs: プロジェクトのビルドに異なるコマンドを使ったり、異なるタスクを使いたいのであれば、それらを指定できます。 たとえば、_ci.gradle_ファイル中で設定された`package`タスクを実行したいこともあるでしょう。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: {% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのGradleパッケージキャッシュがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのパッケージリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # GitHub ActionsでキャッシュされないようにいくつかのファイルをGradleのキャッシュから削除 + # これらのファイルをGitHub Actionsのキャッシュからリストアすると、将来のビルドで問題が生じるかもしれない。 + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -このワークフローは、ランナーのホームディレクトリ内の`.gradle/caches`ディレクトリにあるローカルのGradleパッケージキャッシュの内容を保存します。 キャッシュのキーは、Gradleのビルドファイルの内容をハッシュしたものになるので、それらに変更があればキャッシュは無効になります。 +このワークフローは、ランナーのホームディレクトリ内の`.gradle/caches`ディレクトリと`.gradle/wrapper`ディレクトリにあるローカルのGradleパッケージキャッシュの内容を保存します。 キャッシュのキーはGradleのビルドファイル（Gradleのラッパー属性ファイルを含む）の内容のハッシュになるので、それらに変更があればキャッシュは無効になります。 ### 成果物としてのワークフローのデータのパッケージ化 @@ -122,7 +135,7 @@ steps: Gradleは通常、JAR、EAR、WARのような出力ファイルを`build/libs`ディレクトリに作成します。 このディレクトリの内容は`upload-artifact`アクションを使ってアップロードできます。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md index 29d17e3609..bc91d8a8d6 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Java及びMavenフレームワークの基本的な理解をしておくこと リポジトリの`.github/workflows`に新しいファイルを作成して、手作業でこのワークフローを追加することもできます。 {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ jobs: プロジェクトのビルドに異なるコマンドを使ったり、異なるターゲットを使いたいのであれば、それらを指定できます。 たとえば、_pom-ci.xml_ファイル中で設定された`verify`ターゲットを実行したいこともあるでしょう。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: {% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -117,12 +121,12 @@ steps: ### 成果物としてのワークフローのデータのパッケージ化 -ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、プルリクエストをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 +ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 Mavenは通常、JAR、EAR、WARのような出力ファイルを`target`ディレクトリに作成します。 それらを成果物としてアップロードするために、アップロードする成果物を含む新しいディレクトリにそれらをコピーできます。 たとえば、`staging`というディレクトリを作成できます。 として、そのディレクトリの内容を`upload-artifact`アクションを使ってアップロードできます。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-net.md b/translations/ja-JP/content/actions/guides/building-and-testing-net.md index acdc49f777..4a908cd2ca 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-net.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: {% data variables.product.prodname_dotcom %}ホストランナーにプリインストールされたバージョンの.NET Core SDKを使うには、`setup-dotnet`アクションを使ってください。 このアクションは各ランナーのツールキャッシュから指定されたバージョンの.NETを見つけ、必要なバイナリを`PATH`に追加します。 これらの変更は、ジョブの残りの部分で保持されます。 -`setup-dotnet`アクションは、{% data variables.product.prodname_actions %}で.NETを使うための推奨される方法です。これは、それによって様々なランナーや様々なバージョンの.NETに渡って一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、.NETをインストールして`PATH`に追加しなければなりません。 詳しい情報については[`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet)を参照してください。 +`setup-dotnet`アクションは、{% data variables.product.prodname_actions %}で.NETを使うための推奨される方法です。これは、それによって様々なランナーや様々なバージョンの.NETに渡って一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、.NETをインストールして`PATH`に追加しなければなりません。 詳しい情報については[`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk)アクションを参照してください。 #### 複数の.NETバージョンの利用 diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md index 983ba8667b..f303bd51a8 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md @@ -8,7 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - ノード + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -77,7 +81,7 @@ jobs: それぞれのジョブは、配列`node-version` のマトリクスで定義された値に、`matrix`コンテキストを使ってアクセスできます。 `setup-node`アクションは、このコンテキストを`node-version`のインプットとして使います。 `setup-node`アクションは、コードのビルドとテストに先立って、様々なNode.jsのバージョンで各ジョブを設定します。 マトリクス戦略とコンテキストに関する詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)」及び「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 {% raw %} -```yaml +```yaml{:copy} strategy: matrix: node-version: [10.x, 12.x, 14.x, 15.x] @@ -93,7 +97,7 @@ steps: あるいは、厳密にNode.jsバージョンを指定してビルドとテストを行うこともできます。 -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -102,7 +106,7 @@ strategy: または、Node.jsの1つのバージョンを使ってビルドとテストを行うこともできます。 {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -136,7 +140,7 @@ Node.jsのバージョンを指定しなかった場合、{% data variables.prod 以下の例では、*package.json*ファイルで定義された依存関係がインストールされます。 詳しい情報については[`npm install`](https://docs.npmjs.com/cli/install)を参照してください。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -150,7 +154,7 @@ steps: `npm ci`を使うと、 *package-lock.json*あるいは*npm-shrinkwrap.json*ファイル中のバージョンがインストールされ、ロックファイルの更新を回避できます。 概して`npm ci`は、`npm install`を実行するよりも高速です。 詳しい情報については[`npm ci`](https://docs.npmjs.com/cli/ci.html)及び「[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)」を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -166,7 +170,7 @@ steps: 以下の例では、*package.json*ファイルで定義された依存関係がインストールされます。 詳しい情報については[`yarn install`](https://yarnpkg.com/en/docs/cli/install)を参照してください。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -179,7 +183,7 @@ steps: あるいは`--frozen-lockfile`を渡して*yarn.lock*ファイル中のバージョンをインストールし、*yarn.lock*ファイルの更新を回避できます。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -201,7 +205,7 @@ steps: 依存関係をインストールする前に、`setup-node`アクションを使って*.npmrc*ファイルを作成してください。 このアクションには2つの入力パラメーターがあります。 `node-version`パラメーターはNode.jsのバージョンを設定し、`registry-url`パラメーターはデフォルトのレジストリを設定します。 パッケージレジストリがスコープを使うなら、`scope`パラメーターを使わなければなりません。 詳しい情報については[`npm-scope`](https://docs.npmjs.com/misc/scope)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -220,7 +224,7 @@ steps: 上の例では、以下の内容で*.npmrc*ファイルを作成しています。 -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -231,7 +235,7 @@ always-auth=true {% data variables.product.prodname_dotcom %} ホストランナーを使用する場合、一意のキーを使用して依存関係をキャッシュし、`cache` アクションを使用して将来のワークフローを実行するときに依存関係を復元できます。 詳しい情報については「ワークフローを高速化するための依存関係のキャッシング」及び[`cache`アクション](https://github.com/marketplace/actions/cache)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -256,7 +260,7 @@ steps: ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 たとえば*package.json*ファイルで定義されたビルドのステップを実行するのに`npm run build`を実行し、テストスイートを実行するのに`npm test`を実行しているなら、それらのコマンドをワークフローファイルに追加します。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md b/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md index 16d175ea04..4ab221cd87 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md @@ -7,7 +7,10 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee -type: 'tutorial' +type: tutorial +topics: + - CI + - Powershell --- {% data reusables.actions.enterprise-beta %} @@ -57,17 +60,17 @@ jobs: ``` {% endraw %} -* `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. 例: +* `shell: pwsh` `run`コマンドの実行時にPowerShellを使うようにジョブを設定します。 +* `run: Test-Path resultsfile.log` - リポジトリのルートディレクトリに`resultsfile.log`というファイルが存在するかをチェックします。 +* `Should -Be $true` - Pesterを使って期待される結果を定義します。 結果が期待どおりではなかった場合、{% data variables.product.prodname_actions %}はこれを失敗したテストとしてフラグを立てます。 例: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} - ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png) + ![失敗したPesterテスト](/assets/images/help/repository/actions-failed-pester-test-updated.png) {% else %} - ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) + ![失敗したPesterテスト](/assets/images/help/repository/actions-failed-pester-test.png) {% endif %} -* `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: +* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Pesterを使って`Unit.Tests.ps1`というファイルに定義されたテストを実行します。 たとえば上記の同じテストを実行するには、`Unit.Tests.ps1`には以下を含めます。 ``` Describe "Check results file is present" { It "Check results file is present" { @@ -76,29 +79,29 @@ jobs: } ``` -### PowerShell module locations +### PowerShellのモジュールの場所 -The table below describes the locations for various PowerShell modules in each {% data variables.product.prodname_dotcom %}-hosted runner. +以下の表は、それぞれの{% data variables.product.prodname_dotcom %}ホストランナー内の様々なPowerShellモジュールの場所を示します。 -| | 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\*` | +| | Ubuntu | macOS | Windows | +| ----------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ | +| **PowerShellシステムモジュール** | `/opt/microsoft/powershell/7/Modules/*` | `/usr/local/microsoft/powershell/7/Modules/*` | `C:\program files\powershell\7\Modules\*` | +| **PowerShellアドオンモジュール** | `/usr/local/share/powershell/Modules/*` | `/usr/local/share/powershell/Modules/*` | `C:\Modules\*` | +| **ユーザがインストールしたモジュール** | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` | ### 依存関係のインストール -{% 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. +{% data variables.product.prodname_dotcom %}ホストランナーには、PowerShell 7とPesterがインストールされています。 コードのビルドとテストに先立って、`Install-Module`を使って追加の依存関係をPowerShell Galleryからインストールできます。 {% note %} -**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`. +**ノート:** {% data variables.product.prodname_dotcom %}ホストランナーが使用するプリインストールされたパッケージ（Pesterなど）は定期的に更新され、重要な変更が行われることがあります。 そのため、`Install-Module`で`-MaximumVersion`を使って必要なパッケージのバージョンを常に指定しておくことをおすすめします。 {% endnote %} -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 -For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules: +たとえば以下のジョブは、`SqlServer`及び`PSScriptAnalyzer`モジュールをインストールします。 {% raw %} ```yaml @@ -118,15 +121,15 @@ jobs: {% note %} -**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`. +**ノート:** デフォルトでは、PowerShellはどのリポジトリも信頼しません。 PowerShell Galleryからモジュールをインストールする際には、`PSGallery`のインストールポリシーを明示的に`Trusted`に設定しなければなりません。 {% endnote %} #### 依存関係のキャッシング -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. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_dotcom %} ホストランナーを使用する場合、一意のキーを使用してPowerShellの依存関係をキャッシュし、[`cache`](https://github.com/marketplace/actions/cache)アクションで将来のワークフローを実行するときに依存関係を復元できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 -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. +PowerShellは、ランナーのオペレーティングシステムによって依存関係を様々な場所にキャッシュします。 たとえば以下のUbuntuの例で使われる`path`の場所は、Windowsオペレーティングシステムの場合とは異なります。 {% raw %} ```yaml @@ -151,9 +154,9 @@ steps: ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 -#### Using PSScriptAnalyzer to lint code +#### 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). +以下の例は`PSScriptAnalyzer`をインストールし、それを使ってリポジトリ内のすべての`ps1`ファイルの文法チェックを行います。 詳しい情報については[GitHub上のPSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer)を参照してください。 {% raw %} ```yaml @@ -185,7 +188,7 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` ワークフローの完了後に、成果物をアップロードして見ることができます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 -The following example demonstrates how you can use the `upload-artifact` action to archive the test results received from `Invoke-Pester`. 詳しい情報については[`upload-artifact`アクション](https://github.com/actions/upload-artifact)を参照してください。 +以下の例は、`upload-artifact`アクションを使って`Invoke-Pester`から受信したテスト結果をアーカイブする方法を示しています。 詳しい情報については[`upload-artifact`アクション](https://github.com/actions/upload-artifact)を参照してください。 {% raw %} ```yaml @@ -211,13 +214,13 @@ jobs: ``` {% endraw %} -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)." +`always()`関数は、テストに失敗があっても継続するようにジョブを設定しています。 詳しい情報については「[ always](/actions/reference/context-and-expression-syntax-for-github-actions#always)」を参照してください。 -### Publishing to PowerShell Gallery +### PowerShell Galleryへの公開 -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. 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +CIテストにパスしたら、PowerShellモジュールをPowerShell Galleryに公開するようにワークフローを設定できます。 パッケージを公開するのに必要なトークンや認証情報を保存するために、シークレットを使うことができます。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 -The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery: +以下の例は、パッケージを作成し、`Publish-Module`を使ってそのパッケージをPowerShell Galleryに公開します。 {% raw %} ```yaml diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-python.md b/translations/ja-JP/content/actions/guides/building-and-testing-python.md index 3dc828060b..3f4b4eca9e 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-python.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-python.md @@ -7,7 +7,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Python --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Python、PyPy、pipの基本的な理解をしておくことをおすすめし 手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -94,7 +97,7 @@ jobs: #### Pythonの複数バージョンの利用 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -123,10 +126,10 @@ jobs: #### 　特定のバージョンのPythonの利用 -Pythonの特定バージョンを設定することができます。 たとえば3.8が利用できます。 Alternatively, you can use semantic version syntax to get the latest minor release. 以下の例では、Python 3の最新のマイナーリリースを使います。 +Pythonの特定バージョンを設定することができます。 たとえば3.8が利用できます。 あるいは、最新のマイナーリリースを取得するためにセマンティックバージョン構文を使うこともできます。 以下の例では、Python 3の最新のマイナーリリースを使います。 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -141,11 +144,11 @@ jobs: - name: Set up Python 3.x uses: actions/setup-python@v2 with: - # Semantic version range syntax or exact version of a Python version + # セマンティックバージョン範囲構文もしくは厳密なPythonのバージョン python-version: '3.x' - # Optional - x64 or x86 architecture, defaults to x64 + # オプション - x64もしくはx86アーキテクチャ、デフォルトはx64 architecture: 'x64' - # You can test your matrix by printing the current Python version + # 現在のPythonのバージョンを出力して、マトリクスをテストできる - name: Display Python version run: python -c "import sys; print(sys.version)" ``` @@ -158,7 +161,7 @@ jobs: 実行したくないPythonの環境があるなら、ワークフロー中で`exclude`キーワードを使うこともできます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)」を参照してください。 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -193,10 +196,10 @@ jobs: {% data variables.product.prodname_dotcom %}ホストランナーには、パッケージマネージャーのpipがインストールされています。 コードのビルドとテストに先立って、pipを使ってパッケージレジストリのPyPIから依存関係をインストールできます。 たとえば以下のYAMLは`pip`パッケージインストーラーと`setuptools`及び`wheel`パッケージのインストールやアップグレードを行います。 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -213,7 +216,7 @@ steps: `pip`をアップデートした後、次の典型的なステップは*requirements.txt*からの依存関係のインストールです。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -229,12 +232,12 @@ steps: #### 依存関係のキャッシング -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. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_dotcom %} ホストランナーを使用する場合、一意のキーを使用してpipの依存関係をキャッシュし、[`cache`](https://github.com/marketplace/actions/cache)アクションを使用して将来のワークフローを実行するときに依存関係を復元できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ランナーのオペレーティングシステムによって、pipは依存関係を様々な場所にキャッシュします。 キャッシュする必要があるパスは、使用するオペレーティングシステムによって以下のUbuntuの例とは異なるかもしれません。 詳しい情報については[Pythonのキャッシングの例](https://github.com/actions/cache/blob/main/examples.md#python---pip)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Setup Python @@ -271,7 +274,7 @@ steps: 以下の例では、`pytest`及び`pytest-cov`をインストールあるいはアップグレードします。 そしてテストが実行され、JUnit形式で出力が行われ、一方でコードカバレッジの結果がCoberturaに出力されます。 詳しい情報については[JUnit](https://junit.org/junit5/)及び[Cobertura](https://cobertura.github.io/cobertura/)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -295,7 +298,7 @@ steps: 以下の例は、`flake8`をインストールもしくはアップグレードし、それを使ってすべてのファイルをlintします。 詳しい情報については[Flake8](http://flake8.pycqa.org/en/latest/)を参照してください。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -318,7 +321,7 @@ steps: {% data variables.product.prodname_actions %}では、toxでテストを実行し、その処理を複数のジョブに分散できます。 toxを起動する際には、特定のバージョンを指定するのではなく、`-e py`オプションを使って`PATH`中のPythonのバージョンを選択しなければなりません。 詳しい情報については [tox](https://tox.readthedocs.io/en/latest/)を参照してください。 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -352,7 +355,7 @@ jobs: 以下の例は、`upload-artifact`アクションを使って`pytest`の実行によるテスト結果をアーカイブする方法を示しています。 詳しい情報については[`upload-artifact`アクション](https://github.com/actions/upload-artifact)を参照してください。 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -365,26 +368,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # pip と pytest をインストールする - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # テスト失敗時にテスト結果を公開するには、always() を使用して常にこのステップを実行する - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # pip及びpytestのインストール + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # テストに失敗があった場合でもテスト結果が公開されるよう、always()を使って常にこのステップを実行する + if: ${{ always() }} ``` {% endraw %} @@ -392,10 +395,10 @@ jobs: CIテストにパスしたなら、Pythonパッケージを任意のパッケージレジストリに公開するようにワークフローを設定できます。 -You can store any access tokens or credentials needed to publish your package using secrets. 以下の例では、`twine`と`dist`を使ってパッケージを作成してPyPIに公開しています。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +パッケージを公開するのに必要なアクセストークンや認証情報は、シークレットを使って保存できます。 以下の例では、`twine`と`dist`を使ってパッケージを作成してPyPIに公開しています。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 {% raw %} -```yaml +```yaml{:copy} name: Upload Python Package on: diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md index ee3cebbd11..b822af7a4b 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md @@ -1,11 +1,14 @@ --- -title: Building and testing Ruby -intro: You can create a continuous integration (CI) workflow to build and test your Ruby project. +title: Rubyでのビルドとテスト +intro: Rubyプロジェクトのビルドとテストのための継続的インテグレーション（CI）ワークフローを作成できます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Ruby --- {% data reusables.actions.enterprise-beta %} @@ -13,18 +16,18 @@ type: 'tutorial' ### はじめに -This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem. +このガイドでは、Rubyアプリケーションのビルドとテストを行う継続的インテグレーション（CI）ワークフローの作成方法を紹介します。 CIテストにパスしたなら、コードをデプロイしたりgemを公開したりすることになるでしょう。 ### 必要な環境 -We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. 詳しい情報については、以下を参照してください。 +Ruby、YAML、ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳しい情報については、以下を参照してください。 -- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions) -- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/) +- [{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions) +- [20分のRuby](https://www.ruby-lang.org/en/documentation/quickstart/) -### Starting with the Ruby workflow template +### Rubyワークフローテンプレートを使い始める -{% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml). +{% data variables.product.prodname_dotcom %}は、ほとんどのRubyプロジェクトで使えるRubyのワークフローテンプレートを提供しています。 詳しい情報については[Rubyワークフローテンプレート](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml)を参照してください。 手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。 @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -59,13 +59,13 @@ jobs: ``` {% endraw %} -### Specifying the Ruby version +### Rubyのバージョンの指定 -The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). +Rubyのバージョンを指定する最も簡単な方法は、GitHub上でRuby Organizationが提供している`ruby/setup-ruby`アクションを使うことです。 このアクションは、ワークフロー中の各ジョブの実行時に、`PATH`にサポートされているRubyのバージョンを追加します。 詳しい情報については[`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)を参照してください。 -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. -The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. +`setup-ruby`アクションはRubyのバージョンを入力として取り、ランナー上でそのバージョンを設定します。 {% raw %} ```yaml @@ -79,11 +79,11 @@ steps: ``` {% endraw %} -Alternatively, you can check a `.ruby-version` file into the root of your repository and `setup-ruby` will use the version defined in that file. +あるいは、リポジトリのルートに`.ruby-version`ファイルをチェックインすれば、このファイルで定義されたバージョンを`setup-ruby`が使います。 -### Testing with multiple versions of Ruby +### 複数のバージョンの Ruby でのテスト -You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version. +複数バージョンのRubyでワークフローを実行するように、マトリクス戦略を追加できます。 たとえば、バージョン2.7、2.6、2.5の最新のパッチリリースでコードをテストできます。 この'x'はワイルドカードキャラクターで、そのバージョンで利用できる最新のパッチリリースにマッチします。 {% raw %} ```yaml @@ -93,9 +93,9 @@ strategy: ``` {% endraw %} -Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "Workflow syntax for GitHub Actions" and "Context and expression syntax for GitHub Actions." +`ruby-version`配列で指定されたRubyの各バージョンに対して、同じステップを実行するジョブが作成されます。 現在のジョブのバージョンにアクセスするのには、{% raw %}`${{ matrix.ruby-version }}`{% endraw %}コンテキストが使われます。 マトリクス戦略とコンテキストに関する詳しい情報については、「GitHub Actionsのワークフロー構文」及び「GitHub Actionsのコンテキスト及び式構文」を参照してください。 -The full updated workflow with a matrix strategy could look like this: +マトリクス戦略を持つ更新された完全なワークフローは、以下のようになるでしょう。 {% raw %} ```yaml @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -132,9 +129,9 @@ jobs: ``` {% endraw %} -### Installing dependencies with Bundler +### Bundlerでの依存関係のインストール -The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed. +`setup-ruby` アクションは自動的にbundlerをインストールします。 バージョンは、`gemfile.lock`ファイルで決定されます。 ロックファイルにバージョンがなければ、互換性のある最新のバージョンがインストールされます。 {% raw %} ```yaml @@ -149,9 +146,9 @@ steps: #### 依存関係のキャッシング -If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +{% data variables.product.prodname_dotcom %}ホストランナーを使っているなら、`setup-ruby`は実行間でのgemのキャッシュを自動的に処理する方法を提供します。 -To enable caching, set the following. +キャッシングを有効にするには、以下の設定をしてください。 {% raw %} ```yaml @@ -162,11 +159,11 @@ steps: ``` {% endraw %} -This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install. +これで、gemを`vendor/cache`にインストールするようbundlerが設定されます。 ワークフローの実行が成功するたびに、このフォルダーはアクションによってキャッシュされ、それ以降のワークフローの実行の際に再ダウンロードされます。 キャッシュのキーとしては、gemfile.lockのハッシュとRubyのバージョンが使われます。 新しいgemをインストールしたり、バージョンを変更したりすると、キャッシュは無効になり、bundlerは新しくインストールを行います。 -**Caching without setup-ruby** +**setup-rubyを使わないキャッシング** -For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +キャッシュをさらに制御するには、{% data variables.product.prodname_dotcom %}ホストランナーを使っているなら、`actions/cache`アクションを直接使うことができます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 {% raw %} ```yaml @@ -184,7 +181,7 @@ steps: ``` {% endraw %} -If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this: +マトリクスビルドを使っているなら、キャッシュのキーにマトリクスの変数を含めたくなるでしょう。 たとえば様々なRubyのバージョン(`matrix.ruby-version`) と、様々なオペレーティングシステム(`matrix.os`)のマトリクス戦略を持っているなら、ワークフローのステップは以下のようになるでしょう。 {% raw %} ```yaml @@ -202,9 +199,9 @@ steps: ``` {% endraw %} -### Matrix testing your code +### コードのマトリクステスト -The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS. +以下の例のマトリクスは、すべての安定リリースとヘッドバージョンのMRI、JRuby、TruffleRubyをUbuntu及びmacOSでテストします。 {% raw %} ```yaml @@ -235,9 +232,9 @@ jobs: ``` {% endraw %} -### Linting your code +### コードの文法チェック -The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules. +以下の例は`rubocop`をインストールし、それを使ってすべてのファイルの文法チェックを行います。 詳しい情報については[ Rubocop](https://github.com/rubocop-hq/rubocop)を参照してください。 特定の文法チェックルールを決めるために、[ Rubocopを設定](https://docs.rubocop.org/rubocop/configuration.html)できます。 {% raw %} ```yaml @@ -259,11 +256,11 @@ jobs: ``` {% endraw %} -### Publishing Gems +### gemの公開 -You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass. +CIテストにパスしたなら、Rubyパッケージを任意のパッケージレジストリに公開するようにワークフローを設定できます。 -パッケージを公開するのに必要なアクセストークンやクレデンシャルは、リポジトリシークレットを使って保存できます。 The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`. +パッケージを公開するのに必要なアクセストークンや認証情報は、リポジトリシークレットを使って保存できます。 以下の例は、パッケージを作成して`GitHub Package Registry`及び`RubyGems`に公開します。 {% raw %} ```yaml @@ -271,9 +268,9 @@ You can configure your workflow to publish your Ruby package to any package regi name: Ruby Gem on: - # Manually publish + # 手動で公開 workflow_dispatch: - # Alternatively, publish whenever changes are merged to the default branch. + # あるいは変更がデフォルトブランチにマージされたときに公開。 push: branches: [ $default-branch ] pull_request: @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 27fb3aeab9..b4ecd052ec 100644 --- a/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -1,7 +1,7 @@ --- title: 依存関係をキャッシュしてワークフローのスピードを上げる shortTitle: 依存関係のキャッシング -intro: 'ワークフローを高速化して効率を上げるために、依存関係や広く再利用されるファイルに対するキャッシュを作成して利用できます。' +intro: ワークフローを高速化して効率を上げるために、依存関係や広く再利用されるファイルに対するキャッシュを作成して利用できます。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows @@ -9,7 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: 'tutorial' +type: tutorial +topics: + - ワークフロー --- ### ワークフローの依存関係のキャッシングについて @@ -22,7 +24,7 @@ type: 'tutorial' {% warning %} -**警告**: パブリックリポジトリのキャッシュには、センシティブな情報を保存しないことをおすすめします。 たとえばキャッシュパス内のファイルに保存されたアクセストークンあるいはログインクレデンシャルなどがセンシティブな情報です。 また、`docker login`のようなコマンドラインインターフェース（CLI）プログラムは、アクセスクレデンシャルを設定ファイルに保存することがあります。 読み取りアクセスを持つ人は誰でも、リポジトリにプルリクエストを作成し、キャッシュの内容にアクセスできます。 リポジトリのフォークも、ベースブランチ上にプルリクエストを作成し、ベースブランチ上のキャッシュにアクセスできます。 +**警告**: パブリックリポジトリのキャッシュには、センシティブな情報を保存しないことをおすすめします。 たとえばキャッシュパス内のファイルに保存されたアクセストークンあるいはログインクレデンシャルなどがセンシティブな情報です。 また、`docker login`のようなコマンドラインインターフェース（CLI）プログラムは、アクセスクレデンシャルを設定ファイルに保存することがあります。 読み取りアクセスを持つ人は誰でも、リポジトリにPull Requestを作成し、キャッシュの内容にアクセスできます。 リポジトリのフォークも、ベースブランチ上にPull Requestを作成し、ベースブランチ上のキャッシュにアクセスできます。 {% endwarning %} @@ -37,9 +39,9 @@ type: 'tutorial' `cache` アクションの `v2` を使用すると、`GITHUB_REF` を含むイベントによってトリガーされるワークフローのキャッシュにアクセスできます。 `cache` アクションの `v1` を使用している場合、`pull_request` の `closed` イベントを除いて、`push` イベントと `pull_request` イベントによってトリガーされるワークフローでのみキャッシュにアクセスできます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 -ワークフローは、現在のブランチ、ベースブランチ（フォークされたリポジトリのベースブランチを含む）、またはデフォルトブランチ（通常は `main`）で作成されたキャッシュにアクセスして復元できます。 たとえば、デフォルトブランチで作成されたキャッシュは、どのプルリクエストからもアクセスできます。 また、`feature-b` ブランチに `feature-a` ベースブランチがある場合、`feature-b` でトリガーされたワークフローは、デフォルトのブランチ（`main`）、`feature-a`、および `feature-b` で作成されたキャッシュにアクセスできます。 +ワークフローは、現在のブランチ、ベースブランチ（フォークされたリポジトリのベースブランチを含む）、またはデフォルトブランチ（通常は `main`）で作成されたキャッシュにアクセスして復元できます。 たとえば、デフォルトブランチで作成されたキャッシュは、どのPull Requestからもアクセスできます。 また、`feature-b` ブランチに `feature-a` ベースブランチがある場合、`feature-b` でトリガーされたワークフローは、デフォルトのブランチ（`main`）、`feature-a`、および `feature-b` で作成されたキャッシュにアクセスできます。 -アクセス制限は、様々なワークフローとブランチ間の論理的な境界を作成することによって、キャッシュの分離とセキュリティを提供します。 たとえば、`feature-a` ブランチ（ベース `main` を使用）向けに作成されたキャッシュは、`feature-b` ブランチ（ベース `main` を使用）のプルリクエストにアクセスできません。 +アクセス制限は、様々なワークフローとブランチ間の論理的な境界を作成することによって、キャッシュの分離とセキュリティを提供します。 たとえば、`feature-a` ブランチ（ベース `main` を使用）向けに作成されたキャッシュは、`feature-b` ブランチ（ベース `main` を使用）のPull Requestにアクセスできません。 ### `cache`アクションの利用 @@ -68,7 +70,7 @@ type: 'tutorial' 以下の例では、`package-lock.json`ファイル内のパッケージが変更された場合、あるいはランナーのオペレーティングシステムが変更された場合に新しいキャッシュが作成されます。 キャッシュキーはコンテキストと式を使い、ランナーのオペレーティングシステムと`package-lock.json`ファイルのSHA-256ハッシュを含むキーを生成します。 {% raw %} -```yaml +```yaml{:copy} name: Caching with npm on: push @@ -124,14 +126,14 @@ jobs: 式を使って`key`を作成すれば、依存関係が変化したときに自動的に新しいキャッシュを作成できます。 たとえばnpmの`package-lock.json`ファイルのハッシュを計算する式を使って`key`を作成できます。 {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %}は`hash "package-lock.json"`という式を評価して、最終的な`key`を導出します。 -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ npm-d5ea0750 #### 複数のリストアキーの利用例 {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | ランナーは式を評価します。この式は以下のような`restore-keys`になります。 {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md b/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md index 24253ff7ba..552fdd74a5 100644 --- a/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ YAML、{% data variables.product.prodname_actions %}の構文、PosgreSQLの基 {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL service example on: push @@ -94,7 +97,7 @@ jobs: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} jobs: # コンテナジョブのラベル container-job: @@ -124,7 +127,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # CIテストの実行前にリポジトリのコードのコピーをダウンロード - name: Check out repository code @@ -159,7 +162,7 @@ PostgreSQLサービスのホスト名は、ワークフロー中で設定され {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL Service Example on: push @@ -220,7 +223,7 @@ jobs: このワークフローはPostgreSQLサービスコンテナ上のポート5432をDockerホストにマップします。 `ports`キーワードに関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。 -```yaml +```yaml{:copy} jobs: # ランナージョブのラベル runner-job: @@ -251,7 +254,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # CIテストの実行前にリポジトリのコードのコピーをダウンロード - name: Check out repository code @@ -287,7 +290,7 @@ steps: {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md b/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md index 896e920f4d..e0f55c017c 100644 --- a/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md +++ b/translations/ja-JP/content/actions/guides/creating-redis-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ YAML、{% data variables.product.prodname_actions %}の構文、Redisの基本 {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -91,7 +94,7 @@ jobs: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} jobs: # コンテナジョブのラベル container-job: @@ -118,7 +121,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # CIテストの実行前にリポジトリのコードのコピーをダウンロード - name: Check out repository code @@ -152,7 +155,7 @@ Redisサービスのホスト名は、ワークフロー中で設定されたラ {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis runner example on: push @@ -210,7 +213,7 @@ jobs: このワークフローはRedisサービスコンテナ上のポート6379をDockerホストにマップします。 `ports`キーワードに関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。 -```yaml +```yaml{:copy} jobs: # ランナージョブのラベル runner-job: @@ -238,7 +241,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # CIテストの実行前にリポジトリのコードのコピーをダウンロード - name: Check out repository code @@ -274,7 +277,7 @@ steps: {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // 新しいRedisクライアントの作成 diff --git a/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md index ff82cd3f12..ffac6197bb 100644 --- a/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -1,10 +1,15 @@ --- -title: Deploying to Amazon Elastic Container Service -intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows. +title: Amazon Elastic Container Serviceへのデプロイ +intro: 継続的デプロイメント（CD）ワークフローの一部として、Amazon Elastic Container Service (ECS) へのデプロイを行えます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Amazon ECS --- {% data reusables.actions.enterprise-beta %} @@ -12,57 +17,57 @@ versions: ### はじめに -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). +このガイドは、{% data variables.product.prodname_actions %}を使ってコンテナ化されたアプリケーションをビルドし、それを[Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/)にプッシュし、[Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/)にデプロイする方法を説明します。 -On every new release in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS. +{% data variables.product.company_short %}リポジトリへの新しいリリースごとに、{% data variables.product.prodname_actions %}ワークフローは新しいコンテナイメージをビルドし、Amazon ECRにプッシュし、そして新しいタスクの定義をAmazon ECSにデプロイします。 ### 必要な環境 -Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS: +{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のAmazon ECR及びECSのセットアップのステップを完了しておかなければなりません。 -1. Create an Amazon ECR repository to store your images. +1. イメージを保存するAmazon ECRリポジトリの作成 - For example, using [the AWS CLI](https://aws.amazon.com/cli/): + たとえば[AWS CLI](https://aws.amazon.com/cli/)を使って以下を行います。 {% raw %}```bash{:copy} aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION ```{% endraw %} - Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below. + 以下のワークフロー中では、`ECR_REPOSITORY`変数に同じAmazon ECRリポジトリ名（ここでは`MY_ECR_REPOSITORY`）を使っていることを確認してください。 - Ensure that you use the same AWS region value for the `AWS_REGION` (represented here by `MY_AWS_REGION`) variable in the workflow below. + 以下のワークフローで `AWS_REGION` 変数（ここでは MY_AWS_REGION`）に同じ AWSリージョンの値を使用していることを確認してください。 -2. Create an Amazon ECS task definition, cluster, and service. +2. Amazon ECSのタスク定義、クラスター、サービスの作成 - For details, follow the [Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), or the [Getting started guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) in the Amazon ECS documentation. + 詳細については、[Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun)もしくはAmazon ECSドキュメンテーションの[Fargate を使用した Amazon ECS の開始方法](https://docs.aws.amazon.com/ja_jp/AmazonECS/latest/developerguide/getting-started-fargate.html)を参照してください。 - Ensure that you note the names you set for the Amazon ECS service and cluster, and use them for the `ECS_SERVICE` and `ECS_CLUSTER` variables in the workflow below. + Amazon ECSサービスとクラスターに設定した名前を記録しておき、以下のワークフロー中で`ECS_SERVICE`及び`ECS_CLUSTER`の変数に使ってください。 -3. Store your Amazon ECS task definition as a JSON file in your {% data variables.product.company_short %} repository. +3. Amazon ECSのタスク定義をJSONファイルとして{% data variables.product.company_short %}リポジトリに保存してください。 - The format of the file should be the same as the output generated by: + ファイルのフォーマットは、以下で生成される出力と同じでなければなりません。 {% raw %}```bash{:copy} aws ecs register-task-definition --generate-cli-skeleton ```{% endraw %} - Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file. +以下のワークフローでは、`ECS_TASK_DEFINITION`変数をJSONファイルのパスに設定してください。 - Ensure that you set the `CONTAINER_NAME` variable in the workflow below as the container name in the `containerDefinitions` section of the task definition. + 以下のワークフロー中の`CONTAINER_NAME`変数を、タスク定義中の`containerDefinitions`セクションのコンテナ名に設定してください。 -4. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key. +4. Amazon IAMアクセスキーの値を保存するための`AWS_ACCESS_KEY_ID`及び`AWS_SECRET_ACCESS_KEY`という名前の{% data variables.product.prodname_actions %}シークレットの作成 - For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." + {% data variables.product.prodname_actions %}のシークレットの作成に関する詳しい情報については、「[暗号化されたシークレット]（/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository）」を参照してください。 - See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials. + IAMユーザに推奨されるIAMポリシー及びアクセスキーの認証情報を処理するメソッドについては、以下で使われている各アクションのドキュメンテーションを参照してください。 -### Creating the workflow +### ワークフローの作成 -Once you've completed the prerequisites, you can proceed with creating the workflow. +必要な環境を整えたら、ワークフローの作成に進むことができます。 -The following example workflow demonstrates how to build a container image and push it to Amazon ECR. It then updates the task definition with the new image ID, and deploys the task definition to Amazon ECS. +以下の例のワークフローは、コンテナイメージを作成してAmazon ECRにプッシュする方法を示します。 そして、タスク定義を新しいイメージIDで更新し、タスク定義をAmazon ECSにデプロイします。 -Ensure that you provide your own values for all the variables in the `env` key of the workflow. +ワークフローの`env`キー内のすべての変数について、自分の値を渡すようにしてください。 {% raw %} ```yaml{:copy} @@ -73,14 +78,14 @@ on: types: [ created ] env: - AWS_REGION: MY_AWS_REGION # set this to your preferred AWS region, e.g. us-west-1 - ECR_REPOSITORY: MY_ECR_REPOSITORY # set this to your Amazon ECR repository name - ECS_SERVICE: MY_ECS_SERVICE # set this to your Amazon ECS service name + AWS_REGION: MY_AWS_REGION # 使用するAWSリージョン 例 us-west-1 に設定してください + ECR_REPOSITORY: MY_ECR_REPOSITORY # 使用するAmazon ECRリポジトリ名に設定してください + ECS_SERVICE: MY_ECS_SERVICE # 使用するAmazon ECSサービス名に設定してください ECS_CLUSTER: MY_ECS_CLUSTER # set this to your Amazon ECS cluster name ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # set this to the path to your Amazon ECS task definition # file, e.g. .aws/task-definition.json - CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the - # containerDefinitions section of your task definition + CONTAINER_NAME: MY_CONTAINER_NAME # タスク定義のcontainerDefinitions中の + # コンテナ名に設定してください defaults: run: @@ -112,9 +117,9 @@ jobs: ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} IMAGE_TAG: ${{ github.sha }} run: | - # Build a docker container and - # push it to ECR so that it can - # be deployed to ECS. + # dockerコンテナをビルドし + # ECRへプッシュして、 + # ECSにデプロイできるようにする。 docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG . docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_ENV @@ -137,12 +142,12 @@ jobs: ``` {% endraw %} -### Additional resources +### 追加リソース -For more information on the services used in these examples, see the following documentation: +この例で使われているサービスに関する詳しい情報については、以下のドキュメンテーションを参照してください。 -* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation. -* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action. -* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action. -* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action. -* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action. +* Amazon AWSドキュメンテーションの「[IAM でのセキュリティのベストプラクティス](https://docs.aws.amazon.com/ja_jp/IAM/latest/UserGuide/best-practices.html)」 +* 公式のAWS「[AWS認証情報の設定](https://github.com/aws-actions/configure-aws-credentials)」アクション。 +* 公式のAWS [Amazon ECR "ログイン"](https://github.com/aws-actions/amazon-ecr-login)アクション。 +* 公式のAWS [Amazon ECS "タスク定義の出力"](https://github.com/aws-actions/amazon-ecs-render-task-definition)アクション。 +* 公式のAWS [ Amazon ECS "タスク定義のデプロイ"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition)アクション。 diff --git a/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md b/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md index 11642fef92..e481d7725c 100644 --- a/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/guides/deploying-to-azure-app-service.md @@ -1,10 +1,15 @@ --- -title: Deploying to Azure App Service -intro: You can deploy to Azure App Service as part of your continuous deployment (CD) workflows. +title: Azure App Serviceへのデプロイ +intro: 継続的デプロイメント（CD）ワークフローの一部として、Azure App Serviceへのデプロイを行えます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Azure App Service --- {% data reusables.actions.enterprise-beta %} @@ -12,17 +17,17 @@ versions: ### はじめに -This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy an application to [Azure App Service](https://azure.microsoft.com/en-us/services/app-service/). +このガイドでは、アプリケーションをビルド、テスト、[Azure App Service](https://azure.microsoft.com/en-us/services/app-service/)へデプロイするための{% data variables.product.prodname_actions %}の使い方を説明します。 -Azure App Service can run web apps in several languages, but this guide demonstrates deploying an existing Node.js project. +Azure App Serviceではいくつかの言語でWebアプリケーションを動作させることができますが、このガイドでは既存のNode.jsプロジェクトをデプロイする方法を示します。 ### 必要な環境 -Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: +{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。 -1. Create an Azure App Service plan. +1. Azure App Serviceプランの作成 - For example, you can use the Azure CLI to create a new App Service plan: + たとえば、Azure CLIを使って新しいApp Serviceのプランを作成できます。 ```bash{:copy} az appservice plan create \ @@ -31,16 +36,16 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you --is-linux ``` - In the command above, replace `MY_RESOURCE_GROUP` with your pre-existing Azure Resource Group, and `MY_APP_SERVICE_PLAN` with a new name for the App Service plan. + 上のコマンドで、`MY_RESOURCE_GROUP`はすでに存在するAzure Resource Groupに、`MY_APP_SERVICE_PLAN`はApp Serviceプランの新しい名前に置き換えてください。 - See the Azure documentation for more information on using the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/): + [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/)の使いからに関する詳しい情報については、Azureのドキュメンテーションを参照してください。 - * For authentication, see "[Sign in with Azure CLI](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli)". - * If you need to create a new resource group, see "[az group](https://docs.microsoft.com/en-us/cli/azure/group?view=azure-cli-latest#az_group_create)." + * 認証については「[Sign in with Azure CLI](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli)を参照してください。 + * 新しいリソースグループを作成しなければならない場合は、「[az group](https://docs.microsoft.com/en-us/cli/azure/group?view=azure-cli-latest#az_group_create)」を参照してください。 -2. Create a web app. +2. Webアプリケーションの作成 - For example, you can use the Azure CLI to create an Azure App Service web app with a node runtime: + たとえば、Azure CLIを使ってnodeのランタイムを持つAzure App Service Webアプリケーションを作成できます。 ```bash{:copy} az webapp create \ @@ -50,21 +55,21 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you --runtime "node|10.14" ``` - In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + 上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。 -3. Configure an Azure publish profile and create an `AZURE_WEBAPP_PUBLISH_PROFILE` secret. +3. Azure公開プロフィールを設定して、`AZURE_WEBAPP_PUBLISH_PROFILE`シークレットを作成してください。 - Generate your Azure deployment credentials using a publish profile. For more information, see "[Generate deployment credentials](https://docs.microsoft.com/en-us/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" in the Azure documentation. + 公開されたプロフィールを使って、Azureのデプロイ資格情報を生成してください。 詳しい情報については、Azureのドキュメンテーションの「[デプロイ資格情報を生成する](https://docs.microsoft.com/ja-jp/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)」を参照してください。 - In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." + {% data variables.product.prodname_dotcom %}リポジトリで、公開されたプロフィールの内容を含む`AZURE_WEBAPP_PUBLISH_PROFILE`という名前のシークレットを生成してください。 シークレットの作成に関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。 -### Creating the workflow +### ワークフローの作成 -Once you've completed the prerequisites, you can proceed with creating the workflow. +必要な環境を整えたら、ワークフローの作成に進むことができます。 -The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service. +以下の例のワークフローは、Node.jsのプロジェクトをビルド、テストし、Azure App Serviceへデプロイする方法を示します。 -Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. +ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 {% raw %} ```yaml{:copy} @@ -91,8 +96,8 @@ jobs: - name: npm install, build, and test run: | - # Build and test the project, then - # deploy to Azure Web App. + # プロジェクトをビルドしてテストし、続いて + # Azure Web Appにデプロイする。 npm install npm run build --if-present npm run test --if-present @@ -106,10 +111,10 @@ jobs: ``` {% endraw %} -### Additional resources +### 追加リソース -The following resources may also be useful: +以下のリソースも役に立つでしょう。 -* For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/master/ci/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. -* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. -* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). +* オリジナルのスターターワークフローについては、{% data variables.product.prodname_actions %} `starter-workflows`リポジトリ中の[`azure.yml`](https://github.com/actions/starter-workflows/blob/master/ci/azure.yml)を参照してください。 +* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。 +* Azure web appドキュメンテーション中の「[Azure で Node.js Web アプリを作成する](https://docs.microsoft.com/ja-jp/azure/app-service/quickstart-nodejs)」クイックスタートは、[Azure App Serviceエクステンション](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice)とともにVS Codeを利用する方法を示しています。 diff --git a/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md index 7b120d4cb5..81a1ec7f20 100644 --- a/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/ja-JP/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -1,10 +1,15 @@ --- -title: Deploying to Google Kubernetes Engine -intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows. +title: Google Kubernetes Engineへのデプロイ +intro: 継続的デプロイメント（CD）ワークフローの一部として、Google Kubernetes Engineへのデプロイを行えます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} @@ -12,20 +17,20 @@ versions: ### はじめに -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE). +このガイドは、{% data variables.product.prodname_actions %}を使ってコンテナ化されたアプリケーションをビルドし、それをGoogle Container Registryにプッシュし、Google Kubernetes Engine (GKE)にデプロイする方法を説明します。 -GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). +GKEはGoogle CloudによるマネージドなKubernetesクラスタサービスで、コンテナ化されたワークロードをクラウドもしくはユーザ自身のデータセンターでホストできます。 詳しい情報については[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)を参照してください。 ### 必要な環境 -Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke). +ワークフローの作成に進む前に、Kubernetesプロジェクトについて以下のステップを完了しておく必要があります。 このガイドは、プロジェクトのルートに`Dockerfile`とKubernetes Deployment設定ファイルがすでに存在することを前提としています。 例としては[google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke)を参照してください。 -#### Creating a GKE cluster +#### GKEクラスタの作成 -To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles: +GKEクラスタを作成するには、まず`gcloud` CLIで認証を受けなければなりません。 このステップに関する詳しい情報については、以下の記事を参照してください。 - [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login) - [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference) -- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk) +- [`gcloud` CLIとCloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk) 例: @@ -37,9 +42,9 @@ $ gcloud container clusters create $GKE_CLUSTER \ ``` {% endraw %} -#### Enabling the APIs +#### APIの有効化 -Enable the Kubernetes Engine and Container Registry APIs. 例: +Kubernetes Engine及びContainer Registry APIを有効化してください。 例: {% raw %} ```bash{:copy} @@ -49,23 +54,23 @@ $ gcloud services enable \ ``` {% endraw %} -#### Configuring a service account and storing its credentials +#### サービスアカウントの設定と資格情報の保存 -This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded [encrypted repository secret](/actions/reference/encrypted-secrets) named `GKE_SA_KEY`. +この手順は、GKEインテグレーション用のサービスアカウントの作成方法を示します。 アカウントの作成、アカウントへのロールの追加、アカウントのキーの取得、それらの`GKE_SA_KEY`という名前のbase64エンコードされた[暗号化されたリポジトリシークレット](/actions/reference/encrypted-secrets)としての保存の方法を説明します。 -1. Create a new service account: +1. 新しいサービスアカウントを作成してください。 {% raw %} ``` $ gcloud iam service-accounts create $SA_NAME ``` {% endraw %} -1. Retrieve the email address of the service account you just created: +1. 作成したサービスアカウントのメールアドレスを取得してください。 {% raw %} ``` $ gcloud iam service-accounts list ``` {% endraw %} -1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements. +1. サービスアカウントにロールを追加してください。 ノート: 要件に合わせて、より制約の強いロールを適用してください。 {% raw %} ``` $ gcloud projects add-iam-policy-binding $GKE_PROJECT \ @@ -74,27 +79,27 @@ This procedure demonstrates how to create the service account for your GKE integ --role=roles/storage.admin ``` {% endraw %} -1. Download the JSON keyfile for the service account: +1. サービスアカウントのJSONキーファイルをダウンロードしてください。 {% raw %} ``` $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL ``` {% endraw %} -1. Store the project ID as a secret named `GKE_PROJECT`: +1. プロジェクトIDを`GKE_PROJECT`という名前のシークレットとして保存してください。 {% raw %} ``` $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} -#### (Optional) Configuring kustomize -Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage). +#### （オプション）kustomizeの設定 +Kustomizeは、YAML仕様を管理するために使われるオプションのツールです。 _kustomization_ ファイルの作成後、以下のワークフローを使用して、イメージのフィールドを動的に設定し、結果を `kubectl` にパイプすることができます。 詳しい情報については、「[kustomize の使い方](https://github.com/kubernetes-sigs/kustomize#usage)」を参照してください。 -### Creating the workflow +### ワークフローの作成 -Once you've completed the prerequisites, you can proceed with creating the workflow. +必要な環境を整えたら、ワークフローの作成に進むことができます。 -The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment. +以下のワークフロー例は、コンテナイメージを作成して GCR にプッシュする方法を示しています。 次に、Kubernetes ツール（`kubectl` や `kustomize` など）を使用して、イメージをクラスタデプロイメントにプルします。 {% raw %} ```yaml{:copy} @@ -120,24 +125,24 @@ jobs: - name: Checkout uses: actions/checkout@v2 - # Setup gcloud CLI + # gcloud CLI のセットアップ - uses: google-github-actions/setup-gcloud@v0.2.0 with: service_account_key: ${{ secrets.GKE_SA_KEY }} project_id: ${{ secrets.GKE_PROJECT }} - # Configure docker to use the gcloud command-line tool as a credential helper + # gcloud コマンドラインツールを認証情報ヘルパーとして使用するようにDockerを設定する - run: |- gcloud --quiet auth configure-docker - # Get the GKE credentials so we can deploy to the cluster + # GKE 認証情報を取得して、クラスタにデプロイできるようにする - uses: google-github-actions/get-gke-credentials@v0.2.1 with: cluster_name: ${{ env.GKE_CLUSTER }} location: ${{ env.GKE_ZONE }} credentials: ${{ secrets.GKE_SA_KEY }} - # Build the Docker image + # Docker イメージをビルドする - name: Build run: |- docker build \ @@ -146,18 +151,18 @@ jobs: --build-arg GITHUB_REF="$GITHUB_REF" \ . - # Push the Docker image to Google Container Registry + # Docker イメージを Google Container Registry にプッシュする - name: Publish run: |- docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" - # Set up kustomize + # kustomize を設定する - name: Set up Kustomize run: |- curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize - # Deploy the Docker image to the GKE cluster + # Docker イメージを GKE クラスタにデプロイする - name: Deploy run: |- ./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA @@ -167,11 +172,11 @@ jobs: ``` {% endraw %} -### Additional resources +### 追加リソース -For more information on the tools used in these examples, see the following documentation: +これらの例で使用されているツールの詳細については、次のドキュメントを参照してください。 -* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/master/ci/google.yml). -* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/). -* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/). -* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation. +* 完全なスターターワークフローについては、「[ビルドして GKE にデプロイするワークフロー](https://github.com/actions/starter-workflows/blob/master/ci/google.yml)」を参照してください。 +* その他のスターターワークフローと付随するコードについては、Google の[{% data variables.product.prodname_actions %}ワークフローの例](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/)を参照してください。 +* Kubernetes YAML のカスタマイズエンジンは、「[Kustomize](https://kustomize.io/)」を参照してください。 +* Google Kubernetes Engine のドキュメントにある「[コンテナ化された Web アプリケーションのデプロイ](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)」を参照してください。 diff --git a/translations/ja-JP/content/actions/guides/index.md b/translations/ja-JP/content/actions/guides/index.md index e033b156ba..384289724d 100644 --- a/translations/ja-JP/content/actions/guides/index.md +++ b/translations/ja-JP/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/ja-JP/content/actions/guides/publishing-docker-images.md b/translations/ja-JP/content/actions/guides/publishing-docker-images.md index da81741c29..a576ffcbcc 100644 --- a/translations/ja-JP/content/actions/guides/publishing-docker-images.md +++ b/translations/ja-JP/content/actions/guides/publishing-docker-images.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - パッケージ化 + - Publishing + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -47,15 +51,15 @@ type: 'tutorial' 以下のワークフローの例では、Dockerの`build-push-action`アクションを使ってDockerイメージをビルドし、ビルドが成功すれば構築されたイメージをDocker Hubにプッシュします。 -Docker Hubにプッシュするためには、Docker Hubのアカウントを持っており、Docker Hubのレジストリを作成していなければなりません。 For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation. +Docker Hubにプッシュするためには、Docker Hubのアカウントを持っており、Docker Hubのレジストリを作成していなければなりません。 詳しい情報については、Docker のドキュメントにある「[Docker Hub でイメージを共有する](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)」を参照してください。 Docker Hubに必要な`build-push-action`のオプションは以下のとおりです。 -* `username`及び`password`: Docker Hubのユーザ名とパスワードです。 We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +* `username`及び`password`: Docker Hubのユーザ名とパスワードです。 ワークフローファイルに公開されないように、Docker Hub のユーザ名とパスワードをシークレットとして保存することをお勧めします。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 * `repository`: `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`フォーマットでのDocker Hubのリポジトリ。 {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -93,7 +97,7 @@ jobs: * `repository`: `OWNER/REPOSITORY/IMAGE_NAME`というフォーマットで設定しなければなりません。 たとえば、`http://github.com/octo-org/octo-repo`にある{% data variables.product.prodname_dotcom %}上に保存される`octo-image`という名前のイメージでは、`repository`オプションは`octo-org/octo-repo/octo-image`に設定しなければなりません。 {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -126,7 +130,7 @@ jobs: 以下のワークフローの例では、以前のセクション（「[Docker Hubへのイメージの公開](#publishing-images-to-docker-hub)」及び「[{% data variables.product.prodname_registry %}へのイメージの公開](#publishing-images-to-github-packages)」）での`build-push-action`ステップを使い、両方のレジストリにプッシュを行う1つのワークフローを作成します。 {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: diff --git a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md index 130f7eb968..7105cc47b1 100644 --- a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - パッケージ化 + - Publishing + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ _build.gradle_ファイルには、Gradleがパッケージを公開する配布 _build.gradle_ファイルのpublishingブロックには、パッケージリポジトリを指す新しいMavenリポジトリを定義できます。 たとえば、OSSRHホスティングプロジェクトを通じてMaven Central Repositoryにデプロイしていたなら、_build.gradle_ は`”OSSRH"`という名前でリポジトリを指定できます。 {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -67,7 +72,7 @@ publishing { {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -105,7 +110,7 @@ _build.gradle_のpublishingブロックには、{% data variables.product.prodna たとえば、Organizationの名前が"octocat"でリポジトリの名前が"hello-world"なら、_build.gradle_中の{% data variables.product.prodname_registry %}の設定は以下の例のようになるでしょう。 {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -126,7 +131,7 @@ publishing { この設定で、`gradle publish`コマンドの実行によってパッケージをMaven Central Repositoryに公開するワークフローを作成できます。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -162,7 +167,7 @@ _build.gradle_ファイルに、{% data variables.product.prodname_dotcom %}リ Organizationの名前が"octocat"でリポジトリの名前が"hello-world"なら、_build.gradle_中の{% data variables.product.prodname_registry %}の設定は以下の例のようになるでしょう。 {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -191,7 +196,7 @@ publishing { この設定で、`gradle publish`コマンドの実行によってパッケージをMaven Central Repositoryと{% data variables.product.prodname_registry %}の両方に公開するワークフローを作成できます。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md index 46453f5bcb..84e40b5c82 100644 --- a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - パッケージ化 + - Publishing + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -42,12 +47,12 @@ _pom.xml_ファイルには、Mavenがパッケージをデプロイする配布 新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればMaven Central Repositoryにパッケージを公開します。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/actions/reference/events-that-trigger-workflows#release)」を参照してください。 -このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールしますが、パッケージの公開のためのMavenの_settings.xml_も設定します。 デフォルトでは、設定ファイルは{% data variables.product.prodname_registry %}に対して設定されますが、Maven Central Repositoryなどの他のパッケージレジストリにデプロイするようにも設定できます。 _pom.xml_に設定済みの配布管理リポジトリが酢デイあるなら、`setup-java`アクションの呼び出しの際にその`id`を指定できます。 +このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールしますが、パッケージの公開のためのMavenの_settings.xml_も設定します。 デフォルトでは、設定ファイルは{% data variables.product.prodname_registry %}に対して設定されますが、Maven Central Repositoryなどの他のパッケージレジストリにデプロイするようにも設定できます。 _pom.xml_に設定済みの配布管理リポジトリがすでにあるなら、`setup-java`アクションの呼び出しの際にその`id`を指定できます。 たとえば、OSSRHホスティングプロジェクトを通じてMaven Central Repositoryにデプロイしていたなら、_pom.xml_ は`ossrh`の`id`で配布管理リポジトリを指定できます。 {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ _pom.xml_ファイルには、Mavenがパッケージをデプロイする配布 {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ Mavenベースのプロジェクトでは、{% data variables.product.prodname_r たとえば、Organizationの名前が"octocat"でリポジトリの名前が"hello-world"なら、_pom.xml_中の{% data variables.product.prodname_registry %}の設定は以下の例のようになるでしょう。 {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ Mavenベースのプロジェクトでは、{% data variables.product.prodname_r この設定で、自動的に生成された_settings.xml_を利用して{% data variables.product.prodname_registry %}にパッケージを公開するワークフローを作成できます。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ jobs: _pom.xml_ファイルに、{% data variables.product.prodname_dotcom %}リポジトリとMaven Central Repositoryプロバイダの双方に対する配布管理リポジトリを確実に含めてください。 たとえば、OSSRHホスティングプロジェクトを通じてCentral Repositoryへデプロイするなら、それを`id`を`ossrh`に設定して配布管理リポジトリ内で指定し、`id`を`github`に設定して配布管理リポジトリ内で{% data variables.product.prodname_registry %}を指定することになるかもしれません。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md index 4bb69c41ab..55188c5440 100644 --- a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md @@ -8,7 +8,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - パッケージ化 + - Publishing + - ノード + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -45,7 +50,7 @@ Node.jsプロジェクトのためのCIワークフローの作成に関する 新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればnpmレジストリにパッケージを公開します。 -To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 +ワークフロー中で npm レジストリに対して認証を受けた操作を行うためには、npm の認証トークンをシークレットとして保存しなければなりません。 たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 デフォルトでは、npmは*package.json*ファイルの`name`フィールドを使ってnpmレジストリを決めます。 グローバルな名前空間に公開する場合は、パッケージ名だけを含める必要があります。 たとえば`https://www.npmjs.com/package/npm-hello-world-test`に`npm-hello-world-test`という名前のパッケージを公開できます。 @@ -54,7 +59,7 @@ To perform authenticated operations against the npm registry in your workflow, y 以下の例は、`NPM_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -78,7 +83,7 @@ jobs: 上の例では、`setup-node`アクションは以下の内容でランナー上に*.npmrc*ファイルを作成します。 -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -88,11 +93,11 @@ always-auth=true 新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。 -#### Configuring the destination repository +#### 宛先リポジトリの設定 -If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. +*package.json* ファイルで `repository` キーを指定しない場合、{% data variables.product.prodname_registry %} は *package.json* ファイルの `name` フィールドで指定した {% data variables.product.prodname_dotcom %} リポジトリにパッケージを公開します。 たとえば、`@my-org/test` という名前のパッケージは、`my-org/test` {% data variables.product.prodname_dotcom %} というリポジトリに公開されます。 -However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. +ただし、`repository` キーを指定すると、そのキーのリポジトリが {% data variables.product.prodname_registry %} の宛先 npm レジストリとして使用されます。 たとえば、以下の *package.json* を公開すると、`my-amazing-package` という名前のパッケージが `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} リポジトリに公開されます。 ```json { @@ -103,18 +108,18 @@ However, if you do provide the `repository` key, then the repository in that key }, ``` -#### Authenticating to the destination repository +#### 宛先リポジトリへの認証 -To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." +ワークフローで {% data variables.product.prodname_registry %} レジストリに対して認証するには、リポジトリから `GITHUB_TOKEN` を使用できます。 これは自動的に作成され、ワークフローが実行されるリポジトリ内のパッケージに対する_読み取り_および_書き込み_権限があります。 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」を参照してください。 -If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. 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)." +パッケージを別のリポジトリに公開する場合は、宛先リポジトリ内のパッケージに書き込む権限を持つ個人アクセストークン (PAT) を使用する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。 -#### Example workflow +#### ワークフローの例 以下の例は、`GITHUB_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -140,7 +145,7 @@ jobs: `setup-node`アクションは、ランナー上で*.npmrc*ファイルを作成します。 `setup-node`アクションで`scope`インプットを使うと、*.npmrc*ファイルにはスコーププレフィックスが含まれます。 デフォルトでは、`setup-node`アクションは*.npmrc*ファイルのスコープを、ワークフローファイルを含むアカウントに設定します。 -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -151,7 +156,7 @@ always-auth=true パッケージマネージャーのYarnを使う場合、Yarnを使ってパッケージのインストールと公開が行えます。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -161,13 +166,13 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - # npm に公開する .npmrc ファイルを設定する + # Setup .npmrc file to publish to npm - uses: actions/setup-node@v1 with: node-version: '12.x' registry-url: 'https://registry.npmjs.org' - # デフォルトはワークフローファイルを所有するユーザまたは Organization - scope: '@octocat' + # Defaults to the user or organization that owns the workflow file + scope: '@octocat' - run: yarn - run: yarn publish env: @@ -179,7 +184,7 @@ jobs: {% note %} -**ノート：** 異なるスコーププレフィックスを持つレジストリへ公開する必要がある倍は、ランナー上の*package.json*ファイルを修正してスコーププレフィックスを変更しなければなりません。 たとえばnpmに対しては`@mona`スコープで、{% data variables.product.prodname_registry %}に対しては`@octocat`スコープでパッケージを公開する場合は、npmへの公開後、{% data variables.product.prodname_registry %}への公開前にランナー上の*package.json*ファイルの`@mona`スコープを`@octocat`で置き換えることができます。 +**ノート：** 異なるスコーププレフィックスを持つレジストリへ公開する必要がある場合は、ランナー上の*package.json*ファイルを修正してスコーププレフィックスを変更しなければなりません。 たとえばnpmに対しては`@mona`スコープで、{% data variables.product.prodname_registry %}に対しては`@octocat`スコープでパッケージを公開する場合は、npmへの公開後、{% data variables.product.prodname_registry %}への公開前にランナー上の*package.json*ファイルの`@mona`スコープを`@octocat`で置き換えることができます。 {% endnote %} @@ -196,7 +201,7 @@ jobs: このワークフローは、`setup-node`アクションを2回呼びます。 `setup-node`アクションは、実行されるたびに*.npmrc*ファイルを上書きします。 *.npmrc*ファイルは、パッケージレジストリに対する認証を受けた操作を行えるようにしてくれるトークンを、環境変数の`NODE_AUTH_TOKEN`から参照します。 このワークフローは、環境変数の`NODE_AUTH_TOKEN`を`npm publish`コマンドが実行されるたびに設定します。初回はnpmへの公開のためのトークン（`NPM_TOKEN`）が、続いて{% data variables.product.prodname_registry %}への公開のためのトークン（`GITHUB_TOKEN`）が使われます。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: diff --git a/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 60358c25a2..af1b9c38eb 100644 --- a/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,7 +11,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - ワークフロー + - CI --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md index eb069b0071..53101f8d6e 100644 --- a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -1,6 +1,6 @@ --- -title: ワークフロー データをアーティファクトとして保存する -shortTitle: ワークフロー アーティファクトを保存する +title: ワークフロー データを成果物として保存する +shortTitle: ワークフローの成果物を保存する intro: 成果物を使うと、ワークフロー内のジョブ間でデータを共有し、ワークフローが完了したときに、そのワークフローのデータを保存できます。 product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -11,7 +11,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - ワークフロー --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +38,7 @@ type: 'tutorial' {% else %} -アーティファクトは、{% data variables.product.product_location %} 上の {% data variables.product.prodname_actions %} 向けに設定された外部 blob ストレージ上のストレージスペースを消費します。 +成果物は、{% data variables.product.product_location %} 上の {% data variables.product.prodname_actions %} 向けに設定された外部 blob ストレージ上のストレージスペースを消費します。 {% endif %} @@ -79,7 +81,7 @@ type: 'tutorial' このワークフローは `dist` ディレクトリにプロダクションの成果物をアップロードしますが、Markdownファイルはその対象外です。 また、 `code-coverage.html`レポートは別の成果物としてアップロードされます。 -```yaml +```yaml{:copy} name: Node CI on: [push] @@ -110,11 +112,11 @@ jobs: ``` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### カスタムアーティファクトの保持期間を設定する +### カスタムの成果物の保持期間を設定する -ワークフローによって作成された個々のアーティファクトのカスタム保存期間を定義できます。 ワークフローを使用して新しいアーティファクトを作成する場合、`upload-artifact` アクションで `retention-days` を使用できます。 この例は、`my-artifact` という名前のアーティファクトに 5 日間のカスタム保存期間を設定する方法を示しています。 +ワークフローによって作成された個々の成果物のカスタム保存期間を定義できます。 ワークフローを使用して新しい成果物を作成する場合、`upload-artifact` アクションで `retention-days` を使用できます。 この例は、`my-artifact` という名前の成果物に 5 日間のカスタム保存期間を設定する方法を示しています。 -``` +```yaml{:copy} - name: 'Upload Artifact' uses: actions/upload-artifact@v2 with: @@ -128,13 +130,13 @@ jobs: ### 成果物のダウンロードあるいは削除 -ワークフローの実行中に、[`download-artifactaction`](https://github.com/actions/download-artifact) を使用して、同じワークフローの実行で以前にアップロードされたアーティファクトをダウンロードできます。 +ワークフローの実行中に、[`download-artifactaction`](https://github.com/actions/download-artifact) を使用して、同じワークフローの実行で以前にアップロードされた成果物をダウンロードできます。 -ワークフローの実行が完了したら、{% data variables.product.prodname_dotcom %} または REST API を使用してアーティファクトをダウンロードまたは削除できます。 詳しい情報については、「[ワークフローアーティファクトをダウンロードする](/actions/managing-workflow-runs/downloading-workflow-artifacts)」、「[ワークフローアーティファクトを削除する](/actions/managing-workflow-runs/removing-workflow-artifacts)」、および「[アーティファクト REST API](/rest/reference/actions#artifacts)」を参照してください。 +ワークフローの実行が完了したら、{% data variables.product.prodname_dotcom %} または REST API を使用して成果物をダウンロードまたは削除できます。 詳しい情報については、「[ワークフローの成果物をダウンロードする](/actions/managing-workflow-runs/downloading-workflow-artifacts)」、「[ワークフローの成果物を削除する](/actions/managing-workflow-runs/removing-workflow-artifacts)」、および「[Artifacts REST API](/rest/reference/actions#artifacts)」を参照してください。 #### ワークフロー実行中の成果物のダウンロード -[`actions/download-artifact`](https://github.com/actions/download-artifact) のダウンロードアクションを使用して、ワークフローの実行中に以前にアップロードされたアーティファクトをダウンロードできます。 +[`actions/download-artifact`](https://github.com/actions/download-artifact) のダウンロードアクションを使用して、ワークフローの実行中に以前にアップロードされた成果物をダウンロードできます。 {% note %} @@ -170,12 +172,12 @@ jobs: ジョブ1は、以下のステップを実行します。 - 数式の計算を実行し、その結果を`math-homework.txt`というテキストファイルに保存します。 -- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`. +- `upload-artifact` アクションを使って、`math-homework.txt` ファイルを `homework` という成果物名でアップロードします。 ジョブ2は、前のジョブの結果を利用して、次の処理を実行します。 - 前のジョブでアップロードされた`homework`成果物をダウンロードします。 デフォルトでは、`download-artifact`アクションは、ステップが実行されているワークスペースディレクトリに成果物をダウンロードします。 入力パラメータの`path`を使って、別のダウンロードディレクトリを指定することもできます。 -- 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. -- `math-homework.txt`ファイルをアップロードします。 This upload overwrites the previously uploaded artifact because they share the same name. +- `math-homework.txt` ファイル中の値を読み取り、数式の計算を実行して、結果を `math-homework.txt` に再度保存し、その内容を上書きします。 +- `math-homework.txt`ファイルをアップロードします。 このアップロードでは、同じ名前を共有しているため、以前にアップロードされた成果物を上書きします。 ジョブ3は、前のジョブでアップロードされた結果を表示して、次の処理を実行します。 - `homework`成果物をダウンロードします。 @@ -183,7 +185,7 @@ jobs: このワークフロー例で実行される完全な数式は、`(3 + 7) x 9 = 90`です。 -```yaml +```yaml{:copy} name: Share data between jobs on: [push] @@ -237,7 +239,7 @@ jobs: echo The result is $value ``` -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)." +ワークフローの実行により、生成された成果物がアーカイブされます。 アーカイブされた成果物のダウンロードの詳細については、「[ワークフローの成果物をダウンロードする](/actions/managing-workflow-runs/downloading-workflow-artifacts)」を参照してください。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![ジョブ間でデータを受け渡して計算を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) {% else %} @@ -248,6 +250,6 @@ The workflow run will archive any artifacts that it generated. For more informat ### 参考リンク -- /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions +- [{% data variables.product.prodname_actions %}の支払いの管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions) {% endif %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 840fe066d7..feeb35852a 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -1,5 +1,5 @@ --- -title: 自己ホストランナーについて +title: セルフホストランナーについて intro: '独自のランナーをホストして、{% data variables.product.prodname_actions %}ワークフロー中でジョブの実行に使われる環境をカスタマイズできます。' redirect_from: - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners @@ -7,13 +7,13 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### 自己ホストランナーについて +### セルフホストランナーについて {% data reusables.github-actions.self-hosted-runner-description %} セルフホストランナーは、物理、仮想、コンテナ内、オンプレミス、クラウド内のいずれでも可能です。 @@ -96,13 +96,13 @@ type: 'overview' ### セルフホストランナーと{% data variables.product.prodname_dotcom %}との通信 -そのマシンが{% data variables.product.prodname_actions %}と通信できる。 詳しい情報については「[セルフホストランナーと{% data variables.product.prodname_dotcom %}の通信](#communication-between-self-hosted-runners-and-github)」を参照してください。 +{% data variables.product.prodname_ghe_server %}とあわせて{% data variables.product.prodname_dotcom_the_website %}からアクションを使う場合、あるいはインターネットアクセスのないセルフホストランナーで`actions/setup-LANGUAGE`アクションを使う場合には、多少の追加設定が必要になるかもしれません。 詳しい情報については「[{% data variables.product.prodname_dotcom_the_website %}からのアクションへのアクセスの管理](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)」を参照し、{% data variables.product.prodname_enterprise %}のサイト管理者に連絡してください。 {% endif %} ### セルフホストランナーと{% data variables.product.product_name %}との通信 -The self-hosted runner polls {% data variables.product.prodname_dotcom %} 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.prodname_dotcom %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. アプリケーションは、{% data variables.product.prodname_actions %}ジョブを受け付けて実行するためにマシン上で動作していなければなりません。 +セルフホストランナーは{% data variables.product.product_name %}をポーリングして、アプリケーションのアップデートを取得し、処理のためにジョブがキューイングされていないかチェックします。 セルフホストランナーはHTTPSの_ロングポーリング_を使います。これは{% data variables.product.product_name %}に対して50秒間接続を開き、レスポンスがなければタイムアウトして新しいロングポーリングを生成します。 アプリケーションは、{% data variables.product.prodname_actions %}ジョブを受け付けて実行するためにマシン上で動作していなければなりません。 {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 9e07f48fea..676b0fcdbe 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -1,21 +1,21 @@ --- -title: 自己ホストランナーの追加 -intro: '{{ site.data.variables.product.prodname_actions }}にセルフホストランナーを追加できます。' +title: セルフホストランナーの追加 +intro: リポジトリ、Organization、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: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{{ site.data.variables.product.prodname_actions }}にセルフホストランナーを追加できます。 +リポジトリ、Organization、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. +Organization または Enterprise 管理者の場合は、Organization または Enterprise レベルでセルフホストランナーを追加することをお勧めします。 このアプローチにより、Organization または Enterprise 内の複数のリポジトリでランナーを使用できるようになり、ランナーを1か所で管理することもできます。 セルフホストランナーでサポートされているオペレーティングシステム、あるいはプロキシサーバーとセルフホストランナーを使う方法に関する情報については、「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。 @@ -53,13 +53,13 @@ If you are an organization or enterprise administrator, you might want to add yo ### セルフホストランナーを Enterprise に追加する -セルフホストランナーを Enterprise に追加して、複数の Organization に割り当てることができます。 Organization の管理者は、そのリポジトリの使用対象を制御できます。 +セルフホストランナーを Enterprise に追加して、複数の Organization に割り当てることができます。 Organization の管理者は、そのランナーを使用できるリポジトリを制御できます。 {% if currentVersion == "free-pro-team@latest" %} セルフホストランナーを Enterprise アカウントに追加するには、Enterprise のオーナーである必要があります。 {% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} セルフホストランナーを -{% data variables.product.product_location %} の Enterprise レベルでを追加するには、サイト管理者である必要があります。 +{% data variables.product.product_location %} の Enterprise レベルで削除するには、サイト管理者である必要があります。 {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} @@ -72,10 +72,10 @@ If you are an organization or enterprise administrator, you might want to add yo {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -#### Making enterprise runners available to repositories +#### Enterprise ランナーをリポジトリで利用可能にする -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. +デフォルトでは、Enterprise の「デフォルト」のセルフホストランナーグループのランナーは、Enterprise 内のすべての Organization で使用できますが、各 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. +Enterprise レベルのセルフホストランナーグループを Organization リポジトリで使用できるようにするには、ランナーグループの Organization の継承設定を変更して、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)." +ランナーグループのアクセス設定の変更に関する詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/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/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index eefc591137..0766621563 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial defaultPlatform: linux --- @@ -81,7 +81,7 @@ Windowsでは、ランナーサービスは**サービス**アプリケーショ {% linux %} ```shell -./svc.sh install +sudo ./svc.sh start ``` {% endlinux %} {% windows %} @@ -101,7 +101,7 @@ Start-Service "{{ service_win_name }}" {% linux %} ```shell -./svc.sh start +sudo ./svc.sh status ``` {% endlinux %} {% windows %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 3a2dca8808..87700452dc 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -42,9 +42,9 @@ Enterprise の管理者が Organization にランナーグループへのアク 1. [**Self-hosted runners**] セクションで、[**Add new**] をクリックし、次に [**New group**] をクリックします。 ![新しいランナーを追加](/assets/images/help/settings/actions-org-add-runner-group.png) -1. Enter a name for your runner group, and assign a policy for repository access. +1. ランナーグループの名前を入力し、リポジトリアクセスのポリシーを割り当てます。 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} リポジトリの特定のリスト、または Organization 内のすべてのリポジトリにアクセスできるようにランナーグループを設定できます。 デフォルトでは、パブリックリポジトリはランナーグループ内のランナーにアクセスできませんが、[**Allow public repositories**] オプションを使用してこれをオーバーライドできます。{% else if currentVersion == "enterprise-server@2.22"%} リポジトリの特定のリスト、すべてのプライベートリポジトリ、または Organization 内のすべてのリポジトリにアクセスできるようにランナーグループを設定できます。{% endif %} {% warning %} @@ -65,7 +65,7 @@ Enterprise は、セルフホストランナーをグループに追加して、 セルフホストランナーは、作成時にデフォルトグループに自動的に割り当てられ、一度に 1 つのグループのメンバーになることができます。 登録処理中にランナーを特定のグループに割り当てることも、後でランナーをデフォルトグループからカスタムグループに移動することもできます。 -When creating a group, you must choose a policy that defines which organizations have access to the runner group. +グループを作成するときは、ランナーグループにアクセスできる Organization を定義するポリシーを選択する必要があります。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -74,9 +74,9 @@ When creating a group, you must choose a policy that defines which organizations 1. [**Add new**] をクリックしてから、[**New group**] をクリックします。 ![新しいランナーを追加](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) -1. Enter a name for your runner group, and assign a policy for organization access. +1. ランナーグループの名前を入力し、Organization アクセスのポリシーを割り当てます。 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ランナーグループを設定して、特定の Organization のリスト、または Enterprise 内のすべての Organization にアクセスできるようにすることができます。 デフォルトでは、パブリックリポジトリはランナーグループ内のランナーにアクセスできませんが、[**Allow public repositories**] オプションを使用してこれをオーバーライドできます。{% else if currentVersion == "enterprise-server@2.22"%} Enterprise 内のすべての Organization がアクセスできるようにランナーグループを設定することも、特定の Organization を選択することもできます。{% endif %} {% warning %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 7b25bee88c..c7e02f7762 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -64,8 +64,8 @@ Organizationからセルフホストランナーを削除するには、Organiza {% if currentVersion == "free-pro-team@latest" %} セルフホストランナーを Enterprise アカウントから削除するには、Enterprise のオーナーである必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 {% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} -次の Enterprise レベルでセルフホストランナーを削除するには、 -{% data variables.product.product_location %} の Enterprise レベルでを追加するには、サイト管理者である必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 +セルフホストランナーを +{% data variables.product.product_location %} の Enterprise レベルで削除するには、サイト管理者である必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 {% endif %} {% data reusables.github-actions.self-hosted-runner-reusing %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 98b4abfbec..5c5ad3447b 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +38,7 @@ Windowsマシンで、プロキシ環境変数名で大文字小文字は区別 以下に_.env_プロキシ設定の例を示します。 -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index c46df77faf..4cb61238c2 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,7 +4,7 @@ intro: ラベルを使い、セルフホストランナーを特徴を基に整 versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -20,7 +20,7 @@ type: 'tutorial' {% data reusables.github-actions.self-hosted-runner-list %} {% data reusables.github-actions.self-hosted-runner-list-group %} {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} -1. "Filter labels（フィルターラベル）"フィールドで、新しいラベルの名前を入力し、**Create new label（新しいラベルの作成）　**をクリックしてください。 ![ランナーにラベルを追加](/assets/images/help/settings/actions-add-runner-label.png) +1. "Filter labels（フィルターラベル）"フィールドで、新しいラベルの名前を入力し、**Create new label（新しいラベルの作成）**をクリックしてください。 ![ランナーにラベルを追加](/assets/images/help/settings/actions-add-runner-label.png) カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 0500f05a61..2d046fdcb5 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -1,13 +1,13 @@ --- title: ワークフローでのセルフホストランナーの利用 -intro: 'ワークフローでセルフホストランナーを使うには、ラベルを使ってジョブのためのランナーの種類を指定できます。' +intro: ワークフローでセルフホストランナーを使うには、ラベルを使ってジョブのためのランナーの種類を指定できます。 redirect_from: - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -64,8 +64,11 @@ runs-on: [self-hosted, linux, x64, gpu] ### セルフホストランナーのルーティングの優先順位 -リポジトリレベルと Organization レベルの両方のランナーを使用する場合、{% data variables.product.prodname_dotcom %} は、次の優先順位に従ってジョブをセルフホストランナーにルーティングします。 +ジョブをセルフホストランナーにルーティングする際に、{% data variables.product.prodname_dotcom %}はジョブの`runs-on`ラベルにマッチするランナーを探します。 -1. ジョブの `runs-on` ラベルが処理されます。 次に、{% data variables.product.prodname_dotcom %} は、ラベル要件に一致するランナーを検索します。 -2. ジョブは、ジョブラベルに一致するリポジトリレベルのランナーに送信されます。 リポジトリレベルのランナーが利用できない（ビジー、オフライン、または一致するラベルがない）場合: -3. ジョブは、ジョブラベルに一致する Organization レベルのランナーに送信されます。 Organization レベルのランナーが利用できない場合、ジョブ要求はエラーで失敗します。 +1. {% data variables.product.prodname_dotcom %}ま、まずリポジトリレベルで、続いてOrganizationのレベルで{% if currentVersion ver_gt "enterprise-server@2.21" %}、そしてEnterpriseのレベルで{% endif %}ランナーを探します。 +2. ジョブは最初にマッチした、オンラインでアイドル状態のランナーに送信されます。 + - マッチしたすべてのランナーがビジーだった場合、ジョブはマッチしたオンラインのランナーが最も多いレベルでキューイングされます。 + - マッチしたランナーがすべてオフラインだった場合、ジョブはマッチしたオフラインのランナーが最も多いレベルでキューイングされます。 + - マッチするランナーがどのレベルにもなかった場合、そのジョブは失敗します。 + - 24時間以上にわたってキューに残っていたジョブは失敗します。 diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md index 03fee5cffe..765c305b9f 100644 --- a/translations/ja-JP/content/actions/index.md +++ b/translations/ja-JP/content/actions/index.md @@ -1,7 +1,7 @@ --- title: GitHub Actionsのドキュメント shortTitle: GitHub Actions -intro: '{% data variables.product.prodname_actions %}で、ソフトウェア開発ワークフローをリポジトリの中で自動化、カスタマイズ実行しましょう。 CI/CDを含む好きなジョブを実行してくれるアクションを、見つけたり、作成したり、共有したり、完全にカスタマイズされたワークフロー中でアクションを組み合わせたりできます。' +intro: '{% data variables.product.prodname_actions %}で、ソフトウェア開発ワークフローをリポジトリの中で自動化し、カスタマイズし、実行しましょう。 CI/CDを含む好きなジョブを実行してくれるアクションを、見つけたり、作成したり、共有したり、完全にカスタマイズされたワークフロー中でアクションを組み合わせたりできます。' introLinks: quickstart: /actions/quickstart reference: /actions/reference @@ -10,33 +10,30 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: - - title: Workflow visualization + title: 環境、環境の保護ルール、環境のシークレット（ベータ） + date: '2020-12-15' + href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ + - + title: ワークフローの視覚化 date: '2020-12-08' href: https://github.blog/changelog/2020-12-08-github-actions-workflow-visualization/ - - title: Removing set-env and add-path commands on November 16 + title: 11月16日に set-env コマンドと add-path コマンドを削除します date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Ubuntu-latest workflows will use Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ @@ -63,23 +60,23 @@ versions: {% assign actionsCodeExamples = site.data.variables.action_code_examples %} {% if actionsCodeExamples %}
      -

      Code examples

      +

      コード例

      - +
      {% render 'code-example-card' for actionsCodeExamples as example %}
      - +
      {% octicon "search" width="24" %}
      -

      Sorry, there is no result for

      -

      It looks like we don't have an example that fits your filter.
      Try another filter or add your code example

      - Learn how to add a code example {% octicon "arrow-right" %} +

      検索結果はありません

      +

      フィルタに適合する例がないようです。
      別のフィルタを試すか、コード例を追加してください

      + コード例を追加する方法 {% octicon "arrow-right" %}
      {% endif %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md index 8b81ab9926..d5cb730df7 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,7 +5,9 @@ intro: '{% data variables.product.prodname_actions %} は、堅牢で動的な versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -13,7 +15,7 @@ type: 'overview' ### 概要 -{% data variables.product.prodname_actions %} を使用すると、アプリケーションと Team の固有のニーズに合わせてワークフローをカスタマイズできます。 このガイドでは、変数の使用、スクリプトの実行、ジョブ間でのデータとアーティファクトの共有など、いくつかの重要なカスタマイズ手法について説明します。 +{% data variables.product.prodname_actions %} を使用すると、アプリケーションと Team の固有のニーズに合わせてワークフローをカスタマイズできます。 このガイドでは、変数の使用、スクリプトの実行、ジョブ間でのデータと成果物の共有など、いくつかの重要なカスタマイズ手法について説明します。 ### ワークフローで変数を使用する @@ -58,9 +60,9 @@ jobs: ### ジョブ間でデータを共有する -ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_アーティファクト_として {% data variables.product.prodname_dotcom %} に保存できます。 成果物とは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、成果物には、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 アーティファクトは、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 +ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_成果物_として {% data variables.product.prodname_dotcom %} に保存できます。 成果物とは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、成果物には、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 成果物は、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 -たとえば、ファイルを作成し、それをアーティファクトとしてアップロードできます。 +たとえば、ファイルを作成し、それを成果物としてアップロードできます。 ```yaml jobs: @@ -77,7 +79,7 @@ jobs: path: output.log ``` -別のワークフロー実行からアーティファクトをダウンロードするには、`actions/download-artifact` アクションを使用できます。 たとえば、`output-log-file` という名前のアーティファクトをダウンロードできます。 +別のワークフロー実行から成果物をダウンロードするには、`actions/download-artifact` アクションを使用できます。 たとえば、`output-log-file` という名前の成果物をダウンロードできます。 ```yaml jobs: @@ -89,7 +91,7 @@ jobs: name: output-log-file ``` -アーティファクトに関する詳しい情報については「[アーティファクトを利用してワークフローのデータを永続化する](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)」を参照してください。 +成果物に関する詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)」を参照してください。 ### 次のステップ diff --git a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md index 143f2bd8dd..b46f20d5bd 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -1,7 +1,7 @@ --- title: アクションの検索とカスタマイズ shortTitle: アクションの検索とカスタマイズ -intro: 'アクションは、ワークフローを動かす構成要素です。 ワークフローには、コミュニティによって作成されたアクションを含めることも、アプリケーションのリポジトリ内に直接独自のアクションを作成することもできます。 このガイドでは、アクションを検出、使用、およびカスタマイズする方法を説明します。' +intro: 'アクションは、ワークフローを動かす構成要素です。 ワークフローには、コミュニティによって作成されたアクションを含めることも、アプリケーションのリポジトリ内に直接独自のアクションを作成することもできます。 このガイドでは、アクションを発見、使用、およびカスタマイズする方法を説明します。' redirect_from: - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} @@ -18,7 +20,7 @@ type: 'how_to' ### 概要 -ワークフローで使用するアクションは、次のように定義できます。 +ワークフローで使用するアクションは、以下の場所で定義できます。 - パブリック リポジトリ - ワークフローファイルがアクションを参照するのと同じリポジトリ @@ -68,7 +70,7 @@ steps: #### SHA の使用 -より信頼性の高いバージョン管理が必要な場合は、アクションのバージョンに関連付けられた SHA 値を使用する必要があります。 SHA は不変であるため、タグやブランチよりも信頼性が高くなります。 ただし、このアプローチでは、重要なバグ修正やセキュリティアップデートなど、アクションの更新を自動的に受信しません。 この例では、アクションの SHA を対象としています。 +より信頼性の高いバージョン管理が必要な場合は、アクションのバージョンに関連付けられた SHA 値を使用する必要があります。 SHA は不変であるため、タグやブランチよりも信頼性が高くなります。 ただし、このアプローチでは、重要なバグ修正やセキュリティアップデートなど、アクションの更新を自動的に受信しません。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}短縮された値ではなく、コミットの完全なSHA値を使わなければなりません。 {% endif %}この例ではアクションのSHAを対象としています。 ```yaml steps: @@ -77,7 +79,7 @@ steps: #### ブランチの使用 -Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. この例では、`@main` という名前のブランチを対象としています。 +アクションのターゲットブランチを指定すると、そのブランチに現在あるバージョンが常に実行されます。 ブランチの更新に重大な変更が含まれている場合、このアプローチは問題を引き起こす可能性があります。 この例では、`@main` という名前のブランチを対象としています。 ```yaml steps: @@ -88,7 +90,7 @@ steps: ### アクションで入力と出力を使用する -多くの場合、アクションは入力を受け入れたり要求したりして、使用できる出力を生成します。 For example, an action might require you to specify a path to a file, the name of a label, or other data it will use as part of the action processing. +多くの場合、アクションは入力を受け入れたり要求したりして、使用できる出力を生成します。 たとえば、アクションでは、ファイルへのパス、ラベルの名前、またはアクション処理の一部として使用するその他のデータを指定する必要がある場合があります。 アクションの入力と出力を確認するには、リポジトリのルートディレクトリにある `action.yml` または `action.yaml` を確認してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md index 972d0d916d..3c8984e71d 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -9,7 +9,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -17,7 +19,7 @@ type: 'overview' ### 概要 -{% data variables.product.prodname_actions %} は、ソフトウェア開発ライフサイクル内のタスクを自動化するのに役立ちます。 {% data variables.product.prodname_actions %} はイベント駆動型で、指定されたイベントが発生した後に一連のコマンドを実行できます。 たとえば、誰かがリポジトリのプルリクエストを作成するたびに、ソフトウェアテストスクリプトを実行するコマンドを自動的に実行できます。 +{% data variables.product.prodname_actions %} は、ソフトウェア開発ライフサイクル内のタスクを自動化するのに役立ちます。 {% data variables.product.prodname_actions %} はイベント駆動型で、指定されたイベントが発生した後に一連のコマンドを実行できます。 たとえば、誰かがリポジトリのPull Requestを作成するたびに、ソフトウェアテストスクリプトを実行するコマンドを自動的に実行できます。 この図は、{% data variables.product.prodname_actions %} を使用してソフトウェアテストスクリプトを自動的に実行する方法を示しています。 イベントは、_ジョブ_を含む_ワークフロー_を自動的にトリガーします。 次に、ジョブは_ステップ_を使用して、_アクション_が実行される順序を制御します。 これらのアクションは、ソフトウェアテストを自動化するコマンドです。 @@ -31,11 +33,11 @@ type: 'overview' #### ワークフロー -ワークフローは、リポジトリに追加する自動化された手順です。 ワークフローは 1 つ以上のジョブで構成されており、イベントによってスケジュールまたはトリガーできます。 ワークフローを使用して、{% data variables.product.prodname_dotcom %} でプロジェクトをビルド、テスト、パッケージ、リリース、またはデプロイできます。 +ワークフローは、リポジトリに追加する自動化された手順です。 ワークフローは 1 つ以上のジョブで構成されており、スケジュールまたはイベントによってトリガーできます。 ワークフローを使用して、{% data variables.product.prodname_dotcom %} でプロジェクトをビルド、テスト、パッケージ、リリース、またはデプロイできます。 #### イベント -イベントは、ワークフローをトリガーする特定のアクティビティです。 たとえば、誰かがコミットをリポジトリにプッシュした場合、あるいはIssueもしくはプルリクエストが作成された場合、{% data variables.product.prodname_dotcom %}からアクティビティを発生させることができます。 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. ワークフローのトリガーに使用できるイベントの完全なリストについては、[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)を参照してください。 +イベントは、ワークフローをトリガーする特定のアクティビティです。 たとえば、誰かがコミットをリポジトリにプッシュした場合、あるいはIssueもしくはPull Requestが作成された場合、{% data variables.product.prodname_dotcom %}からアクティビティを発生させることができます。 [リポジトリディスパッチ webhook](/rest/reference/repos#create-a-repository-dispatch-event) を使用して、外部イベントが発生したときにワークフローをトリガーすることもできます。 ワークフローのトリガーに使用できるイベントの完全なリストについては、[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)を参照してください。 #### ジョブ @@ -43,7 +45,7 @@ type: 'overview' #### ステップ -A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. ジョブの各ステップは同じランナーで実行され、そのジョブのアクションが互いにデータを共有できるようにします。 +ステップは、ジョブでコマンドを実行できる個々のタスクです。 ステップは、_アクション_またはシェルコマンドのいずれかです。 ジョブの各ステップは同じランナーで実行され、そのジョブのアクションが互いにデータを共有できるようにします。 #### アクション @@ -51,7 +53,7 @@ _アクション_は、_ジョブ_を作成するために_ステップ_に結 #### ランナー -A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. {% data variables.product.prodname_dotcom %} がホストするランナーを使用することも、自分でランナーをホストすることもできます。 ランナーは、使用可能なジョブをリッスンし、一度に 1 つのジョブを実行し、進行状況、ログ、および結果を {% data variables.product.prodname_dotcom %} に返します。 {% data variables.product.prodname_dotcom %}ホストランナーでは、ワークフロー内の各ジョブは新しい仮想環境で実行されます。 +ランナーは、[{% data variables.product.prodname_actions %}ランナーアプリケーション](https://github.com/actions/runner)がインストールされているサーバーです。 {% data variables.product.prodname_dotcom %} がホストするランナーを使用することも、自分でランナーをホストすることもできます。 ランナーは、使用可能なジョブをリッスンし、一度に 1 つのジョブを実行し、進行状況、ログ、および結果を {% data variables.product.prodname_dotcom %} に返します。 {% data variables.product.prodname_dotcom %}ホストランナーでは、ワークフロー内の各ジョブは新しい仮想環境で実行されます。 {% data variables.product.prodname_dotcom %} ホストランナーは、Ubuntu Linux、Microsoft Windows、および macOS に基づいています。 {% data variables.product.prodname_dotcom %} ホストランナーの詳細については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners)」を参照してください。 別のオペレーティングシステムが必要な場合、または特定のハードウェア設定が必要な場合は、自分のランナーをホストできます。 セルフホストランナーの詳細については、「[自分のランナーをホストする](/actions/hosting-your-own-runners)」を参照してください。 @@ -147,7 +149,7 @@ YAML 構文を使用してワークフローファイルを作成する方法を ```
    		- check-bats-version ジョブで実行されるすべてのステップをグループ化します。 このセクションの下にネストされた各行は、個別のアクションです。 + check-bats-version ジョブで実行されるすべてのステップをグループ化します。 このセクションの下にネストされている各アイテム、個別のアクションもしくはシェルコマンドです。
    - uses キーワードは、actions/checkout@v2 という名前のコミュニティアクションの v2 を取得するようにジョブに指示します。 これは、リポジトリをチェックアウトしてランナーにダウンロードし、コード（テストツールなど）に対してアクションを実行できるようにします。 ワークフローがリポジトリのコードに対して実行されるとき、またはリポジトリで定義されたアクションを使用しているときはいつでも、チェックアウトアクションを使用する必要があります。 + uses キーワードは、actions/checkout@v2 という名前のコミュニティアクションの v2 を取得するようにジョブに指示します。 これは、リポジトリをチェックアウトしてランナーにダウンロードし、コードに対してアクション（テストツールなど）を実行できるようにします。 ワークフローがリポジトリのコードに対して実行されるとき、またはリポジトリで定義されたアクションを使用しているときはいつでも、チェックアウトアクションを使用する必要があります。
    - run キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、npm を使用して bats ソフトウェアテストパッケージをインストールしています。 + run キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、npm を使用して bats ソフトウェアテストパッケージをインストールしています。
    -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_actions %} キャッシングは、{% data variables.product.prodname_dotcom %} ホストランナーにのみ適用できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 {% data variables.product.prodname_actions %}は、CircleCIのDocker Layer Caching（DLC）に相当する機能を持っていません。 @@ -258,24 +263,24 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 - # Add a health check + - 5432:5432 + # ヘルスチェックを追加 options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem 参照 - - name: Setup file system permissions - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake + # このDockerファイルは、デフォルトユーザではなくUSERをcirceciに変更するので、このイメージのファイルの権限をGH Actionsで動作するように変更しなければならない。 + # https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem を参照 + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} @@ -412,35 +417,35 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 - # ヘルスチェックを追加する + - 5432:5432 + # ヘルスチェックを追加 options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - - uses: actions/checkout@v2 - - name: Setup Ruby - uses: eregon/use-ruby-action@master - with: - ruby-version: ${{ matrix.ruby }} - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: vendor/bundle - key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - name: Install postgres headers - run: sudo apt-get install libpq-dev - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake - - name: Install appraisal - run: bundle exec appraisal install - - name: Run appraisal - run: bundle exec appraisal rake + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index a979e521a8..a934181c92 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,7 +4,12 @@ intro: '{% data variables.product.prodname_actions %} と GitLab CI/CDはいく versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - GitLab + - 移行 + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,23 +340,23 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_actions %} キャッシングは、{% data variables.product.prodname_dotcom %} ホストランナーにのみ適用できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ### 成果物 -GitLab CI/CD と {% data variables.product.prodname_actions %} はどちらも、ジョブによって作成されたファイルとディレクトリをアーティファクトとしてアップロードできます。 {% data variables.product.prodname_actions %} では、アーティファクトを使用して、複数のジョブ間でデータを永続化できます。 +GitLab CI/CD と {% data variables.product.prodname_actions %} はどちらも、ジョブによって作成されたファイルとディレクトリを成果物としてアップロードできます。 {% data variables.product.prodname_actions %} では、成果物を使用して、複数のジョブ間でデータを永続化できます。 以下が、それぞれのシステムの構文の例です。 @@ -371,7 +376,7 @@ GitLab CI/CD script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -389,7 +394,7 @@ artifacts: -詳しい情報については、「[ワークフローデータをアーティファクトとして保存する](/actions/guides/storing-workflow-data-as-artifacts)」を参照してください。 +詳しい情報については、「[ワークフローデータを成果物として保存する](/actions/guides/storing-workflow-data-as-artifacts)」を参照してください。 ### データベースとサービスコンテナ @@ -415,21 +420,21 @@ GitLab CI/CD container-job: variables: POSTGRES_PASSWORD: postgres - # The hostname used to communicate with the - # PostgreSQL service container + # PostgreSQLサービスコンテナと通信するために + # 使われるホスト名 POSTGRES_HOST: postgres - # The default PostgreSQL port + # PostgreSQLのデフォルトのポート POSTGRES_PORT: 5432 image: node:10.18-jessie services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # `package.json`ファイル中のすべての依存関係を + # クリーンインストールする + - npm ci + # PostgreSQLクライアントを作成し、クライアントにデータを + # 展開し、データを取り出すスクリプトを実行する + - node client.js tags: - docker ``` @@ -453,20 +458,20 @@ jobs: - name: Check out repository code uses: actions/checkout@v2 - # Performs a clean installation of all dependencies - # in the `package.json` file + # 「package.json」ファイル内のすべての依存関係の + # クリーンインストールを実行する - name: Install dependencies run: npm ci - name: Connect to PostgreSQL - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data + # PostgreSQL クライアントを作成してクライアントにデータを入力し + # データを取得するスクリプトを実行する run: node client.js env: - # The hostname used to communicate with the - # PostgreSQL service container + # PostgreSQL サービスコンテナとの通信に + # 使用されるホスト名 POSTGRES_HOST: postgres - # The default PostgreSQL port + # デフォルトの PostgreSQL ポート POSTGRES_PORT: 5432 ``` {% endraw %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index 579e597f2b..dd389e4db9 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Jenkins + - 移行 + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ Jenkinsでは、ビルドを単一のビルドエージェントに送信する 同様に、{% data variables.product.prodname_actions %} はジョブを {% data variables.product.prodname_dotcom %} ホストまたはセルフホストランナーに送信でき、ラベルを使用してさまざまな属性に従ってランナーを分類できます。 以下の表は、分散ビルドの概念がJenkinsと{% data variables.product.prodname_actions %}でどのように実装されているかを比較しています。 | Jenkins | {% data variables.product.prodname_actions %} -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`エージェント`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`ランナー`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`セルフホストランナー`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`エージェント`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### セクションを利用したパイプラインの整理 @@ -51,7 +56,6 @@ Jenkinsは、宣言的パイプラインを複数のセクションに分割し | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### ディレクティブの利用 Jenkinsは、_宣言的パイプライン_を管理するためにディレクティブを使います。 それらのディレクティブは、ワークフローの特徴と、その実行方法を定義します。 以下の表は、それらのディレクティブが{% data variables.product.prodname_actions %}の概念とどのように対応するかを示しています。 @@ -69,7 +73,6 @@ Jenkinsは、_宣言的パイプライン_を管理するためにディレク | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### シーケンシャルなステージの利用 #### 並列なジョブの処理 @@ -114,23 +117,23 @@ Jenkinsのパイプライン - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +``` @@ -150,25 +153,24 @@ Jenkinsのパイプライン - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +``` @@ -188,30 +190,28 @@ Jenkinsのパイプライン - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +``` @@ -231,26 +231,27 @@ Jenkinsのパイプライン - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - name: demo-workflow - on: - push: - jobs: - test: - runs-on: ${{ matrix.os }} - strategy: - fail-fast: false - matrix: - os: [macos-latest, ubuntu-latest] - steps: - - uses: actions/checkout@v1 - - uses: actions/setup-node@v1 - with: - node-version: 12 - - run: npm install -g bats - - run: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 6c2514f744..4986714ab9 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -1,58 +1,63 @@ --- -title: Migrating from Travis CI to GitHub Actions -intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.' +title: Travis CI から GitHub Actions への移行 +intro: '{% data variables.product.prodname_actions %} と Travis CI は複数の類似点を共有しているため、{% data variables.product.prodname_actions %} への移行は比較的簡単です。' redirect_from: - /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Travis CI + - 移行 + - CI + - CD --- ### はじめに -This guide helps you migrate from Travis CI to {% data variables.product.prodname_actions %}. It compares their concepts and syntax, describes the similarities, and demonstrates their different approaches to common tasks. +このガイドは、Travis CI から {% data variables.product.prodname_actions %} に移行するときに役立ちます。 概念と構文を比較して類似点を説明し、一般的なタスクに対するさまざまなアプローチを示します。 -### Before you start +### はじめる前に -Before starting your migration to {% data variables.product.prodname_actions %}, it would be useful to become familiar with how it works: +{% data variables.product.prodname_actions %} への移行を開始する前に、その仕組みを理解しておくと便利です。 -- For a quick example that demonstrates a {% data variables.product.prodname_actions %} job, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)." -- To learn the essential {% data variables.product.prodname_actions %} concepts, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)." +- {% data variables.product.prodname_actions %} ジョブを示す簡単な例については、「[{% data variables.product.prodname_actions %} のクイックスタート](/actions/quickstart)」を参照してください。 +- 本質的な {% data variables.product.prodname_actions %} の概念については、「[GitHub Actions の概要](/actions/learn-github-actions/introduction-to-github-actions)」を参照してください。 -### Comparing job execution +### ジョブ実行の比較 -To give you control over when CI tasks are executed, a {% data variables.product.prodname_actions %} _workflow_ uses _jobs_ that run in parallel by default. Each job contains _steps_ that are executed in a sequence that you define. If you need to run setup and cleanup actions for a job, you can define steps in each job to perform these. +CI タスクがいつ実行されるかを制御できるように、{% data variables.product.prodname_actions %} _ワークフロー_はデフォルトで並行して実行される_ジョブ_を使用します。 各ジョブには、定義した順序で実行される_ステップ_が含まれています。 ジョブのセットアップおよびクリーンアップアクションを実行する必要がある場合は、各ジョブでステップを定義してこれらを実行できます。 -### Key similarities +### 主な類似点 -{% data variables.product.prodname_actions %} and Travis CI share certain similarities, and understanding these ahead of time can help smooth the migration process. +{% data variables.product.prodname_actions %} と Travis CI は特定の類似点を共有しており、これらを事前に理解しておくと、移行プロセスを円滑に進めることができます。 -#### Using YAML syntax +#### YAML 構文の使用 -Travis CI and {% data variables.product.prodname_actions %} both use YAML to create jobs and workflows, and these files are stored in the code's repository. For more information on how {% data variables.product.prodname_actions %} uses YAML, see ["Creating a workflow file](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)." +Travis CI と {% data variables.product.prodname_actions %} はどちらも YAML を使用してジョブとワークフローを作成し、これらのファイルはコードのリポジトリに保存されます。 {% data variables.product.prodname_actions %} が YAML を使用する方法の詳細については、「[ワークフローファイルを作成する](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。 -#### Custom environment variables +#### カスタム環境変数 -Travis CI lets you set environment variables and share them between stages. Similarly, {% data variables.product.prodname_actions %} lets you define environment variables for a step, job, or workflow. For more information, see ["Environment variables](/actions/reference/environment-variables)." +Travis CI では環境変数を設定し、ステージ間で共有できます。 同様に、{% data variables.product.prodname_actions %} を使用すると、ステップ、ジョブ、またはワークフローの環境変数を定義できます。 詳しい情報については、「[環境変数](/actions/reference/environment-variables)」を参照してください。 #### デフォルトの環境変数 -Travis CI and {% data variables.product.prodname_actions %} both include default environment variables that you can use in your YAML files. For {% data variables.product.prodname_actions %}, you can see these listed in "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)." +Travis CI と {% data variables.product.prodname_actions %} の両方に、YAML ファイルで使用できるデフォルトの環境変数が含まれています。 {% data variables.product.prodname_actions %} の場合、これらは「[デフォルトの環境変数](/actions/reference/environment-variables#default-environment-variables)」にリストされています。 #### 並列なジョブの処理 -Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables.product.prodname_actions %} runs `jobs` in parallel. For more information, see "[Creating dependent jobs](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)." +Travis CI は、`stages` を使用してジョブを並行して実行できます。 同様に、{% data variables.product.prodname_actions %} は `jobs` を並行して実行します。 詳細については、「[依存ジョブを作成する](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)」を参照してください。 -#### Status badges +#### ステータスバッジ -Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing. For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." +Travis CI と {% data variables.product.prodname_actions %} はどちらもステータスバッジをサポートしており、ビルドが成功したか失敗したかを示すことができます。 詳しい情報については、「[リポジトリにワークフローステータスバッジを追加する](/actions/managing-workflow-runs/adding-a-workflow-status-badge)」を参照してください。 #### ビルドマトリックスを使用する -Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +Travis CI と {% data variables.product.prodname_actions %} はどちらもビルドマトリックスをサポートしているため、オペレーティングシステムとソフトウェアパッケージの組み合わせを使用してテストを実行できます。 詳しい情報については、「[ビルドマトリックスを使用する](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)」を参照してください。 -Below is an example comparing the syntax for each system: +以下は、各システムの構文を比較した例です。 @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -88,9 +93,9 @@ jobs:
    -#### Targeting specific branches +#### 特定のブランチをターゲットにする -Travis CI and {% data variables.product.prodname_actions %} both allow you to target your CI to a specific branch. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。 +Travis CI と {% data variables.product.prodname_actions %} はどちらも、CI を特定のブランチにターゲット設定できます。 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。 以下が、それぞれのシステムの構文の例です。 @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -128,9 +133,9 @@ on: -#### Checking out submodules +#### サブモジュールをチェックアウトする -Travis CI and {% data variables.product.prodname_actions %} both allow you to control whether submodules are included in the repository clone. +Travis CI と {% data variables.product.prodname_actions %} はどちらも、サブモジュールをリポジトリクローンに含めるかどうかの制御ができます。 以下が、それぞれのシステムの構文の例です。 @@ -155,44 +160,44 @@ git: {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %} -#### Using environment variables in a matrix +#### マトリックスで環境変数を使用する -Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. +Travis CI と {% data variables.product.prodname_actions %} はどちらも、カスタム環境変数をテストマトリックスに追加できます。これにより、後のステップで変数を参照できます。 -In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} +{% data variables.product.prodname_actions %} では、`include` キーを使用して、カスタム環境変数をマトリックスに追加できます。 {% data reusables.github-actions.matrix-variable-example %} -### Key features in {% data variables.product.prodname_actions %} +### {% data variables.product.prodname_actions %} の主な機能 -When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}: +Travis CI から移行する場合は、{% data variables.product.prodname_actions %} の次の主要機能を考慮してください。 #### シークレットを保存する -{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} organizations can limit which repositories can access organization secrets. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Environment protection rules can require manual approval for a workflow to access environment secrets. {% endif %}For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +{% data variables.product.prodname_actions %} を使用すると、シークレットを保存して、ジョブで参照できます。 {% data variables.product.prodname_actions %} Organization は、Organization のシークレットにアクセスできるリポジトリを制限できます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}環境保護ルールでは、ワークフローが環境シークレットにアクセスするための手動承認が必要になる場合があります。 {% endif %}詳しい情報については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。 -#### Sharing files between jobs and workflows +#### ジョブとワークフロー間でファイルを共有する -{% data variables.product.prodname_actions %} includes integrated support for artifact storage, allowing you to share files between jobs in a workflow. You can also save the resulting files and share them with other workflows. For more information, see "[Sharing data between jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)." +{% data variables.product.prodname_actions %} には、成果物のストレージの統合サポートが含まれており、ワークフロー内のジョブ間でファイルを共有できます。 結果のファイルを保存して、他のワークフローと共有することもできます。 詳しい情報については、「[ジョブ間でデータを共有する](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)」を参照してください。 #### 自分のランナーをホストする -If your jobs require specific hardware or software, {% data variables.product.prodname_actions %} allows you to host your own runners and send your jobs to them for processing. {% data variables.product.prodname_actions %} also lets you use policies to control how these runners are accessed, granting access at the organization or repository level. For more information, see ["Hosting your own runners](/actions/hosting-your-own-runners)." +ジョブに特定のハードウェアまたはソフトウェアが必要な場合、{% data variables.product.prodname_actions %} を使用すると、自分のランナーをホストして、処理のためにジョブをそれらに送信できます。 {% data variables.product.prodname_actions %} では、ポリシーを使用してこれらのランナーへのアクセス方法を制御し、Organization またはリポジトリレベルでアクセスを許可することもできます。 詳しい情報については、「[自分のランナーをホストする](/actions/hosting-your-own-runners)」を参照してください。 -#### Concurrent jobs and execution time +#### 同時ジョブと実行時間 -The concurrent jobs and workflow execution times in {% data variables.product.prodname_actions %} can vary depending on your {% data variables.product.company_short %} plan. 詳しい情報については、「[使用制限、支払い、および管理](/actions/reference/usage-limits-billing-and-administration)」を参照してください。 +{% data variables.product.prodname_actions %} の同時ジョブとワークフローの実行時間は、{% data variables.product.company_short %} プランによって異なります。 詳しい情報については、「[使用制限、支払い、および管理](/actions/reference/usage-limits-billing-and-administration)」を参照してください。 -#### Using different languages in {% data variables.product.prodname_actions %} +#### {% data variables.product.prodname_actions %} で様々な言語を使用する -When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide: +{% data variables.product.prodname_actions %} でさまざまな言語を使用する場合、ジョブにステップを作成して言語の依存関係を設定できます。 特定の言語での作業の詳細については、それぞれのガイドを参照してください。 - [Node.js のビルドとテスト](/actions/guides/building-and-testing-nodejs) - [PowerShell のビルドとテスト](/actions/guides/building-and-testing-powershell) - [Python のビルドとテスト](/actions/guides/building-and-testing-python) @@ -200,36 +205,36 @@ When working with different languages in {% data variables.product.prodname_acti - [GradleでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-gradle) - [AntでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-ant) -### Executing scripts +### スクリプトを実行する -{% data variables.product.prodname_actions %} can use `run` steps to run scripts or shell commands. To use a particular shell, you can specify the `shell` type when providing the path to the script. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)」を参照してください。 +{% data variables.product.prodname_actions %} は、`run` ステップを使用してスクリプトまたはシェルコマンドを実行できます。 特定のシェルを使用するには、スクリプトへのパスを指定するときに `shell` タイプを指定できます。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)」を参照してください。 例: ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` -### Error handling in {% data variables.product.prodname_actions %} +### {% data variables.product.prodname_actions %} でのエラー処理 -When migrating to {% data variables.product.prodname_actions %}, there are different approaches to error handling that you might need to be aware of. +{% data variables.product.prodname_actions %} に移行する場合、エラー処理にはさまざまな方法があり、注意が必要です。 -#### Script error handling +#### スクリプトエラーの処理 -{% data variables.product.prodname_actions %} stops a job immediately if one of the steps returns an error code. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)」を参照してください。 +{% data variables.product.prodname_actions %} は、いずれかのステップでエラーコードが返された場合、すぐにジョブを停止します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)」を参照してください。 -#### Job error handling +#### ジョブエラーの処理 -{% data variables.product.prodname_actions %} uses `if` conditionals to execute jobs or steps in certain situations. For example, you can run a step when another step results in a `failure()`. 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)」を参照してください。 You can also use [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) to prevent a workflow run from stopping when a job fails. +{% data variables.product.prodname_actions %} は、`if` 条件を使用して、特定の状況でジョブまたはステップを実行します。 たとえば、別のステップで `failure()` が発生したときに、そのステップを実行できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)」を参照してください。 また、[`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) を使用して、ジョブが失敗したときにワークフローの実行が停止しないようにすることもできます。 -### Migrating syntax for conditionals and expressions +### 条件文と式の構文を移行する -To run jobs under conditional expressions, Travis CI and {% data variables.product.prodname_actions %} share a similar `if` condition syntax. {% data variables.product.prodname_actions %} lets you use the `if` conditional to prevent a job or step from running unless a condition is met. 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 +条件式でジョブを実行するために、Travis CI と {% data variables.product.prodname_actions %} は同様の `if` 条件構文を共有します。 {% data variables.product.prodname_actions %} を使用すると、`if` 条件を使用して、条件が満たされない限りジョブまたはステップが実行されないようにすることができます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -This example demonstrates how an `if` conditional can control whether a step is executed: +次の例は、`if` 条件がステップを実行するかどうかを制御する方法を示しています。 ```yaml jobs: @@ -240,9 +245,9 @@ jobs: if: env.str == 'ABC' && env.num == 123 ``` -### Migrating phases to steps +### フェーズからステップに移行する -Where Travis CI uses _phases_ to run _steps_, {% data variables.product.prodname_actions %} has _steps_ which execute _actions_. You can find prebuilt actions in the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. 詳細については、「[アクションの構築について](/actions/building-actions)」を参照してください。 +Travis CI が_フェーズ_を使用して_ステップ_を実行する場合、{% data variables.product.prodname_actions %} には_アクション_を実行する_ステップ_があります。 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)でビルド済みのアクションを見つけることも、あるいは独自のアクションを作成することもできます。 詳細については、「[アクションの構築について](/actions/building-actions)」を参照してください。 以下が、それぞれのシステムの構文の例です。 @@ -275,11 +280,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} @@ -288,7 +293,7 @@ jobs: ### 依存関係のキャッシング -Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system. +Travis CIと{% data variables.product.prodname_actions %}では、後で利用できるよう依存関係を手動でキャッシュできます。 以下の例は、それぞれのシステムでのキャッシュの構文を示します。 @@ -323,15 +328,15 @@ cache: npm
    -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% data variables.product.prodname_actions %} キャッシングは、{% data variables.product.prodname_dotcom %} ホストランナーにのみ適用できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 ### 一般的なタスクの例 -This section compares how {% data variables.product.prodname_actions %} and Travis CI perform common tasks. +このセクションは、{% data variables.product.prodname_actions %}とTravis CIでの一般的なタスクの実行方法を比較します。 -#### Configuring environment variables +#### 環境変数の設定 -You can create custom environment variables in a {% data variables.product.prodname_actions %} job. 例: +{% data variables.product.prodname_actions %}のジョブではカスタムの環境変数を作成できます。 例: @@ -345,26 +350,26 @@ Travis CI
    - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +```
    -#### Building with Node.js +#### Node.jsでのビルド @@ -378,24 +383,24 @@ Travis CI @@ -412,4 +417,4 @@ jobs: ### 次のステップ -To continue learning about the main features of {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +{% data variables.product.prodname_actions %}の主な機能について学び続けるには、「[{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions)」を参照してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 8dde92c821..06bba3a522 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -1,14 +1,16 @@ --- title: GitHub Actions のセキュリティ強化 shortTitle: セキュリティ強化 -intro: '{% data variables.product.prodname_actions %} 機能を使用するための適切なセキュリティプラクティス。' +intro: '{% data variables.product.prodname_actions %} の機能を使用するための適切なセキュリティプラクティス。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/getting-started-with-github-actions/security-hardening-for-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - セキュリティ --- {% data reusables.actions.enterprise-beta %} @@ -16,18 +18,18 @@ type: 'overview' ### 概要 -このガイドでは、特定の {% data variables.product.prodname_actions %} 機能のセキュリティ強化を設定する方法について説明します。 {% data variables.product.prodname_actions %} の概念について理解を深めるには、「[GitHub Actions の中核的概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)」を参照してください。 +このガイドでは、特定の {% data variables.product.prodname_actions %} の機能のセキュリティ強化を設定する方法について説明します。 {% data variables.product.prodname_actions %} の概念について理解を深めるには、「[GitHub Actions の中核的概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)」を参照してください。 ### シークレットを使用する -機密性の高い値は、平文としてワークフローファイルに保存するのではなく、シークレットとして保存してください。 [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. +機密性の高い値は、平文としてワークフローファイルに保存するのではなく、シークレットとして保存してください。 [シークレット](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)は、Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、リポジトリ、あるいは環境{% else %}あるいはリポジトリ{% endif %}のレベルで設定でき、機密情報を{% data variables.product.product_name %}に保存できるようになります。 シークレットは [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) を使用するため、{% data variables.product.product_name %} に到達する前に暗号化されます。 これは、[UI を使用](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository)して、または [REST API](/rest/reference/actions#secrets) を介してシークレットが送信されたときに発生します。 このクライアント側の暗号化により、{% data variables.product.product_name %} のインフラストラクチャ内での偶発的なログ（例外ログやリクエストログなど）に関連するリスクを最小限に抑えることができます。 シークレットがアップロードされると、{% data variables.product.product_name %} はそれを復号化して、ワークフローランタイムに挿入できるようになります。 偶発的な開示を防ぐために、{% data variables.product.product_name %} は、実行ログに表示されるシークレットを編集しようとするメカニズムを使用しています。 この編集は、設定されたシークレットの完全一致、および Base64 などの値の一般的なエンコーディングを検索します。 ただし、シークレットの値を変換する方法は複数あるため、この編集は保証されません。 そのため、シークレットを確実に編集し、シークレットに関連する他のリスクを制限するために実行する必要がある、特定の予防的ステップと推奨事項は次のとおりです。 - **構造化データをシークレットとして使用しない** - - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. たとえば、JSON、XML、または YAML（または同様）の Blob を使用してシークレット値をカプセル化しないでください。シークレットが適切に編集される可能性が大幅に低下するためです。 代わりに、機密値ごとに個別のシークレットを作成します。 + - 構造化データは、ログ内のシークレットの編集失敗の原因となる可能性があります。これは、編集が特定のシークレット値の完全一致を見つけることに大きく依存しているためです。 たとえば、JSON、XML、または YAML（または同様）の Blob を使用してシークレット値をカプセル化しないでください。シークレットが適切に編集される可能性が大幅に低下するためです。 代わりに、機密値ごとに個別のシークレットを作成します。 - **ワークフロー内で使用されるすべてのシークレットを登録する** - シークレットを使用してワークフロー内で別の機密値を生成する場合は、生成された値を正式に[シークレットとして登録](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret)して、ログに表示されたときに編集されるようにする必要があります。 たとえば、秘密鍵を使用して署名済み JWT を生成し、Web API にアクセスする場合は、その JWT をシークレットとして登録してください。そうしない場合、ログ出力に入力されても編集されません。 - シークレットの登録は、あらゆる種類の変換/エンコーディングにも適用されます。 シークレットが何らかの方法で変換された場合（Base64 や URL エンコードなど）、新しい値もシークレットとして登録してください。 @@ -40,8 +42,8 @@ type: 'overview' - 登録されたシークレットを定期的に確認して、現在も必要であることを確認します。 不要になったものは削除してください。 - シークレットを定期的にローテーションして、不正使用されたシークレットが有効である期間を短縮します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -- **Consider requiring review for access to secrets** - - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." +- **シークレットへのアクセスのレビューを必須とすることを検討する** + - 必須のレビュー担当者を使って環境のシークレットを保護できます。 レビュー担当者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 緩急尾へのシークレットの保存、あるいは環境にレビュー担当者を必須とすることの詳細については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」及び「[環境](/actions/reference/environments)」を参照してください。 {% endif %} ### サードパーティアクションを使用する @@ -54,11 +56,13 @@ type: 'overview' 現在、アクションを不変のリリースとして使用する唯一の方法は、アクションを完全なコミット SHA にピン止めすることです。 特定の SHA にピン止めすると、有効な Git オブジェクトペイロードに対して SHA-1 衝突を生成する必要があるため、悪意のある人がアクションのリポジトリにバックドアを追加するリスクを軽減できます。 + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **警告:** コミット SHA の短いバージョンは安全ではないため、アクションの Git リファレンスの指定には使用しないでください。 リポジトリネットワークの仕組みにより、どのユーザもリポジトリをフォークし、短い SHA と衝突するよう細工されたコミットをプッシュできます。 これにより、その SHA の後続のクローンがあいまいなコミットになるため失敗します。 その結果、短縮された SHA を使用するワークフローはすぐに失敗します。 {% endwarning %} + {% endif %} * **アクションのソースコードを監査する** @@ -71,18 +75,18 @@ type: 'overview' ### リポジトリ間のアクセスを検討する -{% data variables.product.product_name %} は、意図的に一度に単一のリポジトリに対してスコープされます。 The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. +{% data variables.product.product_name %} は、意図的に一度に単一のリポジトリに対してスコープされます。 `GITHUB_TOKEN` は、書き込みアクセスユーザと同じレベルのアクセスを許可します。書き込みアクセスを持つユーザは、ワークフローファイルを作成または変更することによってこのトークンにアクセスできるためです。 ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 同様に、{% data variables.product.prodname_dotcom %} 認証トークンをワークフローに追加する場合は注意が必要です。これは、コラボレータに誤って広範なアクセスを付与することにより、{% data variables.product.prodname_dotcom %} アクセス許可モデルにも影響を与える可能性があるためです。 -[{% data variables.product.prodname_dotcom %} ロードマップ](https://github.com/github/roadmap/issues/74)では、{% data variables.product.product_name %} 内のリポジトリ間アクセスを可能にするフローをサポートする計画がありますが、この機能はまだサポートされていません。 Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. 多くの認証トークンタイプでは特定のリソースへの詳細なアクセスが許可されていないことから、意図したものよりはるかに広範なアクセスを許可できるため、間違ったトークンタイプを使用すると重大なリスクが生じます。 +[{% data variables.product.prodname_dotcom %} ロードマップ](https://github.com/github/roadmap/issues/74)では、{% data variables.product.product_name %} 内のリポジトリ間アクセスを可能にするフローをサポートする計画がありますが、この機能はまだサポートされていません。 現在、権限のあるリポジトリ間のやり取りを実行する唯一の方法は、ワークフロー内に {% data variables.product.prodname_dotcom %} 認証トークンまたは SSH キーをシークレットとして配置することです。 多くの認証トークンタイプでは特定のリソースへの詳細なアクセスが許可されていないことから、意図したものよりはるかに広範なアクセスを許可できるため、間違ったトークンタイプを使用すると重大なリスクが生じます。 次のリストでは、ワークフロー内のリポジトリデータにアクセスするための推奨アプローチを優先度の高い順に説明しています。 -1. **The `GITHUB_TOKEN`** +1. **`GITHUB_TOKEN`** - このトークンは、ワークフローを呼び出した単一のリポジトリに意図的にスコープが設定されており、リポジトリの書き込みアクセスユーザと同じレベルのアクセス権を持っています。 トークンは各ジョブが開始する前に作成され、ジョブが終了すると期限切れになります。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。 - 可能な場合は、常に `GITHUB_TOKEN` を使用する必要があります。 2. **リポジトリのデプロイキー** - デプロイキーは、単一のリポジトリへの読み取りまたは書き込みアクセスを許可する唯一の認証情報タイプの 1 つであり、ワークフロー内の別のリポジトリとのやり取りに使用できます。 詳しい情報については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys#deploy-keys)」を参照してください。 - - デプロイキーは Git を使用してリポジトリに複製およびプッシュできるだけであり、REST または GraphQL API とのやり取りには使用できないため、要件に適さない場合があることに注意してください。 + - デプロイキーは Git を使用してリポジトリにクローンおよびプッシュできるだけであり、REST または GraphQL API とのやり取りには使用できないため、要件に適さない場合があることに注意してください。 3. **{% data variables.product.prodname_github_app %} トークン** - {% data variables.product.prodname_github_apps %} は、選択したリポジトリにインストールでき、リポジトリ内のリソースに対する詳細な権限を持つこともできます。 Organization の内部で {% data variables.product.prodname_github_app %} を作成し、ワークフロー内でアクセスする必要があるリポジトリにインストールして、それらのリポジトリにアクセスするためのワークフロー内のインストールとして認証できます。 4. **個人アクセストークン** @@ -95,49 +99,49 @@ type: 'overview' **{% data variables.product.prodname_dotcom %} でホストされた**ランナーは、一過性でクリーンな隔離された仮想マシン内でコードを実行します。つまり、この環境を永続的に危険にさらしたり、ブートストラッププロセス中にこの環境に置かれた以上の情報にアクセスしたりする方法はありません。 -**{% data variables.product.product_name %} のセルフホスト**ランナーは、一過性でクリーンな仮想マシンでの実行に関する保証がなく、ワークフロー内の信頼されていないコードによって永続的に侵害される可能性があります。 +{% data variables.product.product_name %} の**セルフホスト**ランナーは、一過性でクリーンな仮想マシンでの実行に関する保証がなく、ワークフロー内の信頼されていないコードによって永続的に侵害される可能性があります。 -そのため、[{% data variables.product.product_name %} のパブリックリポジトリにセルフホストランナーを使用することはほとんどありません](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。これは、ユーザがリポジトリに対してプルリクエストを開き、環境を危険にさらす可能性があるためです。 同様に、プライベートリポジトリでセルフホストランナーを使用する場合は注意してください。リポジトリをフォークして PR を開くことができるユーザ（一般にリポジトリへの読み取りアクセス権を持つユーザ）は、シークレットへのアクセスと、リポジトリへの書き込みアクセス許可を付与する、より特権的な `GITHUB_TOKEN` を取得することを含め、セルフホストのランナー環境を危険にさらすことができるためです。 +そのため、{% data variables.product.product_name %} の[パブリックリポジトリにセルフホストランナーを使用することはほとんどありません](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。これは、任意のユーザがリポジトリに対してプルリクエストを開き、環境を危険にさらす可能性があるためです。 同様に、プライベートリポジトリでセルフホストランナーを使用する場合は注意してください。リポジトリをフォークして PR を開くことができるユーザ（一般にリポジトリへの読み取りアクセス権を持つユーザ）は、シークレットへのアクセスと、リポジトリへの書き込みアクセス許可を付与する、より特権的な `GITHUB_TOKEN` を取得することを含め、セルフホストのランナー環境を危険にさらすことができるためです。 -When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 +セルフホストランナーがOrganizationもしくはEnterpriseのレベルで定義されているなら、{% data variables.product.product_name %}は同じランナー上で複数のリポジトリからのワークフローをスケジューリングするかもしれません。 したがって、これらの環境へのセキュリティ侵害は、大きな影響をもたらす可能性があります。 侵害の範囲を狭めるために、セルフホストランナーを個別のグループにまとめることで、境界を作ることができます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 次のように、セルフホストランナーマシンの環境も考慮する必要があります。 - セルフホストランナーとして設定されたマシンにはどのような機密情報が存在するか。 たとえば、SSH 秘密鍵、API アクセストークンなどです。 - マシンが機密性の高いサービスにネットワークアクセス可能か。 たとえば、Azure または AWS メタデータサービスなどです。 この環境での機密情報量は最小限に抑える必要があります。ワークフローを呼び出すことができるすべてのユーザがこの環境にアクセスできることを常に意識しておいてください。 -Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. +中には、それぞれのジョブの実行後にセルフホストランナーを自動的に破棄するようなシステムを実装することで、このリスクを部分的に軽減しようとするお客様もいます。 しかし、このアプローチは意図したほどには効果的ではないかもしれません。これは、セルフホストランナーが1つのジョブだけを実行するという保証がないためです。 -### Auditing {% data variables.product.prodname_actions %} events +### {% data variables.product.prodname_actions %}イベントの監査 -You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which user account performed the action. +Organizationの管理タスクをモニタするために、監査ログを使用できます。 監査ログは、アクションの種類、実行された時刻、実行したユーザアカウントを記録します。 -For example, you can use the audit log to track the `action:org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) +たとえば、監査ログを使って`action:org.update_actions_secret`イベントを追跡できます。これは、Organizationのシークレットの変更を追跡します。 ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png) -The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." -#### Events for secret management -| アクション | 説明 | -| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `action:org.create_actions_secret` | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization). | -| `action:org.remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:org.update_actions_secret` | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret. | -| `action:repo.create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository). | -| `action:repo.remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:repo.update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret. | +#### シークレット管理のイベント +| アクション | 説明 | +| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action:org.create_actions_secret` | Organizationの管理者が[{% data variables.product.prodname_actions %}シークレットを作成](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)したときにトリガーされます。 | +| `action:org.remove_actions_secret` | Organizationの管理者が{% data variables.product.prodname_actions %}シークレットを削除したときにトリガーされます。 | +| `action:org.update_actions_secret` | Organizationの管理者が{% data variables.product.prodname_actions %}シークレットを更新したときにトリガーされます。 | +| `action:repo.create_actions_secret` | リポジトリ管理者が[{% data variables.product.prodname_actions %}シークレットを作成](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)したときにトリガーされます。 | +| `action:repo.remove_actions_secret` | リポジトリ管理者が{% data variables.product.prodname_actions %}シークレットを削除したときにトリガーされます。 | +| `action:repo.update_actions_secret` | リポジトリ管理者が{% data variables.product.prodname_actions %}シークレットを更新したときにトリガーされます。 | -#### Events for self-hosted runners -| アクション | 説明 | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | -| `action:org.remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | -| `action:repo.register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `action:repo.remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). | +#### セルフホストランナーのイベント +| アクション | 説明 | +| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action:org.register_self_hosted_runner` | Organizationのオーナーが[新しいセルフホストランナーを登録](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)したときにトリガーされます。 | +| `action:org.remove_self_hosted_runner` | Organizationのオーナーが[セルフホストランナーを削除](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)したときにトリガーされます。 | +| `action:repo.register_self_hosted_runner` | リポジトリ管理者が[新しいセルフホストランナーを登録](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)したときにトリガーされます。 | +| `action:repo.remove_self_hosted_runner` | リポジトリ管理者が[セルフホストランナーを削除](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)したときにトリガーされます。 | -#### Events for self-hosted runner groups -| アクション | 説明 | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.runner_group_created` | Triggered when an organization admin [creates a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization). | -| `action:org.runner_group_removed` | Triggered when an organization admin removes a self-hosted runner group. | -| `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | -| `action:org.runner_group_runners_added` | Triggered when an organization admin [adds 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). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +#### セルフホストランナーグループのイベント +| アクション | 説明 | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action:org.runner_group_created` | Organizationの管理者が[セルフホストランナーグループを作成](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)したときにトリガーされます。 | +| `action:org.runner_group_removed` | Organizationの管理者がセルフホストランナーグループを削除したときにトリガーされます。 | +| `action:org.runner_group_renamed` | Organizationの管理者がセルフホストランナーグループの名前を変更したときにトリガーされます。 | +| `action:org.runner_group_runners_added` | Organizationの管理者が[セルフホストランナーをグループに追加](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)したときにトリガーされます。 | +| `action:org.runner_group_runners_removed` | Organizationの管理者がセルフホストランナーをグループから削除したときにトリガーされます。 | diff --git a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 1658a8f155..fcbaa6efb0 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -15,7 +15,7 @@ type: 'how_to' ### 概要 -ワークフローやその他の {% data variables.product.prodname_actions %} 機能を Team と共有する必要がある場合は、{% data variables.product.prodname_dotcom %} Organization 内でのコラボレーションを検討します。 An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. `.github` リポジトリにワークフローテンプレートを作成して、Organization 内の他のユーザと共有することもできます。 +ワークフローやその他の {% data variables.product.prodname_actions %} 機能を Team と共有する必要がある場合は、{% data variables.product.prodname_dotcom %} Organization 内でのコラボレーションを検討します。 Organization を使用すると、シークレット、成果物、およびセルフホストランナーを一元的に保存および管理できます。 `.github` リポジトリにワークフローテンプレートを作成して、Organization 内の他のユーザと共有することもできます。 ### ワークフロー テンプレートの作成 @@ -76,7 +76,7 @@ type: 'how_to' ![ワークフロー テンプレート ファイル](/assets/images/help/images/workflow-template-files.png) -### Using a workflow template from your organization +### Organization のワークフローテンプレートを使用する この手順では、Organizationのメンバーがワークフロー テンプレートを検索して利用し、新しいワークフローを作成する方法を示します。 Organizationのワークフロー テンプレートは、Organizationのメンバーであるすべてのユーザーが使用できます。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index b2673969ba..91c63700ad 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///workflows//badge.svg このMarkdownの例では、"Greet Everyone" という名前のワークフローにステータス バッジを追加します。 リポジトリの `OWNER` は、`actions`というOrganizationであり、 `REPOSITORY`の名前は`hello-world`です。 -``` +```markdown ![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ https://github.com///workflows//badge.svg この Markdown の例では、`.github/workflow/main.yml`というファイル パスのワークフローにステータス バッジを追加します 。 リポジトリの `OWNER` は、`actions`というOrganizationであり、 `REPOSITORY`の名前は`hello-world`です。 -``` +```markdown ![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ https://github.com///workflows//badge.svg この Markdown の例では、`feature-1`という名前のブランチにステータス バッジを追加します。 -``` +```markdown ![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ https://github.com///workflows//badge.svg この Markdown の例では、 `pull_request` イベントによってトリガーされたワークフロー実行のステータスを示すバッジを追加します。 -``` +```markdown ![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md index ae5c7d834a..2430753361 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,8 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel. ![ワークフローの実行の名前](/assets/images/help/repository/in-progress-run.png) -1. ワークフローの右上隅にある [**ワークフローのキャンセル**] をクリックします。 +1. ワークフローの実行のリストから、キャンセルしたい`queued`もしくは`in progress`の実行の名前をクリックしてください。 ![ワークフローの実行の名前](/assets/images/help/repository/in-progress-run.png) +1. ワークフローの右上隅にある [**Cancel workflow（ワークフローのキャンセル）**] をクリックします。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![[Cancel check suite] ボタン](/assets/images/help/repository/cancel-check-suite-updated.png) {% else %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index 8ee66f870f..43fb1fa54a 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -10,12 +10,12 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。 REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しい情報については、「[アクション REST API](/rest/reference/actions#workflows)」を参照してください。 +ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。 REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しい情報については、「[Actions REST API](/rest/reference/actions#workflows)」を参照してください。 -ワークフローを一時的に無効にすると、多くのシナリオで便利です。 以下は、ワークフローを無効すると便利な場合の例の一部です。 +ワークフローを一時的に無効にすると、多くのシナリオで役立つことがあります。 以下は、ワークフローを無効すると便利な場合の例の一部です。 - リクエストが多すぎるまたは間違っていて、外部サービスに悪影響を与えるワークフローエラー。 -- 重要ではないが、アカウントで時間がかかりすぎるワークフロー。 +- 重要ではないが、アカウントの時間を消費しすぎるワークフロー。 - ダウンしているサービスにリクエストを送信するワークフロー。 - フォークされたリポジトリ上の不要なワークフロー（スケジュールされたワークフローなど）。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index ffd2da0704..210489caa9 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -1,6 +1,6 @@ --- -title: ワークフロー アーティファクトをダウンロードする -intro: アーカイブされたアーティファクトは、自動的に有効期限切れになる前にダウンロードできます。 +title: ワークフローの成果物をダウンロードする +intro: アーカイブされた成果物は、自動的に有効期限切れになる前にダウンロードできます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -10,8 +10,8 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}デフォルトでは、{% data variables.product.product_name %} はビルドログとアーティファクトを 90 日間保存します。リポジトリのタイプに応じて、この保持期間をカスタマイズできます。 詳しい情報については、「[リポジトリ内の GitHub Actions アーティファクトとログの保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)」を参照してください。{% endif %} -{% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} には、完全なビルドログとアーティファクトが 90 日間保存されます。{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}デフォルトでは、{% data variables.product.product_name %} はビルドログと成果物を 90 日間保存します。リポジトリのタイプに応じて、この保持期間をカスタマイズできます。 詳しい情報については、「[リポジトリ内の GitHub Actionsの成果物とログの保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)」を参照してください。{% endif %} +{% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} には、完全なビルドログと成果物が 90 日間保存されます。{% endif %} {% data reusables.repositories.permissions-statement-read %} @@ -19,7 +19,7 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. [**Artifacts**] の下で、ダウンロードするアーティファクトをクリックします。 +1. [**Artifacts**] の下で、ダウンロードする成果物をクリックします。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png) {% else %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/index.md b/translations/ja-JP/content/actions/managing-workflow-runs/index.md index 3d33423233..fe48e7f6c2 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/index.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/index.md @@ -1,7 +1,7 @@ --- title: ワークフロー実行を管理する shortTitle: ワークフロー実行を管理する -intro: 'You can view the status and results of each step in your workflow, cancel a pending workflow, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}review deployments, {% endif %}view billable job execution minutes, debug and re-run a failed workflow, search and download logs, and download artifacts.' +intro: 'ワークフロー中の各ステップのステータスと結果を見たり、保留中のワークフローをキャンセルしたり、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}デプロイメントをレビューしたり、{% endif %}支払い可能なジョブの実行分を見たり、失敗したワークフローをデバッグして再実行したり、ログを検索してダウンロードしたり、成果物をダウンロードしたりすることができます。' redirect_from: - /actions/configuring-and-managing-workflows/managing-a-workflow-run - /articles/viewing-your-repository-s-workflows diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md index c801bd2fac..83f56b52b0 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -10,15 +10,15 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Configuring a workflow to run manually +### ワークフローを手動実行する設定 -ワークフローを手動で実行するには、`workflow_dispatch` イベントで実行するようにワークフローを設定する必要があります。 For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". +ワークフローを手動で実行するには、`workflow_dispatch` イベントで実行するようにワークフローを設定する必要があります。 `workflow_dispatch`イベントの設定に関する詳しい情報については「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。 ### {% data variables.product.prodname_dotcom %} でワークフローを実行する {% data variables.product.prodname_dotcom %} で `workflow_dispatch` イベントをトリガーするには、ワークフローがデフォルトブランチに含まれている必要があります。 ワークフローの実行を手動でトリガーするには、次の手順に従います。 -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md index a300a7ea8d..6f6fbaceab 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} +1. ワークフローの右上部から、**Re-run jobs（ジョブの再実行）**ドロップダウンメニューを使い、**Re-run all jobs（すべてのジョブを再実行）**を選択してください。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 2a676da7e7..b27660d73f 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -1,6 +1,6 @@ --- -title: ワークフロー アーティファクトを削除する -intro: '{% data variables.product.product_name %} で期限切れになる前にアーティファクトを削除することで、使用済みの {% data variables.product.prodname_actions %} ストレージを再利用できます。' +title: ワークフローの成果物を削除する +intro: '{% data variables.product.product_name %} で期限切れになる前に成果物を削除することで、使用済みの {% data variables.product.prodname_actions %} ストレージを再利用できます。' product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -10,7 +10,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### アーティファクトを削除する +### 成果物を削除する {% warning %} @@ -26,22 +26,21 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click -{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} - ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact-updated.png) +1. **Artifacts（成果物）**の下で、 +削除したい成果物の隣の{% octicon "trashcan" aria-label="The trashcan icon" %}をクリックしてください。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact-updated.png) {% else %} ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact.png) {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### アーティファクトの保持期間を設定する +### 成果物の保持期間を設定する -アーティファクトとログの保持期間は、リポジトリ、Organization、および Enterprise レベルで設定できます。 詳しい情報については、「[使用制限、支払い、および管理](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)」を参照してください。 +成果物とログの保持期間は、リポジトリ、Organization、および Enterprise レベルで設定できます。 詳しい情報については、「[使用制限、支払い、および管理](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)」を参照してください。 -ワークフローの `actions/upload-artifact` アクションを使用して、個々のアーティファクトのカスタム保持期間を定義することもできます。 詳しい情報については、「[ワークフローデータをアーティファクトとして保存する](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)」を参照してください。 +ワークフローの `actions/upload-artifact` アクションを使用して、個々の成果物にカスタムの保持期間を定義することもできます。 詳しい情報については、「[ワークフローデータを成果物として保存する](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)」を参照してください。 -### アーティファクトの有効期限を探す +### 成果物の有効期限を探す -API を使用して、アーティファクトの削除がスケジュールされている日付を確認できます。 詳しい情報については、「[リポジトリのアーティファクトの一覧表示](/rest/reference/actions#artifacts)」によって返される `expires_at` 値を参照してください。 +API を使用して、成果物の削除がスケジュールされている日付を確認できます。 詳しい情報については、「[リポジトリの成果物の一覧表示](/rest/reference/actions#artifacts)」によって返される `expires_at` 値を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md index cbeb7fe2ce..1f7cdfdd2b 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -1,6 +1,6 @@ --- -title: Reviewing deployments -intro: You can approve or reject jobs awaiting review. +title: デプロイメントのレビュー +intro: レビュー待ちのジョブを承認もしくは拒否できます。 product: '{% data reusables.gated-features.environments %}' versions: free-pro-team: '*' @@ -9,17 +9,17 @@ versions: {% data reusables.actions.environments-beta %} -### About required reviews in workflows +### ワークフローで必須のレビューについて -Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled. +必須のレビュー担当者が設定された環境を参照するジョブは、開始前に承認を待ちます。 承認を待っている間のジョブは、ステータスが"Waiting"になります。 ジョブが30日以内に承認されなければ、そのワークフローは自動的にキャンセルされます。 -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)." +環境と必須の承認に関する詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 -### Approving or rejecting a job +### ジョブの承認もしくは拒否 -1. Navigate to the workflow run that requires review. For more information about navigating to a workflow run, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -2. Click **Review deployments**. ![Review deployments](/assets/images/actions-review-deployments.png) -3. Select the job environment(s) to approve or reject. Optionally, leave a comment. ![Approve deployments](/assets/images/actions-approve-deployments.png) -4. Approve or reject: - - To approve the job, click **Approve and deploy**. Once a job is approved (and any other environment protection rules have passed), the job will proceed. At this point, the job can access any secrets stored in the environment. - - To reject the job, click **Reject**. If a job is rejected, the workflow will fail. +1. レビューを必要とするワークフローの実行へ移動してください。 ワークフローの実行への移動に関する詳しい情報については「[ワークフロー実行の履歴の表示](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 +2. **Review deployments（デプロイメントのレビュー）**をクリックしてください。 ![デプロイメントのレビュー](/assets/images/actions-review-deployments.png) +3. 承認もしくは拒否するジョブ環境を選択してください。 コメントを残すこともできます。 ![デプロイメントの承認](/assets/images/actions-approve-deployments.png) +4. 承認もしくは拒否してください。 + - ジョブを承認するには、**Approve and deploy（承認してデプロイ）**をクリックしてください。 ジョブが承認されると（そして他の環境保護ルールをパスすれば）、ジョブは進行します。 この時点で、ジョブは環境に保存されている任意のシークレットにアクセスできます。 + - ジョブを拒否するには、**Reject（拒否）**をクリックしてください。 ジョブが拒否されると、ワークフローは失敗します。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md index f1ef803e42..109367cc61 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -1,6 +1,6 @@ --- -title: Using the visualization graph -intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. +title: 視覚化グラフの利用 +intro: すべてのワークフローの実行は、実行の進行を示すリアルタイムのグラフを生成します。 このグラフを使って、ワークフローをモニタリング及びデバッグできます。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -16,6 +16,6 @@ versions: {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies. ![Workflow graph](/assets/images/help/images/workflow-graph.png) +1. このグラフは、ワークフロー中の各ジョブを表示します。 ジョブ名の左のアイコンは、ジョブのステータスを表示します。 ジョブ間の線は、依存関係を示します。 ![ワークフローグラフ](/assets/images/help/images/workflow-graph.png) -2. Click on a job to view the job log. ![Workflow graph](/assets/images/help/images/workflow-graph-job.png) +2. ジョブをクリックすると、そのジョブのログが表示されます。 ![ワークフローグラフ](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 7b71a4727f..d67530cfc6 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -14,7 +14,7 @@ versions: 実行が完了している場合には、結果が成功か失敗か、キャンセルされたか、またはニュートラルかを確認できます。 実行が失敗した場合には、ビルドログを表示して検索し、失敗の原因を診断してワークフローを再実行することもできます。 また、課金対象のジョブ実行時間を表示したり、ログやビルドの成果物をダウンロードすることもできます。 -{% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 For more information about the Checks API, see "[Checks](/rest/reference/checks)." +{% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 Checks APIに関する詳しい情報については「[チェック](/rest/reference/checks)」を参照してください。 {% data reusables.github-actions.invalid-workflow-files %} @@ -66,7 +66,7 @@ versions: {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. 右上隅にある -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %}をクリックし、**Download log archive（ログアーカイブをダウンロード）**を選択してください。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![[Download logs] ドロップダウンメニュー](/assets/images/help/repository/download-logs-drop-down-updated-2.png) {% else %} @@ -88,19 +88,18 @@ versions: {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. 右上隅にある -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} - ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックしてください。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) {% else %} ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) {% endif %} 2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} - ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png) + ![すべてのログを削除](/assets/images/help/repository/delete-all-logs-updated-2.png) {% else %} - ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) + ![すべてのログを削除](/assets/images/help/repository/delete-all-logs-updated.png) {% endif %} -After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. +ログを削除すると、**Delete all logs（すべてのログを削除）**ボタンは消え、ワークフローの実行にログファイルが残っていないことを示します。 {% else %} 1. 右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。 ![Delete all logs](/assets/images/help/repository/delete-all-logs.png)ログが削除されると、[**Delete all logs**] ボタンが削除され、ワークフローの実行にログファイルが残っていないことを示します。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md index 4ff2a9fcf9..112d3d12ed 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. ジョブの概要の下で、ジョブの実行時間を表示できます。 To view details about the billable job execution time, click the time under **Billable time**. ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png) +1. ジョブの概要の下で、ジョブの実行時間を表示できます。 請求可能なジョブの実行時間に関する詳細を表示するには、**Billable time（請求可能な時間）**の下の時間をクリックしてください。 ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md index 7e2529c423..04cfab5bb3 100644 --- a/translations/ja-JP/content/actions/quickstart.md +++ b/translations/ja-JP/content/actions/quickstart.md @@ -7,6 +7,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} @@ -14,7 +17,7 @@ versions: ### はじめに -{% data variables.product.prodname_actions %} ワークフローを作成して実行するには、既存の {% data variables.product.prodname_dotcom %} リポジトリのみが必要です。 このガイドでは、[{% data variables.product.prodname_dotcom %}Super-Linter アクション](https://github.com/github/super-linter)を使用して複数のコーディング言語の文法チェックを行うワークフローを追加します。 ワークフローは Super-Linter を使用して、新しいコミットがリポジトリにプッシュされるたびにソースコードを検証します。 +{% data variables.product.prodname_actions %} ワークフローを作成して実行するには、既存の {% data variables.product.prodname_dotcom %} リポジトリのみが必要です。 このガイドでは、[{% data variables.product.prodname_dotcom %} Super-Linter アクション](https://github.com/github/super-linter)を使用して複数のコーディング言語の文法チェックを行うワークフローを追加します。 ワークフローは Super-Linter を使用して、新しいコミットがリポジトリにプッシュされるたびにソースコードを検証します。 ### 最初のワークフローを作成する @@ -49,7 +52,7 @@ versions: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` {% endraw %} -3. ワークフローを実行するには、ページの一番下までスクロールし、[**Create a new branch for this commit and start a pull request**] を選択します。 次に、[**Propose new file**] をクリックしてプルリクエストを作成します。 ![ワークフローファイルのコミット](/assets/images/commit-workflow-file.png) +3. ワークフローを実行するには、ページの一番下までスクロールし、[**Create a new branch for this commit and start a pull request**] を選択します。 次に、[**Propose new file**] をクリックしてPull Requestを作成します。 ![ワークフローファイルのコミット](/assets/images/commit-workflow-file.png) リポジトリ内のワークフローファイルをコミットすると、`push` イベントがトリガーされ、ワークフローが実行されます。 @@ -60,13 +63,13 @@ versions: {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -1. Under **Jobs** or in the visualization graph, click the **Lint code base** job. ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +1. **Jobs（ジョブ）**の下、もしくは可視化グラフ内で、**Lint code base**ジョブをクリックしてください。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) {% else %} 1. 左サイドバーで、[**Lint code base**] をクリックします。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### More workflow templates +### さらなるワークフローテンプレート {% data reusables.actions.workflow-template-overview %} @@ -80,66 +83,66 @@ versions: diff --git a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md index cbf0c6b388..a6c424ba31 100644 --- a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md @@ -18,7 +18,7 @@ versions: {% data variables.product.prodname_dotcom %}は、ワークフローで利用する`GITHUB_TOKEN`シークレットを自動的に生成します。 この`GITHUB_TOKEN`は、ワークフローの実行内での認証に利用できます。 -{% data variables.product.prodname_actions %}を有効化すると、{% data variables.product.prodname_dotcom %}はリポジトリに{% data variables.product.prodname_github_app %}をインストールします。 `GITHUB_TOKEN`シークレットは、{% data variables.product.prodname_github_app %}インストールアクセストークンです。 このインストールアクセストークンは、リポジトリにインストールされた{% data variables.product.prodname_github_app %}の代わりに認証を受けるために利用できます このトークンの権限は、ワークフローを含むリポジトリに限定されます。 詳しい情報については「[`GITHUB_TOKEN`の権限](#permissions-for-the-github_token)」を参照してください。 +{% data variables.product.prodname_actions %}を有効化すると、{% data variables.product.prodname_dotcom %}はリポジトリに{% data variables.product.prodname_github_app %}をインストールします。 `GITHUB_TOKEN`シークレットは、{% data variables.product.prodname_github_app %}インストールアクセストークンです。 このインストールアクセストークンは、リポジトリにインストールされた{% data variables.product.prodname_github_app %}の代わりに認証を受けるために利用できます。 このトークンの権限は、ワークフローを含むリポジトリに限定されます。 詳しい情報については「[`GITHUB_TOKEN`の権限](#permissions-for-the-github_token)」を参照してください。 各ジョブの開始前に、{% data variables.product.prodname_dotcom %} はジョブのインストールアクセストークンをフェッチします。 トークンはジョブが終了すると期限切れになります。 @@ -77,7 +77,7 @@ versions: ### `GITHUB_TOKEN`の権限 -{% data variables.product.prodname_github_apps %} が各権限でアクセできる API エンドポイントについては、「[{% data variables.product.prodname_github_app %} の権限](/rest/reference/permissions-required-for-github-apps)」を参照してください。 +{% data variables.product.prodname_github_apps %} が各権限でアクセスできる API エンドポイントについては、「[{% data variables.product.prodname_github_app %} の権限](/rest/reference/permissions-required-for-github-apps)」を参照してください。 | 権限 | アクセスタイプ | フォークしたリポジトリからのアクセス | | ------------------- | --------- | ------------------ | @@ -86,8 +86,8 @@ versions: | contents | 読み取り/書き込み | 読み取り | | deployments | 読み取り/書き込み | 読み取り | | issues | 読み取り/書き込み | 読み取り | -| メタデータ | 読み取り | 読み取り | -| パッケージ | 読み取り/書き込み | 読み取り | +| metadata | 読み取り | 読み取り | +| packages | 読み取り/書き込み | 読み取り | | pull requests | 読み取り/書き込み | 読み取り | | repository projects | 読み取り/書き込み | 読み取り | | statuses | 読み取り/書き込み | 読み取り | diff --git a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md index bb4c7d215d..75a98f7ded 100644 --- a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -61,10 +61,10 @@ env: | `env` | `オブジェクト` | ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 詳しい情報については[`env`コンテキスト](#env-context)を参照してください。 | | `job` | `オブジェクト` | 現在実行中のジョブに関する情報。 詳しい情報については、「[`job` コンテキスト](#job-context)」を参照してください。 | | `steps` | `オブジェクト` | このジョブで実行されているステップに関する情報。 詳しい情報については、「[`steps` コンテキスト](#steps-context)」を参照してください。 | -| `runner` | `オブジェクト` | 現在のジョブを実行している runner に関する情報。 詳しい情報については[`runner`コンテキスト](#runner-context)を参照してください。 | +| `runner` | `オブジェクト` | 現在のジョブを実行しているランナーに関する情報。 詳しい情報については[`runner`コンテキスト](#runner-context)を参照してください。 | | `secrets` | `オブジェクト` | シークレットへのアクセスを有効にします。 シークレットに関する詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 | | `strategy` | `オブジェクト` | 現在のジョブに関して設定されたstrategyパラメータおよび情報にアクセスできます。 strategyパラメータには、`fail-fast`、`job-index`、`job-total`、`max-parallel`があります。 | -| `matrix` | `オブジェクト` | 現在のジョブに対して決定したmatrixパラメータにアクセスできます。 例えば、`os`および`node` バージョンでmatrixビルドを設定した場合、`matrix`コンテキストオブジェクトには現在のジョブの`os`および`node`バージョンが含まれます。 | +| `matrix` | `オブジェクト` | 現在のジョブに対して決定したmatrixパラメータにアクセスできます。 例えば、`os`および`node` バージョンでマトリックスビルドを設定した場合、`matrix`コンテキストオブジェクトには現在のジョブの`os`および`node`バージョンが含まれます。 | | `needs` | `オブジェクト` | 現在のジョブの依存関係として定義されたすべてのジョブの出力へのアクセスを可能にします。 詳しい情報については[`needs`コンテキスト](#needs-context)を参照してください。 | 式の一部として、次の 2 つの構文のうちいずれかを使用してコンテキストにアクセスすることができます。 @@ -75,7 +75,7 @@ env: - `a-Z` または `_` で始まる。 - `a-Z` 、`0-9`、 `-`、または`_`が続く。 -#### Determining when to use contexts +#### コンテキストを使用する場合の判断 {% data reusables.github-actions.using-context-or-environment-variables %} @@ -85,33 +85,33 @@ env: {% data reusables.github-actions.github-context-warning %} -| プロパティ名 | 種類 | 説明 | -| ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `オブジェクト` | ワークフローのあらゆるジョブやステップにおいて使用できる最上位のコンテキスト。 | -| `github.action` | `string` | 現在実行中のアクションの名前。 {% data variables.product.prodname_dotcom %}は、現在のステップがステップを実行する際に、特殊なキャラクターを削除するか、`run`という名前を使います。 同じジョブの中で同じアクションを複数回使う場合、名前には順番に番号が加えられます。 たとえば、実行する最初のスクリプトの名前は`run1`で、2番目のスクリプトの名前は`run2`というようになります。 同様に、`actions/checkout`の2回目の呼び出しは`actionscheckout2`となります。 | -| `github.action_path` | `string` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルに簡単にアクセスできます。 この属性は、複合実行ステップアクションでのみサポートされています。 | -| `github.actor` | `string` | ワークフローの実行を開始したユーザのログイン。 | -| `github.base_ref` | `string` | ワークフローの実行における `base_ref` またはプルリクエストのターゲットブランチ。 このプロパティは、ワークフローの実行をトリガーしたイベントが `pull_request` の場合のみ使用できます。 | -| `github.event` | `オブジェクト` | webhook ペイロードの完全なイベント。 詳しい情報については、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows/)」を参照してください。 このコンテキストを使用して、イベントの個々のプロパティにアクセスできます。 | -| `github.event_name` | `string` | ワークフローの実行をトリガーしたイベントの名前。 | -| `github.event_path` | `string` | ランナー上の完全なイベントwebhookペイロードへのパス。 | -| `github.head_ref` | `string` | ワークフローの実行における `head_ref` またはプルリクエストのソースブランチ。 このプロパティは、ワークフローの実行をトリガーしたイベントが `pull_request` の場合のみ使用できます。 | -| `github.job` | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | -| `github.ref` | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 ブランチの場合、これは `refs/heads/` の形式で、タグの場合は `refs/tags/` です。 | -| `github.repository` | `string` | 所有者およびリポジトリの名前。 `Codertocat/Hello-World`などです。 | -| `github.repository_owner` | `string` | リポジトリのオーナーの名前。 たとえば`Codertocat`。 | +| プロパティ名 | 種類 | 説明 | +| ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `github` | `オブジェクト` | ワークフローのあらゆるジョブやステップにおいて使用できる最上位のコンテキスト。 | +| `github.action` | `string` | 現在実行中のアクションの名前。 {% data variables.product.prodname_dotcom %}は、現在のステップがスクリプトを実行する際に、特殊なキャラクターを削除するか、`run`という名前を使います。 同じジョブの中で同じアクションを複数回使う場合、名前には順番に番号が加えられます。 たとえば、実行する最初のスクリプトの名前は`run1`で、2番目のスクリプトの名前は`run2`というようになります。 同様に、`actions/checkout`の2回目の呼び出しは`actionscheckout2`となります。 | +| `github.action_path` | `string` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルに簡単にアクセスできます。 この属性は、複合実行ステップアクションでのみサポートされています。 | +| `github.actor` | `string` | ワークフローの実行を開始したユーザのログイン。 | +| `github.base_ref` | `string` | ワークフローの実行における `base_ref` またはPull Requestのターゲットブランチ。 このプロパティは、ワークフローの実行をトリガーしたイベントが `pull_request` の場合のみ使用できます。 | +| `github.event` | `オブジェクト` | webhook ペイロードの完全なイベント。 詳しい情報については、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows/)」を参照してください。 このコンテキストを使用して、イベントの個々のプロパティにアクセスできます。 | +| `github.event_name` | `string` | ワークフローの実行をトリガーしたイベントの名前。 | +| `github.event_path` | `string` | ランナー上の完全なイベントwebhookペイロードへのパス。 | +| `github.head_ref` | `string` | ワークフローの実行における `head_ref` またはPull Requestのソースブランチ。 このプロパティは、ワークフローの実行をトリガーしたイベントが `pull_request` の場合のみ使用できます。 | +| `github.job` | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | +| `github.ref` | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 ブランチの場合、これは `refs/heads/` の形式で、タグの場合は `refs/tags/` です。 | +| `github.repository` | `string` | 所有者およびリポジトリの名前。 `Codertocat/Hello-World`などです。 | +| `github.repository_owner` | `string` | リポジトリのオーナーの名前。 たとえば`Codertocat`。 | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `string` | ワークフローの実行をトリガーしたコミット SHA。 | -| `github.token` | `string` | リポジトリにインストールされたGitHub Appの代わりに認証するためのトークン。 これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。 | -| `github.workflow` | `string` | ワークフローの名前。 ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | -| `github.workspace` | `string` | [`checkout`](https://github.com/actions/checkout)アクションを使う際の、ステップにとってのデフォルトのワーキングディレクトリであり、リポジトリのデフォルトの場所です。 | +| `github.sha` | `string` | ワークフローの実行をトリガーしたコミット SHA。 | +| `github.token` | `string` | リポジトリにインストールされたGitHub Appの代わりに認証するためのトークン。 これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。 | +| `github.workflow` | `string` | ワークフローの名前。 ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | +| `github.workspace` | `string` | [`checkout`](https://github.com/actions/checkout)アクションを使う際の、ステップにとってのデフォルトのワーキングディレクトリであり、リポジトリのデフォルトの場所です。 | #### `env`コンテキスト `env`コンテキストには、ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 ワークフローでの環境変数の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)」を参照してください。 -`env`の構文で、ワークフローファイル中の環境変数の値を利用できます。 You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. ステップの構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)」を参照してください。 +`env`の構文で、ワークフローファイル中の環境変数の値を利用できます。 `id`及び`uses`キーを除く、**step**中の任意のキーの値で`env`コンテキストを利用できます。 ステップの構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)」を参照してください。 ランナー中で環境変数の値を使いたい場合は、ランナーのオペレーティングシステムで環境変数を読み取る通常の方法を使ってください。 @@ -126,13 +126,13 @@ env: | プロパティ名 | 種類 | 説明 | | ----------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ジョブ` | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。 | +| `job` | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。 | | `job.container` | `オブジェクト` | ジョブのコンテナに関する情報。 コンテナに関する詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。 | | `job.container.id` | `string` | コンテナの ID。 | | `job.container.network` | `string` | コンテナネットワークの ID。 runner は、コンテナ内のすべてのジョブに使用されるネットワークを作成します。 | | `job.services` | `オブジェクト` | ジョブのために作成されたサービスコンテナ。 サービスコンテナに関する詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)」を参照してください。 | | `job.services..id` | `string` | サービスコンテナの ID。 | -| `job.services..network` | `string` | サービスコンテナネットワークの ID。 runner は、コンテナ内のすべてのジョブに使用されるネットワークを作成します。 | +| `job.services..network` | `string` | サービスコンテナネットワークの ID。 ランナーは、コンテナ内のすべてのジョブに使用されるネットワークを作成します。 | | `job.services..ports` | `オブジェクト` | サービスコンテナの公開ポート。 | | `job.status` | `string` | ジョブの現在の状態。 `success`、`failure`、`cancelled` のいずれかの値をとります。 | @@ -171,7 +171,7 @@ env: #### コンテキスト情報をログに出力するサンプル -各コンテキストでアクセスできる情報を調べるには、次の例のようにワークフローファイルを使用します。 +各コンテキストでアクセスできる情報を調べるには、次のワークフローファイルの例が利用できます。 {% data reusables.github-actions.github-context-warning %} @@ -186,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -320,7 +320,7 @@ env: `format( string, replaceValue0, replaceValue1, ..., replaceValueN)` -`string` の値を、変数 `replaceValueN` で置換します。 `string` の変数は、`{N}` という構文で指定します。ここで `N` は整数です。 少なくとも、`replaceValue` と `string` を 1 つ指定する必要があります。 使用できる変数 (`replaceValueN`) の数に制限はありません。 中括弧はダブルスペースでエスケープします。 +`string` の値を、変数 `replaceValueN` で置換します。 `string` の変数は、`{N}` という構文で指定します。ここで `N` は整数です。 少なくとも、`replaceValue` と `string` を 1 つ指定する必要があります。 使用できる変数 (`replaceValueN`) の数に制限はありません。 中括弧はダブルブレースでエスケープします。 ##### サンプル @@ -348,7 +348,7 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') `join(github.event.issue.labels.*.name, ', ')`は'bug, help wanted'といった結果を返します。 -#### toJson +#### toJSON `toJSON(value)` @@ -358,13 +358,13 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') `toJSON(job)` は、`{ "status": "Success" }` を返す可能性があります。 -#### fromJson +#### fromJSON `fromJSON(value)` -`value`に対するJSONオブジェクトを返します。 この関数は、評価された式としてJSONオブジェクトを提供するために利用できます。 +`value`に対するJSONオブジェクト、あるいはJSONデータ型を返します。 この関数を使って、評価された式としてJSONオブジェクトを提供したり、環境変数を文字列から変換したりできます。 -##### サンプル +##### JSONオブジェクトを返す例 以下のワークフローはJSONのマトリックスを1つのジョブに設定し、それを出力と`fromJSON`を使って次のジョブに渡します。 @@ -384,12 +384,33 @@ jobs: needs: job1 runs-on: ubuntu-latest strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} steps: - run: build ``` {% endraw %} +##### JSONデータ型を返す例 + +このワークフローは`fromJSON`を使い、環境変数を文字列型から論理型もしくは整数に変換します。 + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... +``` +{% endraw %} + #### hashFiles `hashFiles(path)` @@ -412,7 +433,7 @@ jobs: ### ジョブステータスのチェック関数 -`if` 条件では、次のステータスチェック関数を式として使用できます。 `if` 条件ステータス関数が含まれていない場合、結果は自動的に `success()` になります。 `if` 条件に関する詳しい情報については、「[GitHub Actions のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)」を参照してください。 +`if` 条件では、次のステータスチェック関数を式として使用できます。 `if`式にステータス関数が含まれていない場合、結果は自動的に `success()` になります。 `if` 条件に関する詳しい情報については、「[GitHub Actions のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)」を参照してください。 #### success diff --git a/translations/ja-JP/content/actions/reference/encrypted-secrets.md b/translations/ja-JP/content/actions/reference/encrypted-secrets.md index 0acafdc02e..50548c7671 100644 --- a/translations/ja-JP/content/actions/reference/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/reference/encrypted-secrets.md @@ -1,6 +1,6 @@ --- title: 暗号化されたシークレット -intro: Encrypted secrets allow you to store sensitive information in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environments{% else %} or repository{% endif %}. +intro: 暗号化されたシークレットを使うと、機密情報をOrganization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、リポジトリ、あるいはリポジトリの環境{% else %}あるいはリポジトリ{% endif %}に保存できます。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets @@ -17,12 +17,12 @@ versions: ### 暗号化されたシークレットについて -Secrets are encrypted environment variables that you create in an organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environment{% else %} or repository{% endif %}. The secrets that you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to help ensure that secrets are encrypted before they reach {% data variables.product.prodname_dotcom %} and remain encrypted until you use them in a workflow. +シークレットは暗号化された環境変数で、Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} リポジトリ、あるいはリポジトリ環境{% else %}あるいはリポジトリ{% endif %}に作成できます。 作成したシークレットは、{% data variables.product.prodname_actions %}ワークフローで利用できます。 {% data variables.product.prodname_dotcom %}はシークレットが{% data variables.product.prodname_dotcom %}に到達する前に暗号化され、ワークフローで使用されるまで暗号化されたままになっていることを確実にするのを助けるために[libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)を使います。 {% data reusables.github-actions.secrets-org-level-overview %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers. +環境レベルで保存されたシークレットについては、それらへのアクセスを制御するために必須のレビュー担当者を有効化することができます。 必須の承認者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 {% endif %} #### シークレットに名前を付ける @@ -32,10 +32,10 @@ For secrets stored at the environment level, you can enable required reviewers t * シークレット名には、英数字（`[a-z]`、`[A-Z]`、`[0-9]`）または下線（`_`）のみを含めることができます。 スペースは使用できません。 * シークレット名の最初を `GITHUB_` プレフィックスにすることはできません。 * シークレット名の最初を数字にすることはできません。 -* Secret names are not case-sensitive. -* シークレット名は、作成されたレベルで一意である必要があります。 For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. +* シークレット名は大文字と小文字を区別しません。 +* シークレット名は、作成されたレベルで一意である必要があります。 たとえば {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}環境のレベルで作成されたシークレットはその環境内でユニークな名前になっていなければならず、{% endif %}リポジトリのレベルで作成されたシークレットはそのリポジトリ内でユニークな名前になっていなければならず、Organizationのレベルで作成されたシークレットはそのレベルでユニークな名前になっていなければなりません。 - If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %} + 複数のレベルで同じ名前のシークレットが存在する場合、低いレベルのシークレットが優先されます。 たとえば、Organizationレベルのシークレットがリポジトリレベルのシークレットと同じ名前を持っているなら、リポジトリレベルのシークレットが優先されます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}同様に、Organization、リポジトリ、環境のすべてのレベルで同じ名前のシークレットがあるなら、環境レベルのシークレットが優先されます。{% endif %} {% data variables.product.prodname_dotcom %} がログのシークレットを確実に削除するよう、シークレットの値として構造化データを使用しないでください。 たとえば、JSONやエンコードされたGit blobを含むシークレットは作成しないでください。 @@ -43,7 +43,7 @@ For secrets stored at the environment level, you can enable required reviewers t シークレットをアクションが使用できるようにするには、ワークフローファイルでシークレットを入力または環境変数に設定する必要があります。 アクションに必要な入力および環境変数については、アクションのREADMEファイルを確認します。 詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。 -ファイルを編集するアクセス権を持っていれば、ワークフローファイル中の暗号化されたシークレットを使い、読み取ることができます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/github/getting-started-with-github/access-permissions-on-github)」を参照してください。 +ワークフローファイルを編集するアクセス権を持っていれば、ワークフローファイル中の暗号化されたシークレットを使い、読み取ることができます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/github/getting-started-with-github/access-permissions-on-github)」を参照してください。 {% warning %} @@ -52,14 +52,14 @@ For secrets stored at the environment level, you can enable required reviewers t {% endwarning %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts. +Organization及びリポジトリのシークレットはワークフローの実行がキューイングされた時点で読まれ、環境のシークレットは環境を参照しているジョブが開始された時点で読まれます。 {% endif %} REST API を使用してシークレットを管理することもできます。 詳しい情報については、「[シークレット](/rest/reference/actions#secrets)」を参照してください。 #### 認証情報のアクセス許可を制限する -クレデンシャルを生成する際には、可能な限り最小限の権限だけを許可することをおすすめします。 たとえば、個人のクレデンシャルを使う代わりに、[デプロイキー](/developers/overview/managing-deploy-keys#deploy-keys)あるいはサービスアカウントを使ってください。 必要なのが読み取りだけであれば、読み取りのみの権限を許可すること、そしてアクセスをできるかぎり限定することを考慮してください。 個人アクセストークン（PAT）を生成する際には、必要最小限のスコープを選択してください。 +認証情報を生成する際には、可能な限り最小限の権限だけを許可することをおすすめします。 たとえば、個人の認証情報を使う代わりに、[デプロイキー](/developers/overview/managing-deploy-keys#deploy-keys)あるいはサービスアカウントを使ってください。 必要なのが読み取りだけであれば、読み取りのみの権限を許可すること、そしてアクセスをできるかぎり限定することを考慮してください。 個人アクセストークン（PAT）を生成する際には、必要最小限のスコープを選択してください。 ### リポジトリの暗号化されたシークレットの作成 @@ -68,23 +68,23 @@ REST API を使用してシークレットを管理することもできます {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.sidebar-secret %} -1. Click **New repository secret**. +1. **New repository secret（新しいリポジトリのシークレット）**をクリックしてください。 1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 1. シークレットの値を入力します。 1. [**Add secret（シークレットの追加）**] をクリックします。 -If your repository {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page. +リポジトリが{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}環境のシークレットを持っているか{% endif %}親のOrganizationのシークレットにアクセスできるなら、それらのシークレットもこのページにリストされます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Creating encrypted secrets for an environment +### 環境の暗号化されたシークレットの生成 {% data reusables.github-actions.permissions-statement-secrets-environment %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.sidebar-environment %} -1. Click on the environment that you want to add a secret to. -1. Under **Environment secrets**, click **Add secret**. +1. シークレットを追加したい環境をクリックしてください。 +1. **Environment secrets（環境のシークレット）**の下で、**Add secret（シークレットの追加）**をクリックしてください。 1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 1. シークレットの値を入力します。 1. [**Add secret（シークレットの追加）**] をクリックします。 @@ -99,7 +99,7 @@ Organizationでシークレットを作成する場合、ポリシーを使用 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} -1. Click **New organization secret**. +1. **New organization secret（新しいOrganizationのシークレット）**をクリックしてください。 1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 1. シークレットの **Value（値）** を入力します。 1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 @@ -177,7 +177,7 @@ steps: ### シークレットの制限 -You can store up to 1,000 secrets per organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, 100 secrets per repository, and 100 secrets per environment{% else %} and 100 secrets per repository{% endif %}. A workflow may use up to 100 organization secrets and 100 repository secrets.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Additionally, a job referencing an environment may use up to 100 environment secrets.{% endif %} +Organizationには最大1,000個のシークレットを{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、リポジトリには100個のシークレットを、環境には100個のシークレットを{% else %}、リポジトリには100個のシークレットを{% endif %}保存できます。 ワークフローは最大で100個のOrganizationのシークレットと100個のリポジトリシークレットを利用できます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 加えて、環境を参照するジョブは最大で100個の環境のシークレットを利用できます。{% endif %} シークレットの容量は最大64 KBです。 64 KBより大きなシークレットを使うには、暗号化されたシークレットをリポジトリ内に保存して、復号化パスフレーズを{% data variables.product.prodname_dotcom %}に保存します。 たとえば、{% data variables.product.prodname_dotcom %}のリポジトリにファイルをチェックインする前に、`gpg`を使って認証情報をローカルで暗号化します。 詳しい情報については、「[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)」を参照してください。 diff --git a/translations/ja-JP/content/actions/reference/environment-variables.md b/translations/ja-JP/content/actions/reference/environment-variables.md index a128797a9c..011277ca0f 100644 --- a/translations/ja-JP/content/actions/reference/environment-variables.md +++ b/translations/ja-JP/content/actions/reference/environment-variables.md @@ -18,18 +18,28 @@ versions: {% data variables.product.prodname_dotcom %}は、ワークフローの実行におけるどのステップでも使用できる、デフォルトの環境変数を設定します。 環境変数では、大文字小文字は区別されます。 アクションあるいはステップ内で実行されるコマンドは、環境変数を作成、読み取り、変更することができます。 -カスタムの環境変数を設定するには、ワークフローファイル中でその変数を指定しなければなりません。 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. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。 +カスタムの環境変数を設定するには、ワークフローファイル中でその変数を指定しなければなりません。 [`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)、[`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)といったキーワードを使って、ステップ、ジョブ、あるいはワークフロー全体の環境変数を定義できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。 ```yaml -steps: - - name: Hello world - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +環境変数の値をワークフローファイル内で使うには、[`env`コンテキスト](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)を使わなければなりません。 環境変数の値をランナー内で使いたいなら、ランナーのオペレーティングシステムで環境変数を読む通常の方法が使えます。 + +ワークフローファイルの`run`キーを使って環境変数をランナーのオペレーティングシステム内から読む場合（上の例のように）、ジョブがランナーに送られた後に変数はランナーのオペレーティングシステム内で置き換えられます。 ワークフローファイルの他の部分では、環境変数を読むために`env`コンテキストを使わなければなりません。これは、ワークフローのキー（`if`など）で、ワークフローがランナーに送られる前に変数が置き換えられなければならないためです。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `GITHUB_ENV` 環境ファイル {% else %} `set-env` ワークフローコマンド {% endif %} を使用して、ワークフローの次の手順で使用できる環境変数を設定することもできます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 環境ファイル {% else %} `set-env` コマンド {% endif %} は、アクションによって直接使用することも、`run` キーワードを使用してワークフローファイルのシェルコマンドとして使用することもできます。 詳しい情報については「[{% data variables.product.prodname_actions %}のワークフローコマンド](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)」を参照してください。 ### デフォルトの環境変数 @@ -50,20 +60,20 @@ steps: | `GITHUB_EVENT_PATH` | 完了したwebhookイベントペイロードのファイルのパス。 `/github/workflow/event.json`などです。 | | `GITHUB_WORKSPACE` | {% data variables.product.prodname_dotcom %}ワークスペースディレクトリのパス。 ワークフローで [actions/checkout](https://github.com/actions/checkout) アクションを使用する場合、ワークスペースディレクトリはリポジトリのコピーです。 `actions/checkout`アクションを使用していない場合、ディレクトリは空となります。 たとえば、`/home/runner/work/my-repo-name/my-repo-name`となります。 | | `GITHUB_SHA` | ワークフローをトリガーしたコミットSHA。 たとえば、`ffac537e6cbbf934b08745a378932722df287a53`です。 | -| `GITHUB_REF` | ワークフローをトリガーしたブランチまたはタグref。 たとえば、`refs/heads/feature-branch-1`です。 イベントタイプのブランチもタグも利用できない場合、変数は存在しません。 | -| `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` | {% data variables.product.product_name %} サーバーの URL を返します。 For example: `https://github.com`. | -| `GITHUB_API_URL` | API URL を返します。 For example: `https://api.github.com`. | -| `GITHUB_GRAPHQL_URL` | グラフ QL API の URL を返します。 For example: `https://api.github.com/graphql`. | +| `GITHUB_REF` | ワークフローをトリガーしたブランチまたはタグref。 たとえば、`refs/heads/feature-branch-1`です。 イベントタイプのブランチもタグも利用できない場合、この変数は存在しません。 | +| `GITHUB_HEAD_REF` | Pull Requestのイベントに対してのみ設定されます。 headブランチの名前です。 | +| `GITHUB_BASE_REF` | Pull Requestのイベントに対してのみ設定されます。 ベースブランチの名前です。 | +| `GITHUB_SERVER_URL` | {% data variables.product.product_name %} サーバーの URL を返します。 For example: `https://{% data variables.product.product_url %}`. | +| `GITHUB_API_URL` | API URL を返します。 For example: `{% data variables.product.api_url_code %}`. | +| `GITHUB_GRAPHQL_URL` | グラフ QL API の URL を返します。 For example: `{% data variables.product.graphql_url_code %}`. | {% tip %} -**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` +**ノート:** ワークフローの実行のURLをジョブの中から使う必要がある場合は、`$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`というようにこれらの環境変数を組み合わせることができます。 {% endtip %} -#### Determining when to use default environment variables or contexts +#### デフォルトの環境変数を使う場合とコンテキストを使う場合の判断 {% data reusables.github-actions.using-context-or-environment-variables %} @@ -71,7 +81,7 @@ steps: {% note %} -**Note:** {% data variables.product.prodname_dotcom %} reserves the `GITHUB_` environment variable prefix for internal use by {% data variables.product.prodname_dotcom %}. `GITHUB_`プレフィックスを使用して環境変数またはシークレットを設定すると、エラーになります。 +**ノート:** {% data variables.product.prodname_dotcom %}は環境変数のプレフィックスの`GITHUB_`を、{% data variables.product.prodname_dotcom %}の内部的な利用のために予約しています。 `GITHUB_`プレフィックスを使用して環境変数またはシークレットを設定すると、エラーになります。 {% endnote %} diff --git a/translations/ja-JP/content/actions/reference/environments.md b/translations/ja-JP/content/actions/reference/environments.md index 58585b2950..18f71fcb5a 100644 --- a/translations/ja-JP/content/actions/reference/environments.md +++ b/translations/ja-JP/content/actions/reference/environments.md @@ -1,6 +1,6 @@ --- -title: Environments -intro: You can configure environments with protection rules and secrets. A workflow job can reference an environment to use the environment's protection rules and secrets. +title: 環境 +intro: 保護ルールとシークレットを持つ環境を設定できます。 ワークフローのジョブは、環境を参照して、環境の保護ルールとシークレットを利用できます。 product: '{% data reusables.gated-features.environments %}' versions: free-pro-team: '*' @@ -9,61 +9,61 @@ versions: {% data reusables.actions.environments-beta %} -### About environments +### 環境について -You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass. +保護ルールとシークレットを持つ環境を設定できます。 ワークフローのジョブが環境を参照すると、その環境の保護ルールをすべてパスするまではジョブは開始されません。 すべての環境の保護ルールをパスするまで、ジョブは環境で定義されているシークレットにアクセスできません。 {% if currentVersion == "free-pro-team@latest" %} -Environment protection rules and environment secrets are only available on public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. +環境の保護ルールと環境のシークレットは、パブリックリポジトリでのみ利用できます。 リポジトリをパブリックからプライベートに変換すると、設定された保護ルールや環境のシークレットは無視されるようになり、環境は設定できなくなります。 リポジトリをパブリックに変換して戻せば、以前に設定されていた保護ルールや環境のシークレットにアクセスできるようになります。 {% endif %} -#### Environment protection rules +#### 環境の保護ルール -Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. You can use environment protection rules to require a manual approval or to delay a job. +環境の保護ルールは、その環境を参照しているジョブが進行する前に特定の条件をパスすることを要求します。 環境の保護ルールを使って、手動の承認を必須にしたり、ジョブを遅延させたりできます。 -##### Required reviewers +##### 必須のレビュー担当者 -Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed. +必須のレビュー担当者を使って、特定の人もしくはTeamがその環境を参照するワークフローのジョブを承認しなければならないようにすることができます。 最大で6人のユーザもしくはTeamをレビュー担当者とすることができます。 レビュー担当者は、少なくともそのリポジトリの読み取りアクセス権を持っていなければなりません。 ジョブが進行するため承認が必要なレビュー担当者は1人だけです。 -For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." +必須のレビュー担当者を持つ環境を参照しているジョブのレビューに関する詳しい情報については「[デプロイメントのレビュー](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。 -##### Wait timer +##### 待機タイマー -Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days). +ジョブが最初にトリガーされた後、特定の時間ジョブを遅延させるために、待機タイマーを使ってください。 時間（分）は、0から43,200（30日）の間の整数でなければなりません。 -#### Environment secrets +#### 環境のシークレット -Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +環境に保存されたシークレットは、その環境を参照するワークフロージョブからのみ利用できます。 環境が承認を必要とするなら、ジョブは必須のレビュー担当者の一人が承認するまで環境のシークレットにアクセスできません。 シークレットに関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。 -### Creating an environment +### 環境の作成 {% data reusables.github-actions.permissions-statement-environment %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.sidebar-environment %} -1. Click **New environment**. -1. Enter a name for the environment, then click **Configure environment**. Environment names are not case sensitive. An environment name may not exceed 255 characters and must be unique within the repository. -1. Configure any environment protection rules or environment secrets. +1. **New environment（新しい環境）**をクリックしてください。 +1. 環境の名前を入力し、**Configure environment（環境を設定）**をクリックしてください。 環境名では、大文字と小文字は区別されません。 環境名は255文字を超えてはならず、リポジトリ内でユニークでなければなりません。 +1. 環境保護ルールあるいは環境のシークレットを設定してください。 -Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment. +存在しない環境を参照するワークフローを実行すると、参照された名前を持つ環境が作成されます。 新しく作成される環境には、保護ルールやシークレットは設定されていません。 リポジトリのワークフローを編集できる人は、ワークフローファイルを通じて環境を作成できますが、その環境を設定できるのはリポジトリ管理者だけです。 -### Referencing an environment +### 環境の参照 -Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. When the job is sent to the runner, the job can access the environment's secrets. +ワークフロー中の各ジョブは、1つの環境を参照できます。 その環境を参照するジョブがランナーに送信される前に、その環境に設定された保護ルールはパスしなければなりません。 ジョブがランナーに送信されると、ジョブは環境のシークレットにアクセスできます。 -For more information on syntax to reference environments in workflows, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idenvironment)." For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." +ワークフローで環境を参照するための構文に関する詳しい情報については「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idenvironment)」を参照してください。 必須のレビュー担当者を持つ環境を参照しているジョブのレビューに関する詳しい情報については「[デプロイメントのレビュー](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。 -When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." +ワークフローが環境を参照する場合、その環境はリポジトリのデプロイメントに現れます。 現在及び以前のデプロイメントの表示に関する詳細については「[デプロイメント履歴の表示](/developers/overview/viewing-deployment-history)」を参照してください。 -### Deleting an environment +### 環境の削除 {% data reusables.github-actions.permissions-statement-environment %} -Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail. +環境を削除すると、その環境に関連づけられたすべてのシークレットと保護ルールが削除されます。 削除された環境の保護ルールのために待機していたジョブは、自動的に失敗します。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.sidebar-environment %} -1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}. -2. Click **I understand, delete this environment**. +1. 削除したい環境の隣の{% octicon "trashcan" aria-label="The trashcan icon" %}をクリックしてください。 +2. **I understand, delete this environment（分かりました、この環境を削除してください）**をクリックしてください。 diff --git a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md index 8c91a1f43f..e70d29eb7f 100644 --- a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md @@ -80,7 +80,7 @@ versions: [crontab guru](https://crontab.guru/) を使うと、クーロン構文の生成および実行時間の確認に役立ちます。 また、クーロン構文の生成を支援するため、[crontab guru のサンプル](https://crontab.guru/examples.html)リストもあります。 -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)." +ワークフロー内のクーロン構文を最後に修正したユーザには、スケジュールされたワークフローの通知が送られます。 詳しい情報については「[ワークフローの実行の通知](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)」を参照してください。 ### 手動イベント @@ -94,7 +94,7 @@ Notifications for scheduled workflows are sent to the user who last modified the カスタム定義の入力プロパティ、デフォルトの入力値、イベントに必要な入力をワークフローで直接設定できます。 ワークフローが実行されると、 `github.event.inputs` コンテキスト内の入力値にアクセスできます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)」を参照してください。 -You can manually trigger a workflow run using the {% data variables.product.prodname_dotcom %} API and from {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[ワークフローを手動で実行する](/actions/managing-workflow-runs/manually-running-a-workflow)」を参照してください。 +{% data variables.product.product_name %} APIを使って、あるいは{% data variables.product.product_name %}から、手動でワークフローの実行をトリガーすることができます。 詳しい情報については、「[ワークフローを手動で実行する](/actions/managing-workflow-runs/manually-running-a-workflow)」を参照してください。 {% data variables.product.prodname_dotcom %} でイベントをトリガーすると、{% data variables.product.prodname_dotcom %} で `ref` と `inputs` を直接入力できます。 詳しい情報については、「[アクションで入力と出力を使用する](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)」を参照してください。 @@ -102,7 +102,7 @@ You can manually trigger a workflow run using the {% data variables.product.prod ##### サンプル -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: +`workflow_dispatch`イベントを使うには、GitHub Actionsのワークフローファイル中にトリガーとして含めなければなりません。 以下の例では、手動でトリガーされた場合にのみワークフローが実行されます。 ```yaml on: workflow_dispatch @@ -110,7 +110,7 @@ on: workflow_dispatch ##### ワークフロー設定の例 -この例では、 `code`と`home`を入力として定義し、`github.event.inputs.name`及び`github.event.inputs.home`コンテキストを使用してそれらを出力します。 If a `home` isn't provided, the default value 'The Octoverse' is printed. +この例では、 `code`と`home`を入力として定義し、`github.event.inputs.name`及び`github.event.inputs.home`コンテキストを使用してそれらを出力します。 `home`が提供されなければ、デフォルト値の'The Octoverse'が出力されます。 {% raw %} ```yaml @@ -325,9 +325,9 @@ on: types: [created, deleted] ``` -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. +`issue_comment`イベントは、IssueやPull Requestにコメントされたときに生じます。 `issue_comment`イベントがIssueで生じたのかPull Requestで生じたのかを判断するには、イベントのペイロードの`issue.pull_request`属性をチェックして、それをジョブをスキップする条件として利用できます。 -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. +たとえば、コメントイベントがPull Requestで生じたときに`pr_commented`を実行し、コメントイベントがIssueで生じたときに`issue_commented`ジョブを実行するようにできます。 {% raw %} ```yaml @@ -578,11 +578,11 @@ on: #### `pull_request_target` -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. +このイベントは`pull_request`のようにマージコミット内ではなく、Pull Requestのベースのコンテキストで実行されます。 これにより、リポジトリを変更したり、ワークフローで使うシークレットを盗んだりするような、Pull Requestのヘッドからの安全ではないワークフローのコードが実行されるのを避けられます。 このイベントでは、イベントペイロードの内容に基づいて、プルリクエストにラベルを付けてコメントを付けるワークフローを作成するようなことができます。 {% warning %} -**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. +**警告:** `pull_request_target`イベントは、フォークからトリガーされた場合であっても、リポジトリトークンの読み書きが許可されており、シークレットにアクセスできます。 ワークフローはPull Requestのベースのコンテキストで実行されますが、このイベントでPull Requestから信頼できないコードをチェックアウトしたり、ビルドしたり、実行したりしないようにしなければなりません。 加えて、ベースブランチと同じスコープを共有するキャッシュがあり、キャッシュが汚染されることを避けるために、キャッシュの内容が変更されている可能性があるなら、キャッシュを保存するべきではありません。 {% endwarning %} @@ -734,4 +734,4 @@ on: {% data reusables.github-actions.actions-do-not-trigger-workflows %} 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。 -ワークフローの実行からワークフローをトリガーしたい場合意は、個人アクセストークンを使ってイベントをトリガーできます。 個人アクセストークンを作成し、それをシークレットとして保存する必要があります。 {% data variables.product.prodname_actions %}の利用コストを最小化するために、再帰的あるいは意図しないワークフローの実行が生じないようにしてください。 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)." +ワークフローの実行からワークフローをトリガーしたい場合には、個人アクセストークンを使ってイベントをトリガーできます。 個人アクセストークンを作成し、それをシークレットとして保存する必要があります。 {% data variables.product.prodname_actions %}の利用コストを最小化するために、再帰的あるいは意図しないワークフローの実行が生じないようにしてください。 個人アクセストークンのシークレットとしての保存に関する詳しい情報については「[暗号化されたシークレットの作成と保存](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)」を参照してください。 diff --git a/translations/ja-JP/content/actions/reference/index.md b/translations/ja-JP/content/actions/reference/index.md index c29abf789d..a01b6fe9e0 100644 --- a/translations/ja-JP/content/actions/reference/index.md +++ b/translations/ja-JP/content/actions/reference/index.md @@ -27,15 +27,15 @@ versions: ### 認証とシークレット -{% data variables.product.prodname_dotcom %}は、{% data variables.product.prodname_actions %}の代理で認証を受けるために利用できるトークンを提供します。 You can also store sensitive information as a secret in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environments{% else %} or repository{% endif %}. {% data variables.product.prodname_dotcom %} はすべてのシークレットを暗号化します。 +{% data variables.product.prodname_dotcom %}は、{% data variables.product.prodname_actions %}の代理で認証を受けるために利用できるトークンを提供します。 機密情報をOrganization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、リポジトリ、環境{% else %}あるいはリポジトリ{% endif %}のシークレットとして保存することもできます。 {% data variables.product.prodname_dotcom %} はすべてのシークレットを暗号化します。 {% link_in_list /authentication-in-a-workflow %} {% link_in_list /encrypted-secrets %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Environments +### 環境 -Workflow jobs can reference environments that have protection rules or environment-specific secrets. +ワークフロージョブは、保護ルールあるいは環境固有のシークレットを持つ環境を参照できます。 {% link_in_list /environments %} {% endif %} diff --git a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md index cb0f79cb01..eb961ffa02 100644 --- a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md @@ -29,15 +29,15 @@ versions: #### {% data variables.product.prodname_dotcom %}ホストランナーのクラウドホスト -{% data variables.product.prodname_dotcom %}は、Microsoft AzureのStandard_DS2_v2仮想マシン上で{% data variables.product.prodname_actions %}ランナーアプリケーションがインストールされたLinux及びWindowsランナーをホストします。 {% data variables.product.prodname_dotcom %}ホストランナーアプリケーションは、Azure Pipelines Agentのフォークです。 インバウンドのICMPパケットはすべてのAzure仮想マシンでブロックされるので、pingやtracerouteコマンドは動作しないでしょう。 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 %}は、Microsoft AzureのStandard_DS2_v2仮想マシン上で{% data variables.product.prodname_actions %}ランナーアプリケーションがインストールされたLinux及びWindowsランナーをホストします。 {% data variables.product.prodname_dotcom %}ホストランナーアプリケーションは、Azure Pipelines Agentのフォークです。 インバウンドのICMPパケットはすべてのAzure仮想マシンでブロックされるので、pingやtracerouteコマンドは動作しないでしょう。 Standard_DS2_v2マシンのリソースに関する詳しい情報については、Microsoft Azureドキュメンテーションの「[Dv2 and DSv2シリーズ](https://docs.microsoft.com/ja-jp/azure/virtual-machines/dv2-dsv2-series#dsv2-series)」を参照してください。 -{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. +{% data variables.product.prodname_dotcom %}は、{% data variables.product.prodname_dotcom %}自身macOS Cloud内でmacOSランナーをホストします。 #### {% data variables.product.prodname_dotcom %}ホストランナーの管理権限 LinuxおよびmacOSの仮想環境は、パスワード不要の`sudo`により動作します。 現在のユーザが持っているよりも高い権限が求められるコマンドやインストールツールを実行する必要がある場合は、パスワードを入力する必要なく、`sudo`を使うことができます。 詳しい情報については、「[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)」を参照してください。 -Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効化されて管理者として動作するように設定されています。 詳しい情報については、Windowsのドキュメンテーションの「[ユーザー アカウント制御のしくみ](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)」を参照してください。 +Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効化されて管理者として動作するように設定されています。 詳しい情報については、Windowsのドキュメンテーションの「[ユーザー アカウント制御のしくみ](https://docs.microsoft.com/ja-jp/windows/security/identity-protection/user-account-control/how-user-account-control-works)」を参照してください。 ### サポートされているランナーとハードウェアリソース @@ -83,11 +83,11 @@ Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効 {% endnote %} -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. +Windows及びUbuntuのランナーはAzureでホストされており、そのためAzureのデータセンターと同じIPアドレスの範囲を持ちます。 macOSランナーは{% data variables.product.prodname_dotcom %}独自のmacOSクラウドでホストされます。 -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. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. +{% data variables.product.prodname_dotcom %}ホストランナーに{% data variables.product.prodname_actions %}が使うIPアドレスの範囲のリストを取得するには、{% data variables.product.prodname_dotcom %}のREST APIが利用できます。 詳しい情報については「[GitHubメタ情報の取得](/rest/reference/meta#get-github-meta-information)」エンドポイントのレスポンス中の`actions`キーを参照してください。 内部リソースへの未認可のアクセスを防ぐために許可リストが必要な場合には、このIPアドレスのリストを利用できます。 -The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. +このAPIが返す{% data variables.product.prodname_actions %}のIPアドレスのリストは、週に1回更新されます。 ### ファイルシステム diff --git a/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md index 88c6b1d610..da54cd1876 100644 --- a/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ja-JP/content/actions/reference/usage-limits-billing-and-administration.md @@ -1,6 +1,6 @@ --- title: '使用制限、支払い、管理' -intro: '{% data variables.product.prodname_actions %} ワークフローには使用制限があります。 使用料は、リポジトリの空き時間とストレージの量を超えるリポジトリに適用されます。' +intro: '{% data variables.product.prodname_actions %} ワークフローには使用制限があります。 使用料は、リポジトリの無料の時間とストレージの量を超えるリポジトリに適用されます。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions @@ -29,7 +29,7 @@ GitHub アクションの使用は、 {% note %} -**注釈:** セルフホストランナーの場合、さまざまな使用制限が適用されます。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。 +**ノート:** セルフホストランナーの場合、さまざまな使用制限が適用されます。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。 {% endnote %} @@ -57,17 +57,17 @@ GitHub アクションの使用は、 {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### アーティファクトとログの保持ポリシー +### 成果物とログの保持ポリシー -リポジトリ、Organization、または Enterprise アカウントのアーティファクトとログの保持期間を設定できます。 +リポジトリ、Organization、または Enterprise アカウントの成果物とログの保持期間を設定できます。 {% data reusables.actions.about-artifact-log-retention %} 詳しい情報については、以下を参照してください。 -- [リポジトリ内のアーティファクトとログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [Organization 内のアーティファクトとログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) -- [Enterprise 内のアーティファクトとログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) +- [リポジトリ内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) +- [Organization 内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Enterprise 内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} ### リポジトリまたは Organization の {% data variables.product.prodname_actions %} を無効化または制限する diff --git a/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md index b3a74b06e7..add8a893b4 100644 --- a/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md @@ -71,7 +71,7 @@ core.setOutput('SELECTED_COLOR', 'green'); | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}環境ファイル `GITHUB_PATH` を使用してアクセス可能{% else %} `add-path` {% endif %} | | | | | | `core.debug` | `debug` | -| `core.error` | `エラー` | +| `core.error` | `error` | | `core.endGroup` | `endgroup` | | `core.exportVariable` | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}環境ファイル `GITHUB_ENV` を使用してアクセス可能{% else %} `set-env` {% endif %} | | @@ -119,7 +119,7 @@ echo "::set-output name=action_fruit::strawberry" `::add-path::{path}` -現在のジョブ内にある、続くすべてのアクションにおいて、システム `PATH` 変数の前に、ディレクトリを付加します。 現在実行中のアクションは、新しいパス変数にアクセスできません。 +現在のジョブ内にある、後に続くすべてのアクションにおいて、システム `PATH` 変数の前に、ディレクトリを付加します。 現在実行中のアクションは、新しいパス変数にアクセスできません。 #### サンプル @@ -164,14 +164,14 @@ echo "::warning file=app.js,line=1,col=5::Missing semicolon" echo "::error file=app.js,line=10,col=15::Something went wrong" ``` -### Grouping log lines +### ログの行のグループ化 ``` ::group::{title} ::endgroup:: ``` -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. +展開可能なグループをログ中に作成します。 グループを作成するには、`group`コマンドを使って`title`を指定してください。 `group`と`endgroup`コマンド間でログに出力したすべての内容は、ログ中の展開可能なエントリ内にネストされます。 #### サンプル @@ -181,7 +181,7 @@ echo "Inside group" echo "::endgroup::" ``` -![Foldable group in workflow run log](/assets/images/actions-log-group.png) +![ワークフローの実行ログ中の折りたたみ可能なグループ](/assets/images/actions-log-group.png) ### ログ中での値のマスク @@ -257,7 +257,7 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro **警告:** Powershell はデフォルト設定で UTF-8 を使用しません。 正しいエンコーディングを使用してファイルを書き込むようにしてください。 たとえば、パスを設定するときに UTF-8 エンコーディングを設定する必要があります。 -``` +```yaml steps: - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` @@ -272,13 +272,21 @@ steps: #### サンプル -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} -将来のステップで `$action_state` を実行すると `yellow` が返されるようになりました - -#### Multiline strings +#### 複数行の文字列 複数行の文字列の場合、次の構文で区切り文字を使用できます。 @@ -291,7 +299,7 @@ echo "action_state=yellow" >> $GITHUB_ENV ##### サンプル この例では、区切り文字として `EOF` を使用し、`JSON_RESPONSE` 環境変数を cURL レスポンスの値に設定します。 -``` +```yaml steps: - name: Set the value id: step_one @@ -305,11 +313,11 @@ steps: `echo "{path}" >> $GITHUB_PATH` -Prepends a directory to the system `PATH` variable and 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. +システムの`PATH`変数の先頭にディレクトリを追加し、現在のジョブ中の以降のすべてのアクションで利用できるようにします。現在実行中のアクションは、更新されたPATH変数にアクセスできません。 ジョブに現在定義されているパスを見るには、ステップもしくはアクション中で`echo "$PATH"`を使うことができます。 #### サンプル -This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`: +この例は、ユーザの`$HOME/.local/bin`ディレクトリを`PATH`に追加する方法を示しています。 ``` bash echo "$HOME/.local/bin" >> $GITHUB_PATH diff --git a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md index e20f0e055a..09313196a0 100644 --- a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ versions: ### `on` -**必須** ワークフローをトリガーする{% data variables.product.prodname_dotcom %}イベントの名前。 指定できるのは、1つのイベント`string`、複数イベントの`array`、イベント`types`の`array`です。あるいは、ワークフローをスケジュールする、またはワークフロー実行を特定のファイルやタグ、ブランチ変更に限定するイベント設定`map`も指定できます。 使用可能なイベントの一覧は、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows)」を参照してください。 +**必須**。 ワークフローをトリガーする{% data variables.product.prodname_dotcom %}イベントの名前。 指定できるのは、1つのイベント`string`、複数イベントの`array`、イベント`types`の`array`です。あるいは、ワークフローをスケジュールする、またはワークフロー実行を特定のファイルやタグ、ブランチ変更に限定するイベント設定`map`も指定できます。 使用可能なイベントの一覧は、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows)」を参照してください。 {% data reusables.github-actions.actions-on-examples %} @@ -152,7 +152,7 @@ on: - 肯定のマッチの後に否定のマッチングパターン（`!`がプレフィックスされている）を置くと、パスが除外されます。 - 否定のマッチングパターンの後に肯定のマッチングパターンを定義すると、パスを再び含めます。 -この例は、`push`イベントに`sub-project`ディレクトリあるいはそのサブディレクトリ内のファイルが含まれ、そのファイルが`sub-project/docs`ディレクトリ内にあるのでない場合に実行されます。 たとえば`sub-project/index.js`もしくは`sub-project/src/index.js`を変更するプッシュはワークフローを実行させますが、`sub-project/docs/readme.md`だけを変更するプッシュは実行させません。 +この例は、`push`イベントに`sub-project`ディレクトリあるいはそのサブディレクトリ内のファイルが含まれ、そのファイルが`sub-project/docs`ディレクトリ内にはない場合に実行されます。 たとえば`sub-project/index.js`もしくは`sub-project/src/index.js`を変更するプッシュはワークフローを実行させますが、`sub-project/docs/readme.md`だけを変更するプッシュは実行させません。 ```yaml on: @@ -172,12 +172,12 @@ on: フィルタは、変更されたファイルを`paths-ignore`あるいは`paths`リストに対して評価することによって、ワークフローを実行すべきか判断します。 ファイルが変更されていない場合、ワークフローは実行されません。 -{% data variables.product.prodname_dotcom %}はプッシュに対してはツードットdiff、プルリクエストに対してはスリードットdiffを使って変更されたファイルのリストを生成します。 -- **プルリクエスト：** スリードットdiffは、トピックブランチの最新バージョンとトピックブランチがベースブランチと最後に同期されたコミットとの比較です。 +{% data variables.product.prodname_dotcom %}はプッシュに対してはツードットdiff、Pull Requestに対してはスリードットdiffを使って変更されたファイルのリストを生成します。 +- **Pull Request：** スリードットdiffは、トピックブランチの最新バージョンとトピックブランチがベースブランチと最後に同期されたコミットとの比較です。 - **既存のブランチへのプッシュ：** ツードットdiffは、headとベースのSHAを互いに直接比較します。 - **新しいブランチへのプッシュ：** 最も深いプッシュの先祖の親に対するツードットdiffです。 -詳しい情報については「[プルリクエスト中のブランチの比較について](/articles/about-comparing-branches-in-pull-requests)」を参照してください。 +詳しい情報については「[Pull Request中のブランチの比較について](/articles/about-comparing-branches-in-pull-requests)」を参照してください。 ### `on.schedule` @@ -187,7 +187,7 @@ cron構文に関する詳しい情報については、「[ワークフローを ### `env` -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. 詳しい情報については「[`jobs..env`](#jobsjob_idenv)」及び「[`jobs..steps[*].env`](#jobsjob_idstepsenv)を参照してください。 +ワークフロー中のすべてのジョブのステップから利用できる環境変数の`map`です。 1つのジョブのステップ、あるいは1つのステップからだけ利用できる環境変数を設定することもできます。 詳しい情報については「[`jobs..env`](#jobsjob_idenv)」及び「[`jobs..steps[*].env`](#jobsjob_idstepsenv)を参照してください。 {% data reusables.repositories.actions-env-var-note %} @@ -251,7 +251,7 @@ jobs: このジョブの実行前に正常に完了する必要があるジョブを示します。 文字列型または文字列の配列です。 1つのジョブが失敗した場合、失敗したジョブを続行するような条件式を使用していない限り、そのジョブを必要としている他のジョブはすべてスキップされます。 -#### Example requiring dependent jobs to be successful +#### 依存対象のジョブの成功が必要になる例 ```yaml jobs: @@ -270,7 +270,7 @@ jobs: 2. `job2` 3. `job3` -#### Example not requiring dependent jobs to be successful +#### 依存対象のジョブの成功が必要ではない例 ```yaml jobs: @@ -282,11 +282,11 @@ jobs: needs: [job1, job2] ``` -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 "[Context and expression syntax](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)." +この例では、`job3`は条件式の`always()` を使っているので、`job1`と`job2`が成功したかどうかにかかわらず、それらのジョブが完了したら常に実行されます。 詳しい情報については「[コンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)」を参照してください。 ### `jobs..runs-on` -**必須** ジョブを実行するマシンの種類。 マシンは{% data variables.product.prodname_dotcom %}ホストランナーあるいはセルフホストランナーのいずれかです。 +**必須**。 ジョブが実行されるマシンの種類。 マシンは{% data variables.product.prodname_dotcom %}ホストランナーあるいはセルフホストランナーのいずれかです。 {% data reusables.actions.enterprise-github-hosted-runners %} @@ -299,6 +299,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} ##### サンプル @@ -323,17 +324,17 @@ runs-on: [self-hosted, linux] {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ### `jobs..environment` -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 "[Environments](/actions/reference/environments)." +ジョブが参照する環境。 環境を参照するジョブがランナーに送られる前に、その環境のすべて保護ルールはパスしなければなりません。 詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 -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)." +環境は、環境の`name`だけで、あるいは`name` and `url`を持つenvironmentオブジェクトとして渡すことができます。 デプロイメントAPIでは、このURLは`environment_url`にマップされます。 デプロイメントAPIに関する詳しい情報については「[デプロイメント](/rest/reference/repos#deployments)」を参照してください。 -##### Example using a single environment name +##### 1つの環境名を使う例 ```yaml environment: staging_environment ``` -##### Example using environment name and URL +##### 環境名とURLを使う例 ```yaml environment: @@ -341,7 +342,7 @@ environment: url: https://github.com ``` -The URL can be an expression and can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +URLは式でもよく、`secrets`コンテキスト以外の任意のコンテキストを使うことができます。 式に関する詳しい情報については「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 #### サンプル {% raw %} @@ -387,7 +388,7 @@ jobs: ### `jobs..env` -ジョブ中のすべてのステップから利用できる環境変数の`map`です。 ワークフロー全体あるいは個別のステップのための環境変数を設定することもできます。 For more information, see [`env`](#env) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +ジョブ中のすべてのステップから利用できる環境変数の`map`です。 ワークフロー全体あるいは個別のステップのための環境変数を設定することもできます。 詳しい情報については[`env`](#env)及び[`jobs..steps[*].env`](#jobsjob_idstepsenv)を参照してください。 {% data reusables.repositories.actions-env-var-note %} @@ -506,24 +507,24 @@ steps: Git ref、SHA、またはDockerタグ番号を指定して、使用しているアクションのバージョンを含めることを強く推奨します。 バージョンを指定しないと、アクションのオーナーがアップデートを公開したときに、ワークフローが中断したり、予期せぬ動作をしたりすることがあります。 - リリースされたアクションバージョンのコミットSHAを使用するのが、安定性とセキュリティのうえで最も安全です。 -- 特定のメジャーアクションバージョンを使用すると、互換性を維持したまま重要な修正とセキュリティパッチを受け取ることができます。 ワークフローがまだ動作していることも確認できます。 -- アクションのデフォルトブランチを使用すると便利なこともありますが、別のユーザが大きな変更を加えた新しいメジャーバージョンをリリースすると、ワークフローが中断する場合があります。 +- 特定のメジャーアクションバージョンを使用すると、互換性を維持したまま重要な修正とセキュリティパッチを受け取ることができます。 ワークフローが引き続き動作することも保証できます。 +- アクションのデフォルトブランチを使用すると便利なこともありますが、別のユーザが破壊的変更を加えた新しいメジャーバージョンをリリースすると、ワークフローが動作しなくなる場合があります。 入力が必要なアクションもあり、入力を[`with`](#jobsjob_idstepswith)キーワードを使って設定する必要があります。 必要な入力を判断するには、アクションのREADMEファイルをお読みください。 -アクションは、JavaScriptのファイルもしくはDockerコンテナです。 使用するアクションがDockerコンテナの場合は、Linux環境で実行する必要があります。 詳細については[`runs-on`](#jobsjob_idruns-on)を参照してください。 +アクションは、JavaScriptのファイルもしくはDockerコンテナです。 使用するアクションがDockerコンテナの場合、ジョブはLinux環境で実行する必要があります。 詳細については[`runs-on`](#jobsjob_idruns-on)を参照してください。 -#### バージョンされたアクションを使用する例 +#### バージョン付けされたアクションを使用する例 ```yaml steps: - # 特定のコミットを参照する - - uses: actions/setup-node@74bc508 - # リリースのメジャーバージョンを参照する + # 特定のコミットを参照 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e + # リリースのメジャーバージョンを参照 - uses: actions/setup-node@v1 - # リリースのマイナーバージョンを参照する + # リリースのマイナーバージョンを参照 - uses: actions/setup-node@v1.2 - # ブランチを参照する + # ブランチを参照 - uses: actions/setup-node@main ``` @@ -637,17 +638,17 @@ jobs: #### 特定のシェルを使用する -`shell`キーワードを使用して、ランナーのオペレーティングシステムのデフォルトシェルを上書きできます。 組み込みの`shell`キーワードを使用するか、カスタムセットのシェルオプションを定義することができます。 +`shell`キーワードを使用して、ランナーのオペレーティングシステムのデフォルトシェルの設定を上書きできます。 組み込みの`shell`キーワードを使用するか、カスタムセットのシェルオプションを定義することができます。 -| サポートされているプラットフォーム | `shell` パラメータ | 説明 | 内部で実行されるコマンド | -| ----------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| すべて | `bash` | 非Windowsプラットフォームのデフォルトシェルで、`sh`へのフォールバックがあります。 Windowsでbashシェルを指定すると、Windows用Gitに含まれるbashシェルが使用されます。 | `bash --noprofile --norc -eo pipefail {0}` | -| すべて | `pwsh` | PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `pwsh -command ". '{0}'"` | -| すべて | `python` | Pythonのコマンドを実行します。 | `python {0}` | -| Linux / macOS | `sh` | 非Windowsプラットフォームにおいてシェルが提供されておらず、パス上で`bash`が見つからなかった場合のフォールバック動作です。 | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.cmd`を追加し、`{0}`を置き換えます。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `pwsh` | これはWindowsで使われるデフォルトのシェルです。 PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 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 %}はスクリプト名に拡張子`.ps1`を追加します。 | `powershell -command ". '{0}'"`. | +| サポートされているプラットフォーム | `shell` パラメータ | 説明 | 内部で実行されるコマンド | +| ----------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| すべて | `bash` | 非Windowsプラットフォームのデフォルトシェルで、`sh`へのフォールバックがあります。 Windowsでbashシェルを指定すると、Windows用Gitに含まれるbashシェルが使用されます。 | `bash --noprofile --norc -eo pipefail {0}` | +| すべて | `pwsh` | PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `pwsh -command ". '{0}'"` | +| すべて | `python` | Pythonのコマンドを実行します。 | `python {0}` | +| Linux / macOS | `sh` | 非Windowsプラットフォームにおいてシェルが提供されておらず、パス上で`bash`が見つからなかった場合のフォールバック動作です。 | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.cmd`を追加し、`{0}`を置き換えます。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | これはWindowsで使われるデフォルトのシェルです。 PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 セルフホストのWindowsランナーに_PowerShell Core_がインストールされていない場合、その代わりに_PowerShell Desktop_が使われます。 | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | PowerShell Desktop. {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `powershell -command ". '{0}'"`. | #### bashを使用してスクリプトを実行する例 @@ -676,7 +677,7 @@ steps: shell: pwsh ``` -#### Example: Using PowerShell Desktop to run a script +#### PowerShell Desktopを使用してスクリプトを実行する例 ```yaml steps: @@ -700,23 +701,35 @@ steps: `command […options] {0} [..more_options]`を使用すると、テンプレート文字列に`shell`値を設定できます。 {% data variables.product.prodname_dotcom %}は、空白区切りで最初の文字列をコマンドとして解釈し、`{0}`にある一時的なスクリプトのファイル名を挿入します。 +例: + +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +使われるコマンドは（この例では`perl`）は、ランナーにインストールされていなければなりません。 GitHubホストランナーに含まれるソフトウェアに関する情報については「[GitHubホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners#supported-software)」を参照してください。 + #### 終了コードとエラーアクションの環境設定 組み込みのshellキーワードについては、{% data variables.product.prodname_dotcom %}がホストする実行環境で以下のデフォルトが提供されます。 シェルスクリプトを実行する際には、以下のガイドラインを使ってください。 - `bash`/`sh`: - - `set -e o pipefail`を使用するフェイルファースト動作: `bash`のデフォルトで、組み込みの`shell`。 Windows以外のプラットフォームでオプションを指定しない場合のデフォルトでもあります。 + - `set -eo pipefail`を使用したフェイルファースト動作 : `bash`及び組み込みの`shell`のデフォルト。 Windows以外のプラットフォームでオプションを指定しない場合のデフォルトでもあります。 - フェイルファーストをオプトアウトし、シェルのオプションにテンプレート文字列を指定して完全に制御することもできます。 たとえば、`bash {0}`とします。 - shライクのシェルは、スクリプトで実行された最後のコマンドの終了コードで終了します。これが、アクションのデフォルトの動作でもあります。 runnerは、この終了コードに基づいてステップのステータスを失敗/成功としてレポートします。 - `powershell`/`pwsh` - 可能な場合のフェイルファースト動作。 `pwsh`および`powershell`の組み込みシェルの場合は、スクリプトの内容の前に`$ErrorActionPreference = 'stop'` が付加されます。 - - ここでは、アクションステータスがスクリプトの最後の終了コードを反映するように、PowerShellスクリプトに`if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }`を付加しています。 + - アクションステータスがスクリプトの最後の終了コードを反映するように、PowerShellスクリプトに`if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }`を付加します。 - 必要な場合には、組み込みシェルを使用せずに、`pwsh -File {0}`や`powershell -Command "& '{0}'"`などのカスタムシェルを指定すれば、いつでもオプトアウトすることができます。 - `cmd` - 各エラーコードをチェックしてそれぞれに対応するスクリプトを書く以外、フェイルファースト動作を完全にオプトインする方法はないようです。 デフォルトでその動作を指定することはできないため、この動作はスクリプトに記述する必要があります。 - - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。 + - `cmd.exe`は、実行した最後のプログラムのエラーレベルで終了し、runnerにそのエラーコードを返します。 この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。 ### `jobs..steps[*].with` @@ -775,7 +788,7 @@ steps: entrypoint: /a/different/executable ``` -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. +`entrypoint`キーワードはDockerコンテナアクションで使われることを意図したものですが、入力を定義しないJavaScriptのアクションでも使うことができます。 ### `jobs..steps[*].env` @@ -783,7 +796,7 @@ The `entrypoint` keyword is meant to be used with Docker container actions, but {% data reusables.repositories.actions-env-var-note %} -パブリックなアクションは、READMEファイル中で期待する環境変数を指定できます。 環境変数に秘密情報を設定しようとしている場合、秘密情報は`secrets`コンテキストを使って設定しなければなりません。 詳しい情報については「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」及び「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 +パブリックなアクションは、READMEファイル中で期待する環境変数を指定できます。 環境変数にシークレットを設定しようとしている場合、シークレットは`secrets`コンテキストを使って設定しなければなりません。 詳しい情報については「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」及び「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 #### サンプル @@ -812,7 +825,7 @@ steps: ### `jobs..strategy` -strategy (戦略) によって、ジョブのビルドマトリクスが作成されます。 You can define different variations to run each job in. +strategy (戦略) によって、ジョブのビルドマトリクスが作成されます。 それぞれのジョブを実行する様々なバリエーションを定義できます。 ### `jobs..strategy.matrix` @@ -820,7 +833,7 @@ strategy (戦略) によって、ジョブのビルドマトリクスが作成 {% data reusables.github-actions.usage-matrix-limits %} -`matrix`内で定義した各オプションは、キーと値を持ちます。 定義したキーは`matrix`コンテキスト中のプロパティとなり、ワークフローファイルの他のエリア内のプロパティを参照できます。 たとえば、オペレーティングシステムの配列を含む`os`というキーを定義したなら、`matrix.os`プロパティを`runs-on`キーワードの値として使い、それぞれのオペレーティングシステムに対するジョブを作成できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 +`matrix`内で定義した各オプションは、キーと値を持ちます。 定義したキーは`matrix`コンテキスト中の属性となり、ワークフローファイルの他のエリア内のプロパティを参照できます。 たとえば、オペレーティングシステムの配列を含む`os`というキーを定義したなら、`matrix.os`属性を`runs-on`キーワードの値として使い、それぞれのオペレーティングシステムに対するジョブを作成できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 `matrix`を定義する順序は意味を持ちます。 最初に定義したオプションは、ワークフロー中で最初に実行されるジョブになります。 @@ -828,7 +841,7 @@ strategy (戦略) によって、ジョブのビルドマトリクスが作成 設定オプションに配列を指定すると、マトリクスを指定できます。 たとえばランナーがNode.jsのバージョン6、8、10,をサポートしている場合、これらのバージョンの配列を`matrix`で指定できます。 -この例では、`node`キーにNode.jsの3つのバージョンの配列を設定することによって、3つのジョブのマトリクスを作成します。 このマトリックスを使用するために、この例では`matrix.node`コンテキストプロパティを`setup-node`アクションの入力パラメータである`node-version`に設定しています。 その結果、3 つのジョブが実行され、それぞれが異なるバージョンのNode.js を使用します。 +この例では、`node`キーにNode.jsの3つのバージョンの配列を設定することによって、3つのジョブのマトリクスを作成します。 このマトリックスを使用するために、この例では`matrix.node`コンテキスト属性を`setup-node`アクションの入力パラメータである`node-version`に設定しています。 その結果、3 つのジョブが実行され、それぞれが異なるバージョンのNode.js を使用します。 {% raw %} ```yaml @@ -933,9 +946,9 @@ strategy: {% endnote %} -##### Using environment variables in a matrix +##### マトリックスで環境変数を使用する -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. +それぞれのテストの組み合わせに、`include`キーを使ってカスタムの環境変数を追加できます。 そして、後のステップでそのカスタムの環境変数を参照できます。 {% data reusables.github-actions.matrix-variable-example %} @@ -1009,7 +1022,7 @@ jobs: ### `jobs..container.image` -アクションを実行するコンテナとして使用するDockerイメージ。 The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name. +アクションを実行するコンテナとして使用するDockerイメージ。 この値には、Docker Hubのイメージ名もしくは{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}パブリックの{% endif %}レジストリ名が指定できます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} @@ -1093,7 +1106,7 @@ services: ### `jobs..services..image` -アクションを実行するサービスコンテナとして使用するDockerイメージ。 The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name. +アクションを実行するサービスコンテナとして使用するDockerイメージ。 この値には、Docker Hubのイメージ名もしくは{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}パブリックの{% endif %}レジストリ名が指定できます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} @@ -1159,7 +1172,7 @@ volumes: - `**`ゼロ個以上の任意のキャラクタにマッチします。 - `?`: ゼロ個もしくは1個のキャラクタにマッチします。 たとえば`Octoc?t`は`Octocat`にマッチします。 - `+`: 直前の文字の 1 つ以上に一致します。 -- `[]` 括弧内にリストされた、あるいは範囲に含まれる1つのキャラクタにマッチします。 範囲に含めることができるのは`a-z`、`A-Z`、`0-9`のみです。 For example, the range`[0-9a-z]` matches any digit or lowercase letter. たとえば`[CB]at`は`Cat`あるいは`Bat`にマッチし、`[1-2]00`は`100`や`200`にマッチします。 +- `[]` 括弧内にリストされた、あるいは範囲に含まれる1つのキャラクタにマッチします。 範囲に含めることができるのは`a-z`、`A-Z`、`0-9`のみです。 たとえば、`[0-9a-z]`という範囲は任意の数字もしくは小文字にマッチします。 たとえば`[CB]at`は`Cat`あるいは`Bat`にマッチし、`[1-2]00`は`100`や`200`にマッチします。 - `!`: パターンの先頭に置くと、肯定のパターンを否定にします。 先頭のキャラクタではない場合は、特別な意味を持ちません。 YAMLにおいては、`*`、`[`、`!`は特別なキャラクタです。 パターンを`*`、`[`、`!`で始める場合、そのパターンをクオートで囲まなければなりません。 @@ -1186,7 +1199,7 @@ YAMLにおいては、`*`、`[`、`!`は特別なキャラクタです。 パタ | `'**'` | すべてのブランチ及びタグ名にマッチします。 これは `branches`あるいは`tags`フィルタを使わない場合のデフォルトの動作です。 | `all/the/branches`

    `every/tag` | | `'*feature'` | `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `mona-feature`

    `feature`

    `ver-10-feature` | | `v2*` | `v2`で始めるブランチ及びタグ名にマッチします。 | `v2`

    `v2.0`

    `v2.9` | -| `v[12].[0-9]+.[0-9]+` | メジャーバージョンが1もしくは2のすべてのセマンティックバージョニングタグにマッチします。 | `v1.10.1`

    `v2.0.0` | +| `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` | #### ファイルパスにマッチするパターン diff --git a/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md index 1a2275e95e..26bed59473 100644 --- a/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md @@ -1,27 +1,27 @@ --- -title: About identity and access management for your enterprise -shortTitle: About identity and access management -intro: 'You can use {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}''s built-in authentication, or choose between CAS, LDAP, or SAML{% else %}SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM){% endif %} to centrally manage access {% if currentVersion == "free-pro-team@latest" %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}to {% data variables.product.product_location %}{% endif %}.' +title: Enterprise のアイデンティティおよびアクセス管理について +shortTitle: アイデンティティとアクセス管理について +intro: '{% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} のビルトイン認証を使用するか、CAS、LDAP、または SAML{% else %}SAML シングルサインオン (SSO) と System for Cross-domain Identity Management (SCIM){% endif %} のいずれかを選択して、{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} から {% data variables.product.product_location %} で Enterprise が所有する Organization へのアクセスを一元管理できます{% endif %}。' product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About identity and access management for your enterprise +### Enterprise のアイデンティティおよびアクセス管理について {% if currentVersion == "github-ae@latest" %} {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -After you configure the application for {% data variables.product.product_name %} on your IdP, you can grant access to {% data variables.product.product_location %} by assigning the application to users on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +IdP で {% data variables.product.product_name %} のアプリケーションを設定した後、IdP のユーザにアプリケーションを割り当てることで、{% data variables.product.product_location %} へのアクセスを許可できます。 {% data variables.product.product_name %} の SAML SSO の詳細については、「[Enterprise 向けの SAML シングルサインオンを設定する](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %}詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。 -To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." +自分の固有の IdP を使用して {% data variables.product.product_location %} の認証とユーザプロビジョニングの両方を設定する方法については、「[アイデンティティプロバイダを使用して認証とプロビジョニングを設定する](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)」を参照してください。 {% endif %} ### 参考リンク -- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website -- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website +- OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) +- IETF Web サイトの [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) diff --git a/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md b/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md index 4c5bfae5dd..e45e168679 100644 --- a/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md +++ b/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: {% data variables.product.product_location %}のユーザアカウントは、認証方式を変更しても保存され、ユーザはユーザ名が変更されない限り、同じアカウントにログインし続けることができます。 -新しい認証方式でユーザ名が変更される場合、新しいアカウントが作成されます。 As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). +新しい認証方式でユーザ名が変更される場合、新しいアカウントが作成されます。 管理者は、サイトアドミン設定または[ユーザ管理 API](/rest/reference/enterprise-admin#update-the-username-for-a-user) を使用してユーザ名を変更できます。 他に考慮しなければならない問題には以下があります。 diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 4f3049902c..600154351c 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -1,41 +1,41 @@ --- -title: Configuring authentication and provisioning for your enterprise using Azure AD -shortTitle: Configuring with Azure AD -intro: You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}. -permissions: Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}. +title: Azure AD を使用して Enterprise の認証とプロビジョニングを設定する +shortTitle: Azure AD を使用しての設定 +intro: Azure Active Directory (Azure AD) のテナントをアイデンティティプロバイダ (IdP) として使用して、{% data variables.product.product_location %} の認証とユーザプロビジョニングを一元管理できます。 +permissions: Enterprise のオーナーは、{% data variables.product.product_name %} で Enterprise の認証とプロビジョニングを設定できます。 product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About authentication and user provisioning with Azure AD +### Azure AD を使用した認証とユーザプロビジョニングについて -Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs. +Azure Active Directory (Azure AD) は、ユーザアカウントと Web アプリケーションへのアクセスを一元管理できる Microsoft のサービスです。 詳しい情報については、Microsoft Docs の「[Azure Active Directory とは](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)」を参照してください。 -To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access with SCIM. This configuration allows you to assign or unassign the {% data variables.product.prodname_ghe_managed %} application for a user account in your Azure AD tenant to automatically create, grant access to, or deactivate a corresponding user account on {% data variables.product.product_name %}. +{% data variables.product.product_name %} のアイデンティティとアクセスを管理するために、Azure AD テナントを認証用の SAML IdP として使用できます。 アカウントを自動的にプロビジョニングし、SCIM でアクセスするように Azure AD を設定することもできます。 この設定により、Azure AD テナントのユーザアカウントに {% data variables.product.prodname_ghe_managed %} アプリケーションを割り当てたり、割り当てを解除したりして、{% data variables.product.product_name %} の対応するユーザアカウントを自動作成、アクセス許可、または非アクティブ化できます。 -For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." +{% data variables.product.product_location %} での Enterprise のアイデンティティとアクセスの管理の詳細については、「[Enterprise のアイデンティティとアクセスを管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise)」を参照してください。 ### 必要な環境 -To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs. +Azure AD を使用して {% data variables.product.product_name %} の認証とユーザプロビジョニングを設定するには、Azure AD アカウントとテナントが必要です。 詳しい情報については、「[Azure AD Web サイト](https://azure.microsoft.com/free/active-directory)」および Microsoft Docs の「[クイックスタート: Azure Active Directory テナントを作成する](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)」を参照してください。 -{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs. +{% data reusables.saml.assert-the-administrator-attribute %} Azure AD からの SAML 要求に `administrator` 属性を含める方法について詳しくは、Microsoft Docs の「[方法: Enterprise アプリケーション向けに SAML トークンで発行された要求をカスタマイズする](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization)」を参照してください。 {% data reusables.saml.create-a-machine-user %} -### Configuring authentication and user provisioning with Azure AD +### Azure AD を使用して認証とユーザプロビジョニングを設定する {% if currentVersion == "github-ae@latest" %} -1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. +1. Azure AD で、{% data variables.product.ae_azure_ad_app_link %} をテナントに追加し、シングルサインオンを設定します。 詳しい情報については、Microsoft Docs の「[チュートリアル: Azure Active Directory シングルサインオン (SSO) と {% data variables.product.prodname_ghe_managed %} の統合](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial)」を参照してください。 -1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. +1. {% data variables.product.prodname_ghe_managed %} に、Azure AD テナントの詳細を入力します。 - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} - - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)." + - 別の IdP を使用して {% data variables.product.product_location %} の SAML SSO を既に設定していて、代わりに Azure AD を使用する場合は、設定を編集できます。 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)」を参照してください。 -1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)." +1. {% data variables.product.product_name %} でユーザプロビジョニングを有効化し、Azure AD でユーザプロビジョニングを設定します。 詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md index ef320ac2ce..1d8ff7c0b9 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md +++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider.md @@ -1,6 +1,6 @@ --- -title: Configuring authentication and provisioning with your identity provider -intro: You can use an identity provider (IdP) that supports both SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to configure authentication and user provisioning for {% data variables.product.product_location %}. +title: アイデンティティプロバイダで認証とプロビジョニングを設定する +intro: SAML シングルサインオン (SSO) と System for Cross-domain Identity Management (SCIM) の両方をサポートするアイデンティティプロバイダ (IdP) を使用して、{% data variables.product.product_location %} の認証とユーザプロビジョニングを設定できます。 mapTopic: true versions: github-ae: '*' diff --git a/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md index 321824111f..d1347c7ca7 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,9 +1,9 @@ --- -title: Configuring SAML single sign-on for your enterprise -shortTitle: Configuring SAML SSO -intro: You can configure SAML single sign-on (SSO) for your enterprise, which allows you to centrally control authentication for {% data variables.product.product_location %} using your identity provider (IdP). +title: Enterprise 向けの SAML シングルサインオンを設定する +shortTitle: SAML SSO の設定 +intro: Enterprise の SAML シングルサインオン (SSO) を設定できます。これにより、アイデンティティプロバイダ (IdP) を使用して {% data variables.product.product_location %} の認証を一元的に制御できます。 product: '{% data reusables.gated-features.saml-sso %}' -permissions: Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}. +permissions: Enterprise オーナーは、{% data variables.product.product_name %} で Enterprise の SAML SSO を設定できます。 versions: github-ae: '*' --- @@ -12,51 +12,51 @@ versions: {% if currentVersion == "github-ae@latest" %} -SAML SSO allows you to centrally control and secure access to {% data variables.product.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user. +SAML SSO を使用すると、SAML IdP から {% data variables.product.product_location %} へのアクセスを一元的に制御しアクセスをセキュアにできます。 認証されていないユーザがブラウザで {% data variables.product.product_location %} にアクセスすると、{% data variables.product.product_name %} はユーザを認証するために SAML IdP にリダイレクトします。 ユーザが IdP のアカウントで正常に認証されると、IdP はユーザを {% data variables.product.product_location %} にリダイレクトします。 {% data variables.product.product_name %} は、IdP からのレスポンスを検証してから、ユーザにアクセスを許可します。 -After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.product.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP. +ユーザーが IdP で正常に認証されると、{% data variables.product.product_location %} に対するユーザの SAML セッションはブラウザで 24 時間アクティブになります。 24 時間後、ユーザは IdP で再度認証を行う必要があります。 {% data reusables.saml.assert-the-administrator-attribute %} -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %}詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。 {% endif %} -### Supported identity providers +### サポートされているアイデンティティプロバイダ -{% data variables.product.product_name %} supports SAML SSO with IdPs that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. +{% data variables.product.product_name %} は、SAML2.0 標準を実装し IdP を使用した SAML SSO をサポートします。 詳しい情報については、OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) を参照してください。 -{% data variables.product.company_short %} has tested SAML SSO for {% data variables.product.product_name %} with the following IdPs. +{% data variables.product.company_short %} は、次の IdP を使用して {% data variables.product.product_name %} の SAML SSO をテストしました。 {% if currentVersion == "github-ae@latest" %} - Azure AD {% endif %} -### Enabling SAML SSO +### SAML SSO を有効化する {% if currentVersion == "github-ae@latest" %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. +次の IdP は、{% data variables.product.product_name %} の SAML SSO の設定に関するドキュメントを提供しています。 IdP がリストにない場合は、IdP に問い合わせて、{% data variables.product.product_name %} のサポートをご依頼ください。 - | IdP | 詳細情報 | - |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs | + | IdP | 詳細情報 | + |:-------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | Microsoft Docs の「[チュートリアル: Azure Active Directory シングルサインオン (SSO) と {% data variables.product.prodname_ghe_managed %} の統合](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial)」 | -During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. +{% data variables.product.product_name %} の初期化中に、IdP で {% data variables.product.product_name %} を SAML サービスプロバイダ (SP) として設定する必要があります。 {% data variables.product.product_name %} を有効な SP として設定するには、IdP にいくつかの一意の値を入力する必要があります。 -| 値 | Other names | 説明 | サンプル | -|:--------------------------------------- |:----------- |:-------------------------------------------------------------------------- |:------------------------- | -| SP Entity ID | SP URL | Your top-level URL for {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME | -| SP Assertion Consumer Service (ACS) URL | Reply URL | URL where IdP sends SAML responses | https://YOUR-GITHUB-AE-HOSTNAME/saml/consume | -| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO | https://YOUR-GITHUB-AE-HOSTNAME/sso | +| 値 | 別名 | 説明 | サンプル | +|:------------------------------ |:------ |:--------------------------------------------------------------- |:------------------------- | +| SP エンティティ ID | SP URL | {% data variables.product.prodname_ghe_managed %} の最上位にある URL | https://YOUR-GITHUB-AE-HOSTNAME | +| SP アサーションコンシューマーサービス (ACS) URL | 返信 URL | IdP が SAML レスポンスを送信する URL | https://YOUR-GITHUB-AE-HOSTNAME/saml/consume | +| SP シングルサインオン (SSO) URL | | IdP が SSO を開始する URL | https://YOUR-GITHUB-AE-HOSTNAME/sso | {% endif %} -### Editing the SAML SSO configuration +### SAML SSO 設定を編集する -If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.product.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate. +IdP の詳細が変更された場合は、{% data variables.product.product_location %} の SAML SSO 設定を編集する必要があります。 たとえば、IdP の証明書の有効期限が切れそうな場合、公開証明書の値を編集できます。 {% if currentVersion == "github-ae@latest" %} @@ -69,23 +69,23 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", type the new details for your IdP. ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png) -1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method. ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) +1. [SAML single sign-on] で、IdP の新しい詳細を入力します。 ![Enterprise の SAML SSO 設定の IdP 詳細を含むテキスト入力フィールド](/assets/images/help/saml/ae-edit-idp-details.png) +1. 必要に応じて、{% octicon "pencil" aria-label="The edit icon" %} をクリックして、新しい署名またはダイジェスト方式を設定します。 ![署名とダイジェスト方法を変更するための編集アイコン](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) - - Use the drop-down menus and choose the new signature or digest method. ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) -1. To ensure that the information you've entered is correct, click **Test SAML configuration**. !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) -1. [**Save**] をクリックします。 !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png) -1. Optionally, to automatically provision and deprovision user accounts for {% data variables.product.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." + - ドロップダウンメニューを使用して、新しい署名またはダイジェスト方法を選択します。 ![新しい署名またはダイジェスト方法を選択するためのドロップダウンメニュー](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. [**Test SAML configuration**] をクリックして、入力した情報が正しいことを確認します。 !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. [**Save**] をクリックします。 ![SAML SSO 設定の [Save] ボタン](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. 必要に応じて、{% data variables.product.product_location %} のユーザアカウントを自動的にプロビジョニングおよびプロビジョニング解除するには、SCIM を使用してユーザプロビジョニングを再設定します。 詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。 {% endif %} -### Disabling SAML SSO +### SAML SSO を無効化する {% if currentVersion == "github-ae@latest" %} {% warning %} -**Warning**: If you disable SAML SSO for {% data variables.product.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.product.product_location %}. SAML SSO sessions on {% data variables.product.product_location %} end after 24 hours. +**Warning**: {% data variables.product.product_location %} の SAML SSO を無効にすると、既存の SAML SSO セッションのないユーザは {% data variables.product.product_location %} にサインインできなくなります。 {% data variables.product.product_location %} での SAML SSO セッションは、24 時間後に終了します。 {% endwarning %} @@ -98,7 +98,7 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", unselect **Enable SAML authentication**. ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png) -1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**. !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png) +1. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択解除します。 ![[Enable SAML authentication] チェックボックス](/assets/images/help/saml/ae-saml-disabled.png) +1. SAML SSO を無効にし、初期化中に作成した組み込みユーザアカウントでサインインする必要がある場合は、[**Save**] をクリックします。 ![SAML SSO 設定の [Save] ボタン](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} diff --git a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index ab43453330..213050f8eb 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -1,30 +1,30 @@ --- -title: Configuring user provisioning for your enterprise -shortTitle: Configuring user provisioning -intro: You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.product.product_location %} when you assign the application for {% data variables.product.product_location %} to a user on your identity provider (IdP). -permissions: Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}. +title: Enterprise 向けのユーザプロビジョニングを設定する +shortTitle: ユーザプロビジョニングの設定 +intro: System for Cross-domain Identity Management (SCIM) のシステムを設定できます。これにより、{% data variables.product.product_location %} のアプリケーションをアイデンティティプロバイダ (IdP) 上のユーザに割り当てると、{% data variables.product.product_location %} のユーザアカウントが自動的にプロビジョニングされます。 +permissions: Enterprise オーナーは、{% data variables.product.product_name %} で Enterprise のユーザプロビジョニングを設定できます。 product: '{% data reusables.gated-features.saml-sso %}' versions: github-ae: '*' --- -### About user provisioning for your enterprise +### Enterprise 向けのユーザプロビジョニングについて -{% data reusables.saml.ae-uses-saml-sso %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +{% data reusables.saml.ae-uses-saml-sso %}詳しい情報については、「[Enterprise 向けの SAML シングルサインオンを設定する](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 -{% data reusables.scim.after-you-configure-saml %} For more information about SCIM, see [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website. +{% data reusables.scim.after-you-configure-saml %} SCIM の詳細については、IETF Web サイトの「[System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644)」を参照してください。 {% if currentVersion == "github-ae@latest" %} -Configuring provisioning allows your IdP to communicate with {% data variables.product.product_location %} when you assign or unassign the application for {% data variables.product.product_name %} to a user on your IdP. When you assign the application, your IdP will prompt {% data variables.product.product_location %} to create an account and send an onboarding email to the user. When you unassign the application, your IdP will communicate with {% data variables.product.product_name %} to invalidate any SAML sessions and disable the member's account. +プロビジョニングを設定すると、{% data variables.product.product_name %} のアプリケーションを IdP のユーザに割り当てたり、割り当て解除したりするときに、IdP が {% data variables.product.product_location %} と通信できるようになります。 アプリケーションを割り当てると、IdP は {% data variables.product.product_location %} にアカウントを作成し、オンボーディングメールをユーザに送信するように求めます。 アプリケーションの割り当てを解除すると、IdP は {% data variables.product.product_name %} と通信して、SAML セッションを無効にし、メンバーのアカウントを無効にします。 -To configure provisioning for your enterprise, you must enable provisioning on {% data variables.product.product_name %}, then install and configure a provisioning application on your IdP. +Enterprise のプロビジョニングを設定するには、{% data variables.product.product_name %} でプロビジョニングを有効にしてから、IdP にプロビジョニングアプリケーションをインストールして設定する必要があります。 -The provisioning application on your IdP communicates with {% data variables.product.product_name %} via our SCIM API for enterprises. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#scim)" in the {% data variables.product.prodname_dotcom %} REST API documentation. +IdP のプロビジョニングアプリケーションは、Enterprise 向けの SCIM API を介して {% data variables.product.product_name %} と通信します。 詳しい情報については、{% data variables.product.prodname_dotcom %} REST API ドキュメントの「[GitHub Enterprise の管理](/rest/reference/enterprise-admin#scim)」を参照してください。 {% endif %} -### Supported identity providers +### サポートされているアイデンティティプロバイダ {% data reusables.scim.supported-idps %} @@ -32,49 +32,49 @@ The provisioning application on your IdP communicates with {% data variables.pro {% if currentVersion == "github-ae@latest" %} -To automatically provision and deprovision access to {% data variables.product.product_location %} from your IdP, you must first configure SAML SSO when you initialize {% data variables.product.product_name %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." +IdP から {% data variables.product.product_location %} へのアクセスを自動的にプロビジョニングおよびプロビジョニング解除するには、{% data variables.product.product_name %} を初期化するときに最初に SAML SSO を設定する必要があります。 For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." -You must have administrative access on your IdP to configure the application for user provisioning for {% data variables.product.product_name %}. +{% data variables.product.product_name %} のユーザプロビジョニング用にアプリケーションを設定するには、IdP の管理アクセス権が必要です。 {% endif %} -### Enabling user provisioning for your enterprise +### Enterprise 向けのユーザプロビジョニングを有効化する {% if currentVersion == "github-ae@latest" %} -1. While signed into +1. Enterprise オーナーとして -{% data variables.product.product_location %} as an enterprise owner, create a personal access token with **admin:enterprise** scope. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 +{% data variables.product.product_location %} にサインインしているときに、**admin:enterprise** スコープで個人アクセストークンを作成します。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 {% note %} 設定ファイルでクエリスイートを指定すると、{% data variables.product.prodname_codeql %} 分析エンジンは、デフォルトのクエリセットに加えて、スイートに含まれるクエリを実行します。 - - To create the personal access token, we recommend using the account for the first enterprise owner that you created during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." - - You'll need this personal access token to configure the application for SCIM on your IdP. Store the token securely in a password manager until you need the token again later in these instructions. + - 個人アクセストークンを作成するには、初期化中に作成した最初の Enterprise オーナーのアカウントを使用することをお勧めします。 For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." + - IdP で SCIM 用にアプリケーションを設定するには、この個人アクセストークンが必要です。 手順の後半でトークンが再び必要になるまで、トークンをパスワードマネージャーに安全に保管してください。 {% endnote %} {% warning %} - **Warning**: If the user account for the enterprise owner who creates the personal access token is deactivated or deprovisioned, your IdP will no longer provision and deprovision user accounts for your enterprise automatically. Another enterprise owner must create a new personal access token and reconfigure provisioning on the IdP. + **警告**: 個人アクセストークンを作成する Enterprise オーナーのユーザーアカウントが非アクティブ化またはプロビジョニング解除された場合、IdP は Enterprise のユーザアカウントを自動的にプロビジョニングおよびプロビジョニング解除しません。 別の Enterprise オーナーは、新しい個人アクセストークンを作成し、IdP でプロビジョニングを再設定する必要があります。 {% endwarning %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**. ![Checkbox for "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) -1. [**Save**] をクリックします。 ![Save button under "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-scim-save.png) -1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. +1. [SCIM User Provisioning] で、[**Require SCIM user provisioning**] を選択します。 ![Enterprise セキュリティ設定内の [Require SCIM user provisioning] のチェックボックス](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. [**Save**] をクリックします。 ![Enterprise セキュリティ設定内の [Require SCIM user provisioning] の下にある [Save] ボタン](/assets/images/help/enterprises/settings-scim-save.png) +1. IdP の {% data variables.product.product_name %} のアプリケーションでユーザプロビジョニングを設定します。 - The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. + 次の IdP では、{% data variables.product.product_name %} のプロビジョニングの設定に関するドキュメントを提供しています。 IdP がリストにない場合は、IdP に問い合わせて、{% data variables.product.product_name %} のサポートをご依頼ください。 - | IdP | 詳細情報 | - |:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs | + | IdP | 詳細情報 | + |:-------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Azure AD | Microsoft Docs の「[チュートリアル: 自動ユーザプロビジョニング用に {% data variables.product.prodname_ghe_managed %} を設定する](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial)」 | - The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}. + IdP のアプリケーションでは、{% data variables.product.product_location %} でユーザアカウントをプロビジョニングまたはプロビジョニング解除するために 2 つの値が必要です。 - | 値 | Other names | 説明 | サンプル | - |:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- | - | URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.prodname_ghe_managed %} | https://YOUR-GITHUB-AE-HOSTNAME/scim/v2 | - | Shared secret | Personal access token, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | Personal access token you created in step 1 | + | 値 | 別名 | 説明 | サンプル | + |:-------- |:--------------------- |:--------------------------------------------------------------------------------------------- |:------------------------- | + | URL | テナント URL | {% data variables.product.prodname_ghe_managed %} にある Enterprise の SCIM プロビジョニング API への URL | https://YOUR-GITHUB-AE-HOSTNAME/scim/v2 | + | 共有シークレット | 個人アクセストークン、シークレットトークン | Enterprise オーナーに代わってプロビジョニングタスクを実行するための IdP 上のアプリケーションのトークン | ステップ 1 で作成した個人アクセストークン | {% endif %} diff --git a/translations/ja-JP/content/admin/authentication/index.md b/translations/ja-JP/content/admin/authentication/index.md index 68e82218dc..0ff44f65e7 100644 --- a/translations/ja-JP/content/admin/authentication/index.md +++ b/translations/ja-JP/content/admin/authentication/index.md @@ -1,6 +1,6 @@ --- title: 認証 -intro: You can configure how users sign into {% data variables.product.product_name %}. +intro: ユーザが {% data variables.product.product_name %} にサインインする方法を設定できます。 redirect_from: - /enterprise/admin/authentication versions: diff --git a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md index 9b4b3f0a0a..0556276a7a 100644 --- a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Managing identity and access for your enterprise -shortTitle: Managing identity and access -intro: You can centrally manage accounts and access to {% data variables.product.product_location %}. +title: Enterprise の ID とアクセスを管理する +shortTitle: アイデンティティとアクセスの管理 +intro: アカウントと {% data variables.product.product_location %} のアクセスは一元管理できます。 mapTopic: true versions: github-ae: '*' diff --git a/translations/ja-JP/content/admin/authentication/using-cas.md b/translations/ja-JP/content/admin/authentication/using-cas.md index c4fa1a54ef..2d445cb900 100644 --- a/translations/ja-JP/content/admin/authentication/using-cas.md +++ b/translations/ja-JP/content/admin/authentication/using-cas.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/articles/about-cas-authentication/ - /enterprise/admin/user-management/using-cas - /enterprise/admin/authentication/using-cas -intro: 'CAS は、複数の Web アプリケーションのためのシングルサインオン (SSO) プロトコルです。 CAS ユーザアカウントは、ユーザがサインインするまで、{% if currentVersion ver_gt "enterprise-server@2.16" %}ユーザライセンス{% else %}シート{% endif %}を消費しません。' +intro: 'CAS は、複数の Web アプリケーションのためのシングルサインオン (SSO) プロトコルです。 CAS ユーザアカウントは、ユーザがサインインするまで、{% if currentVersion ver_gt "enterprise-server@2.16" %}ユーザライセンス{% else %}シート{% endif %}の使用を開始しません。' versions: enterprise-server: '*' --- diff --git a/translations/ja-JP/content/admin/configuration/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/command-line-utilities.md index 362f26c8eb..20b76d9c55 100644 --- a/translations/ja-JP/content/admin/configuration/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` `cluster.conf`で有効なUUIDを検索できます。 -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -544,8 +544,8 @@ ghe-dpages status ``` クラスタノードの退避に先立って{% data variables.product.prodname_pages %}ストレージサービスを退避するには、以下のようにします。 -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -570,16 +570,16 @@ ghe-spokes route クラスタノード上のストレージサービスを退避するには、以下のようにします。 -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage このユーティリティを使用すると、クラスタノードからの待避の前にストレージサービスをすべて待避させることができます。 -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/ja-JP/content/admin/configuration/configuring-applications.md b/translations/ja-JP/content/admin/configuration/configuring-applications.md index 013e836f03..dee2a34be9 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-applications.md +++ b/translations/ja-JP/content/admin/configuration/configuring-applications.md @@ -15,7 +15,7 @@ versions: {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} 3. 左のサイドバーで、**Applications（アプリケーション）** をクリックしてください。 ![[Settings] サイドバーでの [Applications] タブ](/assets/images/enterprise/management-console/sidebar-applications.png) -4. [Avatar image cache time (seconds)] で、 +4. [Avatar image cache time (seconds)] でアバター画像をキャッシュする秒数を入力します。 {% data variables.product.product_location %} がアバター画像をキャッシュする秒数を入力します。 ![アバター画像キャッシュのフォームフィールド](/assets/images/enterprise/management-console/add-image-caching-value-field.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md index 831bacf9e2..ec4144c03b 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ For more information about contacting support, see "[About {% data variables.con - [** Authentication（認証）**] ドロップダウンでは、SMTP サーバが利用する暗号化の種類を選択してください。 - [**No-reply email address（No-replyメールアドレス）**] フィールドには、すべての通知メールの From および To フィールドに使うメールアドレスを入力してください。 - {% note %} - - **注釈:** リポジトリの [**Services**] メール webhook で [**Send from author**] チェックボックスを選択した場合、そのリポジトリのアウトバウンドメールは no-reply メールアドレスではなく、作者から送信されます。 For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)." - - {% endnote %} - 6. no-replyメールアドレスへの着信メールをすべて破棄したい場合には、**Discard email addressed to the no-reply email address（no-replyメールアドレスへのメールの破棄）**を選択してください。 ![no-reply メールアドレス宛のメールを廃棄するチェックボックス](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. [**Support（サポート）**] の下で、ユーザに追加のサポートを提供するリンクの種類を選択してください。 - **Email（メール）：** 内部的なメールアドレス。 @@ -155,7 +149,7 @@ Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asm #### DNS設定の検証 -インバウンドのメールを適切に処理するには、適切にAレコード（あるいはCNAME）と共にMXレコードを設定しなければなりません。 詳細は「[着信メールを許可するよう DNS およびファイアウォールを設定する](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)」を参照してください。 +インバウンドのメールを適切に処理するには、適切にAレコード（あるいはCNAME）と共にMXレコードを設定しなければなりません。 For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." #### ファイアウォールあるいはAWSセキュリティグループの設定のチェック diff --git a/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md b/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md index b78cc042b7..a09736d556 100644 --- a/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md +++ b/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md @@ -18,7 +18,7 @@ Geo-replicationがスムーズに動作するためには、[Amazon's Route 53 ### 制限事項 -レプリカへの書き込みリクエストには、データをプライマリとすべてのレプリカへ送信することが必要です。 これは、すべての書き込みのパフォーマンスが最も遅いレプリカによって制限されることを意味しますが、新しいジオレプリカは、プライマリからではなく、既存の同じ場所に配置された Geo レプリカからデータの大部分をシードできます。 Geo-replication は、{% data variables.product.prodname_ghe_server %} インスタンスに容量を追加したり、不十分な CPU やメモリリソースに関連するパフォーマンスの問題を解決したりしません。 プライマリのアプライアンスがオフラインである場合、アクティブなレプリカはいかなる読み込みや書き込みのリクエストも処理できません。 +レプリカへの書き込みリクエストには、データをプライマリとすべてのレプリカへ送信することが必要です。 これは、すべての書き込みのパフォーマンスが最も遅いレプリカによって制限されることを意味しますが、新しいGeo-replication レプリカは、プライマリからではなく、既存の同じ場所に配置された Geo-replication レプリカからデータの大部分をシードできます。 Geo-replication は、{% data variables.product.prodname_ghe_server %} インスタンスに容量を追加したり、不十分な CPU やメモリリソースに関連するパフォーマンスの問題を解決したりしません。 プライマリのアプライアンスがオフラインである場合、アクティブなレプリカはいかなる読み込みや書き込みのリクエストも処理できません。 ### Geo-replication設定のモニタリング diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md b/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md index dc84d54679..694e22ebd6 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md @@ -11,7 +11,7 @@ versions: ### 外部 `collectd` サーバーを設置 -{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 Your `collectd` server must be running `collectd` version 5.x or higher. +{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 `collectd` サーバは、`collectd` 5.x 以降のバージョンを実行している必要があります。 1. `collectd` サーバにログインする 2. `collectd` を作成、または編集することで、ネットワークプラグインをロードし、適切な値をサーバとポートのディレクティブに追加する。 たいていのディストリビューションでは、これは `/etc/collectd/collectd.conf` にあります。 diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index 9526a3e73f..93aaafabc2 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -1,6 +1,6 @@ --- title: Configuring high availability replication for a cluster -intro: '{% data variables.product.prodname_ghe_server %} クラスタ全体のパッシブレプリカを別の場所に設定することで、クラスタを冗長ノードにフェイルオーバーできるようにすることができます。' +intro: '{% data variables.product.prodname_ghe_server %} クラスタ全体のパッシブレプリカを別の場所に設定することで、クラスタを冗長ノードにフェイルオーバーできるようにします。' miniTocMaxHeadingLevel: 4 redirect_from: - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster @@ -10,7 +10,7 @@ versions: ### About high availability replication for clusters -High Availability を実現するために、{% data variables.product.prodname_ghe_server %} のクラスタデプロイメントを設定できます。この場合、パッシブノードの同一のセットがアクティブクラスタ内のノードと同期されます。 If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests without data loss. +High Availability を実現するために、{% data variables.product.prodname_ghe_server %} のクラスタデプロイメントを設定できます。この場合、パッシブノードの同一のセットがアクティブクラスタ内のノードと同期されます。 If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage. In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests. diff --git a/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md index 14a02b7727..9de156a4db 100644 --- a/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ versions: ghe-spokes evac-status ``` {% data variables.product.prodname_pages %}: + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} ストレージ: ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ versions: 3. コピーが完了したら、ストレージサービスを待避させます。 実行するコマンドは次のいずれかです。 Git: + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} {% data variables.product.prodname_pages %}: + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} ストレージに対して、ノードをオフラインにします。 + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} 次に、待避を実行します。 + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md b/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md index 844558b4ba..f7a5c35a3d 100644 --- a/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ versions: 設定した最初のクラスタノードを、`mysql-server` および `mysql-master`で MySQL のプライマリとして指定してください。 -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index 46d774cada..b9c9d3138a 100644 --- a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -30,12 +30,12 @@ versions: 5. レプリカの IP アドレスを指すように DNS レコードを更新します。 TTL 期間が経過すると、トラフィックはレプリカに転送されます。 ロードバランサを使用している場合は、トラフィックがレプリカに送信されるように設定されていることを確認します。 6. 通常の操作が再開できることをユーザーに通知します。 7. 必要に応じて、新しいプライマリから既存のアプライアンスや以前のプライマリへのレプリケーションをセットアップします。 詳細は「[High Availability の設定について](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)」を参照してください。 -8. Appliances you do not intend to setup replication to that were part of the high availability configuration prior the failover, need to be removed from the high availability configuration by UUID. - - On the former appliances, get their UUID via `cat /data/user/common/uuid`. +8. フェイルオーバー前に High Availability 設定の一部であり、レプリケーションをセットアップする予定のないアプライアンスは、UUID による High Availability 設定から削除する必要があります。 + - 以前のアプライアンスでは、`cat /data/user/common/uuid` を介して UUID を取得します。 ```shell $ cat /data/user/common/uuid ``` - - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step. + - 新しいプライマリで、`ghe-repl-teardown` を使用して UUID を削除します。 *`UUID`* を前のステップで取得した UUID に置き換えてください。 ```shell $ ghe-repl-teardown -u UUID ``` diff --git a/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md index 3c2dc664a2..d20b38748b 100644 --- a/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -35,7 +35,7 @@ versions: {% if currentVersion ver_gt "enterprise-server@2.22" %} {% note %} - **Note:** If you have {% data variables.product.prodname_actions %} enabled, you should decommission the former replica server or update its {% data variables.product.prodname_actions %} configuration to use different external storage. For more information, see "[High availability for {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)." + **注釈:** {% data variables.product.prodname_actions %} を有効化している場合は、以前のレプリカサーバーを使用停止するか、その {% data variables.product.prodname_actions %} 設定を更新して別の外部ストレージを使用する必要があります。 詳しい情報については、「[{% data variables.product.prodname_actions %} の High Availability 設定](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)」を参照してください。 {% endnote %} {% endif %} diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md b/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md index 6b16e70bc6..53a467ede6 100644 --- a/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md +++ b/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md @@ -29,7 +29,7 @@ versions: ### 要件 -- アップグレードは、**最大でも**2リリース前のフィーチャリリースから行わなければなりません。 たとえば {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }} にアップグレードするためには、{% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} あるいは {{ enterpriseServerReleases.supported[2] }} でなければなりません。 +- アップグレードは、**最大でも**2リリース前のフィーチャリリースから行わなければなりません。 たとえば {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }} にアップグレードするためには、{% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} あるいは {{ enterpriseServerReleases.supported[2] }} となっていなければなりません。 - {% data reusables.enterprise_installation.hotpatching-explanation %} - ホットパッチは、影響するサービス（カーネル、MySQL、Elasticsearchなど）がVMの再起動やサービスの再起動を必要とするなら、ダウンタイムが必要になります。 リブートや再起動が必要になったときには通知されます。 リブートや再起動は後で完了させることができます。 - ホットパッチでアップグレードをする場合、アップグレードの完了までに特定のサービスの複数バージョンがインストールされることから、追加のルートストレージが利用できなければなりません。 十分なルートディスクストレージがなければ、事前チェックで通知されます。 diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 0d74965bfe..0076fc95e0 100644 --- a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -222,5 +222,5 @@ High Availability と Geo-replication が設定されたアプライアンスは {% if currentVersion ver_gt "enterprise-server@2.22" %} ### 参考リンク -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」 {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md index b5417575a6..f5e66227aa 100644 --- a/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md @@ -1,6 +1,6 @@ --- title: GitHub Enterprise Supportについて -intro: '{% data variables.contact.github_support %} can help you troubleshoot issues that arise on {% data variables.product.product_name %}.' +intro: '{% data variables.contact.github_support %} は、{% data variables.product.product_name %} で発生した問題のトラブルシューティングに役立ちます。' redirect_from: - /enterprise/admin/enterprise-support/about-github-enterprise-support versions: @@ -16,28 +16,28 @@ versions: ### {% data variables.contact.enterprise_support %} について -{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %}. +{% data variables.product.product_name %} には英語 {% if enterpriseServerVersions contains currentVersion %} と日本語の {% data variables.contact.enterprise_support %} が含まれます{% endif %}。 {% if enterpriseServerVersions contains currentVersion %} -You can contact -{% data variables.contact.enterprise_support %} through {% data variables.contact.contact_enterprise_portal %} for help with: +以下については、 +{% data variables.contact.contact_enterprise_portal %} を通じて {% data variables.contact.enterprise_support %} に連絡できます。 - {% data variables.product.product_name %} のインストールと利用 - 調査対象となっているエラーの原因の特定および検証 {% endif %} -In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.premium_support %}{% else %}support for {% data variables.product.product_name %}{% endif %} offers: +{% data variables.contact.enterprise_support %} から得られるすべてのメリットに加えて、{% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.premium_support %}{% else %} では以下が提供{% data variables.product.product_name %}{% endif %}されます。 - GitHub Enterprise サポートページを通じた書面による 24 時間 365 日のサポート - 24 時間 365 日の電話サポート - - A{% if currentVersion == "github-ae@latest" %}n enhanced{% endif %} Service Level Agreement (SLA) {% if enterpriseServerVersions contains currentVersion %}with guaranteed initial response times{% endif %} + - {% if currentVersion == "github-ae@latest" %}初期レスポンス時間が保証された{% endif %}拡張サービスレベルアグリーメント(SLA) {% if enterpriseServerVersions contains currentVersion %}{% endif %} {% if currentVersion == "github-ae@latest" %} - - An assigned Technical Service Account Manager - - Quarterly support reviews - - Managed Admin services + - 担当のテクニカルサービスアカウントマネージャー + - 四半期ごとのサポートレビュー + - 管理者サービスのマネジメント {% else if enterpriseServerVersions contains currentVersion %} - - Technical account managers + - テクニカルアカウントマネージャー - プレミアムコンテンツへのアクセス - 定期的なヘルスチェック - - Managed Admin hours + - 管理者稼働時間のマネジメント {% endif %} {% data reusables.support.government-response-times-may-vary %} @@ -50,7 +50,7 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo ### {% data variables.contact.enterprise_support %} への連絡 -You can contact {% data variables.contact.enterprise_support %} through {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} 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)." +{% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.contact.ae_azure_portal %}{% endif %} を通じて {% data variables.contact.enterprise_support %} に連絡し、問題を書面でレポートすることができます。 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。 ### 営業時間 @@ -61,7 +61,7 @@ You can contact {% data variables.contact.enterprise_support %} through {% if en {% if enterpriseServerVersions contains currentVersion %} 緊急ではない標準的な問題の場合、英語でのサポートは週末とアメリカの休日をのぞく週 5 日 24 時間提供しています。 （アメリカの祝日は除く） 返信までの標準的な時間は 24 時間です。 -For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 days per week, even during national U.S. （アメリカの祝日は除く） +急を要する問題については、{% else %}{% endif %}米国の祝日を含む、24時間年中無休で対応しています。 （アメリカの祝日は除く） {% data reusables.support.government-response-times-may-vary %} @@ -70,18 +70,18 @@ For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 緊急ではない問題については、日本語でのサポートを月曜日から金曜日、日本時間午前9:00から午後5:00まで提供します。これは日本の国民の祝日を除きます。 緊急の問題については、アメリカの祝日を含む、24時間年中無休で英語でサポートを提供しています。 （アメリカの祝日は除く） -また、 and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."{% endif %} +また、 {% data variables.contact.enterprise_support %} におけるアメリカおよび日本の祝祭日は「[休日のスケジュール](#holiday-schedules)」を参照してください。{% endif %} {% if enterpriseServerVersions contains currentVersion %} ### 休日のスケジュール -緊急の問題については、アメリカおよび日本の祝日を含め、24時間年中無休で英語で対応します。 {% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %} holidays. +急を要する問題については、アメリカおよび日本の祝日を含め、24時間年中無休で英語で対応します。 {% if enterpriseServerVersions contains currentVersion %} と 日本{% endif %} の祝祭日。 #### アメリカ合衆国の祝日 -{% data variables.contact.enterprise_support %} は、以下の米国の祝日を休日としています。 holidays{% if enterpriseServerVersions contains currentVersion %}, although our global support team is available to answer urgent tickets{% endif %}. +{% data variables.contact.enterprise_support %} は、以下の米国の祝日を休日としています。 {% if enterpriseServerVersions contains currentVersion %}、ただし、緊急チケットに対してはグローバルサポートチームが対応可能です{% endif %}。 -| アメリカ合衆国の祝日 祝日 | 対象日付 | +| アメリカ合衆国の祝日 祝日 | 対象となる日付 | | --------------------------- | --------------------------- | | New Year's Day | January 1 | | Martin Luther King, Jr. Day | Third Monday in January | @@ -123,8 +123,7 @@ For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 ### 参考リンク {% if enterpriseServerVersions contains currentVersion %} -- [{% data variables.product.prodname_ghe_server %} に関するよくある質問](https://enterprise.github.com/faq) -- 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)"{% if enterpriseServerVersions contains currentVersion %} -- "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} +- [{% data variables.product.prodname_ghe_server %} ライセンスアグリーメント](https://enterprise.github.com/license)のサポートに関するセクション 10{% endif %} +- 「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」{% if enterpriseServerVersions contains currentVersion %} +- 「[チケットのサブミットの準備](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)」{% endif %} - [チケットのサブミット](/enterprise/admin/guides/enterprise-support/submitting-a-ticket) diff --git a/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md index c696b18904..4147c5909f 100644 --- a/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md +++ b/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md @@ -44,7 +44,7 @@ versions: {% data variables.contact.enterprise_support %} は、以下の米国の祝日を休日としています。 （アメリカの祝日は除く） -| アメリカ合衆国の祝日 祝日 | 対象日付 | +| アメリカ合衆国の祝日 祝日 | 対象となる日付 | | --------------------------- | --------------------------- | | New Year's Day | January 1 | | Martin Luther King, Jr. Day | Third Monday in January | diff --git a/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md index 2e50957422..c2ad4542c3 100644 --- a/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md +++ b/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md @@ -1,6 +1,6 @@ --- title: チケットのサブミットの準備 -intro: 'You can expedite your issue with {% data variables.contact.enterprise_support %} by following these suggestions before you open a support ticket.' +intro: 'サポートチケットを開く前にこれらの推奨事項に従うと、{% data variables.contact.enterprise_support %} で問題解決を迅速に行うことができます。' redirect_from: - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket versions: @@ -11,7 +11,7 @@ versions: チケットをサブミットする前に以下の作業を済ませておいてください。 - {% data variables.contact.github_support %} による問題の追跡、優先順位付け、再現、調査を支援する情報の取得 -- 可能であれば問題を再現し、その手順を共有する用意をしてください。 +- 可能であれば問題を再現し、問題発生の手順を共有できるようにしてください。 - 問題の詳細な説明と期待される結果を提供できるように準備してください。 - 問題に関連するすべてのエラーメッセージをそのままコピーしてください。 - {% data variables.contact.github_support %} との進行中のやりとりがあれば、既存のチケット番号があるかを確認してください。 diff --git a/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md index decd682e30..ee8e11a825 100644 --- a/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md @@ -87,7 +87,7 @@ Web べースの {% data variables.enterprise.management_console %} と外部の #### SSHを使ったSupport Bundleの作成 -You can use these steps to create and share a support bundle if you have SSH access to {% data variables.product.product_location %} and have outbound internet access. +{% data variables.product.product_location %} への SSH アクセスがあり、アウトバウンドインターネットアクセスがある場合は、これらのステップで拡張 Support Bundle を作成および共有できます。 {% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} @@ -104,7 +104,7 @@ You can use these steps to create and share a support bundle if you have SSH acc {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} 3. 左のサイドバーで、** Enterprise licensing（Enterpriseライセンス）**をクリックしてください。 ![[Enterprise account settings] サイトバーの "Enterprise licensing"](/assets/images/help/enterprises/enterprise-licensing-tab.png) -4. [{% data variables.product.prodname_enterprise %} Help] の下にある [**Upload a support bundle**] をクリックします。 ![Support Bundle リンクをアップロードする](/assets/images/enterprise/support/upload-support-bundle.png) +4. [{% data variables.product.prodname_enterprise %} Help] にある [**Upload a support bundle**] をクリックします。 ![Support Bundle リンクをアップロードする](/assets/images/enterprise/support/upload-support-bundle.png) 5. [Select an enterprise account] で、ドロップダウンメニューから Support Bundle に関連付けられているアカウントを選択します。 ![Support Bundle の Enterprise アカウントを選択する](/assets/images/enterprise/support/support-bundle-account.png) 6. [Upload a support bundle for {% data variables.contact.enterprise_support %}] で Support Bundle を選択するには、[**Choose file**] をクリックするか、Support Bundle ファイルを [**Choose file**] にドラッグします。 ![Support Bundle ファイルをアップロードする](/assets/images/enterprise/support/choose-support-bundle-file.png) 7. [**Upload**] をクリックします。 @@ -112,8 +112,8 @@ You can use these steps to create and share a support bundle if you have SSH acc #### SSHを使ったSupport Bundleの直接アップロード 以下の状況であれば、Support Bundleを当社のサーバに直接アップロードできます。 -- You have SSH access to {% data variables.product.product_location %}. -- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.product.product_location %}. +- {% data variables.product.product_location %} への SSH アクセス権がある。 +- TCP ポート 443 を介したアウトバウンド HTTPS 接続が、{% data variables.product.product_location %} から許可されている。 1. バンドルを当社のSupport Bundleサーバにアップロードします。 ```shell @@ -128,7 +128,7 @@ Support Bundleには過去2日分のログが含まれますが、_拡張_Suppor #### SSHを使った拡張Support Bundleの作成 -You can use these steps to create and share an extended support bundle if you have SSH access to {% data variables.product.product_location %} and you have outbound internet access. +{% data variables.product.product_location %} への SSH アクセスがあり、アウトバウンドインターネットアクセスがある場合は、これらのステップで拡張 Support Bundle を作成および共有できます。 1. `ghe-support-bundle`コマンドに`-x`フラグを追加して、SSH経由で拡張Support Bundleをダウンロードしてください。 ```shell @@ -140,8 +140,8 @@ You can use these steps to create and share an extended support bundle if you ha #### SSHを使った拡張Support Bundleの直接アップロード 以下の状況であれば、Support Bundleを当社のサーバに直接アップロードできます。 -- You have SSH access to {% data variables.product.product_location %}. -- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.product.product_location %}. +- {% data variables.product.product_location %} への SSH アクセス権がある。 +- TCP ポート 443 を介したアウトバウンド HTTPS 接続が、{% data variables.product.product_location %} から許可されている。 1. バンドルを当社のSupport Bundleサーバにアップロードします。 ```shell diff --git a/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md b/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md index edbe0ab4e3..9367049fb4 100644 --- a/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md +++ b/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md @@ -1,6 +1,6 @@ --- title: GitHub Support への連絡 -intro: 'Contact {% data variables.contact.enterprise_support %} using the {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.' +intro: '{% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} または {% endif %}GitHub Enterprise サポートページから {% data variables.contact.enterprise_support %} に連絡してください。' redirect_from: - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/ - /enterprise/admin/enterprise-support/reaching-github-support @@ -14,7 +14,7 @@ versions: ### {% data variables.contact.enterprise_support %} への連絡 -{% data variables.contact.enterprise_support %} customers can open a support ticket using the {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} the {% data variables.contact.contact_ae_portal %}{% endif %}. チケットの優先度を {% data variables.product.support_ticket_priority_urgent %}、{% data variables.product.support_ticket_priority_high %}、{% data variables.product.support_ticket_priority_normal %}、または {% data variables.product.support_ticket_priority_low %} としてマークします。 詳しい情報については、「[サポートチケットに優先度を割り当てる](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)」および「[チケットをサブミットする](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)」を参照してください。 +{% data variables.contact.enterprise_support %} のお客様は、{% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} または {% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} the {% data variables.contact.contact_ae_portal %}サポートチケットをオープンできます{% endif %}。 チケットの優先度を {% data variables.product.support_ticket_priority_urgent %}、{% data variables.product.support_ticket_priority_high %}、{% data variables.product.support_ticket_priority_normal %}、または {% data variables.product.support_ticket_priority_low %} としてマークします。 詳しい情報については、「[サポートチケットに優先度を割り当てる](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)」および「[チケットをサブミットする](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)」を参照してください。 ### {% data variables.contact.enterprise_support %} への連絡 diff --git a/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support.md b/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support.md index bb8d328267..39e79887f0 100644 --- a/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support.md +++ b/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support.md @@ -1,6 +1,6 @@ --- title: GitHub Support からの支援を受ける -intro: 'You can contact {% data variables.contact.enterprise_support %} to report a range of issues for your enterprise.' +intro: 'Enterprise のさまざまな問題をレポートするには{% data variables.contact.enterprise_support %} に連絡してください。' redirect_from: - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/ - /enterprise/admin/enterprise-support/receiving-help-from-github-support diff --git a/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md b/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md index c1fcce70db..560f39191b 100644 --- a/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md +++ b/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md @@ -1,6 +1,6 @@ --- title: チケットのサブミット -intro: 'You can submit a support ticket using the {% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.' +intro: '{% if enterpriseServerVersions contains currentVersion %}{% data variables.product.prodname_ghe_server %}{% data variables.enterprise.management_console %} または{% endif %} GitHub Enterprise サポートページからサポートチケットをサブミットできます。' redirect_from: - /enterprise/admin/enterprise-support/submitting-a-ticket versions: @@ -13,8 +13,8 @@ versions: チケットをサブミットする前に、{% data variables.contact.github_support %} のための情報を収集し、担当者を選択してください。 詳しい情報については[チケットのサブミットの準備](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)を参照してください。 {% if enterpriseServerVersions contains currentVersion %} -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. 詳細は「[{% data variables.contact.github_support %} にデータを提供する](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)」を参照してください。 +サポートリクエストとオプションの Diagnostics 情報をサブミットした後、 +{% data variables.contact.github_support %} が Support Bundle をダウンロードして共有するように求める場合があります。 詳細は「[{% data variables.contact.github_support %} にデータを提供する](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)」を参照してください。 ### {% data variables.contact.enterprise_portal %} を使ってチケットをサブミットする @@ -51,13 +51,13 @@ After submitting your support request and optional diagnostic information, {% if currentVersion == "github-ae@latest" %} ### {% data variables.contact.ae_azure_portal %} を使ってチケットをサブミットする -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 documentation. +法人のお客様は、{% data variables.contact.contact_ae_portal %} でサポートリクエストをサブミットできます。 政府機関のお客様は、[政府機関のお客様向けの Azure ポータル](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)をご利用ください。 詳しい情報については、Microsoft ドキュメントの「[Azure サポートリクエストの作成](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request)」を参照してください。 -For urgent issues, to ensure a quick response, after you submit a ticket, please call the support hotline immediately. Your Technical Support Account Manager (TSAM) will provide you with the number to use in your onboarding session. +緊急の問題については、確実に迅速な対応を行うため、チケットをサブミットした後、すぐにサポートホットラインに電話してください。 テクニカルサポートアカウントマネージャー (TSAM) から、オンボーディングセッションで使用する番号が提供されます。 {% endif %} ### 参考リンク -- "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"{% if enterpriseServerVersions contains currentVersion %} -- "[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 variables.contact.enterprise_support %} について](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)」{% if enterpriseServerVersions contains currentVersion %} +- 「[{% data variables.product.prodname_ghe_server %} の {% data variables.contact.premium_support %} について](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)」{% endif %} diff --git a/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md index 037e1e4086..90740149c7 100644 --- a/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/about-using-actions-on-github-enterprise-server.md @@ -1,5 +1,5 @@ --- -title: About using actions on GitHub Enterprise Server +title: GitHub Enterprise Server でのアクションの使用について intro: '{% data variables.product.prodname_ghe_server %} には、ほとんどの {% data variables.product.prodname_dotcom %} 作成のアクションが含まれ、{% data variables.product.prodname_dotcom_the_website %} および {% data variables.product.prodname_marketplace %} からの他のアクションへのアクセスを有効にするためのオプションがあります。' redirect_from: - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server @@ -11,15 +11,15 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。 +{% data variables.product.prodname_actions %} ワークフローは_アクション_を使用できます。アクションは、ジョブを作成してワークフローをカスタマイズするために組み合わせることができる個々のタスクです。 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。 {% data reusables.actions.enterprise-no-internet-actions %} ### {% data variables.product.prodname_ghe_server %} にバンドルされている公式アクション -ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.prodname_ghe_server %} にバンドルされ、{% data variables.product.prodname_marketplace %} からある時点でキャプチャされます。 When your {% data variables.product.prodname_ghe_server %} instance is updated, the bundled official actions are also updated. +ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.prodname_ghe_server %} にバンドルされ、{% data variables.product.prodname_marketplace %} からある時点でキャプチャされます。 {% data variables.product.prodname_ghe_server %} インスタンスが更新されると、バンドルされている公式アクションも更新されます。 -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. +The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. Enterprise インスタンスに含まれるすべての公式アクションを確認するには、インスタンスの `Actions` Organization である (https://HOSTNAME/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. @@ -33,6 +33,6 @@ Each action is a repository in the `actions` organization, and each action repos Enterprise インスタンスのユーザが {% data variables.product.prodname_dotcom_the_website %} または {% data variables.product.prodname_marketplace %} から他のアクションにアクセスする必要がある場合、いくつかの設定オプションがあります。 -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.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 {% data reusables.actions.enterprise-limit-actions-use %} +推奨されるアプローチは、{% data variables.product.prodname_dotcom_the_website %} からのすべてのアクションへの自動アクセスを有効化することです。 これを行うには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 {% data reusables.actions.enterprise-limit-actions-use %} -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. 詳しい情報については、「[{% data variables.product.prodname_dotcom_the_website %} からのアクションを手動で同期する](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)」を参照してください。 +または、Enterprise で許可されるアクションをより厳密に制御する場合は、`actions-sync` ツールを使用してアクションを手動でダウンロードして Enterprise インスタンスに同期できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom_the_website %} からのアクションを手動で同期する](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)」を参照してください。 diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md index ca8cd4f131..12ea707112 100644 --- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md +++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting.md @@ -1,6 +1,6 @@ --- -title: Advanced configuration and troubleshooting -intro: 'Configure high availability for {% data variables.product.prodname_actions %}, and troubleshoot {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' +title: 高度な設定とトラブルシューティング +intro: '{% data variables.product.prodname_actions %} の高可用性を設定し、{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} のトラブルシューティングを行います。' mapTopic: true versions: enterprise-server: '>=3.0' diff --git a/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index a2556020e8..c3639230dc 100644 --- a/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -1,22 +1,22 @@ --- -title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled -shortTitle: Backing up and restoring -intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' +title: GitHub Actions を有効化して GitHub Enterprise Server をバックアップおよび復元する +shortTitle: バックアップと復元 +intro: '外部ストレージプロバイダの {% data variables.product.prodname_actions %} データは、通常の {% data variables.product.prodname_ghe_server %} バックアップに含まれていないため、個別にバックアップする必要があります。' versions: enterprise-server: '>=3.0' --- {% data reusables.actions.enterprise-storage-ha-backups %} -If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. +{% data variables.product.prodname_enterprise_backup_utilities %} を使用して {% data variables.product.product_location %} をバックアップする場合、外部ストレージプロバイダに保存されている {% data variables.product.prodname_actions %} データはバックアップに含まれないことにご注意ください。 -This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: +以下は、{% data variables.product.product_location %} と {% data variables.product.prodname_actions %} を新しいアプライアンスに復元するために必要なステップの概要です。 -1. Confirm that the original appliance is offline. -1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. -1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance. -1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. -1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." -1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). +1. 元のアプライアンスがオフラインであることを確認します。 +1. 交換用の {% data variables.product.prodname_ghe_server %} アプライアンスでネットワーク設定を手動設定します。 ネットワーク設定はバックアップスナップショットから除外され、`ghe-restore` で上書きされません。 +1. 元のアプライアンスと同じ {% data variables.product.prodname_actions %} 外部ストレージ設定を使用するように交換用アプライアンスを設定します。 +1. 交換用アプライアンスで {% data variables.product.prodname_actions %} を有効化します。 これにより、交換用アプライアンスが {% data variables.product.prodname_actions %} の同じ外部ストレージに接続されます。 +1. {% data variables.product.prodname_actions %} を外部ストレージプロバイダで設定したら、`ghe-restore` コマンドを使用して、バックアップから残りのデータを復元します。 詳しい情報については、「[バックアップを復元する](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)」を参照してください。 +1. セルフホストランナーを交換用アプライアンスに再登録します。 詳しい情報については、「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 -For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." +{% data variables.product.prodname_ghe_server %} のバックアップと復元の詳細については、「[アプライアンスでバックアップを設定する](/admin/configuration/configuring-backups-on-your-appliance)」を参照してください。 diff --git a/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 4c643744f7..09f7b4b745 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: デフォルトでは、{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} ワークフローは {% data variables.product.prodname_dotcom_the_website %} または [{% 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.prodname_ghe_server %} 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 on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." +{% data variables.product.prodname_dotcom_the_website %} のすべてのアクションを Enterprise インスタンスで使用できるようにするには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 {% data variables.product.prodname_dotcom_the_website %} からアクションにアクセスする他の方法については、「[{% data variables.product.prodname_ghe_server %} でのアクションの使用について](/admin/github-actions/about-using-actions-on-github-enterprise-server)」を参照してください。 ### すべての {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md index 097155565b..c19b33ad68 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server.md @@ -1,6 +1,6 @@ --- -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 %}.' +title: GitHub Enterprise Server の GitHub Actions を有効化する +intro: 'ストレージを設定し、{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効化する方法を学びます。' mapTopic: true versions: enterprise-server: '>=2.22' diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md index 4ee287b789..b91da27182 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Actions with Amazon S3 storage -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +title: Amazon S3 ストレージで GitHub Actions を有効化する +intro: '{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効化し、Amazon S3 ストレージを使用してワークフローの実行によって生成されたアーティファクトを保存できます。' permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' versions: enterprise-server: '>=3.0' @@ -10,27 +10,27 @@ versions: {% data reusables.actions.enterprise-s3-support-warning %} -Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: +{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。 -* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} +* ワークフローの実行によって生成されたアーティファクトを保存するための Amazon S3 バケットを作成します。 {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %} -### Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage +### Amazon S3 ストレージで {% data variables.product.prodname_actions %} を有効化する {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: +1. [Artifact & Log Storage] で、[**Amazon S3**] を選択し、ストレージバケットの詳細を入力します。 - * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + * **AWS Service URL**: バケットのサービス URL。 たとえば、S3 バケットが `us-west-2` リージョンで作成された場合、この値は `https://s3.us-west-2.amazonaws.com` である必要があります。 For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. - * **AWS S3 Bucket**: The name of your S3 bucket. - * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + * **AWS S3 Bucket**: S3 バケットの名前。 + * **AWS S3 Access Key** および **AWS S3 Secret Key**: バケットの AWS アクセスキー IDと シークレットキー。 For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." - ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) + ![Amazon S3 ストレージを選択するためのラジオボタンと S3 設定のフィールド](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md index 1a377bd6ef..447101eb21 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Actions with Azure Blob storage -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +title: Azure Blob ストレージで GitHub Actions を有効化する +intro: '{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効化し、Azure Blob ストレージを使用して、ワークフローの実行によって生成されたアーティファクトを格納できます。' permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' versions: enterprise-server: '>=3.0' @@ -8,28 +8,28 @@ versions: ### 必要な環境 -Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: +{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。 -* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: - * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. +* ワークフローアーティファクトを保存するための Azure ストレージアカウントを作成します。 {% data variables.product.prodname_actions %} はデータをブロック Blob として保存し、次の 2 つのストレージアカウントタイプがサポートされています。 + * **標準**のパフォーマンス層を使用する **general-purpose** ストレージアカウント (`general-purpose v1` または `general-purpose v2` としても知られる)。 {% warning %} - **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + **Warning:** general-purpose ストレージアカウントでの**プレミアム**パフォーマンス層の使用はサポートされていません。 ストレージアカウントを作成するときに**標準**のパフォーマンス層を選択する必要があり、後で変更することはできません。 {% endwarning %} - * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + * **プレミアム**パフォーマンス層を使用する **BlockBlobStorage** ストレージアカウント。 - For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). + Azure ストレージアカウントの種類とパフォーマンス層の詳細については、[Azure のドキュメント](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts)を参照してください。 {% data reusables.actions.enterprise-common-prereqs %} -### Enabling {% data variables.product.prodname_actions %} with Azure Blob storage +### Azure Blob ストレージで {% data variables.product.prodname_actions %} を有効化する {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +1. [Artifact & Log Storage] で、[**Azure Blob Storage**] を選択し、Azure ストレージアカウントの接続文字列型を入力します。 ストレージアカウントの接続文字列型を取得する方法について詳しくは、[Azure のドキュメント](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys)を参照してください。 ![[Azure Blob Storage] と [Connection string] フィールドを選択するためのラジオボタン](/assets/images/enterprise/management-console/actions-azure-storage.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 14c79c03e0..3a4c2e25ce 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Actions with MinIO Gateway for NAS storage -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +title: NAS ストレージ用の MinIO ゲートウェイで GitHub Actions を有効化する +intro: '{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効化し、NAS ストレージに MinIO Gateway を使用して、ワークフローの実行によって生成されたアーティファクトを保存できます。' permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' versions: enterprise-server: '>=3.0' @@ -10,27 +10,27 @@ versions: {% data reusables.actions.enterprise-s3-support-warning %} -Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: +{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。 -* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. -* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} +* アプライアンスでのリソースの競合を回避するために、MinIO を {% data variables.product.product_location %} とは別にホストすることをお勧めします。 +* ワークフローアーティファクトを保存するためのバケットを作成します。 バケットとアクセスキーを設定するには、[MinIO のドキュメント](https://docs.min.io/docs/minio-gateway-for-nas.html)を参照してください。 {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %} -### Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage +### NAS ストレージ用の MinIO ゲートウェイで {% data variables.product.prodname_actions %} を有効化する {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: +1. [Artifact & Log Storage] で、[**Amazon S3**] を選択し、ストレージバケットの詳細を入力します。 - * **AWS Service URL**: The URL to your MinIO service. たとえば、`https://my-minio.example:9000` などです。 - * **AWS S3 Bucket**: The name of your S3 bucket. - * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + * **AWS Service URL**: MinIO サービスへの URL。 たとえば、`https://my-minio.example:9000` などです。 + * **AWS S3 Bucket**: S3 バケットの名前。 + * **AWS S3 Access Key** および **AWS S3 Secret Key**: MinIO インスタンスに使用される `MINIO_ACCESS_KEY` および `MINIO_SECRET_KEY`。 詳しい情報については、[MinIO のドキュメント](https://docs.min.io/docs/minio-gateway-for-nas.html)を参照してください。 - ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) -1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) + ![Amazon S3 ストレージを選択するためのラジオボタンと MinIO 設定のフィールド](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. [Artifact & Log Storage] で [**Force path style**] を選択します。 ![[Force path style] チェックボックス](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index fad9d47882..8e0fb41869 100644 --- a/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -11,7 +11,7 @@ versions: ### Enterprise の {% data variables.product.prodname_actions %} 権限について -{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にすると、企業内のすべての Organization で有効になります。 Enterprise 内のすべての Organization に対して {% data variables.product.prodname_actions %} を無効化するか、特定の Organization のみを許可するかを選択できます。 You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. +{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にすると、企業内のすべての Organization で有効になります。 Enterprise 内のすべての Organization に対して {% data variables.product.prodname_actions %} を無効化するか、特定の Organization のみを許可するかを選択できます。 Enterprise にあるローカルのアクションだけ利用できるように、パブリックなアクションの利用を制限することもできます。 ### Enterprise の {% data variables.product.prodname_actions %} 権限の管理 diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index e4700459c7..785344ee35 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -1,6 +1,6 @@ --- -title: Getting started with GitHub Actions for GitHub Enterprise Server -intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' +title: GitHub Enterprise Server の GitHub Actions を使い始める +intro: '{% data variables.product.prodname_ghe_server %} での {% data variables.product.prodname_actions %} の有効化と設定について初めて学びます。' permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} を有効化して、Enterprise 設定を構成できます。' redirect_from: - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage @@ -21,19 +21,19 @@ versions: {% if currentVersion ver_gt "enterprise-server@2.22" %} -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. +この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_server %} を設定する方法について説明しています。 ハードウェアとソフトウェアの要件、ストレージオプション、セキュリティ管理ポリシーについて説明します。 -### Review hardware considerations +### ハードウェアについての留意点を確認する {% data reusables.actions.enterprise-hardware-considerations %} {% endif %} -### External storage requirements +### 外部ストレージの要件 {% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にするには、外部 Blob ストレージにアクセスできる必要があります。 -{% data variables.product.prodname_actions %} は、blob ストレージを使用して、ワークフローログやユーザがアップロードしたビルドアーティファクトなど、ワークフロー実行によって生成されたアーティファクトを保存します。 必要なストレージ容量は、{% 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 %} は、blob ストレージを使用して、ワークフローログやユーザがアップロードしたビルドアーティファクトなど、ワークフロー実行によって生成されたアーティファクトを保存します。 必要なストレージ容量は、{% data variables.product.prodname_actions %} の使用状況によって異なります。 単一の外部ストレージ設定のみがサポートされており、複数のストレージプロバイダを同時に使用することはできません。 {% data variables.product.prodname_actions %} は、次のストレージプロバイダをサポートしています。 @@ -43,7 +43,7 @@ This article explains how site administrators can configure {% data variables.pr {% 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. +**注釈:** これらは、{% data variables.product.company_short %} がサポートし、支援を提供できる唯一のストレージプロバイダです。 他の S3 API 互換のストレージプロバイダは、S3 API との違いにより、機能しない可能性があります。 追加のストレージプロバイダのサポートをリクエストするには、[お問い合わせ](https://support.github.com/contact)ください。 {% endnote %} @@ -65,32 +65,32 @@ This article explains how site administrators can configure {% data variables.pr {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Enabling {% data variables.product.prodname_actions %} with your storage provider +### ストレージプロバイダで {% data variables.product.prodname_actions %} を有効化する -Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: +以下の手順のいずれかに従って、選択したストレージプロバイダで {% data variables.product.prodname_actions %} を有効にします。 -* [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) +* [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) -### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise +### Enterprise 内の {% data variables.product.prodname_actions %} のアクセス権限を管理する -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)." +ポリシーを使用して、{% 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 %} -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. 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 +{% data variables.product.prodname_actions %} ワークフローを実行するには、セルフホストランナーを追加する必要があります。 Enterprise、Organization、リポジトリレベルでセルフホストランナーを追加できます。 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 -### Managing which actions can be used in your enterprise +### 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 %}. +ユーザーが Enterprise で使用できるアクションを制御できます。 これには、{% data variables.product.prodname_dotcom_the_website %} からのアクションへの自動アクセス用の {% data variables.product.prodname_github_connect %} の設定、または {% data variables.product.prodname_dotcom_the_website %} からのアクションの手動同期が含まれます。 -For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)." +詳しい情報については、「[{% data variables.product.prodname_ghe_server %} でのアクションの使用について](/admin/github-actions/about-using-actions-on-github-enterprise-server)」を参照してください。 -### General security hardening for {% data variables.product.prodname_actions %} +### {% 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 variables.product.prodname_actions %} のセキュリティプラクティスについて詳しく学ぶには、「[{% data variables.product.prodname_actions %} のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md index 4d2a829fc5..b970627216 100644 --- a/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md +++ b/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md @@ -1,29 +1,29 @@ --- -title: High availability for GitHub Actions -intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.' +title: GitHub Actions の High Availability +intro: 'High Availability 設定で {% data variables.product.prodname_actions %} を管理するための特別な留意点がいくつかあります。' versions: enterprise-server: '>=3.0' --- -### Replication or redundancy of your {% data variables.product.prodname_actions %} data +### {% data variables.product.prodname_actions %} データのレプリケーションまたは冗長性 {% data reusables.actions.enterprise-storage-ha-backups %} -We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation: +データの冗長性またはレプリケーションを使用するように、{% data variables.product.prodname_actions %} 外部ストレージを設定することを強くお勧めします。 詳細については、次のストレージプロバイダのドキュメントを参照してください。 -* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) -* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) +* [Azure Storage 冗長性ドキュメント](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy) +* [Amazon S3 レプリケーションドキュメント](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html) -### High availability replicas +### High Availability レプリカ -#### Promoting a replica +#### レプリカの昇格 -When enabling a high availability configuration, any replicas are automatically configured to use the {% data variables.product.prodname_actions %} external storage configuration. If you need to initiate a failover to promote a replica, no extra configuration changes are required for {% data variables.product.prodname_actions %}. +High Availability 設定を有効にすると、レプリカは {% data variables.product.prodname_actions %} 外部ストレージ設定を使用するように自動的に設定されます。 レプリカを昇格させるためにフェイルオーバーを開始する場合、{% data variables.product.prodname_actions %} に対して追加の設定変更は必要ありません。 -For more information, see "[Initiating a failover to your replica appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)." +詳しい情報については、「[レプリカアプライアンスへのフェイルオーバーを開始する](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)」を参照してください。 #### High Availabilityレプリカの削除 -Avoid letting multiple instances to write to the same {% data variables.product.prodname_actions %} external storage. This could occur when using the `ghe-repl-teardown` command to stop and permanently remove a {% data variables.product.prodname_actions %}-enabled replica. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. +複数のインスタンスに同じ {% data variables.product.prodname_actions %} 外部ストレージへの書き込みをさせないようにします。 これは、`ghe-repl-teardown` コマンドを使用して、{% data variables.product.prodname_actions %} 対応のレプリカを停止して完全に削除するときに発生する可能性があります。 これは、レプリカが単独の {% data variables.product.prodname_ghe_server %} に変換され、ティアダウン後もプライマリと同じ外部ストレージ設定を使用するためです。 -To help avoid this issue, we recommend either decommissioning the replica server or updating its {% data variables.product.prodname_actions %} configuration with different external storage. +この問題を回避するには、レプリカサーバーを廃止するか、その {% data variables.product.prodname_actions %} 設定を別の外部ストレージで更新することをお勧めします。 diff --git a/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index dfb6c7256d..89ef65c311 100644 --- a/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -12,9 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -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.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 +{% data variables.product.prodname_dotcom_the_website %} からのアクションへのアクセスを有効化する際に推奨されるアプローチは、すべてのアクションへの自動アクセスを有効化することです。 これを行うには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 -However, if you want stricter control over which actions are allowed in your enterprise, you 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 instance. +ただし、Enterprise で許可されるアクションをより厳密に制御する場合は、このガイドに従って、{% data variables.product.company_short %} のオープンソース [`actions-sync`](https://github.com/actions/actions-sync) ツールを使用して、個々のアクションリポジトリを {% data variables.product.prodname_dotcom_the_website %} から Enterprise インスタンスに同期できます。 ### About the `actions-sync` tool @@ -26,7 +26,7 @@ If your machine has access to both systems at the same time, you can do the sync ### 必要な環境 -* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +* `actions-sync` ツールを使用する前に、すべての宛先 Organization が Enterprise インスタンスにすでに存在していることを確認する必要があります。 The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. 詳しい情報については、「[新しい Organization をゼロから作成する](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)」を参照してください。 * You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 ### Example: Using the `actions-sync` tool @@ -63,7 +63,7 @@ If your machine has access to both systems at the same time, you can do the sync * 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 on your enterprise instance, 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/docker-build-push-action@v1 ``` diff --git a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 1321a822c4..0b176cd875 100644 --- a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -1,6 +1,6 @@ --- title: Setting up the tool cache on self-hosted runners without internet access -intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' +intro: 'インターネットにアクセスできないセルフホストランナー上の `actions/setup` アクションを使用するには、最初にワークフローのランナーのツールキャッシュにデータを入力する必要があります。' redirect_from: - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access versions: @@ -34,7 +34,7 @@ The `actions/setup-LANGUAGE` actions normally need internet access to download t ### Populating the tool cache for a self-hosted runner -1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow. +1. {% data variables.product.prodname_dotcom_the_website %} で、{% data variables.product.prodname_actions %} ワークフローの実行に使用できるリポジトリに移動します。 1. {% data variables.product.prodname_dotcom %} ホストランナーのツールキャッシュを含むアーティファクトをアップロードする、リポジトリの `.github/workflows` フォルダに新しいワークフローファイルを作成します。 The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12. diff --git a/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md index 55ba376bc7..7cbfa999ab 100644 --- a/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -1,26 +1,26 @@ --- -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.' +title: Enterprise 向け GitHub Actions のトラブルシューティング +intro: '{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を使用するときに発生する一般的な問題のトラブルシューティング。' +permissions: 'サイト管理者は、{% data variables.product.prodname_actions %} の問題をトラブルシューティングし、{% data variables.product.prodname_ghe_server %} 設定を変更できます。' versions: enterprise-server: '>=3.0' --- -### Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} +### {% 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 %} 詳しい情報については、「[TLS を設定する](/admin/configuration/configuring-tls)」を参照してください。 -#### Installing the certificate on the runner machine +#### ランナーマシンに証明書をインストールする -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. +セルフホストランナーが自己署名証明書を使用して {% data variables.product.prodname_ghe_server %} に接続するには、接続がセキュリティで強化されるように、証明書をランナーマシンにインストールする必要があります。 -For the steps required to install a certificate, refer to the documentation for your runner's operating system. +証明書をインストールするステップについては、ランナーのオペレーティングシステムのドキュメントを参照してください。 -#### Configuring Node.JS to use the certificate +#### 証明書を使用するように Node.JS を設定する -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. +ほとんどのアクションは JavaScript で記述されており、オペレーティングシステムの証明書ストアを使用しない Node.js を使用して実行されます。 セルフホストランナーアプリケーションで証明書を使用するには、ランナーマシンで `NODE_EXTRA_CA_CERTS` 環境変数を設定する必要があります。 -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. +環境変数をシステム環境変数として設定するか、セルフホストランナーアプリケーションディレクトリの _.env_ という名前のファイルで宣言することができます。 例: @@ -28,44 +28,44 @@ You can set the environment variable as a system environment variable, or declar NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt ``` -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. +環境変数は、セルフホストランナーアプリケーションの起動時に読み込まれるため、セルフホストランナーアプリケーションを設定または起動する前に、環境変数を設定する必要があります。 証明書の設定が変更された場合は、セルフホストランナーアプリケーションを再起動する必要があります。 -#### Configuring Docker containers to use the certificate +#### 証明書を使用するように Docker コンテナを設定する -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. +ワークフローで Docker コンテナアクションまたはサービスコンテナを使用する場合は、上記の環境変数の設定に加えて、Docker イメージに証明書をインストールする必要がある場合もあります。 -### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} +### {% data variables.product.prodname_actions %} の HTTP プロキシ設定 {% data reusables.actions.enterprise-http-proxy %} -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. +これらの設定が正しく行われていない場合、{% data variables.product.prodname_actions %} 設定を設定または変更するときに、`Resource unexpectedly moved to https://` などのエラーが発生する可能性があります。 -### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname +### ホスト名を変更した後、ランナーは {% data variables.product.prodname_ghe_server %} に接続しません -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. +{% data variables.product.product_location %} のホスト名を変更すると、セルフホストランナーは古いホスト名に接続できなくなり、ジョブを実行しなくなります。 -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: +{% data variables.product.product_location %} に新しいホスト名を使用するには、セルフホストランナーの設定を更新する必要があります。 各セルフホストランナーには、次のいずれかの手順を行う必要があります。 -* 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. 詳しい情報については「[セルフホストランナーの削除](/actions/hosting-your-own-runners/removing-self-hosted-runners)」及び「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 +* セルフホストランナーアプリケーションディレクトリで、`.runner` ファイルと `.credentials` ファイルを編集して、古いホスト名のすべての記述を新しいホスト名に置き換えてから、セルフホストランナーアプリケーションを再起動します。 +* UIを使用して {% data variables.product.prodname_ghe_server %} からランナーを削除し、再度追加します。 詳しい情報については「[セルフホストランナーの削除](/actions/hosting-your-own-runners/removing-self-hosted-runners)」及び「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 -### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits +### スタックジョブと {% data variables.product.prodname_actions %} メモリと CPU の制限 -{% 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. +{% data variables.product.prodname_actions %} は、{% data variables.product.product_location %} で実行されている複数のサービスで構成されています。 デフォルトでは、これらのサービスは、ほとんどのインスタンスで機能するデフォルトの CPU およびメモリ制限で設定されています。 ただし、{% data variables.product.prodname_actions %} のヘビーユーザは、これらの設定を調整する必要がある場合があります。 -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. +ジョブが開始されていないことに気付いた場合（アイドル状態のランナーが存在する場合でも）、または UI でジョブの進行状況が更新または変更されていない場合は、CPU またはメモリの上限に達している可能性があります。 -#### 1. Check the overall CPU and memory usage in the management console +#### 1. Management Console で全体的な CPU とメモリの使用率を確認する -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)." +Management Console にアクセスし、モニターダッシュボードを使用して、[System Health] の下の全体的な CPU とメモリのグラフを調べます。 詳しい情報については、「[モニターダッシュボードへのアクセス](/admin/enterprise-management/accessing-the-monitor-dashboard)」を参照してください。 -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)." +[System Health] 全体の CPU 使用率が 100％ に近い場合、または空きメモリが残っていない場合は、{% data variables.product.product_location %} が容量で実行されているため、スケールアップする必要があります。 詳しい情報については、「[CPU またはメモリリソースを増やす](/admin/enterprise-management/increasing-cpu-or-memory-resources)」を参照してください。 -#### 2. Check the Nomad Jobs CPU and memory usage in the management console +#### 2. Management Console で Nomad Jobs の CPU とメモリの使用率を確認する -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. +全体的な [System Health] の CPU とメモリの使用率に問題がない場合は、モニターダッシュボードページを下にスクロールして [Nomad Jobs] セクションに移動し、[CPU Percent Value] と [Memory Usage] のグラフを確認します。 -Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: +これらのグラフの各プロットは、1 つのサービスに対応しています。 {% data variables.product.prodname_actions %} サービスについては、以下を探してください。 * `mps_frontend` * `mps_backend` @@ -74,18 +74,18 @@ Each plot in these graphs corresponds to one service. For {% data variables.prod * `actions_frontend` * `actions_backend` -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. +これらのサービスのいずれかが 100％ またはそれに近い CPU 使用率であるか、メモリが上限（デフォルトでは 2 GB）に近い場合、これらのサービスのリソース割り当てを増やす必要がある場合があります。 上記のサービスのどれが上限に達しているか、上限に近いかを注視してください。 -#### 3. Increase the resource allocation for services at their limit +#### 3. 上限に達したサービスへのリソース割り当てを増やす -1. Log in to the administrative shell using SSH. 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。 -1. Run the following command to see what resources are available for allocation: +1. SSH を使用して管理シェルにログインします。 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。 +1. 次のコマンドを実行して、割り当てに利用可能なリソースを確認します。 ```shell nomad node status -self ``` - In the output, find the "Allocated Resources" section. It looks similar to the following example: + 出力で [Allocated Resources] セクションを見つけます。 次の例のようになります。 ``` Allocated Resources @@ -93,25 +93,25 @@ If any of these services are at or near 100% CPU utilization, or the memory is n 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB ``` - 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. + CPU とメモリの場合、これは**すべて**のサービスの**合計**に割り当てられているｃ量（左の値）と利用可能な容量（右の値）を示しています。 上記の例では、合計 32GiB のうち 23GiB のメモリが割り当てられています。 これは、9GiB のメモリを割り当てることができるということを示しています。 {% warning %} - **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + **Warning:** 利用可能なリソースの合計を超える容量を割り当てると、サービスが開始されませんので注意してください。 {% endwarning %} -1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: +1. ディレクトリを `/etc/consul-templates/etc/nomad-jobs/actions` に変更します。 ```shell cd /etc/consul-templates/etc/nomad-jobs/actions ``` - In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + このディレクトリには、上記の {% data variables.product.prodname_actions %} サービスに対応する 3 つのファイルがあります。 * `mps.hcl.ctmpl` * `token.hcl.ctmpl` * `actions.hcl.ctmpl` -1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: +1. 調整が必要なサービスを特定した場合は、対応するファイルを開き、次のような `resources` グループを見つけます。 ``` resources { @@ -123,9 +123,9 @@ If any of these services are at or near 100% CPU utilization, or the memory is n } ``` - The values are in MHz for CPU resources, and MB for memory resources. + 値は、CPU リソースの場合は MHz、メモリリソースの場合は MB です。 - 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: + たとえば、上記の例のリソース制限を CPU と 4 GBのメモリの 1GHz に増やすには、次のように変更します。 ``` resources { @@ -136,8 +136,8 @@ If any of these services are at or near 100% CPU utilization, or the memory is n } } ``` -1. Save and exit the file. -1. Run `ghe-config-apply` to apply the changes. +1. ファイルを保存して終了します。 +1. `ghe-config-apply` を実行して、変更を適用します。 - 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. + `ghe-config-apply` の実行中に、`Failed to run nomad job '/etc/nomad-jobs/.hcl'` のような出力が表示される場合は、変更によって CPU またはメモリリソースが過剰に割り当てられている可能性があります。 これが発生した場合は、設定ファイルを再度編集し、割り当てられた CPU またはメモリを減らしてから、`ghe-config-apply` を再実行してください。 +1. 設定が適用されたら、`ghe-actions-check` を実行して、{% data variables.product.prodname_actions %} サービスが機能していることを確認します。 diff --git a/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md b/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md index 285cf6b658..a898af2e18 100644 --- a/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md +++ b/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md @@ -1,26 +1,26 @@ --- -title: Using a staging environment -intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +title: ステージング環境を使用する +intro: '{% data variables.product.prodname_actions %} を {% data variables.product.prodname_ghe_server %} ステージング環境で使用する方法について説明します。' versions: enterprise-server: '>=3.0' --- -It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. +{% data variables.product.product_location %} のステージング環境またはテスト環境があると便利な場合があります。これにより、更新または新機能を本番環境に実装する前にテストできます。 -A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. +ステージング環境を作成する一般的な方法は、本番インスタンスのバックアップを使用して、それをステージング環境に復元することです。 -When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. +{% data variables.product.prodname_actions %} が有効になっている {% data variables.product.prodname_ghe_server %} ステージング環境をセットアップする場合、{% data variables.product.prodname_actions %} ストレージには本番環境が使用するものとは異なる外部ストレージ設定を使用する必要があります。 それ以外の場合、ステージング環境は本番環境と同じ外部ストレージに書き込まれます。 -Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. +既存の {% data variables.product.prodname_actions %} ワークフロー実行からログまたはアーティファクトを表示しようとすると、ステージング環境で `404` エラーが発生することが予想されます。これは、そのデータがステージングストレージの場所から消失するためです。 -Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. +{% data variables.product.prodname_actions %} がステージング環境で機能する必要はありませんが、必要に応じて、ファイルを本番ストレージの場所からステージングストレージの場所にコピーできます。 -* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). 例: +* Azure ストレージアカウントの場合、[`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account) を使用できます。 例: ```shell azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive ``` -* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). 例: +* Amazon S3 バケットの場合、[`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html) を使用できます。 例: ```shell aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md index 5a24e43e76..6d0f564a05 100644 --- a/translations/ja-JP/content/admin/index.md +++ b/translations/ja-JP/content/admin/index.md @@ -3,7 +3,7 @@ title: Enterprise 管理者 redirect_from: - /enterprise/admin/hidden/migrating-from-github-fi/ - /enterprise/admin -intro: Documentation and guides for enterprise administrators, system administrators, and security specialists who {% if enterpriseServerVersions contains currentVersion %}deploy, {% endif %}configure{% if enterpriseServerVersions contains currentVersion %},{% endif %} and manage {% data variables.product.product_name %}. +intro: '{% data variables.product.product_name %} を{% if enterpriseServerVersions contains currentVersion %}デプロイ、{% endif %}設定{% if enterpriseServerVersions contains currentVersion %}、{% endif %}管理する Enterprise 管理者、システム管理者、およびセキュリティスペシャリスト向けのドキュメントとガイドです。' versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md index 7c48be358b..58b2bdb517 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,5 +130,5 @@ aws ec2 run-instances \ ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md index 35fdf2a756..d9f5532891 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -14,7 +14,7 @@ versions: - {% data reusables.enterprise_installation.software-license %} - 新しいコンピューターをプロビジョニングできる Azure アカウントを所有していなければなりません。 詳しい情報については [Microsoft Azure のウェブサイト](https://azure.microsoft.com)を参照してください。 -- 仮想マシン（VM）を起動するのに必要なアクションのほとんどは、Azureポータルを使っても行えます。 とはいえ、初期セットアップ用にはAzureコマンドラインインターフェース（CLI）をインストールすることをお勧めします。 以下の例では、Azure CLI 2.0が使われています。 For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)." +- 仮想マシン（VM）を起動するのに必要なアクションのほとんどは、Azureポータルを使っても行えます。 とはいえ、初期セットアップ用にはAzureコマンドラインインターフェース（CLI）をインストールすることをお勧めします。 以下の例では、Azure CLI 2.0が使われています。 詳しい情報については、Azure のガイド「[Azure CLI 2.0 のインストール](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)」を参照してください。 ### ハードウェアについて @@ -26,9 +26,9 @@ versions: #### サポートされているVMタイプとリージョン -{% data variables.product.prodname_ghe_server %} アプライアンスは、プレミアムストレージのデータディスクを必要としており、プレミアムストレージをサポートするあらゆる Azure VM でサポートされます。 For more information, see "[Supported VMs](https://docs.microsoft.com/azure/storage/common/storage-premium-storage#supported-vms)" in the Azure documentation. For general information about available VMs, see [the Azure virtual machines overview page](https://azure.microsoft.com/pricing/details/virtual-machines/#Linux). +{% data variables.product.prodname_ghe_server %} アプライアンスは、プレミアムストレージのデータディスクを必要としており、プレミアムストレージをサポートするあらゆる Azure VM でサポートされます。 詳しい情報については、Azure ドキュメントの「[サポートされている VM](https://docs.microsoft.com/azure/storage/common/storage-premium-storage#supported-vms)」を参照してください。 使用可能な VM の一般的な情報については、[Azure 仮想マシンの概要ページ](https://azure.microsoft.com/pricing/details/virtual-machines/#Linux)を参照してください。 -{% data variables.product.prodname_ghe_server %} は、VM タイプをサポートするあらゆる地域をサポートします。 For more information about the supported regions for each VM, see Azure's "[Products available by region](https://azure.microsoft.com/regions/services/)." +{% data variables.product.prodname_ghe_server %} は、VM タイプをサポートするあらゆる地域をサポートします。 各 VM でサポートされているリージョンの詳細については、Azure の「[リージョン別の利用可能な製品](https://azure.microsoft.com/regions/services/)」を参照してください。 #### 推奨VMタイプ @@ -47,7 +47,7 @@ versions: {% data reusables.enterprise_installation.create-ghe-instance %} -1. 最新の {% data variables.product.prodname_ghe_server %} アプライアンスイメージを見つけます。 For more information about the `vm image list` command, see "[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation. +1. 最新の {% data variables.product.prodname_ghe_server %} アプライアンスイメージを見つけます。 `vm image list` コマンドの詳細については、Microsoft のドキュメントの「[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)」を参照してください。 ```shell $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V ``` @@ -96,7 +96,7 @@ versions: ``` {% note %} - **メモ:** Azure は VM 用の FQDN エントリを自動的に作成しません。 For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)." + **メモ:** Azure は VM 用の FQDN エントリを自動的に作成しません。 詳しい情報については、「[Linux VM 用 Azure Portal での完全修飾ドメイン名の作成](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)」方法に関する Azure のガイドを参照してください。 {% endnote %} @@ -108,6 +108,6 @@ versions: ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index 72f0fb2288..fcfb5d65b0 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,5 +113,5 @@ GCE 仮想マシンは、ファイアウォールが存在するネットワー ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index 8d1f5caf03..267f114595 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -12,7 +12,7 @@ versions: - {% data reusables.enterprise_installation.software-license %} - Hyper-VをサポートしているWindows Server 2008からWindows Server 2016を持っている必要があります。 -- 仮想マシン（VM）の作成に必要なほとんどのアクションは、 [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts)を使っても行えます。 とはいえ、初期セットアップのためにはWindows PowerShellコマンドラインシェルを使うことをおすすめします。 以下の例ではPowerShellを使っています。 For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)." +- 仮想マシン（VM）の作成に必要なほとんどのアクションは、 [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts)を使っても行えます。 とはいえ、初期セットアップのためにはWindows PowerShellコマンドラインシェルを使うことをおすすめします。 以下の例ではPowerShellを使っています。 詳細については、Microsoft ガイド「[Windows PowerShell 入門](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)」を参照してください。 ### ハードウェアについて @@ -62,5 +62,5 @@ versions: ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index 2c616566fa..249efeee64 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,5 +49,5 @@ versions: ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md index ecb0c3713e..aadee4d7b1 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,5 +48,5 @@ versions: ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index 68c29478c2..a66b77888a 100644 --- a/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/ja-JP/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,5 +45,5 @@ versions: ### 参考リンク -- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% if currentVersion ver_gt "enterprise-server@2.22" %} -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% if currentVersion ver_gt "enterprise-server@2.22" %} +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %} diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md b/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md index 92075ec1fb..c2b02a4f9e 100644 --- a/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md @@ -28,5 +28,5 @@ versions: {% if currentVersion ver_gt "enterprise-server@2.22" %} ### 参考リンク -- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" +- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」 {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md index cbd522aa90..08a39aaca0 100644 --- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- title: Enterprise アカウントについて -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management{% if enterpriseServerVersions contains currentVersion %} for billing and license usage{% endif %}.' +intro: '{% data variables.product.product_name %} では、Enterprise アカウントを使用して、管理者に{% if enterpriseServerVersions contains currentVersion %}支払いとライセンスの使用に関する単一の表示と管理ポイントを提供できます{% endif %}。' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts @@ -11,18 +11,18 @@ versions: ### {% data variables.product.product_name %} の Enterprise アカウントについて -An enterprise account allows you to manage multiple organizations{% if enterpriseServerVersions contains currentVersion %} and {% data variables.product.prodname_ghe_server %} instances{% else %} on {% data variables.product.product_name %}{% endif %}. Enterprise アカウントは、{% data variables.product.prodname_dotcom %} 上の Organization や個人アカウントのようにハンドルを持たなければなりません。 Enterprise 管理者は、以下のような設定やプリファレンスを管理できます: +Enterprise アカウントでは、{% data variables.product.product_name %}で複数の Organization{% if enterpriseServerVersions contains currentVersion %} と {% data variables.product.prodname_ghe_server %} インスタンス{% else %}を管理できます{% endif %}。 Enterprise アカウントは、{% data variables.product.prodname_dotcom %} 上の Organization や個人アカウントのようにハンドルを持たなければなりません。 Enterprise 管理者は、以下のような設定やプリファレンスを管理できます: -- Member access and management (organization members, outside collaborators){% if enterpriseServerVersions contains currentVersion %} -- Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs){% endif %} -- Security {% if enterpriseServerVersions contains currentVersion %}(single sign-on, two factor authentication) -- Requests {% if enterpriseServerVersions contains currentVersion %}and support bundle sharing {% endif %}with {% data variables.contact.enterprise_support %}{% endif %} +- メンバーのアクセスと管理（Organization メンバー、外部のコラボレータ）{% if enterpriseServerVersions contains currentVersion %} +- 請求と使用状況（{% data variables.product.prodname_ghe_server %} インスタンス、ユーザライセンス、{% data variables.large_files.product_name_short %} パック）{% endif %} +- セキュリティ {% if enterpriseServerVersions contains currentVersion %}（シングルサインオン、2 要素認証） +- {% data variables.contact.enterprise_support %} との Support Bundle {% endif %} のリクエスト{% if enterpriseServerVersions contains currentVersion %} とサポート{% endif %} -{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about the management of your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %}{% data variables.product.prodname_ghe_cloud %} サブスクリプションの管理に関する詳しい情報については、「[Enterprise アカウントのサブスクリプションと利用状況の表示](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)」を参照してください。 {% endif %}{% data variables.product.product_name %} の支払い設定の管理の詳細については、「[Enterprise の支払いを管理する](/admin/overview/managing-billing-for-your-enterprise)」を参照してください。 -For more information about the management of users, organizations, data, and policies for {% data variables.product.product_location %}, see "[Managing users, organizations, and repositories](/admin/user-management)" and "[Setting policies for your enterprise](/admin/policies)." +{% data variables.product.product_location %} のユーザ、Organization、データ、およびポリシーの管理の詳細については、「[ユーザ、Organization、およびリポジトリを管理する](/admin/user-management)」および「[Enterprise のポリシーを設定する](/admin/policies)」を参照してください。 -For more information about the management of enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +GraphQL API を使用した Enterprise アカウントの管理の詳細については、「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。 {% if enterpriseServerVersions contains currentVersion %} diff --git a/translations/ja-JP/content/admin/overview/about-github-ae.md b/translations/ja-JP/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..99e31c1b2c --- /dev/null +++ b/translations/ja-JP/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: GitHub AE について +intro: '{% data variables.product.prodname_ghe_managed %} は、{% data variables.product.prodname_dotcom %} を使用するための最も安全で準拠した方法です。' +versions: + github-ae: '*' +--- + +### {% data variables.product.prodname_ghe_managed %} について + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} は、アイデアから本番まで1つの開発者プラットフォームを提供します。 開発者の作業を加速させ、ワークフロー全体を自動化し、コードを保護して、開発者のお気に入りのツールでコラボレーションを行うことができます。 + +{% data variables.product.prodname_ghe_managed %} は、Organization に [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) のすべての機能を提供しています。 {% data variables.product.prodname_ghe_managed %} を使用すると、一連の機能と認定でセキュリティとコンプライアンスの目標を達成することもできます。 + +### 高可用性および地球規模のクラウド + +{% data variables.product.prodname_ghe_managed %} は、高可用性アーキテクチャでホストされているフルマネージドサービスです。 {% data variables.product.prodname_ghe_managed %} は、クラウドでグローバルにホストされており、無制限に開発ライフサイクル全体をサポートするように拡張できます。 {% data variables.product.prodname_dotcom %} は、バックアップ、フェイルオーバー、およびシステム災害復旧を完全に管理するため、サービスやデータについて心配する必要はありません。 + +### データの常駐 + +すべてのデータは、ユーザが選択したリージョン内で保存されます。 すべてのデータを選択したリージョン内に保存することで、GDPR およびグローバルデータ保護基準に準拠できます。 + +### 指定の条件下での暗号化 + +すべての顧客データは保存時に暗号化され、暗号化ポリシーに基づいてデータを暗号化するための独自の暗号化キーを提供できます。 キーとすべてのデータへのアクセスを制御できます。 詳しい情報については、「[Enterprise 向けのデータ暗号化を設定する](/admin/configuration/configuring-data-encryption-for-your-enterprise)」を参照してください。 + +### 分離されたアカウント + +すべての開発者アカウントは、{% data variables.product.prodname_ghe_managed %} 内で完全に分離されています。 SAML シングルサインオンを必須として、アイデンティティプロバイダを介してアカウントを完全に制御できます。 SCIM を使用すると、中央のアイデンティティ管理システムで定義されているように、従業員が必要なリソースにのみアクセスできるようにすることができます。 詳しい情報については、「[Enterprise のアイデンティティとアクセスを管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise)」を参照してください。 + +### 制限付きネットワークアクセス + +ネットワークアクセスが制限された {% data variables.product.prodname_ghe_managed %} での Enterprise への安全なアクセスにより、データはネットワーク内からのみアクセスできます。 詳しい情報については、「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/restricting-network-traffic-to-your-enterprise)」を参照してください。 + +### 商用および政府環境 + +{% data variables.product.prodname_ghe_managed %} は、Azure Government クラウドという、米国政府機関とそのパートナー向けの信頼できるクラウドで利用できます。 {% data variables.product.prodname_ghe_managed %} は商用クラウドでも利用できるため、Organization に適したホスティング環境を選択できます。 + +### Premium Plus サポート + +Premium Plus サポートは、すべての {% data variables.product.prodname_ghe_managed %} のお客様にご利用いただけます。これにより、最速かつ最もパーソナルなサポートエクスペリエンスを確実に実現できます。 専任の営業チームがお客様と協力して、{% data variables.product.prodname_dotcom %} を最大限に活用できるよう支援します。 当社のサポートチームは、可能な限り短時間で、いつでも問題を解決します。 + +### {% data variables.product.prodname_ghe_managed %}の支払いについて + +{% data reusables.github-ae.about-billing %} 詳しい情報については、「[Enterprise の支払いを管理する](/admin/overview/managing-billing-for-your-enterprise)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md b/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md index 923bed085a..5669d51f05 100644 --- a/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md +++ b/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md @@ -1,6 +1,6 @@ --- -title: About the GitHub Enterprise API -intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.' +title: GitHub Enterprise API について +intro: '{% data variables.product.product_name %} は、REST および GraphQL API をサポートしています。' redirect_from: - /enterprise/admin/installation/about-the-github-enterprise-server-api - /enterprise/admin/articles/about-the-enterprise-api/ @@ -13,12 +13,12 @@ versions: github-ae: '*' --- -With the APIs, you can automate many administrative tasks. 例えば、 +API を使用すると、さまざまなタスクを自動化できます。 例えば、 {% if enterpriseServerVersions contains currentVersion %} - {% data variables.enterprise.management_console %} に変更を加える。 詳しい情報については、「[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)」を参照してください。 - LDAP 同期を設定する。 詳しい情報については、「[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)」を参照してください。{% endif %} -- Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)." +- 自分の Enterprise に関する統計を収集する。 詳しい情報については、「[管理統計](/rest/reference/enterprise-admin#admin-stats)」を参照してください。 - Enterpriseアカウントの管理。 詳しい情報については「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。 -For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). +{% data variables.product.prodname_enterprise_api %} の完全なドキュメントについては、[{% data variables.product.prodname_dotcom %}REST API](/rest) および [{% data variables.product.prodname_dotcom%}GraphQL API](/graphql) を参照してください。 diff --git a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md index 76ae50c528..71fc1771d3 100644 --- a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md @@ -1,32 +1,32 @@ --- -title: About upgrades to new releases -shortTitle: About upgrades -intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +title: 新しいリリースへのアップグレードについて +shortTitle: アップグレードについて +intro: 'Enterprise を新しくリリースされたバージョンにアップグレードすると、新機能を備え、バグが修正された {% data variables.product.product_name %} を利用できます。' versions: enterprise-server: '>=3.0' --- -{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. +{% data variables.product.product_name %} は常に改善されており、メジャーリリースとマイナーリリースで新機能とバグ修正が導入されています。 -Major releases include new functionality and feature upgrades and typically occur quarterly. +通常、メジャーリリースは四半期ごとに行われ、新機能と機能のアップグレードが含まれます。 -Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. +{% data variables.product.prodname_ghe_server %} 3.0 以降、すべてのメジャーリリースは少なくとも 1 つのリリース候補から始まります。 リリース候補は、完全な機能一式を備えたメジャーリリースとして提案されています。 リリース候補には、実際に {% data variables.product.product_name %} を使用している顧客からのフィードバックを通じてのみ見つけることができるバグまたは問題がある可能性があります。 -You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." +リリース候補が利用可能になり次第、リリース候補をテストすることで、最新の機能に早期アクセスできます。 サポートされているバージョンからリリース候補にアップグレードでき、リリース時にリリース候補からそれ以降のバージョンにアップグレードできます。 リリースが一般に利用可能になり次第、リリース候補を実行している環境をアップグレードする必要があります。 詳しい情報については、「[アップグレード要件](/admin/enterprise-management/upgrade-requirements)」を参照してください。 -Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." +リリース候補は、テスト環境またはステージング環境に展開する必要があります。 リリース候補をテストした際は、サポートに連絡してフィードバックをご提供ください。 詳しい情報については、「[{% data variables.contact.github_support %} での操作](/admin/enterprise-support)」を参照してください。 -We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. +フィードバックを活用して、バグ修正やその他の必要な変更を適用し、安定した本番リリースを作成します。 新しいリリース候補ごとに、以前のバージョンで見つかった問題のバグ修正が追加されます。 リリースが広く普及可能になったら、{% data variables.product.company_short %} は安定した本番リリースを公開します。 {% warning %} -**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." +**Warning**: 新しいメジャーリリースにアップグレードすると、数時間のダウンタイムが発生し、その間、どのユーザも Enterprise を使用できなくなります。 Enterprise 設定または REST API を使用して、グローバルアナウンスバナーを公開することにより、ダウンタイムについてユーザに通知できます。 詳しい情報については、「[インスタンス上でのユーザメッセージをカスタマイズする](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)」および「[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)」を参照してください。 {% endwarning %} -Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. +マイナーリリースは、ホットパッチとバグ修正のみで構成されており、より頻繁に発生します。 マイナーリリースは通常、最初のリリース時に利用可能になっています。リリース候補はありません。 マイナーリリースへのアップグレードには、通常 5 分未満のダウンタイムが発生します。 -To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +Enterprise を新しいリリースにアップグレードするには、「[リリースノート](/enterprise-server/admin/release-notes)」および「[{% data variables.product.prodname_ghe_server %} へのアップグレード](/admin/enterprise-management/upgrading-github-enterprise-server)」を参照してください。 ### 参考リンク diff --git a/translations/ja-JP/content/admin/overview/index.md b/translations/ja-JP/content/admin/overview/index.md index cf2e674ef8..7509b7143a 100644 --- a/translations/ja-JP/content/admin/overview/index.md +++ b/translations/ja-JP/content/admin/overview/index.md @@ -1,6 +1,6 @@ --- title: 概要 -intro: 'You can learn about {% data variables.product.product_name %} and manage{% if enterpriseServerVersions contains currentVersion %} accounts and access, licenses, and{% endif %} billing.' +intro: '{% data variables.product.product_name %} について学び、{% if enterpriseServerVersions contains currentVersion %}アカウントとアクセス、ライセンス、{% endif %}支払いを管理できます。' redirect_from: - /enterprise/admin/overview versions: @@ -12,6 +12,7 @@ versions: ### 目次 +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} diff --git a/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md index af02eb59f0..249f855ee6 100644 --- a/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Managing billing for your enterprise -intro: 'You can view billing information for your enterprise.' +title: Enterprise の支払いを管理する +intro: 'Enterprise の支払情報を確認できます。' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /enterprise/admin/installation/managing-billing-for-github-enterprise @@ -13,26 +13,26 @@ versions: {% if currentVersion == "github-ae@latest" %} -{% data reusables.github-ae.about-billing %} Once per day, {% data variables.product.prodname_dotcom %} will count the number of users with a license for your enterprise. {% data variables.product.company_short %} bills you for each licensed user regardless of whether the user logged into {% data variables.product.prodname_ghe_managed %} that day. +{% data reusables.github-ae.about-billing %} 1日に1度、{% data variables.product.prodname_dotcom %} は、Enterprise のライセンスを持つユーザ数をカウントします。 {% data variables.product.company_short %} は、ユーザがその日に {% data variables.product.prodname_ghe_managed %} にログインしたかどうかに関係なく、ライセンスされたユーザごとに請求します。 -For commercial regions, the price per user per day is $1.2580645161. For 31-day months, the monthly cost for each user is $39. For months with fewer days, the monthly cost is lower. Each billing month begins at a fixed time on the first day of the calendar month. +商業地域の場合、ユーザー1人あたりの1日あたりの価格は $ 1.2580645161 です。 31日間の場合、各ユーザの月額料金は 39 ドルです。 日数が少ない月の場合、月額料金は低くなります。 各支払い月は、カレンダー月の初日の固定の時刻に開始されます。 -If you add a licensed user mid-month, that user will only be included in the count for the days they have a license. When you remove a licensed user, that user will remain in the count until the end of that month. Therefore, if you add a user mid-month and later remove the user in the same month, the user will be included in the count from the day the user was added through the end of the month. There is no additional cost if you re-add a user during the same month the user was removed. +月の半ばにライセンスユーザを追加した場合、そのユーザはライセンスを付与された日からカウントされます。 ライセンスユーザを削除した場合、そのユーザは削除された月の末までカウントされます。 したがって、月の途中でユーザを追加し、その後、同じ月にユーザを削除した場合、そのユーザは、ユーザが追加された日から月末までカウントされます。 同じ月に、ユーザを削除して再度追加した場合、追加料金は発生しません。 -For example, here are the costs for users with licenses on different dates. +たとえば、異なる日付でライセンスを付与した場合のユーザ料金は次のとおりです。 -| ユーザ | License dates | Counted days | Cost | -| --------- | ------------------------------------------------------- | ------------ | ------ | -| @octocat | January 1 - January 31 | 31 | $39 | -| @robocat | February 1 - February 28 | 29 | $35.23 | -| @devtocat | January 15 - January 31 | 17 | $21.39 | -| @doctocat | January 1 - January 15 | 31 | $39 | -| @prodocat | January 7 - January 15 | 25 | $31.45 | -| @monalisa | January 1 - January 7,
    January 15 - January 31 | 31 | $39 | +| ユーザ | ライセンスされた日 | カウント日数 | 料金 | +| --------- | ------------------------------- | ------ | ------ | +| @octocat | 1月1日～1月31日 | 31 | $39 | +| @robocat | 2月1日～2月28日 | 29 | $35.23 | +| @devtocat | 1月15日～1月31日 | 17 | $21.39 | +| @doctocat | 1月1日～1月15日 | 31 | $39 | +| @prodocat | 1月7日～1月15日 | 25 | $31.45 | +| @monalisa | 1月1日～1月7日、
    1月15日～1月31日 | 31 | $39 | -Your enterprise can include one or more instances. {% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day. +Enterprise には、1つ以上のインスタンスを含めることができます。 {% data variables.product.prodname_ghe_managed %} のインスタンスごとの最小ユーザ数は 500 です。 {% data variables.product.company_short %} は、同日にライセンスを付与されたユーザが 500 未満の場合でも、インスタンスごとに最低 500 ユーザ分の料金を請求します。 -You can see your current usage in your [Azure account portal](https://portal.azure.com). +[Azure アカウントポータル](https://portal.azure.com)で現在の使用状況を確認できます。 {% else %} @@ -40,7 +40,7 @@ You can see your current usage in your [Azure account portal](https://portal.azu 現時点では、Enterprise アカウントは請求書で支払いを行っている {% data variables.product.prodname_enterprise %} のお客様が利用できます。 Enterprise アカウントに接続されているすべての Organization と {% data variables.product.prodname_ghe_server %} インスタンスの支払いは、すべての有料の {% data variables.product.prodname_dotcom_the_website %} サービス（Organization の有料ライセンス、{% data variables.large_files.product_name_long %}データパック、および {% data variables.product.prodname_marketplace %} アプリケーションのプランを含む）に対する単一の支払い料金に集約されます。 -Enterprise オーナーと支払いマネージャーは、Enterprise アカウントの支払い設定すべてに対するアクセスおよび管理が可能です。 For more information about enterprise accounts, {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)."For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Enterprise オーナーと支払いマネージャーは、Enterprise アカウントの支払い設定すべてに対するアクセスおよび管理が可能です。 Enterprise アカウントの詳細については、{% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}「[Enterprise のロール](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)」および{% endif %}「[Organization のリポジト権限レベル](/articles/repository-permission-levels-for-an-organization)」を参照してください。支払いマネージャー管理の詳細については、「[Enterprise アカウントを管理するようユーザを招待する](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)」を参照してください。 ### 現在の請求書を表示する diff --git a/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md b/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md index 170cb17565..3d5c7f78ad 100644 --- a/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ versions: {% data reusables.enterprise-accounts.license-tab %} 12. [Quick links] で [**Update license**] をクリックする。 ![ライセンス更新のリンク](/assets/images/enterprise/business-accounts/update-license-link.png) 13. ライセンスを選択するには、[**License file**] をクリックするか、ライセンスファイルを [**License file**] にドラッグします。 ![ライセンスファイルのアップロード](/assets/images/enterprise/management-console/upload-license.png) -14. [**Upload**] をクリックします。 ![アップグレードを開始](/assets/images/enterprise/management-console/begin-upload.png) +14. [**Upload**] をクリックします。 ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %} ### ライセンス使用状況を表示する @@ -52,11 +54,11 @@ versions: ### ユーザライセンスの使用状況を自動で{% data variables.product.prodname_ghe_cloud %}と同期する -{% data variables.product.prodname_github_connect %} を使用して、{% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_ghe_cloud %} の間でユーザライセンスの数と使用状況を自動で同期できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_ghe_cloud %} の間で自動ユーザライセンス同期を有効化する](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)」を参照してください。 +{% data variables.product.prodname_github_connect %}を使用して、{% data variables.product.prodname_ghe_server %}と{% data variables.product.prodname_ghe_cloud %}の間でユーザライセンスの数と使用状況を自動で同期できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_ghe_cloud %} の間で自動ユーザライセンス同期を有効化する](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)」を参照してください。 ### {% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_ghe_cloud %} の間でユーザライセンスの使用状況を手動で同期する -{% data variables.product.prodname_ghe_server %} から JSON ファイルをダウンロードして {% data variables.product.prodname_ghe_cloud %} にそのファイルをアップロードし、2 つのデプロイメント間でユーザライセンスの使用状況を手動で同期できます。 +{% data variables.product.prodname_ghe_server %}からJSONファイルをダウンロードして{% data variables.product.prodname_ghe_cloud %}にそのファイルをアップロードし、2つのデプロイメント間でユーザライセンスの使用状況を手動で同期できます。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} @@ -70,3 +72,23 @@ versions: {% data reusables.enterprise-accounts.license-tab %} 10. [Enterprise Server Instances] の下で、[**Add server usage**] をクリックします。 ![GitHub Enterprise Serversの使用状況リンクをアップロードする](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. {% data variables.product.prodname_ghe_server %}からダウンロードしたJSONファイルをアップロードします。 ![アップロードするファイルをドラッグアンドドロップまたは選択する](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### トラブルシューティング + +In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Restart the services for Git authentication and the HTTP server. + + {% warning %} + + **Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again. + +{% endif %} diff --git a/translations/ja-JP/content/admin/overview/system-overview.md b/translations/ja-JP/content/admin/overview/system-overview.md index 3d393fc5b7..905ee9777d 100644 --- a/translations/ja-JP/content/admin/overview/system-overview.md +++ b/translations/ja-JP/content/admin/overview/system-overview.md @@ -77,7 +77,7 @@ versions: #### 外部サービスおよびサポートへのアクセス -{% data variables.product.prodname_ghe_server %} は、お客様のネットワークから外部サービスにアクセスすることなしに運用できます。 また、メール配信、外部モニタリング、およびログ転送のため、外部サービスとのインテグレーションを有効にすることも可能です。 For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)," "[Setting up external monitoring](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)," and "[Log forwarding](/admin/user-management/log-forwarding)." +{% data variables.product.prodname_ghe_server %} は、お客様のネットワークから外部サービスにアクセスすることなしに運用できます。 また、メール配信、外部モニタリング、およびログ転送のため、外部サービスとのインテグレーションを有効にすることも可能です。 詳しい情報については、「[通知のためのメール設定](/admin/configuration/configuring-email-for-notifications)」、「[外部モニタリングのセットアップ](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)」、「[ログの転送](/admin/user-management/log-forwarding)」を参照してください。 トラブルシューティングデータを手動で収集し、{% data variables.contact.github_support %} に送信できます。 詳しい情報については、「[{% data variables.contact.github_support %} へのデータ提供](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)」を参照してください。 @@ -108,7 +108,7 @@ versions: #### 監査およびアクセスのログ取得 -{% data variables.product.prodname_ghe_server %} は、従来型オペレーティングシステムおよびアプリケーションの両方のログを保存します。 また、アプリケーションは詳細な監査およびセキュリティログも記録し、{% data variables.product.prodname_ghe_server %} はこれを永続的に保存します。 `syslog-ng` プロトコルにより、両タイプのログをリアルタイムで複数の宛先に転送できます。 For more information, see "[Log forwarding](/admin/user-management/log-forwarding)." +{% data variables.product.prodname_ghe_server %} は、従来型オペレーティングシステムおよびアプリケーションの両方のログを保存します。 また、アプリケーションは詳細な監査およびセキュリティログも記録し、{% data variables.product.prodname_ghe_server %} はこれを永続的に保存します。 `syslog-ng` プロトコルにより、両タイプのログをリアルタイムで複数の宛先に転送できます。 詳しい情報については、「[ログの転送](/admin/user-management/log-forwarding)」を参照してください。 アクセスログと監査ログには、以下のような情報が含まれています。 diff --git a/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md index b9ef095954..c4f03f20c5 100644 --- a/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -58,7 +58,8 @@ pre-receiveスクリプトの`終了ステータス`は、プッシュが受け | $GITHUB_VIA | ref の作成に使われた方式。
    **取り得る値: **
    - `auto-merge deployment api`
    - `blob edit`
    - `branch merge api`
    - `branches page delete button`
    - `git refs create api`
    - `git refs delete api`
    - `git refs update api`
    - `merge api`
    - `pull request branch delete button`
    - `pull request branch undo button`
    - `pull request merge api`
    - `pull request merge button`
    - `pull request revert button`
    - `releases delete button`
    - `stafftools branch restore`
    - `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | クライアントによって送信されたプッシュオプション数。 プッシュオプションに関する詳しい情報については、Gitのドキュメンテーションの[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)を参照してください。 | | $GIT_PUSH_OPTION_N | ここで N は 0 から始まる整数で、この変数にはクライアントから送信されたプッシュオプションの文字列が含まれます。 送信された最初のオプションはGIT_PUSH_OPTION_0に保存され、2番目のオプションはGIT_PUSH_OPTION_1に保存され、といったようになります。 プッシュオプションに関する詳しい情報については、Gitのドキュメンテーションの[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)を参照してください。 |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | 変更をプッシュしたクライアントから送信されたユーザエージェント文字列型。 |{% endif %} +| $GIT_USER_AGENT | 変更をプッシュしたクライアントから送信されたユーザエージェント文字列型。 +{% endif %} ### 権限の設定と {% data variables.product.prodname_ghe_server %} への pre-receive フックのプッシュ @@ -93,30 +94,30 @@ pre-receive フックスクリプトは、{% data variables.product.prodname_ghe 2. 以下を含む `Dockerfile.dev` というファイルを作成してください。 - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. `always_reject.sh` というテストのpre-receiveスクリプトを作成してください。 このスクリプト例では、全てのプッシュを拒否します。これは、リポジトリをロックする場合に役立ちます。 + 3. `always_reject.sh` というテストのpre-receiveスクリプトを作成してください。 このスクリプト例では、全てのプッシュを拒否します。これは、リポジトリをロックする場合に役立ちます。 - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 diff --git a/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md index 5885c0a28f..f291a34945 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md @@ -30,11 +30,11 @@ versions: github-ae: '*' --- -### Configuring the default visibility of new repositories in your enterprise +### Enterprise 内の新しいリポジトリのデフォルトの可視性を設定する -Each time someone creates a new repository on your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. リポジトリの可視性に関する詳しい情報については、「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 +ユーザが Enterprise に新しいリポジトリを作成するたびに、そのユーザはリポジトリの可視性を選択する必要があります。 その Enterprise のデフォルトの可視性の設定をする際には、デフォルトで選択される可視性を選択します。 リポジトリの可視性に関する詳しい情報については、「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 -If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)." +Enterprise オーナーがメンバーによる特定のタイプのリポジトリの作成を禁止している場合、可視性設定がデフォルトでそのタイプに設定されていても、メンバーはそのタイプのリポジトリを作成できません。 詳しい情報については、「[リポジトリ作成のためのポリシーを設定する](#setting-a-policy-for-repository-creation)」を参照してください。 {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -43,15 +43,15 @@ If an enterprise owner disallows members from creating certain types of reposito {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -1. "Default repository visibility（デフォルトのリポジトリの可視性）"の下で、ドロップダウンメニューを使ってデフォルトの可視性を選択してください。![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) +1. "Default repository visibility（デフォルトのリポジトリの可視性）"の下で、ドロップダウンメニューを使ってデフォルトの可視性を選択してください。![Enterprise におけるデフォルトのリポジトリの可視化性を選択するためのドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) {% data reusables.enterprise_installation.image-urls-viewable-warning %} ### リポジトリの可視性を変更するためのポリシーを設定する -When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository. +メンバーがリポジトリの可視性を変更できないようにした場合、Enterprise のオーナーのみがリポジトリの可視性を変更できます。 -If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)." +Enterprise のオーナーがリポジトリの作成を Organization のオーナーのみに制限している場合、メンバーはリポジトリの可視性を変更できません。 Enterprise のオーナーがメンバーリポジトリの作成をプライベートリポジトリのみに制限している場合、メンバーはリポジトリの可視性をプライベートにのみ変更できます。 詳しい情報については、「[リポジトリ作成のためのポリシーを設定する](#setting-a-policy-for-repository-creation)」を参照してください。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -77,7 +77,7 @@ If an enterprise owner has restricted repository creation to organization owners ### プライベートまたは内部リポジトリのフォークに関するポリシーを施行する -Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level. +Enterprise が所有しているすべての Organization 全体で、ユーザーにリポジトリのフォーク用にプライベートまたは内部リポジトリへのアクセスを許可したり、プライベートまたは内部リポジトリのフォークを一切禁止したり、オーナーが Organization レベルで設定を管理できるようにしたりすることができます。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -95,7 +95,7 @@ Across all organizations owned by your enterprise, you can allow people with acc ### Git プッシュ制限のためのポリシーを設定する -To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise. +リポジトリのサイズを管理しやすくして、パフォーマンスの問題を防ぐために、Enterprise 内のリポジトリのファイルサイズ制限を設定できます。 デフォルトでは、リポジトリのアップロード制限を適用すると、100MB以上のファイルの追加やアップロードができなくなります。 @@ -115,7 +115,7 @@ To keep your repository size manageable and prevent performance issues, you can {% endif %} {% data reusables.enterprise-accounts.options-tab %} 4. [Repository upload limit] で、ドロップダウンメニューを使用して最大オブジェクトサイズをクリックします。 ![最大オブジェクトサイズのオプションを備えたドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png) -5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories** ![すべてのリポジトリにオブジェクトの最大サイズを適用するオプション](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) +5. 必要に応じて、すべてのリポジトリにアップロードの最大制限を適用するには [**Enforce on all repositories**] を選択します。 ![すべてのリポジトリにオブジェクトの最大サイズを適用するオプション](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) ### リポジトリ間のプルリクエストのためのマージコンフリクトエディタを設定する @@ -132,7 +132,7 @@ To keep your repository size manageable and prevent performance issues, you can ### フォースプッシュを設定する -それぞれのリポジトリは、所属するユーザアカウントもしくはOraganizationの設定から、デフォルトのフォースプッシュの設定を引き継ぎます。 Likewise, each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, it will change for all repositories owned by any user or organization. +それぞれのリポジトリは、所属するユーザアカウントもしくはOraganizationの設定から、デフォルトのフォースプッシュの設定を引き継ぎます。 同様に、それぞれの Organization およびユーザアカウントは、デフォルトのフォースプッシュの設定をアプライアンス全体のフォースプッシュの設定から引き継ぎます。 Enterprise のフォースプッシュの設定を変更すると、すべてのユーザあるいは Organization が所有するすべてのリポジトリが変更されます。 #### アプライアンス上でのすべてのフォースプッシュをブロックする @@ -160,7 +160,7 @@ To keep your repository size manageable and prevent performance issues, you can #### ユーザアカウントもしくはOrganizationが所有するリポジトリへのフォースプッシュのブロック -リポジトリは、所属するユーザアカウントもしくはOrganizationからフォースプッシュの設定を引き継ぎます。 User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise. +リポジトリは、所属するユーザアカウントもしくはOrganizationからフォースプッシュの設定を引き継ぎます。 そして、それぞれの Organization およびユーザアカウントは、フォースプッシュの設定を Enterprise のフォースプッシュの設定から引き継ぎます。 引き継がれたデフォルトの設定は、ユーザアカウントもしくはOrganizationの設定をすることで上書きできます。 @@ -173,7 +173,7 @@ To keep your repository size manageable and prevent performance issues, you can 5. [Repository default settings（リポジトリのデフォルト設定）] の下の [Force pushes（フォースプッシュ）] セクションで、以下から選択してください。 - [**Block（ブロック）**] ですべてのブランチへのフォースプッシュがブロックされます。 - [**Block to the default branch（デフォルトブランチへのブロック）**] でデフォルトブランチへのフォースプッシュのみがブロックされます。 ![フォースプッシュのブロック](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png) -6. **Enforce on all repositories（すべてのリポジトリに対して強制）**を選択して、リポジトリ固有の設定を上書きすることもできます。 Note that this will **not** override an enterprise-wide policy. ![フォースプッシュのブロック](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) +6. **Enforce on all repositories（すべてのリポジトリに対して強制）**を選択して、リポジトリ固有の設定を上書きすることもできます。 これは、Enterprise 全体のポリシーを**上書きしません**のでご注意ください。 ![フォースプッシュのブロック](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) {% if enterpriseServerVersions contains currentVersion %} @@ -181,11 +181,11 @@ To keep your repository size manageable and prevent performance issues, you can {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} -{% if enterpriseServerVersions contains currentVersion %}If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your enterprise, you {% else %}You {% endif %}can allow repository administrators to enable anonymous Git read access to public repositories. +{% if enterpriseServerVersions contains currentVersion %} Enterprise で[プライベートモードを有効化](/enterprise/admin/configuration/enabling-private-mode)している場合は、{% else %}{% endif %}リポジトリ管理者がパブリックリポジトリへの匿名 Git 読み取りアクセスを有効化できるようにすることができます。 -Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. あなたもしくはリポジトリ管理者がこのアクセス設定をリポジトリで有効化すると、認証を受けていない Git の操作 (そして {% data variables.product.product_name %} へのネットワークアクセスができる人はだれでも) は、認証なしでリポジトリに読み取りアクセスできることになります。 +匿名 Git 読み取りアクセスを有効化すると、ユーザは Enterprise 上のカスタムツールの認証をバイパスできるようになります。 あなたもしくはリポジトリ管理者がこのアクセス設定をリポジトリで有効化すると、認証を受けていない Git の操作 (そして {% data variables.product.product_name %} へのネットワークアクセスができる人はだれでも) は、認証なしでリポジトリに読み取りアクセスできることになります。 -If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. リポジトリのGit読み取りアクセス設定をロックすると、サイト管理者だけがこの設定を変更できるようになります。 +必要に応じて、リポジトリのアクセス設定をロックすることで、リポジトリ管理者が Enterprise のリポジトリの匿名 Git アクセス設定を変更不可にすることができます。 リポジトリのGit読み取りアクセス設定をロックすると、サイト管理者だけがこの設定を変更できるようになります。 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %} @@ -201,7 +201,7 @@ If necessary, you can prevent repository administrators from changing anonymous {% endif %} {% data reusables.enterprise-accounts.options-tab %} 4. [Anonymous Git read access（匿名 Git 読み取りアクセス）] の下で、ドロップダウンメニューを使って [**Enabled（有効化）**] をクリックしてください。 ![[Enabled] と [Disabled] のメニューオプションが表示されている [Anonymous Git read access] ドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png) -3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**. ![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) +3. Enterprise のすべてのリポジトリでリポジトリ管理者が匿名 Git 読み取りアクセス設定を変更するのを避けるために、[**Prevent repository admins from changing anonymous Git read access**] を選択することもできます。 ![Enterprise のすべてのリポジトリへの匿名 Git 読み取りアクセス設定をリポジトリ管理者が変更するのを避けるための選択チェックボックス](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) #### 特定のリポジトリでの匿名 Git 読み取りアクセスを設定する diff --git a/translations/ja-JP/content/admin/release-notes.md b/translations/ja-JP/content/admin/release-notes.md index 4fedc31ab9..034895d7f3 100644 --- a/translations/ja-JP/content/admin/release-notes.md +++ b/translations/ja-JP/content/admin/release-notes.md @@ -1,6 +1,6 @@ --- title: リリースノート -intro: The release notes for {{ allVersions[currentVersion].versionTitle }}. +intro: '{{ allVersions[currentVersion].versionTitle }} のリリースノートです。' layout: release-notes versions: enterprise-server: '*' diff --git a/translations/ja-JP/content/admin/user-management/activity-dashboard.md b/translations/ja-JP/content/admin/user-management/activity-dashboard.md index 1c77df010b..609280a4e6 100644 --- a/translations/ja-JP/content/admin/user-management/activity-dashboard.md +++ b/translations/ja-JP/content/admin/user-management/activity-dashboard.md @@ -1,6 +1,6 @@ --- title: アクティビティダッシュボード -intro: 'The Activity dashboard gives you an overview of all the activity in your enterprise.' +intro: 'アクティビティダッシュボードで、Enterprise 内のすべてのアクティビティの概要を確認できます。' redirect_from: - /enterprise/admin/articles/activity-dashboard/ - /enterprise/admin/installation/activity-dashboard @@ -24,8 +24,8 @@ versions: ![アクティビティダッシュボード](/assets/images/enterprise/activity/activity-dashboard-yearly.png) {% if enterpriseServerVersions contains currentVersion %} -For more analytics based on data from -{% data variables.product.product_name %}, you can purchase {% data variables.product.prodname_insights %}. 詳しい情報については、「[{% data variables.product.prodname_insights %} について](/insights/installing-and-configuring-github-insights/about-github-insights)」を参照してください。 +- +{% data variables.product.product_name %} のデータに基づく詳細な分析については、{% data variables.product.prodname_insights %} を購入できます。 詳しい情報については、「[{% data variables.product.prodname_insights %} について](/insights/installing-and-configuring-github-insights/about-github-insights)」を参照してください。 {% endif %} ### アクティビティダッシュボードへのアクセス diff --git a/translations/ja-JP/content/admin/user-management/audit-logging.md b/translations/ja-JP/content/admin/user-management/audit-logging.md index eb2fc84114..48dfedfd1c 100644 --- a/translations/ja-JP/content/admin/user-management/audit-logging.md +++ b/translations/ja-JP/content/admin/user-management/audit-logging.md @@ -1,6 +1,6 @@ --- title: 監査ログ -intro: '{% data variables.product.product_name %} keeps logs of audited{% if enterpriseServerVersions contains currentVersion %} system,{% endif %} user, organization, and repository events. ログはデバッグや内部および外部のコンプライアンスに役立ちます。' +intro: '{% data variables.product.product_name %} は、{% if enterpriseServerVersions contains currentVersion %}監査対象システム、{% endif %}ユーザ、Organization、リポジトリのイベントのログを保持します。 ログはデバッグや内部および外部のコンプライアンスに役立ちます。' redirect_from: - /enterprise/admin/articles/audit-logging/ - /enterprise/admin/installation/audit-logging @@ -10,22 +10,22 @@ versions: github-ae: '*' --- -For a full list, see "[Audited actions](/admin/user-management/audited-actions)." For more information on finding a particular action, see "[Searching the audit log](/admin/user-management/searching-the-audit-log)." +完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 特定のアクションを見つける方法について詳しくは、「[Audit log を検索する](/admin/user-management/searching-the-audit-log)」を参照してください。 ### プッシュのログ -Git プッシュ操作はすべてログに記録されます。 For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)." +Git プッシュ操作はすべてログに記録されます。 詳しい情報については、「[プッシュログを表示する](/admin/user-management/viewing-push-logs)」を参照してください。 {% if enterpriseServerVersions contains currentVersion %} ### システムイベント すべてのプッシュとプルを含む監査されたすべてのシステムイベントは、`/var/log/github/audit.log` に記録されます。 ログは 24 時間ごとに自動的に交換され、7 日間保持されます。 -Support Bundle にはシステムログが含まれています。 For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)." +Support Bundle にはシステムログが含まれています。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Support にデータを提供する](/admin/enterprise-support/providing-data-to-github-support)」を参照してください。 ### Support Bundle -すべての監査情報は、Support Bundle の `github-logs` ディレクトリにある `audit.log` ファイルに記録されます。 ログの転送が有効な場合、[Splunk](http://www.splunk.com/) や [Logstash](http://logstash.net/) などの外部の syslog ストリーミングコンシューマに、このデータをストリーミングすることができます。 このログからのすべてのエントリは、`github_audit` キーワードでフィルタリングできます。 For more information see "[Log forwarding](/admin/user-management/log-forwarding)." +すべての監査情報は、Support Bundle の `github-logs` ディレクトリにある `audit.log` ファイルに記録されます。 ログの転送が有効な場合、[Splunk](http://www.splunk.com/) や [Logstash](http://logstash.net/) などの外部の syslog ストリーミングコンシューマに、このデータをストリーミングすることができます。 このログからのすべてのエントリは、`github_audit` キーワードでフィルタリングできます。 詳しい情報については、「[ログの転送](/admin/user-management/log-forwarding)」を参照してください。 たとえば、次のエントリは新規リポジトリが作成されたことを示しています。 diff --git a/translations/ja-JP/content/admin/user-management/audited-actions.md b/translations/ja-JP/content/admin/user-management/audited-actions.md index df39cc1fb1..88ae1b7d20 100644 --- a/translations/ja-JP/content/admin/user-management/audited-actions.md +++ b/translations/ja-JP/content/admin/user-management/audited-actions.md @@ -12,18 +12,18 @@ versions: #### 認証 -| 名前 | 説明 | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------- | -| `oauth_access.create` | ユーザアカウントに[OAuth アクセストークン][] が[作成][generate token] されました。 | -| `oauth_access.destroy` | [OAuth アクセストークン][] がユーザアカウントから削除されました。 | -| `oauth_application.destroy` | [OAuth application][]がユーザまたは Organization のアカウントから削除されました。 | -| `oauth_application.reset_secret` | [OAuth アプリケーション][]の秘密鍵がリセットされました。 | -| `oauth_application.transfer` | [OAuth アプリケーション][]が別のユーザ、または Organization のアカウントへ移されました。 | -| `public_key.create` | SSHキーがユーザアカウントに[追加][add key]されたか[デプロイキー][]がリポジトリに追加されました。 | -| `public_key.delete` | SSHキーがユーザアカウントから削除されたか[デプロイキー][]がリポジトリから削除されました。 | -| `public_key.update` | A user account's SSH key or a repository's [deploy key][] was updated.{% if enterpriseServerVersions contains currentVersion %} -| `two_factor_authentication.enabled` | ユーザアカウントの[二段階認証][2fa]が有効化されました。 | -| `two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %} +| 名前 | 説明 | +| ------------------------------------:| ----------------------------------------------------------------------------------------------------- | +| `oauth_access.create` | ユーザアカウントに[OAuth アクセストークン][] が[作成][generate token] されました。 | +| `oauth_access.destroy` | [OAuth アクセストークン][] がユーザアカウントから削除されました。 | +| `oauth_application.destroy` | [OAuth application][]がユーザまたは Organization のアカウントから削除されました。 | +| `oauth_application.reset_secret` | [OAuth アプリケーション][]の秘密鍵がリセットされました。 | +| `oauth_application.transfer` | [OAuth アプリケーション][]が別のユーザ、または Organization のアカウントへ移されました。 | +| `public_key.create` | SSHキーがユーザアカウントに[追加][add key]されたか[デプロイキー][]がリポジトリに追加されました。 | +| `public_key.delete` | SSHキーがユーザアカウントから削除されたか[デプロイキー][]がリポジトリから削除されました。 | +| `public_key.update` | ユーザアカウントの SSH キーまたはリポジトリの[デプロイキー][]が更新されました。{% if enterpriseServerVersions contains currentVersion %} +| `two_factor_authentication.enabled` | ユーザアカウントの[二段階認証][2fa]が有効化されました。 | +| `two_factor_authentication.disabled` | ユーザアカウントの [2 要素認証][2fa]が無効になりました。{% endif %} #### フック @@ -34,66 +34,66 @@ versions: | `hook.destroy` | フックが削除されました。 | | `hook.events_changed` | フックの設定されているイベントが変更されました。 | -#### Enterprise configuration settings +#### Enterprise 設定 -| 名前 | 説明 | -| -------------------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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)." | -| `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)."{% if enterpriseServerVersions contains currentVersion %} -| `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 %} +| 名前 | 説明 | +| -------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `business.update_member_repository_creation_permission` | サイトアドミンは、Enterprise 内の Organization でのリポジトリの作成を制限します。 詳しい情報については、「[Enterprise でのリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。 | +| `business.clear_members_can_create_repos` | サイトアドミンは、Enterprise 内の Organization でのリポジトリ作成の制限を解除します。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。{% if enterpriseServerVersions contains currentVersion %} +| `enterprise.config.lock_anonymous_git_access` | サイトアドミンは匿名の Git 読み取りアクセスをロックして、リポジトリ管理者が Enterprise 内のリポジトリの既存の匿名 Git 読み取りアクセス設定を変更できないようにします。 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` | サイトアドミンは匿名 Git 読み取りアクセスのロックを解除して、リポジトリ管理者が Enterprise 内のリポジトリの既存の匿名 Git 読み取りアクセス設定を変更できるようにします。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。{% endif %} #### Issue およびプルリクエスト -| 名前 | 説明 | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------- | -| `issue.update` | Issue のテキスト本体（最初のコメント）が変更されました。 | -| `issue_comment.update` | Issue （最初以外）のコメントが変更されました。 | -| `pull_request_review_comment.delete` | A comment on a pull request was deleted. | -| `issue.destroy` | Issue がリポジトリから削除されました。 For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)." | +| 名前 | 説明 | +| ------------------------------------:| -------------------------------------------------------------------------------------------------------------------- | +| `issue.update` | Issue のテキスト本体（最初のコメント）が変更されました。 | +| `issue_comment.update` | Issue （最初以外）のコメントが変更されました。 | +| `pull_request_review_comment.delete` | A comment on a pull request was deleted. | +| `issue.destroy` | Issue がリポジトリから削除されました。 詳しい情報については、「[>Issue を削除する](/github/managing-your-work-on-github/deleting-an-issue)」を参照してください。 | #### Organization -| 名前 | 説明 | -| ------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org.async_delete` | ユーザが Organization を削除するための背景ジョブを開始しました。 | -| `org.delete` | An organization was deleted by a user-initiated background job.{% if currentVersion != "github-ae@latest" %} -| `org.transform` | ユーザアカウントが 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 %} +| 名前 | 説明 | +| ------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org.async_delete` | ユーザが Organization を削除するための背景ジョブを開始しました。 | +| `org.delete` | ユーザが開始したバックグラウンドジョブによって Organization が削除されました。{% if currentVersion != "github-ae@latest" %} +| `org.transform` | ユーザアカウントが Organization へと変換されました。 詳しい情報については、「[ユーザを Organization に変換する](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)」を参照してください。{% endif %} #### 保護されたブランチ -| 名前 | 説明 | -| ------------------------------------------------------------------:| ----------------------------------------------------------------- | -| `protected_branch.create` | ブランチ保護がブランチで有効になっています。 | -| `protected_branch.destroy` | ブランチ保護がブランチで無効になっています。 | -| `protected_branch.update_admin_enforced` | ブランチ保護がリポジトリ管理者に対して強制されます。 | -| `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review is updated on a branch. | -| `protected_branch.dismiss_stale_reviews` | 却下している古いプルリクエストの強制がブランチで更新されます。 | -| `protected_branch.update_signature_requirement_enforcement_level` | 必要なコミット署名の強制がブランチで更新されます。 | -| `protected_branch.update_pull_request_reviews_enforcement_level` | 必要なプルリクエストレビューの強制がブランチで更新されます。 | -| `protected_branch.update_required_status_checks_enforcement_level` | 必要なステータスチェックの強制がブランチで更新されます。 | -| `protected_branch.rejected_ref_update` | ブランチ更新の試行が拒否されます。 | -| `protected_branch.policy_override` | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされます。 | +| 名前 | 説明 | +| ------------------------------------------------------------------:| ---------------------------------- | +| `protected_branch.create` | ブランチ保護がブランチで有効になっています。 | +| `protected_branch.destroy` | ブランチ保護がブランチで無効になっています。 | +| `protected_branch.update_admin_enforced` | ブランチ保護がリポジトリ管理者に対して強制されます。 | +| `protected_branch.update_require_code_owner_review` | 必要なコードオーナーレビューの強制がブランチで更新されます。 | +| `protected_branch.dismiss_stale_reviews` | 却下している古いプルリクエストの強制がブランチで更新されます。 | +| `protected_branch.update_signature_requirement_enforcement_level` | 必要なコミット署名の強制がブランチで更新されます。 | +| `protected_branch.update_pull_request_reviews_enforcement_level` | 必要なプルリクエストレビューの強制がブランチで更新されます。 | +| `protected_branch.update_required_status_checks_enforcement_level` | 必要なステータスチェックの強制がブランチで更新されます。 | +| `protected_branch.rejected_ref_update` | ブランチ更新の試行が拒否されます。 | +| `protected_branch.policy_override` | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされます。 | #### リポジトリ -| 名前 | 説明 | -| ------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | -| `repo.archive` | リポジトリがアーカイブされました。 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` | リポジトリにコラボレーターが追加されました。 | -| `repo.config` | サイト管理者がフォースプッシュをブロックしました。 詳しくは、 [リポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)を参照してください。 | -| `repo.create` | リポジトリが作成されました。 | -| `repo.destroy` | リポジトリが削除されました。 | -| `repo.remove_member` | コラボレーターがリポジトリから削除されました。 | -| `repo.rename` | リポジトリの名前が変更されました。 | -| `repo.transfer` | ユーザーが転送されたリポジトリを受け取る要求を受け入れました。 | -| `repo.transfer_start` | ユーザーがリポジトリを別のユーザーまたは Organization に転送する要求を送信しました。 | -| `repo.unarchive` | リポジトリがアーカイブ解除されました。 For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% if enterpriseServerVersions contains currentVersion %} -| `repo.config.disable_anonymous_git_access` | Anonymous Git read access is disabled for a repository. 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/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. 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | -| `repo.config.lock_anonymous_git_access` | リポジトリの匿名 Git 読み取りアクセス設定がロックされているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できません。 詳細は「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。 | -| `repo.config.unlock_anonymous_git_access` | リポジトリの匿名 Git 読み取りアクセス設定がロック解除されているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できます。 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 %} +| 名前 | 説明 | +| ------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.access` | リポジトリの可視性がプライベート{% if enterpriseServerVersions contains currentVersion %}、パブリック、{% endif %} または内部に変更されました。 | +| `repo.archived` | リポジトリがアーカイブされました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。 | +| `repo.add_member` | リポジトリにコラボレーターが追加されました。 | +| `repo.config` | サイト管理者がフォースプッシュをブロックしました。 詳しくは、 [リポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)を参照してください。 | +| `repo.create` | リポジトリが作成されました。 | +| `repo.destroy` | リポジトリが削除されました。 | +| `repo.remove_member` | コラボレーターがリポジトリから削除されました。 | +| `repo.rename` | リポジトリの名前が変更されました。 | +| `repo.transfer` | ユーザーが転送されたリポジトリを受け取る要求を受け入れました。 | +| `repo.transfer_start` | ユーザーがリポジトリを別のユーザーまたは Organization に転送する要求を送信しました。 | +| `repo.unarchived` | リポジトリがアーカイブ解除されました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。{% if enterpriseServerVersions contains currentVersion %} +| `repo.config.disable_anonymous_git_access` | 匿名 Git 読み取りアクセスがリポジトリに対して無効になります。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | +| `repo.config.enable_anonymous_git_access` | 匿名 Git 読み取りアクセスがリポジトリに対して有効になります。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | +| `repo.config.lock_anonymous_git_access` | リポジトリの匿名 Git 読み取りアクセス設定がロックされているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できません。 詳細は「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。 | +| `repo.config.unlock_anonymous_git_access` | リポジトリの匿名 Git 読み取りアクセス設定がロック解除されているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できます。 詳しい情報については、「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。{% endif %} #### サイトアドミンのツール @@ -107,40 +107,39 @@ versions: #### Team -| 名前 | 説明 | -| -------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------- | -| `team.create` | ユーザアカウントまたはリポジトリが Team に追加されました。 | -| `team.delete` | A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.{% endif %} -| `team.destroy` | A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer.{% endif %} +| 名前 | 説明 | +| -------------------------:| -------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | ユーザアカウントまたはリポジトリが Team に追加されました。 | +| `team.delete` | ユーザアカウントまたはリポジトリが Team から削除されました。{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | ユーザがチームメンテナからチームメンバーに降格されました。{% endif %} +| `team.destroy` | Team が削除されました。{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | ユーザーがチームメンバーからチームメンテナに昇格しました。{% endif %} #### ユーザ -| 名前 | 説明 | -| -------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | ユーザアカウントにメールアドレスが追加されました。 | -| `user.async_delete` | An asynchronous job was started to destroy a user account, eventually triggering `user.delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.change_password` | A user changed his or her password.{% endif %} -| `user.create` | 新規ユーザが作成されました。 | -| `user.delete` | ユーザアカウントが非同期的ジョブによって削除されました。 | -| `user.demote` | サイトアドミンが一般ユーザアカウントに変更されました。 | -| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | ユーザが間違ったユーザネームやパスワード、または二段階認証コードでサインインしようとしました。 | -| `user.forgot_password` | A user requested a password reset via the sign-in page.{% endif %} -| `user.login` | A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| `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` | 一般ユーザアカウントがサイトアドミンへと変更されました。 | -| `user.remove_email` | ユーザアカウントからメールアドレスが削除されました。 | -| `user.rename` | ユーザ名が変更されました。 | -| `user.suspend` | A user account was suspended by a site admin.{% if enterpriseServerVersions contains currentVersion %} -| `user.two_factor_requested` | A user was prompted for a two-factor authentication code.{% endif %} -| `user.unsuspend` | サイトアドミンがユーザアカウント停止を解除しました。 | +| 名前 | 説明 | +| -------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | ユーザアカウントにメールアドレスが追加されました。 | +| `user.async_delete` | ユーザアカウントを破棄する非同期ジョブが開始され、最終的に ` user.delete ` がトリガーされました。{% if enterpriseServerVersions contains currentVersion %} +| `user.change_password` | ユーザがパスワードを変更しました。{% endif %} +| `user.create` | 新規ユーザが作成されました。 | +| `user.delete` | ユーザアカウントが非同期的ジョブによって削除されました。 | +| `user.demote` | サイトアドミンが一般ユーザアカウントに変更されました。 | +| `user.destroy` | ユーザが自分のアカウントを削除し、`user.async_delete` をトリガーしました。{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | ユーザが間違ったユーザネームやパスワード、または二段階認証コードでサインインしようとしました。 | +| `user.forgot_password` | ユーザがサインインページでパスワードリセットを申請しました。{% endif %} +| `user.login` | ユーザがサインインしました。{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | ユーザが必須メッセージを表示します（詳細については、「[ユーザメッセージをカスタマイズする](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください） | {% endif %} +| `user.promote` | 一般ユーザアカウントがサイトアドミンへと変更されました。 | +| `user.remove_email` | ユーザアカウントからメールアドレスが削除されました。 | +| `user.rename` | ユーザ名が変更されました。 | +| `user.suspend` | ユーザアカウントがサイトアドミンによって一時停止されました。{% if enterpriseServerVersions contains currentVersion %} +| `user.two_factor_requested` | ユーザが 2 要素認証コードを求められました。{% endif %} +| `user.unsuspend` | サイトアドミンがユーザアカウント停止を解除しました。 | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [デプロイキー]: /guides/managing-deploy-keys/#deploy-keys - [deploy key]: /guides/managing-deploy-keys/#deploy-keys [generate token]: /articles/creating-an-access-token-for-command-line-use [OAuth アクセストークン]: /developers/apps/authorizing-oauth-apps [OAuth application]: /guides/basics-of-authentication/#registering-your-app diff --git a/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md index 68c7b32c32..8837f9ee9f 100644 --- a/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md @@ -1,6 +1,6 @@ --- -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 past 90 days, including details such as who performed the action, what the action was, and when the action was performed.' +title: Enterprise にわたるユーザの監査 +intro: 'Audit log ダッシュボードには、サイト管理者に、過去 90 日間に企業全体のすべてのユーザと Organization によって実行されたアクションが表示されます。これには、アクションを実行したユーザ、アクションの内容、アクションの実行時期などの詳細が含まれます。' redirect_from: - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/ - /enterprise/admin/user-management/auditing-users-across-your-instance @@ -12,7 +12,7 @@ versions: ### Audit log にアクセスする -The audit log dashboard gives you a visual display of audit data across your enterprise. +Audit log ダッシュボードには、Enterprise 全体の監査データが表示されます。 ![インスタンスにわたるAudit logのダッシュボード](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) @@ -22,9 +22,9 @@ The audit log dashboard gives you a visual display of audit data across your ent 地図内では、世界中のイベントを見るためにパンやズームができます。 国にカーソルを合わせれば、その国のイベントの簡単な集計が表示されます。 -### Searching for events across your enterprise +### Enterprise にわたるイベントの検索 -The audit log lists the following information about actions made within your enterprise: +Audit log には、Enterprise 内で行われたアクションに関する次の情報が一覧表示されます。 * アクションが行われた[リポジトリ](#search-based-on-the-repository) * アクションを行った[ユーザ](#search-based-on-the-user) @@ -37,7 +37,7 @@ The audit log lists the following information about actions made within your ent **ノート:** -- Audit logのエントリはテキストを使った検索はできませんが、様々なフィルタを使って検索クエリを構築できます。 {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。 +- Audit logのエントリはテキストを使った検索はできませんが、様々なフィルタを使って検索クエリを構築できます。 {% data variables.product.product_name %} は、{% data variables.product.product_name %} 全体を検索するための多くの演算子をサポートしています。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。 - 90日よりも古いイベントの検索には、`created`修飾子を使ってください。 {% endwarning %} @@ -66,13 +66,13 @@ The audit log lists the following information about actions made within your ent `org` 修飾子は、特定の Organization にアクションを限定します。 例: -* `org:my-org` finds all events that occurred for the `my-org` organization. +* `org:my-org` は `my-org` という Organization で生じたすべてのイベントを検索します。 * `org:my-org action:team`は`my-org`というOrganization内で行われたすべてのteamイベントを検索します。 -* `-org:my-org` excludes all events that occurred for the `my-org` organization. +* `-org:my-org` は `my-org` という Organization で生じたすべてのイベントを除外します。 #### 実行されたアクションに基づく検索 -`action`修飾子は、特定のイベントをカテゴリ内でグループ化して検索します。 For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)". +`action`修飾子は、特定のイベントをカテゴリ内でグループ化して検索します。 以下のカテゴリに関連するイベントの詳しい情報については「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 | カテゴリ名 | 説明 | | ------ | -------------------------------------------- | diff --git a/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md b/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md index 8d2a45c2c3..b659cbaa63 100644 --- a/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md +++ b/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md @@ -1,6 +1,6 @@ --- title: ユーザセキュリティのベストプラクティス -intro: '{% if enterpriseServerVersions contains currentVersion %}Outside of instance-level security measures (SSL, subdomain isolation, configuring a firewall) that a site administrator can implement, there {% else %}There {% endif %}are steps your users can take to help protect your enterprise.' +intro: '{% if enterpriseServerVersions contains currentVersion %}サイト管理者が実装できるインスタンスレベルのセキュリティ対策（SSL、Subdomain Isolation、ファイアウォールの設定）以外では、{% else %}{% endif %}Enterprise を保護するためにユーザが実行できるステップがあります。' redirect_from: - /enterprise/admin/user-management/best-practices-for-user-security versions: @@ -18,7 +18,7 @@ versions: ### パスワードマネージャの要求 -We strongly recommend requiring your users to install and use a password manager--such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/)--on any computer they use to connect to your enterprise. そうすることで、確実に、パスワードが強力になり、侵犯されたり盗まれたりする可能性が低くなります。 +Enterprise への接続に使用するすべてのコンピュータに、[LastPass](https://lastpass.com/)、[1Password](https://1password.com/)、[Keeper](https://keepersecurity.com/) などのパスワードマネージャをインストールして使用するようにユーザに求めることを強くお勧めします。 そうすることで、確実に、パスワードが強力になり、侵犯されたり盗まれたりする可能性が低くなります。 ### Teamやリポジトリへのアクセス制限 diff --git a/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md index 77fec27297..ea2e4da4d9 100644 --- a/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md @@ -19,7 +19,7 @@ versions: ### {% data variables.large_files.product_name_long %}について -{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} You can use {% data variables.large_files.product_name_long %} with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable {% data variables.large_files.product_name_short %} for specific repositories or organizations, you need to enable {% data variables.large_files.product_name_short %} for your enterprise. +{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} {% data variables.large_files.product_name_long %} は、単一のリポジトリ、すべての個人または Organization のリポジトリ、または Enterprise 内のすべてのリポジトリで使用できます。 特定のリポジトリまたは Organization に対して {% data variables.large_files.product_name_short %} を有効にする前に、Enterprise に対して {% data variables.large_files.product_name_short %} を有効にする必要があります。 {% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} @@ -28,7 +28,7 @@ versions: {% data reusables.large_files.can-include-lfs-objects-archives %} -### Configuring {% data variables.large_files.product_name_long %} for your enterprise +### Enterprise 向けに {% data variables.large_files.product_name_long %} を設定する {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -65,7 +65,7 @@ versions: {% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} -1. Disable {% data variables.large_files.product_name_short %} on {% data variables.product.product_location %}. For more information, see "[Configuring {% data variables.large_files.product_name_long %} for your enterprise](#configuring-git-large-file-storage-for-your-enterprise)." +1. {% data variables.product.product_location %} で {% data variables.large_files.product_name_short %} を無効化します。 詳しい情報については、「[Enterprise の {% data variables.large_files.product_name_long %} を設定する](#configuring-git-large-file-storage-for-your-enterprise)」を参照してください。 2. サードパーティのサーバーを指し示す {% data variables.large_files.product_name_short %} の設定ファイルを作成します。 ```shell @@ -99,7 +99,7 @@ versions: ### 異なるGit Large File Storageサーバへの移行 -Before migrating to a different {% data variables.large_files.product_name_long %} server, you must configure {% data variables.large_files.product_name_short %} to use a third party server. For more information, see "[Configuring {% data variables.large_files.product_name_long %} to use a third party server](#configuring-git-large-file-storage-to-use-a-third-party-server)." +別の {% data variables.large_files.product_name_long %} サーバーに移行する前に、サードパーティのサーバーを使用するように {% data variables.large_files.product_name_short %} を設定する必要があります。 詳細については、「[サードパーティのサーバーを使用するための {% data variables.large_files.product_name_long %} を設定する](#configuring-git-large-file-storage-to-use-a-third-party-server)」を参照してください。 1. 2 番目のリモートでリポジトリを設定します。 ```shell diff --git a/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md index b71da368a5..740b6ee5c5 100644 --- a/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md +++ b/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md @@ -1,6 +1,6 @@ --- title: Organizationのメンバーシップの可視性の設定 -intro: You can set visibility for new organization members across your enterprise to public or private. また、メンバーが自分の可視性をデフォルトから変更できないようにすることもできます。 +intro: Enterprise 全体の新しい Organization メンバーの可視性をパブリックまたはプライベートに設定できます。 また、メンバーが自分の可視性をデフォルトから変更できないようにすることもできます。 redirect_from: - /enterprise/admin/user-management/configuring-visibility-for-organization-membership versions: @@ -21,4 +21,4 @@ versions: {% data reusables.enterprise-accounts.options-tab %} 3. [Default organization membership visibility] で、ドロップダウンメニューを使用して [**Private**] または [**Public**] をクリックします。 ![デフォルトの Organization のメンバーシップの可視性をパブリックあるいはプライベートに設定するオプションを持つドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png) 4. メンバーがデフォルトからメンバーシップの可視性を変更できないようにするために、**Enforce on organization members（Organizationのメンバーに適用）**を選択することもできます。 ![Checkbox to enforce the default setting on all members](/assets/images/enterprise/site-admin-settings/enforce-default-org-membership-visibility-setting.png){% if enterpriseServerVersions contains currentVersion %} -5. 新しい可視性の設定をすべての既存メンバーに適用したい場合は、`ghe-org-membership-update`コマンドラインユーティリティを使ってください。 For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)."{% endif %} +5. 新しい可視性の設定をすべての既存メンバーに適用したい場合は、`ghe-org-membership-update`コマンドラインユーティリティを使ってください。 詳しい情報については、「[コマンドラインユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)」を参照してください。{% endif %} diff --git a/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md index 036d4c641d..a5ea9088f0 100644 --- a/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Disabling Git SSH access on your enterprise +title: Enterprise で Git SSH アクセスを無効化する redirect_from: - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/ - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/ @@ -13,7 +13,7 @@ redirect_from: - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server -intro: 'You can prevent people from using Git over SSH for certain or all repositories on your enterprise.' +intro: 'Enterprise 内の特定のリポジトリまたはすべてのリポジトリで、ユーザが SSH 経由で Git を使用できないようにすることができます。' versions: enterprise-server: '*' github-ae: '*' @@ -41,7 +41,7 @@ versions: {% data reusables.enterprise_site_admin_settings.admin-tab %} 7. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 続いて、**Enforce on all repositories（すべてのリポジトリで強制）**を選択してください。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) -### Disabling Git SSH access to all repositories in your enterprise +### Enterprise 内のすべてのリポジトリへの Git SSH アクセスを無効化する {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} diff --git a/translations/ja-JP/content/admin/user-management/index.md b/translations/ja-JP/content/admin/user-management/index.md index 7776cd476b..1a3f305a37 100644 --- a/translations/ja-JP/content/admin/user-management/index.md +++ b/translations/ja-JP/content/admin/user-management/index.md @@ -1,7 +1,7 @@ --- title: 'Managing users, organizations, and repositories' shortTitle: 'Managing users, organizations, and repositories' -intro: 'This guide describes authentication methods for users signing in to your enterprise, how to create organizations and teams for repository access and collaboration, and suggested best practices for user security.' +intro: 'このガイドでは、Enterprise にサインインするユーザの認証方式、リポジトリへのアクセスとコラボレーションのための Organization と Team を作成する方法、およびユーザセキュリティで推奨されるベストプラクティスについて説明します。' redirect_from: - /enterprise/admin/categories/user-management/ - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration diff --git a/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md index 1d0d1fd5c9..e05a2bc11f 100644 --- a/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,11 +33,11 @@ versions: 1. 管理シェルに接続します。 詳しい情報については「[管理シェル（SSH）にアクセスする](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)」を参照してください。 2. `/data/github/current`ディレクトリにアクセスしてください。 - ``` + ```shell cd /data/github/current ``` 3. 移行コマンドを実行してください。 - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` diff --git a/translations/ja-JP/content/admin/user-management/viewing-push-logs.md b/translations/ja-JP/content/admin/user-management/viewing-push-logs.md index ab7a84fe4a..e2d5d6a891 100644 --- a/translations/ja-JP/content/admin/user-management/viewing-push-logs.md +++ b/translations/ja-JP/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ versions: ### リポジトリのプッシュログを表示する +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. 1. リポジトリにアクセスします。 -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. In the upper-right corner of the repository's page, click +{% octicon "rocket" aria-label="The rocket ship" %}. + ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. 左のサイドバーで、**Push Log（プッシュログ）** をクリックしてください。 ![プッシュログのタブ](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### コマンドラインでリポジトリのプッシュログを表示する -1. SSHを使ってアプライアンスに接続してください。 詳しくは、"[管理シェル（SSH）へのアクセス方法](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)を参照してください。" -2. 適切な Git リポジトリで Audit log ファイルを開いてください。 +{% data reusables.enterprise_installation.ssh-into-instance %} +1. 適切な Git リポジトリで Audit log ファイルを開いてください。 ```shell ghe-repo コードオーナー/リポジトリ -c "less audit_log" ``` diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 98573ea0cd..72f816a53e 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ versions: ![履歴でタグを表示する](/assets/images/help/desktop/viewing-tags-in-history.png) 3. コミットに関連付けられているすべてのタグは、そのコミットのメタデータに表示されます。 ![コミットでタグを表示する](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### Deleting tags + +{% note %} + +**Note**: You can only delete tags associated with commits that have not yet been pushed. + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md index 64d569c591..81eda4b7bc 100644 --- a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -80,7 +80,7 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ この例では、ウェブページ上にユーザアカウントに対して `POST` リクエストをトリガするボタンがあるフォームを使用します。 -``` +```html Create a GitHub App Manifest:
    @@ -111,7 +111,7 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ ``` この例では、ウェブページ上に Organization アカウントに対して `POST` リクエストをトリガするボタンがあるフォームを使用します。 `ORGANIZATION` は、アプリケーションを作成する場所の Organization アカウントの名前に置き換えます。 -``` +```html Create a GitHub App Manifest:
    diff --git a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md index e4012ee392..1104208b10 100644 --- a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -435,7 +435,7 @@ clone_repository(full_repo_name, repository, head_sha) ### ステップ 2.3. RuboCop を実行する -これでうまくいきました。 リポジトリをクローンし、CI サーバーを使用してチェック実行を作成しようという段階にまで到達しました。 それではいよいよ [RuboCop 文法チェッカー](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) と [Checks API アノテーション](/rest/reference/checks#create-a-check-run)の核心に迫ります。 +これでうまくいきました。 リポジトリをクローンし、CI サーバーを使用してチェック実行を作成しようという段階にまで到達しました。 Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). 次のコードは、RuboCop を実行し、スタイル コード エラーを JSON フォーマットで保存します。 [前のステップ](#step-22-cloning-the-repository) で追加した`clone_repository` への呼び出しの下と、チェック実行を更新するコードの上に追加して完了です。 @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -上記のコードは、リポジトリのディレクトリにある全てのファイルで RuboCop を実行します。 `--format json` のオプションは、文法チェックの結果のコピーをコンピューターで読みとることができるフォーマットで保存する便利な方法です。 JSON フォーマットの詳細および例については、[RuboCop ドキュメント](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter)を参照してください。 +上記のコードは、リポジトリのディレクトリにある全てのファイルで RuboCop を実行します。 `--format json` のオプションは、文法チェックの結果のコピーをコンピューターで読みとることができるフォーマットで保存する便利な方法です。 See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. このコードは RuboCop の結果を `@report` 変数に格納するため、リポジトリのチェックアウトを安全に削除できます。 また、このコードは JSON も解析するため、`@output` 変数を使用して GitHub App のキーと変数に簡単にアクセスできます。 @@ -588,7 +588,7 @@ end `offense_count` が 0 の場合、CI テストは `success` となります。 エラーがある場合、このコードは結果を `neutral` に設定します。これは、コードの文法チェッカーによるエラーを厳格に強制することを防ぐためです。 ただし、文法エラーがある場合にチェックスイートが失敗になるようにしたい場合は、結果を `failure` に変更できます。 -エラーが報告されると、上記のコードは ReboCop レポートの `files` 配列を反復処理します。 コードは各ファイルにおいてファイルパスを抽出し、アノテーションレベルを `notice` に設定します。 さらに細かく、[RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/) の各タイプに特定の警告レベルを設定することもできますが、このクイックスタートでは簡単さを優先し、すべてのエラーを `notice` のレベルに設定します。 +エラーが報告されると、上記のコードは ReboCop レポートの `files` 配列を反復処理します。 コードは各ファイルにおいてファイルパスを抽出し、アノテーションレベルを `notice` に設定します。 You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. このコードはまた、`offenses` 配列の各エラーを反復処理し、違反の場所とエラー メッセージを収集します。 必要な情報を抽出後、コードは各エラーに対してアノテーションを作成し、それを `annotations` 配列に格納します。 アノテーションは同一行の開始列と終了列のみをサポートしているため、開始行と終了行の値が同じである場合にのみ `annotation` オブジェクトに `start_column` と `end_column` が追加されます。 @@ -718,13 +718,13 @@ $ ruby template_server.rb ここまで来たのはすごいですよ！ 👏 あなたはもう CI テストを作成しました。 このセクションでは、もう 1 つの機能を追加します。RuboCop を使用して、見つけたエラーを自動的に修正するために使用するための機能です。 すでに[前のセクション](#step-25-updating-the-check-run-with-ci-test-results)で、[Fix this] ボタンを追加しました。 ここでは、ユーザが [Fix this] ボタンをクリックしたときにトリガーされる、`requested_action` チェック実行イベントを処理するコードを追加します。 -RuboCop ツールには、見つけたエラーを自動的に修正する `--auto-correct` コマンドラインオプションの [機能](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) があります。 `--auto-correct` 機能を使用すると、サーバー上のローカルファイルに更新が適用されます。 RuboCop がこの作業をやってのけた後は、その変更を GitHub にプッシュする必要があります。 +The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. `--auto-correct` 機能を使用すると、サーバー上のローカルファイルに更新が適用されます。 RuboCop がこの作業をやってのけた後は、その変更を GitHub にプッシュする必要があります。 リポジトリにブッシュするには、アプリケーションに [Repository contents] への書き込み権限が必要です。 この権限については、[ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)で既に [**Read & write**] に設定しているので、もう準備は整っています。 ファイルをコミットするには、どの[ユーザ名](/articles/setting-your-username-in-git/)と[メールアドレス](/articles/setting-your-commit-email-address-in-git/)をコミットに関連付けるか Git が知っている必要があります。 `.env` ファイルにあと 2 つの環境変数を追加して、名前 (`GITHUB_APP_USER_NAME`) とメールアドレス (`GITHUB_APP_USER_EMAIL`) の設定を保存します。 アプリケーションにはあなたの名前を付けることもできます。この例では、メールアドレスは何でも構いません。 例: -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 19799bdabe..f721f2da67 100644 --- a/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ _承認された_ OAuth App は、 ユーザまたは Organization のオーナ | インストールトークンは、事前に定義された時間 (現在は 1 時間) が経過すると期限切れになります。 | OAuth トークンは、顧客によって取り消されるまで有効となります。 | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_ghe_cloud %} では、適用されるレート制限値が高くなります。 詳しい情報については、「[GitHub App のレート制限](/developers/apps/rate-limits-for-github-apps)」を参照してください。{% endif %} | OAuth トークンでは、1 時間あたり 5,000 リクエストのレート制限が適用されます。 | | レート制限の増加は、GitHub App レベル (すべてのインストールに影響) と個々のインストールレベルの両方に適用できます。 | レート制限の増加は、OAuth App ごとに適用されます。 その OAuth App に付与されたすべてのトークンで、制限値が増大します。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %} は、ユーザの代わりに認証を行うことができ、これをユーザからサーバーに対するリクエストといいます。 このフローは、OAuth App 認可フローと同じです。 ユーザからサーバーに対するトークンは期限切れとなることがあり、リフレッシュトークンで更新できます。 詳しい情報については、「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)」および「[GitHub Apps のユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 | {% data variables.product.prodname_oauth_app %} により使用される OAuth フローでは、ユーザの代わりに {% data variables.product.prodname_oauth_app %} を承認します。 これは、{% data variables.product.prodname_github_app %} ユーザからサーバーに対する承認で用いられるフローと同じです。 |{% endif %} +| {% data variables.product.prodname_github_app %} は、ユーザの代わりに認証を行うことができ、これをユーザからサーバーに対するリクエストといいます。 このフローは、OAuth App 認可フローと同じです。 ユーザからサーバーに対するトークンは期限切れとなることがあり、リフレッシュトークンで更新できます。 詳しい情報については、「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)」および「[GitHub Apps のユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 | {% data variables.product.prodname_oauth_app %} により使用される OAuth フローでは、ユーザの代わりに {% data variables.product.prodname_oauth_app %} を承認します。 これは、{% data variables.product.prodname_github_app %} ユーザからサーバーに対する承認で用いられるフローと同じです。 +{% endif %} ### リソースに対する権限レベルのリクエスト diff --git a/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index fb4727f2af..ce4dab7a96 100644 --- a/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -89,7 +89,7 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 デフォルトでは、レスポンスは以下の形式になります。 レスポンスパラメータの `expires_in`、`refresh_token`、`refresh_token_expires_in` は、ベータ版の機能である、ユーザからサーバに対するアクセストークンの期限設定を有効にしている場合にのみ返されます。 -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", diff --git a/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md b/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md index 5769e9435a..5397465e5a 100644 --- a/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ versions: ### アプリケーション -誰でも他のユーザと{% data variables.product.prodname_marketplace %}でアプリケーションを共有できますが、有料プランを含めることができるのは{% data variables.product.company_short %}に検証されたユーザのみです。 詳しい情報については、「[検証済みの作者について](/developers/github-marketplace/about-verified-creators)」を参照してください。 +Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. + +To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments. + +To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)." + +#### New to apps? {% data variables.product.prodname_marketplace %}のアプリケーション作成に関心があり、{% data variables.product.prodname_github_apps %}や{% data variables.product.prodname_oauth_app %}に慣れていない場合は、「[{% data variables.product.prodname_github_apps %}を構築する](/developers/apps/building-github-apps)」や「[{% data variables.product.prodname_oauth_app %}を構築する](/developers/apps/building-oauth-apps)」を参照してください。 +#### GitHub Apps vs. OAuth Apps + {% data reusables.marketplace.github_apps_preferred %}、{% data variables.product.prodname_marketplace %}ではOAuthと{% data variables.product.prodname_github_app %}をどちらもリストできます。 詳しい情報については、「[{% data variables.product.prodname_github_apps %}と{% data variables.product.prodname_oauth_app %}の違い](/apps/differences-between-apps/)」および「[{% data variables.product.prodname_oauth_app %}を{% data variables.product.prodname_github_apps %}に移行する](/apps/migrating-oauth-apps-to-github-apps/)」を参照してください。 -{% data variables.product.prodname_marketplace %}に関する質問がある場合は、{% data variables.contact.contact_support %}に直接お問い合わせください。 - -### アプリケーションを{% data variables.product.prodname_marketplace %}に公開する +### Publishing an app to {% data variables.product.prodname_marketplace %} overview アプリケーションを作成したら、{% data variables.product.prodname_marketplace %}に公開して他のユーザと共有できます。 その手順を要約すると以下の通りです。 @@ -38,13 +46,9 @@ versions: 1. 価格プランを追加します。 詳しい情報については、「[リストに対する価格プランの設定](/developers/github-marketplace/setting-pricing-plans-for-your-listing)」を参照してください。 -1. 無料または有料アプリケーションとして{% data variables.product.prodname_marketplace %}に掲載するための要件を満たしているかどうか確認します。 詳しい情報については、「[アプリケーションを載せるための要件](/developers/github-marketplace/requirements-for-listing-an-app)」を参照してください。 - 1. 「[{% data variables.product.prodname_marketplace %}開発者同意書](/articles/github-marketplace-developer-agreement/)」の条項を読み、同意します。 -1. {% data variables.product.prodname_marketplace %}に掲載するリストをサブミットし、アプリケーションを販売したい場合は検証をリクエストします。 詳しい情報については、「[公開するリストをサブミットする](/developers/github-marketplace/submitting-your-listing-for-publication)」を参照してください。 - -質問や追加の手順について、オンボーディング担当者がご連絡します。 たとえば、有料プランを追加した場合は、検証プロセスを完了し、財務的オンボーディングを完了させる必要があります。 リストが承認されると、アプリケーションはただちに{% data variables.product.prodname_marketplace %}で公開されます。 +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. 詳しい情報については、「[公開するリストをサブミットする](/developers/github-marketplace/submitting-your-listing-for-publication)」を参照してください。 ### アプリケーションの実績を確認する @@ -52,3 +56,7 @@ versions: - [リストのメトリクスの参照](/developers/github-marketplace/viewing-metrics-for-your-listing) - [リストの取引の表示](/developers/github-marketplace/viewing-transactions-for-your-listing) + +### Contacting Support + +{% data variables.product.prodname_marketplace %}に関する質問がある場合は、{% data variables.contact.contact_support %}に直接お問い合わせください。 diff --git a/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md b/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..5eca5223e6 --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: About marketplace badges +intro: 'Learn about the badges that you may see for some apps and actions listings on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### For GitHub Apps + +Apps with the {% octicon "verified" aria-label="The verified badge" %}, are owned by an organization that has: +- Confirmed their domain +- Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization +- Required two-factor authentication for their organization. 詳しい情報については [Organization で 2 要素認証を要求する](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)を参照してください。 + +![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +To learn how you can add this badge to your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +{% data variables.product.prodname_marketplace %}でアプリケーションをリストするための要件に関する情報については、「[{% data variables.product.prodname_marketplace %}上にアプリケーションをリストするための要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)」を参照してください。 + +使用するアプリケーションの探し方に関する情報については、「[{% data variables.product.prodname_marketplace %}の検索](/github/searching-for-information-on-github/searching-github-marketplace)」を参照してください。 + +### For GitHub actions + +Actions with the {% octicon "verified" aria-label="The verified badge" %}, or verified creator badge, indicate that {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization. + +![Verified creator badge for GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +For information on how to publish a GitHub action to {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." + +### About the previous verification process for apps + +検証済みの作者バッジの他に、未検証および検証済みのアプリケーションのバッジも表示されます。 これらのアプリケーションは、以前の方法を用いて、個々のアプリケーションを検証して公開されたものです。 + +![検証済みの緑と未検証の灰色のバッジ](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**Note:** The new publisher verification process for apps replaces the previous process where individual apps were verified. The new publisher verification process is similar to the verification process for actions. 旧プロセスの下で検証されたアプリケションを持っている場合、それらはこの変更には影響されません。 {% data variables.product.prodname_marketplace %}チームは、Organizationベースの検証への移行方法の詳細について、お客様に連絡します。 + +{% endnote %} diff --git a/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..9c6ace5c1f --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Applying for publisher verification for your organization +intro: 'To offer paid plans for your app or to include a marketplace badge in your app listing, you must complete the publisher verification process for your organization.' +versions: + free-pro-team: '*' +--- + +Publisher verification ensures that {% data variables.product.prodname_dotcom %} has a way to contact you, that you've enabled two-factor authentication for your organization, and that your organization's domain has been verified. + +Once your organization has been verified, you can publish paid plans for your app. For information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)." + +### Requesting publisher verification + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. 左サイドバーで [**Developer settings**] をクリックします。 ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) +1. Under "Publisher Verification", complete the information in the checklist: + - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. + - Ensure that Two-factor authentication is enabled for your organization. 詳しい情報については [Organization で 2 要素認証を要求する](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)を参照してください。 + - Submit a verified domain. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + + ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) + +1. Click **Request Verification**. {% data variables.product.company_short %} will review your details and let you know once your publisher verification is complete. + +### 参考リンク + +For information about the process of publishing apps, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)." diff --git a/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index b2a1e030e0..4e9f395bed 100644 --- a/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ versions: ### アプリケーションのサブミット -{% data variables.product.prodname_marketplace %}リストが完成したら、**Overview（概要）**ページからレビューのためにリストをサブミットできます。 「[{% data variables.product.prodname_marketplace %}の開発者契約](/articles/github-marketplace-developer-agreement/)」を読んで同意しなければなりません。続いて**Submit for review（レビューのためにサブミット）**をクリックできます。 レビューのためにアプリケーションをサブミットした後、のオンボーディングの専門家から、オンボーディングのプロセスに関する追加情報と併せて連絡が来ます。 オンボーディングとセキュリティレビューのプロセスに関する詳細については「[{% data variables.product.prodname_marketplace %}を使い始める](/marketplace/getting-started/)」を参照してください。 +{% data variables.product.prodname_marketplace %}リストが完成したら、**Overview（概要）**ページからレビューのためにリストをサブミットできます。 「[{% data variables.product.prodname_marketplace %}の開発者契約](/articles/github-marketplace-developer-agreement/)」を読んで同意しなければなりません。続いて**Submit for review（レビューのためにサブミット）**をクリックできます。 レビューのためにアプリケーションをサブミットした後、のオンボーディングの専門家から、オンボーディングのプロセスに関する追加情報と併せて連絡が来ます。 ### {% data variables.product.prodname_marketplace %}リストの削除 diff --git a/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview.md b/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..5b8799f9d9 --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,8 @@ +--- +title: GitHub Marketplace Overview +intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/developers/github-marketplace/index.md b/translations/ja-JP/content/developers/github-marketplace/index.md index 33a722a3a6..a4366eec93 100644 --- a/translations/ja-JP/content/developers/github-marketplace/index.md +++ b/translations/ja-JP/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md index 0251e8c785..5037239a75 100644 --- a/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ versions: ### 有料アプリケーションの要件 -上記のすべてのアプリケーションに関する要件に加え、{% data variables.product.prodname_marketplace %}上で有料サービスとして提供するアプリケーションは、以下の要件も満たさなければなりません。 +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transfering ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. 詳しい情報については、「[リストに対する価格プランの設定](/developers/github-marketplace/setting-pricing-plans-for-your-listing)」を参照してください。 + +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: - {% data variables.product.prodname_github_app %}は、最低でも100個のインストールが必要です。 - {% data variables.product.prodname_oauth_app %}は最低200ユーザが必要です。 - すべての有料アプリケーションは、新規購入、アップグレード、ダウングレード、キャンセル、無料トライアルの{% data variables.product.prodname_marketplace %}購入イベントを処理できなければなりません。 詳しい情報については、以下の「[有料アプリケーションの支払い要件](#billing-requirements-for-paid-apps)」を参照してください。 -- 公開するOrganizationは、検証済みドメインを持っていなければならず、2要素認証を有効化しなければなりません。 詳しい情報については [Organization で 2 要素認証を要求する](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)を参照してください。 -アプリケーションを{% data variables.product.prodname_marketplace %}上で公開する準備ができたら、リストのための検証をリクエストしなければなりません。 +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -検証プロセスは、Organizationに対して開かれています。 {% data reusables.marketplace.app-transfer-to-org-for-verification %} これを行う方法については「[公開のためのリストのサブミット](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)」を参照してください。 +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} diff --git a/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 475644e02d..04a9fd3c39 100644 --- a/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,11 +19,13 @@ versions: ### 価格プランの設定について -アプリケーションを{% data variables.product.prodname_marketplace %}で販売したい場合は、アプリケーションのリストを公開する際に検証をリクエストしなければなりません。 検証プロセスの過程で、オンボーディングの専門家がOrganizationのアイデンティティとセキュリティの設定をチェックします。 オンボーディングの専門家は、Organizationに財務的なオンボーディングも受けさせます。 詳しい情報については、「[{% data variables.product.prodname_marketplace %}にアプリケーションをリストするための要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)」を参照してください。 +{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. 詳細にな情報については「[{% data variables.product.prodname_marketplace %}の価格プラン](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)」を参照してください。 -{% data reusables.marketplace.app-transfer-to-org-for-verification %} これを行う方法については「[公開のためのリストのサブミット](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)」を参照してください。 +To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -{% data variables.product.prodname_marketplace %}は、いくつかの種類の価格プランを提供します。 詳細にな情報については「[{% data variables.product.prodname_marketplace %}の価格プラン](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)」を参照してください。 +If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. + +![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png) ### 価格プランの保存について @@ -33,7 +35,7 @@ versions: ### 価格プランの作成 -{% data variables.product.prodname_marketplace %}リストの価格プランを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Plans and pricing（プランと価格）**をクリックしてください。 詳しい情報については「[ドラフトの{% data variables.product.prodname_marketplace %}リストの作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)」を参照してください。 +{% data variables.product.prodname_marketplace %}リストの価格プランを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Plans and pricing（プラント価格）**をクリックしてください。 詳しい情報については「[ドラフトの{% data variables.product.prodname_marketplace %}リストの作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)」を参照してください。 **New draft plan（新規ドラフトプラン）**をクリックすると、価格プランをカスタマイズできるフォームが表示されます。 価格プランを作成するには、以下のフィールドを設定しなければなりません。 diff --git a/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md index 4a891ed197..ff21110c87 100644 --- a/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: 公開のためのリストのサブミット -intro: '{% data variables.product.prodname_dotcom %}コミュニティに利用してもらうためにリストをサブミットできます。' +intro: 'To finish your app listing submission, you can request a review by an onboarding expert.' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +Once your app listing meets the {% data variables.product.prodname_marketplace %} requirements, you can submit your app. For an overview of the app listing requirements, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +1. In the top left of the app listing page, click **Overview**. For information on finding your app listing page, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -アプリケーションのリストを完成させると、検証ありもしくは検証なしでのリストの公開をリクエストできる2つのボタンが表示されます。 「検証なしでの公開」のための**リクエスト**ボタンは、リスト中で有料プランを公開している場合、無効化されています。 + ![Overview option for the marketplace draft listing](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![未検証及び検証済みリクエストボタン](/assets/images/marketplace/marketplace-request-button.png) +2. To submit your your completed app listing, click **Request review**. -{% data reusables.marketplace.launch-with-free %} + !["Publish your app to Marketplace" checklist with submission button at the bottom](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -レビューのためにリストをサブミットすると、オンボーディングの専門家が追加情報をもって連絡してきます。 - -リストの作成とサブミットのプロセスの概要については、「[{% data variables.product.prodname_marketplace %}について](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)」を参照してください。 - -### 検証付きでの公開のための前提条件 - -リストの検証をリクエストする前に、{% data variables.product.prodname_marketplace %}の支払いフローとwebhookをアプリケーションに統合しなければなりません。 詳しい情報については「[アプリケーションでの{% data variables.product.prodname_marketplace %} APIの利用](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)」を参照してください。 - -リストの要件を満たしており、{% data variables.product.prodname_marketplace %} APIと統合してあれば、先へ進んでリストをサブミットしてください。 詳しい情報については、「[アプリケーションを載せるための要件](/developers/github-marketplace/requirements-for-listing-an-app)」を参照してください。 - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} その方法に関する情報としては、以下の「[サブミットの前にアプリケーションをOrganizationに移譲する](#transferring-an-app-to-an-organization-before-you-submit)」を参照してください。 - -### サブミットの前にアプリケーションをOrganizationに移譲する - -ユーザアカウントが所有するアプリケーションを販売することはできません。 検証済みの作者となっているOrganizationか、アプリケーションのリストの検証をリクエストできるOrganizationに、アプリケーションを移譲しなければなりません。 詳細については以下を参照してください。 - -1. 「[Organizationを最初から作成する](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)」 - -1. 「[GitHub Appの所有権の移譲](/developers/apps/transferring-ownership-of-a-github-app)」あるいは「[OAuth Appの所有権の移譲](/developers/apps/transferring-ownership-of-an-oauth-app)」 +An onboarding expert will reach out to you with additional information. diff --git a/translations/ja-JP/content/developers/overview/secret-scanning.md b/translations/ja-JP/content/developers/overview/secret-scanning.md index a03b9bb190..eca248440c 100644 --- a/translations/ja-JP/content/developers/overview/secret-scanning.md +++ b/translations/ja-JP/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: Secret scanning intro: 'サービスプロバイダーは、{% data variables.product.prodname_dotcom %}とパートナーになり、シークレットスキャンニングを通じてシークレットトークンのフォーマットを保護できます。シークレットスキャンニングは、そのシークレットのフォーマットで誤って行われたコミットを検索し、サービスプロバイダーの検証用エンドポイントに送信します。' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -{% data variables.product.prodname_dotcom %}は、既知のシークレットフォーマットに対してリポジトリをスキャンし、誤ってコミットされたクレデンシャルが不正利用されることを防ぎます。 シークレットスキャンニングは、デフォルトでパブリックなリポジトリで行われ、プライベートリポジトリではリポジトリ管理者もしくはOrganizationのオーナーが有効化できます。 サービスプロバイダーは{% data variables.product.prodname_dotcom %}とパートナーになり、シークレットのフォーマットがシークレットスキャンニングに含まれるようにすることができます。 +{% data variables.product.prodname_dotcom %}は、既知のシークレットフォーマットに対してリポジトリをスキャンし、誤ってコミットされたクレデンシャルが不正利用されることを防ぎます。 {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}. シークレットのフォーマットに対する一致がパブリックリポジトリで見つかった場合、選択したHTTPのエンドポイントにペイロードが送信されます。 -シークレットスキャンニングが設定されたプライベートリポジトリでシークレットフォーマットへの一致が見つかった場合、リポジトリの管理者にはアラートが発せられ、{% data variables.product.prodname_dotcom %}上でシークレットスキャンニングの結果を見て管理できます。 詳しい情報については「[シークレットスキャンニングからのアラートの管理](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。 +When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。 {% note %} -**ノート:** プライベートリポジトリに対するシークレットスキャンニングは、現在ベータです。 +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. {% endnote %} -この記事では、サービスプロバイダーとして{% data variables.product.prodname_dotcom %}とパートナーになり、シークレットスキャンニングプログラムに参加する方法を説明します。 +This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. -### シークレットスキャンニングのプロセス +### The {% data variables.product.prodname_secret_scanning %} process -##### パブリックリポジトリでのシークレットスキャンニングの動作 +##### How {% data variables.product.prodname_secret_scanning %} works in a public repository -以下の図は、パブリックリポジトリに対するシークレットスキャンニングのプロセスをまとめたもので、一致があった場合にサービスプロバイダへの検証エンドポイントに送信されています。 +The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint. -![シークレットのスキャンニングと、サービスプロバイダーの検証エンドポイントへの一致の送信のプロセスのフロー図。](/assets/images/secret-scanning-flow.png "シークレットスキャンニングのフロー") +![シークレットのスキャンニングと、サービスプロバイダーの検証エンドポイントへの一致の送信のプロセスのフロー図。](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow") -### {% data variables.product.prodname_dotcom %}上のシークレットスキャンニングプログラムへの参加 +### Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %} 1. プロセスを開始するために、{% data variables.product.prodname_dotcom %}に連絡してください。 1. スキャンしたい関連シークレットを特定し、それらを捕捉するための正規表現を作成してください。 -1. パブリックリポジトリで見つかったシークレットの一致に対応するために、シークレットスキャンニングのメッセージペイロードを含む{% data variables.product.prodname_dotcom %}からのwebhookを受け付けるシークレットアラートサービスを作成してください。 +1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the {% data variables.product.prodname_secret_scanning %} message payload. 1. シークレットアラートサービスに、署名検証を実装してください。 1. シークレットアラートサービスに、シークレットの破棄とユーザへの通知を実装してください。 +1. Provide feedback for false positives (optional). #### プロセスを開始するための{% data variables.product.prodname_dotcom %}への連絡 -登録のプロセスを開始するために、secret-scanning@github.comにメールしてください。 +To get the enrollment process started, email secret-scanning@github.com. -シークレットスキャンニングプログラムの詳細が送られてくるので、先へ進む前に{% data variables.product.prodname_dotcom %}の参加規約に同意しなければなりません。 +You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. #### シークレットの特定と正規表現の作成 -シークレットをスキャンするために、{% data variables.product.prodname_dotcom %}はシークレットスキャンニングプログラムに含めたいそれぞれのシークレットについて以下の情報を必要とします。 +To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program: * シークレットの種類に対する、ユニークで人が読める名前。 後にこれを使って、メッセージペイロード中の`Type`値が生成されます。 * このシークレットの種類を見つける正規表現。 できるかぎり正確にしてください。そうすることで、誤検知の数を減らすことができます。 * {% data variables.product.prodname_dotcom %}からのメッセージを受信するエンドポイントのURL。 これは各シークレットの種類ごとにユニークである必要はありません。 -この情報をsecret-scanning@github.comに送信してください。 +Send this information to secret-scanning@github.com. #### シークレットアラートサービスの作成 @@ -61,7 +62,7 @@ versions: ##### エンドポイントに送信されるPOSTの例 -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ Content-Length: 0123 次のメッセージを受信したとして、以下のコードは署名検証の方法を示しています。 このコードはまた、`GITHUB_PRODUCTION_TOKEN`という環境変数に生成されたPATが設定されているものとしています(https://github.com/settings/tokens)。 このトークンには権限が設定されている必要はありません。 **検証エンドポイントに送信されたサンプルのメッセージ** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -270,4 +271,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### シークレットアラートサービスへのシークレットの破棄とユーザ通知の実装 -パブリックリポジトリでのシークレットスキャンニングでは、シークレットアラートサービスを拡張して、公開されたシークレットを取り除き、影響されたユーザに通知できます。 これをシークレットアラートサービスへどのように実装するかは実装者に任されていますが、{% data variables.product.prodname_dotcom %}がメッセージを送信したすべてのシークレットは、公開され、侵害されたものと考えることをおすすめします。 +For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. これをシークレットアラートサービスへどのように実装するかは実装者に任されていますが、{% data variables.product.prodname_dotcom %}がメッセージを送信したすべてのシークレットは、公開され、侵害されたものと考えることをおすすめします。 + +#### Provide feedback for false positives + +We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at secret-scanning@github.com. + +When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats. + +You can send us the raw token: + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256: + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +A few important points: +- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both. +- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm. +- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed. + +{% note %} + +**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at secret-scanning@github.com. + +{% endnote %} + diff --git a/translations/ja-JP/content/discussions/index.md b/translations/ja-JP/content/discussions/index.md index d0ee25fb24..2ddd679817 100644 --- a/translations/ja-JP/content/discussions/index.md +++ b/translations/ja-JP/content/discussions/index.md @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -43,12 +43,12 @@ versions: {% render 'discussions-community-card' for discussionsCommunityExamples as example %} {% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
    {% octicon "search" width="24" %}
    -

    Sorry, there is no result for

    -

    It looks like we don't have an example that fits your filter.
    Try another filter or add your code example

    +

    検索結果はありません

    +

    フィルタに適合する例がないようです。
    別のフィルタを試すか、コード例を追加してください

    コミュニティを追加 {% octicon "arrow-right" %}
    diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..01e91613f8 --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +title: Campus Advisorsについて +intro: 'インストラクターあるいはメンターとして、Campus Advisorsトレーニング及びサポートと共に学校での{% data variables.product.prodname_dotcom %}の利用について学んでください。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-advisors + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +教授、教師、メンバーはCampus Advisorsオンライントレーニングを使ってGitと{% data variables.product.prodname_dotcom %}をマスターし、{% data variables.product.prodname_dotcom %}で生徒に教えるためのベストプラクティスを学ぶことができます。 詳しい情報については[Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。 + +{% note %} + +**ノート：**インストラクターとして、学生のために{% data variables.product.prodname_dotcom %}のアカウントを作成することはできません。 学生は自分の{% data variables.product.prodname_dotcom %}アカウントを作成しなければなりません。 + +{% endnote %} diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..556c770423 --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: Campus Expertsについて +intro: '学生として、{% data variables.product.prodname_dotcom %}Campus Expertsトレーニングで学校の技術コミュニティと実社会のポートフォリオを構築するのに必要なスキルを学んでください。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %}Campus Expertsとして、公の場でのスピーチのスキル、テクニカルライティング、コミュニティのリーダーシップ、ソフトウェア開発のスキルを学んでください。 詳しい情報については[Campus Experts](https://education.github.com/students/experts)を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..6274de490d --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: 教育者と研究者のためのGitHub Educationについて +intro: '{% data variables.product.prodname_education %}は、教室の内外で教育者や研究者がより効率的に働くことを支援するための様々なツールを提供します。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 教育者のための{% data variables.product.prodname_education %} + +あらゆるレベルの教育者のための {% data variables.product.prodname_education %} のツールとサービスで、以下のことができます: + - [{% data variables.product.prodname_classroom %}](https://classroom.github.com) を使ってコードを配布し、学生にフィードバックを与え、{% data variables.product.prodname_dotcom %} 上の課題を収集する。 + - 弊社の [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) に加わり、世界中の相手と技術教育における現在のトレンドについて議論する。 + - Git と {% data variables.product.prodname_dotcom %} を教えるための弊社の[オープンソースレッスン計画](https://education.github.community/t/open-source-lesson-plans/1591)にアクセスし、必要に応じて調整する。 + - 学生の教育のための素材が入った [{% data variables.product.prodname_dotcom %} のスワッグバッグをリクエスト](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33)する。 + {% data reusables.education.apply-for-team %} + +### 研究者のための {% data variables.product.prodname_education %} + +研究者のための {% data variables.product.prodname_education %} のツールとサービスで、以下のことができます: + - {% data variables.product.prodname_dotcom %} 上で世界中の人々と研究作業についてコラボレートする。 + - 世界中のアカデミックな組織が研究に {% data variables.product.prodname_dotcom %} をどのように使っているかを[学ぶ](https://education.github.com/stories)。 + {% data reusables.education.apply-for-team %} + +### 参考リンク + +- [学生向け {% data variables.product.prodname_education %}について](/articles/about-github-education-for-students) diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..36e5d4e463 --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: 学生のためのGitHub Educationについて +intro: '{% data variables.product.prodname_education %} は学生に対し、{% data variables.product.prodname_dotcom %} のパートナーからのさまざまな開発者ツールへの無料アクセスを含む実世界の体験を提供します。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +学校のプロジェクトで{% data variables.product.prodname_dotcom %}を利用することは、他者とコラボレーションして実世界の体験を見てもらうためのポートフォリオを構築するための実際的な方法です。 + +{% data reusables.education.about-github-education-link %} + +{% data variables.product.prodname_dotcom %} アカウントを持つ誰もが、{% data variables.product.prodname_free_user %} での無制限のパブリックおよびプライベートリポジトリで協業できます。 学生は {% data variables.product.prodname_student_pack %} に応募することもできます。これはプロフェッショナルの開発者が使用するツールやサービスへの無料アクセスを提供します。 For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +あなたが FIRST robotics club のメンバーなら、あなたの指導者はチームが {% data variables.product.prodname_team %} を使って協力し合うことができるよう、教育者割引に応募できます。これによって、無制限のユーザとプライベートリポジトリが無料で提供されます。 For more information, see "[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)." + +### 参考リンク + +- [教育者および研究者のための {% data variables.product.prodname_education %} について](/articles/about-github-education-for-educators-and-researchers) diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..071c5d269d --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: GitHub Educationについて +intro: '{% data variables.product.prodname_education %} は、{% data variables.product.prodname_dotcom %} を学校のコミュニティのために最大限に活用したいと考える、特定のプログラム要件に同意する学校に対し、特別な無料製品を提供します。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +あなたの中等学校、大学、ブートキャンプは、特定の要件を満たすことに合意すれば、{% data variables.product.prodname_education %} を入手できます。これによって、{% data variables.product.prodname_dotcom %} から最大のメリットを享受できます。メリットとしては以下のものがあります: +- {% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %} +- 弊社の Campus Advisor プログラムと合わせて Git と {% data variables.product.prodname_dotcom %} をマスターするための教師トレーニング +- {% data variables.product.prodname_student_pack %} のような、プレミアムの {% data variables.product.prodname_education %} の機能への自動化されたアクセス +- Campus Experts プログラムをあわせた学生のためのリーダーシップ開発と技術トレーニング + +詳しい情報については[公式{% data variables.product.prodname_education %}](https://education.github.com/partners/schools)ページを参照してください。 + +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)." + +学生のリーダー及び教師に対するトレーニングプログラムについて詳しく学ぶには、[{% data variables.product.prodname_dotcom %}Campus Experts](https://education.github.com/students/experts)及び[ Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。 + +あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_education %} スクールとしてパートナーになっていない場合は、個別に {% data variables.product.prodname_dotcom %} の利用の割引を申請できます。 For more information, see "[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)" or "[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/)." diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..9fbf9d62ce --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: Apply for a student developer pack +intro: '学生は {% data variables.product.prodname_student_pack %} に応募できます。これには {% data variables.product.prodname_dotcom %} パートナーからの特典が含まれます。' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 要件 + +{% data variables.product.prodname_student_pack %} に適格であるには、以下を満たしていなければなりません: +- 高等学校、中等学校、大学、ホームスクールまたはそれに類似した教育機関で、学位を取得できるコースに現在在籍している +- 学校が発行した検証可能なメールアドレスを持っているか、現在の在学状況を証明するドキュメントをアップロードしている +- [{% data variables.product.prodname_dotcom %} のユーザアカウント](/articles/signing-up-for-a-new-github-account)を持っている +- 最低でも 13 歳以上であること + +Documents that prove your current student status include a picture of your school ID with current enrollment date, class schedule, transcript, and affiliation or enrollment verification letter. + +学生としての在籍期間、定期的に現在の在学状況の再検証が求められることがあります。 + +{% note %} + +**メモ:** アカデミック割引をアカウント間で移譲することはできません。 割引を適用したいアカウントを複数持っているなら、ユーザアカウントを[マージ](/articles/merging-multiple-user-accounts)し、もしそうしたいなら残すアカウントの[名前を変更する](/articles/changing-your-github-username)ことを検討してください。 + +{% endnote %} + +{% data variables.product.prodname_student_pack %}の更新に関する詳しい情報については[期限切れと更新](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)を参照してください。 + +### {% data variables.product.prodname_student_pack %} への応募 + +{% data reusables.education.benefits-page %} +3. [Which best describes your academic status?（学業の状況を最もよく述べているのは？）] の下で、[** Student（学生）**] を選択してください。 ![学業の状況を選択](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### 期限切れと更新 + +{% data variables.product.prodname_student_pack %}アクセスが期限切れになった場合、まだあなたが適格であれば再応募できる場合があります。ただし、弊社のパートナーからの提供されているものの中には更新できないものがあります。 弊社のパートナーから期限付きで提供されているもののほとんどは、セットアップ後に開始されます。 詳しい情報については[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)ページを参照してください。 + +無料の {% data variables.product.prodname_student_pack %} プランへのアクセス期限が切れる時期を知るには、アカウントの[支払い設定](https://github.com/settings/billing)にアクセスしてください。 + +### 参考リンク + +- 「[{% data variables.product.prodname_student_pack %} への応募が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)」 +- [新しい {% data variables.product.prodname_dotcom %}アカウントへのサインアップ](/articles/signing-up-for-a-new-github-account) +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..0bb818342f --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: Apply for an educator or researcher discount +intro: '教育者もしくは研究者は、Organization アカウントに対して無料で {% data variables.product.prodname_team %} を受けるために応募できます。' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### 教育者および研究者に対する割引について + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### 教育者割引または研究者割引に応募する + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Organization をアップグレードする + +教育者もしくは研究者割引のリクエストが承認されると、学習コミュニティで利用する Organization を {% data variables.product.prodname_team %} にアップグレードできます。これで、無料で無制限のユーザとプライベートリポジトリの全ての機能が利用できるようになります。 既存の Organization をアップグレードするか、アップグレードする新しい Organization を作成できます。 + +#### 既存の Organization をアップグレードする + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### 新しい Organization をアップグレードする + +{% data reusables.education.upgrade-page %} +1. [{% octicon "plus" aria-label="The plus symbol" %} **Create an organization**] をクリックします。 ![[Create an organization] ボタン](/assets/images/help/education/create-org-button.png) +3. 情報を読んで、[**Create organization**] をクリックします。 ![[Create organization] ボタン](/assets/images/help/education/create-organization-button.png) +4. [Choose a plan] の下で、[**Choose {% data variables.product.prodname_free_team %}**] をクリックします。 +5. プロンプトに従って Organization を作成します。 +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### 参考リンク + +- [教育者あるいは研究者割引が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved) +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %}ビデオ](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..9c6384217d --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Explorer +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### 目次 + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..4ae7c09f8f --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub at your educational institution +intro: '{% data variables.product.prodname_education %} および学生やインストラクターのための弊社のさまざまなトレーニングプログラムを使って、学生、インストラクターや IT スタッフのために施設で {% data variables.product.prodname_dotcom %} を使うことのメリットを最大化してください。' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..4965211893 --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub for your schoolwork +intro: '学生として、{% data variables.product.prodname_dotcom %} を使用して学校のプロジェクトで共同作業を行い、現場経験を積んでください。' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..52ebb3f26e --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub in your classroom and research +intro: '教育者または研究者として、{% data variables.product.prodname_dotcom %} を使用して、教室、学生または研究グループなどで共同作業を行います。' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..e249d17b89 --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +title: 学生用開発者パックの申請が承認されなかったのはなぜですか？ +intro: '{% data variables.product.prodname_student_pack %} の申請が承認されていない一般的な理由を確認し、正常に再申請するためのヒントを学んでください。' +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**ヒント:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 所属文書の不明確な証明 + +アップロードした画像があなたの現在の学術ステータスを明確に識別していない場合は、学術ステータスのさらなる証明が必要です。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 未確認ドメインを持つ学術メールの使用 + +学術メールアドレスに未検証ドメインが含まれている場合、学術ステータスのさらなる証明が必要となります。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 緩い電子メールポリシーを持つ学校からの学術電子メールの使用 + +学校が有料学生登録の前にメールアドレスを発行する場合、学術ステータスのさらなる証明が必要となります。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +学校のドメインに関するその他の質問や懸念がある場合は、学校の IT スタッフにお問い合わせください。 + +### すでに使用されている学術メールアドレス + +別の {% data variables.product.prodname_dotcom %} アカウントの {% data variables.product.prodname_student_pack %} をリクエストするための学術メールアドレスが既に使用されていた場合、その割引が期限切れになるまでは、学術メールアドレスを再利用して別の {% data variables.product.prodname_student_pack %} を正常に申請することはできません。 + +{% note %} + +**メモ:** 複数の個別アカウントを維持することは、{% data variables.product.prodname_dotcom %} [利用規約](/articles/github-terms-of-service/#3-account-requirements)に反しています。 + +{% endnote %} + +複数の個人ユーザアカウントを持っている場合は、自分のアカウントをマージする必要があります。 割引を保持するには、割引を付与されたアカウントをそのままにします。 すべてのメールアドレスを保持アカウントに追加することで、保持アカウントの名前を変更したり、コントリビューション履歴を保存したりできます。 + +詳しい情報については、以下を参照してください。 +- 「[複数のユーザアカウントをマージする](/articles/merging-multiple-user-accounts)」 +- 「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username)」 +- 「[メールアドレスを {% data variables.product.prodname_dotcom %} アカウントに追加する](/articles/adding-an-email-address-to-your-github-account)」 + +### 対象外の学生ステータス + +以下の場合、{% data variables.product.prodname_student_pack %} の対象外となります: +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- 13 歳未満の場合。 + +インストラクターは、教室での使用に対して、{% data variables.product.prodname_education %} 割引を適用できます。 コーディングスクールやブートキャンプの学生は、学校が[{% data variables.product.prodname_dotcom %} キャンパスプログラム](https://education.github.com/schools)に参加した場合、{% data variables.product.prodname_student_pack %} を利用できるようになります。 + +### 参考リンク + +- 「[学生開発者パックに応募する](/articles/applying-for-a-student-developer-pack)」 +- "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..29af586574 --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: 教育者または研究者割引の申請が承認されなかったのはなぜですか？ +intro: 教育者または研究者割引の申請が承認されていない一般的な理由を確認し、正常に再申請するためのヒントを学びます。 +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**ヒント:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 所属文書の不明確な証明 + +アップロードした画像が現在の学校または大学での雇用を明確に識別していない場合、教職員 ID または雇用確認書の別の画像を明瞭な情報と共にアップロードして再申請する必要があります。 + +{% data reusables.education.pdf-support %} + +### 未確認ドメインを持つ学術メールの使用 + +学術メールアドレスに未確認ドメインが含まれている場合、学術ステータスの更なる証明が必要となります。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### 緩い電子メールポリシーを持つ学校からの学術電子メールの使用 + +学校の卒業生および退職した教職員が学校が発行したメールアドレスに一生アクセスできる場合は、学術ステータスの更なる証明が必要となります。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +学校のドメインに関するその他の質問や懸念がある場合は、学校のITスタッフにお問い合わせください。 + +### 学生以外が Student Developer Pack を申請する + +教育者や研究者は、[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)に付属のパートナーオファーの対象にはなりません。 再度申し込む際には、ご自身の学術ステータスを説明するものとして必ず [**Faculty**] (教職員) を選択してください。 + +### 参考リンク + +- "[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)" diff --git a/translations/ja-JP/content/education/guides.md b/translations/ja-JP/content/education/guides.md index 3511be3702..0e06cb3e11 100644 --- a/translations/ja-JP/content/education/guides.md +++ b/translations/ja-JP/content/education/guides.md @@ -12,8 +12,8 @@ Teachers, students, and researchers can use tools from {% data variables.product - [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) -- [Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) +- [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) ### Run a software development course with {% data variables.product.company_short %} @@ -32,7 +32,7 @@ Administer a classroom, assign and review work from your students, and teach the Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. - [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/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [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) @@ -41,5 +41,5 @@ Incorporate {% data variables.product.prodname_dotcom %} into your education, an 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) -- [Campus Expertsについて](/education/teach-and-learn-with-github-education/about-campus-experts) -- [Campus Advisorsについて](/education/teach-and-learn-with-github-education/about-campus-advisors) +- [Campus Expertsについて](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) +- [Campus Advisorsについて](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) diff --git a/translations/ja-JP/content/education/index.md b/translations/ja-JP/content/education/index.md index c3827df288..782c20b772 100644 --- a/translations/ja-JP/content/education/index.md +++ b/translations/ja-JP/content/education/index.md @@ -6,16 +6,16 @@ introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom @@ -41,5 +41,5 @@ versions: free-pro-team: '*' --- - + diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 91066d7f24..66a0ed4547 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ versions: ### 参考リンク -- [{% data variables.product.prodname_education %}で教える、学ぶ](/education/teach-and-learn-with-github-education) +- "[Explore the benefits of teaching and learning with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md index ec1c5bad6a..4ab7f49490 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -58,7 +58,7 @@ LTIは、情報の安全性と機密性を保つために役立ちます。 LTI 1. 外部ツールを設定します。 1. {% data variables.product.prodname_classroom %}で生成された構成認証情報を入力します。 - Consumer key - - Shared secret + - 共有シークレット - Launch URL (「ツールURL」などと呼ばれることもあります) ### Canvasを設定する @@ -113,7 +113,7 @@ Moodleのバージョンは3.0以上である必要があります。 | **LTI version** | LTI 1.0/1.1 | | **Default launch container** | 新規ウィンドウ | | **Consumer key** | {% data variables.product.prodname_classroom %}からのConsumer key | - | **Shared secret** | {% data variables.product.prodname_classroom %}からのShared secret | + | **共有シークレット** | {% data variables.product.prodname_classroom %}からのShared secret | 1. [**Services**] までスクロールしてクリックします。 1. [IMS LTI Names and Role Provisioning] の右にあるドロップダウンメニューを選択し、[**Use this service to retrieve members' information as per privacy settings**] をクリックします。 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index fdb54de2a6..782ee6f564 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -140,6 +140,6 @@ You can see the teams that are working on or have submitted an assignment in the ### 参考リンク -- "[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)" +- "[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/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index a5b2e6c39e..bb0d7322ac 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,8 +11,6 @@ You can use a template repository on {% data variables.product.product_name %} a To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." - ### 参考リンク - "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index 2fcd6b76a4..728b7bcf1d 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -120,5 +120,5 @@ You can see whether a student has joined the classroom and accepted or submitted ### 参考リンク -- "[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)" +- "[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/ja-JP/content/education/manage-coursework-with-github-classroom/index.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/index.md index fd004e5101..9b4de0d494 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 6e051e9d2d..e5dbcf02c1 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -4,5 +4,8 @@ intro: Learn how to set up your classroom and assignments. mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md index b06f523087..e845030093 100644 --- a/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,7 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." diff --git a/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md b/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md index 0748625b6b..8dcd7efdd5 100644 --- a/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md @@ -4,6 +4,7 @@ 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: free-pro-team: '*' + enterprise-server: '>=3.1' --- ### About renaming branches @@ -19,3 +20,15 @@ If you rename a branch, {% data variables.product.prodname_dotcom %} will automa 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) + +### Updating a local clone after a branch name changes + +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. + +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 +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 7305dbe8d3..06953242bc 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ versions: #### BFG を使用する -[BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) は、オープンソースコミュニティによって構築およびメンテナンスされているツールです。 これは、不要なデータを削除する手段として、`git filter-branch` より高速でシンプルです。 たとえば、機密データを含むファイルを削除して、最新のコミットをそのままにしておくには、次を実行します: +[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) は、オープンソースコミュニティによって構築およびメンテナンスされているツールです。 これは、不要なデータを削除する手段として、`git filter-branch` より高速でシンプルです。 たとえば、機密データを含むファイルを削除して、最新のコミットをそのままにしておくには、次を実行します: ```shell $ bfg --delete-files 機密データを含むファイル @@ -46,7 +46,7 @@ $ bfg --replace-text passwords.txt $ git push --force ``` -完全な使用方法とダウンロード手順については、[BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) のドキュメントを参照してください。 +完全な使用方法とダウンロード手順については、[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) のドキュメントを参照してください。 #### filter-branch を使用する diff --git a/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index abd66095ce..287a216337 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ Organization の設定内、もしくはユーザが作成した特定のコメ {% tip %} -**ヒント:**過熱した会話を鎮めるためにユーザをブロックする場合、コラボレータだけがコメントできるように[会話をロックする](/articles/locking-conversations)ことを検討してください。 +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. 詳細は「[会話をロックする](/github/building-a-strong-community/locking-conversations)」を参照してください。 {% endtip %} ユーザを Organization からブロックすると、以下のようになります: - そのユーザによる Organization のリポジトリの Watch は停止します。 - そのユーザによる Star 付けや Issue 割り当てはリポジトリから削除されます。 -- Organization のリポジトリのユーザのフォークが削除されます - Organization のリポジトリ内のディスカッションまたはコメントに対するユーザの投票が削除されます - そのユーザは、Organization のリポジトリのコラボレーターではなくなります。 - Organization のリポジトリへのユーザのコントリビューションがカウントされなくなります diff --git a/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 2fe42c6a28..6822e63b73 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### ユーザのブロックについて -自分のアカウント設定、もしくはユーザのプロファイルからユーザをブロックできます。 {% data variables.product.prodname_dotcom %}は、ユーザをブロックしてもユーザに通知しません。 ブロックした人と同じプロジェクトへのコントリビューションをしたくない場合には、ブロックしたユーザから以前にコントリビューションされているリポジトリで[警告を表示するように選択](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings)できます。 共有スペースでブロックされたユーザのアクティビティが引き続き表示される場合があり、ブロックされたユーザは既存のコンテンツを削除できます。 +自分のアカウント設定、もしくはユーザのプロファイルからユーザをブロックできます。 {% data variables.product.prodname_dotcom %}は、ユーザをブロックしてもユーザに通知しません。 If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see "[Blocking a user in your account settings](#blocking-a-user-in-your-account-settings)." 共有スペースでブロックされたユーザのアクティビティが引き続き表示される場合があり、ブロックされたユーザは既存のコンテンツを削除できます。 {% tip %} -**ヒント:**過熱した会話を鎮めるためにユーザをブロックする場合、コラボレータだけがコメントできるように[会話をロックする](/articles/locking-conversations)ことを検討してください。 +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. 詳細は「[会話をロックする](/github/building-a-strong-community/locking-conversations)」を参照してください。 {% endtip %} @@ -22,8 +22,6 @@ versions: - ユーザがリポジトリの Watch を停止し、リポジトリのピン留めを解除します - ユーザはあなたがオーナーの Organization に参加できません - そのユーザによる Star 付けや Issue 割り当てはリポジトリから削除されます。 -- リポジトリのユーザのフォークが削除されます -- ユーザのリポジトリのフォークを削除します - リポジトリ内のディスカッションまたはコメントに対するユーザの投票が削除されます - そのユーザは、あなたのリポジトリのコラボレーターではなくなります - リポジトリへのユーザのコントリビューションがカウントされなくなります diff --git a/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 3fab705e85..45a0944e21 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ YAML frontmatter を各 Issue テンプレートに追加して、Issue のタ YAML front matter の例は次のとおりです。 -``` +```yaml --- name: Tracking issue about: Use this template for tracking new features. diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index 307a68625b..e3b8419515 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ versions: 4. [Atom](https://atom.io/) などのお気に入りのテキスト エディターを開き、マージ コンフリクトが発生しているファイルに移動します。 5. ファイル内でマージ コンフリクトの始まりを確認するには、ファイル内のコンフリクト マーカー `<<<<<<<` を検索します。 テキストエディタでファイルを開くと、`<<<<<<< HEAD` 行の後に HEAD ブランチまたはベースブランチからの変更が見えます。 次に、`=======` が見えます。これは、自分の変更と他のブランチの変更を区別するもので、その後に `>>>>>>> BRANCH-NAME` が続きます。 この例では、ある人がベースまたは HEAD ブランチで「open an issue」と書き込み、別の人が compare ブランチまたは `branch-a` に「ask your question in IRC」と書き込みました。 - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}この例では、両方の変更が最終的なマージに取り込まれます。 ```shell diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 469a8e4038..9c428361ac 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ Pre-receive フックは、コントリビューションがリポジトリま プッシュが受け入れられない場合は、失敗した pre-receive フックに対応するエラーメッセージが表示されます。 -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md index 5ee86a477d..8b82f110fe 100644 --- a/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,7 +19,7 @@ versions: {% data reusables.actions.actions-not-verified %} -誰でも {% data variables.product.prodname_marketplace %} に無料の {% data variables.product.prodname_github_app %} または {% data variables.product.prodname_oauth_app %} をリストできます。 有料アプリケーションのパブリッシャーは {% data variables.product.company_short %} によって検証され、これらのアプリケーションのリストには検証済みの作者バッジ {% octicon "verified" aria-label="Verified creator badge" %} が表示されます。 未検証および検証済みのアプリケーションのバッジも表示されます。 これらのアプリケーションは、個々のアプリケーションを検証する以前の方法を使用して公開されました。 現在のプロセスの詳細については、「[検証済みの作者について](/developers/github-marketplace/about-verified-creators)」および「[アプリケーションを一覧表示するための要件](/developers/github-marketplace/requirements-for-listing-an-app)」を参照してください。 +誰でも {% data variables.product.prodname_marketplace %} に無料の {% data variables.product.prodname_github_app %} または {% data variables.product.prodname_oauth_app %} をリストできます。 Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. 未検証および検証済みのアプリケーションのバッジも表示されます。 これらのアプリケーションは、個々のアプリケーションを検証する以前の方法を使用して公開されました。 For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### {% data variables.product.prodname_marketplace %} でツールを構築およびリストする diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index d99e3e6568..25ed0126b4 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ To integrate {% data variables.product.prodname_code_scanning %} into your CI sy In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -39,7 +39,7 @@ The {% data variables.product.prodname_codeql_runner %} automatically detects an To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. サポートされている言語のキーワードは、`cpp`、`csharp`、`go`、`java`、`JavaScript`、および `python` です。 -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -55,7 +55,7 @@ If you also are using a configuration file for custom settings, and you are also In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. -``` +```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 ``` @@ -68,7 +68,7 @@ The configuration file is a YAML file. It uses syntax similar to the workflow sy Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. -``` +```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml ``` @@ -84,7 +84,7 @@ For many common build systems, the {% data variables.product.prodname_codeql_run The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. -``` +```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index a2eb453614..f8364118a5 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ You can set up {% data variables.product.prodname_code_scanning %} to check the 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### About alerts details Each alert highlights a problem with the code and the name of the tool that identified it. アラートをトリガーしたコード行と、アラートのプロパティ（問題の重要度や性質など）を確認できます。 アラートは、問題が最初に発生したときにも通知します。 For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem. diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 82d80089de..ca841f17d1 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -93,6 +93,8 @@ You can configure where the {% data variables.product.prodname_codeql_runner %} To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Basic example This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index c17ad6e046..4f4a58e944 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -40,6 +40,8 @@ If you upload a SARIF file without fingerprint data using the `/code-scanning/sa You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### サポートされている SARIF 出力ファイルのプロパティ {% data variables.product.prodname_codeql %} 以外のコード分析エンジンを使用する場合、サポートされている SARIF プロパティを確認して、{% data variables.product.prodname_dotcom %} での分析結果の表示方法を最適化できます。 @@ -82,6 +84,8 @@ You can check a SARIF file is compatible with {% data variables.product.prodname #### `result` オブジェクト +{% data reusables.code-scanning.upload-sarif-alert-limit %} + | 名前 | 説明 | | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ruleId` | **任意。**ルールの一意の識別子（`reportingDescriptor.id`）。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。 {% data variables.product.prodname_code_scanning_capc %} は、ルール識別子を使用して、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタします。 | @@ -89,7 +93,7 @@ You can check a SARIF file is compatible with {% data variables.product.prodname | `rule` | **任意。**この結果のルール（レポート記述子）を見つけるために使用される参照。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。 | | `level` | **任意。**結果の重要度。 このレベルは、ルールで定義されているデフォルトの重要度をオーバーライドします。 {% data variables.product.prodname_code_scanning_capc %} は、レベルを使用して、{% data variables.product.prodname_dotcom %} の重要度で結果をフィルタします。 | | `message.text` | **必須。**結果を説明するメッセージ。 {% data variables.product.prodname_code_scanning_capc %} は、結果のタイトルとしてメッセージテキストを表示します。 表示スペースが限られている場合、メッセージの最初の文のみが表示されます。 | -| `locations[]` | **必須。**結果が検出された場所。 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。 | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。 | | `partialFingerprints` | **必須。**結果の一意の ID を追跡するために使用される文字列。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` を使用して、コミットとブランチで同じ結果であるものを正確に識別します。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` がある場合、それを使用しようとします。 `upload-action` を使用してサードパーティの SARIF ファイルをアップロードする場合、SARIF ファイルに含まれていないときに、アクションによって `partialFingerprints` が作成されます。 詳しい情報については、「[フィンガープリントを使用してアラートの重複を防止する](#preventing-duplicate-alerts-using-fingerprints)」を参照してください。 **注釈:** {% data variables.product.prodname_code_scanning_capc %} は、`primaryLocationLineHash` のみを使用します。 | | `codeFlows[].threadFlows[].locations[]` | **任意。**`threadFlow` オブジェクトに対する `location` オブジェクトの配列。実行スレッドを通してプログラムの進行状況を記述します。 `codeFlow` オブジェクトは、結果の検出に使用されるコード実行パターンを記述します。 コードフローが入力されている場合、{% data variables.product.prodname_code_scanning %} は、関連する結果の {% data variables.product.prodname_dotcom %} のコードフローを拡張します。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。 | | `relatedLocations[]` | この結果に関連する場所。 結果メッセージに埋め込まれている場合、{% data variables.product.prodname_code_scanning_capc %} は、関連する場所にリンクします。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。 | diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 46eee216d4..755fc18e12 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -39,6 +39,8 @@ You can upload the results using {% data variables.product.prodname_actions %}{% SARIF ファイルに `partialFingerprints` が含まれていない場合、`upload-sarif` アクションは、`partialFingerprints` フィールドを計算し、アラートの重複を防止しようと試みます。 {% data variables.product.prodname_dotcom %} は、リポジトリに SARIF ファイルと静的分析で使用されるソースコードの両方が含まれている場合にのみ、`partialFingerprints` を作成できます。 重複アラートの防止に関する詳しい情報については、「[コードスキャンに対する SARIF サポートについて](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)」を参照してください。 +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### リポジトリ外で生成された SARIF ファイルのワークフロー例 SARIF ファイルをリポジトリにコミットした後でアップロードする新しいワークフローを作成できます。 これは、SARIF ファイルがリポジトリ外のアーティファクトとして生成される場合に役立ちます。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md index edc7c1d525..cb310269c0 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/ja-JP/content/github/getting-started-with-github/about-github-advanced-security.md @@ -1,6 +1,6 @@ --- -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. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +title: GitHub Advanced Securityについて +intro: '{% data variables.product.prodname_dotcom %}では、{% data variables.product.prodname_advanced_security %}ライセンスのもとでセキュリティ機能がさらに強化されます。 これらの機能は、{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリに対しても有効になります。' versions: free-pro-team: '*' enterprise-server: '>=3.0' @@ -8,40 +8,40 @@ versions: ### {% data variables.product.prodname_GH_advanced_security %} について -{% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) +{% data variables.product.prodname_dotcom %}には、コードの質を改善し維持できる多くの機能があります。 依存関係グラフや{% data variables.product.prodname_dependabot_alerts %}など、一部の機能はすべてのプランに含まれます。 それ以外のセキュリティ機能には、{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリとは別のリポジトリで{% data variables.product.prodname_GH_advanced_security %}のライセンスを実行する必要があります。 (つまり、{% data variables.product.prodname_dotcom_the_website %}のプライベートおよび内部リポジトリと、{% data variables.product.prodname_ghe_server %}のすべてのリポジトリです。) -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +セキュリティ機能すべての概要については、「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)」を参照してください。 セキュリティ機能に関連するアクションの権限要件に関する詳しい情報については、「[Organization のリポジトリの権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)」を参照してください。 -### About {% data variables.product.prodname_advanced_security %} features +### {% data variables.product.prodname_advanced_security %}機能について -A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: +{% data variables.product.prodname_GH_advanced_security %}のライセンスでは、以下の機能が追加されます。 -- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. 詳しい情報については、「[{% 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 %}** - コードで、潜在的なセキュリティの脆弱性とコーディングエラーを検索します。 詳しい情報については、「[{% 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 %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} について](/github/administering-a-repository/about-secret-scanning)」を参照してください。 +- **{% data variables.product.prodname_secret_scanning_caps %}** - シークレット、たとえばリポジトリにチェックインされているキーやトークンなどを検出します。 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} について](/github/administering-a-repository/about-secret-scanning)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} -- **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 "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +- **依存関係のレビュー** - プルリクエストをマージする前に、依存関係に対する変更の影響を詳細に示し、脆弱性なバージョンがあればその詳細を確認できます。 For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." {% endif %} -For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." +開発中の{% data variables.product.prodname_advanced_security %}機能については、「[{% data variables.product.prodname_dotcom %} パブリックロードマップ](https://github.com/github/roadmap).」を参照してください。 {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} +### {% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_advanced_security %}機能を有効にする -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)." +この機能を使用するには、サイト管理者が{% data variables.product.product_location %}の{% data variables.product.prodname_advanced_security %}を有効にする必要があります。 詳しい情報については、「[高度なセキュリティ機能を設定する](/admin/configuration/configuring-advanced-security-features)」を参照してください。 -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](/github/setting-up-and-managing-organizations-and-teams/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)." +システムを設定すると、Organizationまたはリポジトリのレベルでこの機能を有効化または無効化することができます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」と「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 For information about purchasing a license for {% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. {% endif %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} +### {% data variables.product.prodname_dotcom_the_website %}で{% data variables.product.prodname_advanced_security %}機能を有効にする -For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. +{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリの場合、この機能は永続的に有効になっており、無効にできるのはプロジェクトの可視性背を変更して、コードがパブリックでなくなった場合だけです。 -For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/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)." +その他すべてのリポジトリの場合は、ライセンスを有効にするとOrganizationまたはリポジトリのレベルでこの機能を有効化または無効化することができます。 {% if currentVersion == "free-pro-team@latest" %}詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」と「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 For information about purchasing a license for {% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md index f2773acb76..2c0fd418e0 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ authors: {% endif %} -[bootcamp](/categories/bootcamp/) 記事で、{% data variables.product.product_name %} に精通しましょう。 [{% data variables.product.prodname_dotcom %} のフロー](https://guides.github.com/introduction/flow)でプロセスの紹介をご確認ください。 [概要ガイド](https://guides.github.com)を参照して基本的な概念をご覧ください。 +Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. [{% data variables.product.prodname_dotcom %} のフロー](https://guides.github.com/introduction/flow)でプロセスの紹介をご確認ください。 [概要ガイド](https://guides.github.com)を参照して基本的な概念をご覧ください。 {% data reusables.support.ask-and-answer-forum %} #### ブランチ、フォーク、プルリクエスト -インタラクティブなツールを使用して、[Git のブランチ](http://learngitbranching.js.org/)について学びましょう。 [フォーク](/articles/about-forks)や[プルリクエスト](/articles/using-pull-requests)、および {% data variables.product.prodname_dotcom %} で[プルリクエストがどのように使用されているのか](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github)をお読みください。 - -[コマンドライン](https://hub.github.com)についてのクイックリファレンスや、{% data variables.product.prodname_dotcom %} の[チェックリスト、チートシートなど](https://services.github.com/on-demand/resources)にアクセスしてください。 +インタラクティブなツールを使用して、[Git のブランチ](http://learngitbranching.js.org/)について学びましょう。 [フォーク](/articles/about-forks)や[プルリクエスト](/articles/using-pull-requests)、および {% data variables.product.prodname_dotcom %} で[プルリクエストがどのように使用されているのか](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github)をお読みください。 Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). #### 動画 @@ -41,9 +39,9 @@ authors: ### トレーニング -#### 無料クラス +#### Free courses -{% data variables.product.product_name %} では、インタラクティブな [オンデマンドのトレーニングコース](https://services.github.com/on-demand/)のシリーズを提供しています。これには、{% data variables.product.prodname_dotcom %}101: [導入](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %}102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop)、および{% data variables.product.prodname_dotcom %}103: [コマンドライン](https://services.github.com/on-demand/github-cli)が含まれます。 +{% 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 %}. #### {% data variables.product.prodname_dotcom %}のウェブベース教育プログラム @@ -51,7 +49,7 @@ authors: #### 企業向けトレーニング -{% data variables.product.prodname_dotcom %} では、経験豊富な教育者による[対面クラス](https://services.github.com/#offerings)を提供しています。 トレーニングに関するお問い合わせについては、[こちら](https://services.github.com/#contact)までどうぞ。 +{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. トレーニングに関するお問い合わせについては、[こちら](https://services.github.com/#contact)までどうぞ。 ### その他 diff --git a/translations/ja-JP/content/github/getting-started-with-github/git-cheatsheet.md b/translations/ja-JP/content/github/getting-started-with-github/git-cheatsheet.md index c91d697035..a47857b789 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/ja-JP/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -使用可能なすべての Git コマンドを一回で覚えるのは大変です。 参照用に、[Git チートシート](https://services.github.com/on-demand/resources/cheatsheets/)を 1 枚手元に置いておきましょう。 Git チートシートには複数の言語版があります。 詳細は [GitHub Services ウェブサイトのリソースページ](https://services.github.com/on-demand/resources/)を参照してください。 +使用可能なすべての Git コマンドを一回で覚えるのは大変です。 Our cheat sheets provide a quick reference for the commands you'll use most often: see "[Git Cheat Sheets](https://training.github.com/)." The "Using Git" cheat sheet is available in several languages. また、ガイドや動画などのリンクが掲載された [Git と GitHub の学習リソース](/articles/git-and-github-learning-resources/)ページもご覧ください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md index 958b201407..2dd5a74a0e 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md @@ -26,19 +26,19 @@ versions: Android または iOS に {% data variables.product.prodname_mobile %} をインストールするには、「[{% data variables.product.prodname_mobile %}](https://github.com/mobile)」を参照してください。 -### Managing accounts +### アカウントの管理 -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 variables.product.prodname_dotcom_the_website %} のユーザーアカウントと、{% data variables.product.prodname_ghe_server %}のユーザーアカウントとを使用して同時にモバイルにサインインすることができます。 {% data reusables.mobile.push-notifications-on-ghes %} -{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. +VPN で Enterprise にアクセスする必要がある場合、{% data variables.product.prodname_mobile %} は Enterprise では動作しません。 #### 必要な環境 -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 %}. +{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_mobile %} を使用するには、デバイスに {% data variables.product.prodname_mobile %} 1.4 以降をインストールする必要があります。 -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 "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)." +{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_mobile %} を使用するには、{% data variables.product.product_location %} がバージョン 3.0 以降であり、Enterprise オーナーが Enterprise に対してモバイルサポートを有効にしている必要があります。 詳しい情報については、「[リリースノート](/enterprise-server/admin/release-notes)」と「[Enterprise 向けに {% data variables.product.prodname_mobile %} を管理する](/admin/configuration/managing-github-for-mobile-for-your-enterprise)」を参照してください。 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 %}. diff --git a/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md index 5a31b272c6..4f85eaa0a4 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md +++ b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md @@ -85,6 +85,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる - {% data variables.contact.enterprise_support %}。 詳細は「{% data variables.product.prodname_ghe_cloud %} サポート」および「{% data variables.product.prodname_ghe_cloud %} 補遺」を参照してください。 - 50,000 {% data variables.product.prodname_actions %} 分 - 50GBの{% data variables.product.prodname_registry %}ストレージ +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - 99.9% の月次稼働時間を保証するサービスレベルアグリーメント - エンタープライズアカウントで複数の {% data variables.product.prodname_dotcom_the_website %} Organization に対してポリシーと請求を一元管理するためのオプション。 詳細は「Enterprise アカウントについて」を参照してください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md index 71601cb90a..bc57689ae8 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -76,7 +76,8 @@ versions: | control shift p または command shift p | **Write** と **Preview** のコメントタブを切り替えます。 | | control enter | コメントをサブミットします | | control .、次に control [返信テンプレート番号] | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳しい情報については「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% if currentVersion == "free-pro-team@latest" %} -| control g または command g | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/articles/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 |{% endif %} +| control g または command g | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/articles/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 +{% endif %} | r | 返信で選択したテキストを引用します。 詳細は「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」を参照してください。 | ### Issue およびプルリクエストのリスト @@ -111,7 +112,8 @@ versions: | k | リストで選択を上に移動します | | cmd + shift + enter | プルリクエストの差分にコメントを 1 つ追加します | | alt およびクリック | `alt` キーを押しながら [**Show outdated**] または [**Hide outdated**] をクリックして、プルリクエスト内のすべての古いレビューコメントの折りたたみと展開を切り替えます。|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| クリック後、shift およびクリック | プルリクエストの複数行にコメントするには、行番号をクリックし、shift を押したまま、別の行番号をクリックします。 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。|{% endif %} +| クリック後、shift およびクリック | プルリクエストの複数行にコメントするには、行番号をクリックし、shift を押したまま、別の行番号をクリックします。 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。 +{% endif %} ### プロジェクトボード diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index de9b1acce7..9188c44571 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,10 +45,10 @@ versions: 7. {% data variables.product.product_name %} リポジトリの Quick Setup ページの上部で、{% octicon "clippy" aria-label="The copy to clipboard icon" %} をクリックしてリモートリポジトリの URL をコピーします。 ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. ターミナルで、ローカルリポジトリがプッシュされる[リモートリポジトリの URL を追加](/articles/adding-a-remote)してください。 ```shell - $ git remote add origin remote repository URL - # 新しいリモートの設定 + $ git remote add origin <REMOTE_URL> + # Sets the new remote $ git remote -v - # 新しいリモートリポジトリの検証 + # Verifies the new remote URL ``` 9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/articles/pushing-commits-to-a-remote-repository/)します。 ```shell @@ -83,10 +83,10 @@ versions: 7. {% data variables.product.product_name %} リポジトリの Quick Setup ページの上部で、{% octicon "clippy" aria-label="The copy to clipboard icon" %} をクリックしてリモートリポジトリの URL をコピーします。 ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. コマンドプロンプトで、ローカルリポジトリのプッシュ先となる[リモートリポジトリの URL を追加](/articles/adding-a-remote)します。 ```shell - $ git remote add origin remote repository URL - # 新しいリモートの設定 + $ git remote add origin <REMOTE_URL> + # Sets the new remote $ git remote -v - # 新しいリモートリポジトリの検証 + # Verifies the new remote URL ``` 9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/articles/pushing-commits-to-a-remote-repository/)します。 ```shell @@ -121,10 +121,10 @@ versions: 7. {% data variables.product.product_name %} リポジトリの Quick Setup ページの上部で、{% octicon "clippy" aria-label="The copy to clipboard icon" %} をクリックしてリモートリポジトリの URL をコピーします。 ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. ターミナルで、ローカルリポジトリがプッシュされる[リモートリポジトリの URL を追加](/articles/adding-a-remote)してください。 ```shell - $ git remote add origin remote repository URL - # 新しいリモートの設定 + $ git remote add origin <REMOTE_URL> + # Sets the new remote $ git remote -v - # 新しいリモートリポジトリの検証 + # Verifies the new remote URL ``` 9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/articles/pushing-commits-to-a-remote-repository/)します。 ```shell diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md index 5643f5d2d3..67f2878707 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### {% data variables.product.prodname_dotcom %} のナビゲーションコードについて -コードナビゲーションの機能は、オープンソースの ライブラリ[`semantic`](https://github.com/github/semantic)を使用しています。 以下の言語がサポートされています: +Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). 以下の言語がサポートされています: - C# - CodeQL - Go diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index bd8241ec49..7e1113d8d2 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ When you publish a security advisory, you notify your community about the securi Before you publish a security advisory, you can privately collaborate to fix the vulnerability in a temporary private fork. 詳細は「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照してください。 +{% warning %} + +**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to. + +We recommend you take the following steps in these different situations: + +- If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready. +- If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication. +- If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue. + +{% endwarning %} + When you publish a draft advisory from a public repository, everyone is able to see: - The current version of the advisory data. diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/ja-JP/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 400403e4bb..acd5547325 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: 他のリポジトリにオープン Issue を移譲するには、Issue のあるリポジトリおよびその Issue の移譲先のリポジトリの書き込み権限が必要です。 詳細は「[Organization のためのリポジトリの権限レベル](/articles/repository-permission-levels-for-an-organization)」を参照してください。 -Issue を移動できるのは、同じユーザーまたは Organization アカウントが所有しているリポジトリ間のみです。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}プライベートリポジトリからパブリックリポジトリへ Issue を移譲することはできません。{% endif %} +同じユーザまたは Organization アカウントが所有するリポジトリ間においてのみ、Issue を移譲できます。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} Issueを委譲する場合、コメントとアサインされた人は保持されます。 Issue のラベルとマイルストーンは保持されません。 このIssueは、ユーザー所有または組織全体のプロジェクトボードにとどまり、リポジトリのプロジェクトボードから削除されます。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 diff --git a/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index e1807f3214..00fd605ead 100644 --- a/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,7 +25,8 @@ versions: | `To` フィールド | このフィールドは、直接スレッドに接続します。 メールに返信すると、会話に新しいコメントを追加することになります。 | | `Cc` アドレス | あなたが会話をサブスクライブしていれば、{% data variables.product.product_name %}はあなたに `Cc` します。 2番目の`Cc`メールアドレスは、通知の理由にマッチします。 これらの通知理由に対するサフィックスは{% data variables.notifications.cc_address %}です。 通知の理由には以下のようなものがあります。
    • `assign`: 受信者はIssueあるいはプルリクエストに割り当てられました。
    • `author`: 受信者はIssueあるいはプルリクエストの作者です。
    • `comment`: 受信者はIssueあるいはプルリクエストにコメントしました。
    • `manual`: 手作業でサブスクライブした Issue あるいはプルリクエストが更新されました。
    • `mention`: 受信者は Issue あるいはプルリクエストにメンションされました。
    • `push`: 受信者がサブスクライブしているプルリクエストに誰かがコミットしました。
    • `review_requested`: 受信者あるいは受信者がメンバーになっている Team にプルリクエストのレビューがリクエストされました。
    • `security_alert`: {% data variables.product.prodname_dotcom %} は、受信者がセキュリティのアラートを受け取るリポジトリに脆弱性を検出しました。
    • `state_change`: 受信者がサブスクライブしている Issue あるいはプルリクエストがクローズもしくはオープンされました。
    • `subscribed`: 受信者が Watch しているリポジトリに更新がありました。
    • `team_mention`: 受信者が属している Team が Issue あるいはプルリクエストでメンションされました。
    • `your_activity`: 受信者が Issue あるいはプルリクエストをオープン、コメントあるいはクローズしました。
    | | `mailing list` フィールド | このフィールドはリポジトリの名前とそのオーナーを特定します。 このアドレスのフォーマットは常に`..{% data variables.command_line.backticks %}`となります。 |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| `X-GitHub-Severity`フィールド | {% data reusables.repositories.security-alerts-x-github-severity %} 考えられる重大度レベルは次のとおりです。
    • `low`
    • `moderate`
    • `high`
    • `critical`
    詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 |{% endif %} +| `X-GitHub-Severity`フィールド | {% data reusables.repositories.security-alerts-x-github-severity %} 考えられる重大度レベルは次のとおりです。
    • `low`
    • `moderate`
    • `high`
    • `critical`
    詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 +{% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 6ca329b897..e863d5a2f0 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ You can filter by the visibility of the repository containing the issues and pul | `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされている Issue に一致します。 | | `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされた可能性がある Issue にリンクされていた、クローズされたプルリクエストに一致します。 | | `-linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされていない Issue に一致します。 | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 |{% endif %} +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 +{% endif %} ### ラベルで検索 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 4f3d5d5d23..0f790467c4 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### 個人アカウントへの割引 -{% data variables.product.prodname_free_user %} で学生と教員が無制限のパブリックリポジトリとプライベートリポジトリを使用できることに加えて、検証済みの学生は {% data variables.product.prodname_student_pack %} に申請し、{% data variables.product.prodname_dotcom %} パートナーからのさらなるメリットを受けていただけます。 For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." +{% data variables.product.prodname_free_user %} で学生と教員が無制限のパブリックリポジトリとプライベートリポジトリを使用できることに加えて、検証済みの学生は {% data variables.product.prodname_student_pack %} に申請し、{% data variables.product.prodname_dotcom %} パートナーからのさらなるメリットを受けていただけます。 For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)." ### 学校・大学向け割引 -検証済みの教職員は教育や学術研究の目的で {% data variables.product.prodname_team %} に申し込むことができます。 For more information, see "[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)." また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。 +検証済みの教職員は教育や学術研究の目的で {% data variables.product.prodname_team %} に申し込むことができます。 For more information, see "[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)." また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。 ### 非営利目的や図書館への割引 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md index e821691e3c..fa54c2cf2f 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..a4e831e5ee --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses +{% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. そのサイトは手動で取り下げることができます。 詳細は「[{% data variables.product.prodname_pages %}サイトの取り下げ](/github/working-with-github-pages/unpublishing-a-github-pages-site)」を参照してください。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. [**Save**] をクリックします。 + +### 参考リンク + +- [{% data variables.product.prodname_pages %}について](/github/working-with-github-pages/about-github-pages) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index a4ed1f9db0..dbdcfa1cd3 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ Organization のメンバーは、*owner (オーナー)*{% if currentVersion == {% if currentVersion == "free-pro-team@latest" %} -| Organization のアクション | オーナー | メンバー | 支払いマネージャー | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-----:|:-----:|:--------------------------------------------------:| -| リポジトリの作成 (詳細については「[Organization 内でリポジトリの作成を制限する](/articles/restricting-repository-creation-in-your-organization)」を参照) | **X** | **X** | | -| 支払い情報を表示および編集する | **X** | | **X** | -| Organization に参加するようユーザを招待する | **X** | | | -| Organization に参加する招待を編集およびキャンセルする | **X** | | | -| Organization からメンバーを削除する | **X** | | | -| 以前のメンバーを Oraganization に復帰させる | **X** | | | -| **すべての Team** に対してユーザーを追加および削除する | **X** | | | -| Organization メンバーを*チームメンテナ*に昇格させる | **X** | | | -| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)を参照) | **X** | | | -| スケジュールされたリマインダーを設定する (「[プルリクエストのスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)」を参照) | **X** | | | -| **すべてのリポジトリに**コラボレーターを追加する | **X** | | | -| Organization 参加ログにアクセスする | **X** | | | -| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照) | **X** | | | -| Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照) | **X** | | | -| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | -| **すべての Team** を削除する | **X** | | | -| すべてのリポジトリを含めて Organization のアカウントを削除する | **X** | | | -| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照) | **X** | **X** | | -| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照) | **X** | **X** | | -| Organization の全メンバーおよび Team の表示 | **X** | **X** | | -| 参照可能なチームへの @メンション | **X** | **X** | | -| *チームメンテナ*に指定できる | **X** | **X** | | -| Organization のインサイトを表示する (詳細は「[Organization のインサイトを表示する](/articles/viewing-insights-for-your-organization)」を参照) | **X** | **X** | | -| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | **X** | | -| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | | | -| **すべての Team** で Team ディスカッションを編集および削除する (詳細は「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | | | -| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | **X** | | -| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} -| Organization dependency insights の可視性を管理する (詳細は「[Organization dependency insights の可視性を変更する](/articles/changing-the-visibility-of-your-organizations-dependency-insights)」を参照) | **X** | | |{% endif %} -| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | | -| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | -| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | -| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | -| Organization のリポジトリから {% data variables.product.prodname_pages %} サイトを公開するのを無効にする (詳細、「[Organization の {% data variables.product.prodname_pages %} サイトの公開を無効化する](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)」を参照) | **X** | | | -| Organization のセキュリティおよび分析設定を管理する (詳細は「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」を参照) | **X** | | | -| [SAML シングルサインオン](/articles/about-identity-and-access-management-with-saml-single-sign-on)を有効にして強制する | **X** | | | -| [組織へのユーザーの SAML アクセスを管理する](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | -| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | | -| リポジトリを移譲する | **X** | | | -| {% data variables.product.prodname_marketplace %} アプリケーションを購入、インストール、支払い管理、キャンセルする | **X** | | | -| {% data variables.product.prodname_marketplace %} のアプリケーションをリストする | **X** | | |{% if currentVersion != "github-ae@latest" %} -| Organization のリポジトリすべてについて、脆弱な依存関係についての [{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) アラートを受け取る | **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** | | |{% endif %} -| [フォークポリシーの管理](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Organization のパブリックリポジトリでのアクティビティを制限する](/articles/limiting-interactions-in-your-organization) | **X** | | | -| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー) | **X** | | | -| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換 | **X** | | | -| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| デフォルブランチ名を管理する (「[Organization のリポジトリのデフォルブランチ名を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照) | **X** | | | -| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照) | **X** | | | -| Team の同期を有効化する (「[Organization の Team 同期を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)」を参照) | **X** | | | +| Organization のアクション | オーナー | メンバー | 支払いマネージャー | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:---------:| +| リポジトリの作成 (詳細については「[Organization 内でリポジトリの作成を制限する](/articles/restricting-repository-creation-in-your-organization)」を参照) | **X** | **X** | | +| 支払い情報を表示および編集する | **X** | | **X** | +| Organization に参加するようユーザを招待する | **X** | | | +| Organization に参加する招待を編集およびキャンセルする | **X** | | | +| Organization からメンバーを削除する | **X** | | | +| 以前のメンバーを Oraganization に復帰させる | **X** | | | +| **すべての Team** に対してユーザーを追加および削除する | **X** | | | +| Organization メンバーを*チームメンテナ*に昇格させる | **X** | | | +| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)を参照) | **X** | | | +| スケジュールされたリマインダーを設定する (「[プルリクエストのスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)」を参照) | **X** | | | +| **すべてのリポジトリに**コラボレーターを追加する | **X** | | | +| Organization 参加ログにアクセスする | **X** | | | +| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照) | **X** | | | +| Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照) | **X** | | | +| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | +| **すべての Team** を削除する | **X** | | | +| すべてのリポジトリを含めて Organization のアカウントを削除する | **X** | | | +| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照) | **X** | **X** | | +| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照) | **X** | **X** | | +| Organization の全メンバーおよび Team の表示 | **X** | **X** | | +| 参照可能なチームへの @メンション | **X** | **X** | | +| *チームメンテナ*に指定できる | **X** | **X** | | +| Organization のインサイトを表示する (詳細は「[Organization のインサイトを表示する](/articles/viewing-insights-for-your-organization)」を参照) | **X** | **X** | | +| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | **X** | | +| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | | | +| **すべての Team** で Team ディスカッションを編集および削除する (詳細は「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | | | +| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | **X** | | +| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | | +| Organization dependency insights の可視性を管理する (詳細は「[Organization dependency insights の可視性を変更する](/articles/changing-the-visibility-of-your-organizations-dependency-insights)」を参照) | **X** | | | +| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | +| Organization のセキュリティおよび分析設定を管理する (詳細は「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」を参照) | **X** | | | +| [SAML シングルサインオン](/articles/about-identity-and-access-management-with-saml-single-sign-on)を有効にして強制する | **X** | | | +| [組織へのユーザーの SAML アクセスを管理する](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | | +| リポジトリを移譲する | **X** | | | +| {% data variables.product.prodname_marketplace %} アプリケーションを購入、インストール、支払い管理、キャンセルする | **X** | | | +| {% data variables.product.prodname_marketplace %} のアプリケーションをリストする | **X** | | | +| Organization のリポジトリすべてについて、脆弱な依存関係についての [{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) アラートを受け取る | **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** | | | +| [フォークポリシーの管理](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Organization のパブリックリポジトリでのアクティビティを制限する](/articles/limiting-interactions-in-your-organization) | **X** | | | +| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー) | **X** | | | +| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換 | **X** | | | +| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| デフォルブランチ名を管理する (「[Organization のリポジトリのデフォルブランチ名を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照) | **X** | | | +| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照) | **X** | | | +| Team の同期を有効化する (「[Organization の Team 同期を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)」を参照) | **X** | | | {% else %} -| Organization のアクション | オーナー | メンバー | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-----:|:---------------------------------------------------------------------------------------------------:| -| Organization に参加するようユーザを招待する | **X** | | -| Organization に参加する招待を編集およびキャンセルする | **X** | | -| Organization からメンバーを削除する | **X** | | | -| 以前のメンバーを Oraganization に復帰させる | **X** | | | -| **すべての Team** に対してユーザーを追加および削除する | **X** | | -| Organization メンバーを*チームメンテナ*に昇格させる | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)を参照) | **X** | |{% endif %} -| **すべてのリポジトリに**コラボレーターを追加する | **X** | | -| Organization 参加ログにアクセスする | **X** | | -| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照) | **X** | | | -| **すべての Team** を削除する | **X** | | -| すべてのリポジトリを含めて Organization のアカウントを削除する | **X** | | -| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照) | **X** | **X** | -| Organization の全メンバーおよび Team の表示 | **X** | **X** | -| 参照可能なチームへの @メンション | **X** | **X** | -| *チームメンテナ*に指定できる | **X** | **X** | -| リポジトリを移譲する | **X** | | -| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | -| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照) | **X** | **X** | | -| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | **X** | | -| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | | | -| **すべての Team** で Team ディスカッションを編集および削除する (「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | | | -| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | **X** | **X** | -| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | | -| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| Organization のリポジトリから {% data variables.product.prodname_pages %} サイトを公開するのを無効にする (詳細、「[Organization の {% data variables.product.prodname_pages %} サイトの公開を無効化する](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)」を参照) | **X** | | |{% endif %} -| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー) | **X** | | -| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換 | **X** | | -| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照) | **X** | |{% endif %} +| Organization のアクション | オーナー | メンバー | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------------------------------------------------------------------------:| +| Organization に参加するようユーザを招待する | **X** | | +| Organization に参加する招待を編集およびキャンセルする | **X** | | +| Organization からメンバーを削除する | **X** | | | +| 以前のメンバーを Oraganization に復帰させる | **X** | | | +| **すべての Team** に対してユーザーを追加および削除する | **X** | | +| Organization メンバーを*チームメンテナ*に昇格させる | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)を参照) | **X** | +{% endif %} +| **すべてのリポジトリに**コラボレーターを追加する | **X** | | +| Organization 参加ログにアクセスする | **X** | | +| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照) | **X** | | | +| **すべての Team** を削除する | **X** | | +| すべてのリポジトリを含めて Organization のアカウントを削除する | **X** | | +| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照) | **X** | **X** | +| Organization の全メンバーおよび Team の表示 | **X** | **X** | +| 参照可能なチームへの @メンション | **X** | **X** | +| *チームメンテナ*に指定できる | **X** | **X** | +| リポジトリを移譲する | **X** | | +| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | +| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照) | **X** | **X** | | +| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | **X** | | +| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/articles/about-team-discussions)」を参照) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/articles/managing-disruptive-comments)) | **X** | | | +| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照) | **X** | **X** | **X** | +| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | | +| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | |{% if currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | +{% endif %} +| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー) | **X** | | +| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換 | **X** | | +| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照) | **X** | +{% endif %} {% endif %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index ba9089e98e..9a96b90e09 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: Organization のリポジトリ権限レベル intro: 'Organization の各リポジトリに対するアクセスを、権限レベルを細かく設定することによりカスタマイズできます。これにより、ユーザが必要な機能やタスクにアクセスできるようになります。' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,95 +43,124 @@ Organization レベルの設定を管理することに加え、Organization の {% endwarning %} ### 各権限レベルが可能なリポジトリへのアクセス +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| -| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | -| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | -| Issue のオープン | **X** | **X** | **X** | **X** | **X** | -| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | -| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | -| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | -| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | -| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | -| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** |{% endif %} -| wiki の編集 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [悪用あるいはスパムの可能性があるコンテンツのレポート](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %} -| マイルストーンの適用 | | **X** | **X** | **X** | **X** | -| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | -| [プルリクエストのレビュー](/articles/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | -| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | -| [他者によるコメントの非表示](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [会話のロック](/articles/locking-conversations) | | | **X** | **X** | **X** | -| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | -| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [プルリクエストをドラフトに変換する](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | -| プルリクエストに[提案された変更を適用する](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| [ステータスチェック](/articles/about-status-checks)の作成 | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** |{% endif %} -| リリースの作成と編集 | | | **X** | **X** | **X** | -| ドラフトリリースの表示 | | | **X** | **X** | **X** | -| リポジトリの説明の編集 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | -| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | -| プロジェクトボードの有効化 | | | | **X** | **X** | -| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | -| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | -| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | -| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [リポジトリでのインタラクション](/github/building-a-strong-community/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** |{% endif %} -| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | -| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | -| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | -| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | -| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | -| リポジトリ設定の変更 | | | | | **X** | -| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | -| リポジトリのデフォルトブランチ編集 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 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 %} -| Webhookおよびデプロイキーの管理 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| プライベートリポジトリの[依存関係グラフの有効化](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | -| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | -| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** | -| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | -| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [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 %} -| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** |{% endif %} -| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [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** | -| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} +| +{% endif %} +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | +| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | +| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | +| Issue のオープン | **X** | **X** | **X** | **X** | **X** | +| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | +| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | +| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | +| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | +| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | +| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** +{% endif %} +| wiki の編集 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [悪用あるいはスパムの可能性があるコンテンツのレポート](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} +| マイルストーンの適用 | | **X** | **X** | **X** | **X** | +| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | +| [プルリクエストのレビュー](/articles/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | +| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | +| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | +| [他者によるコメントの非表示](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [会話のロック](/articles/locking-conversations) | | | **X** | **X** | **X** | +| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | +| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [プルリクエストをドラフトに変換する](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | +| プルリクエストに[提案された変更を適用する](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | +| [ステータスチェック](/articles/about-status-checks)の作成 | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** +{% endif %} +| リリースの作成と編集 | | | **X** | **X** | **X** | +| ドラフトリリースの表示 | | | **X** | **X** | **X** | +| リポジトリの説明の編集 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | +| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | +| プロジェクトボードの有効化 | | | | **X** | **X** | +| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | +| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | +| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | +| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [リポジトリでのインタラクション](/github/building-a-strong-community/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** +{% endif %} +| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | +| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | +| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | +| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | +| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | +| リポジトリ設定の変更 | | | | | **X** | +| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | +| リポジトリのデフォルトブランチ編集 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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 %} +| Webhookおよびデプロイキーの管理 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} +| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** +{% endif %} +| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [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** | +| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_advanced_security %} features. + +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | +| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** | +| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| プライベートリポジトリの[依存関係グラフの有効化](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | +| [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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** | +| [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 %} +{% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 38454becd7..fbb27743a7 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -27,46 +27,46 @@ The audit log lists events triggered by activities that affect your organization 特定のイベントを検索するには、クエリで `action` 修飾子を使用します。 Audit log に一覧表示されるアクションは以下のカテゴリに分類されます。 -| カテゴリ名 | 説明 | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| [`アカウント`](#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-category-actions) | Contains all activities related to your organization's billing. | -| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/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. 詳しい情報については、「[{% 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. | -| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | +| カテゴリ名 | 説明 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`アカウント`](#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-category-actions) | Contains all activities related to your organization's billing. | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/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. 詳しい情報については、「[{% 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. | +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. 詳しい情報については、「[依存関係グラフについて](/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) | Team ページに投稿されたディスカッションに関連するすべてのアクティビティが対象です。 | -| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Team ページに投稿されたディスカッションへの返答に関連するすべてのアクティビティが対象です。 | -| [`フック`](#hook-category-actions) | webhookに関連するすべてのアクティビティを含みます。 | -| [`integration_installation_request`](#integration_installation_request-category-actions) | Organization 内で使用するインテグレーションをオーナーが承認するよう求める、 Organization メンバーからのリクエストに関連するすべてのアクティビティが対象です。 | -| [`Issue`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} -| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% 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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を無効化することに関連するすべてのアクティビティが対象です。 詳細については、「[Organization について {% data variables.product.prodname_pages %} サイトの公開を制限する](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)」を参照してください。 |{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Team ページに投稿されたディスカッションに関連するすべてのアクティビティが対象です。 | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Team ページに投稿されたディスカッションへの返答に関連するすべてのアクティビティが対象です。 | +| [`フック`](#hook-category-actions) | webhookに関連するすべてのアクティビティを含みます。 | +| [`integration_installation_request`](#integration_installation_request-category-actions) | Organization 内で使用するインテグレーションをオーナーが承認するよう求める、 Organization メンバーからのリクエストに関連するすべてのアクティビティが対象です。 | +| [`Issue`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% 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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} | [`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. |{% if currentVersion == "free-pro-team@latest" %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. |{% if currentVersion == "free-pro-team@latest" %} | [`payment_method`](#payment_method-category-actions) | Organization の GitHub への支払い方法に関連するすべてのアクティビティが対象です。{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Organization のプロフィール画像に関連するすべてのアクティビティが対象です。 | -| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 | -| [`protected_branch`](#protected_branch-category-actions) | 保護されたブランチ関連するすべてのアクティビティが対象です。 | +| [`profile_picture`](#profile_picture-category-actions) | Organization のプロフィール画像に関連するすべてのアクティビティが対象です。 | +| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 | +| [`protected_branch`](#protected_branch-category-actions) | 保護されたブランチ関連するすべてのアクティビティが対象です。 | | [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} -| [`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_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 %}{% if currentVersion != "github-ae@latest" %} -| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | -| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | -| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | +| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |{% endif %}{% if currentVersion != "github-ae@latest" %} | [`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 %}{% if currentVersion == "free-pro-team@latest" %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. 詳しい情報については、「[シークレットスキャニングについて](/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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. 詳しい情報については、「[シークレットスキャニングについて](/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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [`sponsors`](#sponsors-category-actions) | スポンサーボタンに関連するすべてのアクティビティが対象です (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %} -| [`Team`](#team-category-actions) | Organization内のチームに関連するすべてのアクティビティを含みます。 | -| [`team_discussions`](#team_discussions-category-actions) | Organization の Team ディスカッションに関連するすべてのアクティビティが対象です。 | +| [`Team`](#team-category-actions) | Organization内のチームに関連するすべてのアクティビティを含みます。 | +| [`team_discussions`](#team_discussions-category-actions) | Organization の Team ディスカッションに関連するすべてのアクティビティが対象です。 | 次の用語を使用すれば、特定の一連の行動を検索できます。 例: @@ -128,7 +128,7 @@ To ensure a secure IP and maintain compliance for your organization, you can use {% data reusables.audit_log.audit-log-api-info %} {% if currentVersion == "free-pro-team@latest" %} -Note that you can't retrieve Git events using the GraphQL API. +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 %} GraphQL のレスポンスには、90 日から 120 日までのデータを含めることができます。 @@ -141,7 +141,7 @@ GraphQL のレスポンスには、90 日から 120 日までのデータを含 {% note %} -**Note**: The audit log REST API is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. +**Note:** The audit log REST API is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. {% endnote %} @@ -250,7 +250,7 @@ An overview of some of the most common actions that are recorded as events in th {% note %} -**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. +**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. @@ -308,11 +308,11 @@ For more information about the audit log REST API, see "[Organizations](/rest/re {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} #### `members_can_create_pages` category actions -詳細については、「[Organization について {% data variables.product.prodname_pages %} サイトの公開を制限する](/github/setting-up-and-managing-organizations-and-teams/disabling-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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." | アクション | 説明 | |:--------- |:-------------------------------------------------------------------------------------------------------------- | @@ -343,19 +343,20 @@ For more information about the audit log REST API, see "[Organizations](/rest/re | `oauth_app_access_approved` | オーナーが [{% data variables.product.prodname_oauth_app %} へのアクセスを許可する](/articles/approving-oauth-apps-for-your-organization/)ときにトリガーされます。 | | `oauth_app_access_denied` | オーナーが Organization への[以前に承認した {% data variables.product.prodname_oauth_app %} のアクセス権を無効にする](/articles/denying-access-to-a-previously-approved-oauth-app-for-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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | +| `register_self_hosted_runner` | Organizationのオーナーが[新しいセルフホストランナーを登録](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)したときにトリガーされます。 | | `remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret.{% endif %}{% if currentVersion == "free-pro-team@latest"%} -| `remove_billing_manager` | [オーナーが Organization から支払いマネージャーを削除する](/articles/removing-a-billing-manager-from-your-organization/)とき、または [Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、支払いマネージャーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます。 |{% endif %} +| `remove_billing_manager` | [オーナーが Organization から支払いマネージャーを削除する](/articles/removing-a-billing-manager-from-your-organization/)とき、または [Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、支払いマネージャーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます。 +{% endif %} | `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} 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 %}. Organization から [Organization のメンバーが自身を削除](/articles/removing-yourself-from-an-organization/)するときにもトリガーされます。 | | `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} 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 %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `remove_self_hosted_runner` | Organizationのオーナーが[セルフホストランナーを削除](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)したときにトリガーされます。 |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | `revoke_external_identity` | Organization のオーナーがメンバーのリンクされたアイデンティティを取り消すときにトリガーされます。 詳細は、「[組織へのメンバーの SAML アクセスの表示と管理](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 | | `revoke_sso_session` | Organization のオーナーがメンバーの SAML セッションを取り消すときにトリガーされます。 詳細は、「[組織へのメンバーの SAML アクセスの表示と管理](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `runner_group_created` | Triggered when an organization admin [creates a self-hosted runner group](/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 an organization admin removes a self-hosted runner group. | -| `runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | -| `runner_group_runners_added` | Triggered when an organization admin [adds 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_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. |{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `runner_group_created` | 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` | Organizationの管理者がセルフホストランナーグループを削除したときにトリガーされます。 | +| `runner_group_renamed` | Organizationの管理者がセルフホストランナーグループの名前を変更したときにトリガーされます。 | +| `runner_group_runners_added` | Organizationの管理者が[セルフホストランナーをグループに追加](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)したときにトリガーされます。 | +| `runner_group_runners_removed` | Organizationの管理者がセルフホストランナーをグループから削除したときにトリガーされます。 |{% endif %}{% if currentVersion == "free-pro-team@latest"%} | `unblock_user` | Organizationのオーナーが[ Organization からユーザりブロックを解除](/articles/unblocking-a-user-from-your-organization)するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `update_actions_secret` | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} | `update_new_repository_default_branch_setting` | オーナーが Organization の新しいリポジトリのデフォルトブランチの名前を変更するときにトリガーされます。 詳しい情報については、「[Organization のリポジトリのデフォルブランチ名を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照してください。{% endif %} @@ -469,8 +470,8 @@ For more information about the audit log REST API, see "[Organizations](/rest/re | `enable` | Triggered when a repository is reenabled.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret.{% endif %} | `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| `register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `remove_self_hosted_runner` | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). |{% endif %} +| `register_self_hosted_runner` | リポジトリ管理者が[新しいセルフホストランナーを登録](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)したときにトリガーされます。 | +| `remove_self_hosted_runner` | リポジトリ管理者が[セルフホストランナーを削除](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)したときにトリガーされます。 |{% endif %} | `remove_topic` | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。 | | `rename` | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。 | | `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index 6d20b0cf8b..3e2fd335eb 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -18,14 +18,14 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team ### Supported IdPs -We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. 詳しい情報については、OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) を参照してください。 -| IdP | SAML | User provisioning | Team の同期 | -| ------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory フェデレーションサービス (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | User provisioning | Team の同期 | +| ------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory フェデレーションサービス (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index 1579cd05aa..933580408e 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -33,7 +33,9 @@ The total quantity of your licenses for your enterprise on {% data variables.pro To use the {% data variables.product.prodname_enterprise %} portion of the license, the 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 %}. -Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an 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. +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. + +While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 90f0e64bd7..ae001c631c 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ GitHub will display your profile README on your profile page if all of the follo The generated README file is pre-populated with a template to give you some inspiration for your profile README. ![README file with pre-populated template](/assets/images/help/repository/personal-repository-readme-template.png) +For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](http://www.emoji-cheat-sheet.com/)." + ### Removing a profile README The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply: diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index b57ff84ab2..51a455487a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,20 +30,23 @@ You can also {% if currentVersion == "free-pro-team@latest" %}invite{% else %}ad | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %} | | | [個人リポジトリへのコラボレータの招待](/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" +{% endif %} | 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする | [保護されたブランチについて](/github/administering-a-repository/about-protected-branches) | | リポジトリを削除する | 「[リポジトリを削除する](/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)" |{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} -| パッケージの削除 | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| パッケージの削除 | "[Deleting a package](/github/managing-packages-with-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)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | Receive | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | Dismiss {% data variables.product.prodname_dependabot_alerts %} in the 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 %} +| 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 %} | リポジトリのコードオーナーを定義する | 「[コードオーナー'について](/github/creating-cloning-and-archiving-repositories/about-code-owners)」 | | Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | @@ -64,8 +67,9 @@ Collaborators can also perform the following actions. | アクション | 詳細情報 | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Managing disruptive comments](/github/building-a-strong-community/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)" | @@ -79,7 +83,8 @@ Collaborators can also perform the following actions. | Create and edit a wiki for the repository | 「[ウィキについて](/github/building-a-strong-community/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" +{% endif %} | リポジトリでコラボレーターである自身を削除する | [コラボレーターのリポジトリから自分を削除する](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository) | ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md index a375538c40..dfecfc62ce 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -1,6 +1,6 @@ --- title: GitHub が配信するメールの種類 -intro: '{% data variables.product.product_name %} から受け取るメールには、通知、アカウントの情報、マーケティングの連絡などいくつかの種類があります。' +intro: 'There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, customer research invitations, and marketing communications.' redirect_from: - /articles/types-of-emails-github-sends versions: @@ -25,6 +25,17 @@ versions: 有料の製品や機能にアップグレートしている場合、アカウントのプライマリメールアドレスで支払い領収書を受け取ります。 詳細は「[支払い請求先メールアドレスを設定する](/articles/setting-your-billing-email)」を参照してください。 +### Customer research emails + +{% data variables.product.product_name %} occasionally seeks customers to participate in research sessions to help us build a better GitHub. These are conducted remotely, open to customers worldwide, and may include: + +- Feedback surveys +- Research interviews +- Usability testing sessions +- Previewing early prototypes or concepts + +These emails are infrequent and you can choose whether or not to participate. If you're interested in additional opportunities to participate in research sessions, you may add yourself to the GitHub Customer Research Panel. For more information, see "[GitHub Customer Experience Research](https://cxr.github.com)." + ### マーケティングメール {% data variables.product.product_name %} は時々、これらの種類のマーケティングメールを配信します。 diff --git a/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md b/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md index d3debb9365..a9d64b1f53 100644 --- a/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md @@ -55,7 +55,7 @@ Actions and any elements of the Actions service may not be used in violation of - 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 - gitHubアクションが使用されるリポジトリに関連するソフトウェアプロジェクトの製造、テスト、デプロイ、公開に関連しないその他の行為。 -このような使用制限違反や、GitHubアクションの悪用を防ぐために、GitHubはGitHubアクションの使用を監視する場合があります。 GitHubアクションを不正利用した場合には、ジョブが停止されたり、GitHubアクションの使用を制限されたりすることもあります。 +このような使用制限違反や、GitHubアクションの悪用を防ぐために、GitHubはGitHubアクションの使用を監視する場合があります。 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. #### b. パッケージの使用量 GitHub Packages is billed on a usage basis. The [Packages documentation](/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). diff --git a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md index ab6a7724e0..c2195e90bc 100644 --- a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md @@ -27,7 +27,9 @@ Although we've provided the following information below for your convenience, it GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. また、ユーザは、制裁対象国の政府を含む上記の人物のために、またはその代理として GitHub.com を使用することはできません。 さらに、[17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) に記載されている禁止対象の最終用途を含む、適用される輸出管理法の下で禁止されている目的に GitHub.com を使用することはできません。 +GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. さらに、[17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) に記載されている禁止対象の最終用途を含む、適用される輸出管理法の下で禁止されている目的に GitHub.com を使用することはできません。 #### GitHub Enterprise Server @@ -41,13 +43,13 @@ GitHub Enterprise Server は商用の大衆市場製品であり、`5D992.c` の #### On which countries and territories are U.S. government sanctions applied? -クリミア、キューバ、イラン、北朝鮮、シリアです。 With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. +クリミア、キューバ、イラン、北朝鮮、シリアです。 With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. #### 制裁対象国/地域に住んでいない人や、制裁対象国/地域と職業的なつながりを持たない人がアクセスしたり異議を申し立てたりすることができるよう、GitHub は何か対策をしていますか？ アカウントが意図せずまたは誤って影響を受けることはまれですが、そのような事態に対処するための異議申し立てプロセスはあります。 -個人ユーザまたは Organization 管理者に対する決定が誤りであると考えられる場合、そのユーザは GitHub に検証情報を提供することで決定に異議を申し立てることができます。 ユーザまたは組織が米国の制裁対象区域と関連していないなど、米国の経済制裁によって制限されていないことを確認するのに十分な情報を GitHub が受け取った場合、決定は取り消されます。 economic sanctions, then the flag will be removed. [個人アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrGBcceazKIoz6pY)と [Organization アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrB2je5RBkqLEt5D)をご覧ください。 +個人ユーザまたは Organization 管理者に対する決定が誤りであると考えられる場合、そのユーザは GitHub に検証情報を提供することで決定に異議を申し立てることができます。 If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction for which we do not have a license or otherwise restricted by U.S. economic sanctions, then the flag will be removed. [個人アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrGBcceazKIoz6pY)と [Organization アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrB2je5RBkqLEt5D)をご覧ください。 #### 対象地域を旅行することによる影響はありますか？ @@ -55,13 +57,17 @@ Travel in these regions may impact your account status, but availability may be #### 何が利用できて何が利用できないのですか？ -GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. -GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in Syria and Crimea. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. +GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. + +GitHub services are not available to developers located or otherwise resident in North Korea. #### 対象のユーザをどのように定義しているのですか？ @@ -89,8 +95,13 @@ For example, a developer in Iran may sign up for a Free or Pro plan for their in Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. +If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. #### Will Iranian GitHub users be able to use paid services under the license? Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. + +#### Can you clarify availability of GitHub to Cuban developers? + +GitHub cloud services, both free and paid, are generally available to developers located in Cuba. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. diff --git a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md index 11376b0e95..2209458a10 100644 --- a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **January 6, 2021** +Effective date: **January 29, 2021** GitHubは、お客様のデータを当社が利用する方法、お客様のデータを当社が収集する方法、およびお客様のデータを共有する対象について、高い透明性を提供します。 To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -18,28 +18,26 @@ GitHubは、お客様のデータを当社が利用する方法、お客様の 当社がお客様の情報を、ベンダーやサービスプロバイダなどのサードパーティーのサブプロセッサと共有する場合、それについては当社が責任を負います。 新たなベンダーとのやり取りを行う際に、当社はお客様の信頼を維持するため努力し、全てのベンダーに対して、 ユーザの個人情報 ([プライバシーについての声明](/articles/github-privacy-statement/)の定義による) に関する取り扱いを制限する、データ保護契約を締結するよう要求しています。 -| サブプロセッサ名 | 処理の内容 | 処理の場所 | Corporate Location | -|:------------------ |:------------------------------- |:----- |:------------------ | -| Automattic | ブログサービス | 米国 | 米国 | -| AWS Amazon | データのホスティング | 米国 | 米国 | -| Braintree (PayPal) | プランのクレジットカード決済処理業者 | 米国 | 米国 | -| Clearbit | マーケティングデータのエンリッチメントサービス | 米国 | 米国 | -| Discourse | コミュニティフォーラムのソフトウェアプロバイダ | 米国 | 米国 | -| Eloqua | マーケティングキャンペーンの自動化 | 米国 | 米国 | -| Google Apps | 社内インフラストラクチャ | 米国 | 米国 | -| Google Analytics | Analytics and performance | 米国 | 米国 | -| MailChimp | 顧客チケットメールサービスプロバイダ | 米国 | 米国 | -| Mailgun | トランザクションメールサービスプロバイダ | 米国 | 米国 | -| Microsoft | Microsoft Services | 米国 | 米国 | -| Monday.com | チームコラボレーションおよびプロジェクト管理プラットフォーム | 米国 | イスラエル | -| Nexmo | SMS通知プロバイダ | 米国 | 米国 | -| Salesforce.com | 顧客関係管理 | 米国 | 米国 | -| Sendgrid | トランザクションメールサービスプロバイダ | 米国 | 米国 | -| Sentry.io | Application monitoring provider | 米国 | 米国 | -| Stripe | 決済プロバイダ | 米国 | 米国 | -| Twilio | SMS通知プロバイダ | 米国 | 米国 | -| Zendesk | カスタマーサポートのチケットシステム | 米国 | 米国 | -| Zuora | 企業課金システム | 米国 | 米国 | +| サブプロセッサ名 | 処理の内容 | 処理の場所 | Corporate Location | +|:------------------------ |:--------------------------------------------------------------- |:----- |:------------------ | +| Automattic | ブログサービス | 米国 | 米国 | +| AWS Amazon | データのホスティング | 米国 | 米国 | +| Braintree (PayPal) | プランのクレジットカード決済処理業者 | 米国 | 米国 | +| Clearbit | マーケティングデータのエンリッチメントサービス | 米国 | 米国 | +| Discourse | コミュニティフォーラムのソフトウェアプロバイダ | 米国 | 米国 | +| Eloqua | マーケティングキャンペーンの自動化 | 米国 | 米国 | +| Google Apps | 社内インフラストラクチャ | 米国 | 米国 | +| MailChimp | 顧客チケットメールサービスプロバイダ | 米国 | 米国 | +| Mailgun | トランザクションメールサービスプロバイダ | 米国 | 米国 | +| Microsoft | Microsoft Services | 米国 | 米国 | +| Monday.com | チームコラボレーションおよびプロジェクト管理プラットフォーム | 米国 | イスラエル | +| Nexmo | SMS通知プロバイダ | 米国 | 米国 | +| Salesforce.com | 顧客関係管理 | 米国 | 米国 | +| Sentry.io | Application monitoring provider | 米国 | 米国 | +| Stripe | 決済プロバイダ | 米国 | 米国 | +| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | 米国 | 米国 | +| Zendesk | カスタマーサポートのチケットシステム | 米国 | 米国 | +| Zuora | 企業課金システム | 米国 | 米国 | 当社ユーザの個人情報を取り扱う新たなサブプロセッサとやり取りを始める際、サブプロセッサと解約する際、およびサブプロセッサの利用方法を変更する際は、このページを更新します。 新たなサブプロセッサについての質問や懸念がある場合は、 {% data variables.contact.contact_privacy %}からお気軽にお問い合わせください。 @@ -47,7 +45,7 @@ GitHubは、お客様のデータを当社が利用する方法、お客様の GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. -Since the number and names of cookies may change,the table below may be updated from time to time. +Since the number and names of cookies may change, the table below may be updated from time to time. | Service Provider | Cookie Name | 説明 | Expiration* | |:---------------- |:------------------------------------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------- | diff --git a/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 0aecdc1285..9d50551b0c 100644 --- a/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ Organization アカウントの場合、当社はアカウントオーナーの ### 費用の払い戻し -当社は、法律で許可されているとおり、情報の要求への対応に伴う管理費の払い戻しを求める権利を留保します。 +Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. + +While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: + +- Initial search of up to 25 identifiers: Free +- Production of subscriber information/data for up to 5 accounts: Free +- Production of subscriber information/data for more than 5 accounts: $20 per account +- Secondary searches: $10 per search ### データ保存 diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index a2a5c53396..cebfb19d11 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -22,7 +22,7 @@ You can sponsor an account on behalf of your user account to invest in projects - Developing brand awareness as an organization that values open source - Thanking open source developers for building libraries that complement the product your organization offers -You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %}詳細は「[{% data variables.product.prodname_sponsors %} の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。 diff --git a/translations/ja-JP/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/ja-JP/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index f7cb0ba2f4..bb4cdea1a4 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/ja-JP/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ Windows は、Jekyll を公式にはサポートしていません。 For more i 一部の設定は、{% data variables.product.prodname_pages %}サイトで変更できません。 -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ Jekyllプラグインをダウンロードまたは作成すると、サイト `highlight.js`など、他のハイライターを使用したい場合は、プロジェクトの*_config.yml*ファイルを更新して、Jekyllの構文強調表示を無効にする必要があります。 -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md b/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md index 8a8af18d9d..fa8aa90837 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/ja-JP/content/github/working-with-github-pages/about-github-pages.md @@ -25,11 +25,15 @@ You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. 詳細は「[{% data variables.product.prodname_pages %} でカスタムドメインを使用する](/articles/using-a-custom-domain-with-github-pages)」を参照してください。 {% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + 作成方法については、「[{% data variables.product.prodname_pages %} サイトを作成する](/articles/creating-a-github-pages-site)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Organization owners can disable the publication of -{% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." +{% 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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} ### {% data variables.product.prodname_pages %} サイトの種類 @@ -40,6 +44,10 @@ To publish a user site, you must create a repository owned by your user account プロジェクトサイトのソースファイルは、プロジェクトと同じリポジトリに保存されます。 {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +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](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} カスタムドメインがサイトの URL に与える影響に関する詳しい情報については、「[カスタムドメインと {% data variables.product.prodname_pages %} について](/articles/about-custom-domains-and-github-pages)」を参照してください。 {% endif %} @@ -57,7 +65,7 @@ The URL where your site is available depends on whether subdomain isolation is e `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///` -詳しい情報については、 「[Subdomain Isolation を有効化する](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)」を参照するか、サイト管理者にお問い合わせください。 +For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -90,9 +98,9 @@ If you choose the `/docs` folder of any branch as your publishing source, {% dat プロジェクトサイトは、`master` ブランチまたは `master` ブランチ場の `/docs` フォルダから公開することもできます。 これらの公開元からサイトを公開するには、別の公開元を設定する必要があります。 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)」を参照してください。 - If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. _CNAME_ ファイルに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %} +If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. _CNAME_ ファイルに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %} - デフォルトブランチが`master`または`gh-pages`ではない場合でも、他のブランチからはプロジェクトサイトを公開することはできません。 +デフォルトブランチが`master`または`gh-pages`ではない場合でも、他のブランチからはプロジェクトサイトを公開することはできません。 {% endif %} @@ -118,14 +126,14 @@ If you choose the `/docs` folder of any branch as your publishing source, {% dat - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} - 公開された{% data variables.product.prodname_pages %}のサイトは1GB以上であってはなりません。 {% if currentVersion == "free-pro-team@latest" %} - - {% 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. + - {% data variables.product.prodname_pages %} サイトには、月当たり 100GB の*ソフトな*帯域幅制限があります。 + - {% data variables.product.prodname_pages %} サイトには、時間当たり 10 ビルドの*ソフトな*制限があります。 あなたのサイトがこれらの使用割当量を超えている場合、あなたのサイトにサービスを提供できないか、{% data variables.contact.contact_support %} から、あなたのサイトが当社のサーバーに与える影響を減らす方法を示唆するメールが届くことがあります。そうした方法の例としては、サードパーティのコンテンツ配信ネットワーク (CDN) をサイトの前に配置したり、リリースなどの他の {% data variables.product.prodname_dotcom %} 機能を利用したり、ニーズに合った別のホスティングサービスに移行したりすることなどが挙げられます。 #### 禁止される用途 -{% data variables.product.prodname_pages %} は、オンラインビジネス、eコマースサイト、主に商取引の円滑化またはサービスとしての商用ソフトウェアの提供 (SaaS) のどちらかを目的とする、その他のウェブサイトを運営するための無料のウェブホスティングサービスとしての使用を意図したものではなく、またそのような使用を許可するものでもありません。 +{% data variables.product.prodname_pages %} は、オンラインビジネス、eコマースサイト、主に商取引の円滑化またはサービスとしての商用ソフトウェアの提供 (SaaS) のどちらかを目的とるす、その他のウェブサイトを運営するための無料のウェブホスティングサービスとしての使用を意図したものではなく、またそのような使用を許可するものでもありません。 さらに、{% data variables.product.prodname_pages %} サイトでは、以下を禁じています: diff --git a/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index 8fea86d137..6a7af11e9f 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ja-JP/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ Jekyllがサイトのビルドを試行せず、エラーが発生した場合 各コミット後にエラーメッセージを表示するように、[Travis CI](https://travis-ci.org/) などのサードパーティサービスを設定できます。 1. 公開元のルートに、以下の内容で _Gemfile_ と呼ばれるファイルをまだ追加していない場合は、追加します。 - ``` + ```ruby source `https://rubygems.org` gem `github-pages` ``` 2. 選択したテストサービス用にサイトのリポジトリを設定します。 例えば、[Travis CI](https://travis-ci.org/) を利用するには、以下の内容の _.travis.yml_ ファイルを、公開元のルートに追加します。 - ``` + ```yaml language: ruby rvm: - 2.3 diff --git a/translations/ja-JP/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 2215fb36dc..50b9c16449 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/ja-JP/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ versions: {% data reusables.pages.navigate-publishing-source %} 1. _/assets/css/style.scss_ という新しいファイルを作成します。 2. ファイルの先頭に、以下の内容を追加します。 - ``` + ```scss --- --- diff --git a/translations/ja-JP/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ja-JP/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..bc6de13ef2 --- /dev/null +++ b/translations/ja-JP/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. You can see your site's URL in the repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. 公開されたサイトを見るには、"{% data variables.product.prodname_pages %}"の下で、サイトのURLをクリックしてください。 ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/ja-JP/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ja-JP/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 3d5f4cc765..35a58f1a92 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/ja-JP/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. ファイル名のフィールドに、`404.html` または `404.md` と入力します。 ![ファイル名フィールド](/assets/images/help/pages/404-file-name.png) 4. ファイル名を `404.md` とした場合、ファイルの先頭に以下の YAML front matter を追加します。 - ``` + ```yaml --- permalink: /404.html --- diff --git a/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 7a639e9701..9bdefe9767 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,6 +11,8 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### 必要な環境 Jekyll を使用して {% data variables.product.prodname_pages %} サイトを作成する前に、Jekyll と Git をインストールする必要があります。 詳しい情報については、Jekyll ドキュメンテーションの [Installation](https://jekyllrb.com/docs/installation/) および「[Git のセットアップ](/articles/set-up-git)」を参照してください。 @@ -95,7 +97,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md` で表示されます。 +新しいファイルを追加で作成することにより、ページを追加できます。 各ファイルは、公開元と同じディレクトリ構造で、サイト上に表示されます。 For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html` で表示されます。 また、サイトの見た目をカスタマイズするため、テーマを追加できます。 For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." diff --git a/translations/ja-JP/content/github/working-with-github-pages/index.md b/translations/ja-JP/content/github/working-with-github-pages/index.md index 942952f0df..5b5670ae2c 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/index.md +++ b/translations/ja-JP/content/github/working-with-github-pages/index.md @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/ja-JP/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 34b33f05fe..49315a22b7 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ja-JP/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -78,7 +78,7 @@ versions: このエラーは、`日本語`などアルファベット以外の文字を使用したことを意味します。 トラブルシューティングするには、*_config.yml* ファイルに次の行を追加して UTF-8 エンコーディングを指定します。 -``` +```yaml encoding: UTF-8 ``` diff --git a/translations/ja-JP/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ja-JP/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index b87b05ca02..d14fcc1542 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/ja-JP/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: GitHub Pages サイトを取り下げる -intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available to {% if currentVersion == "free-pro-team@latest" %}the public{% else %}everyone using {% data variables.product.product_location %}{% endif %}.' +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 7a4bdd83c5..710c6e7498 100644 --- a/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -13,7 +13,7 @@ versions: ヘッディングを作成するには、1 つから 6 つの `#` シンボルをヘッディングのテキストの前に追加します。 使用する `#` の数によって、ヘッディングのサイズが決まります。 -``` +```markdown # The largest heading (最大のヘッディング) ## The second largest heading (2番目に大きなヘッディング) ###### The smallest heading (最も小さいヘッディング) @@ -37,7 +37,7 @@ versions: テキストは`>`で引用できます。 -``` +```markdown アブラハムリンカーンの言葉：: > フランス語で失礼します @@ -55,7 +55,7 @@ versions: 単一のバッククォートで文章内のコードやコマンドを引用できます。 バッククォート内のテキストはフォーマットされません。 -``` +```markdown コミットされていない新しいもしくは修正されたすべてのファイルをリストするには `git status` を使ってください。 ``` @@ -102,7 +102,7 @@ git commit 1 つ以上の行の前に `-` または `*` を置くことで、順序なしリストを作成できます。 -``` +```markdown - George Washington - John Adams - Thomas Jefferson @@ -112,7 +112,7 @@ git commit リストを順序付けするには、各行の前に数字を置きます。 -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams @@ -126,7 +126,7 @@ git commit {% data variables.product.product_name %}上の Web のエディタあるいは [Atom](https://atom.io/) のようなモノスペースフォントを使うテキストエディタを使って入れ子になったリストを作成するには、リストが揃って見えるように編集します。 入れ子になったリストアイテムの前に空白を、リストマーカーの文字 (`-` または `*`) が直接上位のアイテム内のテキストの一文字目の下に来るように入力してください。 -``` +```markdown 1. 最初のリストアイテム - 最初の入れ子になったリストアイテム - 2 番目の入れ子になったリストアイテム @@ -140,7 +140,7 @@ git commit この例では、入れ子になったリストアイテムをリストアイテム `100. 最初のリストアイテム` の下に、最低 5 つの空白で入れ子になったリストアイテムをインデントさせることで追加できます。これは、`最初のリストアイテム`の前に 5 文字 (`100. `) があるからです。 -``` +```markdown 100. 最初のリストアイテム - 最初の入れ子になったリストアイテム ``` @@ -149,7 +149,7 @@ git commit 同じ方法で、複数レベルの入れ子になったリストを作成できます。 たとえば、最初の入れ子になったリストアイテムは内容である`最初の入れ子になったリストアイテム`の前に 7 つの空白 (`␣␣␣␣␣-␣`) があるため、2 番目の入れ子になったリストアイテムは 7 つの空白でインデントしなければならないでしょう。 -``` +```markdown 100. 最初のリストアイテム - 最初の入れ子になったリストアイテム - 2 番目の入れ子になったリストアイテム diff --git a/translations/ja-JP/content/github/writing-on-github/organizing-information-with-tables.md b/translations/ja-JP/content/github/writing-on-github/organizing-information-with-tables.md index f9fac18173..afa995a407 100644 --- a/translations/ja-JP/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/ja-JP/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: 表は、パイプ文字 (`|`) とハイフン (`-`) を使って作成できます。 ハイフンでヘッダを作成し、パイプ文字で各列を分けます。 正しく表示されるように、表の前には空白行を 1 行追加してください。 -``` +```markdown | ヘッダ 1 | ヘッダ 2 | | ------------- | ------------- | @@ -27,7 +27,7 @@ versions: セルの幅は変わるので、列がぴったり一致する必要はありません。 各列のヘッダ行には、ハイフンを 3 つ以上使用してください。 -``` +```markdown | Command | Description | | --- | --- | | git status | List all new or modified files | @@ -40,7 +40,7 @@ versions: 表では、リンク、インラインのコードブロック、テキストスタイルなどの[フォーマット](/articles/basic-writing-and-formatting-syntax)を使用できます。 -``` +```markdown | Command | Description | | --- | --- | | `git status` | List all *new or modified* files | @@ -51,7 +51,7 @@ versions: ヘッダー行でハイフンの左、右、両側にコロン (`:`) を使うと、列でテキストを左寄せ、右寄せ、センタリングすることができます。 -``` +```markdown | Left-aligned | Center-aligned | Right-aligned | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ versions: セルでパイプ文字 (`|`) を使用するには、パイプ文字の前に "\" を追加します。 -``` +```markdown | Name | Character | | --- | --- | | Backtick | ` | diff --git a/translations/ja-JP/content/graphql/README.md b/translations/ja-JP/content/graphql/README.md index 557f91946e..1ed548c63c 100644 --- a/translations/ja-JP/content/graphql/README.md +++ b/translations/ja-JP/content/graphql/README.md @@ -3,7 +3,7 @@ GitHub GraphQL API ドキュメントは、`/content/graphql`ディレクトリにあります。 * `/content/graphql/guides`および`/content/graphql/overview`ディレクトリには、ユーザーが編集できる記事があります。 -* `/content/graphql/reference`ディレクトリには、GitHub GraphQL APIで使用されるGraphQLの各データ型についての記事があります。 このディレクトリの内容はほとんど、`include` タグを使用してレンダリングされます。 +* `/content/graphql/reference`ディレクトリには、GitHub GraphQL APIで使用されるGraphQLの各データ型についての記事があります。 プルリクエストがマージ可能かを判断するためには、個別にそれぞれのプルリクエストの[詳細な表現](/rest#detailed-representations)（大きなペイロード）を取得し、その`mergeable`属性がtrueかfalseかをチェックしなければなりません。 `include`タグによってレンダリングされるコンテンツは`/lib/graphql/static`ディレクトリから取得され、これはGitHubで内部的にAPIソースコードから自動的に生成されます。ユーザーは編集しないでください。 詳しい情報については、[`lib/graphql/README.md`](/lib/graphql/README.md)を参照してください。 diff --git a/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md b/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md index d2e3589830..c38bbd2c86 100644 --- a/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md +++ b/translations/ja-JP/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ GraphQLは[イントロスペクション](https://graphql.github.io/learn/intro * `__schema`に対してクエリを行い、スキーマ中で定義されているすべての型と、それぞれについての詳細を取得してください。 ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* 任意の型について、`__type`にクエリを行って詳細を得てください。 + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* 任意の型について、`__type`にクエリを行って詳細を得てください。 - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * `GET`リクエストを通じてスキーマの_イントロスペクションクエリ_を実行することもできます。 diff --git a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md index 71d2c7be7e..ff8b3cafaa 100644 --- a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md @@ -193,6 +193,6 @@ GraphQLの使い始め方に関する詳しい情報については「[GraphQL Enterprise Accounts APIで利用できる新しいクエリ、ミューテーション、スキーマ定義された型の概要を以下に示します。 -Enterprise APIで利用できる新しいクエリ、ミューテーション、スキーマ定義された型に関する詳しい情報については、任意の[GraphQLリファレンスページ](/graphql)の詳細なGraphQLの定義があるサイドバーを見てください。 +Enterprise APIで利用できる新しいクエリ、ミューテーション、スキーマ定義された型に関する詳しい情報については、任意の[GraphQLリファレンスページ](/graphql)の詳細なGraphQLの定義があるサイドバーを参照してください。 GitHub上のGraphQL Explorer内からリファレンスドキュメントにアクセスできます。 詳しい情報については「[Explorerの利用](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)」を参照してください。 認証やレート制限の詳細など その他の情報については[ガイド](/graphql/guides)を参照してください。 diff --git a/translations/ja-JP/content/graphql/overview/resource-limitations.md b/translations/ja-JP/content/graphql/overview/resource-limitations.md index 8b54995aff..6ae48a4531 100644 --- a/translations/ja-JP/content/graphql/overview/resource-limitations.md +++ b/translations/ja-JP/content/graphql/overview/resource-limitations.md @@ -15,7 +15,7 @@ versions: * クライアントはすべての[コネクション](/graphql/guides/introduction-to-graphql#connection)で引数として`first`もしくは`last`を渡さなければなりません。 * `first`及び`last`の値は1から100の間でなければなりません。 -* 個々の呼び出しは合計500,000以上の[ノード](/graphql/guides/introduction-to-graphql#node)を要求してはなりません。 +* 個々の呼び出しは合計500,000以上の[ノード](/graphql/guides/introduction-to-graphql#node)をリクエストできません。 #### 呼び出し中のノードの計算 diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 53eeb43da3..98c4e6cd21 100644 --- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -14,7 +14,7 @@ versions: 1. {% data variables.product.prodname_ghe_server %}の管理シェルに接続してください。 詳しくは、"[管理シェル（SSH）へのアクセス方法](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)を参照してください。" 2. 以下のコマンドを実行してください。 - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. 次に、 diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index 86364cb1f0..2779e94199 100644 --- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - アプリケーションサーバーに依存関係をインストールしなければなりません。 - [Docker](https://docs.docker.com/install/) 1.13.0+ - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/), available via apt for [Debian](https://packages.debian.org/search?keywords=netcat) and [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} diff --git a/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index 2ac583d27e..583dd506fb 100644 --- a/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ versions: パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 {% endif %} -``` +```xml OWNER --registry=https://HOSTNAME/_regist {% data reusables.package_registry.add-npmrc-to-repo-step %} 4. インストールしているパッケージを使うには、プロジェクトの*package.json*を設定してください。 {% data variables.product.prodname_registry %}のためにパッケージの依存関係を*package.json*ファイルに追加するには、`@my-org/server`というように完全なスコープ付きのパッケージ名を指定してください。 *npmjs.com*からのパッケージについては、`@babel/core`あるいは`@lodash`というような完全な名前を指定してください。 たとえば、以下の*package.json*は`@octo-org/octo-app`パッケージを依存関係として使っています。 - ``` + ```json { "name": "@my-org/server", "version": "1.0.0", diff --git a/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md index dc4df376b5..f61f3657e4 100644 --- a/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md +++ b/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -107,7 +107,7 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem 複数のgemを同じリポジトリに公開したい場合は、{% data variables.product.prodname_dotcom %}リポジトリの`gem.metadata`にある`github_repo`フィールドに、URL を記述できます。 If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if enterpriseServerVersions contains currentVersion %} Replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} -``` +```ruby gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` @@ -118,7 +118,7 @@ gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@ {% data reusables.package_registry.authenticate-step %} 2. Bundlerについては、{% data variables.product.prodname_dotcom %}ユーザもしくはOrganizationをソースとして*Gemfile*に追加して、この新しいソースからgemsをフェッチするようにしてください。 For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -130,7 +130,7 @@ gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@ 3. 1.7.0以前のバージョンのBundlerの場合、新しいグローバルな`source`を追加する必要があります。 Bundlerの利用に関する詳しい情報については[bundler.ioのドキュメンテーション](http://bundler.io/v1.5/gemfile.html)を参照してください。 - ``` + ```ruby source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md index 89e277363a..d0970b1595 100644 --- a/translations/ja-JP/content/packages/index.md +++ b/translations/ja-JP/content/packages/index.md @@ -12,13 +12,18 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: + - + title: ghcr.io maintenance mode on 2021-01-09 + date: '2021-01-08' + href: https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/ - title: ghcr.io container names redirect to the container page date: '2020-12-14' @@ -27,10 +32,6 @@ changelog: title: Filter for tagged and untagged containers date: '2020-12-14' href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: Packages container support is an opt-in beta - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md b/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md index fea973038b..ab29bca213 100644 --- a/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md +++ b/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md @@ -54,7 +54,7 @@ GraphQL APIの`deletePackageVersion`ミューテーションを使ってくだ 以下は、個人アクセストークンを使って`MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`というパッケージバージョンIDを持つパッケージのバージョンを削除するcURLコマンドの例です。 {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md index 15ccc422e6..c8ed015e2b 100644 --- a/translations/ja-JP/content/packages/quickstart.md +++ b/translations/ja-JP/content/packages/quickstart.md @@ -80,7 +80,7 @@ You only need an existing {% data variables.product.prodname_dotcom %} repositor NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} ``` {% endraw %} -7. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. 次に、[**Propose new file**] をクリックしてプルリクエストを作成します。 +7. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. 次に、[**Propose new file**] をクリックしてPull Requestを作成します。 8. **Merge** the pull request. 9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md index 8b83e771d3..8406007a6b 100644 --- a/translations/ja-JP/content/rest/overview/libraries.md +++ b/translations/ja-JP/content/rest/overview/libraries.md @@ -79,6 +79,10 @@ Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https: ライブラリ名 | リポジトリ |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +### Rust + +Library name | Repository |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) + ### Scala ライブラリ名 | リポジトリ |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) diff --git a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md index bfeb14ba67..6eb4a5eb9a 100644 --- a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md @@ -107,7 +107,7 @@ _検索_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### "actions"に対する権限 - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _ブランチ_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _コラボレータ_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _ブランチ_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _コミットのコメント_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -836,6 +842,9 @@ _Team_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index ecd4409c02..942ae8ded6 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -35,7 +35,7 @@ - term: 略歴 description: >- - プロフィール（ https://help.github.com/ja/github/setting-up-and-managing-your-github-profile/personalizing-your-profile ）に存在する、ユーザが生成した記述。 + The user-generated description found on a profile: [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile) - term: 支払いサイクル description: 特定の支払いプランの時間間隔。 @@ -156,7 +156,7 @@ - term: コントリビューション description: >- - GitHub で次のことを行う特定のアクティビティ。- ユーザのコントリビューショングラフに正方形を追加：「[コントリビューションとしてカウントされるもの](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)」- ユーザのプロフィール上でタイムラインにアクティビティを追加：「[コントリビューションアクティビティ](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)」 + Specific activities on GitHub that will: - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - term: コントリビューター description: >- @@ -229,7 +229,7 @@ 新しい機能の実験や本番環境にない Issue の修正に使用されるブランチ。トピックブランチともいいます。 - term: コードブロック - description: 'コードのインデントされているブロック。GitHub Flavored Markdown でコードブロックの前後に 3 つのバッククォート（\`\`\`）を使用することで作成できます。[例](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)を参照。' + description: 'An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' - term: フェッチ description: >- diff --git a/translations/ja-JP/data/learning-tracks/README.md b/translations/ja-JP/data/learning-tracks/README.md new file mode 100644 index 0000000000..ec0f70309e --- /dev/null +++ b/translations/ja-JP/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Learning Tracks (aka Learning Paths) + +Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. \ No newline at end of file diff --git a/translations/ja-JP/data/learning-tracks/actions.yml b/translations/ja-JP/data/learning-tracks/actions.yml index 6aed744879..15aaa5c292 100644 --- a/translations/ja-JP/data/learning-tracks/actions.yml +++ b/translations/ja-JP/data/learning-tracks/actions.yml @@ -31,6 +31,13 @@ continuous_deployment: - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Deploy to the cloud' + description: 'Learn how to use {% data variables.product.prodname_actions %} to build an application and deploy it to various cloud-based platforms.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine hosting_your_own_runners: title: 'Host your own runners' description: 'セルフホストランナーを作成し、非常にカスタマイズ性の高い環境でワークフローを実行できます。' diff --git a/translations/ja-JP/data/release-notes/2-20/0.yml b/translations/ja-JP/data/release-notes/2-20/0.yml index 5623123354..4c6437110f 100644 --- a/translations/ja-JP/data/release-notes/2-20/0.yml +++ b/translations/ja-JP/data/release-notes/2-20/0.yml @@ -2,43 +2,43 @@ date: '2020-02-11' sections: features: - - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' - - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' - - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + - 'リポジトリのブランチでは、リポジトリ管理者は[ブランチ保護ルール]を使って`Require linear history（線形履歴を必須とする）`を有効化することによって、マージコミットを含むプッシュを拒否できます(https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions)。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'リポジトリ管理者は、プッシュアクセス権を持つすべてのユーザに、[ブランチ保護ルール]を使って`Allow force pushes（フォースプッシュの許可）`を有効化することによって、保護されたブランチにフォースプッシュを行えるよう許可できます(https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions)。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'リポジトリ管理者は、プッシュアクセス権を持つすべてのユーザに、[ブランチ保護ルール]を使って`Allow deletions（削除の許可）`を有効化することによって、保護されたブランチの削除を行えるよう許可できます(https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions)。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - '管理者は、[Git LFS]内にないリポジトリに`maxobjectsize`の制限[プッシュコミットのサイズ制限](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) を設定できます(https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server)。{% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organizationのオーナーは、新しいリポジトリを作成する際にデフォルトのラベルのセットを作成できます。{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' security_fixes: - - Packages have been updated to the latest security versions. + - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' - - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" - - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' - - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" - - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' - - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' - - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' - - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' - - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' - - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' - - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' - - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + - 'Organizationのメンバーが、そのOrganizationのパブリックリポジトリを表示させようとすると、SSOのプロンプトがページの表示を壊すことがありました。{% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "ユーザのプロフィールを表示した場合、そのユーザのTeamへのリンクが壊れていることがありました。{% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - '`maintain`ロールを持つ有ザーは、リポジトリのトピックスを編集できませんでした。 {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "Organizationの管理者ではないユーザがサインアップページにアクセスしようとすると500エラーが返されることがありました。{% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - '編集履歴のポップアップが、Gistのコメントに表示されないことがありました。{% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'すでに登録済みのメールで新しいアカウントが登録できました。{% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'ストレージサービスがファイルディスクプリプタの上限に達し、カーネルのハングや他のサービスでのエラーがログに残しました。{% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - '自動リンクの参照がURLの一部になっていると、そのハイパーリンクが削除されることがありました。{% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'Pull Requestにコメントを追加する際に、サイドバーの`Linked Issues`セクションが消えてしまうことがありました。{% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'ユーザに対する既存のOrganizationへの招待を編集している際に、`Teams`の表に重複したヘッダが表示されることがありました。{% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'キューが大きくなりすぎると、`resqued`サービスがイベントのロギングを停止してしまうことがありました。 {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'クラスタ及び高可用設定に対する`ghe-config-apply` コマンドの実行時に自己署名証明書が自動的に生成されません。{% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' changes: - - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' - - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' - - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' - - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' - - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' - - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' - - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + - '誰もアップロードしていない場合、トピックに対するロゴが表示されません。{% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'モバイルブラウザでIssueを表示すると、Issueのメタデータがページ上部にリストされてしまいます。{% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consulのトップレベルドメインが".consul"から".ghe.local"に変更されました。{% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'hookshotがElasticsearchに依存しなくなり、データベースストアとしてはMySQLだけを使うようになりました。{% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'プロジェクトノートカードに、Issue、プロジェクト、ディスカッションの視覚的な区別の改善が実装されました。{% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'Pull Requestのレビューにおいて、複数行コメントが切り詰められた場合に注意が表示されるようになりました。{% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'ユーザは、個人設定ページの`Security Log`タブで監査ログを表示できます。 {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - データベース中の重複したwebhookのエントリによって、以前のバージョンからのアップグレードが失敗することがあります。(2020-02-26に更新) + - 'バックグラウンドワーカーの設定がカスタマイズされていると、アップグレード及び設定の更新が失敗します。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。（2020-04-07更新）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/1.yml b/translations/ja-JP/data/release-notes/2-20/1.yml index e303f5525e..c5bb657cb8 100644 --- a/translations/ja-JP/data/release-notes/2-20/1.yml +++ b/translations/ja-JP/data/release-notes/2-20/1.yml @@ -2,20 +2,20 @@ date: '2020-02-27' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' bugs: - - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' - - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' - - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + - 'バックアップからのリストアが`Invalid RDB version number`エラーで失敗します。{% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'HAレプリカのアップグレードが、MySQLの起動を待って無期限に停止します。{% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - '"position"あるいは"original_position"に予期しない値を持つPRレビューコメントによって、インポートが失敗しました。{% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'データベース内の重複するwebhookエントリによって、以前のバージョンからのアップグレードが失敗することがありました。{% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'バックグラウンドワーカーの設定がカスタマイズされていると、アップグレード及び設定の更新が失敗します。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。（2020-04-07更新）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/10.yml b/translations/ja-JP/data/release-notes/2-20/10.yml index 58a38245c0..683fdce26d 100644 --- a/translations/ja-JP/data/release-notes/2-20/10.yml +++ b/translations/ja-JP/data/release-notes/2-20/10.yml @@ -2,20 +2,20 @@ date: '2020-06-23' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' bugs: - - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" - - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + - '転送のメカニズムとしてUDPが使用されている場合に、過度に大きなログイベントによってログのフォワーディングが不安定になることがありました。{% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "SSO経由のユーザの自動サスペンション解除が、すでにユーザアカウントに関連づけられているキーがSSHキーの属性にある場合に完了しませんでした。{% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'インターナルリポジトリへのプルアクセス権を持つビジネスメンバーについて、REST APIからのリポジトリ権限のハッシュがアクセス権を持たないと示していました。' + - 'Markdownで書かれたGitHub Appの説明のプレビューが、適切にレンダリングされていませんでした。{% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - '監査ログにブランチ保護の変更イベントが含まれていませんでした。{% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "空のTeamのメンバーにコードレビューを割り当てようとすると、'500 Internal Server Error'が返されます。{% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'ロードバランシングアルゴリズムを使ってコードレビューを割り当てると、同じTeamのメンバーに繰り返し割り当てられることがありました。{% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/11.yml b/translations/ja-JP/data/release-notes/2-20/11.yml index 0bdd30cf96..265d86ba6d 100644 --- a/translations/ja-JP/data/release-notes/2-20/11.yml +++ b/translations/ja-JP/data/release-notes/2-20/11.yml @@ -2,18 +2,18 @@ date: '2020-07-09' sections: security_fixes: - - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + - '**中:** nginxを1.16.1にアップデートし、CVE-2019-20372に対応しました。（2020-07-22更新）{% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' bugs: - - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' - - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' - - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しませんでした。{% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - '特定のログファイルが7日ごとにローテートされませんでした。{% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'webhookのソースポートの頻繁な再利用によって、接続が拒否されました。{% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - '正しくないバックグラウンドジョブが、パッシブレプリカとして設定されたインスタンス上で動作しようとすることがありました。{% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'SAMLが有効になっているOrganizationで、インターナルリポジトリが検索結果に正しく含まれていませんでした。{% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/12.yml b/translations/ja-JP/data/release-notes/2-20/12.yml index 5b286392f5..212dee2d04 100644 --- a/translations/ja-JP/data/release-notes/2-20/12.yml +++ b/translations/ja-JP/data/release-notes/2-20/12.yml @@ -2,16 +2,16 @@ date: '2020-07-21' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' bugs: - - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + - '大きな画面において、管理コンソースのモニターグラフが適切に表示されないことがあります。{% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'SameSiteクッキーポリシーが適用されている場合に、GitHub Appマニフェストが作成したフローが利用できない状況がありました。{% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' changes: - - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + - 'HAProxyのスケーリングが改善されました。{% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/13.yml b/translations/ja-JP/data/release-notes/2-20/13.yml index 7388ff5103..30b9b58a57 100644 --- a/translations/ja-JP/data/release-notes/2-20/13.yml +++ b/translations/ja-JP/data/release-notes/2-20/13.yml @@ -2,21 +2,21 @@ date: '2020-08-11' sections: security_fixes: - - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + - '**重大:** 攻撃者がGitHub Pagesのサイトの構築の一部としてコマンドを実行できる、リモートコード実行の脆弱性がGitHub Pagesで特定されました。この問題は、Pagesのビルドプロセスで使われている古くて脆弱性のある依存関係によるものです。この脆弱性を突くには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成して構築する権限を持っていなければなりません。この脆弱性は、GitHub Enterprise Serverのすべてのバージョンに影響します。この脆弱性を緩和するために、CVE-2020-14001への対応でkramdownがアップデートされました。{% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**高:** GitHub Enterprise Server上で実行されるGitのサブコマンドに、攻撃者が悪意ある引数をインジェクトすることができました。これによって、攻撃者は部分的にユーザが制御する内容で任意のファイルを上書きでき、GitHub Enterprise Serverインスタンス上で任意のコマンドを実行できる可能性がありました。この脆弱性を突くためには、攻撃者はGitHub Enterprise Serverインスタンス内のリポジトリへのアクセス権限を持っていなければなりません。しかし、他の保護があるので、この脆弱性を積極的に突く方法は特定できませんでした。この脆弱性はGitHub Security Bug Bountyプログラムを通じて報告されました。{% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' bugs: - - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + - 'Consulの設定エラーによって、スタンドアローンインスタンス上で処理されないバックグランドジョブがありました。{% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'サービスのメモリ割り当ての計算が、サービスに不正確もしくは無制限の割り当てを行い、システムのパフォーマンスを低下させることがありました。{% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'oVirt KVMシステムの可視化プラットフォームが適切に検出されず、アップグレードの際に問題を生じさせていました。{% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "Gitコマンドラインからのパスワードでの不正な認証のエラーメッセージが、適切なトークンもしくはSSHキーを追加するためのURLリンクを展開しませんでした。{% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connectが、非推奨のGitHub.com APIエンドポイントを使用していました。{% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - '新しいインスタンスに移行したリポジトリ上で*最近の更新*でIssueをソートできませんでした。{% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - '404ページのフッタに、GitHub.comの連絡先とステータスリンクが含まれていました。{% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/14.yml b/translations/ja-JP/data/release-notes/2-20/14.yml index d33fe2b58d..d38f573ae6 100644 --- a/translations/ja-JP/data/release-notes/2-20/14.yml +++ b/translations/ja-JP/data/release-notes/2-20/14.yml @@ -2,12 +2,12 @@ date: '2020-08-12' sections: bugs: - - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + - 'システム設定のテンプレートを生成する間にCPU使用率を高くしてしまうことがある問題を解決しました。{% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'メモリ割り当てへの最近の変更により、システムパフォーマンスが低下することがありました。{% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/16.yml b/translations/ja-JP/data/release-notes/2-20/16.yml index 4ca63bc213..1971ee1d8a 100644 --- a/translations/ja-JP/data/release-notes/2-20/16.yml +++ b/translations/ja-JP/data/release-notes/2-20/16.yml @@ -2,12 +2,12 @@ date: '2020-09-08' sections: bugs: - - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + - 'サービスのへするチェックでセッションが増加し、ファイルシステムのinodeが枯渇しました。{% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "ホットパッチを使用したアップグレードが`'libdbi1' was not found`というエラーで失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/17.yml b/translations/ja-JP/data/release-notes/2-20/17.yml index 5f3bf87a25..b9cda13903 100644 --- a/translations/ja-JP/data/release-notes/2-20/17.yml +++ b/translations/ja-JP/data/release-notes/2-20/17.yml @@ -2,12 +2,12 @@ date: '2020-09-23' sections: security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + - '**中**: [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715)に対処するためにImageMagickがアップデートされました。{% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/18.yml b/translations/ja-JP/data/release-notes/2-20/18.yml index 3aab7ba337..f39429a0bc 100644 --- a/translations/ja-JP/data/release-notes/2-20/18.yml +++ b/translations/ja-JP/data/release-notes/2-20/18.yml @@ -2,25 +2,25 @@ date: '2020-10-09' sections: security_fixes: - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - 'LDAPディレクトリのユーザ名を標準化すると既存のGHESアカウントのログインになってしまうユーザが、その既存のアカウントとして認証されることがありました。{% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + - '管理コンソールのNameID Fortmatドロップダウンが、"persistent"に設定された後に"unspecified"にリセットされます。{% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - '[管理コンソール](/admin/configuration/accessing-the-management-console) での設定の保存によって、[TLS/SSLの証明書及びキー](/admin/configuration/configuring-tls)ファイルに改行を追加してしまい、不必要に再ロードされるサービスが生じました。{% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - '依存関係グラフのシステムログがローテートされず、無制限にストレージを消費できてしまいました。{% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'GitHubセキュリティアドバイザリへのリンクが、GitHub.comではなくGitHub Enterprise Serverインスタンスのホスト名を持つURLを使い、ユーザを存在しないURLにアクセスさせました。{% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - '`ghe-migrator`でリポジトリをインポートする際に、不整合なデータが存在していると、予期しない例外が生じることがありました。{% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - '`ghe-migrator`を使ってPRレビューリクエストをインポートする際に、削除されたユーザに関連付けられたレコードによって関係性を持たないデータベースレコードが残ります。{% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - '`ghe-migrator`でユーザをインポートする際に、システムによって生成されたメールアドレスが100文字以上の長さになっていると、"Emails is invalid"エラーが生じます。{% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'webhookのアクティビティのログが大量のディスク領域を使い、ルートディスクが一杯になってしまいます。{% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' changes: - - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + - 'AWS EC2のインスタンスタイプ`m5.16xlarge`のサポートが追加されました。{% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - '`ghe-migrator`アーカイブのSSHフィンガープリントはいつでも計算できるので、必須ではなくなりました。{% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub Appマニフェストに`request_oauth_on_install`フィールドが含まれるようになりました。{% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/19.yml b/translations/ja-JP/data/release-notes/2-20/19.yml index b686131852..cf8c29d9e9 100644 --- a/translations/ja-JP/data/release-notes/2-20/19.yml +++ b/translations/ja-JP/data/release-notes/2-20/19.yml @@ -2,13 +2,13 @@ date: '2020-10-20' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' bugs: - - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + - 'Enterpriseアカウントの"Confirm two-factor requirement policy"メッセージが正しくありませんでした。{% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/2.yml b/translations/ja-JP/data/release-notes/2-20/2.yml index 78e2faa7e1..3dcd228b92 100644 --- a/translations/ja-JP/data/release-notes/2-20/2.yml +++ b/translations/ja-JP/data/release-notes/2-20/2.yml @@ -2,27 +2,27 @@ date: '2020-03-10' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' bugs: - - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' - - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' - - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' - - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' - - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' - - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' - - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' - - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' - - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + - '主に監査ログで、転送されたログエントリが切り捨てられる場合がありました。{% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - '一部の有効なライセンスに対して`ghe-license-check`コマンドラインユーティリティが"Invalid license file"エラーを返し、設定変更が失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic例外ログがsyslogによって転送されませんでした。{% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - '[`org_blockイベント`](https://developer.github.com/v3/activity/events/types/#orgblockevent)は利用できませんが、GitHub Enterprise Server上のGitHub Appsに現れます。{% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQLのクエリレスポンスが`ProtectedBranch`オブジェクトのマッチしないノード識別子を返すことがあります。{% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'GitHub Connectが使用するGitHub Appの認証情報が、期限切れ直後の更新に失敗しました。{% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Pull Requestコメントに対する返信としてコメントを残すと、保留されたPull Requestレビューを作成してしまうことがありました。{% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'ghe-migratorを使ってGitHub.comからエクスポートすると、画像以外の添付ファイルのエクスポートが何も出力せずに失敗します。{% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'UTF-8キャラクターがあると、pre-receiveフックがWeb UIで500エラーを返しました。{% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' changes: - - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + - '` ghe-license-usage `コマンドラインユーティリティには、新たな`--unencrypted`オプションによるエクスポートされたライセンス利用ファイルの可視化の提供が含まれます。{% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'バックグラウンドワーカーの設定がカスタマイズされていると、アップグレード及び設定の更新が失敗します。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。（2020-04-07更新）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/20.yml b/translations/ja-JP/data/release-notes/2-20/20.yml index 0cf4def9e0..e8a0f3e94c 100644 --- a/translations/ja-JP/data/release-notes/2-20/20.yml +++ b/translations/ja-JP/data/release-notes/2-20/20.yml @@ -2,15 +2,15 @@ date: '2020-11-03' sections: security_fixes: - - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' + - '**中:** SVNブリッジへの特別に細工されたリクエストによって引き起こされる高いCPU使用率によって、サービス拒否（DoS）が引き起こされる可能性がありました。{% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**低:** 不正確なトークンの検証によって、認証中のトークンのマッチのためのエントリピーが減少しました。分析からは、実際には大きなセキュリティ上のリスクはないことが示されています。{% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' bugs: - - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + - 'サスペンドされたユーザが推奨されるユーザのリストに含まれ、サスペンドされていないユーザを隠してしまう可能性がありました。{% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/21.yml b/translations/ja-JP/data/release-notes/2-20/21.yml index 4b970a92ee..43be5aeb9f 100644 --- a/translations/ja-JP/data/release-notes/2-20/21.yml +++ b/translations/ja-JP/data/release-notes/2-20/21.yml @@ -2,14 +2,14 @@ date: '2020-11-17' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'baneldログに秒とマイクロ秒の間のセパレータが欠けていました。 {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Enterpriseアカウントの"Repository visibility change"ポリシーが"Enabled"に設定されている場合、OrganizationオーナーがOrganization内のリポジトリの可視性を変更できませんでした。 {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/22.yml b/translations/ja-JP/data/release-notes/2-20/22.yml index 099ce93b0d..f53e1bf2dc 100644 --- a/translations/ja-JP/data/release-notes/2-20/22.yml +++ b/translations/ja-JP/data/release-notes/2-20/22.yml @@ -2,18 +2,18 @@ date: '2020-12-03' sections: bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'ブートストラップ時のレース条件により、認可サービスが不健全として検出され、再起動されることにつながりました。{% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - '下位の動作により、ホットパッチアップグレードのプロセス中に、サービスが利用できなくなりました{% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'ログ転送SSL証明書の一部が正しく適用されませんでした。{% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'サスペンドされたユーザがTeamあるいはOrganizationから削除されると、そのユーザにメール通知が送信されました。{% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'SSH証明書の適用方法が、OrganizationとBusiness間で整合していませんでした。{% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - '不正確なパスワードの利用のためにアカウントにレート制限が適用された場合に、最大で24時間ロックアウトされることがありました。{% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - '多くの参照を持つリポジトリ上のPull Requestの同期が、ワーカーキューを遅れさせることがありました。{% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - '特定のページへのアクセスを試みた後にサインインすると、意図したアクセス先ではなくホームページにユーザが送られてしまいました。{% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/23.yml b/translations/ja-JP/data/release-notes/2-20/23.yml index bde9f73982..1870a526a8 100644 --- a/translations/ja-JP/data/release-notes/2-20/23.yml +++ b/translations/ja-JP/data/release-notes/2-20/23.yml @@ -2,12 +2,12 @@ date: '2020-12-17' sections: security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + - '**低:** SVNブリッジへの特別に細工されたリクエストによって引き起こされる高いCPU使用率によって、サービス拒否（DoS）が引き起こされる可能性がありました。{% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/3.yml b/translations/ja-JP/data/release-notes/2-20/3.yml index 23c25312e5..9128bb4e39 100644 --- a/translations/ja-JP/data/release-notes/2-20/3.yml +++ b/translations/ja-JP/data/release-notes/2-20/3.yml @@ -2,14 +2,14 @@ date: '2020-03-12' sections: bugs: - - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + - 'バックグラウンドワーカーの設定がカスタマイズされていると、アップグレード及び設定の更新が失敗します。{% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。（2020-04-07更新）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/4.yml b/translations/ja-JP/data/release-notes/2-20/4.yml index 0f06a203cd..e362503c10 100644 --- a/translations/ja-JP/data/release-notes/2-20/4.yml +++ b/translations/ja-JP/data/release-notes/2-20/4.yml @@ -2,17 +2,17 @@ date: '2020-03-25' sections: bugs: - - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' - - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' - - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + - 'SAML認証リクエストとメタデータが厳密にエンコードされておらず、アイデンティティプロバイダによってはサービスプロバイダが開始した認証リクエストが正しく処理されません。{% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator`のエクスポートにマイルストーンのユーザが含まれず、そのためインポート操作が失敗することがあります。{% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '完全に複製されていないリポジトリを表示しようとする際に、`ghe-repl-status`が失敗することがありました。{% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。（2020-04-07更新）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/5.yml b/translations/ja-JP/data/release-notes/2-20/5.yml index 44115fdc71..22d84ea590 100644 --- a/translations/ja-JP/data/release-notes/2-20/5.yml +++ b/translations/ja-JP/data/release-notes/2-20/5.yml @@ -2,19 +2,19 @@ date: '2020-04-07' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' bugs: - - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' - - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' - - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + - 'グローバルEnterpriseアカウントが100MB以外のGitオブジェクトサイズオプションを持つリポジトリで、最大のGitオブジェクトサイズの100MBが選択できませんでした。{% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - '`updated_at`フィールドで順序付けされている場合、Issue及びPull Request APIからの結果が一貫性を持たない動作になることがありました。{% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'SecurityVulnerabilityの`package`フィールドがGraphQL API経由でクエリできませんでした。{% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'リポジトリを*public*から*internal*に変更すると、無関係な支払いのメッセージが表示されました。{% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/6.yml b/translations/ja-JP/data/release-notes/2-20/6.yml index 568f19954f..392aa32f5e 100644 --- a/translations/ja-JP/data/release-notes/2-20/6.yml +++ b/translations/ja-JP/data/release-notes/2-20/6.yml @@ -2,26 +2,26 @@ date: '2020-04-23' sections: security_fixes: - - '**HIGH**: OpenSSL has been updated to address [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' - - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' - - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + - '**高**: [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967)に対応するためにOpenSSLがアップデートされました。{% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' + - '**高**: [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q)及び[CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7)に対処するため、Gitがアップデートされました。新しい制約によって、悪意あるリポジトリがサーバーインスタンスにプッシュされることが回避され、パッチされていないクライアントが保護されます。{% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**低**: [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131)に対処するためにImageMagickがアップデートされました。{% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' bugs: - - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" - - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + - 'Gitユーザには、Subversionを利用している既存のリポジトリをv4フォーマットからv3 LRSに変換するために必要なプロセスを起動する権限がありませんでした。{% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'MySQLの設定のミスマッチによって、大規模な環境ではバックアップが失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - '以前のバージョンからのアップグレードの際に、バックグラウンドジョブワーカーがspawnせず、Pull Requestのマージなどの重要な機能が動作しないことがあります。{% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "GitHub Enterprise Serverのライセンスが非ASCIIキャラクタを含んでいる場合、管理コンソールのAPI `/setup/api/settings`エンドポイントへの`GET`リクエストに、Internal Server Errorが返されました。{% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'ルートアカウントがロックされている場合でも、リカバリコンソールがルートパスワードを求めました。{% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'CODEOWNERSファイルが先頭にUTF-8のバイトオーダーマークを持っていると、すべてのcodeownerルールが無視されます。{% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' changes: - - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}" + - 'orchestrator-client cronジョブが失敗した場合、複数のメールがルートアカウントに送信されます。 {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "外部のアイデンティティプロバイダがユーザのサイト管理者のステータスを制御している場合、コマンドラインユーティリティでユーザを降格できませんでした。 {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}" known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/7.yml b/translations/ja-JP/data/release-notes/2-20/7.yml index b377d90b66..682c58b0bb 100644 --- a/translations/ja-JP/data/release-notes/2-20/7.yml +++ b/translations/ja-JP/data/release-notes/2-20/7.yml @@ -2,20 +2,20 @@ date: '2020-05-05' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' bugs: - - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' - - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' - - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' - - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' - - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + - '`ghe-repl-start`及び`ghe-repl-status`が構文エラーを表示しました。{% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'リポジトリで"automatically delete head branches（自動的にheadブランチを削除）"設定が有効化されており、Pull RequestがGitHub Appのインストールによってマージされた場合に、headブランチが自動的に削除されませんでした。{% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'Organizationのメンバーが復帰したとき、webhookのペイロードが復帰を行った実際のユーザではなく、`幽霊`ユーザを送信者として報告しました。{% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'リポジトリで"automatically delete head branches（自動的にheadブランチを削除）"設定が有効化されており、headリポジトリがベースリポジトリと異なる場合に、headブランチが自動的に削除されませんでした。{% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871{% endcomment %}' + - '一時ファイルのガベージコレクションがライセンス検証エラーにつながることがありました。{% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'リポジトリが初めて作成された場合を含むいくつかの状況で、pre-receiveフックがGITHUB_REPO_PUBLIC環境変数に展開された値なしで実行されます。{% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/8.yml b/translations/ja-JP/data/release-notes/2-20/8.yml index 510bf779fb..7f6ac125a3 100644 --- a/translations/ja-JP/data/release-notes/2-20/8.yml +++ b/translations/ja-JP/data/release-notes/2-20/8.yml @@ -2,19 +2,19 @@ date: '2020-05-19' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' bugs: - - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' - - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' - - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' - - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + - 'ライセンスファイルが更新された後、サービスが適切に再ロードされず、機能が失われました。{% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - '依存関係グラフの情報を更新する内部APIリクエストが、レスポンスのボディが大きすぎる場合に失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'GraphQLのリポジトリ接続への`affiliations`引数が、対応されないことがありました。{% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'SSO経由のユーザの自動サスペンション解除が、SAMLのemail属性の大文字小文字がGitHubのユーザのメールと異なっている場合に完了しませんでした。{% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Organizationへのユーザのメンバーシップの復元が、webhookと監査ログのペイロード内にアクターを組み込みませんでした。{% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/9.yml b/translations/ja-JP/data/release-notes/2-20/9.yml index 326818d711..738565f217 100644 --- a/translations/ja-JP/data/release-notes/2-20/9.yml +++ b/translations/ja-JP/data/release-notes/2-20/9.yml @@ -2,16 +2,16 @@ date: '2020-06-02' sections: security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + - '**高:** Organizationのメンバーが権限を昇格させ、Organization内の認可されていないリポジトリへのアクセスを取得できてしまう不適切なアクセス制御の脆弱性が、GitHub Enterprise Server APIで特定されました。この脆弱性は、2.21以前のすべてのGitHub Enterprise Serverに影響します。この問題に対応して、[CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516)を発行しました。この脆弱性は、[GitHubバグバウンティプログラム](https://bounty.github.com)で報告されました。{% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' bugs: - - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + - 'インターネットに面しているGitHub Enterprise Serverインスタンスが、検索エンジンにインデックスされることがありました。{% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '複数のRedisノードでのクラスタ設定にデプロイされた際に、依存関係グラフが依存関係を検出しません。（2020-06-30更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/0.yml b/translations/ja-JP/data/release-notes/2-21/0.yml index cfd8a069f8..469347560b 100644 --- a/translations/ja-JP/data/release-notes/2-21/0.yml +++ b/translations/ja-JP/data/release-notes/2-21/0.yml @@ -2,50 +2,50 @@ date: '2020-06-09' sections: features: - - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' - - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' - - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' - - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' - - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' - - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'ユーザは、web通知からアクセスする際に、Issue、Pull Request、その他の課題に関する[通知を管理](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications)できます。{% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'ユーザは、[Pull Requestを"ドラフト"に変換して戻せます](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/)。{% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[複数行の提案](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/)によって、ユーザはPull Requestのレビューの際に複数行のコードに対して特定の変更を提案できます。{% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'リポジトリへの書き込みアクセス権を持つユーザが["複製"としてIssueあるいはPull Requestのコメントを隠す]ことができる(https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment)。{% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - '[テンプレートからリポジトリを作成する](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template)際に、ユーザがデフォルトブランチだけではなく、すべてのブランチを含めるよう選択できる。{% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - 'ユーザがどの開発作業がIssueに関係しているかをプロジェクトボードから直接見ることができるよう、[IssueのプロジェクトカードがリンクされたPull Requestのセクションを含む(https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) ようになりました。{% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'Reactions APIに["リアクションの削除"エンドポイント]の新しいセット(https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/)があります。既存の"リアクションの削除”エンドポイントは、2021年の早い時期に非推奨になります。{% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - '[Teams APIエンドポイント]の新しいセット(https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/)　があり、これによってGitHubはスケールして長期間にわたってTeams APIをサポートできるようになりました。既存のAPIエンドポイントは、2021の早期に非推奨になります。{% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'ユーザは、Pull Requestの説明でキーワードをクローズせずに[IssueとPull Request間のリンクを作成](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue)できます。{% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' security_fixes: - - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - '**高:** Organizationのメンバーが権限を昇格させ、Organization内の認可されていないリポジトリへのアクセスを取得できてしまう不適切なアクセス制御の脆弱性が、GitHub Enterprise Server APIで特定されました。この脆弱性は、2.21以前のすべてのGitHub Enterprise Serverに影響します。この問題に対応して、[CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516)を発行しました。この脆弱性は、[GitHubバグバウンティプログラム](https://bounty.github.com)で報告されました。{% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' bugs: - - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" - - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" - - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' - - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' - - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' - - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' - - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' - - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' - - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' - - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' - - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' - - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' - - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' - - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + - "プッシュアクセス権を持つユーザが他のユーザのコメントを最小化した場合、コメントの作者は十分な権限を持っていない場合であっても最小化を解除できてしまいました。{% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'ユーザが意図せずIssueテンプレートエディタやblobエディタからmasterにマージできてしまいました。{% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'ユーザがGitHubからアカウントを削除した際に、監査ログのレコードは正しくOrganizationの削除レコードを示しませんでした。{% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - '現在のユーザのGistのアバターが存在しないURLにリンクします。{% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'Organizationのリポジトリタブのカウントに、インターナルリポジトリが含まれませんでした。{% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'リポジトリの委譲時に"Show All Teams"ボタンをクリックすると、500エラーが生じました。 {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "diffファイルビュー上で'Changed since last view'ラベルもしくは'Show rich'のdiffトグルを表示する際に、長いファイル名によってオーバーフローの問題が生じることがありました。{% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'OrganizationのTeamのためのホバーカードが、メンバーのサイズを間違って報告していました。{% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'Pull Requestのレビューコメントのポップアップウィンドウに、スクロールの問題がありました。{% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxyが飽和して、gitの操作が遅くなることがありました。{% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'HAレプリカの昇格の後、依存関係グラフの機能が自動的に有効になりませんでした。{% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - '大量のドラフトのPull Requestを持つリポジトリのリリースインデックスページで、タイムアウトが生じることがありました。{% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - '同時に状態とドラフトの両方でPull Requestをフィルタすることができませんでした。{% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'Pull Requestがサブモジュールポインタを変更した場合、Pull Requestのページの"Files changed"タブからサブモジュールファイル上の"Edit file"をクリックすると、404エラーが生じました。{% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'Organizationからすべてのユーザと管理者を一括削除した後、そのOrganizationにユーザを追加したり、そのOrganizationを削除したりすることができませんでした。{% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'ファイル名に発音区別符号と非ラテン文字をファイル名に含むファイルに対する"Files changed"ページのレビューコメントが、ページがリロードすると消えます。 {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - '"Viewed" チェックボックスの状態は、"Files changed"ページのファイル名に発音区別符号と非ラテン文字を含むファイルに対して保持されませんでした。 {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'すべての必須レビューが揃っていない場合にPull Requestが"Approved"バッジを表示していました。{% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - '100以上のタグを持つリポジトリでタグを検索する際に、タグのドロップダウンが空になっていました。{% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - '非UTF-8のタイトルを持つアノテーションを表示するPull Requestのページで、表示のレンダリングの際にエンコーディングエラーが生じることがありました。{% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'OAuthページのリフレッシュのレース条件により、リダイレクトが2回実行されることがありました。{% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - '10以上のトークンがある場合、"Personal Access Tokens"ページがタイムアウトします。{% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'スケジュールされたLDAPのユーザとTeamの同期ジョブが、以前のスケジュールされた同期のジョブがまだ進行中であっても開始されてしまうことがありました。同期のジョブが実行中の場合に新しい同期ジョブが開始されてしまうのを避けるために、ロックのメカニズムが実装されました。{% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' changes: - - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' - - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' - - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' - - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' - - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - '新しい[states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)、[filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)、[shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications)を含むWeb通知インターフェースがアップデートされました。{% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'LDAPの同期でのLDAPユーザの再アクティベートを無効化できるようになりました。{% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'プッシュ保護されたブランチの文言が更新され、管理者は常にプッシュでき、Maintainロールを持つユーザはステータスチェックをパスした場合にプッシュできることが明確化されました。{% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - '提案が元のテキストと同じ場合、空のコミットを防止します。{% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'REST APIを通じて、コミットに関連づけられたdiff中のより多くのファイルを取得する方法として、ページネーションがサポートされました。{% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - '管理者は、`ghe-webhook-manage`を使ってコマンドラインからwebhook IDを利用してwebhookの有効化、無効化、削除、検索を行えます。{% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'マージされたPull Requestに対する手動のhead参照のクリーンアップが行われた後、自動のベース再ターゲティングが行われます。{% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVGファイルはdiffビュー内でテキスト及び画像として扱われます。{% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' @@ -66,7 +66,7 @@ sections: - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/1.yml b/translations/ja-JP/data/release-notes/2-21/1.yml index 9b802bd1f3..6177efb3a8 100644 --- a/translations/ja-JP/data/release-notes/2-21/1.yml +++ b/translations/ja-JP/data/release-notes/2-21/1.yml @@ -16,5 +16,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/10.yml b/translations/ja-JP/data/release-notes/2-21/10.yml index 65b5d9c64c..92088b6ad9 100644 --- a/translations/ja-JP/data/release-notes/2-21/10.yml +++ b/translations/ja-JP/data/release-notes/2-21/10.yml @@ -11,5 +11,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/11.yml b/translations/ja-JP/data/release-notes/2-21/11.yml index ce20fbe36a..ed95c874c5 100644 --- a/translations/ja-JP/data/release-notes/2-21/11.yml +++ b/translations/ja-JP/data/release-notes/2-21/11.yml @@ -14,5 +14,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/12.yml b/translations/ja-JP/data/release-notes/2-21/12.yml index c347bb7aca..8a11a3a985 100644 --- a/translations/ja-JP/data/release-notes/2-21/12.yml +++ b/translations/ja-JP/data/release-notes/2-21/12.yml @@ -13,4 +13,4 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/13.yml b/translations/ja-JP/data/release-notes/2-21/13.yml index 06e910bb50..ba364556bb 100644 --- a/translations/ja-JP/data/release-notes/2-21/13.yml +++ b/translations/ja-JP/data/release-notes/2-21/13.yml @@ -16,4 +16,4 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/14.yml b/translations/ja-JP/data/release-notes/2-21/14.yml index 97d5bac00a..201c8ffdbb 100644 --- a/translations/ja-JP/data/release-notes/2-21/14.yml +++ b/translations/ja-JP/data/release-notes/2-21/14.yml @@ -10,4 +10,4 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/2.yml b/translations/ja-JP/data/release-notes/2-21/2.yml index bdac746dbc..6a19c2ef97 100644 --- a/translations/ja-JP/data/release-notes/2-21/2.yml +++ b/translations/ja-JP/data/release-notes/2-21/2.yml @@ -16,5 +16,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/3.yml b/translations/ja-JP/data/release-notes/2-21/3.yml index dd4ccbbb5e..ceedf888c7 100644 --- a/translations/ja-JP/data/release-notes/2-21/3.yml +++ b/translations/ja-JP/data/release-notes/2-21/3.yml @@ -13,5 +13,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/4.yml b/translations/ja-JP/data/release-notes/2-21/4.yml index e90460c88e..3b1c3b7b84 100644 --- a/translations/ja-JP/data/release-notes/2-21/4.yml +++ b/translations/ja-JP/data/release-notes/2-21/4.yml @@ -23,5 +23,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/5.yml b/translations/ja-JP/data/release-notes/2-21/5.yml index 444cf28527..6df83f51c2 100644 --- a/translations/ja-JP/data/release-notes/2-21/5.yml +++ b/translations/ja-JP/data/release-notes/2-21/5.yml @@ -11,5 +11,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/7.yml b/translations/ja-JP/data/release-notes/2-21/7.yml index 69134720e7..bde6b2b9d3 100644 --- a/translations/ja-JP/data/release-notes/2-21/7.yml +++ b/translations/ja-JP/data/release-notes/2-21/7.yml @@ -10,5 +10,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/8.yml b/translations/ja-JP/data/release-notes/2-21/8.yml index b7bf410b13..e99018a3fd 100644 --- a/translations/ja-JP/data/release-notes/2-21/8.yml +++ b/translations/ja-JP/data/release-notes/2-21/8.yml @@ -12,5 +12,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/9.yml b/translations/ja-JP/data/release-notes/2-21/9.yml index 46656c9e6b..859227f743 100644 --- a/translations/ja-JP/data/release-notes/2-21/9.yml +++ b/translations/ja-JP/data/release-notes/2-21/9.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' @@ -25,5 +25,5 @@ sections: - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-22/1.yml b/translations/ja-JP/data/release-notes/2-22/1.yml index fbd3988c3d..8edfa619f0 100644 --- a/translations/ja-JP/data/release-notes/2-22/1.yml +++ b/translations/ja-JP/data/release-notes/2-22/1.yml @@ -12,7 +12,7 @@ sections: - | Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | diff --git a/translations/ja-JP/data/release-notes/3-0/0-rc1.yml b/translations/ja-JP/data/release-notes/3-0/0-rc1.yml new file mode 100644 index 0000000000..99429fc282 --- /dev/null +++ b/translations/ja-JP/data/release-notes/3-0/0-rc1.yml @@ -0,0 +1,145 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. 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 variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API の変更 + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - 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. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ja-JP/data/release-notes/3-0/0-rc2.yml b/translations/ja-JP/data/release-notes/3-0/0-rc2.yml new file mode 100644 index 0000000000..0e6ed5fd3f --- /dev/null +++ b/translations/ja-JP/data/release-notes/3-0/0-rc2.yml @@ -0,0 +1,25 @@ +--- +date: '2021-01-29' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +sections: + bugs: + - + heading: Fixes for known issues from Release Candidate 1 + notes: + - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. + - The "Mandatory message viewed" audit log event was not being saved. + - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' + - Removing yourself as an enterprise owner returned a 404. + - + heading: Fixes for other issues + notes: + - Issues with migrations and upgrades to 3.0.0 have been fixed. + - Backup Utilities versioning now works for release candidate versions. + - Generating a support bundle resulted in an error in the orchestrator logs. + - A large restore could result in Redis running out of memory. + - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. + - GitHub Actions can only be enabled if the required storage is also configured. + - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + known_issues: + - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/translations/ja-JP/data/reusables/actions/actions-not-verified.md b/translations/ja-JP/data/reusables/actions/actions-not-verified.md index 3107e5a79f..1eebaf90f5 100644 --- a/translations/ja-JP/data/reusables/actions/actions-not-verified.md +++ b/translations/ja-JP/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md b/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md index e2f4ed9452..b1a5f829f1 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-limit-actions-use.md @@ -1 +1 @@ -After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. 詳しい情報については、「[Enterprise に GitHub Actions のポリシーを施行する](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/actions/enterprise-marketplace-actions.md b/translations/ja-JP/data/reusables/actions/enterprise-marketplace-actions.md index a4e6cdf8de..efe118df97 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-marketplace-actions.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-marketplace-actions.md @@ -2,7 +2,7 @@ {% note %} -**Note:** {% data variables.product.prodname_actions %} on {% data variables.product.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. 詳しい情報については「[セルフホストランナーと{% data variables.product.prodname_dotcom %}の通信](#communication-between-self-hosted-runners-and-github)」を参照してください。 +**Note:** {% data variables.product.prodname_actions %} on {% data variables.product.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. 詳しい情報については「[{% data variables.product.prodname_dotcom_the_website %}からのアクションへのアクセスの管理](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)」を参照し、{% data variables.product.prodname_enterprise %}のサイト管理者に連絡してください。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md b/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md index e554d4b605..5881f623ee 100644 --- a/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) +1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. 詳しい情報については、「[新しい Organization をゼロから作成する](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)」を参照してください。 ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) 1. Type the name for your classroom. ![Text field for typing name of classroom](/assets/images/help/classroom/type-classroom-name.png) 1. Click **Create classroom**. ![Text field for typing name of classroom](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/ja-JP/data/reusables/code-scanning/not-available.md b/translations/ja-JP/data/reusables/code-scanning/not-available.md index 6531f5e1d0..0e4d2ac82f 100644 --- a/translations/ja-JP/data/reusables/code-scanning/not-available.md +++ b/translations/ja-JP/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." {% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md new file mode 100644 index 0000000000..c5142332f6 --- /dev/null +++ b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md index a172d82608..1a1527e5ee 100644 --- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md @@ -1,34 +1,35 @@ -The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. +The following table shows, for each package manager: +- The YAML value to use in the *dependabot.yml* file +- The supported versions of the package manager +- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +- Whether vendored dependencies are supported -| パッケージマネージャー | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | -| -------------------------------- |:-----------------------------------------------------------------:|:---------:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir: `hex` | | | -| Elm: `elm` | **✓** | | -| gitサブモジュール:`gitsubmodule` | **✓** | | -| GitHub Actions: `github-actions` | **✓** | | -| Goモジュール:`gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +| パッケージマネージャー | YAML value | Supported versions | Private repositories | Vendoring | +| -------------- | ---------------- | ------------------------- |:--------------------:|:---------:| +| Bundler | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1,v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | +| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | +| Go modules | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | see (A) below | **✓** | | +| Maven | `maven` | see (B) below | **✓** | | +| npm | `npm` | v6 | **✓** | | +| NuGet | `nuget` | <= 4.8.
    see (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**Note**: {% data variables.product.prodname_dependabot %} also supports the following package managers: +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn` (v1 only) (specify `npm`) +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --`.gradle.kts` files, for Kotlin projects (specify `gradle`) - --`pipenv`, `pip-compile`, and `poetry` (specify `pip`) - -For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. diff --git a/translations/ja-JP/data/reusables/desktop/delete-tag.md b/translations/ja-JP/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..40d455b880 --- /dev/null +++ b/translations/ja-JP/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Right-click the commit. + + - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) + - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/education/about-github-education-link.md b/translations/ja-JP/data/reusables/education/about-github-education-link.md index db36f0cbec..8402f201d9 100644 --- a/translations/ja-JP/data/reusables/education/about-github-education-link.md +++ b/translations/ja-JP/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_education %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_education %} について](/education/teach-and-learn-with-github-education/about-github-education)」を参照してください。 +個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_education %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_education %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/education/apply-for-team.md b/translations/ja-JP/data/reusables/education/apply-for-team.md index 3fa2344166..f8f9508edf 100644 --- a/translations/ja-JP/data/reusables/education/apply-for-team.md +++ b/translations/ja-JP/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- 無料の[{% data variables.product.prodname_team %}](/articles/github-s-products)に応募してください。{% data variables.product.prodname_team %}では、無制限のユーザとプライベートリポジトリが利用できます。 For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." +- 無料の[{% data variables.product.prodname_team %}](/articles/github-s-products)に応募してください。{% data variables.product.prodname_team %}では、無制限のユーザとプライベートリポジトリが利用できます。 For more information, see "[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)." diff --git a/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md index 7f1c4f4720..1811645d3b 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. {% data variables.product.product_location %}にSSHでアクセスしてください。 +1. {% data variables.product.product_location %}にSSHでアクセスしてください。 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。 ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/ja-JP/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/ja-JP/data/reusables/enterprise_migrations/ready-to-import-migrations.md index b49d8c0ac8..0cdbb1f880 100644 --- a/translations/ja-JP/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/ja-JP/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. アーカイブされたマイグレーションデータを {% data variables.product.prodname_ghe_server %} のインスタンスにインポートする方法については「[{% data variables.product.prodname_ghe_server %} へのマイグレーションデータのインポート](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)」を参照してください。 +1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[Preparing to migrate data to your enterprise](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/ja-JP/data/reusables/gated-features/private-pages.md b/translations/ja-JP/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..3fb7f0a3a7 --- /dev/null +++ b/translations/ja-JP/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/ja-JP/data/reusables/github-actions/actions-billing.md b/translations/ja-JP/data/reusables/github-actions/actions-billing.md index 283a221a48..5c2243e13d 100644 --- a/translations/ja-JP/data/reusables/github-actions/actions-billing.md +++ b/translations/ja-JP/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. プライベートリポジトリでは、それぞれの{% data variables.product.prodname_dotcom %}アカウントは使用している製品に応じて一定量の無料の分とストレージを受け取ります。 Any usage beyond the included amounts is controlled by spending limits. +{% data variables.product.prodname_actions %} usage is free for both public repositories and self-hosted runners. プライベートリポジトリでは、それぞれの{% data variables.product.prodname_dotcom %}アカウントは使用している製品に応じて一定量の無料の分とストレージを受け取ります。 Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ja-JP/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/ja-JP/data/reusables/github-actions/artifact-log-retention-statement.md index b45a4b1e26..d8190b0418 100644 --- a/translations/ja-JP/data/reusables/github-actions/artifact-log-retention-statement.md +++ b/translations/ja-JP/data/reusables/github-actions/artifact-log-retention-statement.md @@ -1,2 +1,2 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and this retention period can be customized. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)".{% endif %} -{% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} には、完全なビルドログとアーティファクトが 90 日間保存されます。{% endif %} +{% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} には、完全なビルドログと成果物が 90 日間保存されます。{% endif %} diff --git a/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md b/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md index 8c557fc777..6e4c7338be 100644 --- a/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ たとえば、x64プラットフォーム用のバージョン9.0.4のJDKを使いたい場合、 `setup-java`アクションを使って `java-version`及び`architecture`パラメーターを`'9.0.4'`と`x64`に設定できます。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md b/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md index e6db4f8803..0114ffafd7 100644 --- a/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a private preview only. Any users or organizations that are already using this runner can continue using it, but we're not accepting any further users or organizations at this time. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/ja-JP/data/reusables/marketplace/launch-with-free.md b/translations/ja-JP/data/reusables/marketplace/launch-with-free.md index 2151c241cc..15e06d0cb2 100644 --- a/translations/ja-JP/data/reusables/marketplace/launch-with-free.md +++ b/translations/ja-JP/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/ja-JP/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/ja-JP/data/reusables/organizations/reseller-ask-to-become-billing-manager.md index d1534e68a7..29620e32dc 100644 --- a/translations/ja-JP/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ b/translations/ja-JP/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -1 +1 @@ -あなたがOrganizationの支払いマネージャーではないなら、Organizationの*オーナー*に[あなたを支払いマネージャーとしてOrganizationに追加](/articles/adding-a-billing-manager-to-your-organization)するようクライアントに求めてください。 +If you're not a billing manager for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/ja-JP/data/reusables/pages/about-private-publishing.md b/translations/ja-JP/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..f1f13531ce --- /dev/null +++ b/translations/ja-JP/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. diff --git a/translations/ja-JP/data/reusables/pages/choose-visibility.md b/translations/ja-JP/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..bd794a90d7 --- /dev/null +++ b/translations/ja-JP/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..fc98787aaa --- /dev/null +++ b/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md b/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md index b2f49df525..04d4ddeb1c 100644 --- a/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. サイトのリポジトリにセンシティブなデータがあるなら、公開前にそれを取り除くのが良いでしょう。 For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md b/translations/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..b1b8974d29 --- /dev/null +++ b/translations/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。 1時間経っても変更がブラウザーに反映されなければ、「[{% data variables.product.prodname_pages %}サイトのJekyllビルドエラーについて](/articles/about-jekyll-build-errors-for-github-pages-sites)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/pages/visit-site.md b/translations/ja-JP/data/reusables/pages/visit-site.md index 4bdbf98356..5a45bd9883 100644 --- a/translations/ja-JP/data/reusables/pages/visit-site.md +++ b/translations/ja-JP/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% note %} - **メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。 1時間経っても変更がブラウザーに反映されなければ、「[{% data variables.product.prodname_pages %}サイトのJekyllビルドエラーについて](/articles/about-jekyll-build-errors-for-github-pages-sites)」を参照してください。 + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md index d42d4c5f70..77d7f1bad7 100644 --- a/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ プルリクエストをリベースしてマージするには、リポジトリへの[書き込み権限](/articles/repository-permission-levels-for-an-organization/)が必要で、リポジトリでは[リベースマージが許可](/articles/configuring-commit-rebasing-for-pull-requests/)されていなければなりません。 -{% data variables.product.product_name %}上でのリベースとマージの振る舞いは、`gitのリベース`とは少し異なっています。 {% data variables.product.prodname_dotcom %}上でのリベースとマージは、常にコミッターの情報を更新し、新しいSHAを生成しますが、{% data variables.product.prodname_dotcom %}外での`git rebase`は祖先のコミット上でリベースが生じたときにコミッター情報を変更しません。 `git rebase`に関する詳しい情報については[書籍_Pro Git_の"Git rebase" の章](https://git-scm.com/docs/git-rebase)を参照してください。 +{% data variables.product.product_name %}上でのリベースとマージの振る舞いは、`gitのリベース`とは少し異なっています。 {% data variables.product.prodname_dotcom %}上でのリベースとマージは、常にコミッターの情報を更新し、新しいSHAを生成しますが、{% data variables.product.prodname_dotcom %}外での`git rebase`は祖先のコミット上でリベースが生じたときにコミッター情報を変更しません。 For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). `git rebase`の視覚的な表現については、[書籍_Pro Git_の"Git Branching - Rebasing"の章](https://git-scm.com/book/en/Git-Branching-Rebasing)を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md index 0fac301855..6db2640af4 100644 --- a/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,5 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +1. [**Jobs**] または視覚化グラフで、表示するジョブをクリックします。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) {% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. 左のサイドバーで、表示させたいジョブをクリックしてください。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} diff --git a/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md index 918dab289f..c83e052fa8 100644 --- a/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -If you use Okta as your IdP, you can use SCIM to manage organization membership in your enterprise account. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. +If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. diff --git a/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md index cadca78570..231a386883 100644 --- a/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md +++ b/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md @@ -1 +1 @@ -If you can't sign into your enterprise because {% data variables.product.product_name %} can't communicate with your SAML IdP, you can contact {% data variables.contact.github_support %}, who can help you access {% data variables.product.product_name %} to update the SAML SSO configuration. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." +If you can't sign into your enterprise because {% data variables.product.product_name %} can't communicate with your SAML IdP, you can contact {% data variables.contact.github_support %}, who can help you access {% data variables.product.product_name %} to update the SAML SSO configuration. 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md b/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md index 7b7bf4115a..306c505acf 100644 --- a/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. Scroll down to the Marketplace section and click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md index e6571e457a..e67eeed7c6 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| キー | 種類 | 説明 | -| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| キー | 種類 | 説明 | +| -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index 0a1c0cbd38..f36f53a2bb 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -138,9 +138,19 @@ product_sublanding: learning_paths: Learning paths learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. more_guides: その他のガイド - guideTypes: + load_more: Load more guides + all_guides: All Guides + no_result: Sorry, there is no guide that match your filter. + filters: + type: 種類 + topic: Topic + all: すべて + guide_types: overview: 概要 quick_start: クイックスタート tutorial: チュートリアル how_to: How-to guide reference: リファレンス +learning_track_nav: + prevGuide: Previous guide + nextGuide: Next guide diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index 00c61c887c..cdfd06514e 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -61,6 +61,7 @@ prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub App' prodname_github_apps: 'GitHub Apps' prodname_oauth_app: 'OAuth App' +prodname_oauth_apps: 'OAuth App' #API and developer docs prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs' prodname_support_forum_with_url: '[GitHub API Development and Support Forum](https://github.community/c/github-api-development-and-support/37)' diff --git a/translations/ko-KR/content/actions/creating-actions/about-actions.md b/translations/ko-KR/content/actions/creating-actions/about-actions.md index b1122cbf02..860bacb35b 100644 --- a/translations/ko-KR/content/actions/creating-actions/about-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/about-actions.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - Action development + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ steps: #### Using a commit's SHA for release management -Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation. +Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value.{% else %}Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation.{% endif %} ```yaml steps: diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md index d113dcfbf2..d0ef109ced 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,7 +5,9 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Action development --- {% data reusables.actions.enterprise-beta %} @@ -65,12 +67,12 @@ Before you begin, you'll create a {% data variables.product.product_name %} repo required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -122,7 +124,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md index f64f0dcaeb..edb79de5be 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -1,6 +1,6 @@ --- title: Creating a Docker container action -intro: 'This guide shows you the minimal steps required to build a Docker container action.' +intro: This guide shows you the minimal steps required to build a Docker container action. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Action development + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ Before you begin, you'll need to create a GitHub repository. 1. From your terminal, change directories into your new repository. - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ Before you begin, you'll need to create a GitHub repository. In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)." **Dockerfile** -```dockerfile +```dockerfile{:copy} # Container image that runs your code FROM alpine:3.10 @@ -65,7 +68,7 @@ Create a new `action.yml` file in the `hello-world-docker-action` directory you {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ Next, the script gets the current time and sets it as an output variable that ac 1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory. -1. Make your `entrypoint.sh` file executable: - - ```shell - chmod +x entrypoint.sh - ``` - 1. Add the following code to your `entrypoint.sh` file. **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" time=$(date) echo "::set-output name=time::$time" ``` - 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. Make your `entrypoint.sh` file executable by running the following command on your system. + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### Creating a README 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. @@ -130,7 +132,7 @@ In your `hello-world-docker-action` directory, create a `README.md` file that sp - An example of how to use your action in a workflow. **README.md** -```markdown +```markdown{:copy} # Hello world docker action This action prints "Hello World" or "Hello" + the name of a person to greet to the log. @@ -160,7 +162,7 @@ From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and 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 entrypoint.sh Dockerfile README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1 @@ -175,11 +177,11 @@ Now you're ready to test your action out in a workflow. When an action is in a p #### Example using a public action -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. +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. {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### Example using a private action -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. +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. {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md index 73c7dbd452..c3b48c869d 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Action development + - JavaScript --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index a38c66beb8..f446209cd2 100644 --- a/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,7 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '참조' +type: reference --- {% data reusables.actions.enterprise-beta %} @@ -48,20 +48,21 @@ The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Dock If you configure your container to use the _exec_ form of the `ENTRYPOINT` instruction, the `args` configured in the action's metadata file won't run in a command shell. If the action's `args` contain an environment variable, the variable will not be substituted. For example, using the following _exec_ format will not print the value stored in `$GITHUB_SHA`, but will instead print `"$GITHUB_SHA"`. -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` If you want variable substitution, then either use the _shell_ form or execute a shell directly. For example, using the following _exec_ format, you can execute a shell to print the value stored in the `GITHUB_SHA` environment variable. -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction: ##### Example *Dockerfile* -``` + +```dockerfile # Container image that runs your code FROM debian:9.5-slim diff --git a/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md index 1edcdcee6e..77941f7d1f 100644 --- a/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,11 +41,13 @@ For more information, see "[Creating a JavaScript action](/articles/creating-a-j If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. 예시: +{% raw %} ``` if ; then echo "Game over!" exit 1 fi ``` +{% endraw %} For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)." diff --git a/translations/ko-KR/content/actions/guides/about-continuous-integration.md b/translations/ko-KR/content/actions/guides/about-continuous-integration.md index ffb01fc4b5..3fd114ea37 100644 --- a/translations/ko-KR/content/actions/guides/about-continuous-integration.md +++ b/translations/ko-KR/content/actions/guides/about-continuous-integration.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - CI + - CD --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md b/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md index b600ef4726..87716ad09b 100644 --- a/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - 패키징 --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/about-service-containers.md b/translations/ko-KR/content/actions/guides/about-service-containers.md index 88705ae391..f6bb91502c 100644 --- a/translations/ko-KR/content/actions/guides/about-service-containers.md +++ b/translations/ko-KR/content/actions/guides/about-service-containers.md @@ -8,7 +8,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ You can use the `services` keyword to create service containers that are part of This example creates a service called `redis` in a job called `container-job`. The Docker host in this example is the `node:10.18-jessie` container. {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -89,7 +92,7 @@ When you specify the Docker host port but not the container port, the container This example maps the service container `redis` port 6379 to the Docker host port 6379. {% raw %} -```yaml +```yaml{:copy} name: Redis Service Example on: push diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md index 798cfedb97..1618ce4e6f 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CI + - Java + - Ant --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ To get started quickly, you can choose the preconfigured Ant template when you c You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ The starter workflow will run the default target specified in your _build.xml_ f If you use different commands to build your project, or you want to run a different target, you can specify those. For example, you may want to run the `jar` target that's configured in your _build-ci.xml_ file. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ After your build has succeeded and your tests have passed, you may want to uploa Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You can upload the contents of that directory using the `upload-artifact` action. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md index 8102ae80bd..3e1380fcfb 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CI + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ To get started quickly, you can choose the preconfigured Gradle template when yo You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ The starter workflow will run the `build` task by default. In the default Gradle If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your _ci.gradle_ file. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. + # Restoring these files from a GitHub Actions cache might cause problems for future builds. + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` directory of the runner's home directory. The cache key will be the hashed contents of the gradle build files, so changes to them will invalidate the cache. +This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache. ### Packaging workflow data as artifacts @@ -122,7 +135,7 @@ After your build has succeeded and your tests have passed, you may want to uploa Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md index 98b36f6b28..442eb68274 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CI + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ To get started quickly, you can choose the preconfigured Maven template when you You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ The starter workflow will run the `package` target by default. In the default Ma If you use different commands to build your project, or you want to use a different target, you can specify those. For example, you may want to run the `verify` target that's configured in a _pom-ci.xml_ file. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -122,7 +126,7 @@ After your build has succeeded and your tests have passed, you may want to uploa Maven will usually create output files like JARs, EARs, or WARs in the `target` directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory called `staging`. Then you can upload the contents of that directory using the `upload-artifact` action. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-net.md b/translations/ko-KR/content/actions/guides/building-and-testing-net.md index 117006bbec..077152dfbc 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-net.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. -The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action. #### Using multiple .NET versions diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md index 664dd8083a..29bbd7fde9 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md @@ -8,7 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CI + - Node + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -77,7 +81,7 @@ The template includes a matrix strategy that builds and tests your code with fou 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 "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." {% raw %} -```yaml +```yaml{:copy} strategy: matrix: node-version: [10.x, 12.x, 14.x, 15.x] @@ -93,7 +97,7 @@ steps: Alternatively, you can build and test with exact Node.js versions. -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -102,7 +106,7 @@ strategy: Or, you can build and test using a single version of Node.js too. {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -136,7 +140,7 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -150,7 +154,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -166,7 +170,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -179,7 +183,7 @@ steps: Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -201,7 +205,7 @@ In the example below, the secret `NPM_TOKEN` stores the npm authentication token 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -220,7 +224,7 @@ steps: The example above creates an *.npmrc* file with the following contents: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -231,7 +235,7 @@ always-auth=true When using {% data variables.product.prodname_dotcom %}-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" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -256,7 +260,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md b/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md index 40c2f949b7..c15aad2933 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md @@ -7,7 +7,10 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee -type: '튜토리얼' +type: tutorial +topics: + - CI + - Powershell --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-python.md b/translations/ko-KR/content/actions/guides/building-and-testing-python.md index 1fb1cf75d2..fbe336a3af 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-python.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-python.md @@ -7,7 +7,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CI + - Python --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ We recommend that you have a basic understanding of Python, PyPy, and pip. For m To get started quickly, add the template to the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -94,7 +97,7 @@ If you are using a self-hosted runner, you can configure the runner to use the ` #### Using multiple Python versions {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -126,7 +129,7 @@ jobs: 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 +```yaml{:copy} name: Python package on: [push] @@ -158,7 +161,7 @@ If you specify a version of Python that is not available, `setup-python` fails w 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 +```yaml{:copy} name: Python package on: [push] @@ -196,7 +199,7 @@ We recommend using `setup-python` to configure the version of Python used in you 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -213,7 +216,7 @@ steps: After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -234,7 +237,7 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can 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). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Setup Python @@ -271,7 +274,7 @@ You can use the same commands that you use locally to build and test your code. 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -295,7 +298,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -318,7 +321,7 @@ steps: 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 +```yaml{:copy} name: Python package on: [push] @@ -352,7 +355,7 @@ You can upload artifacts to view after a workflow completes. For example, you ma 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 +```yaml{:copy} name: Python package on: [push] @@ -365,26 +368,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} ``` {% endraw %} @@ -395,7 +398,7 @@ You can configure your workflow to publish your Python package to any package re You can store any access tokens or credentials needed to publish your package using secrets. The following example creates and publishes a package to PyPI using `twine` and `dist`. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." {% raw %} -```yaml +```yaml{:copy} name: Upload Python Package on: diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md index acee994c00..87f1da5dc3 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md @@ -5,7 +5,10 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CI + - Ruby --- {% data reusables.actions.enterprise-beta %} @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -63,7 +63,7 @@ jobs: The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index bd1391b865..3cbdf80461 100644 --- a/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,7 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: '튜토리얼' +type: tutorial +topics: + - Workflows --- ### About caching workflow dependencies @@ -68,7 +70,7 @@ For more information, see [`actions/cache`](https://github.com/actions/cache). This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file. {% raw %} -```yaml +```yaml{:copy} name: Caching with npm on: push @@ -124,14 +126,14 @@ A cache key can include any of the contexts, functions, literals, and operators Using expressions to create a `key` allows you to automatically create a new cache when dependencies have changed. For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file. {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`. -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ You can provide a list of restore keys to use when there is a cache miss on `key #### Example using multiple restore keys {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | The runner evaluates the expressions, which resolve to these `restore-keys`: {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md b/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md index 765cb8d47e..e3c115aba5 100644 --- a/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL service example on: push @@ -94,7 +97,7 @@ jobs: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} jobs: # Label of the container job container-job: @@ -124,7 +127,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -159,7 +162,7 @@ When you run a job directly on the runner machine, you'll need to map the ports {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL Service Example on: push @@ -220,7 +223,7 @@ jobs: The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)." -```yaml +```yaml{:copy} jobs: # Label of the runner job runner-job: @@ -251,7 +254,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -287,7 +290,7 @@ You can modify *client.js* to include any PostgreSQL operations needed by your w {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md b/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md index f34c0739e2..4bd051eae7 100644 --- a/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md +++ b/translations/ko-KR/content/actions/guides/creating-redis-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -91,7 +94,7 @@ jobs: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} jobs: # Label of the container job container-job: @@ -118,7 +121,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -152,7 +155,7 @@ When you run a job directly on the runner machine, you'll need to map the ports {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis runner example on: push @@ -210,7 +213,7 @@ jobs: The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)." -```yaml +```yaml{:copy} jobs: # Label of the runner job runner-job: @@ -238,7 +241,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -274,7 +277,7 @@ You can modify *client.js* to include any Redis operations needed by your workfl {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // Creates a new Redis client diff --git a/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md index e5cf699608..1a9afea71c 100644 --- a/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Amazon ECS --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md b/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md index 41e19c44f2..5b904f6f56 100644 --- a/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Azure App Service --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md index 68ab5f9463..31ee61ac48 100644 --- a/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/index.md b/translations/ko-KR/content/actions/guides/index.md index c4c3c5a9c0..0866a7e714 100644 --- a/translations/ko-KR/content/actions/guides/index.md +++ b/translations/ko-KR/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/ko-KR/content/actions/guides/publishing-docker-images.md b/translations/ko-KR/content/actions/guides/publishing-docker-images.md index 2f4287c24c..b79dba03a8 100644 --- a/translations/ko-KR/content/actions/guides/publishing-docker-images.md +++ b/translations/ko-KR/content/actions/guides/publishing-docker-images.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - 패키징 + - Publishing + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -55,7 +59,7 @@ The `build-push-action` options required for Docker Hub are: * `repository`: Your Docker Hub repository in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -93,7 +97,7 @@ The `build-push-action` options required for {% data variables.product.prodname_ * `repository`: Must be set in the format `OWNER/REPOSITORY/IMAGE_NAME`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `repository` option should be set to `octo-org/octo-repo/octo-image`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -126,7 +130,7 @@ In a single workflow, you can publish your Docker image to multiple registries b The following example workflow uses the `build-push-action` steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: diff --git a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md index 21c7ba7e06..e1d7cb6453 100644 --- a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - 패키징 + - Publishing + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ Each time you create a new release, you can trigger a workflow to publish your p You can define a new Maven repository in the publishing block of your _build.gradle_ file that points to your package repository. For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _build.gradle_ could specify a repository with the name `"OSSRH"`. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -67,7 +72,7 @@ In the deploy step, you’ll need to set environment variables for the username {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -105,7 +110,7 @@ The `GITHUB_TOKEN` exists in your repository by default and has read and write p For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -126,7 +131,7 @@ publishing { With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -162,7 +167,7 @@ For example, if you deploy to the Central Repository through the OSSRH hosting p If your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -191,7 +196,7 @@ publishing { With this configuration, you can create a workflow that publishes your package to both the Maven Central Repository and {% data variables.product.prodname_registry %} by running the `gradle publish` command. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md index 7e10e0b45c..afec7018cb 100644 --- a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - 패키징 + - Publishing + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +52,7 @@ In this workflow, you can use the `setup-java` action. This action installs the For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _pom.xml_ could specify a distribution management repository with the `id` of `ossrh`. {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ In the deploy step, you’ll need to set the environment variables to the userna {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ For a Maven-based project, you can make use of these settings by creating a dist For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _pom.xml_ would look similar to the below example. {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ For example, if your organization is named "octocat" and your repository is name With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by making use of the automatically generated _settings.xml_. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ You can publish your packages to both the Maven Central Repository and {% data v Ensure your _pom.xml_ file includes a distribution management repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider. For example, if you deploy to the Central Repository through the OSSRH hosting project, you might want to specify it in a distribution management repository with the `id` set to `ossrh`, and you might want to specify {% data variables.product.prodname_registry %} in a distribution management repository with the `id` set to `github`. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md index 9e306dd15a..ee20e1db7c 100644 --- a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md @@ -8,7 +8,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - 패키징 + - Publishing + - Node + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -54,7 +59,7 @@ If you're publishing a package that includes a scope prefix, include the scope i This example stores the `NPM_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -78,7 +83,7 @@ jobs: In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -114,7 +119,7 @@ If you want to publish your package to a different repository, you must use a pe This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -140,7 +145,7 @@ jobs: The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file. -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -151,7 +156,7 @@ always-auth=true If you use the Yarn package manager, you can install and publish packages using Yarn. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -167,7 +172,7 @@ jobs: node-version: '12.x' registry-url: 'https://registry.npmjs.org' # Defaults to the user or organization that owns the workflow file - scope: '@octocat' + scope: '@octocat' - run: yarn - run: yarn publish env: @@ -196,7 +201,7 @@ When you use the `scope` input to the `setup-node` action, the action creates an This workflow calls the `setup-node` action two times. Each time the `setup-node` action runs, it overwrites the *.npmrc* file. The *.npmrc* file references the token that allows you to perform authenticated operations against the package registry from the `NODE_AUTH_TOKEN` environment variable. The workflow sets the `NODE_AUTH_TOKEN` environment variable each time the `npm publish` command is run, first with a token to publish to npm (`NPM_TOKEN`) and then with a token to publish to {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`). {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: diff --git a/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 294e7b41d8..2ba5495e3d 100644 --- a/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,7 +11,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Workflows + - CI --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md index f375980a66..04b7aa48fd 100644 --- a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,7 +11,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Workflows --- {% data reusables.actions.enterprise-beta %} @@ -79,7 +81,7 @@ This example shows you how to create a workflow for a Node.js project that build The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also and uploads the `code-coverage.html` report as another artifact. -```yaml +```yaml{:copy} name: Node CI on: [push] @@ -114,7 +116,7 @@ jobs: 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' uses: actions/upload-artifact@v2 with: @@ -183,7 +185,7 @@ Job 3 displays the result uploaded in the previous job: The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`. -```yaml +```yaml{:copy} name: Share data between jobs on: [push] diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index a4ec90c92c..09437cd950 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +38,7 @@ If setting environment variables is not practical, you can set the proxy configu An example _.env_ proxy configuration is shown below: -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 30ad9d91dc..77537c94ae 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -64,8 +64,11 @@ These labels operate cumulatively, so a self-hosted runner’s labels must match ### Routing precedence for self-hosted runners -If you use both repository-level and organization-level runners, {% data variables.product.prodname_dotcom %} follows an order of precedence when routing jobs to self-hosted runners: +When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels: -1. The job's `runs-on` labels are processed. {% data variables.product.prodname_dotcom %} then attempts to locate a runner that matches the label requirements: -2. The job is sent to a repository-level runner that matches the job labels. If no repository-level runner is available (either busy, offline, or no matching labels): -3. The job is sent to an organization-level runner that matches the job labels. If no organization-level runner is available, the job request fails with an error. +1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}. +2. The job is then sent to the first matching runner that is online and idle. + - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners. + - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners. + - If there are no matching runners at any level, the job will fail. + - If the job remains queued for more than 24 hours, the job will fail. diff --git a/translations/ko-KR/content/actions/index.md b/translations/ko-KR/content/actions/index.md index 39b2e0d291..6fffe233c7 100644 --- a/translations/ko-KR/content/actions/index.md +++ b/translations/ko-KR/content/actions/index.md @@ -10,21 +10,22 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: + - + title: Environments, environment protection rules and environment secrets (beta) + date: '2020-12-15' + href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ - title: Workflow visualization date: '2020-12-08' @@ -33,10 +34,6 @@ changelog: title: Removing set-env and add-path commands on November 16 date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Ubuntu-latest workflows will use Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ @@ -73,7 +70,7 @@ versions: {% render 'code-example-card' for actionsCodeExamples as example %} - +
    {% octicon "search" width="24" %}
    diff --git a/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md index 5f88701831..a8ba7998ed 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,7 +5,9 @@ intro: '{% data variables.product.prodname_actions %} are designed to help you b versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md index e109e9fa30..994afa3f26 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} @@ -68,7 +70,7 @@ steps: #### Using SHAs -If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. This example targets an action's SHA: +If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA: ```yaml steps: diff --git a/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md index b3b4742c38..a5543e3189 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -9,7 +9,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -147,7 +149,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s ```
    @@ -180,7 +182,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s ``` diff --git a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md index 3faf2e2dc7..c7f2f08a63 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 0350f4407f..68fec2ac9c 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Azure Pipelines + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -62,16 +67,16 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: scripts - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in the default shell" - - bash: echo "This step runs in bash" - - pwsh: Write-Host "This step runs in PowerShell Core" - - task: PowerShell@2 - inputs: - script: Write-Host "This step runs in PowerShell" + - job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" ``` {% endraw %} @@ -82,13 +87,13 @@ jobs: scripts: runs-on: windows-latest steps: - - run: echo "This step runs in the default shell" - - run: echo "This step runs in bash" - shell: bash - - run: Write-Host "This step runs in PowerShell Core" - shell: pwsh - - run: Write-Host "This step runs in PowerShell" - shell: powershell + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell ``` {% endraw %} @@ -123,11 +128,11 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_command - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in CMD on Windows by default" + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} @@ -138,9 +143,9 @@ jobs: run_command: runs-on: windows-latest steps: - - run: echo "This step runs in PowerShell on Windows by default" - - run: echo "This step runs in CMD on Windows explicitly" - shell: cmd + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %} @@ -171,12 +176,12 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: conditional - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This step runs with str equals 'ABC' and num equals 123" - condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) + - job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) ``` {% endraw %} @@ -187,8 +192,8 @@ jobs: conditional: runs-on: ubuntu-latest steps: - - run: echo "This step runs with str equals 'ABC' and num equals 123" - if: ${{ env.str == 'ABC' && env.num == 123 }} + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %} @@ -217,29 +222,29 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: initial - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This job will be run first." -- job: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout2." -- job: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout1." -- job: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - steps: - - script: echo "This job will run after fanout1 and fanout2 have finished." + - job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." + - job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." + - job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." + - job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -250,22 +255,22 @@ jobs: initial: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." fanout1: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout2." + - run: echo "This job will run after the initial job, in parallel with fanout2." fanout2: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout1." + - run: echo "This job will run after the initial job, in parallel with fanout1." fanin: runs-on: ubuntu-latest needs: [fanout1, fanout2] steps: - - run: echo "This job will run after fanout1 and fanout2 have finished." + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -294,15 +299,15 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_python - pool: - vmImage: 'ubuntu-latest' - steps: - - task: UsePythonVersion@0 - inputs: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} @@ -313,11 +318,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index b750afb569..2ab59b3ab8 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - CircleCI + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -258,24 +263,24 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem - - name: Setup file system permissions - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} @@ -412,35 +417,35 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - - uses: actions/checkout@v2 - - name: Setup Ruby - uses: eregon/use-ruby-action@master - with: - ruby-version: ${{ matrix.ruby }} - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: vendor/bundle - key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - name: Install postgres headers - run: sudo apt-get install libpq-dev - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake - - name: Install appraisal - run: bundle exec appraisal install - - name: Run appraisal - run: bundle exec appraisal rake + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 1275b42ee3..8d0d950df5 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,7 +4,12 @@ intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share sev versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - GitLab + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,12 +340,12 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} @@ -371,7 +376,7 @@ GitLab CI/CD script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -424,12 +429,12 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js tags: - docker ``` diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index c20ffe4884..dde19ef9c0 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Jenkins + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ Jenkins lets you send builds to a single build agent, or you can distribute them Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}. | Jenkins | {% data variables.product.prodname_actions %} -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### Using sections to organize pipelines @@ -51,7 +56,6 @@ Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% d | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### Using directives Jenkins uses directives to manage _Declarative Pipelines_. These directives define the characteristics of your workflow and how it will execute. The table below demonstrates how these directives map to concepts within {% data variables.product.prodname_actions %}. @@ -69,7 +73,6 @@ Jenkins uses directives to manage _Declarative Pipelines_. These directives defi | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### Using sequential stages #### Parallel job processing @@ -114,23 +117,23 @@ Jenkins Pipeline @@ -150,25 +153,24 @@ Jenkins Pipeline @@ -188,30 +190,28 @@ Jenkins Pipeline @@ -231,26 +231,27 @@ Jenkins Pipeline diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 071fac3971..d1cd53f390 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '튜토리얼' +type: tutorial +topics: + - Travis CI + - Migration + - CI + - CD --- ### Introduction @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -155,9 +160,9 @@ git: @@ -207,10 +212,10 @@ When working with different languages in {% data variables.product.prodname_acti 예시: ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` ### Error handling in {% data variables.product.prodname_actions %} @@ -275,11 +280,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} @@ -345,20 +350,20 @@ Travis CI @@ -378,24 +383,24 @@ Travis CI diff --git a/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 5a403d6aa1..5eb77d6e2e 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview +topics: + - 보안 --- {% data reusables.actions.enterprise-beta %} @@ -54,11 +56,13 @@ This means that a compromise of a single action within a workflow can be very si Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail. {% endwarning %} + {% endif %} * **Audit the source code of the action** @@ -140,4 +144,4 @@ The following tables describe the {% data variables.product.prodname_actions %} | `action:org.runner_group_removed` | Triggered when an organization admin removes a self-hosted runner group. | | `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | | `action:org.runner_group_runners_added` | Triggered when an organization admin [adds 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). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/ko-KR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index 162499b98a..523e8d551c 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///workflows//badge.svg This Markdown example adds a status badge for a workflow with the name "Greet Everyone." The `OWNER` of the repository is the `actions` organization and the `REPOSITORY` name is `hello-world`. -``` +```markdown ![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ This Markdown example adds a status badge for a workflow with the name "Greet Ev This Markdown example adds a status badge for a workflow with the file path `.github/workflows/main.yml`. The `OWNER` of the repository is the `actions` organization and the `REPOSITORY` name is `hello-world`. -``` +```markdown ![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ This Markdown example adds a status badge for a workflow with the file path `.gi This Markdown example adds a status badge for a branch with the name `feature-1`. -``` +```markdown ![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ This Markdown example adds a status badge for a branch with the name `feature-1` This Markdown example adds a badge that displays the status of workflow runs triggered by the `pull_request` event. -``` +```markdown ![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 081baff4a2..9fd8b65408 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -18,7 +18,7 @@ To run a workflow manually, the workflow must be configured to run on the `workf To trigger the `workflow_dispatch` event on {% data variables.product.prodname_dotcom %}, your workflow must be in the default branch. Follow these steps to manually trigger a workflow run. -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ko-KR/content/actions/quickstart.md b/translations/ko-KR/content/actions/quickstart.md index 362146f7e6..3c49ebe45d 100644 --- a/translations/ko-KR/content/actions/quickstart.md +++ b/translations/ko-KR/content/actions/quickstart.md @@ -7,6 +7,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 2d3f94f479..f8b7756ad4 100644 --- a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -186,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -348,7 +348,7 @@ The value for `array` can be an array or a string. All values in `array` are con `join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted' -#### toJson +#### toJSON `toJSON(value)` @@ -358,13 +358,13 @@ Returns a pretty-print JSON representation of `value`. You can use this function `toJSON(job)` might return `{ "status": "Success" }` -#### fromJson +#### fromJSON `fromJSON(value)` -Returns a JSON object for `value`. You can use this function to provide a JSON object as an evaluated expression. +Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string. -##### 예시 +##### Example returning a JSON object This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`. @@ -384,12 +384,33 @@ jobs: needs: job1 runs-on: ubuntu-latest strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} steps: - run: build ``` {% endraw %} +##### Example returning a JSON data type + +This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer. + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... +``` +{% endraw %} + #### hashFiles `hashFiles(path)` diff --git a/translations/ko-KR/content/actions/reference/environment-variables.md b/translations/ko-KR/content/actions/reference/environment-variables.md index 06df24a886..f9fd467c6a 100644 --- a/translations/ko-KR/content/actions/reference/environment-variables.md +++ b/translations/ko-KR/content/actions/reference/environment-variables.md @@ -21,15 +21,25 @@ versions: 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)." ```yaml -steps: - - name: Hello world - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +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. + +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 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV` environment file{% else %} `set-env` workflow command{% endif %} to set an environment variable that the following steps in a workflow can use. The {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}environment file{% else %} `set-env` command{% endif %} 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)." ### Default environment variables diff --git a/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md index 8056b1f8ae..0ce58d7995 100644 --- a/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md @@ -257,7 +257,7 @@ During the execution of a workflow, the runner generates temporary files that ca **Warning:** 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 ``` @@ -272,11 +272,19 @@ Creates or updates an environment variable for any actions running next in a job #### 예시 -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` - -Running `$action_state` in a future step will now return `yellow` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} #### Multiline strings @@ -291,7 +299,7 @@ For multiline strings, you may use a delimiter with the following syntax. ##### 예시 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 id: step_one diff --git a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md index 4f92ed5fd6..805d37d9ba 100644 --- a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ The name of your workflow. {% data variables.product.prodname_dotcom %} displays ### `on` -**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)." +**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 %} @@ -286,7 +286,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al ### `jobs..runs-on` -**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. +**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. {% data reusables.actions.enterprise-github-hosted-runners %} @@ -299,6 +299,7 @@ Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} ##### 예시 @@ -518,7 +519,7 @@ Actions are either JavaScript files or Docker containers. If the action you're u ```yaml steps: # Reference a specific commit - - uses: actions/setup-node@74bc508 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e # Reference the major version of a release - uses: actions/setup-node@v1 # Reference a minor version of a release @@ -700,12 +701,24 @@ steps: 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}`. +예시: + +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +The command used, `perl` in this example, must be installed on the runner. 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)." + #### Exit codes and error action preference 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`: - - Fail-fast behavior using `set -e o pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms. + - 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. @@ -1186,7 +1199,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.
    `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 tags with major version 1 or 2 | `v1.10.1`

    `v2.0.0` | +| `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` | #### Patterns to match file paths diff --git a/translations/ko-KR/content/admin/configuration/command-line-utilities.md b/translations/ko-KR/content/admin/configuration/command-line-utilities.md index 088c3ab5c4..14308e3ee5 100644 --- a/translations/ko-KR/content/admin/configuration/command-line-utilities.md +++ b/translations/ko-KR/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` Allows you to find the uuid of your node in `cluster.conf`. -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -545,8 +545,8 @@ ghe-dpages status ``` To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node: -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -571,16 +571,16 @@ ghe-spokes route To evacuate storage services on a cluster node: -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage This utility allows you to evacuate all storage services before evacuating a cluster node. -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md b/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md index 03d990e4b9..53849b5f1e 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ For more information about contacting support, see "[About {% data variables.con - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server. - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails. - {% note %} - - **Note:** If you select the **Send from author** checkbox in a repository’s **Services** email webhook, outbound email for that repository will send from the author and not from the no-reply email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)." - - {% endnote %} - 6. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. ![Checkbox to discard emails addressed to the no-reply email address](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. Under **Support**, choose a type of link to offer additional support to your users: - **Email:** An internal email address. @@ -155,7 +149,7 @@ You'll notice that `metroplex` catches the inbound message, processes it, then m #### Verify your DNS settings -In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incom emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." +In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." #### Check firewall or AWS Security Group settings diff --git a/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index e244198a38..ac6796fac0 100644 --- a/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -10,7 +10,7 @@ versions: ### About high availability replication for clusters -You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests without data loss. +You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage. In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests. diff --git a/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md index 7868b4b8b1..c429e92707 100644 --- a/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ If you're taking a node offline that has any data services (like git, pages, or ghe-spokes evac-status ``` For {% data variables.product.prodname_pages %} + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} For storage ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ If you're taking a node offline that has any data services (like git, pages, or 3. After the copying is complete, you can evacuate the storage service. Run any of the following commands: For Git + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} For {% data variables.product.prodname_pages %} + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} For storage, take the node offline + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} then evacuate + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md b/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md index 0fdc22d211..3cb2e45ce2 100644 --- a/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ The names of the nodes can be any valid hostname you choose. The names are set a Specify the first cluster node you configured as the MySQL primary via `mysql-server` and `mysql-master`. -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md index 1825fd3273..2ed0b83607 100644 --- a/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md @@ -123,7 +123,6 @@ When you contact {% data variables.contact.enterprise_support %}, you can choose ### 더 읽을거리 {% if enterpriseServerVersions contains currentVersion %} -- [Frequently asked questions about {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) - 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)"{% if enterpriseServerVersions contains currentVersion %} - "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} diff --git a/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index f144427890..74b4c02298 100644 --- a/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -63,7 +63,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac * 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 on your enterprise instance, 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/docker-build-push-action@v1 ``` diff --git a/translations/ko-KR/content/admin/overview/about-github-ae.md b/translations/ko-KR/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..d2656304e5 --- /dev/null +++ b/translations/ko-KR/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: About GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} is the most secure and compliant way to use {% data variables.product.prodname_dotcom %}.' +versions: + github-ae: '*' +--- + +### About {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase developer velocity, automate entire workflows, secure your code, and collaborate in developers’ favorite tool. + +{% data variables.product.prodname_ghe_managed %} provides your organization with all the power of [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). With {% data variables.product.prodname_ghe_managed %}, you can also meet security and compliance goals with a suite of features and certifications that put you in control. + +### A highly available and planet-scale cloud + +{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. + +### Data residency + +All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region. + +### Encryption on your terms + +All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." + +### Isolated accounts + +All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." + +### Restricted network access + +Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." + +### Commercial and government environments + +{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization. + +### Premium Plus support + +Premium Plus support is available for all {% data variables.product.prodname_ghe_managed %} customers, to ensure you have the fastest and most personal support experience. A dedicated Account Manager will work with you to help you get the most out of {% data variables.product.prodname_dotcom %}. Our support team will resolve issues any time of day, in the shortest possible time. + +### About billing for {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.about-billing %} For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." \ No newline at end of file diff --git a/translations/ko-KR/content/admin/overview/index.md b/translations/ko-KR/content/admin/overview/index.md index 34dad300ca..fe21d32dfb 100644 --- a/translations/ko-KR/content/admin/overview/index.md +++ b/translations/ko-KR/content/admin/overview/index.md @@ -12,6 +12,7 @@ For more information, or to purchase {% data variables.product.prodname_enterpri ### Table of Contents +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} diff --git a/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md b/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md index 078a1b54ae..29653e4111 100644 --- a/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ If you'd like to renew or add user licenses to {% data variables.product.prodnam {% data reusables.enterprise-accounts.license-tab %} 12. Under "Quick links", click **Update license**. ![Update license link](/assets/images/enterprise/business-accounts/update-license-link.png) 13. To select your license, click **License file**, or drag your license file onto **License file**. ![Upload license file](/assets/images/enterprise/management-console/upload-license.png) -14. Click **Upload**. ![Begin upgrade](/assets/images/enterprise/management-console/begin-upload.png) +14. Click **Upload**. ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %} ### Viewing license usage @@ -70,3 +72,23 @@ You can download a JSON file from {% data variables.product.prodname_ghe_server {% data reusables.enterprise-accounts.license-tab %} 10. Under "Enterprise Server Instances", click **Add server usage**. ![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. Upload the JSON file you downloaded from {% data variables.product.prodname_ghe_server %}. ![Drag and drop or select a file to upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### 문제 해결 + +In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Restart the services for Git authentication and the HTTP server. + + {% warning %} + + **Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again. + +{% endif %} diff --git a/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md index 947b9c7191..07fa5ced25 100644 --- a/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -58,7 +58,8 @@ Outside of the values that are provided to `stdin`, there are additional variabl | $GITHUB_VIA | Method used to create the ref.
    **Possible values:**
    - `auto-merge deployment api`
    - `blob edit`
    - `branch merge api`
    - `branches page delete button`
    - `git refs create api`
    - `git refs delete api`
    - `git refs update api`
    - `merge api`
    - `pull request branch delete button`
    - `pull request branch undo button`
    - `pull request merge api`
    - `pull request merge button`
    - `pull request revert button`
    - `releases delete button`
    - `stafftools branch restore`
    - `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | The number of push options that were sent by the client. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. | | $GIT_PUSH_OPTION_N | Where N is an integer starting at 0, this variable contains the push option string that was sent by the client. The first option that was sent is stored in GIT_PUSH_OPTION_0, the second option that was sent is stored in GIT_PUSH_OPTION_1, and so on. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. |{% endif %} +| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. +{% endif %} ### Setting permissions and pushing a pre-receive hook to {% data variables.product.prodname_ghe_server %} @@ -93,30 +94,30 @@ You can test a pre-receive hook script locally before you create or update it on 2. Create a file called `Dockerfile.dev` containing: - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository: + 3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository: - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 diff --git a/translations/ko-KR/content/admin/user-management/audited-actions.md b/translations/ko-KR/content/admin/user-management/audited-actions.md index ad5dd28b4c..1b980266d2 100644 --- a/translations/ko-KR/content/admin/user-management/audited-actions.md +++ b/translations/ko-KR/content/admin/user-management/audited-actions.md @@ -80,7 +80,7 @@ versions: | 이름 | 설명 | | ------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | -| `repo.archive` | 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.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. | @@ -89,7 +89,7 @@ versions: | `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.unarchive` | 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)."{% if enterpriseServerVersions contains currentVersion %} +| `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)."{% if enterpriseServerVersions contains currentVersion %} | `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)." | diff --git a/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md index 5c0b3333d2..ad2e649028 100644 --- a/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,11 +33,11 @@ If you don't have private mode enabled, the migration script will have no effect 1. Connect to the administrative shell. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)." 2. Navigate to the `/data/github/current` directory. - ``` + ```shell cd /data/github/current ``` 3. Run the migration command. - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` diff --git a/translations/ko-KR/content/admin/user-management/viewing-push-logs.md b/translations/ko-KR/content/admin/user-management/viewing-push-logs.md index 0b1a5270f2..b7c0a9041d 100644 --- a/translations/ko-KR/content/admin/user-management/viewing-push-logs.md +++ b/translations/ko-KR/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ Push log entries show: ### Viewing a repository's push logs +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. 1. Navigate to a repository. -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. In the upper-right corner of the repository's page, click +{% octicon "rocket" aria-label="The rocket ship" %}. + ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. In the left sidebar, click **Push Log**. ![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### Viewing a repository's push logs on the command-line -1. SSH into your appliance. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -2. In the appropriate Git repository, open the audit log file: +{% data reusables.enterprise_installation.ssh-into-instance %} +1. In the appropriate Git repository, open the audit log file: ```shell ghe-repo owner/repository -c "less audit_log" ``` diff --git a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 992a23ba0d..6e8a51401d 100644 --- a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ versions: ![Viewing a tag in the history](/assets/images/help/desktop/viewing-tags-in-history.png) 3. All tags associated with the commit are visible in that commit's metadata. ![Viewing a tag in the commit](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### Deleting tags + +{% note %} + +**Note**: You can only delete tags associated with commits that have not yet been pushed. + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md index fa38169b67..0e773f4a66 100644 --- a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -80,7 +80,7 @@ The `hook_attributes` object has the following key: This example uses a form on a web page with a button that triggers the `POST` request for a user account: -``` +```html Create a GitHub App Manifest:
    @@ -111,7 +111,7 @@ This example uses a form on a web page with a button that triggers the `POST` re ``` This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. -``` +```html Create a GitHub App Manifest:
    diff --git a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 21b9026777..6ff6a696c2 100644 --- a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -435,7 +435,7 @@ The code above gets the full repository name and the head SHA of the commit from ### Step 2.3. Running RuboCop -Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). +Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) for details and an example of the JSON format. +The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. Because this code stores the RuboCop results in a `@report` variable, it can safely remove the checkout of the repository. This code also parses the JSON so you can easily access the keys and values in your GitHub App using the `@output` variable. @@ -588,7 +588,7 @@ This code limits the total number of annotations to 50. But you can modify this When the `offense_count` is zero, the CI test is a `success`. If there are errors, this code sets the conclusion to `neutral` in order to prevent strictly enforcing errors from code linters. But you can change the conclusion to `failure` if you would like to ensure that the check suite fails when there are linting errors. -When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. +When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. This code also iterates through each error in the `offenses` array and collects the location of the offense and error message. After extracting the information needed, the code creates an annotation for each error and stores it in the `annotations` array. Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same. @@ -718,13 +718,13 @@ If the annotations are related to a file already included in the PR, the annotat If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button. -The RuboCop tool [offers](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. +The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set. In order to commit files, Git must know which [username](/articles/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. 예시: -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 06d02a63f0..2458b990bf 100644 --- a/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ An _authorized_ OAuth App has access to all of the user's or organization owner' | Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. | | Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |{% endif %} +| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. +{% endif %} ### Requesting permission levels for resources diff --git a/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index a72e7f2d98..380366453a 100644 --- a/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -89,7 +89,7 @@ Expiring user tokens are currently part of the user-to-server token expiration b 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 the beta for expiring user-to-server access tokens. -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", diff --git a/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md b/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md index 697d461954..3490956362 100644 --- a/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ To learn about publishing {% data variables.product.prodname_actions %} in {% da ### 앱 -Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." +Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. + +To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments. + +To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)." + +#### New to apps? If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." +#### GitHub Apps vs. OAuth Apps + {% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." -If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. - -### Publishing an app to {% data variables.product.prodname_marketplace %} +### Publishing an app to {% data variables.product.prodname_marketplace %} overview When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: @@ -38,13 +46,9 @@ When you have finished creating your app, you can share it with other users by p 1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." - 1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." - -An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." ### Seeing how your app is performing @@ -52,3 +56,7 @@ You can access metrics and transactions for your listing. For more information, - "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" - "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" + +### Contacting Support + +If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. diff --git a/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md b/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..b02ef692eb --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: About marketplace badges +intro: 'Learn about the badges that you may see for some apps and actions listings on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### For GitHub Apps + +Apps with the {% octicon "verified" aria-label="The verified badge" %}, are owned by an organization that has: +- Confirmed their domain +- Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization +- Required two-factor authentication for their organization. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + +![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +To learn how you can add this badge to your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### For GitHub actions + +Actions with the {% octicon "verified" aria-label="The verified badge" %}, or verified creator badge, indicate that {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization. + +![Verified creator badge for GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +For information on how to publish a GitHub action to {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." + +### About the previous verification process for apps + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**Note:** The new publisher verification process for apps replaces the previous process where individual apps were verified. The new publisher verification process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..1230712703 --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Applying for publisher verification for your organization +intro: 'To offer paid plans for your app or to include a marketplace badge in your app listing, you must complete the publisher verification process for your organization.' +versions: + free-pro-team: '*' +--- + +Publisher verification ensures that {% data variables.product.prodname_dotcom %} has a way to contact you, that you've enabled two-factor authentication for your organization, and that your organization's domain has been verified. + +Once your organization has been verified, you can publish paid plans for your app. For information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)." + +### Requesting publisher verification + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. In the left sidebar, click **Developer settings**. ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) +1. Under "Publisher Verification", complete the information in the checklist: + - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. + - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + - Submit a verified domain. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + + ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) + +1. Click **Request Verification**. {% data variables.product.company_short %} will review your details and let you know once your publisher verification is complete. + +### 더 읽을거리 + +For information about the process of publishing apps, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)." diff --git a/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 52c2c64dc9..033802f582 100644 --- a/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ Once you've created a {% data variables.product.prodname_marketplace %} draft li ### Submitting your app -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. ### Removing a {% data variables.product.prodname_marketplace %} listing diff --git a/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview.md b/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..5b8799f9d9 --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,8 @@ +--- +title: GitHub Marketplace Overview +intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/developers/github-marketplace/index.md b/translations/ko-KR/content/developers/github-marketplace/index.md index e0fdf26b6e..678e3108bf 100644 --- a/translations/ko-KR/content/developers/github-marketplace/index.md +++ b/translations/ko-KR/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md index aed7c5d235..4bcccd4e00 100644 --- a/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ To protect your customers, we recommend that you also follow security best pract ### Requirements for paid apps -In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transfering ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: - {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. - {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. - All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. -- Publishing organizations must have a verified domain and must enable two-factor authentication. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." -When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} diff --git a/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 9ab919817d..52f91dd1ab 100644 --- a/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,11 +19,13 @@ versions: ### About setting pricing plans -If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." -{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." +To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." +If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. + +![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png) ### About saving pricing plans diff --git a/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md index b25c4580ae..6b338d826b 100644 --- a/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: Submitting your listing for publication -intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +intro: 'To finish your app listing submission, you can request a review by an onboarding expert.' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +Once your app listing meets the {% data variables.product.prodname_marketplace %} requirements, you can submit your app. For an overview of the app listing requirements, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +1. In the top left of the app listing page, click **Overview**. For information on finding your app listing page, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + ![Overview option for the marketplace draft listing](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) +2. To submit your your completed app listing, click **Request review**. -{% data reusables.marketplace.launch-with-free %} + !["Publish your app to Marketplace" checklist with submission button at the bottom](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -After you submit your listing for review, an onboarding expert will reach out to you with additional information. - -For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." - -### Prerequisites for publishing with verification - -Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." - -If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. - -### Transferring an app to an organization before you submit - -You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: - -1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" - -1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" +An onboarding expert will reach out to you with additional information. diff --git a/translations/ko-KR/content/developers/overview/secret-scanning.md b/translations/ko-KR/content/developers/overview/secret-scanning.md index bf0a60000a..e34d1eaca0 100644 --- a/translations/ko-KR/content/developers/overview/secret-scanning.md +++ b/translations/ko-KR/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: Secret scanning intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. Secret scanning happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our secret scanning. +{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}. When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice. -When a match of your secret format is found in a private repository configured for secret scanning, then repository admins are alerted and can view and manage the secret scanning results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from secret scanning](/github/administering-a-repository/managing-alerts-from-secret-scanning)". +When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." {% note %} -**Note:** Secret scanning for private repositories is currently in beta. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. {% endnote %} -This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the secret scanning program. +This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. -### The secret scanning process +### The {% data variables.product.prodname_secret_scanning %} process -##### How secret scanning works in a public repository +##### How {% data variables.product.prodname_secret_scanning %} works in a public repository -The following diagram summarizes the secret scanning process for public repositories, with any matches sent to a service provider's verify endpoint. +The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint. -![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "Secret scanning flow") +![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow") -### Joining the secret scanning program on {% data variables.product.prodname_dotcom %} +### Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %} 1. Contact {% data variables.product.prodname_dotcom %} to get the process started. 1. Identify the relevant secrets you want to scan for and create regular expressions to capture them. -1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the secret scanning message payload. +1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the {% data variables.product.prodname_secret_scanning %} message payload. 1. Implement signature verification in your secret alert service. 1. Implement secret revocation and user notification in your secret alert service. +1. Provide feedback for false positives (optional). #### Contact {% data variables.product.prodname_dotcom %} to get the process started -To get the enrollment process started, email secret-scanning@github.com. +To get the enrollment process started, email secret-scanning@github.com. -You will receive details on the secret scanning program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. +You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. #### Identify your secrets and create regular expressions -To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the secret scanning program: +To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program: * A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later. * A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives. * The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type. -Send this information to secret-scanning@github.com. +Send this information to secret-scanning@github.com. #### Create a secret alert service @@ -61,7 +62,7 @@ Create a public, internet accessible HTTP endpoint at the URL you provided to us ##### Example POST sent to your endpoint -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ You can retrieve the {% data variables.product.prodname_dotcom %} secret scannin Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set. **Sample message sent to verify endpoint** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -278,4 +279,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### Implement secret revocation and user notification in your secret alert service -For secret scanning in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. +For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. + +#### Provide feedback for false positives + +We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at secret-scanning@github.com. + +When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats. + +You can send us the raw token: + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256: + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +A few important points: +- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both. +- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm. +- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed. + +{% note %} + +**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at secret-scanning@github.com. + +{% endnote %} + diff --git a/translations/ko-KR/content/discussions/index.md b/translations/ko-KR/content/discussions/index.md index 66dca4f270..429f32ddbd 100644 --- a/translations/ko-KR/content/discussions/index.md +++ b/translations/ko-KR/content/discussions/index.md @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -43,7 +43,7 @@ versions: {% render 'discussions-community-card' for discussionsCommunityExamples as example %} {% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
    {% octicon "search" width="24" %}
    diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..72f6d0950d --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +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 + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +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 %} + +**Note:** As an instructor, you can't create {% data variables.product.prodname_dotcom %} accounts for your students. Students must create their own {% data variables.product.prodname_dotcom %} accounts. + +{% endnote %} diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..1dad791c70 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: About Campus Experts +intro: 'As a student, learn the skills you need to build your school''s technology community and a real-world portfolio, with {% data variables.product.prodname_dotcom %} Campus Experts training.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +Learn public speaking skills, technical writing, community leadership, and software development skills as a {% data variables.product.prodname_dotcom %} Campus Expert. For more information, see "[Campus Experts](https://education.github.com/students/experts)." diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..cea92845f0 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: About GitHub Education for educators and researchers +intro: '{% data variables.product.prodname_education %} offers a variety of tools to help educators and researchers work more effectively inside and outside of the classroom.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} for educators + +With {% data variables.product.prodname_education %}'s tools and services for educators of all levels, you can: + - Use [{% data variables.product.prodname_classroom %}](https://classroom.github.com) to distribute code, give students feedback, and collect assignments on {% data variables.product.prodname_dotcom %}. + - Join our [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) to discuss current trends in technology education with your peers from around the world. + - Access and adapt our [open source lesson plans](https://education.github.community/t/open-source-lesson-plans/1591) for teaching Git and {% data variables.product.prodname_dotcom %}. + - [Request a {% data variables.product.prodname_dotcom %} swag bag](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) with educational materials and goodies for your students. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} for researchers + +With {% data variables.product.prodname_education %}'s tools and services for researchers, you can: + - Collaborate with others on your research work around the world on {% data variables.product.prodname_dotcom %}. + - [Learn](https://education.github.com/stories) how academic institutions around the world are using {% data variables.product.prodname_dotcom %} for their research. + {% data reusables.education.apply-for-team %} + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_education %} for students](/articles/about-github-education-for-students)" diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..49f4726742 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: About GitHub Education for students +intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience. + +{% data reusables.education.about-github-education-link %} + +Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for the {% data variables.product.prodname_student_pack %}, which offers free access to tools and services used by professional developers. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +If you're a member of a FIRST robotics club, your mentor can apply for an educator discount so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[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)." + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_education %} for educators and researchers](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..c3a05c2f23 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Education +intro: '{% data variables.product.prodname_education %} offers a special free product for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community and agree to specific program requirements.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +If your school agrees to meet certain requirements, your secondary school, university, or bootcamp can get {% data variables.product.prodname_education %}, which offers the best of {% data variables.product.prodname_dotcom %} for free, including: +- {% data variables.product.prodname_ghe_cloud %} and/or {% data variables.product.prodname_ghe_server %} +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} +- Leadership development and technical training for students with the Campus Experts program + +For more information, see the [official {% data variables.product.prodname_education %}](https://education.github.com/partners/schools) page. + +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)." + +To learn more about training programs for student leaders and teachers, see "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" and "[Campus Advisors](https://education.github.com/teachers/advisors)." + +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_education %} 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/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[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/)." diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..0194b029cb --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: Apply for a student developer pack +intro: 'As a student, you can apply for the {% data variables.product.prodname_student_pack %}, which includes offers and benefits from {% data variables.product.prodname_dotcom %} partners.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 요구 사항 + +To be eligible for the {% data variables.product.prodname_student_pack %}, you must: +- Be currently enrolled in a degree or diploma granting course of study such as a high school, secondary school, college, university, homeschool, or similar educational institution +- Have a verifiable school-issued email address or upload documents that prove your current student status +- Have a [{% data variables.product.prodname_dotcom %} user account](/articles/signing-up-for-a-new-github-account) +- Be at least 13 years old + +Documents that prove your current student status include a picture of your school ID with current enrollment date, class schedule, transcript, and affiliation or enrollment verification letter. + +During your tenure as a student, you may be prompted to periodically re-verify your current academic status. + +{% note %} + +**Note:** You cannot transfer academic discounts from one account to another. If you have more than one account you want to apply the discount to, consider [merging](/articles/merging-multiple-user-accounts) your user accounts and [renaming](/articles/changing-your-github-username) the retained account if desired. + +{% endnote %} + +For information about renewing your {% data variables.product.prodname_student_pack %}, see "[Expiration and renewals](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)." + +### Applying for a {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. Under "Which best describes your academic status?", select **Student**. ![Select academic status](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Expiration and renewals + +Once your {% data variables.product.prodname_student_pack %} access expires, you may reapply if you're still eligible, although some of our partner offers cannot renew. Most of the timed offers from our partners start once you set them up. For more information, see the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) page. + +To see when your free access to the {% data variables.product.prodname_student_pack %} expires, visit your account's [billing settings](https://github.com/settings/billing). + +### 더 읽을거리 + +- "[Why wasn't my application for a {% data variables.product.prodname_student_pack %} approved?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..692349edd1 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: Apply for an educator or researcher discount +intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### About educator and researcher discounts + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Applying for an educator or researcher discount + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Upgrading your organization + +After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade. + +#### Upgrading an existing organization + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Upgrading a new organization + +{% data reusables.education.upgrade-page %} +1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**. ![Create an organization button](/assets/images/help/education/create-org-button.png) +3. Read the information, then click **Create organization**. ![Create organization button](/assets/images/help/education/create-organization-button.png) +4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**. +5. Follow the prompts to create your organization. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### 더 읽을거리 + +- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..9dda1a2a4f --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Explore +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Table of Contents + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..c532b9a6e6 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub at your educational institution +intro: 'Maximize the benefits of using {% data variables.product.prodname_dotcom %} at your institution for your students, instructors, and IT staff with {% data variables.product.prodname_education %} and our various training programs for students and instructors.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..8512b9b548 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub for your schoolwork +intro: 'As a student, use {% data variables.product.prodname_dotcom %} to collaborate on your school projects and build real-world experience.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..3dc25db887 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub in your classroom and research +intro: 'As an educator or researcher, use {% data variables.product.prodname_dotcom %} to collaborate on your work in a classroom, student or research group, and more.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..02e96c9468 --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +title: Why wasn't my application for a student developer pack approved? +intro: 'Review common reasons that applications for the {% data variables.product.prodname_student_pack %} are not approved and learn tips for reapplying successfully.' +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear academic affiliation documents + +If the image you uploaded doesn't clearly identify your current academic status, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If your school issues email addresses prior to paid student enrollment, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain please ask your school IT staff to contact us. + +### Academic email address already used + +If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %} until that discount expires. + +{% note %} + +**Note:** It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/articles/github-terms-of-service/#3-account-requirements) to maintain more than one individual account. + +{% endnote %} + +If you have more than one personal user account, you must merge your accounts. To retain the discount, keep the account that was granted the discount. You can rename the retained account and keep your contribution history by adding all your email addresses to the retained account. + +For more information, see: +- "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)" +- "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)" +- "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account)" + +### Ineligible student status + +You're ineligible for a {% data variables.product.prodname_student_pack %} if: +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- You're under 13 years old. + +Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools). + +### 더 읽을거리 + +- "[How to get the GitHub Student Developer Pack without a student ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/)" on {% data variables.product.prodname_blog %} +- "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..9f91adf44f --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: Why wasn't my application for an educator or researcher discount approved? +intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully. +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear proof of affiliation documents + +If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information. + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain, please ask your school IT staff to contact us. + +### Non-student applying for Student Developer Pack + +Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status. + +### 더 읽을거리 + +- "[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)" diff --git a/translations/ko-KR/content/education/guides.md b/translations/ko-KR/content/education/guides.md index 0265b53633..50b347ee8e 100644 --- a/translations/ko-KR/content/education/guides.md +++ b/translations/ko-KR/content/education/guides.md @@ -12,8 +12,8 @@ Teachers, students, and researchers can use tools from {% data variables.product - [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) -- [Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) +- [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) ### Run a software development course with {% data variables.product.company_short %} @@ -32,7 +32,7 @@ Administer a classroom, assign and review work from your students, and teach the Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. - [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/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [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) @@ -41,5 +41,5 @@ Incorporate {% data variables.product.prodname_dotcom %} into your education, an 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) -- [About Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) -- [About Campus Advisors](/education/teach-and-learn-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/ko-KR/content/education/index.md b/translations/ko-KR/content/education/index.md index c3827df288..782c20b772 100644 --- a/translations/ko-KR/content/education/index.md +++ b/translations/ko-KR/content/education/index.md @@ -6,16 +6,16 @@ introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom @@ -41,5 +41,5 @@ versions: free-pro-team: '*' --- - + diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 26a082d449..58ce85cbc7 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ For more information about teaching with {% data variables.product.prodname_clas ### 더 읽을거리 -- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" +- "[Explore the benefits of teaching and learning with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 50361dd2e8..db4e5d990b 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -140,6 +140,6 @@ You can see the teams that are working on or have submitted an assignment in the ### 더 읽을거리 -- "[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)" +- "[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/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index 65a51556da..141fa6ac17 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,8 +11,6 @@ You can use a template repository on {% data variables.product.product_name %} a To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." - ### 더 읽을거리 - "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index 0dc4885527..3986429219 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -120,5 +120,5 @@ You can see whether a student has joined the classroom and accepted or submitted ### 더 읽을거리 -- "[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)" +- "[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/ko-KR/content/education/manage-coursework-with-github-classroom/index.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/index.md index f5a8689fa7..7b1446bd31 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 6e051e9d2d..e5dbcf02c1 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -4,5 +4,8 @@ intro: Learn how to set up your classroom and assignments. mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/ko-KR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index aad50f336b..0c1bf6c483 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -33,8 +33,8 @@ You can filter email notifications you receive for pushes to a repository. For m {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address. ![Email address textbox](/assets/images/help/settings/email_services_addresses.png) -6. If you operate your own server, you can verify the integrity of emails via the **Secret** token. This token is sent with the email as the `Approved` header. If the `Approved` header matches the token you sent, you can trust that the email is from {% data variables.product.product_name %}. ![Email secret textbox](/assets/images/help/settings/email_services_token.png) -7. Click **Save settings**. ![Save settings button](/assets/images/help/settings/save_notification_settings.png) +1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}. ![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png) +7. Click **Setup notifications**. ![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png) ### 더 읽을거리 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} diff --git a/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md index bde7a18dd0..0cede754f9 100644 --- a/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,7 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." diff --git a/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md b/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md index 0748625b6b..8dcd7efdd5 100644 --- a/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md @@ -4,6 +4,7 @@ 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: free-pro-team: '*' + enterprise-server: '>=3.1' --- ### About renaming branches @@ -19,3 +20,15 @@ If you rename a branch, {% data variables.product.prodname_dotcom %} will automa 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) + +### Updating a local clone after a branch name changes + +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. + +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 +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index e0ce88912c..e76ab35527 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: About authentication with SAML single sign-on -intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' +intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on @@ -9,6 +9,8 @@ versions: github-ae: '*' --- +### About authentication with SAML SSO + {% if currentVersion == "github-ae@latest" %} SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. @@ -31,13 +33,17 @@ If you have recently authenticated with your organization's SAML IdP in your bro {% data reusables.saml.you-must-periodically-authenticate %} -To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default. +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}. +### About {% data variables.product.prodname_oauth_apps %} and SAML SSO + +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO. + +After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). {% endif %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 2e1120963c..311f3df601 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ This article tells you how to make commits with sensitive data unreachable from #### Using the BFG -The [BFG Repo-Cleaner](http://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. For example, to remove your file with sensitive data and leave your latest commit untouched, run: +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. 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 @@ -46,7 +46,7 @@ After the sensitive data is removed, you must force push your changes to {% data $ git push --force ``` -See the [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. +See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. #### Using filter-branch diff --git a/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index 9f9cc4bb25..c3774f1894 100644 --- a/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ When you block a user, you can choose to block them indefinitely or for a specif {% tip %} -**Tip:** If you're blocking a user because of a heated conversation, consider [locking the conversation](/articles/locking-conversations) so only collaborators can comment. +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/github/building-a-strong-community/locking-conversations)." {% endtip %} At the time that you block a user from your organization: - The user stops watching your organization's repositories - The user's stars and issue assignments are removed from your repositories -- The user's forks of your organization's repositories are deleted - The user's votes on discussions or comments in your organization's repositories are deleted - The user is removed as a collaborator on your organization's repositories - The user's contributions to your organization's repositories are no longer counted as contributions for them diff --git a/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 16e34b7c00..c913e13463 100644 --- a/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/ko-KR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### About blocking users -You can block a user in your account settings or from the user's profile. {% data variables.product.prodname_dotcom %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can [choose to display a warning](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings) on any repositories with prior contributions from a blocked user. You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content. +You can block a user in your account settings or from the user's profile. {% data variables.product.prodname_dotcom %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see "[Blocking a user in your account settings](#blocking-a-user-in-your-account-settings)." You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content. {% tip %} -**Tip:** If you're blocking a user because of a heated conversation, consider [locking the conversation](/articles/locking-conversations) so only collaborators can comment. +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/github/building-a-strong-community/locking-conversations)." {% endtip %} @@ -22,8 +22,6 @@ When you block a user: - The user stops watching and unpins your repositories - The user is not able to join any organizations you are an owner of - The user's stars and issue assignments are removed from your repositories -- The user's forks of your repositories are deleted -- You delete any forks of the user's repositories - The user's votes on discussions or comments in your repositories are deleted - The user is removed as a collaborator on your repositories - The user's contributions to your repositories are no longer counted as contributions for them diff --git a/translations/ko-KR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/ko-KR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 40f359a88a..924da43feb 100644 --- a/translations/ko-KR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/ko-KR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ You can add YAML frontmatter to each issue template to pre-fill the issue title, Here is example YAML front matter. -``` +```yaml --- name: Tracking issue about: Use this template for tracking new features. diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index 9d54f108fa..99e6638709 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ For example, if you and another person both edited the file _styleguide.md_ on t 4. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts. 5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`. - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge: ```shell diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 85001ffa31..5b78492e23 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ Pre-receive hooks run tests on code pushed to a repository to ensure contributio If your push isn't accepted, you'll see an error message corresponding to the failed pre-receive hook. -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md index 0a907f0579..d937713a03 100644 --- a/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,7 +19,7 @@ You can discover, browse, and install apps and actions created by others on {% d {% data reusables.actions.actions-not-verified %} -Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Building and listing a tool on {% data variables.product.prodname_marketplace %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 35ca124ad3..543e1a6dc0 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ To integrate {% data variables.product.prodname_code_scanning %} into your CI sy In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -39,7 +39,7 @@ The {% data variables.product.prodname_codeql_runner %} automatically detects an To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are `cpp`, `csharp`, `go`, `java`, `javascript`, and `python`. -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -55,7 +55,7 @@ If you also are using a configuration file for custom settings, and you are also In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. -``` +```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 ``` @@ -68,7 +68,7 @@ The configuration file is a YAML file. It uses syntax similar to the workflow sy Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. -``` +```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml ``` @@ -84,7 +84,7 @@ For many common build systems, the {% data variables.product.prodname_codeql_run The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. -``` +```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 74dc2ffaf8..10c720382a 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ You can set up {% data variables.product.prodname_code_scanning %} to check the 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### About alerts details 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 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. diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index db74c3cd53..6ceca9cca4 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -93,6 +93,8 @@ You can configure where the {% data variables.product.prodname_codeql_runner %} To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Basic example This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 3a91315ff7..464bb26bf1 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -40,6 +40,8 @@ If you upload a SARIF file without fingerprint data using the `/code-scanning/sa You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### Supported SARIF output file properties If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}. @@ -82,6 +84,8 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr #### `result` object +{% data reusables.code-scanning.upload-sarif-alert-limit %} + | 이름 | 설명 | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | @@ -89,7 +93,7 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | | `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | | `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | -| `locations[]` | **Required.** The set of locations where the result was detected. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | | `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | | `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | | `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index cbf5073a9d..142db3c02b 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -39,6 +39,8 @@ The `upload-sarif` action can be configured to run when the `push` and `schedule If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Example workflow for SARIF files generated outside of a repository You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository. diff --git a/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md index b923b08a6c..bfffd2ff7e 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/ko-KR/content/github/getting-started-with-github/about-github-advanced-security.md @@ -10,7 +10,7 @@ versions: {% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." For information about permission requirements for actions related to security features, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." ### About {% data variables.product.prodname_advanced_security %} features diff --git a/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md index 656411ec03..2bc4bf741d 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ Familiarize yourself with Git by visiting the [official Git project site](https: {% endif %} -Become better acquainted with {% data variables.product.product_name %} through our [bootcamp](/categories/bootcamp/) 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. +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, forks, and pull requests -Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/articles/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 quick references about the [command line](https://hub.github.com) as well as {% data variables.product.prodname_dotcom %} [checklists, cheat sheets, and more](https://services.github.com/on-demand/resources). +Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/articles/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/). #### Tune in @@ -41,9 +39,9 @@ Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides ch ### 연습 -#### Free classes +#### Free courses -{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://services.github.com/on-demand/) including {% data variables.product.prodname_dotcom %} 101: [Introduction](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %} 102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop), and {% data variables.product.prodname_dotcom %} 103: [Command Line](https://services.github.com/on-demand/github-cli). +{% 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 %}. #### {% data variables.product.prodname_dotcom %}'s web-based educational programs diff --git a/translations/ko-KR/content/github/getting-started-with-github/git-cheatsheet.md b/translations/ko-KR/content/github/getting-started-with-github/git-cheatsheet.md index 38afdb9b1a..3be24decfb 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/ko-KR/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -Learning all available Git commands at once can be a daunting task. Keep one of our [Git Cheat Sheets](https://services.github.com/on-demand/resources/cheatsheets/) nearby for reference. The Using Git Cheat Sheet is available in several languages. For more information, see the [resources page on the GitHub Services website](https://services.github.com/on-demand/resources/). +Learning all available Git commands at once can be a daunting task. Our cheat sheets provide a quick reference for the commands you'll use most often: see "[Git Cheat Sheets](https://training.github.com/)." The "Using Git" cheat sheet is available in several languages. In addition, take a look at our [Git and GitHub learning resources](/articles/git-and-github-learning-resources/) page that links to guides, videos and more. diff --git a/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md b/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md index becafddba7..4f14fddd35 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md +++ b/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md @@ -85,6 +85,7 @@ In addition to the features available with {% data variables.product.prodname_te - {% data variables.contact.enterprise_support %}. For more information, see "{% data variables.product.prodname_ghe_cloud %} support" and "{% data variables.product.prodname_ghe_cloud %} Addendum." - 50,000 {% data variables.product.prodname_actions %} minutes - 50GB {% data variables.product.prodname_registry %} storage +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime - The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." diff --git a/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md index a4407409b5..ea135f2c58 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -76,7 +76,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | control shift p or command shift p | Toggles between the **Write** and **Preview** comment tabs | | 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)."{% if currentVersion == "free-pro-team@latest" %} -| control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} +| control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/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)." | ### Issue and pull request lists @@ -111,7 +112,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | 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**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| 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 %} +| 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 %} ### Project boards diff --git a/translations/ko-KR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/ko-KR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index afe5d37e13..1ccd75ae45 100644 --- a/translations/ko-KR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/ko-KR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,7 +45,7 @@ versions: 7. At the top of your {% data variables.product.product_name %} repository'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](/articles/adding-a-remote) where your local repository will be pushed. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -83,7 +83,7 @@ versions: 7. At the top of your {% data variables.product.product_name %} repository'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](/articles/adding-a-remote) where your local repository will be pushed. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -121,7 +121,7 @@ versions: 7. At the top of your {% data variables.product.product_name %} repository'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](/articles/adding-a-remote) where your local repository will be pushed. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md index 316807351b..1fc09d3f77 100644 --- a/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### About navigating code on {% data variables.product.prodname_dotcom %} -Navigating code functions use the open source library [`semantic`](https://github.com/github/semantic). The following languages are supported: +Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). The following languages are supported: - C# - CodeQL - Go diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 0c7b5fd960..e11f4f42b6 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -47,6 +47,8 @@ For a list of the ecosystems that {% data variables.product.product_name %} can 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." + {% 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 %} diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index cde211c79b..df86a582cf 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ When you publish a security advisory, you notify your community about the securi Before you publish a security advisory, you can privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a security vulnerability](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)." +{% warning %} + +**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to. + +We recommend you take the following steps in these different situations: + +- If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready. +- If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication. +- If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue. + +{% endwarning %} + When you publish a draft advisory from a public repository, everyone is able to see: - The current version of the advisory data. diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 1da15e38ce..71760a5643 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -133,7 +133,8 @@ Email notifications from {% data variables.product.product_name %} contain the f | `To` field | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
    • `assign`: You were assigned to an issue or pull request.
    • `author`: You created an issue or pull request.
    • `comment`: You commented on an issue or pull request.
    • `manual`: There was an update to an issue or pull request you manually subscribed to.
    • `mention`: You were mentioned on an issue or pull request.
    • `push`: Someone committed to a pull request you're subscribed to.
    • `review_requested`: You or a team you're a member of was requested to review a pull request.
      • {% if currentVersion != "github-ae@latest" %}
    • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
      • {% endif %}
    • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
    • `subscribed`: There was an update in a repository you're watching.
    • `team_mention`: A team you belong to was mentioned on an issue or pull request.
    • `your_activity`: You opened, commented on, or closed an issue or pull request.
    | | `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} +| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} ### Choosing your notification settings diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/ko-KR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 089cd7a04e..340185682c 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: To transfer an open issue to another repository, you must have write permissions on the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." -You can only transfer issues between repositories owned by the same user or organization account.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} +You can only transfer issues between repositories owned by the same user or organization account. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)." diff --git a/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index 84be25b024..7bbd792ed9 100644 --- a/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,7 +25,8 @@ Email notifications from {% data variables.product.product_name %} contain the f | `To` field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. | | `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
    • `assign`: You were assigned to an issue or pull request.
    • `author`: You created an issue or pull request.
    • `comment`: You commented on an issue or pull request.
    • `manual`: There was an update to an issue or pull request you manually subscribed to.
    • `mention`: You were mentioned on an issue or pull request.
    • `push`: Someone committed to a pull request you're subscribed to.
    • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive security alerts for.
    • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
    • `subscribed`: There was an update in a repository you're watching.
    • `team_mention`: A team you belong to was mentioned on an issue or pull request.
    • `your_activity`: You opened, commented on, or closed an issue or pull request.
    | | `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} +| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 058d316875..6eb5de6557 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ You can narrow your results to only include issues that are linked to a pull req | `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 %} +| `-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 %} ### Search by label diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index c79f7a32a3..f5f49c9920 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### Discounts for personal accounts -In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." +In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)." ### Discounts for schools and universities -Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[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)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/). +Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[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)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/). ### Discounts for nonprofits and libraries diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md index a3ee6b1216..a51df67c98 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..a4aae9bd5c --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses +{% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/unpublishing-a-github-pages-site)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Click **Save**. + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)" diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 49f490dad7..e285925085 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late {% if currentVersion == "free-pro-team@latest" %} -| Organization action | Owners | Members | Billing managers | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:-------:|:--------------------------------------------------:| -| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-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](/articles/about-your-organization-s-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 domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" 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** | | -| [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** | | -| See all organization members and teams | **X** | **X** | | -| @mention any visible team | **X** | **X** | | -| Can be made a *team maintainer* | **X** | **X** | | -| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | -| View and post public team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | **X** | | -| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | -| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/articles/managing-disruptive-comments)" for details) | **X** | | | -| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/managing-disruptive-comments/#hiding-a-comment)" for details) | **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** | | |{% if currentVersion == "free-pro-team@latest" %} -| 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** | | |{% endif %} -| 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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | -| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | -| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-teams/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** | | |{% if currentVersion != "github-ae@latest" %} -| 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** | | | -| 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** | | |{% endif %} -| [Manage the forking policy](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Limit activity in public repositories in an organization](/articles/limiting-interactions-in-your-organization) | **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 the default branch name (see "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" for details) | **X** | | | +| Organization action | Owners | Members | Billing managers | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:-------:|:----------------:| +| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-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](/articles/about-your-organization-s-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 domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" 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** | | +| [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** | | +| See all organization members and teams | **X** | **X** | | +| @mention any visible team | **X** | **X** | | +| Can be made a *team maintainer* | **X** | **X** | | +| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/articles/managing-disruptive-comments)" for details) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/managing-disruptive-comments/#hiding-a-comment)" for details) | **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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/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](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-teams/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** | | | +| 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** | | | +| [Manage the forking policy](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limit activity in public repositories in an organization](/articles/limiting-interactions-in-your-organization) | **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 the default branch name (see "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" for details) | **X** | | | {% else %} -| 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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Configure code review assignments (see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} -| Add collaborators to **all repositories** | **X** | | -| Access the organization audit log | **X** | | -| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" 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** | -| 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](/articles/about-team-discussions)" for details) | **X** | **X** | | -| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | -| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/articles/managing-disruptive-comments) | **X** | | | -| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/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** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configure code review assignments (see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Add collaborators to **all repositories** | **X** | | +| Access the organization audit log | **X** | | +| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" 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** | +| 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](/articles/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/articles/managing-disruptive-comments)) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/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** | | |{% if currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} {% endif %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 2a26e5b6d0..36b0f7cd4c 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: Repository permission levels for an organization intro: 'You can customize access to each repository in your organization with granular permission levels, giving people access to the features and tasks they need.' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,95 +43,124 @@ In addition to managing organization-level settings, organization owners have ad {% endwarning %} ### Repository access for each permission level +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} -| Repository action | Read | 심사 | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Edit wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Report abusive or spammy content](/articles/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** |{% if currentVersion == "free-pro-team@latest" %} -| [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](/articles/requesting-a-pull-request-review) | | **X** | **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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/articles/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](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [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** |{% if currentVersion == "free-pro-team@latest" %} -| Limit [interactions in a repository](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable the dependency graph](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) for a private repository | | | | | **X** | -| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** | -| [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** | -| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [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 %} -| [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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %} +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} +| +{% endif %} +| Repository action | Read | 심사 | Write | Maintain | Admin | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Edit wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Report abusive or spammy content](/articles/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** |{% if currentVersion == "free-pro-team@latest" %} +| [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](/articles/requesting-a-pull-request-review) | | **X** | **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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/articles/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](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [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** |{% if currentVersion == "free-pro-team@latest" %} +| Limit [interactions in a repository](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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** |{% if currentVersion == "free-pro-team@latest" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_advanced_security %} features. + +| Repository action | Read | 심사 | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** | +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [Enable the dependency graph](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) for a private repository | | | | | **X** | +| [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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** | +| [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 %} +{% endif %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index bc454f6548..5f605bc3b8 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -27,46 +27,46 @@ The audit log lists events triggered by activities that affect your organization 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 | 설명 | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| [`계정`](#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-category-actions) | Contains all activities related to your organization's billing. | -| [`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. | -| [`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)." | +| Category name | 설명 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`계정`](#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-category-actions) | Contains all activities related to your organization's billing. | +| [`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. | +| [`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. | -| [`후크`](#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. | -| [`이슈`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} -| [`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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-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. | +| [`후크`](#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. | +| [`이슈`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} +| [`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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} | [`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. |{% if currentVersion == "free-pro-team@latest" %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. |{% if currentVersion == "free-pro-team@latest" %} | [`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-category-actions) | Contains all activities related to project boards. | -| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. | +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | +| [`프로젝트`](#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.{% if currentVersion == "free-pro-team@latest" %} -| [`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_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 %}{% if currentVersion != "github-ae@latest" %} -| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | -| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | -| [`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)." |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | +| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | +| [`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)." |{% endif %}{% if currentVersion != "github-ae@latest" %} | [`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 %}{% if currentVersion == "free-pro-team@latest" %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [`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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [`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-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. | +| [`팀`](#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. 예시: @@ -128,7 +128,7 @@ To ensure a secure IP and maintain compliance for your organization, you can use {% data reusables.audit_log.audit-log-api-info %} {% if currentVersion == "free-pro-team@latest" %} -Note that you can't retrieve Git events using the GraphQL API. +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. @@ -141,7 +141,7 @@ For example, you can make a GraphQL request to see all the new organization memb {% note %} -**Note**: The audit log REST API is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. +**Note:** The audit log REST API is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. {% endnote %} @@ -250,7 +250,7 @@ An overview of some of the most common actions that are recorded as events in th {% note %} -**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. +**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. @@ -308,11 +308,11 @@ For more information about the audit log REST API, see "[Organizations](/rest/re {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} #### `members_can_create_pages` category actions -For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." | 동작 | 설명 | |:------ |:---------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -345,7 +345,8 @@ For more information, see "[Restricting publication of {% data variables.product | `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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | | `remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret.{% endif %}{% if currentVersion == "free-pro-team@latest"%} -| `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_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/){% if currentVersion != "github-ae@latest" %} 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{% if currentVersion != "github-ae@latest" %} 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 %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). |{% endif %}{% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index f8e9441c10..63c954cdef 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -20,12 +20,12 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. -| IdP | SAML | User provisioning | Team synchronization | -| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | User provisioning | Team synchronization | +| -------------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index d5f6884ead..cdbab68952 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -33,7 +33,9 @@ For more information about {% data variables.product.prodname_enterprise %}, see To use the {% data variables.product.prodname_enterprise %} portion of the license, the 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 %}. -Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an 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. +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. + +While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index c2733cff05..79441c7086 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ GitHub will display your profile README on your profile page if all of the follo The generated README file is pre-populated with a template to give you some inspiration for your profile README. ![README file with pre-populated template](/assets/images/help/repository/personal-repository-readme-template.png) +For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](http://www.emoji-cheat-sheet.com/)." + ### Removing a profile README The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply: diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index ae379d699d..5a4271c826 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,20 +30,23 @@ The repository owner has full control of the repository. In addition to the acti | {% if currentVersion == "free-pro-team@latest" %}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)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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)" |{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} -| Delete packages | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| Delete packages | "[Deleting a package](/github/managing-packages-with-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)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | Receive | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 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 %} +| 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 | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | @@ -64,8 +67,9 @@ Collaborators can also perform the following actions. | 동작 | More information | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Managing disruptive comments](/github/building-a-strong-community/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)" | @@ -79,7 +83,8 @@ Collaborators can also perform the following actions. | Create and edit a wiki for the repository | "[About wikis](/github/building-a-strong-community/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| 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)" | ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md index eca5d3f1b2..48115cd1c3 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -1,6 +1,6 @@ --- title: Types of emails GitHub sends -intro: 'There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, and marketing communications.' +intro: 'There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, customer research invitations, and marketing communications.' redirect_from: - /articles/types-of-emails-github-sends versions: @@ -25,6 +25,17 @@ You can also choose which type of email updates you'd like to receive on convers If you've upgraded to paid products or features, then you'll receive billing receipts at the account's primary email address. For more information, see "[Setting your billing email](/articles/setting-your-billing-email)." +### Customer research emails + +{% data variables.product.product_name %} occasionally seeks customers to participate in research sessions to help us build a better GitHub. These are conducted remotely, open to customers worldwide, and may include: + +- Feedback surveys +- Research interviews +- Usability testing sessions +- Previewing early prototypes or concepts + +These emails are infrequent and you can choose whether or not to participate. If you're interested in additional opportunities to participate in research sessions, you may add yourself to the GitHub Customer Research Panel. For more information, see "[GitHub Customer Experience Research](https://cxr.github.com)." + ### Marketing emails {% data variables.product.product_name %} occasionally sends these types of marketing emails: diff --git a/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md b/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md index 91acf9fde2..d220b5dc9d 100644 --- a/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md @@ -55,7 +55,7 @@ Actions and any elements of the Actions service may not be used in violation of - 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 - any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used. -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, or restrictions in your ability to use GitHub Actions. +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. #### b. Packages Usage GitHub Packages is billed on a usage basis. The [Packages documentation](/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). diff --git a/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md b/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md index 4f17ebc995..b72e615f18 100644 --- a/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ko-KR/content/github/site-policy/github-and-trade-controls.md @@ -27,7 +27,9 @@ Users are responsible for ensuring that the content they develop and share on Gi GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). +GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). #### GitHub Enterprise Server @@ -41,13 +43,13 @@ GitHub Enterprise Server may not be sold to, exported, or re-exported to any cou #### On which countries and territories are U.S. government sanctions applied? -Crimea, Cuba, Iran, North Korea, and Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. +Crimea, Cuba, Iran, North Korea, and Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. #### How is GitHub ensuring that folks not living in and/or having professional links to the sanctioned countries and territories still have access or ability to appeal? In the rare instance that an account is affected unintentionally or in error, we have an appeal process to address such instances. -If an individual user or organization administrator believes that they have been flagged in error, then that user has the opportunity to appeal the flag by providing verification information to GitHub. If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction or otherwise restricted by U.S. economic sanctions, then the flag will be removed. Please see [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY) and [organizational account appeals request form](https://airtable.com/shrB2je5RBkqLEt5D). +If an individual user or organization administrator believes that they have been flagged in error, then that user has the opportunity to appeal the flag by providing verification information to GitHub. If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction for which we do not have a license or otherwise restricted by U.S. economic sanctions, then the flag will be removed. Please see [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY) and [organizational account appeals request form](https://airtable.com/shrB2je5RBkqLEt5D). #### Will traveling in these regions be impacted? @@ -55,13 +57,17 @@ Travel in these regions may impact your account status, but availability may be #### What is available and not available? -GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. -GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in Syria and Crimea. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. +GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. + +GitHub services are not available to developers located or otherwise resident in North Korea. #### How do you define these specific users? @@ -89,8 +95,13 @@ For example, a developer in Iran may sign up for a Free or Pro plan for their in Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. +If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. #### Will Iranian GitHub users be able to use paid services under the license? Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. + +#### Can you clarify availability of GitHub to Cuban developers? + +GitHub cloud services, both free and paid, are generally available to developers located in Cuba. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. diff --git a/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md index 0b0e7594bf..82091f3e99 100644 --- a/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **January 6, 2021** +Effective date: **January 29, 2021** GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -18,28 +18,26 @@ GitHub provides a great deal of transparency regarding how we use your data, how When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the [Privacy Statement](/articles/github-privacy-statement/)). -| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location | -|:-------------------- |:-------------------------------------------------- |:---------------------- |:------------------ | -| Automattic | Blogging service | United States | United States | -| AWS Amazon | Data hosting | United States | United States | -| Braintree (PayPal) | Subscription credit card payment processor | United States | United States | -| Clearbit | Marketing data enrichment service | United States | United States | -| Discourse | Community forum software provider | United States | United States | -| Eloqua | Marketing campaign automation | United States | United States | -| Google Apps | Internal company infrastructure | United States | United States | -| Google Analytics | Analytics and performance | United States | United States | -| MailChimp | Customer ticketing mail services provider | United States | United States | -| Mailgun | Transactional mail services provider | United States | United States | -| Microsoft | Microsoft Services | United States | United States | -| Monday.com | Team collaboration and project management platform | United States | Israel | -| Nexmo | SMS notification provider | United States | United States | -| Salesforce.com | Customer relations management | United States | United States | -| Sendgrid | Transactional mail services provider | United States | United States | -| Sentry.io | Application monitoring provider | United States | United States | -| Stripe | Payment provider | United States | United States | -| Twilio | SMS notification provider | United States | United States | -| Zendesk | Customer support ticketing system | United States | United States | -| Zuora | Corporate billing system | United States | United States | +| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location | +|:------------------------ |:--------------------------------------------------------------- |:---------------------- |:------------------ | +| Automattic | Blogging service | United States | United States | +| AWS Amazon | Data hosting | United States | United States | +| Braintree (PayPal) | Subscription credit card payment processor | United States | United States | +| Clearbit | Marketing data enrichment service | United States | United States | +| Discourse | Community forum software provider | United States | United States | +| Eloqua | Marketing campaign automation | United States | United States | +| Google Apps | Internal company infrastructure | United States | United States | +| MailChimp | Customer ticketing mail services provider | United States | United States | +| Mailgun | Transactional mail services provider | United States | United States | +| Microsoft | Microsoft Services | United States | United States | +| Monday.com | Team collaboration and project management platform | United States | Israel | +| Nexmo | SMS notification provider | United States | United States | +| Salesforce.com | Customer relations management | United States | United States | +| Sentry.io | Application monitoring provider | United States | United States | +| Stripe | Payment provider | United States | United States | +| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | United States | United States | +| Zendesk | Customer support ticketing system | United States | United States | +| Zuora | Corporate billing system | United States | United States | When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via {% data variables.contact.contact_privacy %}. @@ -47,7 +45,7 @@ When we bring on a new subprocessor who handles our Users' Personal Information, GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. -Since the number and names of cookies may change,the table below may be updated from time to time. +Since the number and names of cookies may change, the table below may be updated from time to time. | Service Provider | Cookie Name | 설명 | Expiration* | |:---------------- |:------------------------------------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------- | diff --git a/translations/ko-KR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/ko-KR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 8f50e7c5d4..605e7bd22d 100644 --- a/translations/ko-KR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/ko-KR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ Please note that the information available will vary from case to case. Some of ### Cost reimbursement -We reserve the right to seek reimbursement for administrative costs associated with responding to requests for information, as allowed by law. +Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. + +While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: + +- Initial search of up to 25 identifiers: Free +- Production of subscriber information/data for up to 5 accounts: Free +- Production of subscriber information/data for more than 5 accounts: $20 per account +- Secondary searches: $10 per search ### Data preservation diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 69bff67d4a..ddaa3f6ce3 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -22,7 +22,7 @@ You can sponsor an account on behalf of your user account to invest in projects - Developing brand awareness as an organization that values open source - Thanking open source developers for building libraries that complement the product your organization offers -You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." diff --git a/translations/ko-KR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/ko-KR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index a03eb6041a..3c9c5730ff 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/ko-KR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ You can configure most Jekyll settings, such as your site's theme and plugins, b Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites. -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file. -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md b/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md index 19722761b2..c4beaadc40 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/ko-KR/content/github/working-with-github-pages/about-github-pages.md @@ -25,11 +25,15 @@ 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 %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Organization owners can disable the publication of -{% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." +{% 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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} ### Types of {% data variables.product.prodname_pages %} sites @@ -40,6 +44,10 @@ To publish a user site, you must create a repository owned by your user account The source files for a project site are stored in the same repository as their project. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +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](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} 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 %} @@ -90,9 +98,9 @@ The default publishing source for a project site is the `gh-pages` branch. If th Project sites can also be published from the `master` branch or a `/docs` folder on the `master` branch. To publish your site from one of these sources, you must configure a different publishing source. 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)." - If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} 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 %} +If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} 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 %} - You cannot publish your project site from any other branch, even if the default branch is not `master` or `gh-pages`. +You cannot publish your project site from any other branch, even if the default branch is not `master` or `gh-pages`. {% endif %} diff --git a/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index dc00414587..d1d49acece 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ko-KR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ You can see build failures (but not build warnings) for your site on {% data var You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit. 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. 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 diff --git a/translations/ko-KR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ko-KR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 7ed074204f..8e522d360c 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/ko-KR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ People with write permissions for a repository can add a theme to a {% data vari {% data reusables.pages.navigate-publishing-source %} 1. Create a new file called _/assets/css/style.scss_. 2. Add the following content to the top of the file: - ``` + ```scss --- --- diff --git a/translations/ko-KR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ko-KR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..b19019da27 --- /dev/null +++ b/translations/ko-KR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. You can see your site's URL in the repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. To see your published site, under "{% data variables.product.prodname_pages %}", click your site's URL. ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/ko-KR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ko-KR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 160952a869..082253b63b 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/ko-KR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. In the file name field, type `404.html` or `404.md`. ![File name field](/assets/images/help/pages/404-file-name.png) 4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file: - ``` + ```yaml --- permalink: /404.html --- diff --git a/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 618015f9f7..e466479b76 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,6 +11,8 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### 빌드전 요구 사양 Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." @@ -95,7 +97,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md`. +You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. You can also add a theme to customize your site’s look and feel. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." diff --git a/translations/ko-KR/content/github/working-with-github-pages/index.md b/translations/ko-KR/content/github/working-with-github-pages/index.md index d9cf723b62..eb61cc092a 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/index.md +++ b/translations/ko-KR/content/github/working-with-github-pages/index.md @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/ko-KR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ko-KR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 3b2bb2212b..22f7e9a648 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ko-KR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -78,7 +78,7 @@ This error means that your code references a symlinked file that does not exist This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols. To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file: -``` +```yaml encoding: UTF-8 ``` diff --git a/translations/ko-KR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ko-KR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index b6c6be96fc..c3203ee9a9 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/ko-KR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: Unpublishing a GitHub Pages site -intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available to {% if currentVersion == "free-pro-team@latest" %}the public{% else %}everyone using {% data variables.product.product_location %}{% endif %}.' +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 955f447af3..d4ce4e38d3 100644 --- a/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -13,7 +13,7 @@ versions: 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 # The largest heading ## The second largest heading ###### The smallest heading @@ -37,7 +37,7 @@ You can indicate emphasis with bold, italic, or strikethrough text. You can quote text with a `>`. -``` +```markdown In the words of Abraham Lincoln: > Pardon my French @@ -55,7 +55,7 @@ In the words of Abraham Lincoln: You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted. -``` +```markdown Use `git status` to list all new or modified files that haven't yet been committed. ``` @@ -102,7 +102,7 @@ You can create an inline link by wrapping link text in brackets `[ ]`, and then You can make an unordered list by preceding one or more lines of text with `-` or `*`. -``` +```markdown - George Washington - John Adams - Thomas Jefferson @@ -112,7 +112,7 @@ You can make an unordered list by preceding one or more lines of text with `-` o To order your list, precede each line with a number. -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams @@ -126,7 +126,7 @@ You can create a nested list by indenting one or more list items below another i 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. First list item - First nested list item - Second nested list item @@ -140,7 +140,7 @@ To create a nested list in the comment editor on {% data variables.product.produ 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. First list item - First nested list item ``` @@ -149,7 +149,7 @@ In this example, you could add a nested list item under the list item `100. Firs You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven spaces (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. -``` +```markdown 100. First list item - First nested list item - Second nested list item diff --git a/translations/ko-KR/content/github/writing-on-github/organizing-information-with-tables.md b/translations/ko-KR/content/github/writing-on-github/organizing-information-with-tables.md index c3e86fd0e1..fc1c9ee4a6 100644 --- a/translations/ko-KR/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/ko-KR/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: You can create tables with pipes `|` and hyphens `-`. Hyphens are used to create each column's header, while pipes separate each column. You must include a blank line before your table in order for it to correctly render. -``` +```markdown | First Header | Second Header | | ------------- | ------------- | @@ -27,7 +27,7 @@ The pipes on either end of the table are optional. Cells can vary in width and do not need to be perfectly aligned within columns. There must be at least three hyphens in each column of the header row. -``` +```markdown | Command | Description | | --- | --- | | git status | List all new or modified files | @@ -40,7 +40,7 @@ Cells can vary in width and do not need to be perfectly aligned within columns. You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table: -``` +```markdown | Command | Description | | --- | --- | | `git status` | List all *new or modified* files | @@ -51,7 +51,7 @@ You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as You can align text to the left, right, or center of a column by including colons `:` to the left, right, or on both sides of the hyphens within the header row. -``` +```markdown | Left-aligned | Center-aligned | Right-aligned | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ You can align text to the left, right, or center of a column by including colons To include a pipe `|` as content within your cell, use a `\` before the pipe: -``` +```markdown | Name | Character | | --- | --- | | Backtick | ` | diff --git a/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md b/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md index 017b674775..069cb73fd6 100644 --- a/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md +++ b/translations/ko-KR/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This * Query `__schema` to list all types defined in the schema and get details about each: ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* Query `__type` to get details about any type: + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* Query `__type` to get details about any type: - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * You can also run an _introspection query_ of the schema via a `GET` request: diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index a4cfdabbeb..e3d8eea29a 100644 --- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -14,7 +14,7 @@ After you enable the link, each user can navigate directly from {% data variable 1. Connect to the administrative shell for {% data variables.product.prodname_ghe_server %}. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." 2. Run the following command. - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. Return to diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index 811f412aac..c831c367e5 100644 --- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - You must install dependencies on the application server. - [Docker](https://docs.docker.com/install/) 1.13.0+ - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/), available via apt for [Debian](https://packages.debian.org/search?keywords=netcat) and [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} diff --git a/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index 5a827f2186..2cae2383bb 100644 --- a/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ If you want to interact with multiple repositories, you can add each repository If your instance has subdomain isolation enabled: {% endif %} -``` +```xml "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` @@ -119,7 +119,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y {% data reusables.package_registry.authenticate-step %} 2. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -131,7 +131,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y 3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html). - ``` + ```ruby source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" diff --git a/translations/ko-KR/content/packages/index.md b/translations/ko-KR/content/packages/index.md index 1defcebba0..3d492fe556 100644 --- a/translations/ko-KR/content/packages/index.md +++ b/translations/ko-KR/content/packages/index.md @@ -12,13 +12,18 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: + - + title: ghcr.io maintenance mode on 2021-01-09 + date: '2021-01-08' + href: https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/ - title: ghcr.io container names redirect to the container page date: '2020-12-14' @@ -27,10 +32,6 @@ changelog: title: Filter for tagged and untagged containers date: '2020-12-14' href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: Packages container support is an opt-in beta - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md b/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md index dec649cf0b..f76f5eaefa 100644 --- a/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md +++ b/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md @@ -54,7 +54,7 @@ Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token. {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md index 6dc2e0240c..2d0f25d9c9 100644 --- a/translations/ko-KR/content/rest/overview/libraries.md +++ b/translations/ko-KR/content/rest/overview/libraries.md @@ -79,6 +79,10 @@ Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https: Library name | Repository |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +### Rust + +Library name | Repository |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) + ### Scala Library name | Repository |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) diff --git a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md index fbe9b763a6..9213c43bcf 100644 --- a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md @@ -107,7 +107,7 @@ _검색_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permission on "actions" - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Collaborators_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Commit comments_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -836,6 +842,9 @@ _Teams_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ko-KR/data/glossaries/external.yml b/translations/ko-KR/data/glossaries/external.yml index a7e0591036..89a66f28cd 100644 --- a/translations/ko-KR/data/glossaries/external.yml +++ b/translations/ko-KR/data/glossaries/external.yml @@ -35,7 +35,7 @@ - term: 바이오 description: >- - 프로필에 있는 사용자 생성 설명: https://help.github.com/articles/adding-a-bio-to-your-profile/ + The user-generated description found on a profile: [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile) - term: 청구 주기 description: 특정 청구 계획에 대한 시간 간격입니다. @@ -156,7 +156,7 @@ - term: 기여 description: >- - GitHub의 특정 활동: - 사용자의 기여 그래프에 정사각형 추가: "[기여로 간주되는 것](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - 프로필의 사용자 타임라인에 활동 추가: "[기여 활동](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" + Specific activities on GitHub that will: - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - term: 기여자 description: >- @@ -229,7 +229,7 @@ 새 기능을 실험하거나 프로덕션 환경에 없는 이슈를 해결하는 데 사용되는 분기입니다. 토픽 분기라고도 합니다. - term: 울타리친 코드 블록 - description: '코드 블록 전후의 트리플 백틱 \`\`\`을 사용하여 GitHub Flavored Markdown으로 만들 수 있는 코드의 들여쓴 블록입니다. 이 [example](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)를 참조하십시오.' + description: 'An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' - term: 가져오기 description: >- diff --git a/translations/ko-KR/data/learning-tracks/README.md b/translations/ko-KR/data/learning-tracks/README.md new file mode 100644 index 0000000000..ec0f70309e --- /dev/null +++ b/translations/ko-KR/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Learning Tracks (aka Learning Paths) + +Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. \ No newline at end of file diff --git a/translations/ko-KR/data/learning-tracks/actions.yml b/translations/ko-KR/data/learning-tracks/actions.yml index 678519414c..c825769cc8 100644 --- a/translations/ko-KR/data/learning-tracks/actions.yml +++ b/translations/ko-KR/data/learning-tracks/actions.yml @@ -31,6 +31,13 @@ continuous_deployment: - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Deploy to the cloud' + description: 'Learn how to use {% data variables.product.prodname_actions %} to build an application and deploy it to various cloud-based platforms.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine 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/translations/ko-KR/data/release-notes/2-20/18.yml b/translations/ko-KR/data/release-notes/2-20/18.yml index 3aab7ba337..f38b400522 100644 --- a/translations/ko-KR/data/release-notes/2-20/18.yml +++ b/translations/ko-KR/data/release-notes/2-20/18.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/9.yml b/translations/ko-KR/data/release-notes/2-21/9.yml index 46656c9e6b..a712183036 100644 --- a/translations/ko-KR/data/release-notes/2-21/9.yml +++ b/translations/ko-KR/data/release-notes/2-21/9.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-22/1.yml b/translations/ko-KR/data/release-notes/2-22/1.yml index fbd3988c3d..8edfa619f0 100644 --- a/translations/ko-KR/data/release-notes/2-22/1.yml +++ b/translations/ko-KR/data/release-notes/2-22/1.yml @@ -12,7 +12,7 @@ sections: - | Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | diff --git a/translations/ko-KR/data/release-notes/3-0/0-rc1.yml b/translations/ko-KR/data/release-notes/3-0/0-rc1.yml new file mode 100644 index 0000000000..1d9293905b --- /dev/null +++ b/translations/ko-KR/data/release-notes/3-0/0-rc1.yml @@ -0,0 +1,145 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. 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 variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - 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. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ko-KR/data/release-notes/3-0/0-rc2.yml b/translations/ko-KR/data/release-notes/3-0/0-rc2.yml new file mode 100644 index 0000000000..0e6ed5fd3f --- /dev/null +++ b/translations/ko-KR/data/release-notes/3-0/0-rc2.yml @@ -0,0 +1,25 @@ +--- +date: '2021-01-29' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +sections: + bugs: + - + heading: Fixes for known issues from Release Candidate 1 + notes: + - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. + - The "Mandatory message viewed" audit log event was not being saved. + - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' + - Removing yourself as an enterprise owner returned a 404. + - + heading: Fixes for other issues + notes: + - Issues with migrations and upgrades to 3.0.0 have been fixed. + - Backup Utilities versioning now works for release candidate versions. + - Generating a support bundle resulted in an error in the orchestrator logs. + - A large restore could result in Redis running out of memory. + - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. + - GitHub Actions can only be enabled if the required storage is also configured. + - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + known_issues: + - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/translations/ko-KR/data/reusables/actions/actions-not-verified.md b/translations/ko-KR/data/reusables/actions/actions-not-verified.md index 3107e5a79f..1eebaf90f5 100644 --- a/translations/ko-KR/data/reusables/actions/actions-not-verified.md +++ b/translations/ko-KR/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/ko-KR/data/reusables/code-scanning/not-available.md b/translations/ko-KR/data/reusables/code-scanning/not-available.md index 6531f5e1d0..0e4d2ac82f 100644 --- a/translations/ko-KR/data/reusables/code-scanning/not-available.md +++ b/translations/ko-KR/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." {% endnote %} {% endif %} diff --git a/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md new file mode 100644 index 0000000000..c5142332f6 --- /dev/null +++ b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + +{% endnote %} diff --git a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md index a217ad81ee..e5b61bf344 100644 --- a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md @@ -1,34 +1,35 @@ -The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. +The following table shows, for each package manager: +- The YAML value to use in the *dependabot.yml* file +- The supported versions of the package manager +- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +- Whether vendored dependencies are supported -| Package manager | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | -| -------------------------------- |:-----------------------------------------------------------------:|:---------:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir: `hex` | | | -| Elm: `elm` | **✓** | | -| git submodule: `gitsubmodule` | **✓** | | -| GitHub Actions: `github-actions` | **✓** | | -| Go modules: `gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +| Package manager | YAML value | Supported versions | Private repositories | Vendoring | +| --------------- | ---------------- | ------------------------- |:--------------------:|:---------:| +| 번들러 | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1,v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | +| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | +| Go modules | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | see (A) below | **✓** | | +| Maven | `maven` | see (B) below | **✓** | | +| npm | `npm` | v6 | **✓** | | +| NuGet | `nuget` | <= 4.8.
    see (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**Note**: {% data variables.product.prodname_dependabot %} also supports the following package managers: +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn` (v1 only) (specify `npm`) +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --`.gradle.kts` files, for Kotlin projects (specify `gradle`) - --`pipenv`, `pip-compile`, and `poetry` (specify `pip`) - -For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. diff --git a/translations/ko-KR/data/reusables/desktop/delete-tag.md b/translations/ko-KR/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..40d455b880 --- /dev/null +++ b/translations/ko-KR/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Right-click the commit. + + - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) + - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/education/about-github-education-link.md b/translations/ko-KR/data/reusables/education/about-github-education-link.md index 67fa09ec6a..84a5d61418 100644 --- a/translations/ko-KR/data/reusables/education/about-github-education-link.md +++ b/translations/ko-KR/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_education %} school. For more information, see "[About {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)." +Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_education %} school. For more information, see "[About {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)." diff --git a/translations/ko-KR/data/reusables/education/apply-for-team.md b/translations/ko-KR/data/reusables/education/apply-for-team.md index 88fdff7f90..272564d3d5 100644 --- a/translations/ko-KR/data/reusables/education/apply-for-team.md +++ b/translations/ko-KR/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." +- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[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)." diff --git a/translations/ko-KR/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/ko-KR/data/reusables/enterprise_installation/ssh-into-instance.md index 9dcd8e90d3..c5e62f493a 100644 --- a/translations/ko-KR/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/ko-KR/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. SSH into {% data variables.product.product_location %}. +1. SSH into {% data variables.product.product_location %}. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/ko-KR/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/ko-KR/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 77593c5d20..0cdbb1f880 100644 --- a/translations/ko-KR/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/ko-KR/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. To import the archived migration data to a {% data variables.product.prodname_ghe_server %} instance, see "[Importing migration data to {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)". +1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[Preparing to migrate data to your enterprise](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/ko-KR/data/reusables/gated-features/private-pages.md b/translations/ko-KR/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..3fb7f0a3a7 --- /dev/null +++ b/translations/ko-KR/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/ko-KR/data/reusables/github-actions/actions-billing.md b/translations/ko-KR/data/reusables/github-actions/actions-billing.md index 4e12946e9b..249d4b339a 100644 --- a/translations/ko-KR/data/reusables/github-actions/actions-billing.md +++ b/translations/ko-KR/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. +{% data variables.product.prodname_actions %} usage is free for both public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md b/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md index 2ad79b4182..33c7bd3120 100644 --- a/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ The starter workflow template sets up the `PATH` to contain OpenJDK 8 for the x6 For example, to use version 9.0.4 of the JDK for the x64 platform, you can use the `setup-java` action and configure the `java-version` and `architecture` parameters to `'9.0.4'` and `x64`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md b/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md index e6db4f8803..0114ffafd7 100644 --- a/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a private preview only. Any users or organizations that are already using this runner can continue using it, but we're not accepting any further users or organizations at this time. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/ko-KR/data/reusables/marketplace/launch-with-free.md b/translations/ko-KR/data/reusables/marketplace/launch-with-free.md index 2151c241cc..15e06d0cb2 100644 --- a/translations/ko-KR/data/reusables/marketplace/launch-with-free.md +++ b/translations/ko-KR/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/ko-KR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/ko-KR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md index 30ba905e4b..29620e32dc 100644 --- a/translations/ko-KR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ b/translations/ko-KR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -1 +1 @@ -If you're not a billing manger for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). +If you're not a billing manager for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/ko-KR/data/reusables/pages/about-private-publishing.md b/translations/ko-KR/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..f1f13531ce --- /dev/null +++ b/translations/ko-KR/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. diff --git a/translations/ko-KR/data/reusables/pages/choose-visibility.md b/translations/ko-KR/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..bd794a90d7 --- /dev/null +++ b/translations/ko-KR/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..fc98787aaa --- /dev/null +++ b/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md b/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md index 7620878dbc..04d4ddeb1c 100644 --- a/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. If you have sensitive data in your site's repository, you may want to remove it before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/ko-KR/data/reusables/pages/twenty-minutes-to-publish.md b/translations/ko-KR/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..3e7a2fd5a4 --- /dev/null +++ b/translations/ko-KR/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**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 %}. If your don't see your changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/pages/visit-site.md b/translations/ko-KR/data/reusables/pages/visit-site.md index 7ef1b070cb..6e94a9bfd9 100644 --- a/translations/ko-KR/data/reusables/pages/visit-site.md +++ b/translations/ko-KR/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% note %} - **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 %}. If your don't see your changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/ko-KR/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/ko-KR/data/reusables/pull_requests/rebase_and_merge_summary.md index 284f536db2..cd6ca3efd4 100644 --- a/translations/ko-KR/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/ko-KR/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ When you select the **Rebase and merge** option on a pull request on {% data var To rebase and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow rebase merging](/articles/configuring-commit-rebasing-for-pull-requests/). -The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [the "Git rebase" chapter from the _Pro Git_ book](https://git-scm.com/docs/git-rebase). +The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). For a visual representation of `git rebase`, see [The "Git Branching - Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/ko-KR/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/ko-KR/data/reusables/saml/about-user-provisioning-enterprise-account.md index 918dab289f..c83e052fa8 100644 --- a/translations/ko-KR/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/ko-KR/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -If you use Okta as your IdP, you can use SCIM to manage organization membership in your enterprise account. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. +If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. diff --git a/translations/ko-KR/data/reusables/user-settings/edit_marketplace_listing.md b/translations/ko-KR/data/reusables/user-settings/edit_marketplace_listing.md index 7b7bf4115a..306c505acf 100644 --- a/translations/ko-KR/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/ko-KR/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. Scroll down to the Marketplace section and click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md index 258aac4a8f..444621076f 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| 키 | 유형 | 설명 | -| ---- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `동작` | `문자열` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| 키 | 유형 | 설명 | +| ---- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `동작` | `문자열` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml index 62720ac52e..a48fc65c38 100644 --- a/translations/ko-KR/data/ui.yml +++ b/translations/ko-KR/data/ui.yml @@ -138,9 +138,19 @@ product_sublanding: learning_paths: Learning paths learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. more_guides: more guides - guideTypes: + load_more: Load more guides + all_guides: All Guides + no_result: Sorry, there is no guide that match your filter. + filters: + type: 유형 + topic: Topic + all: All + guide_types: overview: 개요 quick_start: Quickstart tutorial: 튜토리얼 how_to: How-to guide reference: Reference +learning_track_nav: + prevGuide: Previous guide + nextGuide: Next guide diff --git a/translations/ko-KR/data/variables/product.yml b/translations/ko-KR/data/variables/product.yml index ba1a19ad12..c828481f8a 100644 --- a/translations/ko-KR/data/variables/product.yml +++ b/translations/ko-KR/data/variables/product.yml @@ -61,6 +61,7 @@ prodname_marketplace: 'GitHub 마켓플레이스' prodname_github_app: 'GitHub 앱' prodname_github_apps: 'GitHub Apps' prodname_oauth_app: 'OAuth 앱' +prodname_oauth_apps: 'OAuth Apps' #API and developer docs prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs' prodname_support_forum_with_url: '[GitHub API Development and Support Forum](https://github.community/c/github-api-development-and-support/37)' diff --git a/translations/pt-BR/content/actions/creating-actions/about-actions.md b/translations/pt-BR/content/actions/creating-actions/about-actions.md index 0ae4b11b73..2bd3cb742e 100644 --- a/translations/pt-BR/content/actions/creating-actions/about-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/about-actions.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Desenvolvimento da ação + - Princípios básicos --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ etapas: #### Usar um SHA do commit para o gerenciamento de versão -Cada commit do Git recebe um valor SHA calculado, que é único e imutável. Os usuários da sua ação podem preferir depender de um valor SHA do commit, uma vez que esta abordagem pode ser mais confiável do que especificar uma tag, que pode ser excluída ou movida. No entanto, isso significa que os usuários não receberão mais atualizações realizadas na ação. Usar um valor integral SHA do commit em vez de um valor abreviado pode ajudar a impedir que as pessoas usem um commit malicioso que use a mesma abreviatura. +Cada commit do Git recebe um valor SHA calculado, que é único e imutável. Os usuários da sua ação podem preferir depender de um valor SHA do commit, uma vez que esta abordagem pode ser mais confiável do que especificar uma tag, que pode ser excluída ou movida. No entanto, isso significa que os usuários não receberão mais atualizações realizadas na ação. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Você deve usar o valor completo do SHA de um commit e não um valor abreviado.{% else %}Usar o valor SHA completo de um commit em vez do valor abreviado pode ajudar a impedir que as pessoas usem um commit malicioso que usa a mesma abreviação.{% endif %} ```yaml etapas: diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md index 112c0e6ff8..03025561e1 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Desenvolvimento da ação' --- {% data reusables.actions.enterprise-beta %} @@ -65,12 +67,12 @@ Antes de começar, você criará um repositório {% data variables.product.produ required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -122,7 +124,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md index 59a5e5d3ec..70e2a14321 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Desenvolvimento da ação' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ Antes de começar, você precisa criar um repositório GitHub. 1. No seu terminal, mude os diretórios para seu novo repositório. - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ Antes de começar, você precisa criar um repositório GitHub. Em seu novo diretório `hello-world-docker-action`, crie um arquivo `Dockerfile`. Para obter mais informações, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)". **arquivo Docker** -```dockerfile +```dockerfile{:copy} # Imagem de contêiner que executa seu código FROM alpine:3.10 @@ -65,7 +68,7 @@ Crie um novo arquivo `action.yml` no diretório `hello-world-docker-action` que {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ Na sequência, o script obtém a hora atual e a configura como uma variável de 1. Crie um novo arquivo `entrypoint.sh` no diretório `hello-world-docker-action`. -1. Torne o seu arquivo `entrypoint.sh` file executável: - - ```shell - chmod +x entrypoint.sh - ``` - 1. Adicione o código a seguir ao arquivo `entrypoint.sh`. **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" time=$(date) echo "::set-output name=time::$time" ``` - Se `entrypoint.sh` for executado sem qualquer erro, o status da ação será definido como `success`. Você também pode definir explicitamente códigos de saída no código de ação para fornecer o status de uma ação. 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)". +1. Torne seu arquivo executável `entrypoint.sh` executando o seguinte comando no seu sistema. + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### Criar LEIAME Para que as pessoas saibam como usar sua ação, você pode criar um arquivo LEIAME. Um arquivo LEIAME é ú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. @@ -130,7 +132,7 @@ No diretório `hello-world-docker-action`, crie um arquivo `README.md` que espec - Um exemplo de uso da ação no fluxo de trabalho. **README.md** -```markdown +```markdown{:copy} # Hello world docker action Esta ação imprime "Hello World" ou "Hello" + o nome de uma pessoa a ser cumprimentada no log. @@ -160,7 +162,7 @@ A partir do seu terminal, faça commit dos arquivos `action.yml`, `entrypoint.sh 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)". -```shell +```shell{:copy} git add action.yml entrypoint.sh Dockerfile README.md git commit -m "Minha primeira ação está pronta" git tag -a -m "Versão da minha primeira ação" v1 @@ -175,11 +177,11 @@ Agora você está pronto para testar sua ação em um fluxo de trabalho. Quando #### Exemplo usando uma ação pública -O código do fluxo de trabalho a seguir usa a ação hello world completa no repositório público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copie o exemplo de código de fluxo de trabalho a seguir em um arquivo `.github/workflows/main.yml`, mas substitua `actions/hello-world-docker-action` pelo nome de seu repositório e ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. +O código do fluxo de trabalho a seguir usa a ação completa _hello world_ no repositório público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copie o exemplo de código de fluxo de trabalho a seguir em um arquivo `.github/workflows/main.yml`, mas substitua `actions/hello-world-docker-action` pelo nome de seu repositório e ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. {% if currentVersion == "free-pro-team@latest" %}As ações públicas podem ser usadas mesmo se não forem publicadas em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Publicar uma ação](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)". {% endif %} {% raw %} **.github/workflows/main.yml** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### Exemplo usando uma ação privada -Copie o seguinte exemplo de código de 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. +Copie o seguinte exemplo de código de 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. {% if currentVersion == "free-pro-team@latest" %}Esta ação privada não pode ser publicada em {% data variables.product.prodname_marketplace %}, e só pode ser usada neste repositório.{% endif %} {% raw %} **.github/workflows/main.yml** -```yaml +```yaml{:copy} em: [push] trabalhos: 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 e8d84aaf69..b931fae8cc 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 @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Desenvolvimento da ação' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index a92adf20ea..83c0644551 100644 --- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,7 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} @@ -48,20 +48,21 @@ A instrução do `ENTRYPOINT` do Docker tem forma de _shell_ e forma de _exec_. Se você configurar o seu contêiner para usar a forma _exec_ da instrução `ENTRYPOINT`, os `args` configurados no arquivo de metadados da ação não serão executados em um shell do comando. Se os `args` da ação contiverem uma variável do ambiente, esta não será substituída. Por exemplo, usar o formato _exec_ a seguir não imprimirá o valor armazenado em `$GITHUB_SHA`. Em vez disso, imprimirá `$GITHUB_SHA`. -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` Se você desejar uma substituição de variável, use a forma _shell_ ou execute um shell diretamente. Por exemplo, ao usar o formato _exec_ a seguir, você poderá executar um shell para imprimir o valor armazenado na variável do ambiente `GITHUB_SHA`. -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` Para fornecer os `args` definidos no arquivo de metadados da ação para um contêiner Dock que usa a forma _exec_ no `ENTRYPOINT`, recomendamos criar um script do shell denominado `entrypoint.sh` que você pode acessar a partir da instrução `ENTRYPOINT`: ##### Exemplo *arquivo Docker* -``` + +```dockerfile # Container image that runs your code FROM debian:9.5-slim diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index b311f35db8..d07fceda53 100644 --- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,7 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md index 01c0580ece..9294b50be3 100644 --- a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,6 +41,7 @@ Para obter mais informações, consulte "[Criar uma ação JavaScript](/articles Se estiver criando uma ação de contêiner do Docker, você poderá definir um código de saída de falha no seu script `entrypoint.sh`. Por exemplo: +{% raw %} ``` if ; then echo "Game over!" @@ -49,5 +50,6 @@ fi exit 1 fi ``` +{% endraw %} Para obter mais informações, consulte "[Criar uma ação de contêiner do Docker](/articles/creating-a-docker-container-action)". diff --git a/translations/pt-BR/content/actions/guides/about-continuous-integration.md b/translations/pt-BR/content/actions/guides/about-continuous-integration.md index 310fe14a71..6d57454cbe 100644 --- a/translations/pt-BR/content/actions/guides/about-continuous-integration.md +++ b/translations/pt-BR/content/actions/guides/about-continuous-integration.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - CI + - CD --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md b/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md index ca286dd834..6cd4bcb6fb 100644 --- a/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Empacotando --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/about-service-containers.md b/translations/pt-BR/content/actions/guides/about-service-containers.md index 8abe96e9bd..1a7ada5f13 100644 --- a/translations/pt-BR/content/actions/guides/about-service-containers.md +++ b/translations/pt-BR/content/actions/guides/about-service-containers.md @@ -8,7 +8,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ Você pode usar a palavra-chave `serviços` para criar contêineres de serviço Este exemplo cria um serviço denominado `redis` em um trabalho denominado `container-job`. O host do Docker, neste exemplo, é o contêiner `node:10.18-jessie`. {% raw %} -```yaml +```yaml{:copy} nome: Exemplo de contêiner Redis em: push @@ -89,7 +92,7 @@ Ao especificar a porta do host do Docker mas não a porta do contêiner, a porta Este exemplo mapeia a porta 6379 do contêiner de serviço `redis` com a porta 6379 do host do Docker. {% raw %} -```yaml +```yaml{:copy} nome: Exemplo de serviço Redis em: push diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md index 72fe60fc70..bd56c156d1 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-ant.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Para começar rapidamente, você pode escolher o modelo do Ant pré-configurado Você também pode adicionar este fluxo de trabalho manualmente, criando um novo arquivo no diretório `.github/workflows` do seu repositório. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ O fluxo de trabalho inicial executará o alvo-padrão especificado no arquivo _b Se você usa comandos diferentes para criar seu projeto ou se você quer executar um alvo diferente, você poderá especificá-los. Por exemplo, você pode desejar executar o `jar` alvo configurado no arquivo _build-ci.xml_. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ Após a sua criação ter sido criada com sucesso e os seus testes aprovados, é De modo geral, o Ant cria arquivos de saída como JARs, EARs ou WARs no diretório `build/jar`. Você pode fazer upload do conteúdo desse diretório usando a ação `upload-artefact`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md index 97c1521224..ccc558b2ea 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-gradle.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Para começar rapidamente, você pode escolher o modelo do Gradle pré-configura Você também pode adicionar este fluxo de trabalho manualmente, criando um novo arquivo no diretório `.github/workflows` do seu repositório. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ O fluxo de tarbalho inicial executará a tarefa `criar` por padrão. Na configur Se você usa comandos diferentes para criar seu projeto ou se você desejar usar uma atividade diferente, você poderá especificá-los. Por exemplo, é possível que você deseje executar a tarefa `pacote` configurada no seu arquivo _ci.gradle_. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. + # Restoring these files from a GitHub Actions cache might cause problems for future builds. + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -Este fluxo de trabalho salvará o conteúdo da sua cache local do pacote Gradle, localizado no diretório `.gradle/caches` do diretório principal do executor. A chave da cache será o conteúdo em hash dos arquivos de criação do Gradle. Portanto, suas alterações irão invalidar a cache. +Este fluxo de trabalho salvará o conteúdo de seu cache local do pacote Gradle, localizado nos diretórios `.gradle/caches` e `.gradle/wrapper` do diretório inicial do executor. A chave de cache será o conteúdo da compilação com hash (incluindo o arquivo de propriedades do wrapper do Gradle). Portanto, qualquer alteração neles irá invalidar o cache. ### Empacotar dados do fluxo de trabalho como artefatos @@ -122,7 +135,7 @@ Após a sua criação ter sido criada com sucesso e os seus testes aprovados, é De modo geral, o Gradle cria arquivos de saída como JARs, EARs ou WARs no diretório `build/libs`. Você pode fazer upload do conteúdo desse diretório usando a ação `upload-artefact`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md index 95b58cab25..c3eeddbaf1 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-java-with-maven.md @@ -8,6 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ Para começar rapidamente, você pode escolher o modelo do Maven pré-configurad Você também pode adicionar este fluxo de trabalho manualmente, criando um novo arquivo no diretório `.github/workflows` do seu repositório. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ O fluxo de trabalho inicial executará o `pacote`-alvo por padrão. Na configura Se você usa comandos diferentes para criar seu projeto ou se desejar usar um alvo diferente, você poderá especificá-los. Por exemplo, você pode desejar executar o alvo de `verificar`, configurado em um arquivo _pom-ci.xml_. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -122,7 +126,7 @@ Após a sua criação ter sido criada com sucesso e os seus testes aprovados, é De modo geral, o Maven criará arquivos de saída como JARs, EARs ou WARs no diretório `alvo`. Para fazer o upload como artefatos, você pode copiá-los em um novo diretório que contém artefatos a serem subidos. Por exemplo, você pode criar um diretório denominado `treinamento`. Em seguida, você pode fazer o upload do conteúdo desse diretório usando a ação `upload-artifact`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-net.md b/translations/pt-BR/content/actions/guides/building-and-testing-net.md index 857bf965d3..cbfc8160fc 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-net.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: Para usar uma versão pré-instalada do .NET Core SDK em um executor hospedado em {% data variables.product.prodname_dotcom %}, use a ação `setup-dotnet`. Esta ação encontra uma versão específica do .NET do cache de ferramentas em cada executor e adiciona os binários necessários para `PATH`. Estas alterações persistirão para o resto do trabalho. -A ação `setup-dotnet` é a forma recomendada de usar .NET com {% data variables.product.prodname_actions %}, porque garante um comportamento consistente em executores diferentes e versões diferentes do .NET. Se você estiver usando um executor auto-hospedado, você deverá instalar o .NET e adicioná-lo ao `PATH`. Para obter mais informações, consulte a [`configuração-dotnet`](https://github.com/marketplace/actions/setup-dotnet). +A ação `setup-dotnet` é a forma recomendada de usar .NET com {% data variables.product.prodname_actions %}, porque garante um comportamento consistente em executores diferentes e versões diferentes do .NET. Se você estiver usando um executor auto-hospedado, você deverá instalar o .NET e adicioná-lo ao `PATH`. Para obter mais informações, consulte a ação [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk). #### Usar múltiplas versões do .NET diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md index 16f59d7ca9..8617c5e77d 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md @@ -8,6 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CI' + - 'Nó' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} @@ -36,7 +41,11 @@ Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do ```yaml{:copy} name: Node.js CI -on: [push] +on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] jobs: build: @@ -45,7 +54,7 @@ jobs: strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -53,11 +62,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -69,15 +76,15 @@ A maneira mais fácil de especificar uma versão do Node.js é usar a ação `se 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`. -O modelo inclui uma estratégia de matriz que cria e testa o seu código com três versões do Node.js: 8.x, 10.x, e 12.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. +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. 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 os contextos e estratégias da 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 "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". {% raw %} -```yaml +```yaml{:copy} strategy: matrix: - node-version: [8.x, 10.x, 12.x] + node-version: [10.x, 12.x, 14.x, 15.x] steps: - uses: actions/checkout@v2 @@ -90,7 +97,7 @@ steps: Como alternativa, você pode criar e fazes testes com versões exatas do Node.js. -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -99,7 +106,7 @@ strategy: Você também pode criar e testar usando uma versão única do Node.js. {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -115,11 +122,9 @@ jobs: uses: actions/setup-node@v1 with: node-version: '12.x' - - run: npm install + - run: npm ci - run: npm run build --if-present - run: npm test - env: - CI: true ``` {% endraw %} @@ -135,7 +140,7 @@ Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, v 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). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -149,7 +154,7 @@ steps: 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)". {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -165,7 +170,7 @@ steps: 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). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -178,7 +183,7 @@ steps: 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*. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -200,7 +205,7 @@ No exemplo abaixo, o segredo `NPM_TOKEN` armazena o token de autenticação npm. 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). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -219,7 +224,7 @@ steps: O exemplo acima cria um arquivo *.npmrc* com o conteúdo a seguir: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -230,7 +235,7 @@ always-auth=true Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar dependências usando uma chave única e restaurar as dependências ao executar futuros fluxos de trabalho usando a ação `cache`. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -255,7 +260,7 @@ steps: 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. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md index 13a1c1bb0f..978cc88c47 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md @@ -8,6 +8,9 @@ versions: authors: - potatoqualitee type: 'tutorial' +topics: + - 'CI' + - 'Powershell' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-python.md b/translations/pt-BR/content/actions/guides/building-and-testing-python.md index 09567d6ee3..02e02048d7 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-python.md @@ -8,6 +8,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ O {% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de tra Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. {% raw %} -```yaml +```yaml{:copy} nome: Pacote do Python em: [push] @@ -94,7 +97,7 @@ O {% data variables.product.prodname_dotcom %} é compatível com a sintaxe sem #### Usar várias versões do Python {% raw %} -```yaml +```yaml{:copy} nome: Pacote Python em: [push] @@ -126,7 +129,7 @@ trabalhos: 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. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -158,7 +161,7 @@ Se especificar uma versão do Python que estiver indisponível, `setup-python` o 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)." {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -196,7 +199,7 @@ Os executores hospedados em {% data variables.product.prodname_dotcom %} têm in 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". {% raw %} -```yaml +```yaml{:copy} etapas: - usa: actions/checkout@v2 - nome: Configurar Python @@ -213,7 +216,7 @@ etapas: Depois de atualizar o `pip`, um o próximo passo típico é instalar as dependências de *requirements.txt*. {% raw %} -```yaml +```yaml{:copy} etapas: - usa: actions/checkout@v2 - nome: Configurar Python @@ -234,7 +237,7 @@ Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, v 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). {% raw %} -```yaml +```yaml{:copy} etapas: - usa: actions/checkout@v2 - nome: Setup Python @@ -271,7 +274,7 @@ Você pode usar os mesmos comandos usados localmente para criar e testar seu có 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/). {% raw %} -```yaml +```yaml{:copy} etapas: - usa: actions/checkout@v2 - nome: Set up Python @@ -295,7 +298,7 @@ etapas: 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/). {% raw %} -```yaml +```yaml{:copy} etapas: - usa: actions/checkout@v2 - nome: Configurar Python @@ -318,7 +321,7 @@ etapas: 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/). {% raw %} -```yaml +```yaml{:copy} nome: Pacote Python em: [push] @@ -352,7 +355,7 @@ Você pode fazer o upload de artefatos para visualização após a conclusão de 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). {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -365,26 +368,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} ``` {% endraw %} @@ -395,7 +398,7 @@ Você pode configurar o seu fluxo de trabalho para publicar seu pacote de Python Você pode armazenar qualquer token de acesso ou credenciais necessárias para publicar seu pacote usando segredos. O exemplo a seguir cria e publica um pacote no PyPI usando `twine` e `dist`. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". {% raw %} -```yaml +```yaml{:copy} Nome: Fazer o upload no pacote Python em: diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md index 3caf3699d8..e377a8d1b2 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md @@ -6,6 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CI' + - 'Ruby' --- {% data reusables.actions.enterprise-beta %} @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -63,7 +63,7 @@ jobs: A maneira mais fácil de especificar uma versão do Ruby é usar a ação `ruby/setup-ruby` fornecida pela organização Ruby no GitHub. A ação adiciona qualquer versão do Ruby compatível com `PATH` para cada tarefa executada em um fluxo de trabalho. Para mais informações, consulte [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Usar a ação `ruby/setup-ruby` do Ruby ou a ação `/setup-ruby` do GitHubt é a forma recomendada de usar o Ruby com o GitHub Actions porque garante um comportamento consistente entre diferentes executores e versões do Ruby. +Usar a ação `ruby/setup-ruby` do Ruby é a forma recomendada de usar o Ruby com o GitHub Actions porque garante um comportamento consistente entre executores diferentes e versões diferentes do Ruby. A ação `setup-ruby` toma uma versão Ruby como uma entrada e configura essa versão no executor. @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index 046f307f62..30ce37c6ef 100644 --- a/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -10,6 +10,8 @@ redirect_from: versions: free-pro-team: '*' type: 'tutorial' +topics: + - 'Fluxos de trabalho' --- ### Sobre a memorização das dependências do fluxo de trabalho @@ -68,7 +70,7 @@ Para obter mais informações, consulte [`ações/cache`](https://github.com/act Este exemplo cria uma nova cache quando são alterados os pacotes no arquivo `package-lock.json` ou quando é alterado o sistema operacional do executor. A chave da cache usa contextos e expressões para gerar uma chave que inclui o sistema operacional do executor e um hash SHA-256 do arquivo `package-lock.json` file. {% raw %} -```yaml +```yaml{:copy} nome : Memorização com npm em: push @@ -124,14 +126,14 @@ Uma chave da cache pode incluir quaisquer contextos, funções, literais e opera Usar expressões para criar uma `chave` permite que você crie automaticamente uma nova cache quando as dependências forem alteradas. Por exemplo, você pode criar uma `chave` usando uma expressão que calcula o hash de um arquivo `package-lock.json` de npm. {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %} avalia a expressão `hash "package-lock.json"` para derivar a `chave` final. -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ Você pode fornecer uma lista de chaves de restauração a serem usadas quando h #### Exemplo do uso de múltiplas chaves de restauração {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | O executor avalia as expressões, que resolvem essas `chaves de restauração`: {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md index cd9b89ae89..691710b3c7 100644 --- a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md @@ -10,6 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% da {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} nome: exemplo de serviço PostgreSQL em: push @@ -94,7 +97,7 @@ trabalhos: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} trabalhos: # Etiqueta do trabalho do contêiner container-job: @@ -124,7 +127,7 @@ trabalhos: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} etapas: # Faz o download de uma cópia do código no seu repositório antes de executar testes de CI - nome: Verifica o código do repositório @@ -159,7 +162,7 @@ Ao executar um trabalho diretamente na máquina executora, você deverá mapear {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} nome: Exemplo de serviço do PostgreSQL em: push @@ -220,7 +223,7 @@ trabalhos: O fluxo de trabalho mapeia a porta 5432 no contêiner de serviço do PostgreSQL com o host do Docker. Para obter mais informações sobre a palavra-chave `portas`, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". -```yaml +```yaml{:copy} trabalhos: # Etiqueta do trabalho executor runner-job: @@ -251,7 +254,7 @@ trabalhos: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} etapas: # Faz o download de uma cópia do código no seu repositório antes de executar testes de CI - nome: Verifica o código do repositório @@ -287,7 +290,7 @@ Você pode modificar o *client.js* para incluir qualquer operação do PostgreSQ {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md b/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md index 5dfa890c32..1c47ed0680 100644 --- a/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md +++ b/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md @@ -10,6 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% da {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} nome: exemplo do contêiner Redis em: push @@ -91,7 +94,7 @@ trabalhos: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} trabalhos: # Etiqueta do trabalho do contêiner container-job: @@ -118,7 +121,7 @@ trabalhos: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} etapas: # Faz o download de uma cópia do código no seu repositório antes de executar testes de CI - nome: Verifica o código do repositório @@ -152,7 +155,7 @@ Ao executar um trabalho diretamente na máquina executora, você deverá mapear {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} nome: Exemplo do executor do Redis em: push @@ -210,7 +213,7 @@ trabalhos: O fluxo de trabalho mapeia a porta 6379 no contêiner de serviço do Redis com o host do Docker. Para obter mais informações sobre a palavra-chave `portas`, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)". -```yaml +```yaml{:copy} trabalhos: # Etiqueta do trabalho executor runner-job: @@ -238,7 +241,7 @@ trabalhos: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} etapas: # Faz o download de uma cópia do código no seu repositório antes de executar os testes de CI - nome: Verifica o código do repositório @@ -274,7 +277,7 @@ Você pode modificar o *client.js* para incluir qualquer operação necessária {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // Cria um novo cliente Redis diff --git a/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md index e2272a0061..16887e98f5 100644 --- a/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md b/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md index 0e140cf995..503d8c6b8a 100644 --- a/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Serviço do aplicativo Azure' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md index f3727e523d..9d98112c96 100644 --- a/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'CD' + - 'Containers' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/index.md b/translations/pt-BR/content/actions/guides/index.md index 3b3df1b640..1f88adb201 100644 --- a/translations/pt-BR/content/actions/guides/index.md +++ b/translations/pt-BR/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/pt-BR/content/actions/guides/publishing-docker-images.md b/translations/pt-BR/content/actions/guides/publishing-docker-images.md index f8445c5ffd..c70412f396 100644 --- a/translations/pt-BR/content/actions/guides/publishing-docker-images.md +++ b/translations/pt-BR/content/actions/guides/publishing-docker-images.md @@ -7,6 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'Empacotando' + - 'Publicar' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -46,7 +51,7 @@ Neste guia, usaremos a ação `build-push-action` do Docker para criar a imagem No exemplo do fluxo de trabalho abaixo, usamos a ação `build-push-action` do Docker para criar a imagem e, se a construção for bem-sucedida, faça o push da imagem criada para o Docker Hub. -Para fazer push para o Docker Hub, você deverá ter uma conta Docker Hub e ter criado um repositório Docker Hub. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation. +Para fazer push para o Docker Hub, você deverá ter uma conta Docker Hub e ter criado um repositório Docker Hub. Para obter mais informações, consulte "[Fazer push de uma imagem de contêiner do Docker para o Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" na documentação do Docker. As opções `build-push-action` necessárias para o Docker Hub são: @@ -54,7 +59,7 @@ As opções `build-push-action` necessárias para o Docker Hub são: * `repositório`: Seu repositório do Docker Hub no formato `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`. {% raw %} -```yaml +```yaml{:copy} nome: Publicar imagem do Docker em: versão: @@ -92,7 +97,7 @@ As opções de `build-push-action` necessárias para {% data variables.product.p * `repositório`: Deve ser definido no formato `OWNER/REPOSITORY/IMAGE_NAME`. Por exemplo, para uma imagem denominada `octo-image` armazenada no {% data variables.product.prodname_dotcom %} em `http://github. Um/octo-org/octo-repo`, a opção `repositório` deve ser definida como `octo-org/octo-repo/octo-image`. {% raw %} -```yaml +```yaml{:copy} nome: Publish Docker image em: versão: @@ -125,7 +130,7 @@ Em um único fluxo de trabalho, você pode publicar sua imagem do Docker em vár O exemplo do fluxo de trabalho a seguir usa as etapas `build-push-action` das seções anteriores ("[Publicar imagens para o Docker Hub](#publishing-images-to-docker-hub)" e "[Publicar imagens em {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para criar um único fluxo de trabalho que faça push em ambos os registros. {% raw %} -```yaml +```yaml{:copy} nome: Publicar imagem do Docker em: versão: diff --git a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md index 674e789539..bfb0058db5 100644 --- a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md @@ -8,6 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Empacotando' + - 'Publicar' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ Cada vez que você criar uma nova versão, você poderá acionar um fluxo de tra É possível definir um novo repositório do Maven no bloco de publicação do seu arquivo _build.gradle_ que aponta para o repositório de pacotes. Por exemplo, se você estava fazendo uma implementaão no Central Repositório do Maven por meio do projeto de hospedagem OSSRH, seu _build.gradle_ poderá especificar um repositório com o nome `"OSSRH"`. {% raw %} -```groovy +```groovy{:copy} publicando { ... @@ -67,7 +72,7 @@ Na etapa de implementação, você deverá definir variáveis de ambiente para o {% raw %} -```yaml +```yaml{:copy} nome: Publicar pacote no Repositório Central do Maven em: versão: @@ -105,7 +110,7 @@ O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura Por exemplo, se sua organização é denominado "octocat" e seu repositório é denominado de "hello-world", a configuração do {% data variables.product.prodname_registry %} no _build.gradle_ será parecida ao exemplo abaixo. {% raw %} -```groovy +```groovy{:copy} publicando { ... @@ -126,7 +131,7 @@ publicando { Com essa configuração, é possível criar um fluxo de trabalho que publica seu pacote no Repositório Central do Maven ao executar o comando `publicação do gradle`. {% raw %} -```yaml +```yaml{:copy} nome: Publicar pacote nos pacotes do GitHub em: versão: @@ -162,7 +167,7 @@ Por exemplo, se fizer a implementação no Repositório Central por meio do proj Se sua organização for denominada "octocat" e seu repositório for denominado "hello-world", a configuração de {% data variables.product.prodname_registry %} em _build.gradle_ será parecida ao exemplo abaixo. {% raw %} -```groovy +```groovy{:copy} publicando { ... @@ -191,7 +196,7 @@ publicando { Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote no Repositório Central do Maven e em {% data variables.product.prodname_registry %}, executando o comando `publicação do gradle`. {% raw %} -```yaml +```yaml{:copy} nome: Publicar pacote no Repositório Central do Maven e nos Pacotes do GitHub em: versão: diff --git a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md index a29d017411..9d9a8d6f64 100644 --- a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md @@ -8,6 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Empacotando' + - 'Publicar' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +52,7 @@ Neste fluxo de trabalho, você pode usar a ação `setup-java`. Esta ação inst Por exemplo, se você estava implantando no Repositório Central do Maven por meio do projeto de hospedagem OSSRH, seu _pom.xml_ poderia especificar um repositório de gerenciamento de distribuição com o `id` de `ossrh`. {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ Na etapa de implementação, você deverá definir as variáveis de ambiente par {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ Para um projeto baseado no Maven, você pode usar essas configurações ao criar Por exemplo, se sua organização é denominada "octocat" e seu repositório é denominado "hello-world", a configuração do {% data variables.product.prodname_registry %} no _pom.xml_ será parecida ao exemplo abaixo. {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ Por exemplo, se sua organização é denominada "octocat" e seu repositório é Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote em {% data variables.product.prodname_registry %}, fazendo uso do _settings.xml_ gerado automaticamente. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ Você pode publicar seus pacotes no Repositório Central Maven e em {% data vari Certifique-se de que seu arquivo _pom.xml_ inclui um repositório de gerenciamento de distribuição tanto para seu repositório {% data variables.product.prodname_dotcom %} como para o seu provedor de Repositório Central do Maven. Por exemplo, se você fizer a implementação em um Repositório Central por meio do projeto de hospedagem OSSRH, é possível que você deseje especificá-la em um repositório de gerenciamento de distribuição com o `id` definido como `ossrh`. Além disso, você pode desejar especificar {% data variables.product.prodname_registry %} em um repositório de gerenciamento de distribuição com o `id` definido como `github`. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md index 01b61818fd..7bcfc61e9b 100644 --- a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md @@ -8,6 +8,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'tutorial' +topics: + - 'Empacotando' + - 'Publicar' + - 'Nó' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} @@ -53,7 +59,7 @@ Se você estiver publicando um pacote que inclui um prefixo de escopo, inclua o Este exemplo armazena o segredo `NPM_TOKEN` na variável de ambiente `NODE_AUTH_TOKEN`. Quando a ação `setup-node` cria um arquivo *.npmrc*, ela faz referência ao token da variável de ambiente `NODE_AUTH_TOKEN`. {% raw %} -```yaml +```yaml{:copy} nome: Pacote Node.js em: versão: @@ -77,7 +83,7 @@ trabalhos: No exemplo acima, a ação `setup-node` cria um arquivo *.npmrc* no executor com o conteúdo a seguir: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -87,14 +93,33 @@ always-auth=true Cada vez que você criar uma nova versão, você poderá acionar um fluxo de trabalho para publicar o seu pacote. O fluxo de trabalho no exemplo abaixo é executado sempre que ocorre o evento `versão` com o tipo `criado`. O fluxo de trabalho publica o pacote em {% data variables.product.prodname_registry %} se o teste de CI for aprovado. -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 %}. Para obter mais informações, consulte [`npm-scope`](https://docs.npmjs.com/misc/scope) na documentação do npm. +#### Configurar o repositório de destino -Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". +Se você não fornecer a chave do `repositório` no seu arquivo *package.json*, {% data variables.product.prodname_registry %} irá publicar um pacote no repositório de {% data variables.product.prodname_dotcom %} especificado no campo `nome` do arquivo *package.json*. Por exemplo, um pacote denominado `@my-org/test` é publicado no `my-org/test` repositório de {% data variables.product.prodname_dotcom %}. + +No entanto, se você fornecer a chave `repositório`, o repositório nessa chave será usado como o registro de npm de destino para {% data variables.product.prodname_registry %}. Por exemplo, publicar os resultados *package.json* abaixo em um pacote denominado `my-amazing-package` publicado no repositório `octocat/meu-repo` de {% data variables.product.prodname_dotcom %}. + +```json +{ + "name": "@octocat/my-amazing-package", + "repository": { + "type": "git", + "url": "https://github.com/octocat/my-other-repo.git" + }, +``` + +#### Efetuar a autenticação no repositório de destino + +Para efetuar a autenticação no registro de {% data variables.product.prodname_registry %} no seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN` do seu repositório. Ele é criado automaticamente e tem permissão de _leitura_ e _gravação_ para pacotes no repositório, em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)". + +Se você quiser publicar seu pacote em um repositório diferente, você deverá usar um token de acesso pessoal (PAT) que tenha permissão para escrever pacotes no repositório de destino. 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)". + +#### Exemplo de fluxo de trabalho Este exemplo armazena o segredo `GITHUB_TOKEN` na variável de ambiente `NODE_AUTH_TOKEN`. Quando a ação `setup-node` cria um arquivo *.npmrc*, ela faz referência ao token da variável de ambiente `NODE_AUTH_TOKEN`. {% raw %} -```yaml +```yaml{:copy} nome: Pacote Node.js em: versão: @@ -120,7 +145,7 @@ trabalhos: A ação `setup-node` cria um arquivo *.npmrc* no executor. Ao usar a entrada do `escopo` para a ação `setup-node`, o arquivo *.npmrc* incluirá o prefixo do escopo. Por padrão, a ação `setup-node` define o escopo no arquivo *.npmrc* na conta que contém esse arquivo do fluxo de trabalho. -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -131,25 +156,25 @@ always-auth=true Se você usar o gerenciador de pacotes Yarn, você poderá instalar e publicar pacotes usando o Yarn. {% raw %} -```yaml -nome: Pacote Node.js -em: - versão: - tipos: [created] -trabalhos: - criar: +```yaml{:copy} +name: Node.js Package +on: + release: + types: [created] +jobs: + build: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - # Configura o arquivo .npmrc a ser publicado no npm - - usa: actions/setup-node@v1 - com: + steps: + - uses: actions/checkout@v2 + # Setup .npmrc file to publish to npm + - uses: actions/setup-node@v1 + with: node-version: '12.x' registry-url: 'https://registry.npmjs.org' - # Tem como padrão o usuário ou a organização que é proprietário do arquivo do fluxo de trabalho - escopo: '@octocat' - - executar: yarn - - executar: yarn publish + # Defaults to the user or organization that owns the workflow file + scope: '@octocat' + - run: yarn + - run: yarn publish env: NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} ``` @@ -176,7 +201,7 @@ Ao usar a entrada do `escopo` para a ação `setup-node`, esta cria um arquivo * Este fluxo de trabalho chama a ação `setup-node` duas vezes. Cada vez que a ação `setup-node` é executada, ela substitui o arquivo *.npmrc*. O arquivo *.npmrc* faz referência ao token que permite que você execute operações autenticadas com o registro do pacote a partir da variável de ambiente `NODE_AUTH_TOKEN`. O fluxo de trabalho define a variável de ambiente `NODE_AUTH_TOKEN` toda vez que o comando `publicação do npm` é executado. Primeiro com um token para publicar no npm (`NPM_TOKEN`) e, em seguida, com um token para publicar em {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`). {% raw %} -```yaml +```yaml{:copy} nome: Pacote Node.js em: versão: diff --git a/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 4cad6cca72..a41ce28c2d 100644 --- a/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -12,6 +12,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Fluxos de trabalho' + - 'CI' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md index fdc3cf0894..263349f6bb 100644 --- a/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -12,6 +12,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Fluxos de trabalho' --- {% data reusables.actions.enterprise-beta %} @@ -79,7 +81,7 @@ Esse exemplo mostra como criar um fluxo de trabalho para um projeto Node.js que O fluxo de trabalho faz o upload dos artefatos de produção no diretório `dist`, mas exclui todos os arquivos de markdown. Ele também e faz o upload do relatório de `code-coverage.html` como outro artefato. -```yaml +```yaml{:copy} name: Node CI on: [push] @@ -114,7 +116,7 @@ jobs: Você pode definir um período de retenção personalizado para artefatos individuais criados por um fluxo de trabalho. Ao usar um fluxo de trabalho para criar um novo artefato, você pode usar `retention-days` com a ação `upload-artifact`. Este exemplo demonstra como definir um período de retenção personalizado de 5 dias para o artefato denominado `my-artifact`: -``` +```yaml{:copy} - name: 'Upload Artifact' uses: actions/upload-artifact@v2 with: @@ -183,7 +185,7 @@ O Job 3 (Trabalho 3) mostra o resultado carregado no trabalho anterior: A operação matemática completa executada nesse fluxo de trabalho é `(3 + 7) x 9 = 90`. -```yaml +```yaml{:copy} name: Share data between jobs on: [push] 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 index 08f7e6dd7a..b67b94a213 100644 --- 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 @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview --- {% data reusables.actions.enterprise-beta %} 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 134c183c82..6362583af6 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 @@ -38,7 +38,7 @@ Se não for prático definir as variáveis do ambiente, você poderá definir as Um exemplo de configuração de proxy _.env_ é mostrado abaixo: -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index fd1a28aba5..1adb41d31a 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -64,8 +64,11 @@ Estas etiquetas operam cumulativamente. Portanto, as etiquetas de um executor au ### Precedência de encaminhamento para executores auto-hospedados -Se você usar executores no nível do repositório e da organização, {% data variables.product.prodname_dotcom %} seguirá uma ordem de precedência ao encaminhar trabalhos para os executores auto-hospedados: +Ao encaminhar um trabalho para um executor auto-hospedado, {% data variables.product.prodname_dotcom %} procura um executor que corresponde às etiquetas `runs-on` do trabalho: -1. As etiquetas `runs-on` do trabalho são processadas. {% data variables.product.prodname_dotcom %}, em seguida, tenta localizar um executor que corresponda aos requisitos da etiqueta: -2. O trabalho é enviado para um executor do nível de repositório que corresponde à etiqueta do trabalho. Se nenhum executor no nível do repositório estiver disponível (ocupado, off-line ou sem etiquetas correspondentes): -3. O trabalho será enviado para um executor do nível da organização que corresponde às etiquetas do trabalho. Se nenhum executor de nível de organização estiver disponível, ocorrerá uma falha na solicitação do trabalho em razão de erro. +1. {% data variables.product.prodname_dotcom %} primeiro procura um executor no nível do repositório, depois no nível da organização{% if currentVersion ver_gt "enterprise-server@2.21" %} e, por fim, no nível empresarial{% endif %}. +2. Em seguida, o trabalho é enviado para o primeiro executor correspondente que está on-line e inativo. + - Se todos os executores on-line estiverem ocupados, o trabalho será agendado no nível com o maior número de executores on-line. + - Se todos os runners correspondentes estiverem off-line, a tarefa será listada no nível com o maior número de executores off-line correspondentes. + - Se não houver executores correspondentes em qualquer nível, o trabalho falhará. + - Se o trabalho permanecer na fila por mais de 24 horas, o trabalho falhará. diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index 9fa1e6562f..bb78b095c5 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -10,21 +10,22 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: + - + title: Ambientes, regras de proteção do ambiente e segredos de ambiente (beta) + date: '2020-12-15' + href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ - title: Visualização do fluxo de trabalho date: '2020-12-08' @@ -33,10 +34,6 @@ changelog: title: Remover comandos set-env e add-path em 16 de novembro date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Os últimos fluxos de trabalho do Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ @@ -73,7 +70,7 @@ versions: {% render 'code-example-card' for actionsCodeExamples as example %}
    - +
    {% octicon "search" width="24" %}
    diff --git a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md index 84341e9610..7a5285b3b0 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,7 +5,9 @@ intro: '{% data variables.product.prodname_actions %} foram projetados para ajud versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Princípios básicos --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md index 64a0e3d24b..a444cc3511 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Princípios básicos' --- {% data reusables.actions.enterprise-beta %} @@ -68,7 +70,7 @@ etapas: #### Usar SHAs -Se você precisar de uma versão mais confiável, você deverá usar o valor de SHA associado à versão da ação. Os SHAs são imutáveis e, portanto, mais confiáveis que tags ou branches. No entanto, esta abordagem significa que você não receberá automaticamente atualizações de uma ação, incluindo correções de erros importantes e atualizações de segurança. Este exemplo tem como alvo a ação do SHA: +Se você precisar de uma versão mais confiável, você deverá usar o valor de SHA associado à versão da ação. Os SHAs são imutáveis e, portanto, mais confiáveis que tags ou branches. No entanto, esta abordagem significa que você não receberá automaticamente atualizações de uma ação, incluindo correções de erros importantes e atualizações de segurança. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Você deve usar o valor completo do SHA de um commit e não um valor abreviado. {% endif %}Este exemplo aponta para o SHA de uma ação: ```yaml etapas: diff --git a/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md index b92cf8d637..096422b8b5 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -9,7 +9,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Princípios básicos --- {% data reusables.actions.enterprise-beta %} @@ -147,7 +149,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ```
    @@ -180,7 +182,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ``` diff --git a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md index e2c8617945..17dc573c37 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -1,24 +1,27 @@ --- -title: Gerenciar fluxos de trabalhos complexos -shortTitle: Gerenciar fluxos de trabalhos complexos -intro: 'Este guia mostra como usar os recursos avançados de {% data variables.product.prodname_actions %}, com gestão de segredo, trabalhos dependentes, cache, matrizes de compilação{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ambientes,{% endif %} e etiquetas.' +title: Managing complex workflows +shortTitle: Managing complex workflows +intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} environments,{% endif %} and labels.' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' +topics: + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Visão Geral +### Overview -Este artigo descreve alguns dos recursos avançados de {% data variables.product.prodname_actions %} que ajudam você a trabalhar criar fluxos de trabalho mais complexos. +This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you work create more complex workflows. -### Armazenar segredos +### Storing secrets -Se os seus fluxos de trabalho usarem dados confidenciais, como senhas ou certificados, você pode salvá-los em {% data variables.product.prodname_dotcom %} como _segredos_ e usá-los nos seus fluxos de trabalho como variáveis de ambiente. Isto significa que você poderá criar e compartilhar fluxos de trabalho sem ter de incorporar valores sensíveis diretamente no fluxo de trabalho de YAML. +If your workflows use sensitive data, such as passwords or certificates, you can save these in {% data variables.product.prodname_dotcom %} as _secrets_ and then use them in your workflows as environment variables. This means that you will be able to create and share workflows without having to embed sensitive values directly in the YAML workflow. -Esta ação de exemplo demonstra como fazer referência a um segredo existente como uma variável de ambiente e enviá-lo como um parâmetro para um comando de exemplo. +This example action demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command. {% raw %} ```yaml @@ -34,13 +37,13 @@ jobs: ``` {% endraw %} -Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". +For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." -### Criar trabalhos dependentes +### Creating dependent jobs -Por padrão, os trabalhos do seu fluxo de trabalho são executadas em paralelo e ao mesmo tempo. Portanto, se você tem um trabalho que só deve ser executado após a conclusão de outro trabalho, você pode usar a palavra-chave `needs` para criar esta dependência. Se um dos trabalhos falhar, todos os trabalhos dependentes serão suprimidos. No entanto, se você precisa que os trabalhos continuem, você pode definir isso usando a declaração condicional [`se`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif). +By default, the jobs in your workflow all run in parallel at the same time. So if you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the [`if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) conditional statement. -Neste exemplo, os trabalhos de `configuração`, `criação` e `teste` executados em série, com `criação` e `teste` sendo dependentes da conclusão bem-sucedida do trabalho que os precede: +In this example, the `setup`, `build`, and `test` jobs run in series, with `build` and `test` being dependent on the successful completion of the job that precedes them: ```yaml jobs: @@ -60,11 +63,11 @@ jobs: - run: ./test_server.sh ``` -Para obter mais informações, consulte [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). +For more information, see [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). -### Usar uma matriz de criação +### Using a build matrix -Você pode usar uma matriz de criação se quiser que seu fluxo de trabalho execute testes em várias combinações de sistemas operacionais, plataformas e linguagens. A matriz de criação é criada usando a palavra-chave `estratégia`, que recebe as opções de compilação como um array. Por exemplo, essa matriz de criação irá executar o trabalho várias vezes, usando diferentes versões do Node.js: +You can use a build matrix if you want your workflow to run tests across multiple combinations of operating systems, platforms, and languages. The build matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this build matrix will run the job multiple times, using different versions of Node.js: {% raw %} ```yaml @@ -81,13 +84,13 @@ jobs: ``` {% endraw %} -Para obter mais informações, consulte [`>jobs..strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). +For more information, see [`jobs..strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). -### Memorizar dependências +### Caching dependencies -Executores hospedados em {% data variables.product.prodname_dotcom %} são iniciados como ambientes novos para cada trabalho. Portanto, se os seus trabalhos reutilizam dependências regularmente, você pode considerar fazer armazenamento em cache desses arquivos para ajudar a melhorar o desempenho. Após a criação do armazenamento em cache, ele fica disponível para todos os fluxos de trabalho no mesmo repositório. +{% data variables.product.prodname_dotcom %}-hosted runners are started as fresh environments for each job, so if your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. Once the cache is created, it is available to all workflows in the same repository. -Este exemplo demonstra como armazenar em cache o diretório `~/.npm`: +This example demonstrates how to cache the ` ~/.npm` directory: {% raw %} ```yaml @@ -106,11 +109,11 @@ jobs: ``` {% endraw %} -Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +For more information, see "Caching dependencies to speed up workflows." -### Usar bancos de dados e contêineres de serviço +### Using databases and service containers -Se sua tarefa exigir um banco de dados ou serviço de cache, você poderá usar a palavra-chave [`serviços`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) para criar um contêiner efêmero para hospedar o serviço; o contêiner resultante ficará disponível em todas as etapas do trabalho e será removido quando o trabalho for concluído. Este exemplo demonstra como um trabalho pode usar `serviços` para criar um contêiner `postgres` e, em seguida, usar o `nó` para conectar-se ao serviço. +If your job requires a database or cache service, you can use the [`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) keyword to create an ephemeral container to host the service; the resulting container is then available to all steps in that job and is removed when the job has completed. This example demonstrates how a job can use `services` to create a `postgres` container, and then use `node` to connect to the service. ```yaml jobs: @@ -132,13 +135,13 @@ jobs: POSTGRES_PORT: 5432 ``` -Para obter mais informações, consulte "[Usar bancos de dados e contêineres de serviço](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)". +For more information, see "[Using databases and service containers](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)." -### Usar etiquetas para encaminhar fluxos de trabalho +### Using labels to route workflows -Esse recurso ajuda você a atribuir tarefas a um executor auto-hospedado específico. Se você quiser ter certeza de que um determinado tipo de executor irá processar seu trabalho, você pode usar etiquetas para controlar os locais onde os trabalhos são executados. Você pode atribuir etiquetas a um corredor auto-hospedado e, em seguida, consultá-las no fluxo de trabalho de YAML, garantindo que o trabalho seja encaminhado de uma forma previsível. +This feature helps you assign jobs to a specific self-hosted runner. If you want to be sure that a particular type of runner will process your job, you can use labels to control where jobs are executed. You can assign labels to a self-hosted runner, and then refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way. -Este exemplo mostra como um fluxo de trabalho pode usar etiquetas para especificar o executor obrigatório: +This example shows how a workflow can use labels to specify the required runner: ```yaml jobs: @@ -146,14 +149,25 @@ jobs: runs-on: [self-hosted, linux, x64, gpu] ``` -Para obter mais informações, consulte ["Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". +For more information, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)." {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Usar ambientes +### Using environments -Você pode configurar ambientes com regras de proteção e segredos. Cada trabalho em um fluxo de trabalho pode fazer referência a um único ambiente. Todas as regras de proteção configuradas para o ambiente têm de ser aprovadas antes que um trabalho de referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)". +You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." {% endif %} -### Próximas etapas +### Using a workflow template -Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Compartilhar fluxos de trabalho com a sua organização](/actions/learn-github-actions/sharing-workflows-with-your-organization)". +{% data reusables.actions.workflow-template-overview %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. If your repository already has existing workflows: In the upper-left corner, click **New workflow**. + ![Create a new workflow](/assets/images/help/repository/actions-new-workflow.png) +1. Under the name of the template you'd like to use, click **Set up this workflow**. + ![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png) + +### Next steps + +To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 624f959e6b..e01f44e11d 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Azure Pipelines' + - 'Migração' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -61,34 +66,34 @@ Azure Pipelines @@ -122,25 +127,25 @@ Azure Pipelines @@ -170,25 +175,25 @@ Azure Pipelines @@ -216,56 +221,56 @@ Azure Pipelines @@ -293,31 +298,31 @@ Azure Pipelines diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index a24bf3bd0a..3fbab301fc 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'CircleCI' + - 'Migração' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -235,47 +240,47 @@ fluxos de trabalho: @@ -386,15 +391,15 @@ fluxos de trabalho: diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 2e7c8a489e..f72c9ce2de 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -5,6 +5,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'GitLab' + - 'Migração' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,12 +340,12 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} @@ -371,7 +376,7 @@ GitLab CI/CD script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -424,12 +429,12 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js tags: - docker ``` diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index fab03b1da1..71c712bc8f 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Jenkins' + - 'Migração' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ O Jenkins permite que se envie criações para um único agente de criação, ou De modo similar, o {% data variables.product.prodname_actions %} pode enviar trabalhos para executores hospedados em {% data variables.product.prodname_dotcom %} ou executores auto-hospedados, e você pode usar as etiquetas para classificar os executores de acordo com vários atributos. A tabela a seguir compara como o conceito de criação distribuída é implementado tanto para o Jenkins e quanto para o {% data variables.product.prodname_actions %}. | Jenkins | {% data variables.product.prodname_actions %} -| ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`agentes`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`executores`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`executores auto-hospedados`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`agentes`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`executores`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`executores auto-hospedados`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### Usar seções para organizar pipelines @@ -51,7 +56,6 @@ O Jenkins divide seus Declarative Pipelines em múltiplas seções. De forma sim | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### Usar diretivas O Jenkins usa diretivas para gerenciar os _Declarative Pipelines_. Essas diretivas definem as características do seu fluxo de trabalho e como ele será executado. A tabela abaixo demonstra como estas diretivas são mapeadas com conceitos dentro do {% data variables.product.prodname_actions %}. @@ -69,7 +73,6 @@ O Jenkins usa diretivas para gerenciar os _Declarative Pipelines_. Essas diretiv | [`entrada`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`quando`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### Usar estágios sequenciais #### Processamento paralelo do trabalho @@ -114,23 +117,23 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %}     @@ -150,25 +153,24 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} @@ -188,30 +190,28 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} @@ -231,26 +231,27 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 1a10100117..d4bb5537ef 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -7,6 +7,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'tutorial' +topics: + - 'Travis CI' + - 'Migração' + - 'CI' + - 'CD' --- ### Introdução @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -155,9 +160,9 @@ git: @@ -207,10 +212,10 @@ Ao trabalhar com diferentes linguagens em {% data variables.product.prodname_act Por exemplo: ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` ### Manuseio de erros em {% data variables.product.prodname_actions %} @@ -271,15 +276,15 @@ script: @@ -345,20 +350,20 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} @@ -378,24 +383,24 @@ Fluxo de trabalho do {% data variables.product.prodname_actions %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 9506977915..8656a0c352 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' +type: overview +topics: + - Segurança --- {% data reusables.actions.enterprise-beta %} @@ -54,11 +56,13 @@ Isso significa que comprometer uma única ação dentro de um fluxo de trabalho Fixar uma ação para um commit SHA de comprimento completo é, atualmente, a única maneira de usar uma ação como uma versão imutável. Fixar um SHA em particular ajuda a mitigar o risco de um ator malicioso adicionar uma porta traseira ao repositório da ação, porque precisariam gerar uma colisão de SHA-1 para uma carga válida do objeto de Git. + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **Aviso:** A versão curta do commit SHA é insegura e nunca deve ser usada para especificar a referência do Git de uma ação. Devido ao modo como funcionam as redes de repositório, qualquer usuário pode bifurcar o repositório e fazer push de um commit criado que colida com o SHA curto. Isso faz com que os clones subsequentes falhem nesse SHA, pois se converte em um commit ambíguo. Como resultado, todos os fluxos de trabalho que usam o SHA encurtado falharão imediatamente. {% endwarning %} + {% endif %} * **Audite o código-fonte da ação** @@ -113,7 +117,7 @@ Você pode usar o log de auditoria para monitorar tarefas administrativas em uma Por exemplo, você pode usar o log de auditoria para monitorar o evento de `action:org.update_actions_secret`, que controla as alterações nos segredos da organização: ![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png) -As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. Para obter mais informações sobre como usar o registro de auditoria, consulte [Revisar o log de auditoria para a sua organização](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". +As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. Para obter mais informações sobre como usar o log de auditoria, consulte [Revisar o log de auditoria para a sua organização](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". #### Eventos para gerenciamento de segredo | Ação | Descrição | @@ -140,4 +144,4 @@ As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_a | `action:org.runner_group_removed` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | | `action:org.runner_group_renamed` | Acionado quando um administrador da organização renomeia um grupo de executores auto-hospedados. | | `action:org.runner_group_runners_added` | Acionada quando um administrador da organização [adiciona um executor auto-hospedado a um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `action:org.runner_group_runners_removed` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | +| `action:org.runner_group_runners_removed` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | diff --git a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 75e45c99f4..acb6685574 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -7,6 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'how_to' --- {% data reusables.actions.enterprise-beta %} @@ -44,10 +45,10 @@ Este procedimento demonstra como criar um modelo de fluxo de trabalho e um arqui runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v2 - - name: Run a one-line script - run: echo Hello from Octo Organization + - name: Run a one-line script + run: echo Hello from Octo Organization ``` 1. Crie um arquivo de metadados dentro do diretório `workflow-templates`. O arquivo de metadados deve ter o mesmo nome do arquivo de fluxo de trabalho, mas em vez da extensão `.yml`, deve-se adicionar `.properties.json`. Por exemplo, este arquivo denominado `octo-organization-ci.properties.json` contém os metadados para um arquivo de fluxo de trabalho denominado `octo-organization-ci.yml`: ```yaml @@ -75,7 +76,7 @@ Para adicionar outro modelo de fluxo de trabalho, adicione seus arquivos ao mesm ![Arquivos do modelo do fluxo de trabalho](/assets/images/help/images/workflow-template-files.png) -### Usar um modelo do fluxo de trabalho +### Usar um modelo de fluxo de trabalho da sua organização Este procedimento demonstra como um membro da sua organização pode localizar e usar um modelo de fluxo de trabalho para criar um novo fluxo de trabalho. Os modelos de fluxo de trabalho de uma organização podem ser usados por qualquer pessoa que seja integrante da organização. diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/pt-BR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index 64447b964c..28d2d75263 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///fluxos de trabalho// Este exemplo de Markdown adiciona um crachá de status para um fluxo de trabalho com o nome "Cumprimente a Todos". O proprietário `do repositório é a ações` organização e o nome repositório `é `hello-world . -``` +```markdown ! [nome do fluxo de trabalho de exemplo] (https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ Este exemplo de Markdown adiciona um crachá de status para um fluxo de trabalho Este exemplo de Markdown adiciona um crachá de status para um fluxo de trabalho com o caminho do arquivo `.github/workflows/main.yml`. O proprietário `do repositório é a ações` organização e o nome repositório `é `hello-world . -``` +```markdown ! [exemplo caminho do arquivo de fluxo de trabalho] (https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ Este exemplo de Markdown adiciona um crachá de status para um fluxo de trabalho Este exemplo de Markdown adiciona um crachá de status para uma filial com o nome `recurso-1`. -``` +```markdown ! [parâmetro de ramo de exemplo] (https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ Este exemplo de Markdown adiciona um crachá de status para uma filial com o nom Este exemplo de Markdown adiciona um crachá que exibe o status das corridas de fluxo de trabalho desencadeadas pelo `pull_request` evento. -``` +```markdown ! [parâmetro de evento de exemplo] (https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md index ebc6a5002c..34b0d4154f 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -18,7 +18,7 @@ Para executar um fluxo de trabalho manualmente, o fluxo de trabalho deve ser con Para acionar o evento `workflow_dispatch` em {% data variables.product.prodname_dotcom %}, seu fluxo de trabalho deve estar no branch-padrão. Siga estas etapas para acionar manualmente uma execução do fluxo de trabalho. -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index d762304a99..cb0be03b8a 100644 --- a/translations/pt-BR/content/actions/quickstart.md +++ b/translations/pt-BR/content/actions/quickstart.md @@ -7,6 +7,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - 'Princípios básicos' --- {% data reusables.actions.enterprise-beta %} @@ -66,9 +69,9 @@ Fazer commit do arquivo de fluxo de trabalho no repositório aciona o evento `pu {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### Mais fluxos de trabalho iniciais +### Mais modelos de fluxo de trabalho -O {% data variables.product.prodname_dotcom %} fornece modelos de fluxo de trabalho pré-configurados com os quais você pode começar para automatizar ou criar fluxos de trabalho de integração contínua. Você pode pesquisar a lista completa de modelos de fluxo de trabalho no repositório de {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` e no repositório {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} ### Próximas etapas @@ -120,7 +123,7 @@ Imprimir "Olá, mundo!" é uma ótima maneira de explorar a configuração e a s {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Na barra lateral esquerda, clique no fluxo de trabalho que você deseja executar. +1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja executar. ![Selecione o trabalho "say hello"](/assets/images/help/repository/say-hello-job.png) 1. À direita, clique no menu suspenso **Executar fluxo de trabalho** e clique em **Executar fluxo de trabalho**. Opcionalmente, você pode inserir uma mensagem personalizada na entrada "Pessoa a saudar" antes de executar o fluxo de trabalho. ![Acionar o fluxo de trabalho manual](/assets/images/help/repository/manual-workflow-trigger.png) @@ -129,15 +132,15 @@ Imprimir "Olá, mundo!" é uma ótima maneira de explorar a configuração e a s 1. Na barra lateral esquerda, clique no trabalho "say_hello". ![Lista de trabalhos do fluxo de trabalho](/assets/images/help/repository/workflow-job-listing.png) 1. Nos registros do fluxo de trabalho, expanda a seção 'Run echo "Hello World!"'. - ![Detalhe do fluxo de trabalho(/assets/images/help/repository/workflow-log-listing.png) + ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png) -### Mais fluxos de trabalho iniciais +### More workflow templates -{% data variables.product.prodname_dotcom %} fornece modelos de fluxo de trabalho pré-configurados dos quais você pode partir para automatizar ou criar fluxos de trabalho de integração contínua. Você pode pesquisar a lista completa de modelos de fluxo de trabalho no repositório {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows){% else %} repositorio `actions/starter-workflows` em {% data variables.product.product_location %}{% endif %}. +{% data reusables.actions.workflow-template-overview %} -### Próximas etapas +### Next steps -O fluxo de trabalho hello-world que você acabou de adicionar é um exemplo simples de um fluxo de trabalho acionado manualmente. Esse é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}. O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos. O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}: +The hello-world workflow you just added is a simple example of a manually triggered workflow. Esse é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}. O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos. O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}: - "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para um tutorial detalhado - "[Guides](/actions/guides)" para casos específicos de usos e exemplos diff --git a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 654b6591e2..a26756e5f2 100644 --- a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,6 +75,10 @@ Para usar a sintaxe de propriedade de desreferência, o nome da propriedade deve - começar com `a-Z` ou `_`; - ser seguido por `a-Z` `0-9` `-` ou `_`. +#### Determinar quando usar contextos + +{% data reusables.github-actions.using-context-or-environment-variables %} + #### Contexto `github` O contexto `github` context contém informações sobre a execução do fluxo de trabalho e sobre o evento que a acionou. Você pode ler a maioria dos dados de contexto `github` em variáveis de ambiente. Para obter mais informações sobre as variáveis de ambiente, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)". @@ -107,15 +111,14 @@ O contexto `github` context contém informações sobre a execução do fluxo de O contexto `env` contém variáveis de ambiente que foram definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações sobre como configurar variáveis de ambiente em seu fluxo de trabalho, consulte "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)". -A sintaxe de contexto `env` permite que você use o valor de uma variável de ambiente no seu arquivo de fluxo de trabalho. Se você desejar usar o valor de uma variável de ambiente dentro de um executor, use o método normal do sistema operacional do executor para ler as variáveis de ambiente. +A sintaxe de contexto `env` permite que você use o valor de uma variável de ambiente no seu arquivo de fluxo de trabalho. Você pode usar o contexto `env` no valor de qualquer chave em uma **etapa**, exceto para as chaves `id` e `uses`. Para obter mais informações sobre a sintaxe da etapa, consulte "[Sintaxe do fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". -Você só pode usar o contexto `env` no valor de `com` e as chaves do `nome` ou em uma condição `se` da etapa. Para obter mais informações sobre a sintaxe da etapa, consulte "[Sintaxe do fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". +Se você desejar usar o valor de uma variável de ambiente dentro de um executor, use o método normal do sistema operacional do executor para ler as variáveis de ambiente. | Nome da propriedade | Tipo | Descrição | | ---------------------- | -------- | ----------------------------------------------------------------------------------------------------------------- | | `env` | `objeto` | Esse contexto altera cada etapa em um trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. | -| `env.` | `string` | O valor de uma variável de ambiente específica. | - +| `env.` | `string` | O valor de uma variável de ambiente específica. | #### Contexto `trabalho` @@ -183,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -345,7 +348,7 @@ O valor para `array` pode ser uma array ou uma string. Todos os valores na `arra `join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted' -#### toJson +#### toJSON `toJSON(value)` @@ -355,35 +358,56 @@ Retorna uma bela representação JSON de `value`. Você pode usar essa função `toJSON(job)` pode retornar `{ "status": "Success" }` -#### fromJson +#### fromJSON `fromJSON(value)` -Retorna um objeto JSON para `valor`. Você pode usar esta função para fornecer um objeto JSON como uma expressão avaliada. +Retorna um objeto do JSON ou tipo de dado do JSON para `valor`. Você pode usar esta função para fornecer um objeto do JSON como uma expressão avaliada ou para converter variáveis de ambiente de uma string. -##### Exemplo +##### Exemplo que retorna um objeto do JSON Este fluxo de trabalho define uma matriz JSON em um trabalho, e o passa para o próximo trabalho usando uma saída do `fromJSON`. {% raw %} ```yaml -nome: criar -em: push -trabalhos +name: build +on: push +jobs: job1: runs-on: ubuntu-latest - saídas: - matriz: ${{ steps.set-matrix.outputs.matrix }} - etapas: + outputs: + matrix: ${{ steps.set-matrix.outputs.matrix }} + steps: - id: set-matrix - executar: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" + run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" job2: needs: job1 runs-on: ubuntu-latest - estratégia: - matriz: ${{fromJson(needs.job1.outputs.matrix)}} - etapas: - - executar: criar + strategy: + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} + steps: + - run: build +``` +{% endraw %} + +##### Exemplo que retorna um tipo de dado do JSON + +Este fluxo de trabalho usa `fromJSON` para converter variáveis de ambiente de uma string para um número inteiro ou booleano. + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... ``` {% endraw %} @@ -391,7 +415,7 @@ trabalhos `hashFiles(path)` -Retorna um único hash para o conjunto de arquivos que correspondem ao padrão do `caminho`. Você pode fornecer um único padrão de `caminho` ou vários padrões de `caminho` separados por vírgulas. O `caminho` é relativo ao diretório `GITHUB_WORKSPACE` e pode incluir apenas arquivos dentro do `GITHUB_WORKSPACE`. Essa função calcula um hash SHA-256 individual para cada arquivo correspondente e, em seguida, usa esses hashes para calcular um hash SHA-256 final para o conjunto de arquivos. Para obter mais informações sobre o SHA-256, consulte "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)". +Retorna um único hash para o conjunto de arquivos que correspondem ao padrão do `caminho`. Você pode fornecer um único padrão de `caminho` ou vários padrões de `caminho` separados por vírgulas. O `caminho` é relativo ao diretório `GITHUB_WORKSPACE` e pode incluir apenas arquivos dentro do `GITHUB_WORKSPACE`. Essa função calcula uma hash SHA-256 individual para cada arquivo correspondente e, em seguida, usa esses hashes para calcular um hash SHA-256 final para o conjunto de arquivos. Para obter mais informações sobre o SHA-256, consulte "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)". Você pode usar a correspondência de padrão de caracteres para corresponder os nomes dos arquivos. No Windows, a correspondência do padrão diferencia maiúsculas e minúsculas. Para obter mais informações sobre caracteres de correspondência de padrões suportados, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)". diff --git a/translations/pt-BR/content/actions/reference/environment-variables.md b/translations/pt-BR/content/actions/reference/environment-variables.md index e25c71a480..fb84cff15b 100644 --- a/translations/pt-BR/content/actions/reference/environment-variables.md +++ b/translations/pt-BR/content/actions/reference/environment-variables.md @@ -21,15 +21,25 @@ versions: Para definir as variáveis do ambiente personalizadas, você deverá especificar as variáveis no arquivo do fluxo de trabalho. Você pode definir as variáveis de ambiente para uma etapa, trabalho ou para todo um fluxo de trabalho, usando as palavras-chave [`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). Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)". ```yaml -passos: - - nome: Olá mundo - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +Para usar o valor de uma variável de ambiente em um arquivo do fluxo de trabalho, você deve usar o [contexto` env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). Se você deseja usar o valor de uma variável de ambiente dentro de um executor, você poderá usar o método normal do sistema operacional do executor para ler variáveis de ambiente. + +Se você usar a chave `executar` do arquivo de fluxo de trabalho para ler variáveis de ambiente de dentro do sistema operacional do executor (como mostrado no exemplo acima), a variável será substituída no sistema operacional do executor depois que a tarefa for enviada para o executor. Para outras partes de um arquivo de fluxo de trabalho, você deve usar o contexto `env` para ler variáveis de ambiente. Isso ocorre porque as chaves do fluxo de trabalho (como `se`) exigem que a variável seja substituída durante o processamento do fluxo de trabalho antes de ser enviada para o executor. + Você também pode usar o {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" %} arquivo de ambiente `GITHUB_ENV` {% else %} comando de fluxo de trabalho `set-env` {% endif %} para definir uma variável de ambiente que as seguintes etapas em um fluxo de trabalho podem usar. O {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" %}arquivo de ambiente{% else %} comando `set-env` {% endif %} pode ser usado diretamente por uma ação ou como um comando de shell em um arquivo de fluxo de trabalho usando a palavra-chave `executar`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)". ### Variáveis padrão de ambiente @@ -57,6 +67,16 @@ Você também pode usar o {% if currentVersion == "free-pro-team@latest" or curr | `GITHUB_API_URL` | Retorna a URL da API. Por exemplo: `https://api.github.com`. | | `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo: `https://api.github.com/graphql`. | +{% tip %} + +**Observação:** Se você precisar usar o URL de um fluxo de trabalho em um trabalho, você poderá combinar estas variáveis de ambiente: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` + +{% endtip %} + +#### Determinar quando usar variáveis de ambiente padrão ou contextos + +{% data reusables.github-actions.using-context-or-environment-variables %} + ### Convenções de nomenclatura para variáveis de ambiente {% note %} diff --git a/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md index 46241217e8..a614144e1d 100644 --- a/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md @@ -80,6 +80,8 @@ Você pode usar estes operadores em qualquer um dos cinco campos: Você pode usar [crontab guru](https://crontab.guru/) para ajudar a gerar a sintaxe cron e confirmar a hora em que ela será executada. Para ajudar você a começar, há também uma lista de [exemplos de crontab guru](https://crontab.guru/examples.html). +As notificações de fluxos de trabalho agendados são enviadas ao usuário que modificou a sintaxe cron no arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Notificações para execuções do fluxo de trabalho](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)". + ### Eventos manuais Você pode acionar as execuções de fluxo de trabalho manualmente. Para acionar fluxos de trabalho específicos em um repositório, use o evento `workflow_dispatch`. Para acionar mais de um fluxo de trabalho em um repositório e criar eventos personalizados e tipos de eventos, use o evento `repository_dispatch`. @@ -593,7 +595,8 @@ Por padrão, um fluxo de trabalho só é executado quando o tipo de atividade de Por exemplo, você pode executar um fluxo de trabalho quando um pull request tiver sido `atribuído`, `aberto`, `sincronizado` ou `reaberto`. ```yaml -on: pull_request_target +on: + pull_request_target: types: [assigned, opened, synchronize, reopened] ``` diff --git a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md index c20ede373b..5d4c1fe7e9 100644 --- a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -83,44 +83,11 @@ Se houver uma ferramenta que você queira solicitar, abra um problema em [action {% endnote %} -Executores do Windows e Ubuntu são hospedados no Azure e têm os mesmos intervalos de endereços IP dos centros de dados Azure. Atualmente, todos os executores hospedados em {% data variables.product.prodname_dotcom %} do Windows e Ubuntu encontram-se nas seguintes regiões do Azure: +Os executores do Windows e Ubuntu são hospedados no Azure e, consequentemente, têm as mesmas faixas de endereços IP que os centros de dados do Azure. Os executores do macOS estão hospedados na própria nuvem do macOS de {% data variables.product.prodname_dotcom %}. -- Leste dos EUA (`eastus`) -- Leste dos EUA 2 (`eastus2`) -- Oeste dos EU 2 (`westus2`) -- Centro dos EUA (`centralus`) -- Centro-sul dos EUA (`southcentralus`) +Para obter uma lista de intervalos de endereços IP que {% data variables.product.prodname_actions %} usa para executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá usar a API REST de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a chave de `ações` na resposta do ponto de extremidade "[Obtenha as metainformações do GitHub](/rest/reference/meta#get-github-meta-information)". Você pode usar essa lista de endereços IP se precisar de uma lista de permissão para evitar acesso não autorizado para os seus recursos internos. -A Microsoft atualiza os intervalos de endereços IP Azure semanalmente em um arquivo JSON que você pode baixar no site [Azure intervalos IP e tags de serviço - nuvem pública](https://www.microsoft.com/en-us/download/details.aspx?id=56519). Você pode usar esse intervalo de endereços IP se precisar de uma lista de permissão para evitar acesso não-autorizado em seus recursos internos. - -O arquivo JSON contém um array chamado `values` (valores). Dentro desse array, você pode encontrar os endereços IP suportados em um objeto com `name` e `id` da região Azure, por exemplo `"AzureCloud. astus2"`. - -Você pode encontrar os intervalos de endereços IP compatíveis no objeto `"addressPrefixes"`. Este é um exemplo resumido do arquivo JSON. - -```json -{ - "changeNumber": 84, - "cloud": "Public", - "values": [ - { - "name": "AzureCloud.eastus2", - "id": "AzureCloud.eastus2", - "properties": { - "changeNumber": 33, - "region": "eastus2", - "platform": "Azure", - "systemService": "", - "addressPrefixes": [ - "13.68.0.0/17", - "13.77.64.0/18", - "13.104.147.0/25", - ... - ] - } - } - ] -} -``` +A lista de endereços IP de {% data variables.product.prodname_actions %} retornados pela API é atualizada uma vez por semana. ### Sistemas de arquivos diff --git a/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md index fd32c91674..7f4d7d8d04 100644 --- a/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md @@ -257,7 +257,7 @@ Durante a execução de um fluxo de trabalho, o executor gera arquivos temporár **Aviso:** O 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: -``` +```yaml steps: - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` @@ -272,11 +272,19 @@ Cria ou atualiza uma variável de ambiente para quaisquer ações a serem execut #### Exemplo -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` - -Executar `$action_state` em uma etapa futura agora retornará `amarelo` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} #### Strings de linha múltipla @@ -291,7 +299,7 @@ Para strings linha múltipla, você pode usar um delimitador com a seguinte sint ##### Exemplo Neste exemplo, usamos `EOF` como um delimitador e definimos a variável de ambiente `JSON_RESPONSE` como o valor da resposta de curl. -``` +```yaml steps: - name: Set the value id: step_one @@ -305,11 +313,11 @@ steps: `echo "{path}" >> $GITHUB_PATH` -Prepends a directory to the system `PATH` variable and 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. +Prepara um diretório para a variável `PATH` do sistema e o torna disponível 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. #### Exemplo -This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`: +Este exemplo demonstra como adicionar o diretório `$HOME/.local/bin` ao `PATH`: ``` bash echo "$HOME/.local/bin" >> $GITHUB_PATH diff --git a/translations/pt-BR/content/admin/configuration/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/command-line-utilities.md index 3f33b5b25d..5a2eca8ab1 100644 --- a/translations/pt-BR/content/admin/configuration/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` Permite encontrar o uuid do nó em `cluster.conf`. -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -468,20 +468,23 @@ ghe-webhook-logs ``` Para exibir todas as entregas de hook falhas do último dia: +{% if currentVersion ver_gt "enterprise-server@2.22" %} +```shell +ghe-webhook-logs -f -a YYYY-MM-DD +``` + +O formato da data deve ser `AAAA-MM-DD`, `AAAA-MM-DD HH:MM:SS`, ou `AAAA-MM-DD HH:MM:SS (+/-) HH:M`. +{% else %} ```shell ghe-webhook-logs -f -a YYYYMMDD ``` +{% endif %} Para exibir a carga útil total do hook, o resultado e quaisquer exceções para a entrega: ```shell ghe-webhook-logs -g delivery-guid -v ``` -Para exibir entregas globais do webhook: -```shell -ghe-webhook-logs --global -``` - ### Clustering #### ghe-cluster-status @@ -542,8 +545,8 @@ ghe-dpages status ``` Para evacuar um serviço de armazenamento {% data variables.product.prodname_pages %} antes de evacuar um nó de cluster: -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -568,16 +571,16 @@ ghe-spokes route Para evacuar os serviços de armazenamento em um nó de cluster: -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage Este utilitário permite remover todos os serviços de armazenamento antes de remover um nó de cluster. -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md index 9c188cf99f..889718c466 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md +++ b/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md @@ -21,5 +21,7 @@ Quando houver um servidor proxy habilitado para a {% data variables.product.prod {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} 4. Em **HTTP Proxy Server** (Servidor proxy HTTP), digite a URL do seu servidor proxy. ![Campo para digitar a URL do servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) -5. Você também pode ir até **HTTP Proxy Exclusion** (Exclusão de proxy HTTP) e digitar qualquer host que não exija acesso por proxy, separando os hosts por vírgulas. ![Campo para digitar qualquer exclusão de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + +5. Você também pode ir até **HTTP Proxy Exclusion** (Exclusão de proxy HTTP) e digitar qualquer host que não exija acesso por proxy, separando os hosts por vírgulas. Para excluir todos os hosts de um domínio que exige acesso ao proxy, você pode usar `.` como um prefixo curinga. Por exemplo: `octo-org.tentacle` ![Campo para digitar qualquer exclusão de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) + {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md index c23d3eccee..1678921982 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md @@ -80,6 +80,14 @@ Se houver sobreposição de tentativas de backup, o comando `ghe-backup` será i Em caso de interrupção prolongada ou evento catastrófico no site primário, é possível restaurar a {% data variables.product.product_location %} provisionando outro appliance do {% data variables.product.prodname_enterprise %} e executando uma restauração no host de backup. Antes de restaurar um appliance, você deve adicionar a chave SSH do host de backup ao appliance de destino do {% data variables.product.prodname_enterprise %} como chave SSH autorizada. +{%if currentVersion ver_gt "enterprise-server@2.22"%} +{% note %} + +**Nota:** Se {% data variables.product.product_location %} tiver {% data variables.product.prodname_actions %} habilitado, você deverá primeiro configurar o provedor de armazenamento externo de {% data variables.product.prodname_actions %} no aplicativo de substituição antes de executar o comando `ghe-restore`. Para obter mais informações, consulte "[Backup e restauração de {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %} ativado](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." + +{% endnote %} +{% endif %} + Para restaurar a {% data variables.product.product_location %} do instantâneo mais recente bem-sucedido, use o comando `ghe-restore`. Você verá um conteúdo semelhante a este: ```shell diff --git a/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 732e2dde1a..e0b46b7b9c 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -28,11 +28,11 @@ Para os usuários do {% data variables.product.product_location %} conseguirem h {% data reusables.enterprise_site_admin_settings.management-console %} 1. Verificar se há uma **{% data variables.product.prodname_advanced_security %}** entrada na barra lateral esquerda. ![Barra lateral de segurança avançada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) -Se você não puder ver **{% data variables.product.prodname_advanced_security %}** na barra lateral, isso significa que sua licença não inclui suporte para recursos do {% data variables.product.prodname_advanced_security %}, incluindo {% data variables.product.prodname_code_scanning %}. A licença do {% data variables.product.prodname_advanced_security %} dá a você e aos seus usuários acesso a recursos que ajudam a tornar seus repositórios e códigos mais seguros. +{% data reusables.enterprise_management_console.advanced-security-license %} ### Habilitar o {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% 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 %} @@ -47,35 +47,42 @@ Se você não puder ver **{% data variables.product.prodname_advanced_security % #### Configurar um executor auto-hospedado -Se você estiver inscrito no beta de {% data variables.product.prodname_actions %}, {% data variables.product.prodname_ghe_server %} poderá executar {% data variables.product.prodname_code_scanning %} usando um fluxo de trabalho de {% data variables.product.prodname_actions %}. Primeiro, você precisa fornecer um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} em seu ambiente. É possível fornecer executores auto-hospedados no nível da conta do repositório, organização ou empresa. 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)". +{% data variables.product.prodname_ghe_server %} pode executar {% data variables.product.prodname_code_scanning %} usando um fluxo de trabalho de {% data variables.product.prodname_actions %}. Primeiro, você precisa fornecer um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} em seu ambiente. É possível fornecer executores auto-hospedados no nível da conta do repositório, organização ou empresa. 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)". Você deve garantir que o Git esteja na variável do PATH em qualquer executor auto-hospedados que você usar para executar ações de {% data variables.product.prodname_codeql %}. -#### Provisionar a ação -Para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %}, a ação apropriada deve estar disponível localmente. Você pode disponibilizar a ação de três maneiras. +{% if currentVersion == "enterprise-server@2.22" %} +#### Provisionar ações +Para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %}, as ações apropriadas devem estar disponíveis localmente. Você pode disponibilizar as ações de três maneiras. -- **Recomendado** Você pode usar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". +- **Recomendado**: Você pode usar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". - Se você desejar usar o {% data variables.product.prodname_codeql_workflow %}, você pode sincronizar o repositório do {% data variables.product.prodname_dotcom_the_website %} ao {% data variables.product.prodname_ghe_server %}, usando a ferramenta de sincronização de Ação do {% data variables.product.prodname_codeql %} disponível em [https://github. om/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Você pode usar essa ferramenta independentemente se {% data variables.product.product_location %} ou seus executores de {% data variables.product.prodname_actions %} terem acesso à internet, contanto que você possa acessar {% data variables.product.product_location %} e {% data variables.product.prodname_dotcom_the_website %} simultaneamente no seu computador. -- Você pode criar uma cópia local do repositório da ação no seu servidor, clonando o repositório de {% data variables.product.prodname_dotcom_the_website %} com a ação. Por exemplo, se você desejar usar a ação {% data variables.product.prodname_codeql %}, você poderá criar um repositório na sua instância denominada `github/codeql-action` e, em seguida, clonar o [repositório](https://github.com/github/codeql-action) a partir do {% data variables.product.prodname_dotcom_the_website %} e, posteriormente, fazer push desse repositório no repositório da sua instância `github/codeql-action`. Você também deverá fazer o download de qualquer uma das versões do repositório no {% data variables.product.prodname_dotcom_the_website %} e fazer o upload no repositório `github/codeql-action` de sua instância como versões. - +- É possível criar uma cópia local do repositório de uma ação no servidor, clonando o repositório de {% data variables.product.prodname_dotcom_the_website %} que contém a ação. Por exemplo, se você quiser usar as ações para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você poderá criar um repositório na sua instância denominado `github/codeql-action`. Em seguida, clone o [repositório](https://github.com/github/codeql-action) de {% data variables.product.prodname_dotcom_the_website %} depois faça push desse repositório no repositório `github/codeql-action` da instância. Você também deverá fazer o download de qualquer uma das versões do repositório no {% data variables.product.prodname_dotcom_the_website %} e fazer o upload no repositório `github/codeql-action` de sua instância como versões. ##### Configurar {% data variables.product.prodname_github_connect %} para sincronizar {% data variables.product.prodname_actions %} - 1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)". -2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". 3. A próxima etapa é configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". 4. Adicione um executor auto-hospedado ao seu repositório, organização ou conta corporativa. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +{% endif %} -Depois de configurar um executor auto-hospedado, os usuários podem habilitar o {% data variables.product.prodname_code_scanning %} para repositórios individuais em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). +{% if currentVersion ver_gt "enterprise-server@2.22" %} +#### Configurar {% data variables.product.prodname_codeql %} em um servidor sem acesso à internet +Se o servidor em que você está executando +{% data variables.product.prodname_ghe_server %} não estiver conectado à internet, e você deseja permitir que os usuários habilitem {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para seus repositórios, você deverá usar a ferramenta de sincronização de {% data variables.product.prodname_codeql %} para copiar as ações de {% data variables.product.prodname_codeql %} e consultar o pacote de {% data variables.product.prodname_dotcom_the_website %} para o seu servidor. A ferramenta e os detalhes de como usá-la estão disponíveis em [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). +{% endif %} + +#### Habilitar a verificação de código para repositórios individuais +Depois que você configurar um executor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}e provisionar as ações,{% endif %} os usuários poderão habilitar {% data variables.product.prodname_code_scanning %} para repositórios individuais em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). ### Executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %} -Se sua organização não está participando da versão beta do {% data variables.product.prodname_actions %} ou se você não desejar usar {% data variables.product.prodname_actions %}, você poderá executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}. +Se você não quiser usar {% data variables.product.prodname_actions %}, você poderá executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}. O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que você pode adicionar ao seu sistema CI/CD de terceiros. A ferramenta executa a análise do {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". ### Desabilitar {% data variables.product.prodname_code_scanning %} -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} +{% 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 %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md index c8c74cc42c..addd9b82e8 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ Para obter mais informações sobre como entrar em contato com o suporte, consul - No menu suspenso **Authentication** (Autenticação), escolha o tipo de criptografia usado pelo servidor SMTP. - No campo **No-reply email address** (Endereço de e-mail no-reply), digite o endereço de e-mail para usar nos campos De e Para em todos os e-mails de notificação. - {% note %} - - **Observação:** se você marcar a caixa de seleção **Send from author** (Enviar do autor) no webhook de e-mail de um repositório **Services** (Serviços), os e-mails de saída do repositório em questão serão enviados pelo autor, e não pelo endereço de e-mail no-reply. 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)". - - {% endnote %} - 6. Se você quiser descartar todos os e-mails recebidos destinados ao endereço no-reply, selecione **Discard email addressed to the no-reply email address** (Descartar e-mails recebidos no endereço no-reply). ![Caixa de seleção para descartar e-mails destinados ao endereço no-reply](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. Em **Support** (Suporte), escolha um tipo de link para dar suporte adicional aos usuários: - **Email:** endereço de e-mail interno. @@ -155,7 +149,7 @@ Você verá que `metroplex` capta a mensagem de entrada, processa a mensagem e d #### Verificar as configurações DNS -Para processar corretamente os e-mails de entrada, você deve configurar um registro A válido (ou CNAME) e um registro MX. Para obter mais informações, consulte "[Configurar DNS e firewall para o recebimento de e-mails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". +Para processar corretamente os e-mails de entrada, você deve configurar um registro A válido (ou CNAME) e um registro MX. Para obter mais informações, consulte "[Definir as configurações de DNS e firewall para permitir recebimento de e-mails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". #### Verificar as configurações de firewall ou grupo de segurança do AWS diff --git a/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md index 237c778c3e..90915977f4 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-secret-scanning-for-your-appliance.md @@ -1,7 +1,7 @@ --- title: Configurar a varredura de segredo para o seu dispositivo shortTitle: Configurar a varredura de segredo -intro: 'Você pode habilitar, configurar e desabilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' +intro: 'Você pode habilitar, configurar e desabilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} permite aos usuários fazer a varredura de códigos para os segredos que se confirmaram acidentalmente.' product: '{% data reusables.gated-features.secret-scanning %}' miniTocMaxHeadingLevel: 4 versions: @@ -18,13 +18,13 @@ versions: Para usar {% data variables.product.prodname_secret_scanning %} em {% data variables.product.product_location %} você precisa destes dois pré-requisitos. -- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}. +- É necessário habilitar o sinalizador de CPU das [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extensões SIMD de Streaming Suplementar 3) no VM/KVM que executa {% data variables.product.product_location %}. - Você precisa de uma licença de {% data variables.product.prodname_advanced_security %}. #### Verificar suporte para o sinalizador SSSE3 nos seus vCPUs -The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 está habilitado para a maioria das CPUs modernas. Você pode verificar se o SSSE3 está habilitado para oa vCPUs disponíveis para sua instância de {% data variables.product.prodname_ghe_server %}. +O conjunto de instruções das SSSE3 é necessário porque o {% data variables.product.prodname_secret_scanning %} alavanca o padrão acelerado de hardware que corresponde para encontrar possíveis credenciais confirmadas com os seus repositórios de {% data variables.product.prodname_dotcom %}. SSSE3 está habilitado para a maioria das CPUs modernas. Você pode verificar se o SSSE3 está habilitado para oa vCPUs disponíveis para sua instância de {% data variables.product.prodname_ghe_server %}. 1. Conecte ao shell administrativo para sua instância de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". 2. Insira o seguinte comando: diff --git a/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md b/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md index 62464419a5..8d4ae91ade 100644 --- a/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md +++ b/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md @@ -15,30 +15,31 @@ O isolamento de subdomínios reduz os problemas de script entre sites e outras v Quando o isolamento do subdomínio está ativado, o {% data variables.product.prodname_ghe_server %} substitui vários caminhos pelos subdomínios. -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} Para usar o Docker com {% data variables.product.prodname_registry %}, você também deve habilitar o isolamento de subdomínio. Para obter mais informações, consulte "[Configurar Docker para uso com o {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)". {% data reusables.package_registry.packages-ghes-release-stage %} | {% endif %} -| Caminho sem isolamento de subdomínio | Caminho com isolamento de subdomínio | -| -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A, Docker com {% data variables.product.prodname_registry %} não funcionará com o isolamento de subdomínio desabilitado. | `http(s)://uploads.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| Caminho sem isolamento de subdomínio | Caminho com isolamento de subdomínio | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion == "enterprise-server@2.22" %} +| N/A, Docker com {% data variables.product.prodname_registry %} não funcionará com o isolamento do subdomínio desabilitado para o beta 2.22 de {% data variables.product.prodname_registry %}. | `http(s)://docker.HOSTNAME/` |{% endif %} |{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} ### Pré-requisitos diff --git a/translations/pt-BR/content/admin/configuration/index.md b/translations/pt-BR/content/admin/configuration/index.md index fb4e38d0a3..2aaa7dcfe3 100644 --- a/translations/pt-BR/content/admin/configuration/index.md +++ b/translations/pt-BR/content/admin/configuration/index.md @@ -29,6 +29,7 @@ versions: {% link_in_list /configuring-backups-on-your-appliance %} {% link_in_list /site-admin-dashboard %} {% link_in_list /enabling-private-mode %} + {% link_in_list /managing-github-for-mobile-for-your-enterprise %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} {% link_in_list /configuring-applications %} @@ -56,3 +57,4 @@ versions: {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} + {% link_in_list /configuring-secret-scanning-for-your-appliance %} diff --git a/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md index 7f34387f45..d5fe1644d2 100644 --- a/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md @@ -22,5 +22,5 @@ Os membros da sua empresa podem usar {% data variables.product.prodname_mobile % {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} 1. Na barra lateral esquerda, clique em **Celular**. !["Celular" na barra lateral esquerda para o console de gerenciamento de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/click-mobile.png) -1. Under "GitHub for mobile", select or deselect **Enable GitHub Mobile Apps**. ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +1. Em "GitHub dispositivos móveis", selecione ou desmarque a opção de **Habilitar aplicativos para GitHub móvel**. ![Caixa de seleção para "Habilitar os aplicativos do GitHub móvel" no console de gerenciamento de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/enterprise-management/about-clustering.md b/translations/pt-BR/content/admin/enterprise-management/about-clustering.md index b6fb46e24d..4103eb9cfd 100644 --- a/translations/pt-BR/content/admin/enterprise-management/about-clustering.md +++ b/translations/pt-BR/content/admin/enterprise-management/about-clustering.md @@ -24,6 +24,8 @@ O {% data variables.product.prodname_ghe_server %} requer baixa latência entre O clustering fornece redundância, mas não foi feito para substituir uma configuração de alta disponibilidade. Para obter mais informações, consulte [Configuração de alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A configuração de um failover primário/secundário é muito mais simples do que o clustering e funcionará perfeitamente para várias organizações. Para obter mais informações, consulte [Diferenças entre clustering e alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). +{% data reusables.package_registry.packages-cluster-support %} + ### Como faço para obter acesso ao clustering? O clustering foi feito para situações específicas de dimensionamento e não se aplica a todas as organizações. Se você está pensando em usar o clustering, converse com seu representante exclusivo ou {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index 65a7243970..527b0ab6dd 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -10,7 +10,7 @@ versions: ### Sobre a alta disponibilidade de replicação de clusters -Você pode configurar uma implantação de cluster de {% data variables.product.prodname_ghe_server %} para alta disponibilidade, em que um conjunto idêntico de nós passivos estejam sincronizados com os nós no seu cluster ativo. Se falhas no hardware ou software afetarem o centro de dados com o seu cluster ativo, você pode gerar uma falha manualmente nos nós de réplica e continuar processando solicitações de usuário sem perda de dados. +Você pode configurar uma implantação de cluster de {% data variables.product.prodname_ghe_server %} para alta disponibilidade, em que um conjunto idêntico de nós passivos estejam sincronizados com os nós no seu cluster ativo. Se falhas no hardware ou software afetarem o centro de dados com o seu cluster ativo, você poderá transferir a falha manualmente para os nós da réplica e continuar processando as solicitações do usuário, minimizando o impacto da interrupção. Em modo de alta disponibilidade, cada nó ativo é sincronizado regularmente com um nó passivo correspondente. O nó passivo é executado em modo de espera e não atende a aplicativos nem processa solicitações de usuário. diff --git a/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md index cdbd0c55e5..333c61ff3b 100644 --- a/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ Se você estiver usando um nó offline que tenha qualquer tipo de serviços de d ghe-spokes evac-status ``` Para o {% data variables.product.prodname_pages %} + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} Para o armazenamento ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ Se você estiver usando um nó offline que tenha qualquer tipo de serviços de d 3. Após a conclusão do processo de cópia, você poderá remover o serviço de armazenamento. Execute qualquer um dos comandos a seguir: Para o Git + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} Para o {% data variables.product.prodname_pages %} + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} Para o armazenamento, use o nó offline + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} e remova + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/pt-BR/content/admin/enterprise-management/index.md b/translations/pt-BR/content/admin/enterprise-management/index.md index 8ad69b0339..54497054f0 100644 --- a/translations/pt-BR/content/admin/enterprise-management/index.md +++ b/translations/pt-BR/content/admin/enterprise-management/index.md @@ -23,7 +23,6 @@ versions: {% link_in_list /increasing-storage-capacity %} {% link_in_list /increasing-cpu-or-memory-resources %} {% link_in_list /migrating-from-github-enterprise-1110x-to-2123 %} - {% link_in_list /migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later %} {% topic_link_in_list /configuring-clustering %} {% link_in_list /about-clustering %} {% link_in_list /differences-between-clustering-and-high-availability-ha %} diff --git a/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md b/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md index 1ebf1964ad..9a62f40491 100644 --- a/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ Os nomes dos nós podem ser qualquer nome de host válido. Cada nome é definido Especifique o primeiro nó do cluster que você configurou como principal do MySQL via `mysql-server` e `mysql-master`. -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md index 31ff8160ee..b05ec2f3bf 100644 --- a/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md +++ b/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md @@ -31,3 +31,11 @@ versions: ```shell $ ghe-repl-teardown ``` + + {% if currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} + + **Observação:** Se você tiver {% data variables.product.prodname_actions %} habilitado, você deverá desabilitar o antigo servidor de réplica ou atualizar sua configuração de {% data variables.product.prodname_actions %} para usar um armazenamento externo diferente. Para obter mais informações, consulte "[Alta disponibilidade para {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)". + + {% endnote %} + {% endif %} diff --git a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 710c056503..7e52b13a56 100644 --- a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -218,3 +218,9 @@ Para obter mais informações, consulte "[Utilitários de linha de comando](/ent #### Voltar a uma versão de recurso Para voltar a partir de uma versão de recurso, faça a restauração partindo de um instantâneo da VM para garantir o estado consistente das partições raiz e de dados. Para obter mais informações, consulte "[Obter um instantâneo](#taking-a-snapshot)". + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Leia mais + +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md index 7cf42d6330..57c25627de 100644 --- a/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md @@ -123,7 +123,6 @@ Ao entrar em contato com {% data variables.contact.enterprise_support %}, você ### Leia mais {% if enterpriseServerVersions contains currentVersion %} -- [Perguntas frequentes sobre o {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) - 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)"{% if enterpriseServerVersions contains currentVersion %} - "[Preparar para enviar um tíquete](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} diff --git a/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md index b1d5b8a546..4847191804 100644 --- a/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md @@ -59,7 +59,9 @@ Depois do envio da sua solicitação de suporte, podemos pedir que você compart - `configuration-logs/ghe-config.log`: logs de configuração do {% data variables.product.prodname_ghe_server %}; - `collectd/logs/collectd.log`: logs coletados; - `mail-logs/mail.log`: logs de entrega de e-mail por SMTP; +{% if currentVersion ver_lt "enterprise-server@3.0" %} - `hookshot-logs/exceptions.log`: erros de entrega por webhook. +{% endif %} Para obter mais informações, consulte "[Gerar logs de auditoria](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". diff --git a/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index e03339a861..d4d579a362 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -13,7 +13,7 @@ versions: Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 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). -Para tornar todas as ações do {% data variables.product.prodname_dotcom_the_website %} disponíveis na instância empresarial, você pode conectar {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %} usando {% data variables.product.prodname_github_connect %}. Para outras formas de acessar as ações de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre o uso de ações de {% data variables.product.prodname_dotcom_the_website %} no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)". +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.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}. Para conhecer outras formas de acessar ações a partir de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre ações em {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server). ### Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %} @@ -23,3 +23,4 @@ Antes de permitir o acesso a todas as ações de {% data variables.product.prodn {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.github-connect-tab %} 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. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md index f45c627ec9..c065289d93 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md @@ -26,9 +26,9 @@ Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se * **URL de serviço do AWS**: A URL do serviço para seu bucket. Por exemplo, se o seu bucket S3 foi criado na região `us-west-2`, esse valor deverá ser `https://s3.us-west-2.amazonaws.com`. - For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + Para obter mais informações, consulte "[pontos de extremidade do serviço AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" na documentação do AWS. * **Balde S3 AWS**: O nome do seu bucket S3. - * **Chave de acesso do AWS S3** e **Chave de segredo do AWS S3**: A chave de acesso AWS e chave do segredo para o seu bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + * **Chave de acesso do AWS S3** e **Chave de segredo do AWS S3**: A chave de acesso AWS e chave do segredo para o seu bucket. Para mais informações sobre como gerenciar as chaves de acesso do AWS, consulte a "[Documentação de identidade do AWS e gerenciamento de acesso](https://docs.aws.amazon.com/iam/index.html)". ![Botão de opção para selecionar o armazenamento do Amazon S3 e campos para configuração S3](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md index 8c582d9b8f..4efd78dbbd 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- title: Habilitar o o GitHub Actions com armazenamento do Azure Blob -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +intro: 'Você pode habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} e usar o Azure Blob Storage para armazenar artefatos gerados por execuções do fluxo de trabalho.' permissions: 'Os administradores de site podem ativar o {% data variables.product.prodname_actions %} e definir as configurações empresariais.' versions: enterprise-server: '>=3.0' @@ -11,17 +11,17 @@ versions: Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: * Crie sua conta de armazenamento do Azure para armazenar artefatos de fluxo de trabalho. {% data variables.product.prodname_actions %} armazena seus dados como blobs de bloco, e dois tipos de conta de armazenamento são compatíveis: - * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. + * Uma conta de armazenamento para **propósitos gerais** (também conhecida como `propósito geral v1` ou `propósito geral v2`) que usa o nível de desempenho **padrão**. {% warning %} - **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + **Aviso:** Usar a camada de desempenho **premium** com uma conta de armazenamento com propósito geral não é compatível. A camada de desempenho **padrão** deve ser selecionada ao criar a conta de armazenamento e não pode ser alterada posteriormente. {% endwarning %} - * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + * Uma conta de armazenamentoBlockBlobStorage**, que usa a camada de desempenho **premium**. Para obter mais informações sobre os tipos de conta de armazenamento do Azure e níveis de desempenho, consulte a [Documentação do Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). -{% data reusables.actions.enterprise-common-prereqs %} +{% data reusables.actions.enterprise-common-prereqs %} ### Habilitar {% data variables.product.prodname_actions %} com o armazenamento do Azure Blob @@ -29,7 +29,7 @@ Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Botão de opção para selecionar o armazenamento do Azure Blob e o campo de string de conexão](/assets/images/enterprise/management-console/actions-azure-storage.png) +1. Em "Artefato & Registro de armazenamento", selecione **Azure Blob Storage**, e insira a string de conexão da sua conta de do Azure Storage. Para obter mais informações sobre como obter a string de conexão para sua conta de armazenamento, consulte a [Documentação do Azure](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). ![Botão de opção para selecionar o armazenamento do Azure Blob e o campo de string de conexão](/assets/images/enterprise/management-console/actions-azure-storage.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md index e5a7a940c8..e9254de52d 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -27,10 +27,10 @@ Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se * **URL de serviço do AWS**: A URL para p serviço do seu MinIO. Por exemplo, `https://my-minio.example:9000`. * **Balde S3 AWS**: O nome do seu bucket S3. - * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + * **Chave de AWS S3 Access** e **Chave de AWS S3 Secret**: A `MINIO_ACCESS_KEY` e `MINIO_SECRET_KEY` utilizada para a sua instância do MinIO. Para obter mais informações, consulte a [Documentação do MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). - ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) -1. Under "Artifact & Log Storage", select **Force path style**. ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) + ![Botão de opção para selecionar o Amazon S3 Storage e os campos para a configuração do MinIO](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Em "Armazenamento de artefatos& registro", selecione **Forçar o estilo do caminho**. ![Caixa de seleção para forçar estilo de caminho](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md index 3123ee0986..bc2216f32b 100644 --- a/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md @@ -8,7 +8,6 @@ versions: --- {% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} ### Sobre as permissões de {% data variables.product.prodname_actions %} para sua empresa diff --git a/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md b/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md index 22aff2dabb..c1176fe4a4 100644 --- a/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md +++ b/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md @@ -24,6 +24,6 @@ Para obter mais informações, consulte "[Iniciar uma falha na réplica do seu d #### Remover réplica de alta disponibilidade -Evitar deixar várias instâncias para serem gravadas no mesmo armazenamento externo de {% data variables.product.prodname_actions %}. Isso pode ocorrer ao usar o comando `ghe-repl-teardown` para parar e remover permanentemente uma réplica de habilitada por {% data variables.product.prodname_actions %}. This is because the replica will be converted into a standalone {% data variables.product.prodname_ghe_server %}, and after the teardown it will still use the same external storage configuration as the primary. +Evitar deixar várias instâncias para serem gravadas no mesmo armazenamento externo de {% data variables.product.prodname_actions %}. Isso pode ocorrer ao usar o comando `ghe-repl-teardown` para parar e remover permanentemente uma réplica de habilitada por {% data variables.product.prodname_actions %}. Isto porque a réplica será convertida em uma versão autônoma de {% data variables.product.prodname_ghe_server %} e, após a sua desmontagem, continuará usando a mesma configuração de armazenamento externo. Para evitar esse problema, recomendamos desativar o servidor de réplica ou atualizar a sua configuração de {% data variables.product.prodname_actions %} com um armazenamento externo diferente. diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md index aae61ee08a..b5230dc084 100644 --- a/translations/pt-BR/content/admin/github-actions/index.md +++ b/translations/pt-BR/content/admin/github-actions/index.md @@ -12,11 +12,22 @@ versions: ### Índice -{% link_in_list /enabling-github-actions-and-configuring-storage %} +{% topic_link_in_list /enabling-github-actions-for-github-enterprise-server %} + {% link_in_list /getting-started-with-github-actions-for-github-enterprise-server %} + {% link_in_list /enabling-github-actions-with-azure-blob-storage %} + {% link_in_list /enabling-github-actions-with-amazon-s3-storage %} + {% link_in_list /enabling-github-actions-with-minio-gateway-for-nas-storage %} + {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %} {% topic_link_in_list /managing-access-to-actions-from-githubcom %} - {% link_in_list /about-using-githubcom-actions-on-github-enterprise-server %} - {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} - {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /about-using-actions-on-github-enterprise-server %} {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %} + {% link_in_list /manually-syncing-actions-from-githubcom %} + {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} + +{% topic_link_in_list /advanced-configuration-and-troubleshooting %} + {% link_in_list /high-availability-for-github-actions %} + {% link_in_list /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled %} + {% link_in_list /using-a-staging-environment %} + {% link_in_list /troubleshooting-github-actions-for-your-enterprise %} diff --git a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 51abb54c9c..5a472e3879 100644 --- a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -12,7 +12,9 @@ versions: {% data reusables.actions.enterprise-no-internet-actions %} -Para tornar as ações específicas de {% data variables.product.prodname_dotcom_the_website %} disponíveis para uso em fluxos de trabalho, você pode usar a ferramenta de código aberto [`actions-sync`](https://github.com/actions/actions-sync) do {% data variables.product.company_short %} para sincronizar repositórios de ações de {% data variables.product.prodname_dotcom_the_website %} para a instância corporativa. Para outras formas de acessar as ações de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre o uso de ações de {% data variables.product.prodname_dotcom_the_website %} no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)". +A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.prodname_ghe_server %} a {% 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)". + +No entanto, se você quer ter um controle mais rigoroso sobre quais as ações permitidas na sua empresa, você pode seguir esse guia para usar a ferramenta de código aberto de {% data variables.product.company_short %}de [`actions-sync`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} com sua instância corporativa. ### Sobre a ferramenta `actions-sync` @@ -61,7 +63,7 @@ Este exemplo demonstra o uso da ferramenta de `actions-sync` para sincronizar um * Você pode sincronizar várias ações substituindo o parâmetro `--repo-name` por `--repo-name-list` ou `--repo-name-list-file`. Para obter mais informações, consulte o LEIAME de [`actions-sync`](https://github.com/actions/actions-sync#actions-sync). 1. Depois que o repositório de ação é criada na instância corporativa, as pessoas da sua empresa podem usar o repositório de destino para fazer referência à ação nos fluxos de trabalho. Para o exemplo da ação mostrado acima: - ``` + ```yaml uses: synced-actions/docker-build-push-action@v1 ``` diff --git a/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md index c972c4d6cd..fbea95a0c3 100644 --- a/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/troubleshooting-github-actions-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -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 %}.' +title: Solucionar problemas no GitHub Actions para a sua empresa +intro: 'Solucionar problemas comuns que ocorrem ao usar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}.' permissions: 'Os administradores do site podem resolver problemas de {% data variables.product.prodname_actions %} e modificar configurações de {% data variables.product.prodname_ghe_server %}.' versions: enterprise-server: '>=3.0' @@ -20,7 +20,7 @@ Para as etapas necessárias para instalar um certificado, consulte a documentaç A maioria das ações são escritas em JavaScript e são executadas usando Node.js, que não usa o armazenamento de certificados do sistema operacional. Para o aplicativo runner auto-hospedado usar o certificado, você deve definir a variável de ambiente `NODE_EXTRA_CA_CERTS` na máquina do executor. -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. +Você pode definir a variável de ambiente como uma variável de ambiente do sistema, ou declará-la em um arquivo denominado _.env_ no diretório do aplicativo do executor auto-hospedado. Por exemplo: @@ -28,44 +28,44 @@ Por exemplo: NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt ``` -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. +As variáveis de ambiente são lidas quando o aplicativo do executor auto-hospedado é iniciado. Portanto, você deve definir a variável de ambiente antes de configurar ou iniciar o aplicativo do executor auto-hospedado. Se a sua configuração de certificado for alterada, você deverá reiniciar o aplicativo do executor auto-hospedado. -#### Configuring Docker containers to use the certificate +#### Configurar contêineres do Docker para usar o certificado -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. +Se você usa ações do contêiner do Docker ou contêineres de serviço nos seus fluxos de trabalho, você também deverá instalar o certificado na sua imagem do Docker, além de definir a variável de ambiente acima. -### Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} +### Configurar as definições de proxy HTTP para {% data variables.product.prodname_actions %} {% data reusables.actions.enterprise-http-proxy %} -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. +Se estas configurações não estiverem definidas corretamente, você poderá receber erros como `Recurso movido inesperadamente para https://` ao definir ou mudar a configuração de {% data variables.product.prodname_actions %}. -### Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname +### Os executores que não se conectam a {% data variables.product.prodname_ghe_server %} depois de mudar o hostname -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. +Se você alterar o nome do host de {% data variables.product.product_location %}, os executores auto-hospedados não poderão conectar-se ao host antigo e não executarão nenhum trabalho. -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: +Você precisará atualizar a configuração dos seus executores auto-hospedados para usar o novo nome de host para {% data variables.product.product_location %}. Cada executor auto-hospedado exigirá um dos seguintes procedimentos: -* 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. Para obter mais informações, consulte "[Removendo os executores auto-hospedados](/actions/hosting-your-own-runners/removing-self-hosted-runners)" e "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +* No diretório de do aplicativo do executor auto-hospedado, edite os arquivos de `.runner` e `.credentials` para substituir todas as menções do nome de host antigo pelo novo nome de host. Em seguida, reinicie o aplicativo do executor auto-hospedado. +* Remova o executor de {% data variables.product.prodname_ghe_server %} usando a interface do usuário e adicione-o novamente. Para obter mais informações, consulte "[Removendo os executores auto-hospedados](/actions/hosting-your-own-runners/removing-self-hosted-runners)" e "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". -### Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits +### Trabalhos travados e limites de CPU e de memória das {% data variables.product.prodname_actions %} -{% 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. +{% data variables.product.prodname_actions %} é composto de vários serviços em execução em {% data variables.product.product_location %}. Por padrão, esses serviços são configurados com limites padrão de CPU e memória que devem funcionar para a maioria das instâncias. No entanto, usuários assíduos de {% data variables.product.prodname_actions %} talvez precisem para ajustar essas configurações. -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. +É possível que você atinja o limite de CPU ou memória se você notar que os trabalhos não estão sendo iniciados (ainda que existam executores inativos), ou se o progresso do trabalho não estiver sendo atualizado ou alterando na interface do usuário. -#### 1. Check the overall CPU and memory usage in the management console +#### 1. Verifique o uso total da CPU e memória no console de gerenciamento -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)." +Acesse o console de gerenciamento e use o painel do monitor para inspecionar os gráficos gerais de CPU e memória em "Saúde do Sistema". Para obter mais informações, consulte "[Acessar o painel do monitor](/admin/enterprise-management/accessing-the-monitor-dashboard)". -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. Para obter mais informações, consulte "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." +Se o uso geral de "Saúde do Sistema" da CPU estiver próximo a 100% ou não houver mais memória livre, {% data variables.product.product_location %} será executado na capacidade e precisará ser dimensionado. Para obter mais informações, consulte "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." -#### 2. Check the Nomad Jobs CPU and memory usage in the management console +#### 2. Verifique o uso de CPU e a memória dos trabalhos Nomad no console de gerenciamento -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. +Se a "Saúde do Sistema" para o uso total da CPU e da memória estiver OK, acesse a seção "Trabalhos Normad" na parte inferior do painel e observe os gráficos "Valor porcentual da CPU" e "Uso da memória". -Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: +Cada seção nesses gráficos corresponde a um serviço. Para os serviços de {% data variables.product.prodname_actions %}, busque: * `mps_frontend` * `mps_backend` @@ -74,18 +74,18 @@ Each plot in these graphs corresponds to one service. For {% data variables.prod * `actions_frontend` * `actions_backend` -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. +Se qualquer um destes serviços estiver em ou perto de 100% de utilização da CPU ou se a memória estiver próxima do seu limite (2 GB por padrão), talvez seja necessário aumentar a atribuição de recursos para estes serviços. Tome nota de quais dos serviços acima estão no ou próximo do seu limite. -#### 3. Increase the resource allocation for services at their limit +#### 3. Aumenta a alocação de recursos para serviços em seu limite -1. Log in to the administrative shell using SSH. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". -1. Run the following command to see what resources are available for allocation: +1. Efetue o login no shell administrativo usando SSH. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". +1. Execute o comando a seguir para ver quais recursos estão disponíveis para alocação: ```shell nomad node status -self ``` - In the output, find the "Allocated Resources" section. It looks similar to the following example: + Na saída, encontre a seção "Recursos alocados". É algo parecido com o exemplo a seguir: ``` Allocated Resources @@ -93,25 +93,25 @@ If any of these services are at or near 100% CPU utilization, or the memory is n 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB ``` - 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. + Para a memória e a CPU, isso mostra quanto é alocado para o **total** de **todos** serviços (o valor à esquerda) e quanto está disponível (o valor correto). No exemplo acima, há 23 GiB de memória alocado para um total de 32 GiB. Isto significa que há 9 GiB de memória disponíveis para atribuição. {% warning %} - **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. + **Aviso:** Tenha cuidado para não alocar mais do que o total de recursos disponíveis, ou os serviços não poderão ser iniciados. {% endwarning %} -1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: +1. Mude o diretório para `/etc/consul-templates/etc/nomad-jobs/ações`: ```shell cd /etc/consul-templates/etc/nomad-jobs/actions ``` - In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: + Neste diretório existem três arquivos que correspondem aos serviços de {% data variables.product.prodname_actions %} descritos anteriormente: * `mps.hcl.ctmpl` * `token.hcl.ctmpl` * `actions.hcl.ctmpl` -1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: +1. Para os serviços que você identificou que precisam de ajuste, abra o arquivo correspondente e localize o grupo de `recursos` que se parece com o exemplo a seguir: ``` resources { @@ -123,9 +123,9 @@ If any of these services are at or near 100% CPU utilization, or the memory is n } ``` - The values are in MHz for CPU resources, and MB for memory resources. + Os valores estão em MHz para recursos de CPU e em MB para recursos de memória. - 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: + Por exemplo, para aumentar os limites de recursos no exemplo acima para 1 GHz para a CPU e 4 GB de memória, altere-os para: ``` resources { @@ -136,8 +136,8 @@ If any of these services are at or near 100% CPU utilization, or the memory is n } } ``` -1. Save and exit the file. -1. Run `ghe-config-apply` to apply the changes. +1. Salve e saia do arquivo. +1. Execute o `ghe-config-apply` para aplicar as alterações. - 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. + Ao executar `ghe-config-apply`, se você vir a saída como `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, a mudança provavelmente atribuiu muitos recursos de CPU ou memória. Se isso acontecer, edite os arquivos de configuração novamente e baixe a CPU ou memória alocados e execute `ghe-config-apply` novamente. +1. Depois que a configuração for aplicada, execute `ghe-actions-check` para verificar se os serviços {% data variables.product.prodname_actions %} estão operando. diff --git a/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md b/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md index b315bb23f4..92e7db11a3 100644 --- a/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md +++ b/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md @@ -1,26 +1,26 @@ --- -title: Using a staging environment -intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.' +title: Usar um ambiente de preparo +intro: 'Aprenda a usar {% data variables.product.prodname_actions %} com ambientes de preparo de {% data variables.product.prodname_ghe_server %}.' versions: enterprise-server: '>=3.0' --- -It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment. +Pode ser útil ter um ambiente de preparo ou de teste para {% data variables.product.product_location %} para que você possa testar atualizações ou novas funcionalidades antes de implementá-las no seu ambiente de produção. -A common way to create the staging environment is to use a backup of your production instance and restore it to the staging environment. +Uma maneira comum de criar o ambiente de preparo é usar um backup da sua instância de produção e restaurá-lo para o ambiente de preparo. -When setting up a {% data variables.product.prodname_ghe_server %} staging environment that has {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment uses. Otherwise, your staging environment will write to the same external storage as production. +Ao configurar um ambiente de preparação de {% data variables.product.prodname_ghe_server %} que {% data variables.product.prodname_actions %} habilitou, você deve usar uma configuração de armazenamento externo diferente para {% data variables.product.prodname_actions %} armazenamento da usada pelo seu ambiente de produção. Caso contrário, seu ambiente de preparo escreverá no mesmo armazenamento externo da produção. -Expect to see `404` errors in your staging environment when trying to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs, because that data will be missing from your staging storage location. +Espere ver erros do tipo `404` no seu ambiente de preparo ao tentar visualizar os registros ou artefatos de execuções de fluxo de trabalho já existentes, {% data variables.product.prodname_actions %} porque esses dados estarão faltando no seu local de preparo de armazenamento. -Although it is not required for {% data variables.product.prodname_actions %} to be functional in your staging environment, you can optionally copy the files from the production storage location to the staging storage location. +Embora não seja necessário que {% data variables.product.prodname_actions %} seja funcional no seu ambiente de preparo, você pode copiar, opcionalmente, os arquivos do local de armazenamento de produção para o local de armazenamento de preparo. -* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Por exemplo: +* Para uma conta de armazenamento do Azure, você pode usar [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Por exemplo: ```shell azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive ``` -* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Por exemplo: +* Para os buckets do Amazon S3, você pode usar [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Por exemplo: ```shell aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md index d59a78075b..9e23ba6f2e 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-aws.md @@ -130,4 +130,5 @@ As instâncias primária e de réplica devem receber EIPs separados nas configur ### Leia mais -- [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md index 84cb9430df..893156054b 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-azure.md @@ -106,8 +106,8 @@ O {% data variables.product.prodname_ghe_server %} dá suporte a qualquer regiã {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +### Leia mais - ### Leia mais - - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md index d650283415..6bf5be953c 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md @@ -113,4 +113,5 @@ Para criar a instância do {% data variables.product.prodname_ghe_server %}, voc ### Leia mais -- [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md index d56c5ad415..bbaf1f38a9 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-hyper-v.md @@ -62,4 +62,5 @@ versions: ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md index b6eca49787..a2ac14611a 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-openstack-kvm.md @@ -49,4 +49,5 @@ imagem de {% data variables.product.prodname_ghe_server %} que você baixou. Par ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md index 683cda227b..c9f14f3886 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-vmware.md @@ -48,4 +48,5 @@ versions: ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md index f20dc92601..551a8adef7 100644 --- a/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md +++ b/translations/pt-BR/content/admin/installation/installing-github-enterprise-server-on-xenserver.md @@ -45,4 +45,5 @@ versions: ### Leia mais - - [Visão geral do sistema](/enterprise/admin/guides/installation/system-overview) +- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% if currentVersion ver_gt "enterprise-server@2.22" %} +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md b/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md index e3de812be9..efc25895f5 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md @@ -24,3 +24,9 @@ Para fazer um teste completo em todo o appliance do {% data variables.product.pr 1. Faça backup da sua instância de produção usando o {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte a seção "Sobre o {% data variables.product.prodname_enterprise_backup_utilities %}" em "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)". 2. Configure uma nova instância para funcionar como ambiente de preparo. Você pode usar os mesmos guias para provisionar e instalar sua instância de preparo, assim como fez na instância de produção. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)". 3. Restaure o backup na sua instância de preparo. Para obter mais informações, consulte a seção "Restaurar backup" em "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)". + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +### Leia mais + +- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)" +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 6d55813c0c..901052ae6f 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -18,11 +18,11 @@ Uma conta corporativa permite gerenciar várias organizações{% if enterpriseSe - Segurança {% if enterpriseServerVersions contains currentVersion %}(logon único, autenticação de dois fatores) - Compartilhamento de pacotes de solicitação e {% if enterpriseServerVersions contains currentVersion %}suporte {% endif %} com {% data variables.contact.enterprise_support %}{% endif %} -{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about the management of your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}Para obter mais informações sobre como gerenciar suas configurações de cobrança de {% data variables.product.product_name %}, consulte "[Gerenciar cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} Para obter mais informações sobre o gerenciamento da sua assinatura de {% data variables.product.prodname_ghe_cloud %}, consulte "[Visualizar a assinatura e o uso da sua conta corporativa](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)". {% endif %}Para obter mais informações sobre como gerenciar suas configurações de cobrança de {% data variables.product.product_name %}, consulte "[Gerenciar cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". -For more information about the management of users, organizations, data, and policies for {% data variables.product.product_location %}, see "[Managing users, organizations, and repositories](/admin/user-management)" and "[Setting policies for your enterprise](/admin/policies)." +Para obter mais informações sobre o gerenciamento de usuários, organizações, dados e políticas para {% data variables.product.product_location %}, consulte "[Gerenciar usuários, organizações e repositórios](/admin/user-management)" e "[Definir políticas para a sua empresa](/admin/policies)." -For more information about the management of enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +Para obter mais informações sobre o gerenciamento de contas corporativas usando a API do GraphQL, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". {% if enterpriseServerVersions contains currentVersion %} diff --git a/translations/pt-BR/content/admin/overview/about-github-ae.md b/translations/pt-BR/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..aba009ba79 --- /dev/null +++ b/translations/pt-BR/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: Sobre o GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} é a forma mais segura e compatível de usar {% data variables.product.prodname_dotcom %}.' +versions: + github-ae: '*' +--- + +### Sobre o {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} oferece uma plataforma de desenvolvedor da ideia à produção. Você pode aumentar a velocidade de desenvolvedor, automatizar fluxos de trabalho inteiros, proteger seu código e colaborar na ferramenta favorita de desenvolvedores. + +{% data variables.product.prodname_ghe_managed %} confere à sua organização todo o poder de [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). Com {% data variables.product.prodname_ghe_managed %}, você também pode cumprir as metas de segurança e conformidade com um conjunto de funcionalidades e certificações que colocam você no controle. + +### Uma nuvem de alta disponibilidade e escala planetária + +{% data variables.product.prodname_ghe_managed %} é um serviço totalmente gerenciado, hospedado em uma arquitetura de alta disponibilidade. {% data variables.product.prodname_ghe_managed %} está hospedado globalmente em uma nuvem que pode ser escalada para ser compatível com todo o seu ciclo de vida de desenvolvimento sem limites. {% data variables.product.prodname_dotcom %} gerencia totalmente os backups, failover e recuperação de desastres para que você nunca tenha que se preocupar com o seu serviço ou dados. + +### Residência dos dados + +Todos os seus dados são armazenados na região geográfica da sua escolha. Você pode cumprir os padrões de proteção de dados e o RGPD global mantendo todos os seus dados na sua região escolhida. + +### Criptografia conforme as suas condições + +Todos os dados do cliente serão criptografados de forma estática e você pode fornecer a sua própria chave de criptografia para criptografar seus dados com base nos termos das suas políticas de criptografia. Você controla sua chave e o acesso a todos os seus dados. Para obter mais informações, consulte "[Configurar a criptografia de dados para sua empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)". + +### Contas isoladas + +Todas as contas de desenvolvedor são completamente isoladas em {% data variables.product.prodname_ghe_managed %}. Você pode controlar totalmente as contas por meio do seu provedor de identidade, com o logon único SAML como obrigatório. O SCIM permite que você garanta que os funcionários só têm acesso aos recursos que deveriam, conforme definido no seu sistema central de gestão de identidades. Para obter mais informações, consulte "[Gerenciar identidade e acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". + +### Acesso restrito às redes + +Acesso seguro à sua empresa em {% data variables.product.prodname_ghe_managed %} com acesso restrito à rede, para que seus dados possam ser acessados somente de dentro da sua rede. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)". + +### Ambientes comercial e governamental + +{% data variables.product.prodname_ghe_managed %} está disponível na nuvem do Azure Government, na nuvem de confiança das agências governamentais dos EUA e seus parceiros. {% data variables.product.prodname_ghe_managed %} também está disponível na nuvem comercial. Portanto, você pode escolher o ambiente de hospedagem correto para a sua organização. + +### Suporte Premium Plus + +O suporte Premium Plus está disponível para todos os clientes de {% data variables.product.prodname_ghe_managed %} para garantir que você tenha uma experiência de suporte mais rápida e pessoal. Um Gerente de Conta dedicado trabalhará com você para ajudá-lo a obter o máximo proveito de {% data variables.product.prodname_dotcom %}. A nossa equipe de suporte resolverá problemas a qualquer hora do dia, no menor tempo possível. + +### Sobre a cobrança do {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.about-billing %} Para obter mais informações, consulte "[Gerenciar a cobrança para a sua empresa](/admin/overview/managing-billing-for-your-enterprise)". \ No newline at end of file diff --git a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md index 3cd0d506d3..410df25a84 100644 --- a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md @@ -1,32 +1,32 @@ --- -title: About upgrades to new releases -shortTitle: About upgrades -intro: 'You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.' +title: Sobre atualizações para novas versões +shortTitle: Sobre as atualizações +intro: 'Você pode beneficiar-se das novas funcionalidades e correções de erros para {% data variables.product.product_name %} atualizando a sua empresa para uma versão recém-lançada.' versions: enterprise-server: '>=3.0' --- -{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. +{% data variables.product.product_name %} está constantemente melhorando, com novas funcionalidades e correções de erros introduzidas por meio de versões maiores e menores. -Major releases include new functionality and feature upgrades and typically occur quarterly. +As principais versões incluem novas funcionalidades e atualizações de recursos e normalmente ocorrem a cada trimestre. -Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}. +Começando com {% data variables.product.prodname_ghe_server %} 3.0, todas as principais versões começam com pelo menos um candidato de versão. Os candidatos de verão são as principais versões propostas, com um conjunto completo de recursos. Pode haver erros ou problemas em um candidato de versão que só podem ser encontrados por meio do feedback de clientes que usam {% data variables.product.product_name %}. -You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)." +Você pode ter acesso rápido às últimas funcionalidades testando um candidato de versão assim que este estiver disponível. Você pode atualizar para um candidato de versão a partir de uma versão compatível e pode atualizar do candidato de versão para versões posteriores quando lançado. Você deve atualizar qualquer ambiente executando um candidato de versão assim que a versão estiver geralmente disponível. Para obter mais informações, consulte "[Requisitos de atualização](/admin/enterprise-management/upgrade-requirements)". -Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)." +Os candidatos de versão devem ser implantados em ambientes de teste ou de preparação. Ao testar um candidato de versão, entre em contato com o suporte. Para obter mais informações, consulte "[Trabalhando com {% data variables.contact.github_support %}](/admin/enterprise-support)". -We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release. +Usaremos seus comentários para aplicar correções de erros e quaisquer outras alterações necessárias para criar uma versão de produção estável. Cada novo candidato de versão adiciona correções de erros para problemas encontrados em versões anteriores. Quando a versão estiver pronta para ser utilizada amplamente, {% data variables.product.company_short %} irá publicar uma versão de produção estável. {% warning %} -**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." +**Aviso**: A atualização para uma nova versão principal implicará algumas horas de inatividade, durante as quais nenhum dos seus usuários poderá usar a empresa. Você pode informar aos seus usuários sobre tempo de inatividade, publicando um banner de anúncio global, usando as configurações da sua empresa ou a API REST. Para obter mais informações, consulte "[Personalizar mensagens de usuário na sua instância](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" e "[ administração de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". {% endwarning %} -Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime. +Lançamentos menores, que consistem apenas em correções de erros e correções de erros, acontecem com mais frequência. De modo geral, as versões menores ficam disponíveis quando são lançadas pela primeira vez, sem candidatos de versões. Atualizar para uma versão menor normalmente requer menos de cinco minutos de tempo de inatividade. -To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +Para atualizar a sua empresa para uma nova versão, consulte "[Liberar notas](/enterprise-server/admin/release-notes)" e "[Atualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server). ### Leia mais diff --git a/translations/pt-BR/content/admin/overview/index.md b/translations/pt-BR/content/admin/overview/index.md index 5e243d5ad1..c5ce49912c 100644 --- a/translations/pt-BR/content/admin/overview/index.md +++ b/translations/pt-BR/content/admin/overview/index.md @@ -12,8 +12,10 @@ Para obter mais informações ou comprar o {% data variables.product.prodname_en ### Índice +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} +{% link_in_list /about-upgrades-to-new-releases %} {% link_in_list /system-overview %} {% link_in_list /about-the-github-enterprise-api %} diff --git a/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md b/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md index 080d7f3d25..baf3aad72a 100644 --- a/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ Instância de {% data variables.product.prodname_ghe_server %} como administrado {% data reusables.enterprise-accounts.license-tab %} 12. Em "Quick links" (Links rápidos), clique em **Update license** (Atualizar licença). ![Link de atualização de licença](/assets/images/enterprise/business-accounts/update-license-link.png) 13. Para selecionar sua licença, clique em **License file** (Arquivo de licença) ou arraste o arquivo de licença para o **License file** (Arquivo de licença). ![Fazer upload do arquivo de licença](/assets/images/enterprise/management-console/upload-license.png) -14. Clique em **Fazer upload**. ![Iniciar atualização](/assets/images/enterprise/management-console/begin-upload.png) +14. Clique em **Fazer upload**. ![Iniciar upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}Se a interface do usuário web para {% data variables.product.prodname_ghe_server %} não refletir sua licença atualizada imediatamente, consulte "[Solução de problemas](#troubleshooting)".{% endif %} ### Exibir o uso de licenças @@ -70,3 +72,23 @@ Para sincronizar manualmente o uso das licenças de usuário entre as duas impla {% data reusables.enterprise-accounts.license-tab %} 10. Em "Instâncias Enterprise Server", clique em **Add server usage** (Adicionar uso de servidor). ![Fazer upload do link de uso do GitHub Enterprise Server](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. Faça upload do arquivo JSON que você baixou do {% data variables.product.prodname_ghe_server %}.![Arrastar e soltar ou selecionar um arquivo para upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### Solução de Problemas + +Em alguns cenários, a interface de usuário web para {% data variables.product.prodname_ghe_server %} pode não refletir imediatamente sua nova licença. Você pode forçar o sistema a detectar a licença, reiniciando dois serviços do sistema. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Reinicie os serviços para autenticação Git e o servidor HTTP. + + {% warning %} + + **Aviso**: Executar o seguinte comando gerará alguns minutos de tempo de inatividade do usuário para {% data variables.product.prodname_ghe_server %}. Execute o comando com cuidado. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. Depois que {% data variables.product.prodname_ghe_server %} retornar você para uma instrução, tente acessar {% data variables.product.prodname_ghe_server %} por meio da linha de comando ou da interface do usuário da web novamente. + +{% endif %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md index 8944f71044..ed48905de0 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Packages with AWS -intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' +title: Habilitar o GitHub Packeges com AWS +intro: 'Configure {% data variables.product.prodname_registry %} com AWS como seu armazenamento externo.' versions: enterprise-server: '>=2.22' --- @@ -8,7 +8,7 @@ versions: {% warning %} **Avisos:** -- It is critical that you configure any 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 to the public internet. For more information, see "[Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" in the AWS Documentation. +- É fundamental que você configure todas as políticas de acesso restritivas necessárias para o seu bucket de armazenamento, porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à sua configuração do bucket de armazenamento. Por exemplo, se o seu bucket for público, os dados do bucket poderão ser acessados por meio da internet pública. Para obter mais informações, consulte "[Configurar as permissões de acesso de objetos](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" na documentação do AWS. - Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. - Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. @@ -16,9 +16,9 @@ versions: ### Pré-requisitos -Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). +Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você precisa preparar o bucket do seu armazenamento do AWS. Para preparar seu bucket de armazenamento do AWS, recomendamos consultar a documentação oficial do AWS na [Documentação do AWS](https://docs.aws.amazon.com/index.html). -Ensure your AWS access key ID and secret have the following permissions: +Certifique-se de que o seu ID da sua chave e o segredo de acesso do AWS tenham as permissões a seguir: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -27,7 +27,7 @@ Ensure your AWS access key ID and secret have the following permissions: - `s3:DeleteObject` - `s3:ListBucket` -### Enabling {% data variables.product.prodname_registry %} with AWS external storage +### Habilitar {% data variables.product.prodname_registry %} com armazenamento externo do AWS {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -41,17 +41,17 @@ Ensure your AWS access key ID and secret have the following permissions: 1. Em "Região do AWS S3", digite sua região para o S3. ![Campo Região do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: - - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. +1. Em "Armazenamento de pacotes", selecione **Amazon S3** e insira os detalhes do seu bucket de armazenamento: + - **URL do serviço do AWS:** A URL do serviço para seu bucket. Por exemplo, se seu bucket de S3 foi criado em `us-west-2 region`, esse valor deve ser `https://s3.us-west-2.guide/s.com`. - For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. + Para obter mais informações, consulte "[pontos de extremidade do serviço AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" na documentação do AWS. - - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. - - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. + - **Balde S3 AWS:** O nome do seu bucket do S3 dedicado a {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** e **AWS S3 Secret Key**: O ID da chave de acesso e segredo do AWS para acessar o seu bucket. - For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + Para mais informações sobre como gerenciar as chaves de acesso do AWS, consulte a "[Documentação de identidade do AWS e gerenciamento de acesso](https://docs.aws.amazon.com/iam/index.html)". - ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) + ![Caixas de entrada para detalhes do seu bucket do AWS S3](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index 99f0a51308..8e288f1ab3 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Packages with Azure Blob Storage -intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' +title: Habilitar o GitHub Packages com o Azure Blob Storage +intro: 'Configure o {% data variables.product.prodname_registry %} com o Azure Blob Storage como seu armazenamento externo.' versions: enterprise-server: '>=3.0' --- @@ -8,7 +8,7 @@ versions: {% warning %} **Avisos:** -- 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. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. +- É fundamental que você defina as políticas de acesso restritivas necessárias para o seu bucket de armazenamento, porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à sua configuração do bucket de armazenamento. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. - Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. - Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. @@ -16,15 +16,15 @@ versions: ### Pré-requisitos -Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.product.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). +Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você precisa preparar o bucket do seu Azure Blob Storage. Para preparar o bucket do seu Azure Blob Storage, recomendamos consultar a documentação oficial do do Azure Blob Storage no [site oficial da documentação do Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/). -### Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage +### Habilitar {% data variables.product.prodname_registry %} com o Azure Blob Storage {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} -1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) +1. Em "Armazenamento de pacotes", selecione **Azure Blob Storage** e insira o nome do seu contêiner do Azure para seus pacotes de armazenamento e string de conexão. ![Nome do contêiner do Azure Blob Storage e caixas de string de conexão](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md index 43a5204496..67ae427301 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Packages with MinIO -intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' +title: Habilitar o GitHub Packeges com o MinIO +intro: 'Configure {% data variables.product.prodname_registry %} com o MinIO como seu armazenamento externo.' versions: enterprise-server: '>=2.22' --- @@ -8,15 +8,15 @@ versions: {% warning %} **Avisos:** -- 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. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. +- É fundamental que você defina as políticas de acesso restritivas necessárias para o seu bucket de armazenamento, porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à sua configuração do bucket de armazenamento. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. - Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. - Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. {% endwarning %} ### Pré-requisitos -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)." +Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você precisa preparar seu grupo de armazenamento do MinIO. Para ajudá-lo a configurar rapidamente um bucket do MinIO e acessar as opções de personalização do MinIO, consulte o "[Guia de inícoio rápido para configurar seu bucket de armazenamento do MinIO para {% 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: +Certifique-se de que que o seu ID da chave de acesso e o segredo de armazenamento externo do MinIO tenham essas permissões: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -25,29 +25,29 @@ Ensure your MinIO external storage access key ID and secret have these permissio - `s3:DeleteObject` - `s3:ListBucket` -### Enabling {% data variables.product.prodname_registry %} with MinIO external storage +### Habilitar {% data variables.product.prodname_registry %} com armazenamento externo do MinIO -Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still {% if currentVersion == "enterprise-server@2.22" %} officially{% endif %} 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. +Embora o MinIO atualmente não apareça na interface do usuário em "Armazenamento de Pacote", o MinIO ainda é {% if currentVersion == "enterprise-server@2. 2" %} oficialmente{% endif %} compatível com {% data variables.product.prodname_registry %} em {% data variables.product.prodname_enterprise %}. Além disso, observe que o armazenamento de objetos do MinIO é compatível com a API do S3 e você pode inserir detalhes do bucket do MinIO no lugar dos detalhes do AWS S3. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} {% if currentVersion == "enterprise-server@2.22" %} -1. Under "AWS Service URL", type the MinIO URL for your bucket's region. ![Campo da URL do Serviço do AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) -1. Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts. ![Campo de Bucket para AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) -1. Under "AWS S3 Access Key", type your access key for MinIO. ![Campo Chave de acesso do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) -1. Under "AWS S3 Secret Key", type your secret key for MinIO. ![Campo Chave Secreta do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) -1. Under "AWS S3 Region", type your region for MinIO. ![Campo Região do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) +1. Em "URL de serviço do AWS" digite a URL do MinIO para a região do seu bucket. ![Campo da URL do Serviço do AWS](/assets/images/enterprise/site-admin-settings/storage-service-url.png) +1. Em "Bucket do AWS S3", digite o nome do bucket do MinIO que você deseja usar para armazenar artefatos do pacote. ![Campo de Bucket para AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) +1. Em "Chave de acesso do AWS S3", digite sua chave de acesso para o MinIO. ![Campo Chave de acesso do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) +1. Em "Chave secreta do AWS S3", digite sua chave secreta para o MinIO. ![Campo Chave Secreta do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) +1. Em "Região do AWS S3", digite sua região para o MinIO. ![Campo Região do AWS S3](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -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. +1. Em "Armazenamento de pacotes", selecione **Amazon S3**. +1. Insira os detalhes do seu bucket de armazenamento do MinIO nas configurações de armazenamento do AWS. + - **URL de serviço do AWS:** A URL de hospedagem do bucket do seu MinIO. + - **Bucket do S3 AWS**: O nome do bucket do seu MinIO compatível com S3 e dedicado a {% data variables.product.prodname_registry %}. + - **Chave de Acesso do AWS S3** e **Chave secreta do AWS S3**: Digite a chave de acesso do MinIO e a chave secreta para acessar seu bucket. - ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) + ![Caixas de entrada para detalhes do seu bucket do AWS S3](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index 66ebd448bb..ab63dc7f65 100644 --- a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Getting started with GitHub Packages for your enterprise -intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' +title: Primeiros passos com o GitHub Packages para a sua empresa +intro: 'Você pode começar a usar {% data variables.product.prodname_registry %} em {% data variables.product.product_location %} habilitando o recurso, configurando armazenamento de terceiros, configurando os ecossistemas que você deseja que sejam compatíveis e atualizando seu certificado TLS.' redirect_from: - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise - /admin/packages/enabling-github-packages-for-your-enterprise @@ -14,7 +14,7 @@ versions: {% note %} -**Note:** After you've been invited to join the beta, follow the instructions from your account representative to enable {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}. +**Observação:** Depois de ser convidado a participar da versão beta, siga as instruções do representante de sua conta para habilitar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}. {% endnote %} @@ -22,28 +22,28 @@ versions: {% data reusables.package_registry.packages-cluster-support %} -### Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage +### Etapa 1: Habilite {% data variables.product.prodname_registry %} e configure o armazenamento externo {% data variables.product.prodname_registry %} em {% data variables.product.prodname_ghe_server %} usa armazenamento externo de blob para armazenar seus pacotes. -After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. +Depois de habilitar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, você deverá preparar seu bucket de armazenamento de terceiros. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_registry %}, e as diretrizes de configuração podem variar de acordo com o provedor de armazenamento. -Supported external storage providers +Provedores de armazenamento externos compatíveis - Amazon Web Services (AWS) S3 {% if currentVersion ver_gt "enterprise-server@2.22" %} - Azure Blob Storage {% endif %} - MinIO -To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: - - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} - - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} - - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" +Para habilitar {% data variables.product.prodname_registry %} e configurar o armazenamento de terceiros, consulte: + - "[Habilitar o GitHub Packages com AWS](/admin/packages/enabling-github-packages-with-aws)"{% if currentVersion ver_gt "enterprise-server@2.22" %} + - "[Habilitar o GitHub Packages com o Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Habilitar o GitHub Packages com o MinIO](/admin/packages/enabling-github-packages-with-minio)" -### Step 2: Specify the package ecosystems to support on your instance +### Etapa 2: Especifique os ecossistemas de pacote que serão compatíveis com a sua instância -Choose which package ecosystems you'd like to enable, disable, or set to read-only on your {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." +Escolha quais ecossistemas de pacote você gostaria de habilitar, desabilitar ou definir como somente leitura no seu {% data variables.product.product_location %}. As opções disponíveis são Docker, RubyGems, npm, Apache Maven, Gradle ou NuGet. Para obter mais informações, consulte "[Configurar a compatibilidade com o ecossistema de pacote para a sua empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". -### Step 3: Ensure you have a TLS certificate for your package host URL, if needed +### Etapa 3: Certifique-se de ter um certificado TLS para a URL do seu pacote de hospedagem, se necessário -If subdomain isolation is enabled for {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, which is required to use {% data variables.product.prodname_registry %} with Docker{% endif %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Certifique-se de que o host de cada pacote contém `https://`. +Se o isolamento do subdomínio for habilitado para {% data variables.product.product_location %}{% if currentVersion == "enterprise-server@2.22" %}, que é necessário para usar {% data variables.product.prodname_registry %} com o Docker{% endif %}, você precisará criar e fazer o upload de um certificado TLS que permite a URL de host do pacote para cada ecossistema que você deseja usar como, por exemplo, `npm.HOSTNAME`. Certifique-se de que o host de cada pacote contém `https://`. - You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. Para obter mais informações sobre as URLs de host do pacote, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obter mais informações sobre o upload de certificados TLS para {% data variables.product.product_name %}, consulte "[Configurar TLS](/enterprise/admin/configuration/configuring-tls)". + Você pode criar o certificado manualmente ou pode usar _Let's Encrypt_. Se você já usa _Let's Encrypt_, você deverá solicitar um novo certificado TLS depois de habilitar {% data variables.product.prodname_registry %}. Para obter mais informações sobre as URLs de host do pacote, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obter mais informações sobre o upload de certificados TLS para {% data variables.product.product_name %}, consulte "[Configurar TLS](/enterprise/admin/configuration/configuring-tls)". diff --git a/translations/pt-BR/content/admin/packages/index.md b/translations/pt-BR/content/admin/packages/index.md index 2a5c94fda0..09289e3b93 100644 --- a/translations/pt-BR/content/admin/packages/index.md +++ b/translations/pt-BR/content/admin/packages/index.md @@ -9,7 +9,11 @@ versions: {% data reusables.package_registry.packages-ghes-release-stage %} -{% link_with_intro /enabling-github-packages-for-your-enterprise %} -{% link_with_intro /quickstart-for-configuring-minio-storage %} -{% link_with_intro /configuring-packages-support-for-your-enterprise %} -{% link_with_intro /configuring-third-party-storage-for-packages %} +{% link_with_intro /getting-started-with-github-packages-for-your-enterprise %} + + {% link_in_list /enabling-github-packages-with-aws %}{% if currentVersion ver_gt "enterprise-server@2.22" %} + {% link_in_list /enabling-github-packages-with-azure-blob-storage %}{% endif %} + {% link_in_list /enabling-github-packages-with-minio %} + {% link_in_list /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages %} + +{% link_with_intro /configuring-package-ecosystem-support-for-your-enterprise %} diff --git a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md index 348cd102ea..aa6f0dc23b 100644 --- a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md +++ b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -1,6 +1,6 @@ --- -title: Quickstart for configuring your MinIO storage bucket for GitHub Packages -intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' +title: Guia de início rápido para configurar o seu bucket de armazenamento de MinIO para o GitHub Packages +intro: 'Configure seu bucket de armazenamento do MinIO personalizado para uso com {% data variables.product.prodname_registry %}.' versions: enterprise-server: '>=2.22' --- @@ -129,4 +129,4 @@ Para concluir a configuração de armazenamento para {% data variables.product.p echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" ``` -For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." +Para os próximos passos, consulte "[Habilitar {% data variables.product.prodname_registry %} com o MinIO](/admin/packages/enabling-github-packages-with-minio)". diff --git a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md index a93c3ebc6c..e8ef11f792 100644 --- a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -58,7 +58,8 @@ Fora dos valores fornecidos para `stdin`, há variáveis adicionais disponíveis | $GITHUB_VIA | Método de criação da ref.
    **Valores possíveis:**
    - `api de desenvolvimento automerge`
    - `edição blob`
    - `api de merge branch`
    - `botão de exclusão de página de branches`
    - `api de criação de refs git`
    - `api de exclusão de refs git`
    - `api de atualização de refs git`
    - `api de merge`
    - `botão de exclusão de branch de pull request`
    - `botão de desfazer branch de pull request`
    - `api de merge de pull request`
    - `botão de merge de pull request`
    - `api de reverter pull request`
    - `botão de exclusão de versões`
    - `restauração de branch de ferramentas de equipe`
    - `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | Número de opções de push enviadas pelo cliente. Para obter mais informações sobre as opções de push, consulte "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" na documentação do Git. | | $GIT_PUSH_OPTION_N | Quando N for um número inteiro a partir de 0, esta variável vai conter a string de opção de push enviada pelo cliente. A primeira opção enviada é armazenada em GIT_PUSH_OPTION_0, a segunda é armazenada em GIT_PUSH_OPTION_1 e assim por diante. Para obter mais informações sobre as opções de push, consulte "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" na documentação do Git. |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | A string do user-agent enviada pelo cliente que fez push das alterações. |{% endif %} +| $GIT_USER_AGENT | A string do user-agent enviada pelo cliente que fez push das alterações. +{% endif %} ### Configurar permissões e fazer push de um hook pre-receive para o {% data variables.product.prodname_ghe_server %} @@ -93,30 +94,30 @@ Antes de criar ou atualizar um script de hook pre-receive no appliance do {% dat 2. Crie um arquivo de nome `Dockerfile.dev` contendo: - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. Crie um script pre-receive de teste chamado `always_reject.sh`. Este exemplo de script rejeitará todos os pushes, o que é importante para bloquear um repositório: + 3. Crie um script pre-receive de teste chamado `always_reject.sh`. Este exemplo de script rejeitará todos os pushes, o que é importante para bloquear um repositório: - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 diff --git a/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md index 79552b39ee..f476dba092 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ versions: Toda vez que alguém criar um novo repositório na sua empresa, essa pessoa deverá escolher uma visibilidade para o repositório. Ao configurar uma configuração padrão de visibilidade para a empresa, você escolhe qual visibilidade será selecionada por padrão. Para obter mais informações sobre a visibilidade de repositório, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". -If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". +Se um proprietário corporativo impedir que os integrantes criem certos tipos de repositórios, os integrantes não serão capazes de criar esse tipo de repositório, mesmo se a configuração de visibilidade for o padrão para esse tipo. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". {% data reusables.enterprise-accounts.access-enterprise %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} @@ -49,9 +49,9 @@ If an enterprise owner disallows members from creating certain types of reposito ### Definir uma política para alterar a visibilidade de um repositório -When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository. +Quando você impede que os integrantes alterem a visibilidade do repositório, somente os proprietários corporativos podem alterar a visibilidade de um repositório. -If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". +Se um proprietário corporativo tiver restringido a criação de repositório apenas para os proprietários da organização, os integrantes não poderão alterar a visibilidade do repositório. Se um proprietário corporativo restringir a criação do repositório de integrantes apenas para repositórios privados, os integrantes só poderão alterar a visibilidade de um repositório para privado. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -77,7 +77,7 @@ If an enterprise owner has restricted repository creation to organization owners ### Aplicar uma política de bifurcação de repositórios internos ou privados -Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level. +Em todas as organizações pertencentes à sua empresa, é possível permitir que pessoas com acesso a um repositório privado o bifurquem, nunca permitir a bifurcação de repositórios privados ou permitir que os proprietários administrem a configuração no nível da organização. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/pt-BR/content/admin/user-management/audited-actions.md b/translations/pt-BR/content/admin/user-management/audited-actions.md index a0e8616d25..ac708ca044 100644 --- a/translations/pt-BR/content/admin/user-management/audited-actions.md +++ b/translations/pt-BR/content/admin/user-management/audited-actions.md @@ -80,7 +80,7 @@ versions: | Nome | Descrição | | ------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `repo.access` | A visibilidade de um repositório alterado para privado{% if enterpriseServerVersions contains currentVersion %}, público,{% endif %} ou interno. | -| `repo.archive` | Um repositório foi arquivado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | +| `repo.archived` | Um repositório foi arquivado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | | `repo.add_member` | Um colaborador foi adicionado ao repositório. | | `repo.config` | Um administrador do site bloqueou a opção de forçar pushes. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/). | | `repo.create` | Um repositório foi criado. | @@ -89,7 +89,7 @@ versions: | `repo.rename` | Um repositório foi renomeado. | | `repo.transfer` | Um usuário aceitou uma solicitação para receber um repositório transferido. | | `repo.transfer_start` | Um usuário enviou uma solicitação para transferir um repositório a outro usuário ou organização. | -| `repo.unarchive` | Um repositório teve o arquivamento cancelado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".{% if enterpriseServerVersions contains currentVersion %} +| `repo.unarchived` | Um repositório teve o arquivamento cancelado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".{% if enterpriseServerVersions contains currentVersion %} | `repo.config.disable_anonymous_git_access` | O acesso de leitura anônimo do Git está desabilitado em um repositório. 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)". | | `repo.config.enable_anonymous_git_access` | O acesso de leitura anônimo do Git está abilitado em um repositório. 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)". | | `repo.config.lock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está bloqueado, impedindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | @@ -107,32 +107,36 @@ versions: #### Equipes -| Nome | Descrição | -| --------------:| --------------------------------------------------------------- | -| `team.create` | Um repositório ou conta de usuário foi adicionado a uma equipe. | -| `team.delete` | Um repositório ou conta de usuário foi removido de uma equipe. | -| `team.destroy` | Uma equipe foi excluída. | +| Nome | Descrição | +| -------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.create` | Um repositório ou conta de usuário foi adicionado a uma equipe. | +| `team.delete` | Uma conta ou repositório foi removido de uma equipe.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.demote_maintainer` | A categoria de um usuário foi rebaixada para de mantenedor da equipe para membro da equipe.{% endif %} +| `team.destroy` | Uma equipe foi excluída.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `team.promote_maintainer` | Um usuário foi promovido de membro da equipe para mantenedor da equipe.{% endif %} + #### Usuários -| Nome | Descrição | -| ---------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | Um endereço de e-mail foi adicionado a uma conta de usuário. | -| `user.async_delete` | Um trabalho assíncrono foi iniciado para destruir uma conta de usuário, eventualmente acionando `user.delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.change_password` | Um usuário alterou sua senha.{% endif %} -| `user.create` | Uma nova conta de usuário foi criada. | -| `user.delete` | Uma conta de usuário foi destruída por um trabalho assíncrono. | -| `user.demote` | Um administrador do site foi rebaixado a uma conta de usuário regular. | -| `user.destroy` | Um usuário excluiu a sua conta, acionando `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} -| `user.failed_login` | Um usuário tentou fazer login com nome de usuário, senha ou código de autenticação de dois fatores incorretos. | -| `user.forgot_password` | Um usuário solicitou uma redefinição de senha através da página de login.{% endif %} -| `user.login` | Um usuário fez login. | -| `user.promote` | Uma conta de usuário regular foi promovida a administrador do site. | -| `user.remove_email` | Um endereço de e-mail foi removido de uma conta de usuário. | -| `user.rename` | Um nome de usuário foi alterado. | -| `user.suspend` | Uma conta de usuário foi suspensa por um administrador do site.{% if enterpriseServerVersions contains currentVersion %} -| `user.two_factor_requested` | Um código de autenticação de dois fatores foi solicitado de um usuário.{% endif %} -| `user.unsuspend` | Uma conta de usuário teve a suspensão cancelada por um administrador do site. | +| Nome | Descrição | +| -------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `user.add_email` | Um endereço de e-mail foi adicionado a uma conta de usuário. | +| `user.async_delete` | Um trabalho assíncrono foi iniciado para destruir uma conta de usuário, eventualmente acionando `user.delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.change_password` | Um usuário alterou sua senha.{% endif %} +| `user.create` | Uma nova conta de usuário foi criada. | +| `user.delete` | Uma conta de usuário foi destruída por um trabalho assíncrono. | +| `user.demote` | Um administrador do site foi rebaixado a uma conta de usuário regular. | +| `user.destroy` | Um usuário excluiu a sua conta, acionando `user.async_delete`.{% if enterpriseServerVersions contains currentVersion %} +| `user.failed_login` | Um usuário tentou fazer login com nome de usuário, senha ou código de autenticação de dois fatores incorretos. | +| `user.forgot_password` | Um usuário solicitou uma redefinição de senha através da página de login.{% endif %} +| `user.login` | Um usuário iniciou a sessão.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `user.mandatory_message_viewed` | Um usuário visualiza uma mensagem obrigatória (ver "[Personalizar mensagens de usuário](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obter detalhes). {% endif %} +| `user.promote` | Uma conta de usuário regular foi promovida a administrador do site. | +| `user.remove_email` | Um endereço de e-mail foi removido de uma conta de usuário. | +| `user.rename` | Um nome de usuário foi alterado. | +| `user.suspend` | Uma conta de usuário foi suspensa por um administrador do site.{% if enterpriseServerVersions contains currentVersion %} +| `user.two_factor_requested` | Um código de autenticação de dois fatores foi solicitado de um usuário.{% endif %} +| `user.unsuspend` | Uma conta de usuário teve a suspensão cancelada por um administrador do site. | [add key]: /articles/adding-a-new-ssh-key-to-your-github-account [chave de implantação]: /guides/managing-deploy-keys/#deploy-keys diff --git a/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index c298b992da..e22c54ef81 100644 --- a/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -4,13 +4,18 @@ redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message/ - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance -intro: 'Você pode criar mensagens personalizadas que os usuários verão nas{% if enterpriseServerVersions contains currentVersion %} páginas de login e logout{% else %} página de logout{% endif %}{% if currentVersion ver_gt "enterprise-server@2. 1" ou versão atual == "github-ae@latest" %} ou em um banner de anúncio na parte superior de cada página{% endif %}.' +intro: 'Você pode criar mensagens personalizadas que os usuários verão em {% data variables.product.product_location %}.' versions: enterprise-server: '*' github-ae: '*' --- -Você pode usar markdown para formatar sua mensagem. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)". +### Sobre mensagens de usuário + +Existem vários tipos de mensagens de usuário. +- Mensagens que aparecem na página {% if enterpriseServerVersions contains currentVersion %}página de ingresso ou {% endif %}saída{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- Mensagens obrigatórias, que aparecem uma vez em uma janela pop-up que deve ser ignoradas{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- Banners de anúncios, que aparecem na parte superior de cada página{% endif %} {% if enterpriseServerVersions contains currentVersion %} {% note %} @@ -19,17 +24,20 @@ Você pode usar markdown para formatar sua mensagem. Para obter mais informaçõ {% endnote %} +Você pode usar markdown para formatar sua mensagem. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)". + ### Criar mensagem personalizada de login {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Em "Sign in page" (Página de login), clique em **Add message** (Adicionar mensagem) ou **Edit message** (Editar mensagem). ![Botão Edit message (Editar mensagem)](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Em **Sign in message** (Mensagem de login), digite a mensagem que você pretende exibir para os usuários. ![Mensagem de login](/assets/images/enterprise/site-admin-settings/sign-in-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2. 2" %}À direita de{% else %}em{% endif %} "página de login", clique em **Adicionar mensagem** ou **Editar mensagem**. ![{% if currentVersion ver_gt "enterprise-server@2.22" %}Botão de mensagem de Adicionar{% else %}Editar{% endif %}](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Em **Sign in message** (Mensagem de login), digite a mensagem que você pretende exibir para os usuários. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% if currentVersion ver_gt "enterprise-server@2.22" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) 8. Revise a mensagem renderizada. ![Mensagem de login renderizada](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} ### Criar mensagem personalizada de logout @@ -37,12 +45,35 @@ Você pode usar markdown para formatar sua mensagem. Para obter mais informaçõ {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Em "Sign out page" (Página de logout), clique em **Add message** (Adicionar mensagem) ou **Edit message** (Editar mensagem). ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Em **Sign out message** (Mensagem de logout), digite a mensagem que você pretende exibir para os usuários. ![Mensagem de login two_factor_auth_header](/assets/images/enterprise/site-admin-settings/sign-out-message.png) +5. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}À direita de{% else %}em{% endif %} "página de logout", clique em **Adicionar mensagem** ou **Editar mensagem**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Em **Sign out message** (Mensagem de logout), digite a mensagem que você pretende exibir para os usuários. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) 8. Revise a mensagem renderizada. ![Mensagem de logout renderizada](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### Criar uma mensagem obrigatória + +Você pode criar uma mensagem obrigatória que {% data variables.product.product_name %} mostrará a todos os usuários na primeira vez que efetuarem o login depois de salvar a mensagem. A mensagem aparece em uma janela pop-up que o usuário deve ignorar antes que o usuário possa usar o {% data variables.product.product_location %}. As mensagens obrigatórias têm uma série de usos. + +- Fornecer informações de integração para novos funcionários +- Contar para os usuários como obter ajuda com {% data variables.product.product_location %} +- Garantir que todos os usuários leiam seus termos de serviço para usar {% data variables.product.product_location %} + +Se você incluir caixas de seleção de Markdown na mensagem, todas as caixas de seleção deverão ser selecionadas antes de o usuário poder ignorar a mensagem. Por exemplo, se você incluir seus termos de serviço na mensagem obrigatória, você poderá exigir que cada usuário marque uma caixa de seleção para confirmar que o usuário leu os termos. + +Cada vez que um usuário vê uma mensagem obrigatória, um evento de log de auditoria é criado. O evento inclui a versão da mensagem que o usuário visualizou. Para obter mais informações, consulte "[Ações auditadas](/admin/user-management/audited-actions)". + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. À direita da "Mensagem obrigatória", clique em **Adicionar mensagem**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Em "Mensagem obrigatória", na caixa de texto, digite sua mensagem. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} + +{% endif %} {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### Criar um banner de anúncio global @@ -50,9 +81,8 @@ Você pode usar markdown para formatar sua mensagem. Para obter mais informaçõ Você pode definir um banner de anúncio global para ser exibido para todos os usuários na parte superior de cada página. {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -Você também pode definir um banner de anúncio{% if enterpriseServerVersions contains currentVersion %} no shell administrativo usando um utilitário de linha de comando ou{% endif %} usando a API. Para obter mais informações, consulte {% if enterpriseServerVersions contains currentVersion %}"[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" e {% endif %}"[Administração de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". - +Você também pode definir um banner de anúncio +{% if enterpriseServerVersions contains currentVersion %} no shell administrativo usando um utilitário de linha de comando ou{% endif %} usando a API. Para obter mais informações, consulte {% if enterpriseServerVersions contains currentVersion %}"[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" e {% endif %}"[Administração de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". {% else %} Você também pode definir um banner de anúncio no shell administrativo usando um utilitário de linha de comando. Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)". @@ -62,9 +92,8 @@ Você também pode definir um banner de anúncio no shell administrativo usando {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. Em "Sign in page" (Página de login), clique em **Add message** (Adicionar mensagem) ou **Edit message** (Editar mensagem). ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. {% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}À direita de{% else %}em{% endif %} "Anúncio", clique em **Adicionar anúncio**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) 1. Em "Anúncio", no campo de texto, digite o anúncio que deseja exibir em um banner. ![Campo de texto para digitar o anúncio](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Opcionalmente, em "Vence em", use o menu suspenso do calendário e selecione uma data de validade. ![Menu suspenso do calendário para escolher data de vencimento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. Opcionalmente, para ver como ficará o banner, clique em **Pré-visualizar**. ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) +1. Opcionalmente, em "Expira em", selecione o menu suspenso do calendário e clique em uma data de validade. ![Menu suspenso do calendário para escolher data de vencimento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md b/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md index 4aee97ca5c..6f1496ce56 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,11 +33,11 @@ Se você não tiver o modo privado ativado, o script de migração não terá ef 1. Conecte-se ao shell administrativo. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/enterprise/{}/admin/installation/accessing-the-administrative-shell-ssh)". 2. Navegue no diretório `/data/github/current`. - ``` + ```shell cd /data/github/current ``` 3. Execute o comando de migração. - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` diff --git a/translations/pt-BR/content/admin/user-management/viewing-push-logs.md b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md index 8328b8c545..157b609de3 100644 --- a/translations/pt-BR/content/admin/user-management/viewing-push-logs.md +++ b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ As entradas de log de push mostram o seguinte: ### Exibir os logs de push do repositório +1. Efetue o login em {% data variables.product.prodname_ghe_server %} como administrador do site. 1. Navegue até um repositório. -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. No canto superior direito da página do repositório, clique em +{% octicon "rocket" aria-label="The rocket ship" %}. + ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. Na barra lateral esquerda, clique em **Push Log** (Log de push). ![Guia de log de push](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### Exibir os logs de push do repositório na linha de comando -1. Acesse o SSH no appliance. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)". -2. No repositório do Git adequado, abra o arquivo de log de auditoria: +{% data reusables.enterprise_installation.ssh-into-instance %} +1. No repositório do Git adequado, abra o arquivo de log de auditoria: ```shell ghe-repo owner/repository -c "less audit_log" ``` diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 8fe91cb6a5..97af095f92 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ O {% data variables.product.prodname_desktop %} permite que você crie tags anot ![Visualizar uma tag no histórico](/assets/images/help/desktop/viewing-tags-in-history.png) 3. Todas as tags associadas ao commit são visíveis nos metadados desse commit. ![Visualizar uma tag no commit](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### Excluir tags + +{% note %} + +**Observação**: Você só pode excluir tags associadas a commits que ainda não foram enviados por push. + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md index a69a98ccea..d0a20bd54d 100644 --- a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md @@ -72,13 +72,13 @@ Troque este `código` por um token de acesso: ##### Parâmetros -| Nome | Tipo | Descrição | -| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_github_app %}. | -| `client_secret` | `string` | **Obrigatório.** O segredo do cliente que recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_github_app %}. | -| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | -| `redirect_uri` | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização. | -| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | +| Nome | Tipo | Descrição | +| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. | +| `client_secret` | `string` | **Obrigatório.** O segredo do cliente que recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. | +| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | +| `redirect_uri` | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização. | +| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | ##### Resposta @@ -213,7 +213,7 @@ Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de aces #### Limites de taxa para o fluxo do dispositivo -Quando um usuário envia o código de verificação no navegador, existe um limite de taxa máximo de 50 submissões em uma hora por aplicativo. +Quando um usuário envia o código de verificação no navegador, há um limite de taxa de 50 envios por hora por aplicativo. Se você fizer mais de uma solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`) no período mínimo necessário entre solicitações (ou `intervalo`), você atingirá o limite de taxa e receberá uma resposta de erro `slow_down`. A resposta de erro `slow_down`adiciona 5 segundos ao último `intervalo`. Para obter mais informações, consulte [Erros para o fluxo do dispositivo](#errors-for-the-device-flow). diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md index 8bce30d942..6b0dbd812e 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -80,7 +80,7 @@ O objeto `hook_attributes` tem a chave a seguir: Este exemplo usa um formulário em uma página web com um botão que aciona a solicitação `POST` para uma conta de usuário: -``` +```html Criar um manifesto do aplicativo GitHub:
    @@ -111,7 +111,7 @@ Este exemplo usa um formulário em uma página web com um botão que aciona a so ``` Este exemplo usa um formulário em uma página web com um botão que aciona a solicitação `POST` para uma conta da organização. Substitua `ORGANIZAÇÃO` pelo nome da conta da organização em que você deseja criar o aplicativo. -``` +```html Criar um manifesto do aplicativo GitHub:
    diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md index 5a65213a1a..1b8ad79725 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -80,7 +80,7 @@ Você pode selecionar permissões em uma string de consultas usando o nome da pe | [`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: `none`, `read` ou `write`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %} -| `vulnerability_alerts` | Concede acesso a alertas de segurança para dependências vulneráveis em um repositório. Consulte "[Sobre alertas de segurança para dependências vulneráveis](/articles/about-security-alerts-for-vulnerable-dependencies)" para saber mais. Can be one of: `none` or `read`.{% endif %} +| `vulnerability_alerts` | Concede acesso a alertas de segurança para dependências vulneráveis em um repositório. Consulte "[Sobre alertas de segurança para dependências vulneráveis](/articles/about-security-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`. | ### Eventos webhook do {% data variables.product.prodname_github_app %} diff --git a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index b0c7342f1e..7cd3cf5cf7 100644 --- a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ Um código de host do servidor de CI que executa testes de CI, como, por exemplo A [API de verificação](/rest/reference/checks) permite que você configure testes de CI executados automaticamente em cada commit de código em um repositório. A API de verificação relata informações detalhadas sobre cada verificação no GitHub na aba **Verificações** do pull request. Com a API de Verificações, você pode criar anotações com detalhes adicionais para linhas específicas de código. As anotações são visíveis na aba **Verificações**. Ao criar uma anotação para um arquivo que faz parte do pull request, as anotações também são exibidas na aba **Arquivos alterados**. -Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Usar esses status com [branches protegidos](/rest/reference/repos#branches) pode impedir que as pessoas mesclem de pull requests prematuramente. Consulte "[Habilitando as verificações de status necessárias](/articles/enabling-required-status-checks/)" para mais detalhes. +Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Usar esses status com [branches protegidos](/rest/reference/repos#branches) pode impedir que as pessoas mesclem de pull requests prematuramente. Veja "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" para mais informações. A API de verificações envia o evento do webhook [`check_suite` webhook](/webhooks/event-payloads/#check_suite) para todos os aplicativos GitHub instalados em um repositório sempre que um novo código for enviado para o repositório. Para receber todas as ações do evento de verificações da API, o aplicativo deverá ter a permissão de `checks:write`. O GitHub cria automaticamente eventos `check_suite` para novos códigos de commits em um repositório usando o fluxo-padrão, embora [Atualizar preferências do repositório para o conjunto de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites) esteja disponível se desejar. Veja como funciona o fluxo-padrão: @@ -435,7 +435,7 @@ O código acima obtém o nome completo do repositório e o SHA principal do comm ### Etapa 2.3. Executar o RuboCop -Ótimo! Você está clonando o repositório e criando execuções de verificação usando seu servidor de CI. Agora você irá entrar nas informações principais do [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) e das [anotações da API de verificação](/rest/reference/checks#create-a-check-run). +Ótimo! Você está clonando o repositório e criando execuções de verificação usando seu servidor de CI. Agora você irá entrar nas informações principais do [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) e das [anotações da API de verificação](/rest/reference/checks#create-a-check-run). O código a seguir executa RuboCop e salva os erros do código de estilo no formato JSON. Adicione este código abaixo da chamada para `clone_repository` que você adicionou na [etapa anterior](#step-22-cloning-the-repository) e acima do código que atualiza a execução de verificação para concluir. @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -O código acima executa o RuboCop em todos os arquivos no diretório do repositório. A opção `--format json` é uma maneira útil de salvar uma cópia dos resultados de linting, em um formato analisável por máquina. Consulte a [documentação do RuboCop](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) para obter informações e um exemplo do formato JSON. +O código acima executa o RuboCop em todos os arquivos no diretório do repositório. A opção `--format json` é uma maneira útil de salvar uma cópia dos resultados de linting, em um formato analisável por máquina. Consulte a [documentação do RuboCop](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) para obter informações e um exemplo do formato JSON. Como esse código armazena os resultados do RuboCop em uma variável `@report`, ele pode remover o checkout do repositório com segurança. Este código também analisa o JSON para que possa acessar facilmente as chaves e valores no seu aplicativo GitHub usando a variável `@output`. @@ -588,7 +588,7 @@ Este código limita o número total de anotações a 50. Mas você pode modifica Quando o `offense_count` é zero, o teste de CI é um `sucesso`. Se houver erros, este código definirá a conclusão como `neutro` para evitar estritamente a imposição de erros dos linters do código. Mas você pode alterar a conclusão para `falha` se desejar garantir que o conjunto de verificações falhe quando houver erros de linting. -Quando os erros são relatados, o código acima afirma por meio da array de `arquivos` no relatório do RuboCop. Para cada arquivo, ele extrai o caminho do arquivo e define o nível de anotação como `aviso`. Você pode ir além e definir os níveis específicos de aviso para cada tipo de [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), mas simplificar as coisas neste início rápido, todos os erros são definidos para um nível de `aviso`. +Quando os erros são relatados, o código acima afirma por meio da array de `arquivos` no relatório do RuboCop. Para cada arquivo, ele extrai o caminho do arquivo e define o nível de anotação como `aviso`. Você pode ir além e definir os níveis específicos de aviso para cada tipo de [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), mas simplificar as coisas neste início rápido, todos os erros são definidos para um nível de `aviso`. Este código também é afirmado por meio de cada erro no array de `ofensas` e coleta o local da mensagem de erro e de ofensa. Após extrair as informações necessárias, o código cria uma anotação para cada erro e a armazena no array de `anotações`. Uma vez que as anotações são compatíveis apenas com colunas iniciais e finais na mesma linha, `start_column` e `end_column` só são adicionados ao objeto `anotação` se os valores da linha inicial e final forem iguais. @@ -718,13 +718,13 @@ Se as anotações estiverem relacionadas a um arquivo já incluído no PR, as an Se você chegou até aqui, parabéns! 👏 Você já criou um teste de CI. Nesta seção, você irá adicionar mais um recurso que usa RuboCop para corrigir automaticamente os erros que encontra. Você já adicionou o botão "Corrija isso" na [seção anterior](#step-25-updating-the-check-run-with-ci-test-results). Agora você irá adicionar o código para lidar com o evento de execução de verificação `requested_action` acionado quando alguém clica no botão "Corrija isso". -A ferramenta do RuboCop [oferece](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) a opção de linha de comando `--auto-correct` para corrigir automaticamente os erros que encontra. Ao usar o recurso `--auto-correct`, as atualizações são aplicadas aos arquivos locais do servidor. Você deverá fazer push das alterações no GitHub depois que o RuboCop fizer sua mágica. +A ferramenta do RuboCop [oferece](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) a opção de linha de comando `--auto-correct` para corrigir automaticamente os erros que encontra. Ao usar o recurso `--auto-correct`, as atualizações são aplicadas aos arquivos locais do servidor. Você deverá fazer push das alterações no GitHub depois que o RuboCop fizer sua mágica. Para fazer push para um repositório, seu aplicativo deve ter permissões de "conteúdo do repositório". Você redefiniu essa permissão na [Etapa 2.2. Clonar o repositório](#step-22-cloning-the-repository) para **Leitura & gravação**. Agora, você está pronto. Para enviar arquivos do commit, o Git deve saber qual o [nome de usuário](/articles/setting-your-username-in-git/) e [e-mail](/articles/setting-your-commit-email-address-in-git/) devem ser associados ao commit. Adicione mais duas variáveis de ambiente ao seu arquivo `.env` para armazenar as configurações do nome (`GITHUB_APP_USER_NAME`) e do e-mail (`GITHUB_APP_USER_EMAIL`). Seu nome pode ser o nome do seu aplicativo e o e-mail pode ser qualquer e-mail que desejar para este exemplo. Por exemplo: -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 4f1b824715..9c362dfda2 100644 --- a/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ Um aplicativo OAuth _authorized_ tem acesso a todos os recursos acessíveis do u | Os tokens de instalação expiram após um tempo predefinido (atualmente, 1 hora). | Os tokens do OAuth permanecem ativos até que sejam cancelados pelo cliente. | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Limites de taxa mais alto aplicam-se a {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Limites de taxas para os aplicativos GitHub](/developers/apps/rate-limits-for-github-apps)."{% endif %} | Os tokens do OAuth usam o limite de taxa de usuário de 5.000 solicitações por hora. | | Os aumentos no limite de taxa pode ser concedido tanto no nível do aplicativo GitHub (afetando todas as instalações) quanto no nível de instalação individual. | Os aumentos no limite de taxa são concedidos pelo aplicativo OAuth. Todo token concedido para que o aplicativo OAuth obtém um aumento do limite. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %}s podem efetuar a autenticação em nome do usuário, o que é denominado solicitações de usuário para servidor. O fluxo para autorizar é o mesmo que o fluxo de autorização do aplicativo OAuth. Os tokens de usuário para servidor podem expirar e ser renovados com um token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" e "[identificando e autorizando os usuários para os aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | O fluxo do OAuth usado por {% data variables.product.prodname_oauth_app %}s autoriza um {% data variables.product.prodname_oauth_app %} em nome do usuário. Este é o mesmo fluxo de uso na autorização de usuário para servidor do {% data variables.product.prodname_github_app %}. |{% endif %} +| {% data variables.product.prodname_github_app %}s podem efetuar a autenticação em nome do usuário, o que é denominado solicitações de usuário para servidor. O fluxo para autorizar é o mesmo que o fluxo de autorização do aplicativo OAuth. Os tokens de usuário para servidor podem expirar e ser renovados com um token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" e "[identificando e autorizando os usuários para os aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | O fluxo do OAuth usado por {% data variables.product.prodname_oauth_app %}s autoriza um {% data variables.product.prodname_oauth_app %} em nome do usuário. Este é o mesmo fluxo de uso na autorização de usuário para servidor do {% data variables.product.prodname_github_app %}. +{% endif %} ### Solicitar níveis de permissão para os recursos @@ -85,7 +86,7 @@ Ao contrário dos aplicativos OAuth, os aplicativos GitHub têm permissões dire | Aplicativos do GitHub | Aplicativos OAuth | | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Por padrão, os aplicativos GitHub têm um único webhook que recebe os eventos que estão configurados para receber para cada repositório ao qual têm acesso. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. | +| Por padrão, os aplicativos GitHub têm um único webhook que recebe os eventos que estão configurados para receber para cada repositório ao qual têm acesso. | Os aplicativos OAuth solicitam o escopo do webhook para criar um webhook do repositório para cada repositório do qual precisam receber eventos. | | O aplicativo GitHub recebe certos eventos a nível da organização com a permissão do integrante da organização. | Os aplicativos OAuth solicitam o escopo do webhook da organização para criar um webhook da organização para cada organização da qual precisam para receber eventos a nível da organização. | ### Acesso Git diff --git a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index c091a91e07..a8a81ce2d4 100644 --- a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -89,7 +89,7 @@ Os tokens de usuário expirados atualmente fazem parte da expiração do token b Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `expires_in`, `atualizar_token`, e `refresh_token_expires_in` são apenas retornados quando você ativar o beta para expirar os tokens de acesso do usuário para servidor. -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", diff --git a/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md index b88c9088c1..9588be43a1 100644 --- a/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### Escopos disponíveis -| Nome | Descrição | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Nome | Descrição | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (inclui informações de perfil do usuário público, informações de repositório público e gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`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 a repositórios privados e públicos. 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 públicos e privados. Também concede capacidade para gerenciar projetos de usuário. | -|  `repo:status` | Concede acesso de leitura/gravação aos status do commit do repositório público e 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 de implantação](/rest/reference/repos#deployments) para repositórios públicos e privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso ao status de implantação, *sem* conceder acesso ao código. | -|  `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 com uma estrela. | +| **`repo`** | Concede acesso total a repositórios privados e públicos. 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 públicos e privados. Também concede capacidade para gerenciar projetos de usuário. | +|  `repo:status` | Concede acesso de leitura/gravação aos status do commit do repositório público e 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 de implantação](/rest/reference/repos#deployments) para repositórios públicos e privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso ao status de implantação, *sem* conceder acesso ao código. | +|  `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 com uma estrela. | |  `repo:invite` | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. Este escopo só é necessário para conceder a outros usuários ou serviços acesso a convites *sem* conceder acesso ao código. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `security_events` | Concede:
    acesso de leitura e gravação para eventos de segurança na [ API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning).
    acesso de leitura e gravação para eventos de segurança da [ API de {% data variables.product.prodname_secret_scanning %} ](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} -|  `security_events` | Concede acesso de leitura e escrita a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Concede acesso de leitura, gravação e ping aos hooks do repositório em repositórios públicos e privados. O escopos do `repo` e `public_repo` concede 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, escrita e ping para os hooks em repositórios públicos ou privados. | -|  `read:repo_hook` | Concede acesso de leitura e ping para hooks em repositórios públicos ou 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. | +|  `security_events` | Concede:
    acesso de leitura e gravação a eventos de segurança na [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    acesso de leitura e gravação a eventos de segurança na [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
    Este escopo só é necessário para conceder acesso de outros usuários ou serviços a eventos de segurança *sem* conceder acesso ao código.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@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 e ping aos hooks do repositório em repositórios públicos e privados. O escopos do `repo` e `public_repo` concede 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, escrita e ping para os hooks em repositórios públicos ou privados. | +|  `read:repo_hook` | Concede acesso de leitura e ping para hooks em repositórios públicos ou 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` | Permite acesso de leitura para as discussões de equipe.{% if currentVersion == "free-pro-team@latest" %} -| **`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)". | +| **`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 %}. Para obter mais informações, consulte "[Excluir pacotes](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -| **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | -|  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | +| **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | +|  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | |  `read:gpg_key` | Liste e visualize informações para as chaves GPG.{% if currentVersion == "free-pro-team@latest" %} | **`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 `GITHUB_TOKEN` que pode ter um conjunto diferente de escopos. Consulte https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token para detalhes.{% endif %} diff --git a/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md b/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md index 823e6a5468..3f411a38d9 100644 --- a/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ Para saber mais sobre publicação de {% data variables.product.prodname_actions ### Aplicativos -Qualquer pessoa pode compartilhar seus aplicativos com outros usuários em {% data variables.product.prodname_marketplace %}, mas apenas os anúncios verificados por {% data variables.product.company_short %} podem incluir planos pagos. Para obter mais informações, consulte "[Sobre criadores verificados](/developers/github-marketplace/about-verified-creators)". +Qualquer pessoa pode compartilhar seus aplicativos com outros usuários gratuitamente em {% data variables.product.prodname_marketplace %}, mas somente os aplicativos pertencentes a organizações podem vender seu aplicativo. + +Para publicar planos pagos para o seu aplicativo e exibir um selo do Marketplace, você deve concluir o processo de verificação do publicador. Para obter mais informações, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" ou "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)". + +Uma vez que a organização atenda aos requisitos, alguém com permissões de proprietário na organização pode publicar planos pagos para qualquer um dos aplicativos. Cada aplicativo com um plano pago também passa por um processo de integração financeira para habilitar pagamentos. + +Para publicar aplicativos com planos grátis, você só precisa atender aos requisitos gerais para anunciar qualquer aplicativo. Para obter mais informações, consulte "[Requisitos para todos os anúncios do GitHub Marketplace](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)". + +#### Novo nos aplicativos? Se estiver interessado em criar um aplicativo para {% data variables.product.prodname_marketplace %}, mas você é novo em {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_app %}s, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" ou "[Criar {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)". +#### Aplicativos GitHub vs. Aplicativos OAuth + {% data reusables.marketplace.github_apps_preferred %}, embora você possa listar tanto o OAuth quanto {% data variables.product.prodname_github_app %}s no {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" e[Migrando {% data variables.product.prodname_oauth_app %}s para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/) -Em caso de dúvidas dúvidas sobre {% data variables.product.prodname_marketplace %}, entre em contato diretamente com {% data variables.contact.contact_support %}. - -### Publicar um aplicativo em {% data variables.product.prodname_marketplace %} +### Publicar um aplicativo na visão geral de {% data variables.product.prodname_marketplace %} Ao terminar de criar seu aplicativo, você poderá compartilhá-lo com outros usuários publicando-o em {% data variables.product.prodname_marketplace %}. Em resumo, o processo é: @@ -38,13 +46,9 @@ Ao terminar de criar seu aplicativo, você poderá compartilhá-lo com outros us 1. Adicionar um plano de preços. Para obter mais informações, consulte "[Configurar planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". -1. Verifique se seu aplicativo atende aos requisitos para a listagem em {% data variables.product.prodname_marketplace %} como um aplicativo grátis ou pago. Para obter mais informações, consulte "[Requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app)". - 1. Leia e aceite os termos do "[Contrato do Desenvolvedor de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". -1. Envie sua listagem para publicação em {% data variables.product.prodname_marketplace %}, solicitando verificação, se você desejar vender o aplicativo. Para obter mais informações, consulte "[Enviar sua listagem para publicação](/developers/github-marketplace/submitting-your-listing-for-publication)". - -Um especialista em integração entrará em contato com você com outras dúvidas ou etapas posteriores. Por exemplo, se você adicionou um plano pago, você deverá concluir o processo de verificação e concluir a integração financeira. Assim que seu anúncio for aprovado, o aplicativo será publicado em {% data variables.product.prodname_marketplace %}. +1. Envie seu anúncio para publicação em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Enviar sua listagem para publicação](/developers/github-marketplace/submitting-your-listing-for-publication)". ### Ver como seu aplicativo está sendo executado @@ -52,3 +56,7 @@ Você pode acessar métricas e transações para a sua listagem. Para obter mais - "[Visualizar métricas para a sua listagem](/developers/github-marketplace/viewing-metrics-for-your-listing)" - "[Visualizar transações para a sua listagem](/developers/github-marketplace/viewing-transactions-for-your-listing)" + +### Entrar em contato com o suporte + +Em caso de dúvidas dúvidas sobre {% data variables.product.prodname_marketplace %}, entre em contato diretamente com {% data variables.contact.contact_support %}. diff --git a/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md b/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..955b5b7c94 --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: Sobre selos do marketplace +intro: 'Saiba mais sobre os selos que você pode ver em alguns aplicativos e anúncios de ações em {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### Para aplicativos GitHub + +Os aplicativos com {% octicon "verified" aria-label="The verified badge" %} pertencem a uma organização que: +- Confirmou o domínio dela +- Confirmou o endereço de e-mail da empresa, para que o suporte de {% data variables.product.prodname_dotcom %} possa entrar em contato com a empresa +- Exigiu a autenticação de dois fatores para sua organização. Para obter mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + +![Selo do Marketplace para Aplicativos GitHub](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +Para saber como adicionar esse selo ao seu aplicativo, consulte "[Candidatar-se para a verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". + +Para obter mais informações sobre os requisitos para a listagem de um aplicativo em {% data variables.product.prodname_marketplace %}, consulte "[Requisitos para listar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". + +Para obter informações sobre como encontrar aplicativos para usar, consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". + +### Para ações no GitHub + +Ações com {% octicon "verified" aria-label="The verified badge" %} ou com o selo de criador verificado indicam que {% data variables.product.prodname_dotcom %} verificou o criador da ação como uma organização parceira. + +![Selo de criador verificada para o GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +Para obter informações sobre como publicar uma ação do GitHub em {% data variables.product.prodname_marketplace %}, consulte "[Publicar ações no GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)". + +### Sobre o processo de verificação anterior para aplicativos + +Além do selo de criador verificado, você também verá selos referentes a aplicativos verificados e não verificados. Esses aplicativos foram publicados usando o método antigo para verificar aplicativos individuais. + +![Selo verde para verificado e cinza para não verificado](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**Observação:** O processo de verificação do novo publicador para aplicativos substitui o processo anterior em que os aplicativos individuais foram verificados. O novo processo de verificação de publicador é semelhante ao processo de verificação para ações. Se você tiver aplicativos que foram verificados no processo antigo, eles não serão afetados pelas alterações. A equipe de {% data variables.product.prodname_marketplace %} entrará em contato com você com detalhes sobre como fazer a migração para uma verificação baseada na organização. + +{% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..9b7bde8a4f --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Candidatar-se à verificação de publicador para a sua organização +intro: 'Para oferecer planos pagos para seu aplicativo ou para incluir um selo no Marketplace no anúncio do seu aplicativo, você deverá concluir o processo de verificação de publicação para a sua organização.' +versions: + free-pro-team: '*' +--- + +A verificação do editor garante que {% data variables.product.prodname_dotcom %} tem uma forma de entrar em contato com você, que você habilitou a autenticação de dois fatores para a sua organização e que o domínio da sua organização foi verificado. + +Assim que sua organização for verificada, você poderá publicar planos pagos para o seu aplicativo. Para obter informações, consulte "[Configurar planos de preços para o seu anúncio](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". + +Para oferecer planos pagos para o seu aplicativo, este deverá pertencer a uma organização e você deverá ter permissões de proprietário na organização. Se seu aplicativo pertence atualmente a uma conta de usuário, você precisará transferir a propriedade do aplicativo para uma organização. Para obter mais informações, consulte "[Transferir a propriedade de um aplicativo GitHub](/developers/apps/transferring-ownership-of-a-github-app)" ou "[Transferir a propriedade de um aplicativo OAuth](/developers/apps/transferring-ownership-of-an-oauth-app)". + +### Solicitar verificação de publicador + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. Na barra lateral esquerda, clique em **Developer settings** (Configurações do desenvolvedor). ![Opção de configurações do desenvolvedor na barra lateral de configurações da organização](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. Em "Configurações de desenvolvedor", clique em **Verificação do publicador**. ![Opção de verificação do editor na barra lateral de configurações da organização](/assets/images/marketplace/publisher-verification-settings-option.png) +1. Em "Verificação do Publicador, preencha as informações na lista de verificação: + - Certifique-se de que as suas informações básicas do perfil estejam presentes e precisas. Além disso, certifique-se de incluir o melhor endereço de e-mail para suporte e atualizações de {% data variables.product.company_short %}. + - Certifique-se de que a autenticação de dois fatores esteja habilitada para a sua organização. Para obter mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + - Envie um domínio verificado. Para obter informações relacionadas, consulte "[Verificar o domínio da sua organização](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)". + + ![Lista de verificação do publicador](/assets/images/marketplace/publisher-verification-checklist.png) + +1. Clique **Solicitar verificação**. {% data variables.product.company_short %} analisará as suas informações e informará assim que a verificação de publicação for concluída. + +### Leia mais + +Para obter informações sobre o processo de publicação de aplicativos, consulte "[Sobre o GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)". diff --git a/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 6658599377..ad90ca6d20 100644 --- a/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ Após criar um rascunho da listagem do {% data variables.product.prodname_market ### Enviar o seu aplicativo -Após concluir a sua listagem do {% data variables.product.prodname_marketplace %}, você poderá enviá-la para revisão na página **Visão geral**. Você vai precisar ler e aceitar o "[{% data variables.product.prodname_marketplace %} Contrato de desenvolvedor](/articles/github-marketplace-developer-agreement/)" e, em seguida, você poderá clicar em **Enviar para revisão**. Depois de enviar seu aplicativo para análise, um especialista em integração entrará em contato com você com informações adicionais sobre o processo de integração. Você pode saber mais sobre o processo de revisão de segurança e integração em "[Começando com {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)". +Após concluir a sua listagem do {% data variables.product.prodname_marketplace %}, você poderá enviá-la para revisão na página **Visão geral**. Você vai precisar ler e aceitar o "[{% data variables.product.prodname_marketplace %} Contrato de desenvolvedor](/articles/github-marketplace-developer-agreement/)" e, em seguida, você poderá clicar em **Enviar para revisão**. Depois de enviar seu aplicativo para análise, um especialista em integração entrará em contato com você com informações adicionais sobre o processo de integração. ### Remover uma listagem do {% data variables.product.prodname_marketplace %} diff --git a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview.md b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..deb49a8196 --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,8 @@ +--- +title: Visão geral do GitHub Marketplace +intro: 'Saiba como compartilhar seu aplicativo ou ação com a comunidade de {% data variables.product.company_short %} em {% data variables.product.prodname_marketplace %}.' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/developers/github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/index.md index 0842fc13a3..c80a2ad2e6 100644 --- a/translations/pt-BR/content/developers/github-marketplace/index.md +++ b/translations/pt-BR/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/pt-BR/content/developers/github-marketplace/receiving-payment-for-app-purchases.md b/translations/pt-BR/content/developers/github-marketplace/receiving-payment-for-app-purchases.md index 628aed3dd8..6b2d3688ab 100644 --- a/translations/pt-BR/content/developers/github-marketplace/receiving-payment-for-app-purchases.md +++ b/translations/pt-BR/content/developers/github-marketplace/receiving-payment-for-app-purchases.md @@ -13,14 +13,14 @@ versions: -After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process. +Depois que o seu anúncio de {% data variables.product.prodname_marketplace %} para um aplicativo com um plano pago for criado e aprovado, você fornecerá detalhes de pagamento para {% data variables.product.product_name %} como parte do processo de integração financeira. -Once your revenue reaches a minimum of $500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs. +Quando sua receita atingir o mínimo de US$ 500 dólares no mês, você receberá um pagamento eletrônico de {% data variables.product.company_short %}. Este será o rendimento das transações no mercado menos o valor cobrado por {% data variables.product.company_short %} para cobrir seus custos administrativos. -For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward. +Para transações feitas antes de 1 de janeiro de 2021, {% data variables.product.company_short %} irá reter 25% da renda da transação. Para transações feitas após essa data, apenas 5% é será retido por {% data variables.product.company_short %}. Esta alteração irá refletir-se nos pagamentos recebidos a partir do final de Janeiro de 2021. {% note %} -**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/github/site-policy/github-marketplace-developer-agreement)." +**Observação:** Para obter os detalhes dos preços atuais e dos termos de pagamento, consulte o "[ acordo do desenvolvedor de {% data variables.product.prodname_marketplace %}](/github/site-policy/github-marketplace-developer-agreement)". {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md index fc213a86bf..a71e1fb5d5 100644 --- a/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ Para proteger seus clientes, recomendamos que siga as práticas recomendadas em ### Requisitos para aplicativos pagos -Além dos requisitos para todos os aplicativos acima, cada aplicativo que você oferece como serviço pago em {% data variables.product.prodname_marketplace %} também deve atender aos seguintes requisitos: +Para publicar um plano pago para o seu aplicativo em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá pertencer a uma organização que seja um publicador verificado. Para obter mais informações sobre o processo de verificação ou transferência da propriedade do seu aplicativo, consulte "[Candidatar-se para a verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". + +Se seu aplicativo já está publicado e você é um editor verificado, você poderá publicar um novo plano pago no editor do plano de preços. Para obter mais informações, consulte "[Configurar planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". + +Para publicar um aplicativo pago (ou um aplicativo que ofereça um plano pago), você também deve atender aos seguintes requisitos: - Os {% data variables.product.prodname_github_app %}s deve ter, no mínimo, 100 instalações. - Os {% data variables.product.prodname_oauth_app %}s devem ter, no mínimo, 200 usuários. - Todos os aplicativos pagos devem lidar com eventos de compra de {% data variables.product.prodname_marketplace %} para novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter mais informações, consulte "[Requisitos de cobrança para aplicativos pagos](#billing-requirements-for-paid-apps)" abaixo. -- As organizações publicadoras devem ter um domínio verificado e devem habilitar a autenticação de dois fatores. Para obter mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." -Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio. +Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio do aplicativo. {% note %} -O processo de verificação está aberto às organizações. {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como fazer isso, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". +**Observação:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como transferir um aplicativo para uma organização, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 724d9292b8..43cb15d996 100644 --- a/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,11 +19,13 @@ versions: ### Sobre a configuração dos planos de preços -Se desejar vender um aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar verificação ao publicar o anúncio do seu aplicativo. Durante o processo de verificação, um especialista em integração verifica as configurações de identidade e segurança da organização. O especialista em integração fará com que a organização passe pela integração financeira. Para mais informações, consulte: "[Requisitos para anunciar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". +{% data variables.product.prodname_marketplace %} oferece vários tipos diferentes de planos de preços. Para obter informações detalhadas, consulte "[Planos de preços para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". -{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como fazer isso, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". +Para oferecer um plano pago para seu aplicativo, este deve ser pertencente a uma organização que tenha concluído o processo de verificação de editor e atendido a certos critérios. Para obter mais informações, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" e "[Requisitos para listar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". -{% data variables.product.prodname_marketplace %} oferece vários tipos diferentes de plano de preços. Para obter informações detalhadas, consulte "[Planos de preços para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". +Se seu aplicativo já foi publicado com um plano pago e você é um editor verificado, você poderá publicar um novo plano pago a partir da página "Editar um plano de preços" nas configurações da listagem do seu aplicativo do Marketplace. + +![Botão Publicar este plano](/assets/images/marketplace/publish-this-plan-button.png) ### Sobre como salvar planos de preços diff --git a/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md index 3911035dc7..fe8612db1d 100644 --- a/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: Enviando seu anúncio para publicação -intro: 'Você pode enviar seu anúncio para a comunidade {% data variables.product.prodname_dotcom %} usar.' +intro: 'Para concluir o envio do anúncio do seu aplicativo, você pode solicitar que uma análise seja realizada por um especialista em integração.' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +Quando anúncio do seu aplicativo atender aos requisitos de {% data variables.product.prodname_marketplace %}, você poderá enviar o seu aplicativo. Para obter uma visão geral dos requisitos de anúncio de aplicativos, consulte "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)". +1. Na parte superior esquerda da página de anúncio do aplicativo, clique em **Visão geral**. Para obter informações sobre como encontrar a página de anúncio do seu aplicativo, consulte "[Desenhar um anúncio para o seu aplicativo](/developers/github-marketplace/drafting-a-listing-for-your-app)". -Depois de concluir o anúncio do seu aplicativo, você verá dois botões que permitem que você solicite a publicação do anúncio, com ou sem verificação. O botão **Solicitar** para "Publicar sem verificação" encontra-se desabilitado se você tiver publicado algum plano de preços pago no anúncio. + ![Opção de visão geral para o anúncio de rascunho do Marketplace](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![Botão de solicitação verificada e não verificada](/assets/images/marketplace/marketplace-request-button.png) +2. Para enviar o seu anúncio completo de aplicativos, clique em **Solicitar revisão**. -{% data reusables.marketplace.launch-with-free %} + ![Lista de verificação para "Publicar o seu aplicativo no Marketplace" com o botão de envio na parte inferior](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -Depois de enviar seu anúncio para revisão, um especialista de integração entrará em contato com você com informações adicionais. - -Para uma visão geral do processo de criação e envio de uma listagem, consulte "[Sobre {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)". - -### Pré-requisitos para publicação com verificação - -Antes de solicitar a verificação do seu anúncio, você precisará integrar os fluxos de cobrança de {% data variables.product.prodname_marketplace %} e webhook no seu aplicativo. Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". - -Se você cumpriu os requisitos para o anúncio integrou-se à API de {% data variables.product.prodname_marketplace %}, envie o seu anúncio. Para obter mais informações, consulte "[Requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app)". - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para informações sobre como fazer isso, consulte: "[Transferir um aplicativo para uma organização antes de enviar](#transferring-an-app-to-an-organization-before-you-submit)" abaixo. - -### Transferir um aplicativo para uma organização antes de enviar - -Você não pode vender um app que pertence a uma conta de usuário. Você precisa transferir o aplicativo para uma organização que já é um criador verificado ou que possa solicitar verificação para um anúncio do aplicativo. Para detalhes, consulte: - -1. "[Criar uma organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" - -1. "[Transferir a propriedade de um aplicativo GitHub](/developers/apps/transferring-ownership-of-a-github-app)" ou "[Transferir a propriedade de um aplicativo OAuth](/developers/apps/transferring-ownership-of-an-oauth-app)" +Um especialista de integração entrará em contato com você com informações adicionais. diff --git a/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index c5f6b30520..1f947074f0 100644 --- a/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Visualizar transações para a sua listagem -intro: 'A página de transações do {% data variables.product.prodname_marketplace %} permite que você faça o download e visualize todas as transações para a sua listagem do {% data variables.product.prodname_marketplace %}. Você pode visualizar as transações para o último dia (24 horas), semana, mês ou referente a todo o tempo em que sua {% data variables.product.prodname_github_app %} foi listado.' +intro: 'A página de transações do {% data variables.product.prodname_marketplace %} permite que você faça o download e visualize todas as transações para a sua listagem do {% data variables.product.prodname_marketplace %}. Você pode visualizar as transações do último dia (24 horas), semana, mês ou por todo o período em que o seu {% data variables.product.prodname_github_app %} foi listado.' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/pt-BR/content/developers/overview/secret-scanning.md b/translations/pt-BR/content/developers/overview/secret-scanning.md index 1017a9386b..b0b13749b2 100644 --- a/translations/pt-BR/content/developers/overview/secret-scanning.md +++ b/translations/pt-BR/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: Varredura secreta intro: 'Como um provedor de serviço, você pode associar-se ao {% data variables.product.prodname_dotcom %} para proteger os seus formatos de token secretos por varredura de segredos, que pesquisa commits acidentais no seu formato secreto e que pode ser enviado para o ponto de extremidade de verificação de um provedor de serviços.' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -O {% data variables.product.prodname_dotcom %} faz a varredura de repositórios de formatos secretos conhecidos para evitar uso fraudulento de credenciais confirmadas acidentalmente. A verificação secreta acontece por padrão em repositórios públicos e pode ser ativada em repositórios privados por administradores de repositórios ou proprietários de organizações. Como um provedor de serviço, você pode associar-se ao {% data variables.product.prodname_dotcom %} para que seus formatos secretos estejam incluídos em nossa varredura de segredos. +O {% data variables.product.prodname_dotcom %} faz a varredura de repositórios de formatos secretos conhecidos para evitar uso fraudulento de credenciais confirmadas acidentalmente. {% data variables.product.prodname_secret_scanning_caps %} acontece por padrão em repositórios públicos e pode ser habilitado em repositórios privados por administradores de repositório ou proprietários da organização. Como provedor de serviço, você pode fazer parcerias com {% data variables.product.prodname_dotcom %} para que seus formatos de segredo estejam incluídos em nosso {% data variables.product.prodname_secret_scanning %}. Quando uma correspondência do seu formato secreto é encontrada em um repositório público, uma carga é enviada para um ponto de extremidade HTTP de sua escolha. -Quando uma correspondência do seu formato secreto é encontrada em um repositório privado configurado para varredura de segredos, os administradores do repositório são alertados e podem visualizar e gerenciar os resultados da varredura secreta em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciar alertas do varredura de segredos](/github/administering-a-repository/managing-alerts-from-secret-scanning)". +Quando uma correspondência do formato do segredo é encontrada em um repositório privado configurado para {% data variables.product.prodname_secret_scanning %}, os administradores do repositório são alertados e podem visualizar e gerenciar os resultados {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." {% note %} -**Observação:** A verificação secreta de repositórios privados encontra-se atualmente em beta. +**Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios privados está atualmente em beta. {% endnote %} -Este artigo descreve como você pode associar-se ao {% data variables.product.prodname_dotcom %} como um provedor de serviço e participar do programa de varredura secreto. +Este artigo descreve como fazer parceria com {% data variables.product.prodname_dotcom %} como um provedor de serviço e participa do programa de {% data variables.product.prodname_secret_scanning %}. -### O processo de varredura de segredo +### O processo de {% data variables.product.prodname_secret_scanning %} -##### Como funciona a varredura de segredo em um repositório público +##### Como {% data variables.product.prodname_secret_scanning %} funciona em um repositório público -O diagrama a seguir resume o processo de varredura de segredo de repositórios públicos, com quaisquer correspondências enviadas para o ponto de extremidade de verificação de um provedor de serviços. +O diagrama a seguir resume o processo de {% data variables.product.prodname_secret_scanning %} para repositórios públicos, com qualquer correspondência enviada para o ponto de extremidade de verificação de um provedor de serviços. -![Diagrama do fluxo que mostra o processo de varredura de um segredo e envio de correspondências para o ponto de extremidade de verificação de um provedor de serviços](/assets/images/secret-scanning-flow.png "Fluxo de varredura de segredo") +![Diagrama do fluxo que mostra o processo de varredura de um segredo e envio de correspondências para o ponto de extremidade de verificação de um provedor de serviços](/assets/images/secret-scanning-flow.png "Fluxo de {% data variables.product.prodname_secret_scanning_caps %}") -### Associar-se ao programa de varredura secreto em {% data variables.product.prodname_dotcom %} +### Juntando-se ao programa de {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %} 1. Entre em contato com {% data variables.product.prodname_dotcom %} para dar início ao processo. 1. Identifique os segredos relevantes cuja varredura você deseja realizar e crie expressões regulares para capturá-los. -1. Para correspondências secretas encontradas em repositórios públicos, crie um serviço de alerta secreto que aceita webhooks do {% data variables.product.prodname_dotcom %}, que contêm a carga da mensagem da varredura de segredo. +1. Para correspondências de segredos encontradas em repositórios públicos, crie um serviço de alerta de segredo que aceite webhooks de {% data variables.product.prodname_dotcom %} que contenham a carga da mensagem de {% data variables.product.prodname_secret_scanning %}. 1. Implemente a verificação de assinatura em seu serviço de alerta secreto. 1. Implemente revogação do segredo e notificação do usuário no seu serviço de alerta secreto. +1. Fornece feedback sobre falsos positivos (opcional). #### Entre em contato com {% data variables.product.prodname_dotcom %} para dar início ao processo -Para iniciar o processo de inscrição, envie um e-mail para secret-scanning@github.com. +Para iniciar o processo de inscrição, envie um e-mail para secret-scanning@github.com. -Você receberá os detalhes sobre o programa de verificação secreta e deverá concordar com os termos de participação de {% data variables.product.prodname_dotcom %} antes de prosseguir. +Você receberá detalhes do programa de {% data variables.product.prodname_secret_scanning %} e você precisará aceitar os termos de participação de {% data variables.product.prodname_dotcom %} antes de prosseguir. #### Identifique seus segredos e crie expressões regulares -Para fazer a varredura dos seus segredos, o {% data variables.product.prodname_dotcom %} precisa das seguintes informações para cada segredo que você desejar incluir no programa de varredura de segredo: +Para fazer a varredura dos seus segredos, {% data variables.product.prodname_dotcom %} precisa das informações a seguir para cada segredo que você deseja que seja incluído no programa {% data variables.product.prodname_secret_scanning %}: * Um nome único e legível para o tipo do segredo. Nós vamos usá-lo para gerar o valor `Tipo` na carga da mensagem posteriormente. * Uma expressão regular que encontra o tipo do segredo. Seja o mais preciso possível, pois isso reduzirá o número de falsos positivos. * A URL do ponto de extremidade que recebe mensagens de {% data variables.product.prodname_dotcom %}. Isso não precisa ser único para cada tipo de segredo. -Envie esta informação para o secret-scanning@github.com. +Envie esta informação para secret-scanning@github.com. #### Crie um serviço de alerta secreto @@ -61,7 +62,7 @@ Crie um ponto de extremidade HTTP público e acessível à internet na URL que v ##### Exemplo de POST enviado para seu ponto de extremidade -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ Você pode recuperar a chave pública de da varredura secreta do segredo do {% d Supondo que você receba a mensagem a seguir, os trechos de código abaixo demonstram como você poderia efetuar a validação da assinatura. O código também assume que você definiu uma variável de ambiente denominada `GITHUB_PRODUCTION_TOKEN` com um PAT gerado (https://github.com/settings/tokens). O token não precisa de nenhuma permissão definida. **Mensagem de exemplo enviada para verificar o ponto de extremidade** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -277,4 +278,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### Implemente revogação do segredo e notificação do usuário no seu serviço de alerta secreto -Para a verificação de segredo de repositórios públicos, é possível melhorar o serviço de alerta de segredo para revogar os segredos expostos e notificar os usuários afetados. Você define como implementa isso no seu serviço de alerta de segredo, mas recomendamos considerar qualquer segredo que {% data variables.product.prodname_dotcom %} envie mensagens de que é público e que está comprometido. +Para {% data variables.product.prodname_secret_scanning %} em repositórios públicos, você pode melhorar o seu serviço de alerta de segredo para revogar os segredos expostos e notificar os usuários afetados. Você define como implementa isso no seu serviço de alerta de segredo, mas recomendamos considerar qualquer segredo que {% data variables.product.prodname_dotcom %} envie mensagens de que é público e que está comprometido. + +#### Fornece feedback sobre falsos positivos + +Coletamos feedback sobre a validade dos segredos individuais detectados nas respostas do parceiro. Se você deseja participar, envie um e-mail para secret-scanning@github.com. + +Quando relatamos segredos para você, enviamos uma matriz JSON com cada elemento que contém o token, o identificador de tipo e a URL dp commit. Quando você nos envia feedback, você nos envia informações sobre se o token detectado era uma credencial real ou falsa. Aceitamos comentários nos seguintes formatos. + +Você pode nos enviar o token não processado: + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +Você também pode fornecer o token em forma de hash após executar uma única forma de hash criptográfico do token não processado usando SHA-256: + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +Alguns pontos importantes: +- Você deve enviar-nos apenas a forma não processada do token ("token_raw"), ou a forma em hash ("token_hash"), mas não ambos. +- Para a forma de hash do token não processado, você só pode usar SHA-256 para armazenar o token, e não qualquer outro algoritmo de hashing. +- A etiqueta indica se o token é verdadeiro ("true_positive") ou um falso positivo ("false_positive"). São permitidas apenas essas duas strings literais minúsculas. + +{% note %} + +**Nota:** Nosso tempo limite de solicitação está definido para ser maior (isto é, 30 segundos) para parceiros que fornecem dados sobre falsos positivos. Se você precisar de um tempo limite superior a 30 segundos, envie um e-mail para secret-scanning@github.com. + +{% endnote %} + diff --git a/translations/pt-BR/content/discussions/index.md b/translations/pt-BR/content/discussions/index.md index 2bdc454757..61d4baab9c 100644 --- a/translations/pt-BR/content/discussions/index.md +++ b/translations/pt-BR/content/discussions/index.md @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -43,7 +43,7 @@ versions: {% render 'discussions-community-card' for discussionsCommunityExamples as example %} {% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
    {% octicon "search" width="24" %}
    diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..4ba7023939 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +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.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-advisors + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +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)". + +{% note %} + +**Observação:** como um instrutor, você não pode criar contas do {% data variables.product.prodname_dotcom %} para seus alunos. Os estudantes devem criar as próprias contas do {% data variables.product.prodname_dotcom %}. + +{% endnote %} diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..6dd8efa3dd --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: Sobre Especialistas de campus +intro: 'Como aluno, adquira as habilidades necessárias para criar a comunidade tecnológica da sua escola e um portfólio do mundo real com o treinamento Especialistas de campus do {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +Aprenda as habilidades de falar em público, escrita técnica, liderança de comunidade e desenvolvimento de software como um Especialista de campus do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Especialistas de campus](https://education.github.com/students/experts)". diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..54104b6c89 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: Sobre o GitHub Education para educadores e pesquisadores +intro: 'O {% data variables.product.prodname_education %} oferece várias ferramentas para ajudar os educadores e pesquisadores a trabalhar de maneira mais eficaz dentro e fora da sala de aula.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} para educadores + +Com os serviços e ferramentas do {% data variables.product.prodname_education %} para educadores de todos os níveis, você pode: + - Usar o [{% data variables.product.prodname_classroom %}](https://classroom.github.com) para distribuir código, dar feedback aos alunos e coletar atribuições no {% data variables.product.prodname_dotcom %}. + - Ingressar na nossa [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) para discutir tendências atuais na educação tecnológica com seus colegas ao redor do mundo. + - Acessar e adaptar nossos [planos de estudo de código aberto](https://education.github.community/t/open-source-lesson-plans/1591) para ensinar sobre o Git e o {% data variables.product.prodname_dotcom %}. + - [Solicitar um kit surpresa do {% data variables.product.prodname_dotcom %}](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) com materiais e brindes educativos para os estudantes. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} para pesquisadores + +Com os serviços e ferramentas do {% data variables.product.prodname_education %} para pesquisadores, você pode: + - Colaborar com outras pessoas no trabalho de pesquisa ao redor do mundo no {% data variables.product.prodname_dotcom %}. + - [Aprender](https://education.github.com/stories) como as instituições acadêmicas ao redor do mundo estão usando o {% data variables.product.prodname_dotcom %} para suas pesquisas. + {% data reusables.education.apply-for-team %} + +### Leia mais + +- "[Sobre o {% data variables.product.prodname_education %} para estudantes](/articles/about-github-education-for-students)" diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..3306814b5d --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: Sobre o GitHub Education para estudantes +intro: 'O {% data variables.product.prodname_education %} proporciona aos estudantes do mundo real experiência com acesso grátis a várias ferramentas de desenvolvedor de parceiros do {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Usar o {% data variables.product.prodname_dotcom %} nos projetos da sua escola é uma maneira prática de colaborar com outras pessoas e de criar um portfólio que demonstra experiência no mundo real. + +{% data reusables.education.about-github-education-link %} + +Cada pessoa com uma conta do {% data variables.product.prodname_dotcom %} pode colaborar em repositórios públicos e privados ilimitados com o {% data variables.product.prodname_free_user %}. Como estudante, você também pode solicitar o {% data variables.product.prodname_student_pack %}, que oferece acesso grátis às ferramentas e aos serviços usados por desenvolvedores profissionais. Para obter mais informações, consulte "[Aplicar um pacote de desenvolvedor para estudante](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" e [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +Se você for integrante de um clube de robótica FIRST, seu mentor poderá solicitar um desconto para educador para que sua equipe possa colaborar usando o {% data variables.product.prodname_team %}, que permite repositórios privados e de usuários ilimitados, gratuitamente. Para obter mais informações, consulte "[Aplicar um desconto para educador ou pesquisador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)". + +### Leia mais + +- "[Sobre o {% data variables.product.prodname_education %} para educadores e pesquisadores](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..35b7b6ef75 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: Sobre o GitHub Education +intro: 'O {% data variables.product.prodname_education %} oferece um produto gratuito especial para escolas que querem aproveitar o {% data variables.product.prodname_dotcom %} ao máximo na respectiva comunidade e que concordam com os requisitos específicos do programa.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +Se a sua escola concorda em atender a determinados requisitos, sua escola secundária, universidade ou bootcamp pode obter o {% data variables.product.prodname_education %}, que oferece o melhor do {% data variables.product.prodname_dotcom %} gratuitamente, incluindo: +- {% data variables.product.prodname_ghe_cloud %} e/ou {% data variables.product.prodname_ghe_server %} +- Treinamento do professor para domínio do Git e do {% data variables.product.prodname_dotcom %} com nosso programa de consultores de campus +- Acesso automatizado a recursos premium do {% data variables.product.prodname_education %}, como o {% data variables.product.prodname_student_pack %} +- Desenvolvimento da liderança e treinamento técnico para estudantes com o programa de especialistas de campus + +Para obter mais informações, consulte a página [oficial do {% data variables.product.prodname_education %}](https://education.github.com/partners/schools). + +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)". + +Para saber mais sobre programas de treinamento para líderes estudantis e professores, consulte "[especialistas de campus do {% data variables.product.prodname_dotcom %}](https://education.github.com/students/experts)" e "[consultores de campus](https://education.github.com/teachers/advisors)". + +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_education %}, 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/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" ou "[Usar o {% data variables.product.prodname_dotcom %} em sala de aula e em pesquisas](/education/explore-the-benefits-of-teaching-and-learning-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/apply-for-a-student-developer-pack.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..1881cdd50f --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: Aplicar ao pacote de desenvolvedor de aluno +intro: 'Como um estudante, você pode se candidatar ao {% data variables.product.prodname_student_pack %}, que inclui ofertas e benefícios dos parceiros {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Requisitos + +Para se qualificar para o {% data variables.product.prodname_student_pack %}, você deve: +- Estar atualmente matriculado em um curso superior ou curso que conceda um diploma, tal como ensino médio, ensino secundário, faculdade, universidade, educação domiciliar ou instituição de ensino similar +- Ter um endereço de e-mail verificável concedido pela instituição de ensino ou fazer upload de documentos que comprovem seu status de estudante +- Ter uma conta de usuário do [{% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account) +- Ter pelo menos 13 anos + +Documentos que provam o seu estado atual do aluno incluem uma foto do seu ID da escola com a data atual de matrícula. cronograma de aula, histórico escolar e carta de verificação de afiliação ou inscrição. + +Durante o período como estudante, pode ser que você seja solicitado a verificar periodicamente seu status acadêmico atual. + +{% note %} + +**Observação:** não é possível transferir descontos acadêmicos de uma conta para outra. Se você tiver mais de uma conta em que queira aplicar o desconto, considere [fazer merge](/articles/merging-multiple-user-accounts) das suas contas de usuários e [renomear](/articles/changing-your-github-username) a conta retida se desejado. + +{% endnote %} + +Para obter informações sobre como renovar seu {% data variables.product.prodname_student_pack %}, consulte "[Vencimento e renovações](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)". + +### Candidatar-se a um {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. Em "Which best describes your academic status?" (Qual opção melhor descreve seu status acadêmico?), selecione **Student** (Estudante). ![Selecione o status acadêmico](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Vencimento e renovações + +Assim que seu acesso ao {% data variables.product.prodname_student_pack %} expirar, você poderá se recandidatar se ainda estiver qualificado, embora algumas das nossas ofertas de parceiro não possam ser renovadas. A maioria das ofertas com tempo limitado de nossos parceiros entra em vigor assim que você as configura. Para obter mais informações, consulte a página do [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). + +Para ver quando seu acesso grátis ao {% data variables.product.prodname_student_pack %} expira, visite as [configurações de cobrança](https://github.com/settings/billing) da sua conta. + +### Leia mais + +- "[Por que minha solicitação para um {% data variables.product.prodname_student_pack %} não foi aprovada?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..8523fecddf --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: Solicitar um desconto de educador ou pesquisador +intro: 'Sendo um educador ou pesquisador, você pode se candidatar para receber o {% data variables.product.prodname_team %} gratuitamente para a conta da sua organização.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### Sobre descontos para educador e pesquisador + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +Para obter mais informações sobre contas de usuário em {% data variables.product.product_name %}, consulte "[Cadastrar-se para uma nova conta de {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/signing-up-for-a-new-github-account)". + +### Candidatar-se a um desconto de educador ou pesquisador + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Atualizar sua organização + +Depois que sua solicitação para desconto de educador ou pesquisador for aprovada, você poderá atualizar as organizações que usa com sua comunidade de aprendizagem para o {% data variables.product.prodname_team %}, o que permite usuários ilimitados e repositórios privados com recursos completos, gratuitamente. Você pode atualizar uma organização existente ou criar uma para atualizar. + +#### Atualizar uma organização existente + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Atualizar uma nova organização + +{% data reusables.education.upgrade-page %} +1. Clique em {% octicon "plus" aria-label="The plus symbol" %} **Create an organization** (Criar uma organização). ![Botão Create an organization (Criar uma organização)](/assets/images/help/education/create-org-button.png) +3. Leia as informações e clique em **Criar organização**. ![Botão Create an organization (Criar uma organização)](/assets/images/help/education/create-organization-button.png) +4. Em "Choose a plan" (Escolher um plano), clique em **Escolher {% data variables.product.prodname_free_team %}**. +5. Siga as instruções para criar sua organização. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Leia mais + +- "[Por que minha solicitação para desconto de educador ou pesquisador não foi aprovada?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [Vídeos do {% data variables.product.prodname_classroom %}](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..7f8e77e134 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore os benefícios de ensinar e aprender com o GitHub Education +shortTitle: Explorar +intro: Aprenda como {% data variables.product.prodname_education %} pode beneficiar sua sala de aula, trabalho escolar ou pesquisa e como inscrever-se para ter acesso gratuito a várias ferramentas de desenvolvedor dos parceiros de {% data variables.product.company_short %}. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Índice + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..7576dcf44f --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: Use o GitHub na sua instituição educacional +intro: 'Maximize os benefícios de usar o {% data variables.product.prodname_dotcom %} na sua instituição para alunos, instrutores e equipe de TI com o {% data variables.product.prodname_education %} e nossos diversos programas de treinamento para alunos e instrutores.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..9b8f06ba04 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: Use o GitHub para tarefas de aprendizagem +intro: 'Como aluno, use o {% data variables.product.prodname_dotcom %} para colaborar nos projetos da sua escola e ganhar experiência no mundo real.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..75044e8cfb --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: Use o GitHub em aula e pesquisas +intro: 'Como educador ou pesquisador, use o {% data variables.product.prodname_dotcom %} para colaborar no seu trabalho em sala de aula, em um grupo de pesquisa ou de alunos, e muito mais.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/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/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..22808a05d5 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Dica:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Falta de clareza em documentos de afiliação acadêmica + +Se a imagem que você enviou por upload não identificar claramente seu status acadêmico atual, exigiremos mais provas dele. {% 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 o seu endereço de e-mail acadêmico já tiver sido usado para solicitar um {% data variables.product.prodname_student_pack %} para outra conta do {% data variables.product.prodname_dotcom %}, você não poderá reutilizá-lo para se candidatar a outro {% data variables.product.prodname_student_pack %} enquanto o desconto estiver válido. + +{% 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á matriculado em um programa de aprendizado informal que não faz parte do [programa de campus do {% data variables.product.prodname_dotcom %}](https://education.github.com/schools) e não está matriculado em um curso superior ou técnico. +- 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ê for aluno de uma escola de programação ou de um bootcamp, só estará qualificado para um {% data variables.product.prodname_student_pack %} se a sua instituição de ensino participar do [programa de campus do {% data variables.product.prodname_dotcom %}](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/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..3da3ceacee --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: Motivos da reprovação da candidatura ao desconto de educador ou pesquisador +intro: Analise os motivos comuns para a reprovação de candidaturas ao desconto de educador ou pesquisador e veja dicas para se candidatar novamente sem problemas. +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Dica:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Falta de clareza em documentos que comprovam a afiliação + +Se a imagem que você enviou por upload não identificar claramente sua ocupação atual em uma instituição de ensino ou universidade, você precisará se candidatar novamente e enviar por upload outra imagem do seu crachá na faculdade ou de uma carta de verificação de referência pessoal com informações claras. + +{% 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, poderemos exigir mais provas do seu status acadêmico. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Uso de e-mail acadêmico de uma escola com políticas de e-mail pouco rígidas + +Se ex-alunos e professores aposentados da sua instituição de ensino tiverem acesso vitalício a endereços de e-mail concedidos pela escola, poderemos exigir mais provas do seu status acadêmico. {% data reusables.education.upload-different-image %} + +{% 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. + +### Candidatura de não alunos ao pacote de desenvolvedor para estudante + +Educadores e pesquisadores não estão qualificados para as ofertas de parceiros que acompanham o [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Quando você se candidatar novamente, lembre-se de escolher **Faculty** (Faculdade) para descrever seu status acadêmico. + +### Leia mais + +- "[Solicite desconto para educador ou pesquisador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/pt-BR/content/education/guides.md b/translations/pt-BR/content/education/guides.md index abf2f33035..bd07a83cd7 100644 --- a/translations/pt-BR/content/education/guides.md +++ b/translations/pt-BR/content/education/guides.md @@ -12,8 +12,8 @@ Professores, estudantes e pesquisadores podem usar ferramentas de {% data variab - [Cadastre-se para uma nova conta de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-a-new-github-account) - [Git e início rápido de {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/quickstart) -- [Solicitar um desconto de educador ou pesquisador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Aplicar ao pacote de desenvolvedor de aluno](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) +- [Solicitar um desconto de educador ou pesquisador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Aplicar ao pacote de desenvolvedor de aluno](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) ### Execute um curso de desenvolvimento software com {% data variables.product.company_short %} @@ -32,7 +32,7 @@ Administrar uma sala de aula, atribuir e revisar o trabalho de seus alunos e ens Incorpore {% data variables.product.prodname_dotcom %} na sua educação e use as mesmas ferramentas dos profissionais. - [Git e recursos de aprendizagem de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/git-and-github-learning-resources) -- [Use {% data variables.product.prodname_dotcom %} para o seu trabalho na escola](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [Use {% data variables.product.prodname_dotcom %} para o seu trabalho na escola](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork) - [Experimente {% data variables.product.prodname_desktop %}](/desktop) - [Experimente {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) @@ -41,5 +41,5 @@ Incorpore {% data variables.product.prodname_dotcom %} na sua educação e use a Participe da comunidade, receba treinamento de {% data variables.product.company_short %}, e aprenda ou ensine novas habilidades. - [{% data variables.product.prodname_education_community %}](https://education.github.community) -- [Sobre Especialistas de campus](/education/teach-and-learn-with-github-education/about-campus-experts) -- [Sobre Consultores de campus](/education/teach-and-learn-with-github-education/about-campus-advisors) +- [Sobre Especialistas de campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) +- [Sobre Consultores de campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) diff --git a/translations/pt-BR/content/education/index.md b/translations/pt-BR/content/education/index.md index 15ace3db12..5c35dc0248 100644 --- a/translations/pt-BR/content/education/index.md +++ b/translations/pt-BR/content/education/index.md @@ -1,45 +1,41 @@ --- title: Documentação do GitHub Education shortTitle: Educação -intro: "{% data variables.product.prodname_education %} ajuda você a ensinar ou aprender desenvolvimento de software com as ferramentas e suporte da plataforma e comunidade de {% data variables.product.company_short %}." +intro: '{% data variables.product.prodname_education %} ajuda você a ensinar ou aprender desenvolvimento de software com as ferramentas e suporte da plataforma e comunidade de {% data variables.product.company_short %}.' introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom changelog: - - - title: 'Try something new at Local Hack Day: Learn' + - title: 'Tente algo novo no dia local do Hack: Aprenda' date: '2020-10-15' - href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ - - - title: 'Educação remota: criar comunidade por meio de experiências compartilhadas' + href: 'https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/' + - title: 'Educação remota: criar comunidade por meio de experiências compartilhadas' date: '2020-09-24' - href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ - - - title: 'Educação remota: Uma série de práticas recomendadas para comunidades do campus on-line' + href: 'https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/' + - title: 'Educação remota: Uma série de práticas recomendadas para comunidades do campus on-line' date: '2020-09-10' - href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ - - - title: Bem-vindo à classe inaugural de MLH Fellows + href: 'https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/' + - title: Bem-vindo à classe inaugural de MLH Fellows date: '2020-06-24' - href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ + href: 'https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/' layout: product-landing versions: free-pro-team: '*' --- - + diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index e055802e86..5a060da9d9 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ Para obter mais informações sobre aulas com {% data variables.product.prodname ### Leia mais -- "[Ensine e aprenda com {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" +- "[Explore os benefícios do ensino e da aprendizagem com {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 72761cba75..07b4b52ef5 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -140,6 +140,6 @@ Você pode ver as equipes que estão trabalhando ou que enviaram uma atividade n ### Leia mais -- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquise](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" - "[Conecte um sistema de gerenciamento de aprendizagem para {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" - [Usar Equipes Existentes atividades em grupo?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) na comunidade de {% data variables.product.prodname_education %} diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index 27aa2b1306..115043295e 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,8 +11,6 @@ Você pode utilizar um repositório de modelo em {% data variables.product.produ Para usar o repositório de modelo para a sua atribuição, o repositório de modelo deve pertencer à sua organização, ou a visibilidade do repositório de modelos deverá ser pública. -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} Para obter mais informações, consulte "[Definir as configurações-padrão para repositórios de atividades](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)". - ### Leia mais - "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index efe8208272..5ad58c1f2c 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -120,5 +120,5 @@ Você pode ver se um aluno juntou-se à sala de aula e aceitou ou enviou uma ati ### Leia mais -- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquise](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" - "[Conecte um sistema de gerenciamento de aprendizagem para {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md index 59e8df2aa1..02fd5c8bb5 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index 505b06b61c..6e153a82c5 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ Você pode arquivar uma sala de aula que você não usa mais em {% data variable {% 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 nome da sala de aula](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +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) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 7b7bd5e6b9..d6d442772a 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -4,5 +4,8 @@ intro: Aprenda a configurar sua sala de aula e suas atividades. mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md index 50ca42cd02..d18d0ff406 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -43,3 +43,7 @@ Se tiver habilitado atualizações de segurança, às vezes você verá atualiza {% data reusables.dependabot.supported-package-managers %} Se o seu repositório já usa uma integração para gerenciamento de dependências, você precisará desativar isso antes de habilitar o {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre integrações](/github/customizing-your-github-workflow/about-integrations)". + +### Sobre notificações para atualizações de versão para {% data variables.product.prodname_dependabot %} + +Você pode filtrar suas notificações em {% data variables.product.company_short %} para mostrar atualizações de versão de {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". diff --git a/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index d4a28706c6..04be7feed9 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -44,9 +44,9 @@ Cada notificação de e-mail para um push no repositório lista os novos commits 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) -6. Se você é quem opera o seu próprio servidor, será possível verificar a integridade dos e-mails por meio do token **Secret**. Esse token é enviado com o e-mail como o header `Approved`. Se o header `Approved` corresponder ao token enviado, você poderá confiar que esse e-mail é do {% data variables.product.product_name %}. ![Caixa de texto do segredo do e-mail](/assets/images/help/settings/email_services_token.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 **Save settings** (Salvar configurações). ![Botão Save settings (Salvar configurações)](/assets/images/help/settings/save_notification_settings.png) +7. Clique em **Configurar notificações**. ![Botão para configurar notificações](/assets/images/help/settings/setup_notifications_settings.png) diff --git a/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md index 47147dae57..4ccee3888e 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-merge-methods-on-github.md @@ -14,7 +14,7 @@ versions: {% data reusables.pull_requests.default_merge_option %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. Para obter mais informações, consulte "[Exigindo um histórico de commit linear](/github/administering-a-repository/requiring-a-linear-commit-history)".{% endif %} +O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} ### Combinar por squash os commits de merge diff --git a/translations/pt-BR/content/github/administering-a-repository/about-releases.md b/translations/pt-BR/content/github/administering-a-repository/about-releases.md index b43680a4f6..9bfc0deb56 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-releases.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-releases.md @@ -25,7 +25,7 @@ Você pode receber notificações quando novas versões são publicadas em um re Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar versões, mas somente pessoas com permissões de gravação a um repositório podem gerenciar versões. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Pessoas com permissões de administrador para um repositório podem escolher se {% data variables.large_files.product_name_long %} os objetos de ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte " diff --git a/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md b/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md index 4bd9474d0a..3ccdd33769 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md @@ -8,116 +8,59 @@ redirect_from: - /articles/about-token-scanning-for-private-repositories versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + Se o seu projeto se comunicar com um serviço externo, você pode usar um token ou uma chave privada para autenticação. Tokens e chaves privadas são exemplos de segredos que um provedor de serviços pode publicar. Se você marcar um segredo em um repositório, qualquer pessoa que tenha acesso de leitura ao repositório pode usar o segredo para acessar o serviço externo com seus privilégios. Recomendamos que você armazene segredos em um local dedicado e seguro fora do repositório do seu projeto. +Os provedores de serviço podem fazer parceria com -Se alguém verificar um segredo de um parceiro {% data variables.product.company_short %} em um repositório público ou privado, {% data variables.product.prodname_secret_scanning %} pode detectar o segredo e ajudar você a mitigar o impacto do vazamento. +{% data variables.product.company_short %} para fornecer seus formatos de segredo para varredura.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Varredura de segredo](/developers/overview/secret-scanning)". +{% endif %} -Os provedores de serviço podem fazer parceria com o {% data variables.product.company_short %} para fornecer os respectivos formatos de segredo para verificação. Para obter mais informações, consulte "[Verificação de segredo](/partnerships/secret-scanning)". +{% data reusables.secret-scanning.about-secret-scanning %} +{% if currentVersion == "free-pro-team@latest" %} ### Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios públicos - {% data variables.product.prodname_secret_scanning_caps %} é automaticamente habilitado em repositórios públicos, em que faz a varredura de código para saber se há segredos, para verificar os formatos de segredos conhecidos. Quando uma correspondência do seu formato de segredo é encontrada em um repositório público, {% data variables.product.company_short %} não divulga publicamente as informações como um alerta, mas envia uma carga para um ponto de extremidade de HTTP da sua escolha. Para uma visão geral de como a varredura de segredo funciona em repositórios públicos, consulte "[Varredura de segredo](/developers/overview/secret-scanning)". +{% data variables.product.prodname_secret_scanning_caps %} é automaticamente habilitado nos repositórios públicos. Quando você faz push para um repositório público, o {% data variables.product.product_name %} verifica segredos no conteúdo dos commits. Se você alternar um repositório privado para público, o {% data variables.product.product_name %} verifica segredos em todo o repositório. -Quando você faz push para um repositório público, o {% data variables.product.product_name %} verifica segredos no conteúdo dos commits. Se você alternar um repositório privado para público, o {% data variables.product.product_name %} verifica segredos em todo o repositório. - -Quando o {% data variables.product.prodname_secret_scanning %} detecta um conjunto de credenciais, notificamos o provedor de serviço que emitiu o segredo. O provedor de serviço valida a credencial e decide se deve revogar o segredo, emitir um novo segredo ou entrar em contato com você diretamente, o que dependerá dos riscos associados a você ou ao provedor de serviço. +Quando o {% data variables.product.prodname_secret_scanning %} detecta um conjunto de credenciais, notificamos o provedor de serviço que emitiu o segredo. O provedor de serviço valida a credencial e decide se deve revogar o segredo, emitir um novo segredo ou entrar em contato com você diretamente, o que dependerá dos riscos associados a você ou ao provedor de serviço. Para obter uma visão geral de como trabalhamos com parceiros emissores de token, consulte "[Varredura de segredo](/developers/overview/secret-scanning)". O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-public-repo %} ### Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios privados +{% endif %} -{% data reusables.secret-scanning.beta %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +### Sobre {% data variables.product.prodname_secret_scanning %} em {% data variables.product.product_name %} -Se você for um administrador de repositório ou um proprietário da organização, você poderá habilitar {% data variables.product.prodname_secret_scanning %} para repositórios privados que pertençam a organizações. Você pode habilitar {% data variables.product.prodname_secret_scanning %} para todos os seus repositórios ou para todos os novos repositórios da organização. {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados de contas de usuário. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" e "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +{% data variables.product.prodname_secret_scanning_caps %} está disponível em todos os repositórios de propriedade da organização como parte de {% data variables.product.prodname_GH_advanced_security %}. Não está disponível em repositórios pertencentes a usuários. +{% endif %} -Quando você faz push de commits em um repositório privado com o {% data variables.product.prodname_secret_scanning %} habilitado, o {% data variables.product.product_name %} verifica o conteúdo dos commits em busca de segredos. +Se você é um administrador de repositório ou um proprietário de uma organização, você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% if currentVersion == "free-pro-team@latest" %} repositórios privados{% endif %} pertencentes a organizações. Você pode habilitar {% data variables.product.prodname_secret_scanning %} para todos os seus repositórios ou para todos os novos repositórios na sua organização.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados pertencentes a usuários.{% endif %} Para mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" e "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". -Quando o {% data variables.product.prodname_secret_scanning %} detecta um segredo em um repositório privado, o {% data variables.product.prodname_dotcom %} envia alertas. +Quando você faz push dos commits para um repositório{% if currentVersion == "free-pro-team@latest" %} privado{% endif %} com {% data variables.product.prodname_secret_scanning %} habilitado, {% data variables.product.prodname_dotcom %} verifica o conteúdo dos segredos dos commits. + +Quando {% data variables.product.prodname_secret_scanning %} detecta um segredo em um repositório{% if currentVersion == "free-pro-team@latest" %} privado{% endif %}, {% data variables.product.prodname_dotcom %} envia alertas. - O {% data variables.product.prodname_dotcom %} envia um alerta de email para os administradores do repositório e proprietários da organização. - O {% data variables.product.prodname_dotcom %} exibe um alerta no repositório. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -Os administradores do repositório e proprietários da organização podem conceder acesso a alertas de {% data variables.product.prodname_secret_scanning %} aos usuários e à equipe. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +Os administradores do repositório e proprietários da organização podem conceder acesso aos usuários aos alertas de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". -Para monitorar os resultados de {% data variables.product.prodname_secret_scanning %} nos seus repositórios privados ou na sua organização, você pode usar a API de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações sobre pontos de extremidade da API, consulte "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)". +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Para monitorar resultados de +{% data variables.product.prodname_secret_scanning %} em todos os seus repositórios privados ou na sua organização, você pode usar a API de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações sobre pontos de extremidade da API, consulte "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)".{% endif %} -O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. +{% data variables.product.prodname_dotcom %} atualmente faz a varredura de repositórios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} para segredos emitidos pelos seguintes provedores de serviços. -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Doppler -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio +{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% note %} diff --git a/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md index 0033ab237c..f9637a4993 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md @@ -3,6 +3,7 @@ title: Sobre proteger seu repositório intro: 'O {% data variables.product.product_name %} fornece uma série de maneiras que você pode ajudar a manter seu repositório protegido.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Configurar o seu repositório com segurança @@ -13,6 +14,7 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod {% data variables.product.prodname_dotcom %} tem um conjunto crescente de recursos de segurança que ajudam você a manter seu código protegido. Você pode encontrá-los na aba **Segurança** do seu repositório. +{% if currentVersion == "free-pro-team@latest" %} - **Política de segurança** Facilita para as pessoas relatar, de modo confidencial, vulnerabilidades de segurança que encontram no seu repositório. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)". @@ -24,18 +26,32 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod - **{% data variables.product.prodname_dependabot_alerts %} e atualizações de segurança** Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. Para obter mais informações, consulte "[Sobre alertas de dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) e "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". + {% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +- **{% data variables.product.prodname_dependabot_alerts %}** + + Exibir alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e gerenciar esses alertas. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} - **atualizações de versão de {% data variables.product.prodname_dependabot %}** +Use - Use {% data variables.product.prodname_dependabot %} para levantar automaticamente os pull requests a fim de manter suas dependências atualizadas. Isso ajuda a reduzir a exposição a versões mais antigas de dependências. Usar versões mais recentes facilita a aplicação de patches, caso as vulnerabilidades de segurança sejam descobertas e também torna mais fácil para {% data variables.product.prodname_dependabot_security_updates %} levantar, com sucesso, os pull requests para atualizar as dependências vulneráveis. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". + {% data variables.product.prodname_dependabot %} para aumentar automaticamente os pull requests e manter suas dependências atualizadas. Isso ajuda a reduzir a exposição a versões mais antigas de dependências. Usar versões mais recentes facilita a aplicação de patches, caso as vulnerabilidades de segurança sejam descobertas e também torna mais fácil para {% data variables.product.prodname_dependabot_security_updates %} levantar, com sucesso, os pull requests para atualizar as dependências vulneráveis. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". + {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - **Alertas de {% data variables.product.prodname_code_scanning_capc %}** Detectar automaticamente vulnerabilidades de segurança e erros de codificação em códigos novos ou modificados. São destacados os problemas potenciais, com informações detalhadas, o que permite que você corrija o código antes que seja mesclado no seu branch-padrão. Para obter mais informações, consulte "[Sobre a varredura de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". - **Segredos detectados** +Visualizar qualquer segredo que - Visualize todos os segredos que {% data variables.product.prodname_dotcom %} encontrou no seu código. Você deve tratar os tokens ou credenciais verificados no repositório como comprometidos. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." + {% data variables.product.prodname_dotcom %} encontrou no seu código. Você deve tratar os tokens ou credenciais verificados no repositório como comprometidos. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." + {% endif %} ### Explorar dependências O gráfico de dependências de {% data variables.product.prodname_dotcom %} permite que você explore: diff --git a/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md b/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md index d24a6f5205..dbc26bb487 100644 --- a/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,13 @@ Você pode escolher o branch-padrão para um repositório. O branch-padrão é o {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +Você também pode renomear o branch padrão. Para obter mais informações, consulte "[Renomear um branch](/github/administering-a-repository/renaming-a-branch). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% data reusables.branches.set-default-branch %} diff --git a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 3e49ab0c8c..7441c35eb9 100644 --- a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -1,7 +1,7 @@ --- -title: Configuring secret scanning for your repositories -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.' -permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.' +title: Configurar a varredura de segredo para os seus repositórios +intro: 'Você pode configurar como {% data variables.product.prodname_dotcom %} faz a varredura de segredos dos seus repositórios.' +permissions: 'As pessoas com permissões de administrador para um repositório podem habilitar {% data variables.product.prodname_secret_scanning %} para o repositório.' redirect_from: - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories product: '{% data reusables.gated-features.secret-scanning %}' @@ -16,30 +16,30 @@ versions: {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only. +**Observação:** {% data variables.product.prodname_secret_scanning_caps %} está habilitado por padrão em repositórios públicos e não pode ser desativado. Você pode configurar {% data variables.product.prodname_secret_scanning %} apenas para seus repositórios privados. {% endnote %} {% endif %} -### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories +### Habilitar {% data variables.product.prodname_secret_scanning %} para repositórios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} {% if currentVersion == "free-pro-team@latest" %} -4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) -5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) -6. When you enable -{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} +4. Se "{% data variables.product.prodname_secret_scanning_caps %}" não for exibido na página, você deverá habilitar {% data variables.product.prodname_GH_advanced_security %} primeiro. À direita de "{% data variables.product.prodname_GH_advanced_security %}", clique em **Habilitar**. ![Habilitar {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-dotcom.png) +5. Clique **Habilitar {% data variables.product.prodname_GH_advanced_security %} para este repositório** para confirmar a ação. ![Confirme a habilitação de {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) +6. Quando você habilitar +{% data variables.product.prodname_GH_advanced_security %} isto poderá habilitar automaticamente {% data variables.product.prodname_secret_scanning %} para o repositório (este é controlado pela configuração da organização). Se "{% data variables.product.prodname_secret_scanning_caps %}" é exibido com um botão **habilitar**. Você ainda precisa habilitar {% data variables.product.prodname_secret_scanning %} clicando em **Habilitar**. Se você vir um botão **Desabilitar**, significa que {% data variables.product.prodname_secret_scanning %} já está habilitado. + ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} -4. To the right of " -{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) +4. À direita de " +{% data variables.product.prodname_secret_scanning_caps %}", clique em **Habilitar**. + ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-ghe.png) {% endif %} -### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories +### Excluir alertas de {% data variables.product.prodname_secret_scanning %} em repositórios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} Você pode usar um arquivo *secret_scanning.yml* para excluir diretórios do {% data variables.product.prodname_secret_scanning %}. Por exemplo, você pode excluir diretórios que contenham testes ou conteúdo gerado aleatoriamente. diff --git a/translations/pt-BR/content/github/administering-a-repository/index.md b/translations/pt-BR/content/github/administering-a-repository/index.md index 5e42bcfd20..d98fe1b8e1 100644 --- a/translations/pt-BR/content/github/administering-a-repository/index.md +++ b/translations/pt-BR/content/github/administering-a-repository/index.md @@ -33,6 +33,7 @@ versions: {% link_in_list /restoring-a-deleted-repository %} {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} + {% link_in_list /renaming-a-branch %} {% link_in_list /changing-the-default-branch %} {% link_in_list /deleting-and-restoring-branches-in-a-pull-request %} {% topic_link_in_list /configuring-pull-request-merges %} @@ -43,19 +44,8 @@ versions: {% link_in_list /managing-the-automatic-deletion-of-branches %} {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} - {% link_in_list /configuring-protected-branches %} - {% link_in_list /about-required-status-checks %} - {% link_in_list /types-of-required-status-checks %} - {% link_in_list /enabling-required-status-checks %} - {% link_in_list /about-branch-restrictions %} - {% link_in_list /enabling-branch-restrictions %} - {% link_in_list /about-required-reviews-for-pull-requests %} - {% link_in_list /enabling-required-reviews-for-pull-requests %} - {% link_in_list /about-required-commit-signing %} - {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} - {% link_in_list /enabling-force-pushes-to-a-protected-branch %} - {% link_in_list /enabling-deletion-of-a-protected-branch %} + {% link_in_list /managing-a-branch-protection-rule %} + {% link_in_list /troubleshooting-required-status-checks %} {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} @@ -66,7 +56,7 @@ versions: {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} - {% link_in_list /configuring-secret-scanning-for-private-repositories %} + {% link_in_list /configuring-secret-scanning-for-your-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md index f366971fc7..3f51b61784 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-a-branch-protection-rule.md @@ -1,6 +1,6 @@ --- -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.' +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.' product: '{% data reusables.gated-features.protected-branches %}' redirect_from: - /articles/configuring-protected-branches @@ -20,14 +20,14 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: People with admin permissions to a repository can manage branch protection rules. +permissions: As pessoas com permissões de administrador em um repositório podem gerenciar as regras de proteção do branch. --- -### About branch protection rules +### Sobre as regras de proteção do branch {% data reusables.repositories.branch-rules-example %} -You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. 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. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. 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). +É 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). 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. @@ -35,52 +35,52 @@ As regras de branch protegido que mencionam um caractere especial, como `*`, `?` 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. -For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +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)". -### Creating a branch protection rule +### Criar uma regra de proteção de branch -When you create a branch rule, the branch you specify doesn't have to exist yet in the repository. +Ao criar uma regra de branch, o branch que você especificar ainda não existe no repositório. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} {% data reusables.repositories.add-branch-protection-rules %} -1. Optionally, enable required pull request reviews. - - Under "Protect matching branches", select **Require pull request reviews 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.png) - - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd 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) - - 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**. ![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) - - 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**. 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) - - 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. Para obter mais informações, consulte " +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) + - Clique no menu suspenso **Revisões obrigatórias de aprovação** e, em seguida, selecione o número de revisões que deseja exigir no 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) + - 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". ![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. Optionally, enable required status checks. + 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) - - 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**. ![Caixa de seleção Status obrigatório rígido ou flexível](/assets/images/help/repository/protecting-branch-loose-status.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) -1. Optionally, select **Require signed commits**. ![Opção Require signed commits (Exigir commits assinados)](/assets/images/help/repository/require-signed-commits.png) +1. Opcionalmente, selecione **Exigir commits assinados**. ![Opção Require signed commits (Exigir commits assinados)](/assets/images/help/repository/require-signed-commits.png) -1. Optionally, select **Require linear history**. ![Opção de histórico linear necessária](/assets/images/help/repository/required-linear-history.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. 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. Optionally,{% if currentVersion == "free-pro-team@latest" %} 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. +1. Opcionalmente, {% if currentVersion == "free-pro-team@latest" %} 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. - - Select **Restrict who can push to matching branches**. ![Caixa de seleção Branch restriction (Restrição de branch)](/assets/images/help/repository/restrict-branch.png) + - 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. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![Permitir opção push forçado](/assets/images/help/repository/allow-force-pushes.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. Optionally, select **Allow deletions**. ![Permitir a opção de exclusão de branch](/assets/images/help/repository/allow-branch-deletions.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**. -### Editing a branch protection rule +### Editar uma regra de proteção de branch {% data reusables.repositories.navigate-to-repo %} @@ -92,15 +92,15 @@ Ignorar uma revisão de pull request". ![Caixa de seleção Restrict who can dis {% data reusables.repositories.repository-branches %} -1. To the right of the branch protection rule you want to edit, click **Edit**. ![Botão editar](/assets/images/help/repository/edit-branch-protection-rule.png) +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. Make your desired changes to the branch protection rule. +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) -### Deleting a branch protection rule +### Excluir as regras de proteção do branch {% data reusables.repositories.navigate-to-repo %} @@ -112,4 +112,4 @@ Ignorar uma revisão de pull request". ![Caixa de seleção Restrict who can dis {% data reusables.repositories.repository-branches %} -1. To the right of the branch protection rule you want to delete, click **Delete**. ![Botão excluir](/assets/images/help/repository/delete-branch-protection-rule.png) +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) diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md b/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md index 48918cac69..3d7fee809e 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-alerts-from-secret-scanning.md @@ -4,6 +4,7 @@ intro: Você pode visualizar e fechar alertas de segredos verificados para seu r product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- {% data reusables.secret-scanning.beta %} @@ -13,12 +14,24 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 3. Na barra lateral esquerda, clique em **Segredos detectados**. ![Aba "Segredos detectados" ](/assets/images/help/repository/sidebar-secrets.png) -4. Em "Escaneamento de segredos", clique no alerta que desejar visualizar. ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert.png) -5. Opcionalmente, use o menu suspenso "Resolver" e clique em um motivo para resolver um alerta. ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert.png) +4. Em "Escaneamento de segredos", clique no alerta que desejar visualizar. + {% if currentVersion == "free-pro-team@latest" %} + ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert-ghe.png) + {% endif %} +1. Opcionalmente, use o menu suspenso "Marcar como" e clique em um motivo para resolver um alerta. + {% if currentVersion == "free-pro-team@latest" %} + ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png) + {% endif %} ### Protegendo segredos comprometidos Uma vez que um segredo tenha sido committed a um repositório, você deve considerar o segredo comprometido. O {% data variables.product.prodname_dotcom %} recomenda as seguintes ações para segredos comprometidos: - Para um token de acesso pessoal do {% data variables.product.prodname_dotcom %}, exclua o token comprometido, crie outro token e atualize os serviços que usam o token antigo. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". -- Para todos os outros segredos, primeiro, verifique se o segredo commited para {% data variables.product.prodname_dotcom %} é válido. Se sim, crie um novo segredo, atualize quaisquer serviços que utilizam o segredo antigo, e depois exclua o segredo antigo. +- Para todos os outros segredos, primeiro, verifique se o segredo commited para {% data variables.product.product_name %} é válido. Se sim, crie um novo segredo, atualize quaisquer serviços que utilizam o segredo antigo, e depois exclua o segredo antigo. diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md index 97346e253b..11cf15a17f 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -5,7 +5,7 @@ intro: 'Você pode escolher se os objetos {% data variables.large_files.product_ permissions: 'Pessoas com permissões de administrador para um repositório podem gerenciar se os objetos {% data variables.large_files.product_name_short %} estão incluídos nos arquivos do repositório.' versions: free-pro-team: '*' - enterprise-server: '=>2.23' + enterprise-server: '>3.0' github-ae: '*' --- @@ -13,7 +13,7 @@ versions: O {% data variables.product.product_name %} cria arquivos de código-fonte do seu repositório na forma de arquivos ZIP e tarballs. As pessoas podem baixar esses arquivos na página principal do seu repositório ou como ativos de versão. Por padrão, os objetos {% data variables.large_files.product_name_short %} não estão incluídos nesses arquivos, apenas os arquivos de ponteiro para esses objetos. Para melhorar a usabilidade dos arquivos no seu repositório, você pode optar por incluir os objetos do {% data variables.large_files.product_name_short %}. -{% if currentVersion != "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" %} Se optar por incluir objetos de {% data variables.large_files.product_name_short %} nos arquivos do seu repositório, cada download desses arquivos será contabilizado no uso da banda larga para a sua conta. Cada conta recebe {% data variables.large_files.initial_bandwidth_quota %} por mês de largura de banda gratuitamente, e você pode pagar pelo uso adicional. Para obter mais informações, consulte "[Sobre armazenamento e uso de largura de banda](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" e "[Gerenciamento de cobrança para {% data variables.large_files.product_name_long %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)". {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md index 02118acafa..83e1edc9c0 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md @@ -15,7 +15,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion ver_gt "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %} ### Sobre o gerenciamento da versão diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 7e05aa25da..066ce1fb66 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -9,18 +9,36 @@ redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- -### Habilitar ou desabilitar recursos de segurança e análise +{% if currentVersion == "free-pro-team@latest" %} +### Habilitar ou desabilitar recursos de segurança e análise para repositórios públicos -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +É possível gerenciar um subconjunto de recursos de segurança e análise para repositórios públicos. Outros recursos são habilitados permanentemente, incluindo gráfico de dependências e varredura de segredo. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" em um repositório público](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png) +{% endif %} + +### Habilitar ou desabilitar os recursos de segurança e análise{% if currentVersion == "free-pro-team@latest" %} para repositórios privados{% endif %} + +Você pode gerenciar os recursos de segurança e análise do repositório {% if currentVersion == "free-pro-team@latest" %}privado ou interno {% endif %}. Se sua organização ou empresa tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, haverá opções adicionais disponíveis. {% data reusables.advanced-security.more-info-ghas %} {% data reusables.security.security-and-analysis-features-enable-read-only %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. +{% if currentVersion == "free-pro-team@latest" %}Se "{% data variables.product.prodname_secret_scanning_caps %}" não for exibido, talvez seja necessário habilitar {% data variables.product.prodname_GH_advanced_security %} primeiro. + ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) + {% endif %} ### Conceder acesso aos alertas de segurança @@ -35,7 +53,13 @@ Os proprietários e administradores da organização só podem conceder acesso p {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências. ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências. + {% if currentVersion == "free-pro-team@latest" %} + ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search-ghe.png) + {% endif %} 5. Clique em **Save changes** (Salvar alterações). ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### Remover o acesso aos alertas de segurança @@ -43,7 +67,14 @@ Os proprietários e administradores da organização só podem conceder acesso p {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Acesso aos alertas", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em {% octicon "x" aria-label="X symbol" %}. ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. Em "Acesso aos alertas", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em +{% octicon "x" aria-label="X symbol" %}. + {% if currentVersion == "free-pro-team@latest" %} + ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x-ghe.png) + {% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md b/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md index 0748625b6b..11e7f5c671 100644 --- a/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md @@ -1,21 +1,34 @@ --- -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. +title: Renomear um branch +intro: É possível alterar o nome de um branch em um repositório. +permissions: As pessoas com permissões de gravação em um repositório podem renomear um branch no repositório. As pessoas com permissões de administrador podem renomear o branch padrão. versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -### About renaming branches +### Sobre a renomeação de branches -You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)." +Você pode renomear um branch em um repositório em {% data variables.product.product_location %}. Para obter mais informações sobre os branches, consulte "[Sobre os branches](/github/collaborating-with-issues-and-pull-requests/about-branches)". -If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases. +Se você renomear um branch, {% data variables.product.prodname_dotcom %} irá redirecionar automaticamente links em {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} que contêm o nome do branch antigo para o link equivalente no branch renomeado. {% data variables.product.prodname_dotcom %} também atualizará as políticas de proteção do branch, bem como o branch de base para pull requests abertos e versões de rascunho. -### Renaming a branch +### Renomear um branch {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} -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) +1. Na lista de branches, à direita do branch que você deseja renomear, clique em {% octicon "pencil" aria-label="The edit icon" %}. ![Ícone do lápis à direita do branch que você deseja renomear](/assets/images/help/branch/branch-rename-edit.png) +1. Digite um novo nome para o branch. ![Campo de texto para digitar o novo nome do branch](/assets/images/help/branch/branch-rename-type.png) +1. Revise as informações sobre ambientes locais e clique em **Renomear o branch**. ![Informações de ambiente local e botão para "Renomear o branch"](/assets/images/help/branch/branch-rename-rename.png) + +### Atualizar um clone local após alterações de nome do branch + +Após renomear um branch em um repositório em {% data variables.product.product_name %}, qualquer colaborador com um clone local do repositório deverá atualizar o clone. + +A partir do clone local do repositório em um computador, execute os seguintes comandos para atualizar o nome do branch padrão. + +```shell +$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md b/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md index 4346db4ef8..7fd8db9d0c 100644 --- a/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/pt-BR/content/github/administering-a-repository/setting-repository-visibility.md @@ -1,6 +1,6 @@ --- -title: Definir a visibilidade de um repositório -intro: Você pode escolher quem pode visualizar seu repositório. +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/ @@ -12,91 +12,104 @@ versions: github-ae: '*' --- -### Sobre alterações de visibilidade do repositório +### About repository visibility changes -Os proprietários da organização podem restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização. Para obter mais informações, consulte "[Restringir as alterações de visibilidade do repositório na sua organização](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." -Recomendamos revisar as seguintes advertências antes de alterar a visibilidade de um repositório. +We recommend reviewing the following caveats before you change the visibility of a repository. -#### Tornar um repositório privado +#### Making a repository private {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -* O {% data variables.product.product_name %} destacará bifurcações públicas do repositório público e as colocará em uma nova rede. As bifurcações públicas não se convertem em privadas.{% endif %} -* Se você alterar a visibilidade de um repositório interno para privado, {% data variables.product.prodname_dotcom %} removerá bifurcações que pertencem a qualquer usuário sem acesso ao repositório privado recente. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}A visibilidade de qualquer bifurcação também será alterada para privada.{% elsif currentVersion == "github-ae@latest" %}Se o repositório interno tiver alguma bifurcação, significa que a visibilidade das bifurcações já é privada.{% endif %} Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou a visibilidade é alterada?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} -* Se você estiver usando {% data variables.product.prodname_free_user %} para contas de usuário ou organizações, alguns recursos não estarão disponíveis no repositório depois de alterar a visibilidade para privada. {% data reusables.gated-features.more-info %}{% endif %} -* Qualquer site de {% data variables.product.prodname_pages %} publicado terá a publicação cancelada automaticamente.{% if currentVersion == "free-pro-team@latest" %} Se você adicionou um domínio personalizado ao site de {% data variables.product.prodname_pages %} você deve remover ou atualizar seus registros de DNS antes de tornar o repositório privado para evitar o risco de tomada de um domínio. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para o seu site de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. Para obter mais informações, consulte "[Sobre sobre arquivamento de conteúdo e dados em {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)".{% endif %}{% if enterpriseServerVersions contains currentVersion %} -* O acesso de leitura anônimo do Git não está mais disponível. 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)".{% 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. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}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)"{% if currentVersion == "free-pro-team@latest" %} +* 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. {% data reusables.gated-features.more-info %}{% endif %} +* Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} 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 "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} +* {% 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% 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 has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* 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 %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -#### Tornar um repositório interno +#### Making a repository internal {% note %} -**Observação:** {% data reusables.gated-features.internal-repos %} +**Note:** {% data reusables.gated-features.internal-repos %} {% endnote %} -* Todas as bifurcações do repositório permanecerão na rede do repositório e a {% data variables.product.product_name %} manterá a relação entre o repositório raiz e a bifurcação. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda de visibilidade?](/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 %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -#### Tornar um repositório público +#### Making a repository public -* O {% data variables.product.product_name %} irá destacar bifurcações privadas e transformá-las em um repositório privado independente. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda a visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* Se você estiver convertendo seu repositório privado em um repositório público, como parte de um movimento para a criação de um projeto de código aberto, consulte os [Guias de Código Aberto](http://opensource.guide) para obter dicas e diretrizes úteis. Você também pode fazer um curso grátis sobre gerenciamento de projeto de código aberto com [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. Para obter mais informações, consulte "[Exibir o perfil da comunidade](/articles/viewing-your-community-profile)."{% endif %} +* {% 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)"{% if currentVersion == "free-pro-team@latest" %} +* 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. + +For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -### Alterar a visibilidade de um repositório +### Changing a repository's visibility {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em "Danger Zone" (Zona de Perigo), à direita de "Alterar a visibilidade do repositório", clique **Alterar visibilidade**. ![Botão de alteração de visibilidade](/assets/images/help/repository/repo-change-vis.png) -4. Selecione uma visibilidade. ![Caixa de diálogo de opções para visibilidade do repositório](/assets/images/help/repository/repo-change-select.png) -5. Para verificar se você está alterando a visibilidade do repositório correto, digite o nome do repositório que deseja alterar a visibilidade. -6. Clique em **Eu entendi, altere a visibilidade do repositório**. ![Confirmar alteração do botão de visibilidade do repositório](/assets/images/help/repository/repo-change-confirm.png) +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. + ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png) +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**. + ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png) {% endif %} {% if currentVersion ver_lt "enterprise-server@2.22" %} -### Tornar um repositório privado +### Making a repository private {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em "Zona de perigo", perto de "Tornar este repositório privado", clique em **Tornar privado**. ![Botão Make private (Tornar privado)](/assets/images/help/repository/repo-makeprivate.png) -4. Leia os avisos sobre tornar um repositório privado. ![Pop-up de avisos](/assets/images/help/repository/repo-privateconfirm.png) -5. Insira o nome do repositório que deseja tornar privado, como `accountname/reponame`. -6. Clique em **Eu compreendo, tornar este repositório privado**. +3. Under "Danger Zone", next to "Make this repository private", click **Make private**. + ![Make private button](/assets/images/help/repository/repo-makeprivate.png) +4. Read the warnings about making a repository private. + ![Warnings popup](/assets/images/help/repository/repo-privateconfirm.png) +5. Type the name of the repository that you want to make private, for example `accountname/reponame`. +6. Click **I understand, make this repository private**. -### Tornar um repositório público +### Making a repository public {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em "Zona de perigo, perto de "Tornar este repositório público", clique em **Tornar público**. ![Botão Make public (Tornar público)](/assets/images/help/repository/repo-makepublic.png) -4. Leia os avisos sobre tornar um repositório público. ![Pop-up com informações sobre converter repositório privado em público](/assets/images/help/repository/repo-publicconfirm.png) -5. Insira o nome do repositório que deseja tornar público, como `accountname/reponame`. -6. Clique em **Eu compreendo, tornar este repositório público**. +3. Under "Danger Zone", next to "Make this repository public", click **Make public**. + ![Make public button](/assets/images/help/repository/repo-makepublic.png) +4. Read the warnings about making a repository public. + ![Pop-up with information about making a private repository public](/assets/images/help/repository/repo-publicconfirm.png) +5. Type the name of the repository that you want to make public, for example `accountname/reponame`. +6. Click **I understand, make this repository public**. {% if currentVersion ver_gt "enterprise-server@2.19" %} -### Tornar um repositório interno +### Making a repository internal {% data reusables.organizations.internal-repos-enterprise %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em "Zona de perigo", perto de "Tornar este repositório interno", clique em **Tornar interno**. ![Botão Make internal (Tornar interno)](/assets/images/help/repository/repo-makeinternal.png) -4. Leia os avisos sobre tornar um repositório interno. ![Pop-up de avisos](/assets/images/help/repository/repo-internalconfirm.png) -5. Insira o nome do repositório que deseja tornar interno, como `accountname/reponame`. -6. Clique em **Eu compreendo, tornar este repositório interno**. +3. Under "Danger Zone", next to "Make this repository internal", click **Make internal**. + ![Make internal button](/assets/images/help/repository/repo-makeinternal.png) +4. Read the warnings about making a repository internal. + ![Warnings popup](/assets/images/help/repository/repo-internalconfirm.png) +5. Type the name of the repository that you want to make internal, for example `accountname/reponame`. +6. Click **I understand, make this repository internal**. {% endif %} {% endif %} -### Leia mais -- "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" +### Further reading +- "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md index b18df7ad64..af6e06d5d3 100644 --- a/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md +++ b/translations/pt-BR/content/github/administering-a-repository/troubleshooting-required-status-checks.md @@ -1,6 +1,6 @@ --- title: Solução de problemas de verificações de status necessárias -intro: 'You can check for common errors and resolve issues with required status checks.' +intro: 'Você pode verificar erros comuns e resolver problemas com as verificações de status necessárias.' product: '{% data reusables.gated-features.protected-branches %}' versions: free-pro-team: '*' @@ -8,9 +8,9 @@ versions: github-ae: '*' --- -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. Para obter mais informações, consulte "[Verificações](/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)". -After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. 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)". +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)". {% note %} @@ -26,13 +26,13 @@ remote: error: Required status check "ci-build" is failing ``` {% note %} -**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. Isso pode ser feito sem verificações de status em execução no próprio commit de merge. +**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. {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. If the test merge commit has a status, the test merge commit must pass. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." +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)". ![Branch com commits de mescla conflitantes](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) {% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 051502db07..0a4f75ae46 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Sobre a autenticação com SAML SSO -intro: 'Você pode acessar {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}uma organização que usa o logon único SAML (SSO){% endif %}, efetuando a autenticação {% if currentVersion == "github-ae@latest" %}com o logon único SAML (SSO) {% endif %}através de um provedor de identidade (IdP).{% if currentVersion == "free-pro-team@latest" %}Para efetuar a autenticação com a API ou Git na linha de comando quando uma organização aplica o SAML SSO, você deve autorizar seu token de acesso pessoal ou chave SSH.{% endif %}' +intro: 'Você pode acessar {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}uma organização que usa o logon único SAML (SSO){% endif %} efetuando a autenticação {% if currentVersion == "github-ae@latest" %}com o logon único SAML (SSO) {% endif %}através de um provedor de identidade (IdP).{% if currentVersion == "free-pro-team@latest" %} Após efetuar a autenticação com o IdP em {% data variables.product.product_name %}, você deve autorizar qualquer token de acesso pessoal, chave SSH, ou {% data variables.product.prodname_oauth_app %} que deseja acessar os recursos da organização.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on @@ -9,6 +9,8 @@ versions: github-ae: '*' --- +### Sobre autenticação com SSO do SAML + {% if currentVersion == "github-ae@latest" %} O SAML SSO permite que um proprietário corporativo realize o controle central e proteja o acesso para {% data variables.product.product_name %} a partir de um IdP do SAML. Ao acessar {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} irá redirecioná-lo para seu IdP para efetuar a autenticação. Depois de concluir a autenticação com sucesso com uma conta no IdP, este irá redirecionar você de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IpD e, em seguida, concede acesso. @@ -31,13 +33,17 @@ Se você efetuou a autenticação recentemente com o IdP SAML da sua organizaç {% data reusables.saml.you-must-periodically-authenticate %} -Para usar a API ou o Git na linha de comando de modo a acessar conteúdo protegido em uma organização que usa SAML SSO, você precisará usar um token de acesso pessoal autorizado por HTTPS ou uma chave SSH autorizada. Os tokens de acesso do {% data variables.product.prodname_oauth_app %} são autorizados por padrão. +Para usar a API ou o Git na linha de comando de modo a acessar conteúdo protegido em uma organização que usa SAML SSO, você precisará usar um token de acesso pessoal autorizado por HTTPS ou uma chave SSH autorizada. Na falta de um token de acesso pessoal ou uma chave SSH, você poderá criar um token de acesso pessoal para a linha de comando ou gerar uma nova chave SSH. Para obter mais informações consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)ou "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent-](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". -Para usar uma chave SSH ou um token de acesso pessoal existente ou novo com uma organização que impõe o SAML SSO, você precisará autorizar o token ou a chave SSH para uso com uma organização de logon único de SAML. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on). +Para usar um token novo ou existente de acesso pessoal ou chave SSH com uma organização que usa ou impõe o SSO do SAML, você precisará autorizar o token ou autorizar a chave SSH para uso com uma organização de SSO do SAML. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on). -Você deve ter uma sessão de SAML ativa toda vez que autorizar um {% data variables.product.prodname_oauth_app %}. +### Sobre {% data variables.product.prodname_oauth_apps %} e SSO do SAML + +Você deve ter uma sessão do SAML ativa toda vez que autorizar um {% data variables.product.prodname_oauth_app %} para acessar uma organização que usa ou aplica o SSO do SAML. + +Após o proprietário de uma empresa ou organização habilitar ou aplicar o SSO do SAML para uma organização, você deverá autorizar novamente qualquer {% data variables.product.prodname_oauth_app %} que você autorizou anteriormente a acessar a organização. Para visualizar {% data variables.product.prodname_oauth_apps %} que você autorizou ou ou autorizar novamente um {% data variables.product.prodname_oauth_app %}, acesse a sua página de [{% data variables.product.prodname_oauth_apps %}](https://github.com/settings/applications). {% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md index fd4100bc43..514a665fca 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -19,11 +19,13 @@ Você pode assinar commits e tags localmente para que outras pessoas possam veri Se um commit ou uma tag tiver uma assinatura que não possa ser verificada, o {% data variables.product.product_name %} marcará o commit ou a tag como não verificado(a). -Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre a assinatura de commit obrigatória](/articles/about-required-commit-signing)". +Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits)". Você pode conferir o status de verificação de seus commits ou tags assinados no {% data variables.product.product_name %} e ver por que as assinaturas de commit podem não ter sido verificadas. Para obter mais informações, consulte "[Conferir o status de verificação da assinatura de commit ou tag](/articles/checking-your-commit-and-tag-signature-verification-status)". -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} usará automaticamente o GPG para assinar commits que você criar usando a interface web do {% data variables.product.product_name %}, exceto quando você faz combinação por squash e merge de um pull request do qual você não é o autor. Commits assinados por {% data variables.product.product_name %} terão um status de verificado em {% data variables.product.product_name %}. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %} usará automaticamente o GPG para assinar os commits que você fizer usando a interface web do {% data variables.product.product_name %} exceto quando você faz combinação por squash e mescla um pull request do qual você não é o autor. Opcionalmente, você pode escolher que {% data variables.product.product_name %} assine os commits que você fizer em {% data variables.product.prodname_codespaces %}. Commits assinados por {% data variables.product.product_name %} terão um status de verificado em {% data variables.product.product_name %}. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg. Para obter mais informações sobre como habilitar a verificação de GPG para os seus códigos, consulte "[Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". +{% endif %} ### Verificação da assinatura de commit GPG diff --git a/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md b/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md index 183fecb7f3..4970bdd54d 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md +++ b/translations/pt-BR/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md @@ -1,6 +1,6 @@ --- -title: Keeping your account and data secure -intro: 'To protect your personal information, you should keep both your {% data variables.product.product_name %} account and any associated data secure.' +title: Proteger sua conta e dados +intro: 'Para proteger suas informações pessoais, você deve manter sua conta {% data variables.product.product_name %} e quaisquer dados associados a ela seguros.' mapTopic: true redirect_from: - /articles/keeping-your-account-and-data-secure diff --git a/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 6fb0957ee4..251cfceb71 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ Este artigo explica como fazer commits com dados confidenciais que não podem se #### Usar o BFG -O [BFG Repo-Cleaner](http://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. Por exemplo: para remover o arquivo com dados confidenciais sem alterar o commit mais recente, execute: +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. Por exemplo: para remover o arquivo com dados confidenciais sem alterar o commit mais recente, execute: ```shell $ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA @@ -46,7 +46,7 @@ Depois que os dados confidenciais são removidos, você deve fazer push forçado $ git push --force ``` -Consulte as instruções completas de download e uso na documentação do [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/). +Consulte as instruções completas de download e uso na documentação do [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/). #### Usar o filter-branch diff --git a/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md index 73c964f158..3dd12defa2 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md +++ b/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md @@ -39,6 +39,7 @@ Os eventos listados no seu registro de segurança são acionados por suas açõe | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} | [`account_recovery_token`](#account_recovery_token-category-actions) | Contém todas as atividade relacionadas a [adicionar um token de recuperação](/articles/configuring-two-factor-authentication-recovery-methods). | | [`cobrança`](#billing-category-actions) | Contém todas as atividades relacionadas às suas informações de cobrança. | +| [`espaços de código`](#codespaces-category-actions) | Contém todas as atividades relacionadas a {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)". | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contém todas as atividades relacionadas à assinatura do Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. | | [`marketplace_listing`](#marketplace_listing-category-actions) | Contém todas as atividades relacionadas aos aplicativos listados no {% data variables.product.prodname_marketplace %}.{% endif %} | [`oauth_access`](#oauth_access-category-actions) | Contém todas as atividades relacionadas a [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) com as quais você se conectou.{% if currentVersion == "free-pro-team@latest" %} @@ -82,6 +83,12 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `change_billing_type` | Acionada quando você [altera o modo de pagamento](/articles/adding-or-editing-a-payment-method) do {% data variables.product.prodname_dotcom %}. | | `change_email` | Acionada quando você [altera o endereço de e-mail](/articles/changing-your-primary-email-address). | +#### ações da categoria `codespaces` + +| Ação | Descrição | +| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `trusted_repositories_access_update` | Acionada quando você altera o [acesso e as configurações de segurança da sua conta de usuário para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | + #### ações de categoria de `marketplace_agreement_signature` | Ação | Descrição | @@ -176,7 +183,7 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `repo_funding_link_button_toggle` | Acionada quando você habilita ou desabilita um botão de patrocinador no repositório (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_create` | Acionada quando você patrocina uma conta (veja "[Patrocinar um contribuidor de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | | `sponsor_sponsorship_preference_change` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/articles/managing-your-sponsorship)") | | `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | | `sponsored_developer_approve` | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (ver "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | @@ -227,20 +234,20 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev #### ações de categoria `user` -| Ação | Descrição | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email` | Acionada quando você {% if currentVersion != "github-ae@latest" %}[adiciona um novo endereço de email](/articles/changing-your-primary-email-address){% else %}adiciona um novo endereço de email{% endif %}. | -| `create` | Acionada quando você cria uma nova conta de usuário.{% if currentVersion != "github-ae@latest" %} -| `change_password` | Acionada quando você altera a senha. | -| `forgot_password` | Acionada quando você solicita [a redefinição da senha](/articles/how-can-i-reset-my-password).{% endif %} -| `hide_private_contributions_count` | Acionada quando você [oculta as contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | -| `login` | Acionada quando você faz login no {% data variables.product.product_location %}. | -| `failed_login` | Acionada quando você não consegue fazer login. | -| `remove_email` | Acionada quando você remove um endereço de e-mail. | -| `rename` | Acionada quando você renomeia a conta.{% if currentVersion == "free-pro-team@latest" %} -| `report_content` | Acionada quando você [denuncia um problema ou uma pull request, ou um comentário em um problema, uma pull request, ou commit](/articles/reporting-abuse-or-spam).{% endif %} -| `show_private_contributions_count` | Acionada quando você [divulga contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} -| `two_factor_requested` | Acionada quando {% data variables.product.product_name %} pede a você por [seu código de autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication).{% endif %} +| Ação | Descrição | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email` | Acionada quando você | +| {% if currentVersion != "github-ae@latest" %}[adiciona um novo endereço de e-mail](/articles/changing-your-primary-email-address){% else %}adiciona um novo endereço de e-mail{% endif %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Acionada quando você \[permite que os codespaces que você cria para um repositório acessem outros repositórios pertencentes à sua conta de usuário\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Acionada quando você \[não permite que os codespaces que você cria para um repositório acessem outros repositórios pertencentes à sua conta de usuário\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %} +| `create` | Acionada quando você cria uma nova conta de usuário.{% if currentVersion != "github-ae@latest" %} +| `change_password` | Acionada quando você altera a senha. | +| `forgot_password` | Acionada quando você solicita [a redefinição da senha](/articles/how-can-i-reset-my-password).{% endif %} +| `hide_private_contributions_count` | Acionada quando você [oculta as contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). | +| `login` | Acionada quando você efetua o login em {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`mandatory_message_viewed` | Acionada quando você visualiza uma mensagem obrigatória (consulte "[Personalizar mensagens de usuário](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obter detalhes) e ├{% endif %}➲ ├ `falhou_login` | Acionada quando você não efetuou o login com sucesso. | `remove_email` | Acionado quando você remove um endereço de e-mail. | `rename` | Acionado quando você renomeia a sua conta.{% if currentVersion == "free-pro-team@latest" %} | `report_content` | Acionado quando você [relata um problema ou pull request ou um comentário em um problema, pull request ou commit](/articles/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Acionado quando você [publica contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | Acionado quando {% data variables.product.product_name %} solicita o seu [código de autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication).{% endif %} #### ações de categoria `user_status` @@ -249,4 +256,3 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `update` | Acionada quando você configura ou altera o status no perfil. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)". | | `destroy` | Acionada quando você remove o status no perfil. | - diff --git a/translations/pt-BR/content/github/authenticating-to-github/testing-your-ssh-connection.md b/translations/pt-BR/content/github/authenticating-to-github/testing-your-ssh-connection.md index 2472ac868d..c5255dee6f 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/testing-your-ssh-connection.md +++ b/translations/pt-BR/content/github/authenticating-to-github/testing-your-ssh-connection.md @@ -31,7 +31,7 @@ Quando você testar a conexão, precisará autenticar essa ação usando sua sen > Tem certeza de que deseja continuar com a conexão (sim/não)? ``` -3. Verify that the fingerprint in the message you see matches {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %}'s RSA public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`: +3. Verifique se a impressão digital na mensagem em que você vê correspondências com {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %} é da chave pública de RSA de](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} é da chave pública da sua empresa{% endif %}. Se isso acontecer, digite `sim`: ```shell > Olá, username! You've successfully authenticated, but GitHub does not > provide shell access. diff --git a/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index 1bccf1ef61..b4b36e337d 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -18,12 +18,11 @@ Com as chaves SSH, se alguém conseguir acessar seu computador, terá acesso a t É possível alterar a frase secreta de uma chave privada sem gerar novamente o par de chaves. Basta digitar o seguinte comando: ```shell -$ ssh-keygen -p -# Start the SSH key creation process -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' -> Enter new passphrase (empty for no passphrase): [Digite a nova frase secreta] -> Enter same passphrase again: [Digite mais uma vez para garantir] +$ ssh-keygen -p -f ~/.ssh/id_ed25519 +> Enter old passphrase: [Type old passphrase] +> Key has comment 'your_email@example.com' +> Enter new passphrase (empty for no passphrase): [Type new passphrase] +> Enter same passphrase again: [Repeat the new passphrase] > Your identification has been saved with the new passphrase. ``` diff --git a/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index 1db8371921..07f43ae223 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ Ao bloquear um usuário, você pode optar por bloqueá-lo indefinidamente ou por {% tip %} -**Dica:** se for bloquear um usuário por conta de uma conversa acalorada, considere [bloquear a conversa](/articles/locking-conversations) para que apenas colaboradores possam comentar. +**Dica:** se for bloquear um usuário por conta de uma conversa acalorada, considere bloquear a conversa para que apenas colaboradores possam comentar. Para obter mais informações, consulte "[Bloquear conversas](/github/building-a-strong-community/locking-conversations)". {% endtip %} No momento que você bloqueia um usuário da organização: - O usuário para de inspecionar os repositórios da sua organização - As estrelas e atribuições de problema do usuário são removidas dos repositórios -- As bifurcações dos repositórios da sua organização são excluídas - Os votos do usuário nas discussões ou comentários nos repositórios da sua organização são excluídos - O usuário é removido como um colaborador dos repositórios da organização - As contribuições do usuário para os repositórios da sua organização não são mais contabilizadas como contribuições para eles diff --git a/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 81c18a34f2..cac2fc5e3a 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/pt-BR/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### Sobre o bloqueio de usuários -Você pode bloquear um usuário nas configurações da sua conta ou no perfil do usuário. {% data variables.product.prodname_dotcom %} não notificará o usuário quando você bloqueá-lo. Se quiser evitar contribuir com o mesmo projeto da pessoa que foi bloqueada, você pode [optar por exibir um aviso](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings) em todos os repositórios com contribuições anteriores de um usuário bloqueado. Você ainda pode ver a atividade dos usuários bloqueados em espaços compartilhados e os usuários bloqueados podem excluir seu conteúdo existente. +Você pode bloquear um usuário nas configurações da sua conta ou no perfil do usuário. {% data variables.product.prodname_dotcom %} não notificará o usuário quando você bloqueá-lo. Se você quiser evitar contribuir para o mesmo projeto que alguém bloqueou, você pode optar por exibir um aviso em qualquer repositório com contribuições anteriores de um usuário bloqueado. Para obter mais informações, consulte "[Bloquear um usuário nas configurações da sua conta](#blocking-a-user-in-your-account-settings)". Você ainda pode ver a atividade dos usuários bloqueados em espaços compartilhados e os usuários bloqueados podem excluir seu conteúdo existente. {% tip %} -**Dica:** se for bloquear um usuário por conta de uma conversa acalorada, considere [bloquear a conversa](/articles/locking-conversations) para que apenas colaboradores possam comentar. +**Dica:** se for bloquear um usuário por conta de uma conversa acalorada, considere bloquear a conversa para que apenas colaboradores possam comentar. Para obter mais informações, consulte "[Bloquear conversas](/github/building-a-strong-community/locking-conversations)". {% endtip %} @@ -22,8 +22,6 @@ Quando você bloqueia um usuário: - O usuário para de inspecionar e deixa de fixar seus repositórios - O usuário não pode participar de nenhuma organização da qual você é proprietário - As estrelas e atribuições de problema do usuário são removidas dos repositórios -- As bifurcações dos seus repositórios são excluídas -- Você exclui qualquer bifurcação dos repositórios do usuário - Os votos do usuário em discussões ou comentários em seus repositórios são excluídos - O usuário é removido como um colaborador dos seus repositórios - As contribuições do usuário nos seus repositórios não são mais contabilizadas como contribuições para eles diff --git a/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index fc4f36b06c..5eb912319b 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/pt-BR/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ Você pode adicionar o YAML frontmatter a cada modelo de problema para preencher Aqui está um exemplo de YAML front matter. -``` +```yaml --- name: Rastreando problema about: Use este modelo para rastrear novos recursos. diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index e4df9034b3..8c874d0b44 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -74,7 +74,7 @@ Quando um branch estiver protegido: - 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](/articles/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](/articles/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 a assinatura de commit obrigatória](/articles/about-required-commit-signing). {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +- 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). {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - 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)".{% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md index ee98e3cd53..077715c48a 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md @@ -44,9 +44,7 @@ Você pode exibir todas as revisões que uma pull request recebeu na linha do te ### Revisões obrigatórias -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -Para obter mais informações, consulte "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)". +{% data reusables.pull_requests.required-reviews-for-prs-summary %} Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". {% tip %} @@ -57,6 +55,5 @@ Para obter mais informações, consulte "[Sobre revisões obrigatórias para pul ### Leia mais - "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Habilitar revisões obrigatórias para pull requests](/articles/enabling-required-reviews-for-pull-requests)" - "[Exibir uma revisão de pull request](/articles/viewing-a-pull-request-review)" - "[Configurar diretrizes para os contribuidores do repositório](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md index 38aaa27b45..d8d7c09ca9 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews.md @@ -9,9 +9,9 @@ versions: github-ae: '*' --- -Para obter mais informações sobre revisões obrigatórias, consulte "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)". +Para obter mais informações sobre as análises necessárias, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". -Você pode comentar em uma pull request, aprovar as alterações ou solicitar melhorias antes da aprovação. Para obter mais informações, consulte "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" e "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". +Você pode comentar em uma pull request, aprovar as alterações ou solicitar melhorias antes da aprovação. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". {% data reusables.search.requested_reviews_search %} @@ -34,6 +34,5 @@ Você pode comentar em uma pull request, aprovar as alterações ou solicitar me ### Leia mais -- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" - "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" - "[Comentar em uma pull request](/articles/commenting-on-a-pull-request)" diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 32c04eecaf..c9c7b9a713 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -13,7 +13,7 @@ Só é possível fazer commits em branches da pull request que: - esteja aberta em um repositório em que você tem acesso push e que foi criada de uma bifurcação desse repositório - estão em uma bifurcação de propriedade do usuário - tiver permissão concedida pelo criador da pull request -- não tenha [restrições de branch](/articles/about-branch-restrictions) que impedirá você de fazer commit +- não tenha [restrições de branch](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) que impedirá você de fazer commit Somente o usuário que criou a pull request pode dar a você permissão para fazer push de commits na bifurcação de propriedade do usuário. Para obter mais informações, consulte "[Permitir alterações no branch de uma pull request criada de uma bifurcação](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)". diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md index 5da7d3f782..adc83e2ff5 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md @@ -3,7 +3,7 @@ title: Criando uma pull request a partir de uma bifurcação intro: É possível criar uma pull request para propor alterações que você fez em uma bifurcação de um repositório upstream. redirect_from: - /articles/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: Qualquer pessoa com acesso de gravação a um repositório pode criar um pull request a partir de uma bifurcação pertencente ao usuário. versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md index a81bb4db56..caf8e96fc6 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review.md @@ -1,6 +1,6 @@ --- title: Ignorar uma revisão de pull request -intro: 'Se o seu repositório [exige revisões](/articles/about-required-reviews-for-pull-requests), você pode ignorar revisões de pull request que já não sejam mais válidas ou que não tenham sido aprovadas pelo revisor.' +intro: 'Se seu repositório exigir revisões, você poderá descartar revisões de pull request que não são mais válidas ou não podem ser aprovadas pelo revisor.' redirect_from: - /articles/dismissing-a-pull-request-review versions: @@ -24,4 +24,4 @@ Isso altera o status da revisão para um comentário de revisão. Quando você i - "[Sobre revisões de solicitação pull](/articles/about-pull-request-reviews)" - "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" +- "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" \ No newline at end of file diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md index 332e399b36..f184641070 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/github-flow.md @@ -14,7 +14,7 @@ versions: ### Seguir o fluxo GitHub 1. [Crie um branch](/articles/creating-and-deleting-branches-within-your-repository) do repositório. -2. [Crie](/articles/creating-new-files), [edite](/articles/editing-files), [renomeie](/articles/renaming-a-file), [mova](/articles/moving-a-file-to-a-new-location) ou [exclua](/articles/deleting-files) arquivos. +2. [Crie](/articles/creating-new-files), [edite](/articles/editing-files), [renomeie](/articles/renaming-a-file), [mova](/articles/moving-a-file-to-a-new-location) ou [exclua](/github/managing-files-in-a-repository/deleting-files-in-a-repository) arquivos. 3. [Envie uma pull request](/articles/creating-a-pull-request) de seu branch com as modificações propostas para iniciar uma discussão. 4. Faça as modificações necessárias em seu branch. Sua pull request atualizará automaticamente. 5. [Faça o merge da pull request](/articles/merging-a-pull-request) assim que o branch estiver pronto. diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index f6ec4ef7e3..c5dd9cb1fc 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -12,7 +12,7 @@ versions: ### Sobre merges de pull request -Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. {% data reusables.pull_requests.about-protected-branches %} No entanto, pode haver restrições sobre quando você pode fazer merge de um pull request em um branch específico. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". +Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. Por padrão, qualquer pull request pode sofrer merge a qualquer momento, a menos que o branch head esteja em conflito com o branch base. No entanto, pode haver restrições sobre quando você puder fazer merge de um pull request em um branch específico. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". {% data reusables.pull_requests.you-can-auto-merge %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index b1cb53a0ec..cb7f6ae169 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ Por exemplo, se você e outra pessoa editarem as mesmas linhas do arquivo _style 4. Abra o editor de texto de sua preferência, como o [Atom](https://atom.io/), e navegue até o arquivo que tem conflitos de merge. 5. Para ver o começo do conflito de merge no arquivo, pesquise o marcador de conflito `<<<<<<<` no arquivo. Quando abrir o arquivo no editor de texto, você verá as alterações do branch HEAD ou base após a linha `<<<<<<< HEAD`. Em seguida, você verá `=======`, que divide suas alterações das alterações no outro branch, seguido por `>>>>>>> BRANCH-NAME`. Neste exemplo, uma pessoa escreveu "open an issue" (abrir um problema) no branch base ou HEAD e outra pessoa escreveu "ask your question in IRC" (faça sua pergunta no IRC) no branch de comparação ou `branch-a`. - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} Neste exemplo, as duas alterações são incorporadas ao merge final: ```shell diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index ddbc77cdfa..5e66fedd1d 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -36,7 +36,7 @@ A revisão de dependências é compatível com as mesmas linguagens e os mesmos ![Menu de filtro de arquivos](/assets/images/help/pull_requests/file-filter-menu-json.png) -1. À direita do cabeçalho para um manifesto ou arquivo de bloqueio, mostre a revisão de dependências clicando no botão de diff avançado. +1. À direita do cabeçalho de um manifesto ou arquivo de bloqueio, exiba a revisão de dependências clicando no botão de diff avançado**{% octicon "file" aria-label="The rich diff icon" %}**. ![Botão de diff avançado](/assets/images/help/pull_requests/dependency-review-rich-diff.png) @@ -69,6 +69,4 @@ A revisão de dependências é compatível com as mesmas linguagens e os mesmos * A gravidade da vulnerabilidade. * A versão da dependência na qual a vulnerabilidade foi corrigida. Se você estiver revisando um pull request para alguém, você pode pedir ao contribuidor para atualizar a dependência para a versão corrigida ou para uma versão posterior. -1. Você pode retornar para a visualização original do arquivo clicando no botão de diff de fonte. - - ![Botão de diff de fonte](/assets/images/help/pull_requests/dependency-review-source-diff.png) +{% data reusables.repositories.return-to-source-diff %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 877349b5cd..b493ba7367 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -32,13 +32,15 @@ Antes de enviar a revisão, os comentários em linha ficam com status _pendente_ {% if currentVersion == "free-pro-team@latest" %} ### Revisar alterações de dependência -Se o pull request contiver alterações em dependências, você poderá usar a revisão de dependências para um manifesto ou arquivo de bloqueio para ver o que mudou e verificar se as alterações introduzem vulnerabilidades de segurança. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +Se o pull request contiver alterações em dependências, você poderá usar a revisão de dependências para um manifesto ou arquivo de bloqueio para ver o que mudou e verificar se as alterações introduzem vulnerabilidades de segurança. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% data reusables.repositories.changed-files %} -1. À direita do cabeçalho para um manifesto ou arquivo de bloqueio, mostre a revisão de dependências clicando no botão de diff avançado. +1. À direita do cabeçalho de um manifesto ou arquivo de bloqueio, exiba a revisão de dependências clicando no botão de diff avançado**{% octicon "file" aria-label="The rich diff icon" %}**. ![Botão de diff avançado](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + +{% data reusables.repositories.return-to-source-diff %} {% endif %} ### Marcar um arquivo como visualizado @@ -65,5 +67,5 @@ Quando terminar de revisar os arquivos que deseja incluir na pull request, envie ### Leia mais -- "[Sobre revisões obrigatórias para pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)" - "[Filtrar pull requests por status de revisão](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 536216cd5a..03575a7c54 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ Os hooks pre-receive executam testes em um código do qual foi feito push em um Se o push não for aceito, você receberá uma mensagem de erro correspondente ao hook pre-receive com falha. -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md index 61fc34b59c..e6ea61859f 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization.md @@ -26,7 +26,17 @@ A organização pode usar o e-mail `name@organization.com` como um ponto públic ### Criar commits com um selo `on-behalf-of` na linha de comando -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +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. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% tip %} + + **Dica:** Se você estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, certifique-se de que existem duas novas linhas entre o final da sua descrição do commit e o indicador `on-behalf-of:`. + + {% endtip %} 2. Na próxima linha da mensagem do commit, digite `on-behalf-of: @org ` e, em seguida, aspas de fechamento. diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index 06b1572e0e..8174acfbb0 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -39,7 +39,17 @@ Você pode usar o {% data variables.product.prodname_desktop %} para criar um co {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} +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. + ```shell + $ git commit -m "Refactor usability tests. + > + > + ``` + {% 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:`. + + {% 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. diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index fa35031901..163aaade01 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -19,7 +19,7 @@ As pessoas que você escolhe como proprietários do código devem ter permissõe 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)". -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 "[Habilitar revisões obrigatórias para pull requests](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)". +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 currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Se uma equipe habilitou as atribuições de revisão de código, as aprovações individuais não vão atender ao requisito para a aprovação do proprietário do código em um branch protegido. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md index a1bb123070..968bc7e8b0 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md @@ -13,7 +13,7 @@ versions: ### Sobre READMEs -É possível adicionar um arquivo LEIAME a um repositório para comunicar informações importantes sobre o seu projeto. Um LEIAME, junto com uma licença de repositório{% if currentVersion == "free-pro-team@latest" %}, diretrizes de contribuição, e um código de conduta{% elsif enterpriseServerVersions contains currentVersion %} e diretrizes de contribuição{% endif %}, comunica as expectativas para o seu projeto e ajuda você a gerenciar contribuições. +É possível adicionar um arquivo README a um repositório para comunicar informações importantes sobre o seu projeto. Um README, junto com uma licença de repositório{% if currentVersion == "free-pro-team@latest" %}, diretrizes de contribuição, e um código de conduta{% elsif enterpriseServerVersions contains currentVersion %} e diretrizes de contribuição{% endif %}, comunica as expectativas para o seu projeto e ajuda você a gerenciar contribuições. Para obter mais informações sobre como fornecer diretrizes para o seu projeto, consulte {% if currentVersion == "free-pro-team@latest" %}"[Adicionar um código de conduta ao seu projeto](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)e {% endif %}"[Configurar o seu projeto para contribuições saudáveis](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)". @@ -42,7 +42,7 @@ Se você colocar o arquivo README na raiz do repositório, `docs`, ou no diretó ### Links de seção nos arquivos README e páginas blob -Muitos projetos usam uma tabela de conteúdo no início de um LEIAME para direcionar usuários para diferentes seções do arquivo. {% data reusables.repositories.section-links %} +Muitos projetos usam uma tabela de conteúdo no início de um README para direcionar usuários para diferentes seções do arquivo. {% data reusables.repositories.section-links %} ### Links relativos e caminhos de imagem em arquivos README diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index c28b4e307c..5ef016929b 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -23,8 +23,8 @@ Cada pessoa e organização podem ter repositórios ilimitados e convidar um nú {% endif %} Você pode usar repositórios para gerenciar seu trabalho e colaborar com outras pessoas. -- Você pode usar problemas para coletar feedback do usuário, relatar erros de software e organizar tarefas que você gostaria de realizar. Para obter mais informações, consulte "[Sobre problemas](/github/managing-your-work-on-github/about-issues)". -- {% data reusables.discussions.you-can-use-discussions %} +- Você pode usar problemas para coletar feedback do usuário, relatar erros de software e organizar tarefas que você gostaria de realizar. Para obter mais informações, consulte "[Sobre problemas](/github/managing-your-work-on-github/about-issues)."{% if currentVersion == "free-pro-team@latest" %} +- {% data reusables.discussions.you-can-use-discussions %}{% endif %} - É possível usar pull requests para propor alterações em um repositório. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". - Você pode usar quadros de projeto para organizar e priorizar seus problemas e pull requests. Para obter mais informações, consulte "[Sobre quadros de projeto](/github/managing-your-work-on-github/about-project-boards)". diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 40c6e4d0b9..b62b8d4ac6 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -74,7 +74,7 @@ Quando você pesquisar uma família de licenças, os resultados incluirão todas ### Identificar uma licença -[A licenciada de código aberto Ruby gem ](https://github.com/benbalter/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[A licenciada de código aberto Ruby gem ](https://github.com/licensee/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). Caso o seu repositório use uma licença listada no site Choose a License que não aparece na parte superior da página do repositório, ele pode conter licenças múltiplas ou outras complexidades. Para que sua licença seja detectada, simplifique o arquivo *LICENSE* e anote a complexidade em algum outro local, como no arquivo *LEIAME* do repositório. diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md index 33734a97e7..01bfbfa143 100644 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,7 +19,7 @@ Você pode descobrir, navegar e instalar aplicativos e ações criados por outro {% data reusables.actions.actions-not-verified %} -Qualquer um pode listar um {% data variables.product.prodname_github_app %} ou {% data variables.product.prodname_oauth_app %} grátis em {% data variables.product.prodname_marketplace %}. Os editores de aplicativos pagos são verificados por {% data variables.product.company_short %} e os anúncios para esses aplicativos são exibidos com um selo criador verificado de {% octicon "verified" aria-label="Verified creator badge" %}. Você também verá selos para aplicativos não verificados e verificados. Esses apps foram publicados usando o método anterior para verificar aplicativos individuais. Para obter mais informações sobre o processo atual, consulte "[Sobre criadores verificados](/developers/github-marketplace/about-verified-creators)" e "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)". +Qualquer um pode listar um {% data variables.product.prodname_github_app %} ou {% data variables.product.prodname_oauth_app %} grátis em {% data variables.product.prodname_marketplace %}. Os publicadores de aplicativos pagos são verificados por {% data variables.product.company_short %} e os anúncios desses aplicativos são mostrados com um selo do marketplace de {% octicon "verified" aria-label="Verified creator badge" %}. Você também verá selos para aplicativos não verificados e verificados. Esses apps foram publicados usando o método anterior para verificar aplicativos individuais. Para obter mais informações sobre o processo atual, consulte "[Sobre o GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" e "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)." ### Criar e listar uma ferramenta no {% data variables.product.prodname_marketplace %} diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md index bd92c65f73..910e406720 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/about-codespaces.md @@ -38,6 +38,8 @@ Todos os desenvolvedores podem criar um ou mais codespaces para qualquer reposit {% data reusables.codespaces.about-personalization %} 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)". +Você pode definir as configurações para adicionar segredos criptografados, habilitar a verificação de GPG e permitir que os codespaces acessem outros repositórios. Para obter mais informações, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Gerenciar verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)" e "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". + {% data reusables.codespaces.you-can-see-all-your-codespaces %} {% data reusables.codespaces.beta-functionality-limited %} diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/index.md b/translations/pt-BR/content/github/developing-online-with-codespaces/index.md index 9cef2e35f9..9bb126005c 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/index.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/index.md @@ -19,6 +19,9 @@ versions: {% link_in_list /creating-a-codespace %} {% link_in_list /developing-in-a-codespace %} {% link_in_list /personalizing-codespaces-for-your-account %} +{% link_in_list /managing-encrypted-secrets-for-codespaces %} +{% link_in_list /managing-access-and-security-for-codespaces %} +{% link_in_list /managing-gpg-verification-for-codespaces %} {% link_in_list /deleting-a-codespace %} {% link_in_list /troubleshooting-your-codespace %} {% link_in_list /using-codespaces-in-visual-studio-code %} diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md index 0de052636d..68a8e71b65 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing access and security for Codespaces -intro: You can manage the repositories that codespaces can access. +title: Gerenciar o acesso e a segurança de codespaces +intro: Você pode gerenciar os repositórios que os codespaces podem acessar. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,30 +8,30 @@ versions: {% note %} -**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**Observação:** O acesso e a segurança para {% data variables.product.prodname_codespaces %} estão atualmente em fase beta e sujeitos a alterações. {% endnote %} -### Managing security and access for your user account +### Gerenciar a segurança e o acesso da sua conta de usuário -When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. +Ao habilitar o acesso e a segurança de um repositório pertencente à sua conta de usuário, quaisquer codespaces que você criar para esse repositório terão permissões de leitura e gravação em todos os outros repositórios que você possuir. Você pode habilitar o acesso e a segurança em nenhum dos seus repositórios, em todos os seus repositórios ou em repositórios específicos. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-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 you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) +1. Em "Acesso e segurança", selecione a configuração que deseja para sua conta de usuário. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. Se você escolher "repositórios selecionados", selecione o menu suspenso e clique em um repositório para permitir que os codespaces do repositório tenham acesso a outros repositórios dos quais você é proprietário. Repita para todos os repositórios cujos codespaces você deseja que acessem outros repositórios dos quais você é proprietário. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) -### Managing security and access for your organization +### Gerenciar a segurança e o acesso para a sua organização -Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. +Os proprietários da organização podem gerenciar a segurança e o acesso para {% data variables.product.prodname_codespaces %}. -When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. +Ao habilitar o acesso e a segurança de um repositório pertencente à sua organização, todos os codespaces criados para esse repositório terão permissões de leitura e gravação em todos os outros repositórios pertencentes à organização. Você pode habilitar o acesso e a segurança em nenhum dos repositórios da sua organização, em todos os seus repositórios da sua organização ou em repositórios específicos. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.click-codespaces %} -5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. - ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.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-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) +5. Para aprovar os [termos de serviço do programa de pré-lançamento](/github/site-policy/github-pre-release-program) em nome da sua organização e habilitar {% data variables.product.prodname_codespaces %}, em "Permissões do usuário", selecione **Usuários selecionados** e, em seguida, digite o nome de usuário para cada pessoa conceder acesso. Repita para todos os usuários que você deseja que tenham acesso aos codespaces da sua organização. + ![Botão de opção para "Usuários selecionados"](/assets/images/help/organizations/select-selected-users-radio-button.png) +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-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) diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md index 117a0bac28..09ef580598 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing encrypted secrets for Codespaces -intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +title: Gerenciar segredos criptografados para codespaces +intro: Você pode armazenar informações confidenciais, como tokens, que você deseja acessar nos seus codespaces por meio de variáveis de ambiente. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,46 +8,46 @@ versions: {% note %} -**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**Observação:** Os segredos criptografados para {% data variables.product.prodname_codespaces %} estão atualmente na versão beta e sujeitos a alterações. {% endnote %} -### About encrypted secrets for {% data variables.product.prodname_codespaces %} +### Sobre os segredos criptografados para {% data variables.product.prodname_codespaces %} -You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. +Você pode adicionar segredos criptografados à sua conta de usuário que deseja usar nos seus codespaces. Por exemplo, você pode querer armazenar e acessar as seguintes informações confidenciais como segredos criptografados. -- Personal access tokens to cloud services -- Service principals -- Subscription identifiers +- Tokens de acesso pessoal para os serviços da nuvem +- Entidades de serviço +- Identificadores da assinatura -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. +Você pode escolher quais repositórios devem ter acesso a cada segredo. Em seguida, você pode usar o segredo em qualquer código que criar para um repositório que tiver acesso ao segredo. -### Adding a secret +### Adicionar um segredo {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +1. À direita dos "Segredos dos codespaces", clique em **Novo segredo**. ![Botão "Novo segredo"](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Em "Nome", digite um nome para seu segredo. ![Caixa de texto "Nome"](/assets/images/help/settings/codespaces-secret-name-field.png) {% data reusables.user_settings.codespaces-secret-value %} {% data reusables.user_settings.codespaces-secret-repository-access %} 1. Clique em **Add secret** (Adicionar segredo). -### Editing a secret +### Editar um segredo -You can update the value of an existing secret, and you can change which repositories can access a secret. +Você pode atualizar o valor de um segredo existente, bem como alterar quais repositórios podem acessar um segredo. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +1. Em "Segredos do codespace", à direita do segredo que você deseja editar, clique em **Atualizar**. ![Botão "Atualizar"](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Em "Valor", clique em **Inserir um novo valor**. ![Link "Inserir um novo valor"](/assets/images/help/settings/codespaces-secret-update-value-text.png) {% data reusables.user_settings.codespaces-secret-value %} {% data reusables.user_settings.codespaces-secret-repository-access %} -1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Opcionalmente, para remover o acesso do segredo a um repositório, desmarque o repositório. ![Caixas de seleção para remover acesso aos repositórios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) 1. Clique em **Save changes** (Salvar alterações). -### Deleting a secret +### Excluir um segredo {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Leia o alerta e clique em **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) +1. Em "Segredos dos codespaces", à direita do segredo que você deseja excluir, clique em **Excluir**. ![Botão "Excluir"](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Leia o alerta e clique em **OK**. ![Confirmação para excluir um segredo](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md index a326f5be89..e9d9442190 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing GPG verification for Codespaces -intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +title: Gerenciar a verificação de GPG de codespaces +intro: Você pode permitir que {% data variables.product.company_short %} use o GPG automaticamente para assinar os commits que você faz nos seus codespaces para que outras pessoas possam confiar que as alterações vêm de uma fonte de confiança. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,13 +8,13 @@ versions: {% note %} -**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**Observação:** A verificação do GPG para {% data variables.product.prodname_codespaces %} está atualmente em fase beta e sujeita a alterações. {% endnote %} -After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." +Depois que você habilitar a verificação do GPG, {% data variables.product.company_short %} assinará automaticamente os commits que você fizer em {% data variables.product.prodname_codespaces %}, e os commits terão um status de verificado em {% data variables.product.product_name %}. Por padrão, a verificação do GPG está desabilitada para os codespaces que você criar. Você pode optar por permitir a verificação do GPG para todos os repositórios ou repositórios específicos. Habilite apenas a verificação do GPG para repositórios nos quais você confia. Para obter mais informações sobre commits assinado por {% data variables.product.product_name %}, consulte "[Sobre a verificação de assinatura do commit](/github/authenticating-to-github/about-commit-signature-verification)". {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) +1. Em "Verificação do GPG, selecione a configuração que deseja para verificação do GPG. ![Botões de opção para gerenciar a verificação do GPG](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para o qual deseja habilitar a verificação do GPG. Repita esse procedimento para todos os repositórios para os quais você deseja habilitar a verificação do GPG. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md index af356b8368..44ea11aaae 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md @@ -40,6 +40,7 @@ Para obter mais informações, consulte [Personalizar](https://docs.microsoft.co {% endnote %} +Você também pode definir as configurações para que a sua conta de usuário adicione segredos criptografados, habilitar a verificação de GPG e permitir que os seus codespaces acessem outros repositórios. Para obter mais informações, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Gerenciar verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)" e "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". ### Leia mais diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index ce18e7150f..57094f656f 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ Para integrar {% data variables.product.prodname_code_scanning %} ao seu sistema De modo geral, você invoca o {% data variables.product.prodname_codeql_runner %} da seguinte forma. -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -39,7 +39,7 @@ O {% data variables.product.prodname_codeql_runner %} detecta e faz a varredura 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 as linguagens compatíveis são `cpp`, `csharp`, `go`, `java`, `javascript` e `python`. -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -55,7 +55,7 @@ Se você também estiver usando um arquivo de configuração para configuraçõe 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 ``` @@ -68,7 +68,7 @@ O arquivo de configuração é um arquivo YAML. Ele usa uma sintaxe semelhante 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 ``` @@ -84,7 +84,7 @@ Para muitos sistemas de criação comuns, o {% data variables.product.prodname_c 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 ``` diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index 39c41a2402..5a047120a9 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -40,13 +40,16 @@ Você decide como gerar alertas do {% data variables.product.prodname_code_scann No {% data variables.product.prodname_codeql_workflow %} padrão, {% data variables.product.prodname_code_scanning %} está configurado para analisar o seu código cada vez que você fizer push de uma alteração no branch-padrão ou em qualquer branch protegido, ou criar um pull request contra o branch padrão. Como resultado, {% data variables.product.prodname_code_scanning %} vai começar agora. +### Habilitar {% data variables.product.prodname_code_scanning %} em massa +Você pode habilitar {% data variables.product.prodname_code_scanning %} em muitos repositórios em massa usando um script. Para obter um exemplo de um script que apresenta pull requests para adicionar um fluxo de trabalho de {% data variables.product.prodname_actions %} em vários repositórios, veja o repositório [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs). + ### Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %} Depois de habilitar o {% data variables.product.prodname_code_scanning %} para o seu repositório, você poderá inspecionar a saída das ações conforme forem executadas. {% data reusables.repositories.actions-tab %} - Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. + Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. O texto da entrada é o título que você deu à sua mensagem de commit. ![Lista de ações que mostram o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index ba573e5bf4..7a1747e907 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ Você pode configurar {% data variables.product.prodname_code_scanning %} para v 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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 propriedades do alerta, como, por exemplo, a gravidade 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. diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 39018f0f9f..8f302d1359 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,16 @@ Você pode usar {% data variables.product.prodname_codeql_runner %} para executa O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que executa a análise de {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Você adiciona o executor ao seu sistema de terceiros e, em seguida, chama o executor para analisar o código e fazer o upload dos resultados para o {% data variables.product.product_location %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório. -{% data reusables.code-scanning.codeql-runner-license %} +{% note %} + +**Notas:** +{% if currentVersion == "free-pro-team@latest" %} +* O {% data variables.product.prodname_codeql_runner %} usa o CLI de {% data variables.product.prodname_codeql %} para analisar o código e, portanto, tem as mesmas condições da licença. É grátis usar em repositórios públicos que são mantidos no {% data variables.product.prodname_dotcom_the_website %}, e disponíveis para uso em repositórios privados que são propriedade de clientes com uma licença do {% data variables.product.prodname_advanced_security %}. Para obter informações, consulte "[{% data variables.product.product_name %} Termos e Condições](https://securitylab.github.com/tools/codeql/license) de do CLI de {% data variables.product.prodname_codeql %} " e "[{% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +{% else %} +* O {% data variables.product.prodname_codeql_runner %} está disponível para os clientes com uma licença de {% data variables.product.prodname_advanced_security %}. +{% endif %} +* O {% data variables.product.prodname_codeql_runner %} não deve ser confundido com o CLI de {% data variables.product.prodname_codeql %}. O CLI de {% data variables.product.prodname_codeql %} é uma interface de linha de comando interativa que permite que você crie bancos de dados de {% data variables.product.prodname_codeql %} para pesquisa de segurança e realize consultas de {% data variables.product.prodname_codeql %}. Para obter mais informações, consulte "[ CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +{% endnote %} ### Fazer o download do {% data variables.product.prodname_codeql_runner %} @@ -51,7 +60,7 @@ No Windows, o arquivo `codeql-runner-win.exe` normalmente não exige alteração ### Adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de CI -Após concluído o download do {% data variables.product.prodname_codeql_runner %} e verificado que pode ser executado, você deve disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. É importante notar que cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %} deve ter o {% data variables.product.prodname_codeql_runner %}. Você pode configurar cada servidor para copiar o executor a partir de um local central interno ou você pode usar a API REST para obter o executor direto do GitHub, por exemplo: +Após fazer o download de {% data variables.product.prodname_codeql_runner %} e verificar se pode ser executado, você deverá disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. Por exemplo, você pode configurar cada servidor para que copie o executor de um local central interno. Como alternativa, você pode usar a API REST para obter o executor diretamente do GitHub, por exemplo: ```shell wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux @@ -60,8 +69,8 @@ chmod +x codeql-runner-linux Além disso, cada servidor de CI também precisa: -- Um {% data variables.product.prodname_github_apps %} ou um token de acesso pessoal para {% data variables.product.prodname_codeql_runner %} usar. Para repositórios privados, o token deve ter o escopo do `repositório`. Para público, o token precisa apenas dos escopos `public_repo` e `repo:security_events`. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". -- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. Este pacote contém CLI de {% data variables.product.prodname_codeql %}, consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %}. Para obter informações, consulte "[CLI de {% data variables.product.prodname_codeql %}](https://help.semmle.com/codeql/codeql-cli.html)". +- Um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para {% data variables.product.prodname_codeql_runner %} usar. Você deve usar um token de acesso com o escopo `security_events` ou um {% data variables.product.prodname_github_app %} com a permissão de gravação `security_events`. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. Este pacote contém consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %} mais o CLI de {% data variables.product.prodname_codeql %}, que é usado internamente pelo executor. Para obter informações, consulte "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são: @@ -84,6 +93,8 @@ Você pode configurar o local onde o {% data variables.product.prodname_codeql_r Para visualizar a referência de linha de comando para o executor, use o sinalizador `-h`. Por exemplo, para listar todos os comandos executados: `codeql-runner-OS -h` ou para listar todos os sinalizadores disponíveis para o comando `init` executado: `codeql-runner-OS init -h` (em que `OS` varia de acordo com o executável que você está usando). Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)". +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Exemplo básico Este exemplo executa a análise do {% data variables.product.prodname_codeql %} em um servidor de Linux CI para o repositório `octo-org/example-repo` hospedado em `{% data variables.command_line.git_url_example %}`. O processo é muito simples porque o repositório contém apenas linguagens que podem ser analisadas diretamente pelo {% data variables.product.prodname_codeql %}, sem ser criado (ou seja, Go, JavaScript, Python e TypeScript). diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 22fa4181b4..7a4bc1a77d 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -40,6 +40,8 @@ Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFinge 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 %}. @@ -82,6 +84,8 @@ O {% data variables.product.prodname_code_scanning_capc %} usa o objeto `executa #### 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 %}. | @@ -89,7 +93,7 @@ O {% data variables.product.prodname_code_scanning_capc %} usa o objeto `executa | `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. 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. | +| `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). | @@ -109,7 +113,7 @@ Um local dentro de um artefato de programação, como, por exemplo, um arquivo n | 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. For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. | +| `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. | diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index ab553d6878..d10a87bf69 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: Em repositórios onde {% data variables.product.prodname_code_scanning %} está configurado como uma verificação de pull request, {% data variables.product.prodname_code_scanning %} verifica o código no pull request. Por padrão, isso é limitado a pull requests que visam o branch-padrão ou branches protegidos, mas você pode alterar esta configuração em {% data variables.product.prodname_actions %} ou em um sistema de CI/CD de terceiros. Se o merge das alterações introduziria novos alertas de {% data variables.product.prodname_code_scanning %} no branch de destino, estes serão relatados como resultados de verificação no pull request. Os alertas também são exibidos como anotações na aba **Arquivos alterados** do pull request. Se você tiver permissão de gravação no repositório, você poderá ver qualquer alerta de {% data variables.product.prodname_code_scanning %} existente na aba **Segurança**. Para obter informações sobre os alertas do repositório, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} do repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido que foi habilitado por {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou {% if currentVersion == "enterprise-server@2. 2" %}fechar{% else %}dismiss{% endif %} todos os erros alertas antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre verificações de status obrigatórias](/github/administering-a-repository/about-required-status-checks)". +Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido que foi habilitado por {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou {% if currentVersion == "enterprise-server@2. 2" %}fechar{% else %}dismiss{% endif %} todos os erros alertas antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". ![Ocorreu uma falha na verificação de {% data variables.product.prodname_code_scanning %} em um pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md index e5e86c2b05..d8878480d1 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md @@ -12,6 +12,7 @@ versions: {% data reusables.code-scanning.beta-codeql-runner %} {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### O comando `init` leva muito tempo diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md index 0b9026a06a..87a9ac2e1a 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md @@ -11,6 +11,7 @@ versions: --- {% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.not-available %} ### Ocorreu uma falha durante a criação automática para uma linguagem compilada @@ -81,17 +82,6 @@ Para obter mais informações sobre a especificação de etapas de criação, co O recurso de {% data variables.product.prodname_codeql %} `autobuild` usa heurística para criar o código em um repositório. No entanto, às vezes, essa abordagem resulta em uma análise incompleta de um repositório. Por exemplo, quando uma compilação múltipla de `build.sh` existe em um único repositório, é possível que a análise não seja concluída, já que a etapa `autobuild` executará apenas um dos comandos. A solução é substituir a etapa `autobuild` pelas etapas de criação que criam todo o código-fonte que você deseja analisar. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". -### Error: "Erro do servidor" - -Se a execução de um fluxo de trabalho para {% data variables.product.prodname_code_scanning %} falhar devido a um erro no servidor, tente executar o fluxo de trabalho novamente. Se o problema persistir, entre em contato com {% data variables.contact.contact_support %}. - -### Erro: "Fora do disco" ou "Sem memória" -Em projetos muito grandes, - -{% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor. -{% if currentVersion == "free-pro-team@latest" %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema. -{% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %} - ### A criação demora muito tempo Se a sua criação com a análise de {% data variables.product.prodname_codeql %} demorar muito para ser executada, existem várias abordagens que você pode tentar para reduzir o tempo de criação. @@ -126,3 +116,54 @@ Se você estiver analisando o código escrito no Python, você poderá ver resul Nos executores hospedados no GitHub que usam o Linux, o {% data variables.product.prodname_codeql_workflow %} tenta instalar e analisar as dependências do Python, o que pode gerar mais resultados. Para desabilitar a instalação automática, adicione `setup-python-dependencies: false` à etapa "Inicializar CodeQL" do fluxo de trabalho. Para obter mais informações sobre a configuração da análise de dependências do Python, consulte "[Analisar as dependências do Python](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)". {% endif %} + +### Error: "Erro do servidor" + +Se a execução de um fluxo de trabalho para {% data variables.product.prodname_code_scanning %} falhar devido a um erro no servidor, tente executar o fluxo de trabalho novamente. Se o problema persistir, entre em contato com {% data variables.contact.contact_support %}. + +### Erro: "Fora do disco" ou "Sem memória" +Em projetos muito grandes, + +{% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor. +{% if currentVersion == "free-pro-team@latest" %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema. +{% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %} + +### Aviso: "git checkout HEAD^2 is no longer necessary" + +Se você estiver usando um fluxo de trabalho antigo de {% data variables.product.prodname_codeql %}, você poderá receber o aviso a seguir na saída "Inicializar {% data variables.product.prodname_codeql %}" da ação: + +``` +Aviso: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer +necessary. Please remove this step as Code Scanning recommends analyzing the merge +commit for best results. +``` + +Corrija isto removendo as seguintes linhas do fluxo de trabalho {% data variables.product.prodname_codeql %}. Essas linhas foram incluídas na seção `etapas` do trabalho `Analyze` nas versões iniciais do fluxo de trabalho de {% data variables.product.prodname_codeql %}. + +```yaml + with: + # We must fetch at least the immediate parents so that if this is + # a pull request then we can checkout the head. + fetch-depth: 2 + + # If this run was triggered by a pull request event, then checkout + # the head of the pull request instead of the merge commit. + - run: git checkout HEAD^2 + if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %} +``` + +A seção revisada de `etapas` do fluxo de trabalho será parecida com esta: + +```yaml + steps: + - name: Checkout repository + uses: actions/checkout@v2 + + # Initializes the {% data variables.product.prodname_codeql %} tools for scanning. + - name: Initialize {% data variables.product.prodname_codeql %} + uses: github/codeql-action/init@v1 + + ... +``` + +Para obter mais informações sobre a edição do arquivo de fluxo de trabalho {% data variables.product.prodname_codeql %}, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)". \ No newline at end of file diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 23f0938c8e..a80ccde03b 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -27,6 +27,8 @@ Você pode fazer o upload dos resultados usando {% data variables.product.prodna - {% 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 de resultados, você poderá usar o comando `upload` (para obter mais informações, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-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 obter mais informações, consulte "[Fazer o upload de um arquivo SARIF](/rest/reference/code-scanning#upload-a-sarif-file)"). +{% 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 "[Aprender {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" e "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". @@ -37,6 +39,8 @@ A ação `upload-sarif` pode ser configurada para ser executada quando ocorrem o 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-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. diff --git a/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md index d5628a3669..9c99697884 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md @@ -1,6 +1,6 @@ --- -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. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +title: Sobre o GitHub Advanced Security +intro: '{% data variables.product.prodname_dotcom %} disponibiliza funcionalidades extras de segurança para os clientes em uma licença de {% data variables.product.prodname_advanced_security %}. Essas funcionalidades também estão habilitadas para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}.' versions: free-pro-team: '*' enterprise-server: '>=3.0' @@ -8,41 +8,41 @@ versions: ### Sobre o {% data variables.product.prodname_GH_advanced_security %} -{% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) +{% data variables.product.prodname_dotcom %} tem muitas funcionalidades que ajudam você a melhorar e manter a qualidade do seu código. Algumas delas estão incluídas em todos os planos, por exemplo: gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (Ou seja, repositórios privados e internos em {% data variables.product.prodname_dotcom_the_website %}, e todos os repositórios em {% data variables.product.prodname_ghe_server %}.) -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +Para uma visão geral de todas as funcionalidades de segurança, consulte "[Sobre como proteger seu repositório](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)". Para obter informações sobre os requisitos de permissão para ações relacionadas às funcionalidades de segurança, consulte "[Níveis de permissão do repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)". -### About {% data variables.product.prodname_advanced_security %} features +### Sobre as funcionalidades de {% data variables.product.prodname_advanced_security %} -A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: +Uma licença de {% data variables.product.prodname_GH_advanced_security %} fornece as funcionalidades adicionais a seguir: -- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. 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 %}** - 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_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. 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 %}** - 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)". {% if currentVersion == "free-pro-team@latest" %} -- **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 "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +- **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 "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% endif %} -For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." +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)". {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} +### Habilitar funcionalidades de {% data variables.product.prodname_advanced_security %} em {% data variables.product.prodname_ghe_server %} -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)." +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)". -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](/github/setting-up-and-managing-organizations-and-teams/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)." -For information about purchasing a license for +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](/github/setting-up-and-managing-organizations-and-teams/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)". +Para obter informações sobre a compra de uma licença para -{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% data variables.product.prodname_GH_advanced_security %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. {% endif %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} +### Habilitar funcionalidades de {% data variables.product.prodname_advanced_security %} em {% data variables.product.prodname_dotcom_the_website %} -For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. +Para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}, essas funcionalidades estão permanentemente habilitadas e só serão desabilitados se você alterar a visibilidade do projeto, de modo que o código não seja mais público. -For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/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)." -For information about purchasing a license for +Para todos os outros repositórios, uma vez que você tenha uma licença, é possível habilitar e desabilitar essas funcionalidades no nível de organização ou repositório. {% if currentVersion == "free-pro-team@latest" %}Para mais informações, consulte "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/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)". +Para obter informações sobre a compra de uma licença para -{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% data variables.product.prodname_GH_advanced_security %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. {% endif %} diff --git a/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md index 1919591b2b..d9aa3a9c59 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ O {% data variables.product.prodname_learning %} oferece cursos interativos grá {% endif %} -Conheça melhor o {% data variables.product.product_name %} por meio de nossos artigos [bootcamp](/categories/bootcamp/). 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. +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. {% data reusables.support.ask-and-answer-forum %} #### Branches, bifurcações e pull requests -Saiba como [criar branches no Git ](http://learngitbranching.js.org/) com uma ferramenta interativa. Leia sobre [bifurcações](/articles/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 %}. - -Faça consultas rápidas sobre [linha de comando](https://hub.github.com) e também sobre {% data variables.product.prodname_dotcom %} [ listas de verificação, folhas de consultas e mais](https://services.github.com/on-demand/resources). +Saiba como [criar branches no Git ](http://learngitbranching.js.org/) com uma ferramenta interativa. Leia sobre [bifurcações](/articles/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/). #### Fique antenado @@ -41,9 +39,9 @@ Nosso {% data variables.product.prodname_dotcom %} [canal do YouTube de Treiname ### Treinamentos -#### Aulas grátis +#### Cursos grátis -O {% data variables.product.product_name %} oferece uma série de [treinamentos sob demanda](https://services.github.com/on-demand/) interativos, inclusive {% data variables.product.prodname_dotcom %} 101: [Introdução](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %} 102: [Desktop GitHub](https://services.github.com/on-demand/github-desktop) e {% data variables.product.prodname_dotcom %} 103: [Linha de comando](https://services.github.com/on-demand/github-cli). +{% 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 %}. #### Programas educacionais online do {% data variables.product.prodname_dotcom %} diff --git a/translations/pt-BR/content/github/getting-started-with-github/git-cheatsheet.md b/translations/pt-BR/content/github/getting-started-with-github/git-cheatsheet.md index 1f8ae4b1ad..9865269d0a 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/pt-BR/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -Aprender sobre todos os comandos Git disponíveis pode ser uma tarefa muito difícil. Mantenha uma das [Folhas de Consulta Git](https://services.github.com/on-demand/resources/cheatsheets/) perto de você para referências. O artigo Usar Folhas de Consulta Git está disponível em vários idiomas. Para obter mais informações, consulte a [página de recursos no site GitHub Services](https://services.github.com/on-demand/resources/). +Aprender sobre todos os comandos Git disponíveis pode ser uma tarefa muito difícil. Nossas folhas de dicas fornecem uma referência rápida para os comandos que você usará com mais frequência: consulte "[Folhas de dicas do Git](https://training.github.com/)". A folha de dicas sobre "Como usar o Git" está disponível em vários idiomas. Complementarmente, entre em nossa página [recursos de aprendizagem Git e GitHub](/articles/git-and-github-learning-resources/), que apresenta links para orientações, vídeos e outros. diff --git a/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md index f8e64d3dc5..c9fbcb0e56 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md @@ -1,15 +1,18 @@ --- title: GitHub para dispositivos móveis -intro: 'Faça triagem, colabore e gerencie seu trabalho em {% data variables.product.company_short %} do seu dispositivo móvel.' +intro: 'Faça triagem, colabore e gerencie seu trabalho em {% data variables.product.product_name %} do seu dispositivo móvel.' versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- +{% data reusables.mobile.ghes-release-phase %} + ### Sobre o {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} está atualmente disponível para usuários {% data variables.product.prodname_dotcom_the_website %} como app Android e iOS. +{% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} oferece a você uma maneira de realizar trabalhos de alto impacto {% data variables.product.prodname_dotcom %} rapidamente e de qualquer lugar. O {% data variables.product.prodname_mobile %}é uma maneira segura e confiável de acessar seus dados {% data variables.product.prodname_dotcom %} através de um aplicativo cliente confiável e primordial. +{% 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. Com o {% data variables.product.prodname_mobile %} você pode: - Gerenciar, fazer triagem e limpar notificações @@ -23,12 +26,38 @@ Para mais informações sobre notificações para {% data variables.product.prod Para instalar {% data variables.product.prodname_mobile %} para Android ou iOS, consulte [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +### Gerenciar contas + +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 %}. + +{% 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. + +#### Pré-requisitos + +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 %}. + +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. Para obter mais informações, consulte "[Notas de versão](/enterprise-server/admin/release-notes)" e "[Gerenciar {% data variables.product.prodname_mobile %} para a sua empresa](/admin/configuration/managing-github-for-mobile-for-your-enterprise)". + +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 %}. + +#### Adicionar, alternar ou encerrar a sessão das contas + +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. + +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. + +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**. + ### Idiomas compatíveis com {% data variables.product.prodname_mobile %} {% data variables.product.prodname_mobile %} está disponível nos seguintes idiomas. +- English - Japanese - Português do Brasil +- Chinês simplificado - 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 %}. @@ -37,9 +66,9 @@ Se você configurar o idioma do seu dispositivo para um idioma compatível, {% d {% 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 -Para desabilitar os links universais, mantenha qualquer link {% data variables.product.prodname_dotcom %} pressionado e, em seguida, pressione **Abrir**. Toda vez que você clica em um link {% data variables.product.prodname_dotcom %} no futuro, a URL de destino abrirá no Safari em vez do {% data variables.product.prodname_mobile %}. +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 %}. -Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.prodname_dotcom %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. +Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.product_name %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. ### Compartilhando feedback diff --git a/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md b/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md index 3735db6d81..090ee7e077 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md +++ b/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md @@ -1,5 +1,6 @@ --- -title: GitHub's products +title: Produtos do GitHub +intro: 'Uma visão geral dos produtos e planos de preços de {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/github-s-products - /articles/githubs-products @@ -9,95 +10,96 @@ versions: github-ae: '*' --- -{% data variables.product.prodname_dotcom %} offers free and paid products. You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} +O {% data variables.product.prodname_dotcom %} oferece produtos grátis e pagos. Você pode ver o preço e uma lista completa dos recursos de cada produto em <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} -### {% data variables.product.prodname_free_user %} for user accounts +### {% data variables.product.prodname_free_user %} para contas de usuário -With {% data variables.product.prodname_free_team %} for user accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set. +Com o {% data variables.product.prodname_free_team %} para contas de usuário, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados com um conjunto completo de recursos e em repositórios privados ilimitados com um conjunto de recursos limitado. -With {% data variables.product.prodname_free_user %}, your user account includes: +Com o {% data variables.product.prodname_free_user %}, sua conta de usuário inclui: - {% data variables.product.prodname_gcf %} - {% data variables.product.prodname_dependabot_alerts %} -- Two-factor authentication enforcement -- 2,000 {% data variables.product.prodname_actions %} minutes -- 500MB {% data variables.product.prodname_registry %} storage +- Implementação de autenticação de dois fatores +- 2.000 {% data variables.product.prodname_actions %} minutos +- 500MB {% data variables.product.prodname_registry %} de armazenamento ### {% data variables.product.prodname_pro %} -In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_pro %} includes: -- {% data variables.contact.github_support %} via email -- 3,000 {% data variables.product.prodname_actions %} minutes -- 2GB {% data variables.product.prodname_registry %} storage -- Advanced tools and insights in private repositories: - - Required pull request reviewers - - Multiple pull request reviewers - - Auto-linked references +Além dos recursos disponíveis no {% data variables.product.prodname_free_user %} para contas de usuário, o {% data variables.product.prodname_pro %} inclui: +- {% data variables.contact.github_support %} via e-mail +- 3.000 {% data variables.product.prodname_actions %} minutos +- 2GB {% data variables.product.prodname_registry %} de armazenamento +- Ferramentas avançadas e insights em repositórios privados: + - Revisores de pull request necessários + - Múltiplos revisores de pull request + - Referências autovinculadas - {% data variables.product.prodname_pages %} - Wikis - - Protected branches - - Code owners - - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks + - Branches protegidos + - Proprietários de código + - Gráficos de informações de repositório: Pulse, contribuidores, tráfego, commits, frequência de códigos, rede e bifurcações -### {% data variables.product.prodname_free_team %} for organizations +### {% data variables.product.prodname_free_team %} para organizações -With {% data variables.product.prodname_free_team %} for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. +Com o {% data variables.product.prodname_free_team %} para organizações, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados com um conjunto completo de recursos ou em repositórios privados ilimitados com um conjunto de recursos limitado. -In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_free_team %} for organizations includes: +Além dos recursos disponíveis no {% data variables.product.prodname_free_user %} para contas de usuário, o {% data variables.product.prodname_free_team %} para organizações inclui: - {% data variables.product.prodname_gcf %} -- Team discussions -- Team access controls for managing groups -- 2,000 {% data variables.product.prodname_actions %} minutes -- 500MB {% data variables.product.prodname_registry %} storage +- Discussões de equipe +- Controles de acesso de equipes para gerenciar grupos +- 2.000 {% data variables.product.prodname_actions %} minutos +- 500MB {% data variables.product.prodname_registry %} de armazenamento ### {% data variables.product.prodname_team %} -In addition to the features available with {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %} includes: -- {% data variables.contact.github_support %} via email -- 3,000 {% data variables.product.prodname_actions %} minutes -- 2GB {% data variables.product.prodname_registry %} storage -- Advanced tools and insights in private repositories: - - Required pull request reviewers - - Multiple pull request reviewers +Além dos recursos disponíveis no {% data variables.product.prodname_free_team %} para organizações, o {% data variables.product.prodname_team %} inclui: +- {% data variables.contact.github_support %} via e-mail +- 3.000 {% data variables.product.prodname_actions %} minutos +- 2GB {% data variables.product.prodname_registry %} de armazenamento +- Ferramentas avançadas e insights em repositórios privados: + - Revisores de pull request necessários + - Múltiplos revisores de pull request - {% data variables.product.prodname_pages %} - Wikis - - Protected branches - - Code owners - - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks - - Draft pull requests - - Team pull request reviewers - - Scheduled reminders + - Branches protegidos + - Proprietários de código + - Gráficos de informações de repositório: Pulse, contribuidores, tráfego, commits, frequência de códigos, rede e bifurcações + - Pull requests de rascunho + - Equipe de revisores de pull request + - Lembretes agendados {% data reusables.github-actions.actions-billing %} ### {% data variables.product.prodname_enterprise %} -{% data variables.product.prodname_enterprise %} includes two deployment options: cloud-hosted and self-hosted. +O {% data variables.product.prodname_enterprise %} inclui duas opções de implementação: hospedagem em nuvem e auto-hospedagem. -In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes: +Além dos recursos disponíveis no {% data variables.product.prodname_team %}, o {% data variables.product.prodname_enterprise %} inclui: - {% data variables.contact.enterprise_support %} -- Additional security, compliance, and deployment controls -- Authentication with SAML single sign-on -- Access provisioning with SAML or SCIM +- Segurança adicional, conformidade e controles de instalação +- Autenticação com SAML de logon único +- Provisionamento de acesso com SAML ou SCIM - {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_ghe_cloud %} also includes: -- {% data variables.contact.enterprise_support %}. For more information, see "{% data variables.product.prodname_ghe_cloud %} support" and "{% data variables.product.prodname_ghe_cloud %} Addendum." -- 50,000 {% data variables.product.prodname_actions %} minutes -- 50GB {% data variables.product.prodname_registry %} storage -- A service level agreement for 99.9% monthly uptime -- The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." +O {% data variables.product.prodname_ghe_cloud %} também inclui: +- {% data variables.contact.enterprise_support %}. Para obter mais informações, consulte "{% data variables.product.prodname_ghe_cloud %} suporte" e "{% data variables.product.prodname_ghe_cloud %} Adendo" +- 50.000 {% data variables.product.prodname_actions %} minutos +- 50GB {% data variables.product.prodname_registry %} de armazenamento +- Controle de acesso para sites de {% data variables.product.prodname_pages %}. Para obter mais informações, consulte Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}" +- Um acordo de nível de serviço para tempo de atividade de 99,9% por mês +- A opção de gerenciar de forma centralizada a política e cobrança para várias organizações {% data variables.product.prodname_dotcom_the_website %} com uma conta corporativa. Para obter mais informações, consulte "Sobre contas corporativas". -You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "Setting up a trial of {% data variables.product.prodname_ghe_cloud %}." +Você pode configurar uma versão para avaliar o {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}". -For more information about hosting your own instance of [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contact {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %} +Para obter mais informações sobre hospedar sua própria instância do [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), entre em contato com {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %} ### {% data variables.product.prodname_ghe_one %} -{% data variables.product.prodname_ghe_one %} includes [{% data variables.product.prodname_enterprise %}](#github-enterprise), plus: +O {% data variables.product.prodname_ghe_one %} inclui [{% data variables.product.prodname_enterprise %}](#github-enterprise), mais: - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} -- [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations) +- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. 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){% endif %} +- [{% data variables.product.prodname_learning %} para organizações](https://lab.github.com/organizations) -For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact [{% data variables.product.product_name %}'s Sales team](https://enterprise.github.com/contact). +Para obter mais informações sobre a inscrição para {% data variables.product.prodname_ghe_one %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/github/getting-started-with-github/index.md b/translations/pt-BR/content/github/getting-started-with-github/index.md index 97e4f61fac..ac9638c73c 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/index.md +++ b/translations/pt-BR/content/github/getting-started-with-github/index.md @@ -28,6 +28,7 @@ versions: {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} {% link_in_list /githubs-products %} + {% link_in_list /about-github-advanced-security %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} {% link_in_list /types-of-github-accounts %} {% link_in_list /faq-about-changes-to-githubs-plans %} diff --git a/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md index f3f7cbdb3b..2983f732dc 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -33,7 +33,7 @@ Below is a list of some of the available keyboard shortcuts. |-----------|------------ |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](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +|g p | Go to the **Pull requests** tab. For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} |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](/articles/about-wikis)." @@ -159,6 +159,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | 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 fullscreen logs +|esc | Exit fullscreen logs {% endif %} diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/pt-BR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index e9146ff379..7bb20ffa0b 100644 --- a/translations/pt-BR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/pt-BR/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,7 +45,7 @@ versions: 7. No topo da página Quick Setup (Configuração rápida) do repositório do {% data variables.product.product_name %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remote. ![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](/articles/adding-a-remote) onde será feito push do seu repositório local. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -83,7 +83,7 @@ versions: 7. No topo da página Quick Setup (Configuração rápida) do repositório do {% data variables.product.product_name %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remote. ![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](/articles/adding-a-remote) onde será feito push do seu repositório local. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -121,7 +121,7 @@ versions: 7. No topo da página Quick Setup (Configuração rápida) do repositório do {% data variables.product.product_name %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remote. ![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](/articles/adding-a-remote) onde será feito push do seu repositório local. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md index 357a797e84..13a0e1246f 100644 --- a/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -1,6 +1,6 @@ --- -title: Deleting files in a repository -intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +title: Excluir arquivos em um repositório +intro: 'Você pode excluir um arquivo individual{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ou um diretório inteiro{% endif %} no seu repositório em {% data variables.product.product_name %}.' redirect_from: - /articles/deleting-files - /github/managing-files-in-a-repository/deleting-files @@ -9,18 +9,18 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +permissions: As pessoas com permissões de gravação podem excluir arquivos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ou diretórios{% endif %} em um repositório. --- -### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion +### Sobre a exclusão de arquivo{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} e diretório{% endif %} -You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. +É possível excluir um arquivo individual no repositório{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ou um diretório inteiro, incluindo todos os arquivos no diretório{% endif %}. -If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". +Se você tentar excluir um arquivo{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ou diretório{% endif %} em um repositório no qual você não tem permissões de gravação, faremos uma bifurcação do projeto para a sua conta de usuário e iremos ajudá-lo a enviar um pull request para o repositório original depois de fazer commit da sua alteração. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". -If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. Para obter mais informações, consulte "[Remover dados confidenciais do repositório](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". +Se o arquivo{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ou diretório{% endif %} que você excluiu contém dados cnfidenciais, os dados ainda estarão disponíveis no histórico Git do repositório. Para remover completamente o arquivo de {% data variables.product.product_name %}, você deve remover o arquivo do histórico do seu repositório. Para obter mais informações, consulte "[Remover dados confidenciais do repositório](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". -### Deleting a file +### Excluir um arquivo 1. Navegue até o arquivo no repositório que deseja excluir. 2. Na parte superior do arquivo, clique @@ -31,11 +31,11 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_ {% data reusables.files.propose_file_change %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Deleting a directory +### Excluir um diretório -1. Browse to the directory in your repository that you want to delete. -1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) -1. Review the files you will delete. +1. Acesse o diretório no seu repositório que deseja excluir. +1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Excluir diretório**. ![Botão para excluir um diretório](/assets/images/help/repository/delete-directory-button.png) +1. Revise os arquivos que você excluirá. {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/index.md b/translations/pt-BR/content/github/managing-files-in-a-repository/index.md index d7b9a300d9..1bdba524cf 100644 --- a/translations/pt-BR/content/github/managing-files-in-a-repository/index.md +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/index.md @@ -21,7 +21,7 @@ versions: {% link_in_list /editing-files-in-your-repository %} {% link_in_list /editing-files-in-another-users-repository %} {% link_in_list /tracking-changes-in-a-file %} - {% link_in_list /deleting-files %} + {% link_in_list /deleting-files-in-a-repository %} {% link_in_list /renaming-a-file %} {% link_in_list /getting-permanent-links-to-files %} {% topic_link_in_list /managing-files-using-the-command-line %} diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md index 6cd7ac646d..4142ebdd6a 100644 --- a/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### Sobre a navegação do código no {% data variables.product.prodname_dotcom %} -As funções de navegar por código usam a biblioteca de código aberto [`semântica`](https://github.com/github/semantic). As linguagens a seguir são compatíveis: +A navegação por código usa a biblioteca de código aberto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). As linguagens a seguir são compatíveis: - C# - CodeQL - Go diff --git a/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index d2fdab3236..ec015036f9 100644 --- a/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/pt-BR/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -19,7 +19,7 @@ Por exemplo: - Se você fizer push de um arquivo de 500 MB no {% data variables.large_files.product_name_short %}, serão usados 500 MB do armazenamento alocado e nada da largura de banda. Se você fizer uma alteração de 1 byte e fizer push do arquivo novamente, serão usados outros 500 MB do armazenamento e nada a largura de banda, totalizando 1 GB de uso total do armazenamento e zero de largura de banda para esses dois pushes. - Se você baixar um arquivo de 500 MB que é rastreado com o LFS, serão usados 500 MB da largura de banda alocada do proprietário do repositório. Se um colaborador fizer push de uma alteração no arquivo e você fizer pull da nova versão no repositório local, serão usados outros 500 MB de largura de banda, totalizando 1 GB de uso total da largura de banda para esses dois downloads. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Se {% data variables.large_files.product_name_long %} objetos de ({% data variables.large_files.product_name_short %}) estiverem incluídos nos arquivos do código-fonte do seu repositório, os downloads desses arquivos contarão para o uso de banda larga no repositório. Para obter mais informações, consulte " [Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

    diff --git a/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md index f97112a867..4a0f441acb 100644 --- a/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/pt-BR/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -59,5 +59,5 @@ Se houver arquivos no seu repositório com os quais deseja usar o {% data variab ### Leia mais -- "[Colaboração com {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- "[Colaboração com {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - "[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md index 45a9faeff0..14e89de4d9 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-dependabot-security-updates.md @@ -33,3 +33,7 @@ Ao fazer merge de um pull request que contém uma atualização de segurança, o ### Sobre pontuações de compatibilidade O {% data variables.product.prodname_dependabot_security_updates %} pode inclui uma pontuação de compatibilidade para que você saiba se atualizar uma vulnerabilidade pode causar alterações significativas no seu projeto. Estes são calculados a partir de testes de CI em outros repositórios públicos onde a mesma atualização de segurança foi gerada. Uma pontuação de compatibilidade da atualização é a porcentagem de execuções de CI que foram aprovadas durante a atualização entre versões específicas da dependência. + +### Sobre notificações para atualizações de segurança de {% data variables.product.prodname_dependabot %} + +Você pode filtrar suas notificações em {% data variables.product.company_short %} para mostrar as atualizações de segurança de {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". \ No newline at end of file diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md index dce4a99695..c5065ca4a4 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -11,7 +11,7 @@ versions: 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). As informações no gráfico de dependências são usadas pela revisão das dependências e {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". #### Revisão de dependência -Ao verificar as revisões de dependências nos pull requests, você pode evitar a introdução de vulnerabilidades de dependências na sua base de código. Se os pull requests adicionarem uma dependência vulnerável, ou alterarem a dependência a uma versão vulnerável, isso será destacado na revisão de dependências. Você pode alterar a dependência para uma versão alterada antes de realizar o merge do pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +Ao verificar as revisões de dependências nos pull requests, você pode evitar a introdução de vulnerabilidades de dependências na sua base de código. Se os pull requests adicionarem uma dependência vulnerável, ou alterarem a dependência a uma versão vulnerável, isso será destacado na revisão de dependências. Você pode alterar a dependência para uma versão alterada antes de realizar o merge do pull request. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". #### {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dotcom %} pode criar {% data variables.product.prodname_dependabot_alerts %} quando detectar dependências vulneráveis no seu repositório. O alerta é exibido na aba Segurança do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.prodname_dotcom %} também notifica os mantenedores do repositório, de acordo com as suas preferências de notificação. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md index 528e4bfc9a..cc5213d968 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-dependabot-security-updates.md @@ -42,16 +42,18 @@ Se as atualizações de segurança não estiverem habilitadas para o seu reposit ### Gerenciar {% data variables.product.prodname_dependabot_security_updates %} para seus repositórios -Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} em um repositório individual. +Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para um repositório individual (veja abaixo). Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios pertencentes à sua conta de usuário ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". O {% data variables.product.prodname_dependabot_security_updates %} exige configurações específicas do repositório. Para obter mais informações, consulte "[Repositórios compatíveis](#supported-repositories)". +#### Habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para um repositório individual + {% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Acima da lista de alertas, use o menu suspenso e selecione ou desmarque as atualizações de segurança do **{% data variables.product.prodname_dependabot %}**. ![Menu suspenso com a opção de ativar {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) +{% data reusables.repositories.sidebar-settings %} +{% data reusables.repositories.navigate-to-security-and-analysis %} +1. Em "Configurar recursos de segurança e análise" à direita de "atualizações de segurança de {% data variables.product.prodname_dependabot %}", clique em **Habilitar** ou **Desabilitar**. ![Seção "Configurar recursos de segurança e análise" com botão para habilitar {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png) ### Leia mais diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index 1ec7743a2f..c6682299ef 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md @@ -42,7 +42,7 @@ Você pode definir as configurações de notificação para si mesmo ou para sua {% note %} -**Observação:** Você pode filtrar suas notificações da caixa de entrada de {% data variables.product.company_short %} para mostrar {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %}{% else %} alertas de segurança{% endif %}. Para obter mais informações, consulte "[Gerenciar notificações da sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)". +**Observação:** Você filtrar as notificações de {% data variables.product.company_short %} para mostrar os alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}segurança {% endif %} do {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)". {% endnote %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index bb789818c0..e111694a4d 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ Ao publicar uma consultoria de segurança, você notifica a sua comunidade sobre Antes de publicar uma consultoria de segurança, você pode colaborar de forma privada para consertar a vulnerabilidade em uma bifurcação privada temporária. Para obter mais informações, consulte "[Colaborar em uma bifurcação privada temporária para resolver uma vulnerabilidade de segurança](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". +{% warning %} + +**Aviso**: Sempre que possível, você deve adicionar uma versão de correção a uma consultoria de segurança antes de publicá-la. Se você não fizer isso, a sua consultoria será publicado sem uma versão de correção e {% data variables.product.prodname_dependabot %} alertará os seus usuários sobre o problema, sem oferecer qualquer versão segura para a qual atualizar. + +Recomendamos que você tome as seguintes medidas nestas situações diferentes: + +- Se uma versão de correção estiver disponível imediatamente, e você puder, espere para divulgar o problema quando a correção estiver pronta. +- Se uma versão de correção estiver em desenvolvimento mas ainda não disponível, mencione isso no consultor e edite a consultoria mais tarde, após a publicação. +- Se você não está planejando corrigir o problema, tenha isso claro na consultoria para que os usuários não entrem em contato com você para perguntar quando será feita uma correção. Neste caso, é útil incluir as etapas que os usuários podem seguir para mitigar o problema. + +{% endwarning %} + Ao publicar um rascunho de consultoria a partir de um repositório público, todos poderão ver: - A versão atual dos dados da consultoria. diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index c9d9ce7b78..5dda972f78 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -78,13 +78,15 @@ A melhor maneira de resolver este erro é fazer o merge ou fechar alguns dos pul #### {% data variables.product.prodname_dependabot %} não pode resolver seus arquivos de dependência -**Somente atualizações da versão.** Se {% data variables.product.prodname_dependabot %} tentar verificar se referências de dependências precisam ser atualizadas em um repositório, mas não for possível acessar um ou mais arquivos referenciados, você verá a mensagem de erro "{% data variables.product.prodname_dependabot %} não pode resolver seus arquivos de dependência de LANGUAGE". +Se {% data variables.product.prodname_dependabot %} tentar verificar se as referências de dependências precisam ser atualizadas em um repositório, mas não puder acessar um ou mais arquivos referenciados, a operação irá falhar com a mensagem de erro "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." O tipo de erro da API é `git_dependencies_not_reachable`. -{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, {% data variables.product.prodname_dependabot %} não é compatível com dependências privadas {% data variables.product.prodname_dotcom %} para todos os gerenciadores de pacote. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". +Para permitir que {% data variables.product.prodname_dependabot %} atualize as referências de dependências com sucesso, certifique-se de que todas as dependências referenciadas estejam hospedadas em locais acessíveis. + +**Somente atualizações de versão.** {% data reusables.dependabot.private-dependencies-note %} Além disso, {% data variables.product.prodname_dependabot %} não é compatível com dependências privadas de {% data variables.product.prodname_dotcom %} para todos os gerenciadores de pacotes. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)". ### Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente Se você desbloquear {% data variables.product.prodname_dependabot %}, você poderá iniciar manualmente uma nova tentativa de criar um pull request. - **Atualizações de segurança**—exibe o alerta de {% data variables.product.prodname_dependabot %}, que mostra o erro que você corrigiu e clique em **Criar atualização de segurança de {% data variables.product.prodname_dependabot %}**. -- **Atualizações da versão**— exibir o arquivo de log para o manifesto que mostra o erro que você corrigiu e clique em **Verificar se há atualizações**. +- **Atualização de versão**—na aba **Insights** do repositório, clique no **Gráfico de dependência** e, em seguida, clique na aba **Dependabot**. Clique em **Última verificação*há* hora** para ver o arquivo de registro que {% data variables.product.prodname_dependabot %} gerou durante a última verificação de atualizações de versão. Clique em **Verificar atualizações**. diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index 97ab1fd06e..dfb7f5b55f 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -11,6 +11,10 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### Notificações e assinaturas Você pode optar por receber atualizações em curso sobre a atividade específica no {% data variables.product.product_name %} por meio de uma assinatura. As notificações são atualizações que você recebe para atividades específicas que você assinou. @@ -50,7 +54,7 @@ Para cancelar a inscrição de conversas que você se inscreveu automaticamente, ### Personalizando notificações e assinaturas -Você pode optar por visualizar suas notificações através da caixa de entrada de notificações [https://github. um/notificações](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} e no {% data variables.product.prodname_mobile %} aplicativo{% endif %}, através do seu e-mail ou de uma combinação dessas opções. +Você pode optar por visualizar as notificações por meio da caixa de entrada [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} e no aplicativo de {% data variables.product.prodname_mobile %}{% endif %}, por meio do seu e-mail ou alguma combinação dessas opções. Para personalizar os tipos de atualizações que você gostaria de receber e para onde enviar essas atualizações, configure suas configurações de notificação. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". @@ -58,7 +62,7 @@ Para manter suas assinaturas gerenciáveis, revise suas assinaturas e os reposit Para personalizar como você gostaria de receber atualizações de pull requests ou problemas específicos, é possível configurar suas preferências dentro do problema ou da pull request. Para obter mais informações, consulte “[Fazendo triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22"%} Você pode habilitar notificações push no aplicativo {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)". {% endif %} @@ -89,7 +93,7 @@ Em sua caixa de entrada, você também pode fazer triagem de várias notificaç ### Personalizando sua caixa de entrada de notificações -Para se concentrar em um grupo de notificações na sua caixa de entrada em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} ou em {% data variables.product.prodname_mobile %}{% endif %}, você pode criar filtros personalizados. Por exemplo, você pode criar um filtro personalizado para um projeto de código aberto para o qual contribui e somente visualizar notificações para esse repositório em que você é mencionado. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para mais exemplos de como personalizar a triagem de seu fluxo de trabalho, consulte "[Personalizando um fluxo de trabalho para triagem de suas notificações.](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications) +Para se concentrar em um grupo de notificações na sua caixa de entrada em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ou {% data variables.product.prodname_mobile %}{% endif %}, você pode criar filtros personalizados. Por exemplo, você pode criar um filtro personalizado para um projeto de código aberto para o qual contribui e somente visualizar notificações para esse repositório em que você é mencionado. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para mais exemplos de como personalizar a triagem de seu fluxo de trabalho, consulte "[Personalizando um fluxo de trabalho para triagem de suas notificações.](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications) ### Política de retenção de notificações diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 0a07850cfc..3dc882c5df 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -19,15 +19,19 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% 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_name %} nos locais a seguir. - - Caixa de notificações na interface web de {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %} + - Caixa de entrada de notificações na interface web de {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} - A caixa de entrada no {% data variables.product.prodname_mobile %}, que sincroniza com a caixa de entrada em {% data variables.product.product_name %}{% 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_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% 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 em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} e {% data variables.product.prodname_mobile %}{% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% 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 %} @@ -35,7 +39,7 @@ Você pode receber notificações de atividades em {% data variables.product.pro #### Benefícios da caixa de entrada de notificações -A caixa de entrada de notificações em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %} inclui opções de triagem projetadas especificamente para o seu fluxo de notificações de {% data variables.product.product_name %} e inclui opções para: +A caixa de entrada de notificações em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} e {% data variables.product.prodname_mobile %}{% endif %} inclui opções de triagem projetadas especificamente para o seu fluxo de notificações de {% data variables.product.product_name %} 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`. @@ -45,7 +49,7 @@ A caixa de entrada de notificações em {% data variables.product.product_name % - 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 -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} Além disso, a caixa de entrada de notificações em {% data variables.product.prodname_mobile %} permite que você faça triagem de notificações no modo escuro e receba notificações push para menções diretas. Para obter mais informações, consulte "[Habilitar notificações push com GitHub para celular](#enabling-push-notifications-with-github-for-mobile)" ou "[GitHub para celular](/github/getting-started-with-github/github-for-mobile)". {% endif %} @@ -77,7 +81,7 @@ Você pode configurar as notificações para um repositório na página do repos #### 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 em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_mobile %}{% endif %}. +Para conversas que você está inspecionando ou das quais você está participando, você pode escolher se deseja receber notificações por e-mail ou por meio da caixa de entrada em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} 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) @@ -85,7 +89,7 @@ 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 permite assistir ou participar de notificações da web{% if currentVersion == "free-pro-team@latest" %} e móvel{% endif %}, sua caixa de entrada de notificações não terá nenhuma atualização. +Se você não habilitar notificações de inspeção ou participação para a web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} e dispositivos móveis{% endif %}, a sua caixa de entrada de notificações não terá nenhuma atualização. ### Personalizando suas notificações por e-mail @@ -129,7 +133,8 @@ As notificações de e-mail do {% data variables.product.product_name %} contêm | Campo `To` | Este campo conecta-se diretamente à corrente.{% if currentVersion != "github-ae@latest" %} 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.
    • '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.
      • {% if currentVersion != "github-ae@latest" %}
    • '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 %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| 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 %} +| 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 @@ -197,13 +202,15 @@ Escolha como você deseja receber atualizações de execução de fluxo de traba {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} ### Habilitando notificações push com {% data variables.product.prodname_mobile %} Quando você instalar {% data variables.product.prodname_mobile %}, você será automaticamente incluído em notificações da web. Você poderá então ativar notificações push para menções diretas no app. Você só pode receber notificações de pushes para repositórios no {% data variables.product.prodname_mobile %} neste momento. +{% data reusables.mobile.push-notifications-on-ghes %} + #### Habilitar notificações de push com {% data variables.product.prodname_ios %} 1. Acima de "Home", clique na foto do seu perfil. @@ -211,9 +218,11 @@ Você só pode receber notificações de pushes para repositórios no {% data va 3. Para atualizar suas configurações de notificação, clique em **Notificações push**. 4. Para ativar as notificações push para menções diretas, use a alternância **Menções Diretas**. +{% if currentVersion == "free-pro-team@latest" %} #### Habilitar notificações de push com {% data variables.product.prodname_android %} 1. Acima de "Home", clique na foto do seu perfil. 2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. ![Ícone de configurações para GitHub para iOS](/assets/images/help/mobile/android-settings-icon.png) 3. Para ativar as notificações push para menções diretas, use a alternância **Menções Diretas**. {% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index f8fda0941b..5e5c8949b4 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- title: Managing notifications from your inbox -intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}.' +intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -10,9 +10,13 @@ versions: github-ae: '*' --- +{% if enterpriseServerVersions contains currentVersion %} +{% data reusables.mobile.ghes-release-phase %} +{% endif %} + ### About your inbox -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} {% 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 %} @@ -86,31 +90,16 @@ Custom filters do not currently support: ### Supported queries for custom filters -There are three types of filters that you can use: +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:` + - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -To add a `repo:` filter, you must include the owner of the repository in the query. For example, `repo:atom/atom` represents the Atom repository owned by the Atom organization. +#### Supported `repo:` queries -#### Supported `reason:` queries - -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)." - -| 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.{% if currentVersion != "github-ae@latest" %} -| `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. +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. #### Supported `is:` queries @@ -137,3 +126,55 @@ You can also use the `is:` query to describe how the notification was triaged. - `is:done` - `is:unread` - `is:read` + +#### Supported `reason:` queries + +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)." + +| 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.{% if currentVersion != "github-ae@latest" %} +| `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. + +{% if currentVersion == "free-pro-team@latest" %} +#### Supported `author:` queries + +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`. + +#### Supported `org:` queries + +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. + +For example, to see notifications from the octo-org organization, use `org:octo-org`. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +### {% data variables.product.prodname_dependabot %} custom filters + +{% if currentVersion == "free-pro-team@latest" %} +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. + +For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% endif %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. + +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/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 3fdbc3e4d9..84b67758f6 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -39,7 +39,7 @@ Ao cancelar a assinatura de notificações em sua caixa de entrada, elas desapar {% data reusables.notifications.access_notifications %} 1. Na caixa de entrada de notificações, selecione as notificações das quais você deseja cancelar sua assinatura. -2. Use o menu suspenso **selecionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para clicar em **Cancelar inscrição.** ![Opção de cancelamento de assinatura da caixa de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Use o menu suspenso **selecionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para clicar em **Cancelar inscrição.** ![Cancele a assinatura na caixa de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### Cancelar assinatura de notificações na página de assinaturas @@ -64,4 +64,4 @@ Quando você deixa de inspecionar um repositório, você cancela sua assinatura - deixar de inspecionar um repositório - ignorar todas as notificações de um repositório - personalizar os tipos de eventos para os quais você recebe notificações (problemas, pull requests, versões ou discussões, se habilitado) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index d01efdc56d..b0eb92f628 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -36,7 +36,7 @@ Para ter uma visão geral das assinaturas de seu repositório, consulte "[Revisa {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. 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. +**Dica:** Você pode selecionar os tipos de evento a serem notificados utilizando a opção **Personalizar** na lista suspensa **Inspecionar/Cancelar inspeção** na sua [página](https://github.com/watching) ou em qualquer página de repositório em {% data variables.product.prodname_dotcom_the_website %}. 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. {% endtip %} {% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md index 6351ff3088..bda3322de9 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- title: Alterar a visibilidade dos quadros de projeto -intro: 'Como proprietário da organização ou administrador do quadro de projeto, você pode tornar um quadro de projeto público ou privado.' +intro: 'Como proprietário ou administrador de um projeto da organização, você pode tornar um quadro de projeto {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} ou privado.' redirect_from: - /articles/changing-project-board-visibility versions: @@ -13,11 +13,14 @@ versions: {% tip %} -**Dica:** quando você torna seu quadro de projeto público, os integrantes da organização recebem acesso de leitura por padrão. Você pode conceder a integrantes específicos da organização permissões de gravação ou de administrador dando às equipes acesso ao quadro de projeto em que eles estão ativos ou adicionando-os ao quadro de projeto como um colaborador. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)". +**Dica:** Ao tornar seu quadro de projeto {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}, os integrantes da organização recebem acesso de leitura por padrão. Você pode conceder a integrantes específicos da organização permissões de gravação ou de administrador dando às equipes acesso ao quadro de projeto em que eles estão ativos ou adicionando-os ao quadro de projeto como um colaborador. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)". {% endtip %} -1. Navegue até o quadro de projeto que deseja tornar público ou privado. +1. Acesse o quadro de projeto que você deseja criar + +{% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} ou privado. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -4. Em "Visibility" (Visibilidade), selecione **Public** (Público) ou **Private** (Privado). Em seguida, clique em **Save** (Salvar). ![Botões de opção Public (Público) e Private (Privado)](/assets/images/help/projects/project-board-visibility-options.png) +{% data reusables.project-management.choose-visibility %} +1. Clique em **Salvar**. diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md index cc8267c704..1e595a54e1 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/copying-a-project-board.md @@ -22,5 +22,5 @@ A automação de um quadro de projeto também é habilitada por padrão. Para ob 5. Se preferir, em "Project board name" (Nome do quadro de projeto), digite o nome do quadro de projeto copiado. ![Campo para digitar um nome para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-name.png) 6. Se desejar, em "Description" (Descrição), digite uma descrição do quadro de projeto copiado que outras pessoas verão. ![Campo para digitar uma descrição para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-description.png) 7. Se desejar, em "Automation settings" (Configurações de automação), selecione se deseja copiar os fluxos de trabalho automáticos configurados. Essa opção é habilitada por padrão. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards/)". ![Configurações de seleção de automação para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. Se você estiver copiando um quadro de projeto pertencente à organização, em "Visibility" (Visibilidade), selecione se deseja que o quadro de projeto copiado seja privado ou público. ![Configurações de seleção de visibilidade para o quadro de projeto copiado](/assets/images/help/projects/copied-project-board-visibility-settings.png) +{% data reusables.project-management.choose-visibility %} 9. Clique em **Copy project** (Copiar projeto). ![Botão Confirm Copy (Confirmar cópia)](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md index c51ec25f2e..4d9ed90420 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/creating-a-project-board.md @@ -31,6 +31,7 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} @@ -50,6 +51,7 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md b/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md index 0d30cc38e1..3d837fcd29 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/filtering-pull-requests-by-review-status.md @@ -11,7 +11,7 @@ versions: Você pode filtrar uma lista de pull requests do repositório para encontrar: - Pull requests que ainda não foram [revisadas](/articles/about-pull-request-reviews) -- Pull requests que [necessitam de revisão](/articles/about-required-reviews-for-pull-requests) antes de serem mescladas +- Pull requests que [necessitam de revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de serem mescladas - Pull requests que um revisor aprovou - Pull requests nas quais um revisor solicitou alterações - Pull requests que você revisou diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 28a03999f7..64920e0815 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -1,6 +1,6 @@ --- -title: Transferir um problema para outro repositório -intro: 'Para mover um problema para um repositório mais adequado, você pode transferir problemas abertos para outros repositórios.' +title: Transferring an issue to another repository +intro: 'To move an issue to a better fitting repository, you can transfer open issues to other repositories.' redirect_from: - /articles/transferring-an-issue-to-another-repository versions: @@ -9,25 +9,28 @@ versions: github-ae: '*' --- -Para transferir um problema aberto para outro repositório, é preciso ter permissões de gravação no repositório em que o problema está e no repositório para onde você está transferindo o problema. Para obter mais informações, consulte "[Níveis de permissão do repositório para organizações](/articles/repository-permission-levels-for-an-organization)". +To transfer an open issue to another repository, you must have write permissions on the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." -Você só pode transferir problemas entre repositórios pertencentes à mesma conta de usuário ou de organização.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Você não pode transferir um problema de um repositório privado para um repositório público.{% endif %} +You can only transfer issues between repositories owned by the same user or organization account. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} -Quando você transfere um problema, os comentários e responsáveis são mantidos. As etiquetas e os marcos do problema não são retidos. Esse problema permanecerá em qualquer quadro de projeto pertencente ao usuário ou à organização e será removido dos quadros de projeto de todos os repositórios. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". +When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)." -As pessoas ou equipes mencionadas no problema receberão uma notificação informando que o problema foi transferido para um novo repositório. O URL original redirecionará para o novo URL do problema. As pessoas que não tenham permissões de leitura no novo repositório verão um banner informando que o problema foi transferido para um novo repositório ao qual elas não têm acesso. +People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access. -### Transferir um problema aberto para outro repositório +### Transferring an open issue to another repository {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} -3. Na lista de problemas, clique no problema que deseja transferir. -4. Na barra lateral direita, clique em **Transfer issue** (Transferir problema). ![Botão para transferir problema](/assets/images/help/repository/transfer-issue.png) -5. Use o menu **Choose a repository** (Escolher um repositório) e selecione o repositório para o qual deseja transferir o problema. ![Seleção em Choose a repository (Escolher um repositório)](/assets/images/help/repository/choose-a-repository.png) -6. Clique em **Transfer issue** (Transferir problema). ![Botão Transfer issue (Transferir problema)](/assets/images/help/repository/transfer-issue-button.png) +3. In the list of issues, click the issue you'd like to transfer. +4. In the right sidebar, click **Transfer issue**. +![Button to transfer issue](/assets/images/help/repository/transfer-issue.png) +5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to. +![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png) +6. Click **Transfer issue**. +![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png) -### Leia mais +### Further reading -- "[Sobre problemas](/articles/about-issues)" -- "[Revisar o log de segurança](/articles/reviewing-your-security-log)" -- "[Revisar o log de auditoria da organização](/articles/reviewing-the-audit-log-for-your-organization)" +- "[About issues](/articles/about-issues)" +- "[Reviewing your security log](/articles/reviewing-your-security-log)" +- "[Reviewing the audit log for your organization](/articles/reviewing-the-audit-log-for-your-organization)" diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index d71d54c91b..cb6f4cdaf3 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -36,7 +36,7 @@ Para problemas, você também pode usar a busca para: Para pull requests, você também pode usar a pesquisa para: - Filtrar pull requests de [rascunho](/articles/about-pull-requests#draft-pull-requests): `is:draft` - Filtrar pull requests que não tenham sido [revisadas](/articles/about-pull-request-reviews) yet: `state:open type:pr review:none` -- Filtrar pull requests que [exijam uma revisão](/articles/about-required-reviews-for-pull-requests) para que o merge possa ser feito: `state:open type:pr review:required` +- Filtrar pull requests que [exijam uma revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) para que o merge possa ser feito: `state:open type:pr review:required` - Filtrar pull requests que tenham sido aprovadas por um revisor: `state:open type:pr review:approved` - Filtrar pull requests nas quais um revisor tenha solicitado alterações: `state:open type:pr review:changes_requested` - Filtrar pull requests por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` diff --git a/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index ae97d3bb36..78e9d37fc9 100644 --- a/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,7 +25,8 @@ As notificações de e-mail do {% data variables.product.product_name %} contêm | Campo `To` | Esse campo conecta-se diretamente ao thread. Se você responder ao e-mail, será adicionado um novo comentário à conversa. | | 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.
    • '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.
    • 'security_alert': o {% data variables.product.prodname_dotcom %} detectou uma vulnerabilidade em um repositório para o qual você recebe alertas de segurança.
    • '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 %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| 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 %} +| 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 %} ### Leia mais diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md index 48ccd45b3c..81cbfaf06c 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-commits.md @@ -51,7 +51,7 @@ Use os qualificadores `author-date` e `committer-date` para identificar commits | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) identifica os commits criados antes de 01-01-2016. | -| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A<2016-01-01&type=Commits) identifica os commits feitos depois de 01-01-2016. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) corresponde a commits confirmados após 2016-01-01. | ### Filtrar commits de merge diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md index 1ce7d37a55..d8455618e0 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md @@ -60,50 +60,50 @@ O qualificador `commenter` encontra discussões que contêm um comentário de um Você pode usar o qualificador `envolve` para encontrar discussões que envolvam um determinado usuário. O qualificador retorna discussões que ou foram criadas por um determinado usuário, menciona o usuário, ou contém comentários feitos pelo usuário. O qualificador `involves` é um operador lógico OU entre os qualificadores `autor`, `mentions` e `commenter` para um único usuário. -| Qualifier | Exemplo | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| involves:USERNAME | **[envolves:becca envolve:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** corresponde às discussões em que @becca ou @octocat estão envolvidos. | -| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[envolves:becca envolve:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** corresponde às discussões em que @becca ou @octocat estão envolvidos. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) corresponde a discussões @becca que não contêm a palavra "beta" no texto. | ### Pesquisar por número de comentários -You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +Você pode usar o qualificador `comments` com os qualificadores maior que, menor que e intervalo para pesquisar pelo número de comentários. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". -| Qualifier | Exemplo | -|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | +| Qualifier | Exemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) corresponde a discussões com mais de 100 comentários. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) corresponde a discussões com comentários que variam de 500 a 1.000. | ### Pesquisar por número de interações -You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +Você pode filtrar discussões pelo número de interações com o qualificador de `interações` com os qualificadores maior que, menor que e intervalo. A contagem das interações é o número de reações e comentários em uma discussão. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". -| Qualifier | Exemplo | -|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | +| Qualifier | Exemplo | +|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) corresponde a discussões com mais de 2.000 interações. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) corresponde a discussões com interações que variam de 500 a 1.000. | ### Pesquisar por número de reações -You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +Você pode filtrar discussões pelo número de reações usando o qualificador de `reações`, junto os qualificadores maior que, menor que e de intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". -| Qualifier | Exemplo | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) corresponde a discussões com mais de 500 reações. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) corresponde a discussões com 500 a 1.000 reações. | -### Search by when a discussion was created or last updated +### Procurar por quando uma discussão foi criada ou quando foi atualizada por último -You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. +Você pode filtrar discussões com base no tempo de criação, ou quando a discussão foi atualizada pela última vez. Para a criação de discussões, você pode usar o qualificador `criado`; para saber quando uma discussão foi atualizada pela última vez, use o qualificador `atualizada`. -Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Ambos os qualificadores tomam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Exemplo | -|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | -| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | +| Qualifier | Exemplo | +|:-------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) corresponde a discussões que foram criadas após 15 de novembro de 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) corresponde a discussões com a palavra "weird" no texto que foram atualizadas após dezembro de 2020. | ### Leia mais diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index d057cc7335..ae6a21d5c2 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ Você pode restringir seus resultados para apenas incluir problemas vinculados a | `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) corresponde a problemas abertos no re repositório `desktop/desktop` vinculados a um pull request por uma referência fechada. | | `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) corresponde a pull requests fechados no repositório `desktop/desktop` vinculados a um problema que o pull request pode ter fechado. | | `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) corresponde a problemas abertos no repositório `desktop/desktop` que não estão vinculados a um pull request por uma referência fechada. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) corresponde a pull requests abertos no repositório `desktop/desktop` que não estão vinculados a um problema que o pull request pode fechar. |{% endif %} +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) corresponde a pull requests abertos no repositório `desktop/desktop` que não estão vinculados a um problema que o pull request pode fechar. +{% endif %} ### Pesquisar por etiqueta diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 29c00b76b4..95518b802d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### Descontos para contas pessoais -Além de repositórios públicos e privados ilimitados para alunos e docentes com o {% data variables.product.prodname_free_user %}, os alunos confirmados podem se inscrever no {% data variables.product.prodname_student_pack %} para receber outros benefícios de parceiros do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Aplicar a um pacote de desenvolvedor para estudante](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)". +Além de repositórios públicos e privados ilimitados para alunos e docentes com o {% data variables.product.prodname_free_user %}, os alunos confirmados podem se inscrever no {% data variables.product.prodname_student_pack %} para receber outros benefícios de parceiros do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Aplicar a um pacote de desenvolvedor para estudante](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)". ### Descontos para escolas e universidades -Os docentes acadêmicos confirmados podem se inscrever na {% data variables.product.prodname_team %} para atividades de ensino ou pesquisa acadêmica. Para obter mais informações, consulte "[Usar {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)". Também é possível solicitar brindes de material educacional para os alunos. Para obter mais informações, visite [{% data variables.product.prodname_education %}](https://education.github.com/). +Os docentes acadêmicos confirmados podem se inscrever na {% data variables.product.prodname_team %} para atividades de ensino ou pesquisa acadêmica. Para obter mais informações, consulte "[Usar {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)". Também é possível solicitar brindes de material educacional para os alunos. Para obter mais informações, visite [{% data variables.product.prodname_education %}](https://education.github.com/). ### Descontos para organizações sem fins lucrativos e bibliotecas diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md index 93e44adb09..9deed8c3fd 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md @@ -14,7 +14,7 @@ versions: Depois de configurar o SAML SSO, os integrantes da sua organização de {% data variables.product.prodname_dotcom %} continuarão a fazer login em suas contas de usuário no {% data variables.product.prodname_dotcom %}. Quando um membro acessa recursos dentro de sua organização que usa o SAML SSO, o {% data variables.product.prodname_dotcom %} redireciona o integrante para o seu IdP para efetuar a autenticação. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. -Os proprietários das empresas também podem aplicar SAML SSO para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% data reusables.saml.outside-collaborators-exemption %} @@ -32,6 +32,8 @@ Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um n Os integrantes da organização também devem ter uma sessão de SAML ativa para autorizar um {% data variables.product.prodname_oauth_app %}. Você pode optar por não participar deste requisito entrando em contato com {% data variables.contact.contact_support %}. {% data variables.product.product_name %} não recomenda a exclusão deste requisito, o que irá expor sua organização a um maior risco de aquisições de conta e perda potencial de dados. +{% data reusables.saml.saml-single-logout-not-supported %} + ### Serviços SAML compatíveis {% data reusables.saml.saml-supported-idps %} @@ -42,12 +44,12 @@ Alguns IdPs suportam acesso de provisionamento a uma organização do {% data va Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/rest/reference/orgs#add-or-update-organization-membership)". -{% data reusables.organizations.team-synchronization %} - Para provisionar novos usuários sem o convite de um proprietário da organização, você pode usar a URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, substituindo _ORGANIZATION_ pelo nome da sua organização. Por exemplo, é possível configurar o IdP para que qualquer pessoa que tenha acesso possa clicar em um link no painel do IdP para ingressar na sua organização do {% data variables.product.prodname_dotcom %}. Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". +{% data reusables.organizations.team-synchronization %} + {% data reusables.saml.saml-single-logout-not-supported %} ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md index 8205802885..417532a8b1 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/about-scim.md @@ -17,7 +17,7 @@ Estes provedores de identidade são compatíveis com a API de SCIM de {% data va - Okta - OneLogin -{% data reusables.scim.enterprise-account-scim %} Para obter mais informações, consulte "[Aplicando configurações de segurança na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)". +{% data reusables.scim.enterprise-account-scim %} Para obter mais informações, consulte "[Sobre o provisionamento do usuário para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md index db435ffb35..e05174b88c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} @@ -113,7 +113,6 @@ versions: {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} - {% link_in_list /managing-secret-scanning-for-your-organization %} {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} {% link_in_list /restricting-email-notifications-to-an-approved-domain %} {% link_in_list /reviewing-the-audit-log-for-your-organization %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index c3df4b4ca2..3e085cf03d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -2,13 +2,17 @@ title: Gerenciar as configurações de segurança e análise para a sua organização intro: 'Você pode controlar recursos que protegem e analisam o código nos projetos da sua organização no {% data variables.product.prodname_dotcom %}.' permissions: Os proprietários da organização podem gerenciar as configurações de segurança e análise de repositórios na organização. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- ### Sobre a gestão de configurações de segurança e análise -O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. +O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. {% if currentVersion == "free-pro-team@latest" %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, você também poderá gerenciar o acesso a essas funcionalidades. {% data reusables.advanced-security.more-info-ghas %}{% endif %} + {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} @@ -19,35 +23,80 @@ O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os reposit {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -A página exibida permite que você habilite ou desabilite os recursos de segurança e análise dos repositórios na sua organização. +A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização. {% if currentVersion == "free-pro-team@latest" %}Se a sua organização ou a empresa à qual pertence tem uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. + +![Funcionalidades de {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) +{% endif %} ### Habilitar ou desabilitar um recurso para todos os repositórios existentes -1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -1. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -1. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -1. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) +Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. {% if currentVersion == "free-pro-team@latest" %}O impacto de suas alterações nos repositórios da organização é determinado pela visibilidade: -### Habilitar ou desabilitar um recurso para todos os novos repositórios quando forem adicionados +- **Gráfico de dependências** - Suas alterações afetam apenas repositórios privados porque a funcionalidade está sempre habilitada para repositórios públicos. +- **{% data variables.product.prodname_dependabot_alerts %}** - As suas alterações afetam todos os repositórios. +- **{% data variables.product.prodname_dependabot_security_updates %}** - As suas alterações afetam todos os repositórios. +- **{% data variables.product.prodname_GH_advanced_security %}** - As suas alterações afetam apenas repositórios privados, porque {% data variables.product.prodname_GH_advanced_security %} e os as funcionalidades relacionadas estão sempre habilitadas para repositórios públicos. +- **{% data variables.product.prodname_secret_scanning_caps %}** - As suas alterações afetam apenas repositórios privados em que {% data variables.product.prodname_GH_advanced_security %} também está habilitado. {% data variables.product.prodname_secret_scanning_caps %} está sempre habilitado para repositórios públicos.{% endif %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". -1. Em "Configurar recursos de segurança e análise", à direita do recurso, habilite ou desabilite o recurso por padrão para novos repositórios na sua organização. ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) +1. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. + {% if currentVersion == "free-pro-team@latest" %} + ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) + {% endif %} +2. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. + {% if currentVersion == "free-pro-team@latest" %} + ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) + {% endif %} +1. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. + {% if currentVersion == "free-pro-team@latest" %} + ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) + {% endif %} + +### Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados + +1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". +1. Em "Configurar funcionalidades de segurança e análise", à direita da funcionalidade, habilite ou desabilite a funcionalidade por padrão para novos repositórios +{% if currentVersion == "free-pro-team@latest" %}, ou todos os novos repositórios privados,{% endif %} na sua organização. + {% if currentVersion == "free-pro-team@latest" %} + ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) + {% endif %} + {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) + {% endif %} + + {% data reusables.advanced-security.note-org-enable-uses-seats %} + +{% if currentVersion == "free-pro-team@latest" %} ### Permitir que o Dependabot acesse repositórios privados -{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. Para fazer isso, {% data variables.product.prodname_dependabot %} deve ter acesso aos arquivos de dependência de destino. Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências localizadas em repositórios privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório. Para obter mais informações, incluindo detalhes das limitações para o suporte de dependências privadas, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". +{% data reusables.dependabot.beta-note %} + +{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. Para fazer isso, {% data variables.product.prodname_dependabot %} deve ter acesso a todos os arquivos de dependência de destino. Normalmente, atualizações da versão irão falhar se uma ou mais dependências forem inacessíveis. + +Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências localizadas em repositórios privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório. Para obter mais informações, incluindo detalhes das limitações para o suporte de dependências privadas, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates)". 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". 1. Na seção "acesso ao repositório de {% data variables.product.prodname_dependabot %}" clique no botão de configurações **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) Uma lista é exibida mostrando todos os repositórios privados da sua organização. ![A lista de repositórios](/assets/images/help/organizations/repositories-dialog.png) 1. Selecione os repositórios que {% data variables.product.prodname_dependabot %} pode acessar. 1. Clique em **Selecionar repositórios**. - +{% endif %} ### Leia mais -{% if currentVersion == "free-pro-team@latest" %}- "[Sobre proteger o seu repositório](/github/administering-a-repository/about-securing-your-repository)" -- "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)" -- "[Manter suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" -{% endif %} +- "[Sobre proteger seu repositório](/github/administering-a-repository/about-securing-your-repository)" +- "[Sobre a varredura de segredo](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Manter suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} - "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" - "[Gerenciar vulnerabilidades nas dependências do seu projeto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..1093f8ea24 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Gerenciar a publicação dos sites do GitHub Pages para a sua organização +intro: 'Você pode controlar se os integrantes da organização podem publicar sites de {% data variables.product.prodname_pages %} a partir de repositórios na organização{% if currentVersion == "free-pro-team@latest" %} e restringir as visibilidades que os integrantes podem escolher para os sites{% endif %}.' +permissions: 'Os proprietários da organização podem gerenciar a publicação de sites de {% data variables.product.prodname_pages %} a partir de repositórios na organização.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization +--- + +{% if currentVersion == "free-pro-team@latest" %} +Se a sua organização usar +{% data variables.product.prodname_ghe_cloud %}, você poderá optar por permitir que os integrantes da organização criem sites publicados publicadamente, privadamente, ambos ou nenhum. Caso contrário, você pode optar por permitir ou negar a publicação pública. Para obter mais informações sobre controle de acesso para sites de {% data variables.product.prodname_pages %}, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% endif %} + +Se você não permitir a publicação de sites de {% data variables.product.prodname_pages %}, todos os sites publicados permanecerão publicados. Você pode remover manualmente a publicação do site. Para obter mais informações, consulte "[Cancelar a publicação de um site do {% data variables.product.prodname_pages %}](/github/working-with-github-pages/unpublishing-a-github-pages-site)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Em "Criação de páginas", selecione as visibilidades que você deseja permitir e desmarque as visibilidades que você não deseja permitir. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Em "Criação de páginas", marque ou desmarque **Permitir que os integrantes publiquem sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Clique em **Salvar**. + +### Leia mais + +- "[Sobre o {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 4f4cd7136b..d0bb5ea65f 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ Os integrantes da organização podem ter funções de *proprietário*{% if curr {% if currentVersion == "free-pro-team@latest" %} -| Ação da organização | Proprietários | Integrantes | Gerentes de cobrança | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:-----------:|:--------------------------------------------------:| -| Criar repositórios (consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)" para detalhes) | **X** | **X** | | -| Visualizar e editar informações de cobrança | **X** | | **X** | -| Convidar pessoas para integrar a organização | **X** | | | -| Editar e cancelar convites para integrar a organização | **X** | | | -| Remover integrantes da organização | **X** | | | -| Restabelecer ex-integrantes da organização | **X** | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | -| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | | | -| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | -| Adicionar colaboradores em **todos os repositórios** | **X** | | | -| Acessar o log de auditoria da organização | **X** | | | -| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes) | **X** | | | -| Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes) | **X** | | | -| Restringir notificações de e-mail a domínios verificados (consulte "[Restringir notificações de e-mail para um domínio aprovado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" para obter informações) | **X** | | | -| Excluir **todas as equipes** | **X** | | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | -| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | | -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | -| Ver todos os integrantes e equipes da organização | **X** | **X** | | -| @mencionar qualquer equipe visível | **X** | **X** | | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | | -| Visualizar as informações da organização (consulte "[Visualizar informações da organização](/articles/viewing-insights-for-your-organization)" para detalhes) | **X** | **X** | | -| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | **X** | | -| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | | | -| Editar e excluir discussões de equipe em **todas as equipes** (consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments)" para detalhes) | **X** | | | -| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | | -| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} -| Gerenciar a visualização de informações de dependência da organização (consulte "[Alterar a visibilidade das informações de dependência da organização](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para detalhes) | **X** | | |{% endif %} -| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | | -| Patrocinar contas e gerenciar os patrocínios da organização (Consulte "[Patrocinar contribuidoresde código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para mais detalhes) | **X** | **X** | | -| Gerenciar atualizações de e-mail de contas patrocinadas (consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" para obter detalhes) | **X** | | | -| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obter mais detalhes) | **X** | | | -| Desabilitar a publicação de sites do {% data variables.product.prodname_pages %} em repositórios na organização (consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para obter informações) | **X** | | | -| Gerenciar as configurações de segurança e análise (consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" para obter mais informações) | **X** | | | -| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | -| [Gerenciar o acesso de SAML de um usuário à sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | -| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | | -| Transferir repósitórios | **X** | | | -| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | -| Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | |{% if currentVersion != "github-ae@latest" %} -| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | -| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | |{% endif %} -| [Gerenciar a política de bifurcação](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Limitar a atividade em repositórios públicos na organização](/articles/limiting-interactions-in-your-organization) | **X** | | | -| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | -| Habilitar sincronização de equipes (consulte "[Gerenciar sincronização de equipe para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" para obter informações) | **X** | | | +| Ação da organização | Proprietários | Integrantes | Gerentes de cobrança | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:-----------:|:--------------------:| +| Criar repositórios (consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)" para detalhes) | **X** | **X** | | +| Visualizar e editar informações de cobrança | **X** | | **X** | +| Convidar pessoas para integrar a organização | **X** | | | +| Editar e cancelar convites para integrar a organização | **X** | | | +| Remover integrantes da organização | **X** | | | +| Restabelecer ex-integrantes da organização | **X** | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | +| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Adicionar colaboradores em **todos os repositórios** | **X** | | | +| Acessar o log de auditoria da organização | **X** | | | +| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes) | **X** | | | +| Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes) | **X** | | | +| Restringir notificações de e-mail a domínios verificados (consulte "[Restringir notificações de e-mail para um domínio aprovado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" para obter informações) | **X** | | | +| Excluir **todas as equipes** | **X** | | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | +| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | | +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | +| Ver todos os integrantes e equipes da organização | **X** | **X** | | +| @mencionar qualquer equipe visível | **X** | **X** | | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | | +| Visualizar as informações da organização (consulte "[Visualizar informações da organização](/articles/viewing-insights-for-your-organization)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | | | +| Editar e excluir discussões de equipe em **todas as equipes** (consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments)" para detalhes) | **X** | | | +| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | | +| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | +| Gerenciar a visualização de informações de dependência da organização (consulte "[Alterar a visibilidade das informações de dependência da organização](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para detalhes) | **X** | | | +| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | | +| Patrocinar contas e gerenciar os patrocínios da organização (Consulte "[Patrocinar contribuidoresde código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para mais detalhes) | **X** | **X** | | +| Gerenciar atualizações de e-mail de contas patrocinadas (consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" para obter detalhes) | **X** | | | +| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obter mais detalhes) | **X** | | | +| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | | | +| Gerenciar as configurações de segurança e análise (consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" para obter mais informações) | **X** | | | +| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [Gerenciar o acesso de SAML de um usuário à sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | | +| Transferir repósitórios | **X** | | | +| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | +| Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | | +| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | +| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | +| [Gerenciar a política de bifurcação](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limitar a atividade em repositórios públicos na organização](/articles/limiting-interactions-in-your-organization) | **X** | | | +| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Habilitar sincronização de equipes (consulte "[Gerenciar sincronização de equipe para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" para obter informações) | **X** | | | {% else %} -| Ação da organização | Proprietários | Integrantes | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:---------------------------------------------------------------------------------------------------:| -| Convidar pessoas para integrar a organização | **X** | | -| Editar e cancelar convites para integrar a organização | **X** | | -| Remover integrantes da organização | **X** | | | -| Restabelecer ex-integrantes da organização | **X** | | | -| Adicionar e remover pessoas de **todas as equipes** | **X** | | -| Promover integrantes da organização a *mantenedor de equipe* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} -| Adicionar colaboradores em **todos os repositórios** | **X** | | -| Acessar o log de auditoria da organização | **X** | | -| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes) | **X** | | | -| Excluir **todas as equipes** | **X** | | -| Excluir a conta da organização, inclusive todos os repositórios | **X** | | -| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | -| Ver todos os integrantes e equipes da organização | **X** | **X** | -| @mencionar qualquer equipe visível | **X** | **X** | -| Poder se tornar um *mantenedor de equipe* | **X** | **X** | -| Transferir repósitórios | **X** | | -| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | -| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | -| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | **X** | | -| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | | | -| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments) | **X** | | | -| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | **X** | -| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | -| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| Desabilitar a publicação de sites do {% data variables.product.prodname_pages %} em repositórios na organização (consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para obter informações) | **X** | | |{% endif %} -| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | -| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | -| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |{% endif %} +| Ação da organização | Proprietários | Integrantes | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------:|:------------------------------------------------------------------------------------------------:| +| Convidar pessoas para integrar a organização | **X** | | +| Editar e cancelar convites para integrar a organização | **X** | | +| Remover integrantes da organização | **X** | | | +| Restabelecer ex-integrantes da organização | **X** | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Adicionar colaboradores em **todos os repositórios** | **X** | | +| Acessar o log de auditoria da organização | **X** | | +| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes) | **X** | | | +| Excluir **todas as equipes** | **X** | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | +| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | +| Ver todos os integrantes e equipes da organização | **X** | **X** | +| @mencionar qualquer equipe visível | **X** | **X** | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | +| Transferir repósitórios | **X** | | +| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | +| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/articles/about-team-discussions)" para detalhes) | **X** | | | +| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments)) | **X** | | | +| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/articles/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | **X** | +| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | +| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | +{% endif %} +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} {% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md index cf3176d343..0c6bc970a5 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md @@ -30,7 +30,7 @@ Por exemplo, se um proprietário da organização concedeu a todos os integrante ### Visibilidade do quadro de projeto -{% data reusables.project-management.project-board-visibility %} Você pode alterar a visibilidade do quadro de projeto de privada para pública e vice-versa. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". +{% data reusables.project-management.project-board-visibility %} Você pode alterar a visibilidade do quadro de projeto de privado para {% if currentVersion == "github-ae@latest" %}interno{% else %}public{% endif %} e novamente para privado. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index b02423a034..f1116cda49 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: Níveis de permissão do repositório da organização intro: 'Você pode personalizar o acesso a cada repositório da organização com níveis granulares de permissão, fornecendo aos usuários o acesso aos recursos e às tarefas que eles precisam.' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,7 +43,14 @@ Além de gerenciar as configurações da organização, os proprietários da org {% endwarning %} ### Acesso ao repositório de cada nível de permissão +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} +**Observação:** As permissões de repositório necessárias para usar funcionalidades de segurança estão listadas em "[Requisitos de permissões para recursos de segurança](#permission-requirements-for-security-features)" abaixo. + +{% endnote %} +| +{% endif %} | Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| | Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | @@ -55,13 +63,16 @@ Além de gerenciar as configurações da organização, os proprietários da org | Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | | Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | | Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +{% endif %} | Editar wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Denunciar conteúdo abusivo ou spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Aplicar etiquetas | | **X** | **X** | **X** | **X** | +| [Denunciar conteúdo abusivo ou spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Aplicar/ignorar etiquetas | | **X** | **X** | **X** | **X** | | Criar, editar, excluir etiquetas | | | **X** | **X** | **X** | | Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} +| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +{% endif %} | Aplicar marcos | | **X** | **X** | **X** | **X** | | Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | | Solicitar [revisões de pull requests](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | @@ -72,11 +83,13 @@ Além de gerenciar as configurações da organização, os proprietários da org | Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | | [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | | [Marcar uma pull request de rascunho como pronta para revisão](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} +| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} | Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | | [Aplicar alterações sugeridas](/articles/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | | Criar [verificações de status](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} +| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +{% endif %} | Criar e editar versões | | | **X** | **X** | **X** | | Exibir versões de rascunho | | | **X** | **X** | **X** | | Editar a descrição de um repositório | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} @@ -90,7 +103,8 @@ Além de gerenciar as configurações da organização, os proprietários da org | Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | | [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | | [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Limitar [interações em um repositório](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} +| Limitar [interações em um repositório](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** +{% endif %} | Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | | Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** | | [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | @@ -100,25 +114,20 @@ Além de gerenciar as configurações da organização, os proprietários da org | Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | | Alterar as configurações do repositório | | | | | **X** | | Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | -| Editar o branch padrão do repositório | | | | | **X** | +| Editar o branch padrão do repositório | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +{% endif %} | Gerenciar webhooks e chaves de implantação | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Habilitar o gráfico de dependências](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) em um repositório privado | | | | | **X** | -| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | -| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) para as dependências vulneráveis | | | | | **X** | -| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | -| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [Lista, descarta e exclui alertas de {% 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** |{% endif %} +| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} | [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | | [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | | [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | | [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} +| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** +{% endif %} | Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [Lista, descarta e exclui alertas de {% 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** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório | | | | **X** | **X** | | [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | | [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | @@ -127,7 +136,31 @@ Além de gerenciar as configurações da organização, os proprietários da org | [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | | [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | | [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} +| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Requisitos de permissão para funcionalidades de segurança + +Nesta seção, você pode encontrar os níveis de permissão de repositório necessários para as funcionalidades de segurança, como os funcionalidades de {% data variables.product.prodname_dependabot %} e {% data variables.product.prodname_advanced_security %}. + +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------:|:-------:|:--------:|:----------:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | +| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para as dependências vulneráveis | | | | | **X** | +| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [Habilitar o gráfico de dependências](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) em um repositório privado | | | | | **X** | +| [Visualizar as revisões de dependências](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [Lista, descarta e exclui alertas de {% 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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios | | | | | **X** +{% endif %} +{% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md index 424cab5098..0d8c7e5c19 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -15,6 +15,8 @@ versions: Você pode conectar até cinco grupos de IdP a uma equipe do {% data variables.product.prodname_dotcom %}. Um grupo de IdP pode ser atribuído a várias equipes do {% data variables.product.prodname_dotcom %} sem restrição. +A sincronização de equipes não é compatível com grupos de IdP com mais de 5000 integrantes. + Uma vez que uma equipe do {% data variables.product.prodname_dotcom %} está conectada a um grupo de IdP, o administrador do IdP deve efetuar as alterações da associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação na equipe em {% data variables.product.product_name %} ou usar a API. Todas as alterações de membros da equipe feitas através do seu IdP aparecerão no log de auditoria do {% data variables.product.product_name %} como alterações feitas pelo bot de sincronização de equipe. Seu IdP enviará dados de membros da equipe para {% data variables.product.prodname_dotcom %} uma vez a cada hora. A conexão de uma equipe a um grupo de IdP pode remover alguns integrantes da equipe. Para obter mais informações, consulte "[Requisitos para integrantes de equipes sincronizadas](#requirements-for-members-of-synchronized-teams)". @@ -27,19 +29,22 @@ Você também pode gerenciar a sincronização de equipe com a API. Para obter m ### Requisitos para integrantes de equipes sincronizadas -Após conectar uma equipe a um grupo de IdP, os dados da associação para cada integrante da equipe serão sincronizados se a pessoa continuar a efetuar a autenticação usando o SAML SSO com a mesma identidade SSO em {% data variables.product.prodname_dotcom %} e se a pessoa continuar como integrante do grupo de IdP conectado. +Após conectar uma equipe a um grupo de IdP, a sincronização da equipe adicionará cada integrante do grupo IdP à equipe correspondente em {% data variables.product.prodname_dotcom %} apenas se: +- A pessoa for integrante da organização em {% data variables.product.prodname_dotcom %}. +- A pessoa já efetuou o login com sua conta de usuário em {% data variables.product.prodname_dotcom %} e efetuou a autenticação na conta corporativa ou corporativa via logon único SAML pelo menos uma vez. +- A identidade SSO da pessoa é um integrante do grupo IdP. -As equipes ou integrantes de grupo existentes podem ser automaticamente removidos da equipe em {% data variables.product.prodname_dotcom %}. Todas as equipes ou membros de grupo que não efetuem a autenticação na conta da organização ou da empresa usando SSO podem perder o acesso aos repositórios. Todas as equipes existentes ou integrantes de grupo que não estiverem no grupo de IdP conectado podem perder o acesso aos repositórios. +As equipes ou integrantes de grupo que não atenderem a esses critérios serão automaticamente removidos da equipe em {% data variables.product.prodname_dotcom %} e perderão o acesso aos repositórios. Revogar a identidade vinculada a um usuário também removerá o usuário de quaisquer equipes mapeadas com os grupos de IdP. Para obter mais informações consulte "[Visualizar e gerenciar o acesso de SAML de um integrante da sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" e "[Visualizar e gerenciar o acesso de SAML de um usuário à sua conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)". Um integrante removido da equipe pode ser adicionado de volta a uma equipe automaticamente após efetuar a autenticação na conta da organização ou na conta corporativa usando SSO e será movidos para o grupo de IdP conectado. -Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". +Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. Para mais informações, consulte "[Aplicar logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" e "[Habilitar o logon único SAML para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". -Se sua organização pertencer a uma conta corporativa, habilitar a sincronização de equipes para a conta corporativa irá substituir as configurações de sincronização de equipe no nível da organização. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)". +Se sua organização pertencer a uma conta corporativa, habilitar a sincronização de equipes para a conta corporativa irá substituir as configurações de sincronização de equipe no nível da organização. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". ### Pré-requisitos -Antes poder conectar uma equipe a um grupo de provedores de identidade, uma organização ou dono da empresa deve habilitar a sincronização de equipes para sua organização ou conta corporativa. Para mais informações consulte "[Gerenciar a sincronização de equipes para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" e "[Aplicar configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)". +Antes poder conectar uma equipe a um grupo de provedores de identidade, uma organização ou dono da empresa deve habilitar a sincronização de equipes para sua organização ou conta corporativa. Para mais informações, consulte "[Gerenciar a sincronização de equipes para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" e "[Gerenciando a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". Para evitar a remoção involuntária dos integrantes da equipe, visite o portal administrativo do seu IdP e confirme se cada integrante atual da equipe está também nos grupos de IdP aos quais você deseja conectar a esta equipe. Se você não tiver acesso ao provedor de identidade, entre em contato com o administrador do IdP. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md index 8a120580cd..f8ac672a82 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -20,6 +20,8 @@ Você pode visualizar e revogar a identidade vinculada de cada integrante, as se {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.people %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index 048042ddfa..085c5d649c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -1,31 +1,31 @@ --- -title: About identity and access management for your enterprise account -intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +title: Sobre a identidade e gestão de acesso para a sua conta corporativa +intro: Você pode gerenciar centralmente o acesso aos recursos da sua empresa, associação da organização da equipe usando seu provedor de identidade (IdP). product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' --- -### About identity and access management for your enterprise account +### Sobre a identidade e gestão de acesso para a sua conta corporativa -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} Para obter mais informações, consulte "[Habilitar o login único SAML para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. +Depois de habilitar o SSO do SAML, dependendo do IdP que você usar, você poderá habilitar as funcionalidades adicionais de gerenciamento de identidade e acesso. -{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.about-user-provisioning-enterprise-account %} Para obter mais informações, consulte "[Sobre o provisionamento do usuário para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". -If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." +Se você usar o Azure AD como seu IDP, você poderá usar a sincronização de equipe para gerenciar a associação de equipe em cada organização. {% data reusables.identity-and-permissions.about-team-sync %} Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". -### Supported IdPs +### IdPs compatíveis -We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. Para obter mais informações, consulte a [Wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS. +Nós testamos e oferecemos compatibilidade oficial os seguintes IdPs. Para o SSO do SAML, oferecemos suporte limitado a todos os provedores de identidade que implementam o padrão SAML 2.0. Para obter mais informações, consulte a [Wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS. -| IdP | SAML | User provisioning | Sincronização de equipes | -| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | Provisionamento de usuários | Sincronização de equipes | +| -------------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md index 88bcd9d270..ec06997ade 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: About user provisioning for organizations in your enterprise account -intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +title: Sobre o provisionamento de usuários para organizações na sua conta corporativa +intro: Você pode gerenciar a associação das organizações em uma conta corporativa diretamente de um provedor de identidade (IdP). product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' @@ -12,7 +12,7 @@ versions: {% data reusables.scim.enterprise-account-scim %} Opcionalmente, você também pode habilitar o provisionamento de SAML e, separadamente, o desprovisionamento. -If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. Se você ativar o provisionamento de SAML, toda vez que um integrante da empresa acessar um recurso protegido pela configuração de SAML da conta corporativa, essa declaração de SAML irá acionar o provisionamento. +Se você configurar o SCIM para o aplicativo de {% data variables.product.product_name %} no seu IdP, cada vez que fizer alterações na associação do grupo no seu IdP, este fará uma chamada SCIM para {% data variables.product.prodname_dotcom %} para atualizar a associação da organização. Se você ativar o provisionamento de SAML, toda vez que um integrante da empresa acessar um recurso protegido pela configuração de SAML da conta corporativa, essa declaração de SAML irá acionar o provisionamento. Para cada chamada de SCIM ou declaração de SAML, {% data variables.product.product_name %} irá verificar os grupos de IdP aos quais o usuário pertence e executar as operações a seguir: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md index 5ccf47f7ad..a21034861d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Configuring identity and access management for your enterprise account -intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +title: Configurar identidade e gestão de acesso para a sua conta corporativa +intro: Você pode gerenciar o login único SAML, o provisionamento do usuário e a sincronização de equipes para a sua empresa. product: '{% data reusables.gated-features.enterprise-accounts %}' mapTopic: true versions: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md index c5a43dcdf1..71aaf5ec90 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md @@ -54,7 +54,7 @@ Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponív 1. À direita do menu suspenso, digite `.*.*`. 1. Clique em **Salvar**. {% data reusables.saml.okta-view-setup-instructions %} -1. Habilite o SAML para a conta corporativa usando as informações nas instruções de configuração. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +1. Habilite o SAML para a conta corporativa usando as informações nas instruções de configuração. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". ### Criar grupos no Okta diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index 559e516aac..2d2ca8827f 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -1,13 +1,13 @@ --- title: Habilitar logon único de SAML para organizações na conta corporativa -intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +intro: 'É possível controlar e garantir o acesso a recursos como repositórios, problemas, e pull requests habilitando o logon único SAML (SSO) e a autenticação centralizada através de um IdP em todas as organizações pertencentes a uma conta corporativa.' product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +permissions: Os proprietários das empresas podem habilitar o logon único SAML para organizações em uma conta corporativa. versions: free-pro-team: '*' --- -### About SAML single sign-on for enterprise accounts +### Sobre o logon único SAML para contas corporativas {% data reusables.saml.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". @@ -17,9 +17,9 @@ versions: {% data reusables.saml.saml-supported-idps %} -{% data reusables.scim.enterprise-account-scim %} Se você não estiver participando do beta privado, o SCIM não será compatível para as contas corporativas. For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.scim.enterprise-account-scim %} Se você não estiver participando do beta privado, o SCIM não será compatível para as contas corporativas. Para obter mais informações, consulte "[Sobre o provisionamento do usuário para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". -### Enabling SAML single-sign on for organizations in your enterprise account +### Habilitar o logn único SAML para organizações na sua conta corporativa {% note %} @@ -35,8 +35,8 @@ Para obter informações mais detalhadas sobre como ativar o SAML usando o Okta, 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} 5. Em "SAML single sign-on" (Logon único de SAML), selecione **Enable SAML authentication** (Habilitar autenticação SAML). ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) 6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) +7. Opcionalmente, no campo **Emissor**, digite a URL do emissor do SAML para verificar a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) 8. Em **Public Certificate** (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) -9. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) +9. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, no menu suspenso "Método de assinatura" e "Método de resumo", escolha o algoritmo de hashing usado pelo seu emissor do SAML. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) 10. Antes de habilitar o SAML SSO para sua empresa, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png) 11. Clique em **Salvar**. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md index 804ea9da4a..f6df857271 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md @@ -88,97 +88,6 @@ Você também pode configurar endereços IP permitidos para uma organização in {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} -### Habilitar logon único de SAML para organizações na conta corporativa - -{% data reusables.saml.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". - -Os proprietários empresariais podem ativar o SAML SSO e autenticação centralizada através de um IdP de SAML em todas as organizações que pertencem a uma conta corporativa. Depois que você habilita o SAML SSO para a conta corporativa, ele é habilitado por padrão para todas as organizações pertencentes a ela. Todos os integrantes deverão autenticar usando o SAML SSO para obter acesso às organizações de que fazem parte, e os proprietários corporativos precisarão autenticar usando o SAML SSO ao acessar uma conta corporativa. - -{% data reusables.saml.about-saml-access-enterprise-account %} Para obter mais informações, consulte "[Visualizar e gerenciar o acesso de SAML de um usuário à sua conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %} Se você não estiver participando do beta privado, o SCIM não será compatível para as contas corporativas. Para obter mais informações, consulte "[Gerenciar o provisionamento de usuários para organizações na sua conta corporativa](#managing-user-provisioning-for-organizations-in-your-enterprise-account)". - -{% note %} - -**Observação**: se você habilitar a autenticação com logon único SAML para a conta corporativa, as configurações SAML existentes no nível da organização serão substituídas. - -{% endnote %} - -Para obter informações mais detalhadas sobre como ativar o SAML usando o Okta, consulte "[Configurar o logon único SAML e SCIM para a sua conta corporativa usando o Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Em "SAML single sign-on" (Logon único de SAML), selecione **Enable SAML authentication** (Habilitar autenticação SAML). ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Isso confirma a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) -8. Em **Public Certificate** (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) -9. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, 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 de SAML. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) -10. Antes de habilitar o SAML SSO para sua empresa, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png) -11. Clique em **Salvar**. - -### Gerenciar o provisionamento de usuários para organizações na conta corporativa - -Os proprietários das empresas podem gerenciar a participação na organização de uma conta corporativa diretamente de um provedor de identidade (IdP). - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} Opcionalmente, você também pode habilitar o provisionamento de SAML e, separadamente, o desprovisionamento. - -Se você configurar o SCIM no seu IdP, toda vez que fizer alterações na associação do grupo no seu IdP, este fará uma chamada de SCIM para {% data variables.product.prodname_dotcom %} afim de atualizar a associação da organização correspondente. Se você ativar o provisionamento de SAML, toda vez que um integrante da empresa acessar um recurso protegido pela configuração de SAML da conta corporativa, essa declaração de SAML irá acionar o provisionamento. - -Para cada chamada de SCIM ou declaração de SAML, {% data variables.product.product_name %} irá verificar os grupos de IdP aos quais o usuário pertence e executar as operações a seguir: - -- Se o usuário for integrante de um grupo de IdP que corresponde a uma organização pertencente à conta corporativa e o usuário não for, atualmente, um membro dessa organização, adicione o usuário à organização (declaração de SAML) ou envie um convite por e-mail para participar da organização (chamada de SCIM). -- Cancele quaisquer convites existentes para o usuário juntar-se a uma organização que pertencem à conta corporativa. - -Para cada chamada de SCIM e, no caso de habilitar o desprovisionamento de SAML, em cada declaração de SAML, o {% data variables.product.product_name %} também executará a operação a seguir: - -- Se o usuário não for membro de um grupo de IdP que corresponde a uma organização pertencente à sua conta corporativa, e o usuário for, atualmente, um integrante dessa organização, remova o usuário da organização. - -Se desprovisionamento remover o último proprietário de uma organização, a organização ficará sem proprietário. Os proprietários das empresas podem assumir a propriedade de organizações sem proprietários. Para obter mais informações, consulte "[Gerenciar organizações sem proprietários na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account)". - -Para habilitar o provisionamento de usuários para sua conta corporativa usando o Okta, consulte "[Configurar o logon único SAML e SCIM para a sua conta corporativa usando o Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)". - -### Gerenciar a sincronização de equipes para organizações na conta corporativa - -Os proprietários das empresas podem habilitar a sincronização de equipes entre um IdP e {% data variables.product.product_name %} para permitir que os proprietários da organização e os mantenedores de equipe conectem equipes nas organizações pertencentes à sua conta corporativa com grupos de IdP. - -{% data reusables.identity-and-permissions.about-team-sync %} - -Você pode usar a sincronização de equipes com a sua conta corporativa com o Azure AD. - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -Você também pode configurar e gerenciar a sincronização da equipe para uma organização individual. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)". - -#### Pré-requisitos - -Antes de poder habilitar a sincronização de equipes para a sua conta corporativa: - - Você ou o administrador do Azure AD deve ser um administrador global ou um administrador com função privilegiada no Azure AD. - - Você deve habilitar o logon único SAML para organizações na conta corporativa com o IdP compatível. Para obter mais informações, consulte "[Habilitar o logon único SAML para organizações na conta corporativa](#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". - - Você deve efetuar a autenticação na sua conta corporativa usando o SAML SSO e o IdP compatível. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)". - -#### Gerenciar a sincronização de equipe para o Azure AD - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Revise as informações do locatário do provedor de identidade que você deseja conectar à conta corporativa e clique em **Aprovar**. ![Solicitação pendente para habilitar a sincronização de equipes para um determinado encarregado do IdP com opção de aprovar ou cancelar a solicitação](/assets/images/help/teams/approve-team-synchronization.png) -8. Para desativar a sincronização de equipe, clique **Desativar sincronização de equipe**. ![Desabilitar a sincronização de equipes](/assets/images/help/teams/disable-team-synchronization.png) - ### Gerenciar autoridades certificadas de SSH da conta corporativa Os proprietários corporativos podem adicionar e excluir autoridades certificadas (CAs) de SSH de uma conta corporativa. @@ -203,3 +112,7 @@ A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} + +### Leia mais + +- "[Configurar identidade e gerenciamento de acesso para a sua conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md index aafad0d5d9..2f7c5e8091 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md @@ -28,14 +28,20 @@ versions: {% link_in_list /managing-unowned-organizations-in-your-enterprise-account %} {% link_in_list /viewing-the-audit-logs-for-organizations-in-your-enterprise-account %} {% link_in_list /configuring-webhooks-for-organization-events-in-your-enterprise-account %} +{% topic_link_in_list /configuring-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /about-identity-and-access-management-for-your-enterprise-account %} + {% link_in_list /enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account %} + {% link_in_list /about-user-provisioning-for-organizations-in-your-enterprise-account %} + {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} + {% link_in_list /managing-team-synchronization-for-organizations-in-your-enterprise-account %} {% topic_link_in_list /setting-policies-for-organizations-in-your-enterprise-account %} {% link_in_list /enforcing-repository-management-policies-in-your-enterprise-account %} {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %} {% link_in_list /enforcing-team-policies-in-your-enterprise-account %} {% link_in_list /enforcing-security-settings-in-your-enterprise-account %} - {% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %} {% link_in_list /verifying-your-enterprise-accounts-domain %} {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %} {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %} {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %} + diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index f71e6b4e4b..94995e2fd4 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -15,7 +15,9 @@ versions: {% data variables.product.prodname_vss_ghe %} é uma oferta combinada da Microsoft que permite que um assinante use {% data variables.product.prodname_enterprise %} e {% data variables.product.prodname_vs %}. {% data variables.product.prodname_vss_ghe %} está disponível na Microsoft nos termos do Contrato da Microsoft. 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 %} -Depois de atribuir uma licença de {% data variables.product.prodname_vss_ghe %} a um assinante, o integrante usará a parte {% data variables.product.prodname_enterprise %} da licença, juntando-se a uma organização na sua conta corporativa com uma conta de usuário no {% data variables.product.prodname_dotcom_the_website %}. +Depois de atribuir uma licença de {% data variables.product.prodname_vss_ghe %} a um assinante, o integrante usará a parte {% data variables.product.prodname_enterprise %} da licença, juntando-se a uma organização na sua conta corporativa com uma conta de usuário no {% 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 %}. + +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 %}. 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)". @@ -27,11 +29,15 @@ Para obter mais informações sobre o {% data variables.product.prodname_enterpr 3. Em {% data variables.product.prodname_dotcom_the_website %}, crie pelo menos uma organização pertencente à conta corporativa. Para obter mais informações, consulte "[Adicionar organizações à sua conta corporativa](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)". -4. O assinante deve criar uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %} e o endereço de e-mail para a conta deve ser o mesmo endereço de e-mail que o endereço de e-mail no portal {% data variables.product.prodname_vs %}. Para obter mais informações, consulte "[Inscrever-se em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" e " "[Gerenciar preferências de e-mail](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)". - ### Convidar um assinante para usar {% data variables.product.prodname_enterprise %} -Para usar a parte de {% data variables.product.prodname_enterprise %} da licença, o integrante deve participar de uma organização pertencente à sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. Os proprietários da organização podem convidar novos integrantes para uma organização. Para obter mais informações, consulte "[Convidar usuários para participar da sua organização](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)". +Para usar a parte da licença de {% data variables.product.prodname_enterprise %}, a conta de usuário assinante no {% data variables.product.prodname_dotcom_the_website %} deve ser ou tornar-se integrante de uma organização de propriedade da sua empresa em {% data variables.product.prodname_dotcom_the_website %}. + +Os proprietários da organização podem convidar novos integrantes para uma organização por endereço de e-mail. 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. + +Embora não seja necessário, recomendamos que os proprietários da organização enviem um convite para o mesmo endereço de e-mail usado para o Nome Principal do Usuário (UPN) do assinante de {% data variables.product.prodname_vs %}. Quando o endereço de e-mail em {% data variables.product.product_name %} corresponder ao UPN do assinante, você poderá garantir que outro integrante da organização não reivindique a licença do assinante. + +Para obter mais informações, consulte "[Convidar usuários para participar da sua organização](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization), "[Inscrever-se em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)" e "[Gerenciar preferências de e-mail](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)". ### Visualizar licenciamento de {% data variables.product.prodname_enterprise %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index 040ed9f953..bf95371164 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -1,15 +1,15 @@ --- title: Gerenciar a sincronização de equipes para organizações na conta corporativa -intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +intro: 'É possível habilitar a sincronização de equipes entre um provedor de identidade (IdP) e {% data variables.product.product_name %} para permitir que organizações pertencentes à sua conta corporativa gerenciem a associação de equipes por meio de grupos IdP.' product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Enterprise owners can manage team synchronization for an enterprise account. +permissions: Os proprietários das empresas podem gerenciar a sincronização de equipes para uma conta corporativa. versions: free-pro-team: '*' --- -### About team synchronization for enterprise accounts +### Sobre a sincronização de equipes para contas corporativas -If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. +Se você usar o Azure AD como seu IdP, você pode habilitar a sincronização de equipes para sua conta corporativa para permitir que os proprietários da organização e mantenedores de equipe sincronizem as equipes nas organizações pertencentes às contas corporativas com os grupos de IdP. {% data reusables.identity-and-permissions.about-team-sync %} @@ -37,5 +37,5 @@ Você deve efetuar a autenticação na sua conta corporativa usando o SAML SSO e {% data reusables.identity-and-permissions.team-sync-confirm-saml %} {% data reusables.identity-and-permissions.enable-team-sync-azure %} {% data reusables.identity-and-permissions.team-sync-confirm %} -7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![Solicitação pendente para habilitar a sincronização de equipes para um determinado encarregado do IdP com opção de aprovar ou cancelar a solicitação](/assets/images/help/teams/approve-team-synchronization.png) +7. Revise os detalhes do organismo de IdP que você deseja conectar à conta corporativa e, em seguida, clique em **Aprovar**. ![Solicitação pendente para habilitar a sincronização de equipes para um determinado encarregado do IdP com opção de aprovar ou cancelar a solicitação](/assets/images/help/teams/approve-team-synchronization.png) 8. Para desativar a sincronização de equipe, clique **Desativar sincronização de equipe**. ![Desabilitar a sincronização de equipes](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md index c34c8c04cf..b5e26d0813 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -Se você habilitar o desprovisionamento de usuários para gerenciar a associação da organização na sua conta corporativa, você poderá acabar com uma organização sem proprietários. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)". +Se você habilitar o desprovisionamento de usuários para gerenciar a associação da organização na sua conta corporativa, você poderá acabar com uma organização sem proprietários. Para obter mais informações, consulte "[Sobre o provisionamento do usuário para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". {% data reusables.enterprise-accounts.access-enterprise %} 2. À direita do campo de pesquisa, clique **X sem proprietário**. ![Botão para visualizar organizações sem proprietários](/assets/images/help/business-accounts/unowned-organizations-button.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index a1ab984a6e..07f9816649 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,6 +18,8 @@ Ao ativar o logon único do SAML para a sua conta corporativa, cada integrante d {% data reusables.saml.about-linked-identities %} +{% data reusables.identity-and-permissions.revoking-identity-team-sync %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index d93885da2f..72515333ae 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -22,8 +22,8 @@ Para obter mais informações sobre como administrar gerentes de cobrança, cons {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -4. Em +1. Em {% if currentVersion == "free-pro-team@latest" %}Licenças{% else %}licenças{% endif %} do usuário", visualize o seu total de licenças, o número de licenças consumidas e a data de expiração da assinatura. {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Informações de assinaturas e licenças nas configurações de cobrança da empresa](/assets/images/enterprise/enterprises/enterprise-server-billing-license-info.png){% endif %} -5. Para ver os detalhes das licenças dos usuários em uso atualmente, clique em **Ver {% if currentVersion == "free-pro-team@latest" %}detalhes{% else %}de usuários{% endif %}**. +1. Opcionalmente, para visualizar os detalhes para o uso da licença ou para fazer o download de um arquivo {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} com detalhes da licença{% if currentVersion == "free-pro-team@latest" %}, à direita de "LIcenças do usuário" {% endif %}, clique em **Visualizar {% if currentVersion == "free-pro-team@latest" %}detalhes{% elsif enterpriseServerVersions contains currentVersion %}usuários{% endif %}** ou {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Exportar uso da licença**{% endif %}.{% if currentVersion == "free-pro-team@latest" %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 4dea21b893..6ce0d02262 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ O GitHub irá exibir o LEIAME do seu perfil na sua página de perfil se todas as O arquivo README gerado é pré-preenchido com um modelo para dar alguma inspiração para o LEIAME do seu perfil. ![Arquivo README com modelo pré-preenchido](/assets/images/help/repository/personal-repository-readme-template.png) +Para obter um resumo todos os emojis disponíveis e seus códigos, consulte "[Folha de dicas de Emoji](http://www.emoji-cheat-sheet.com/)". + ### Remover um LEIAME do perfil O perfil LEIAME é removido do seu perfil de {% data variables.product.prodname_dotcom %} se algum dos pontos seguintes se aplicar: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md index d5fbb28c3a..8e9c2168cb 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline.md @@ -36,23 +36,23 @@ Na maioria das vezes, a data de criação e a data do commit são as mesmas, mas Você pode usar o comando `git show` com o sinalizador `--pretty=fuller` para verificar se a data de criação do commit e a data do commit são diferentes. ```shell -$ git show O número de SHA do commit --pretty=fuller -commit O número de SHA do commit -Author: octocat e-mail do usuário -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 -Commit: Sally Johnson e-mail do usuário -CommitDate: Wed Jul 20 06:25:08 2016 +0900 +$ git show Your commit SHA number --pretty=fuller +commit Your commit SHA number +Author: octocat user email +AuthorDate: Tue Apr 03 02:02:30 2018 +0900 +Commit: Sally Johnson user email +CommitDate: Tue Apr 10 06:25:08 2018 +0900 ``` Se a data de criação e do commit forem diferentes, é possível alterar manualmente a data do commit na URL para ver os detalhes do commit. Por exemplo: -- Esta URL usa a data de criação `2016-07-13`: +- Esta URL usa a data de criação `2018-04-03`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- Esta URL usa a data do commit `2016-07-19`: + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z` +- Esta URL usa a data do commit `2018-04-10`: - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` + `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z` Quando você abrir a URL com a data do commit modificada, poderá ver os detalhes do commit. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index c061614021..88dbde9790 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -11,9 +11,9 @@ versions: ### Contribuições que são contabilizadas -#### Problemas e pull requests +#### Problemas, pull requests e discussões -Os problemas e as pull requests aparecerão no gráfico de contribuições se tiverem sido abertos em um repositório autônomo, e não em uma bifurcação. +Os problemas, pull requests e discussões aparecerão no gráfico de contribuição se estiverem abertos em um repositório autônomo, não em uma bifurcação. #### Commits Os commits aparecerão no gráfico de contribuições se atenderem a **todas** estas condições: diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md index 24fb71f04c..a0b04ec719 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md @@ -22,7 +22,7 @@ Existem três níveis de permissões para colaboradores de quadro de projeto: O proprietário do quadro de projeto e colaboradores com acesso de administrador têm controle total do quadro de projeto. Além de todas as permissões de colaboradores de quadro de projeto, um proprietário de quadro de projeto e um colaborador com acesso de administrador podem: - [Gerenciar, visualizar e adicionar colaboradores](/articles/managing-access-to-your-user-account-s-project-boards) -- [Configurar um quadro de projeto como público ou privado](/articles/changing-project-board-visibility) +- [Configurar um quadro de projeto como {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} ou privado](/articles/changing-project-board-visibility) - [Excluir um quadro de projeto](/articles/deleting-a-project-board/) - [Fechar um quadro de projeto](/articles/closing-a-project-board/) - [Reabrir um quadro de projeto fechado](/articles/reopening-a-closed-project-board) @@ -51,7 +51,7 @@ Colaboradores com acesso de gravação em um quadro de projeto pertencente a um ### Visibilidade do quadro de projeto -Você pode alterar a visibilidade do quadro de projeto de privada para pública e vice-versa. Por padrão, os quadros de projeto pertencentes a um usuário são privados. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". +Você pode alterar a visibilidade do painel do projeto de privado para {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} e de volta. Por padrão, os quadros de projeto pertencentes a um usuário são privados. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md index 4532bdf043..a5def5e8c3 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -1,6 +1,6 @@ --- title: Tipos de e-mails enviados pelo GitHub -intro: 'Há vários tipos de e-mails que você pode receber do {% data variables.product.product_name %}, como notificações, informações da conta e comunicações de marketing.' +intro: 'Existem vários tipos de e-mails que você pode receber de {% data variables.product.product_name %}, incluindo notificações, informações da conta, convites de pesquisa de clientes e comunicações de marketing.' redirect_from: - /articles/types-of-emails-github-sends versions: @@ -25,6 +25,17 @@ Você também pode escolher qual tipo de atualizações de e-mail deseja receber Se você tiver atualizado para recursos ou produtos pagos, receberá recibos de cobrança no endereço de e-mail principal da conta. Para obter mais informações, consulte "[Configurar o e-mail de cobrança](/articles/setting-your-billing-email)". +### E-mails de pesquisa de cliente + +Ocasionalmente, {% data variables.product.product_name %} procura clientes para participar de sessões de pesquisa para nos ajudar a construir um GitHub melhor. Isso é realizado remotamente, aberto a clientes em todo o mundo, e pode incluir: + +- Pesquisas de feedback +- Entrevistas de pesquisa +- Sessões de teste de usabilidade +- Pré-visualizar protótipos iniciais ou conceitos + +Esses e-mails são infrequentes e você pode escolher participar ou não. Se estiver interessado em oportunidades adicionais para participar de sessões de pesquisa, você poderá adicionar você mesmo ao Painel de Pesquisa de Cliente do GitHub. Para obter mais informações, consulte "[Pesquisa de Experiência do Cliente do GitHub](https://cxr.github.com)." + ### E-mails de marketing De vez em quando, o {% data variables.product.product_name %} envia estes tipos de e-mails de marketing: diff --git a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md index 49a1a976b3..3acc8e9247 100644 --- a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md +++ b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: December 14, 2020 +Data da entrada em vigor da versão: 14 de dezembro de 2020 Quando você cria uma Conta, tem acesso a vários recursos e produtos diferentes que fazem parte do Serviço. Como muitos desses recursos e produtos oferecem diferentes funcionalidades, eles podem exigir termos e condições adicionais específicos para esse recurso ou produto. Abaixo, listamos esses recursos e produtos, juntamente com os termos adicionais correspondentes que se aplicam ao uso deles. @@ -46,19 +46,19 @@ O GitHub Pages está sujeito a limites específicos de uso e largura de banda e ### 5. Ações e Pacotes #### a. Uso das Ações -GitHub 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. +O GitHub Actions é cobrado com base no uso. A [Documentação de ações](/actions) inclui detalhes, que abrangem quantidades de computação e armazenamento (dependendo do plano da sua conta) e como monitorar seus minutos de ação de uso e definir limites de uso. -Actions and any elements of the Actions 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). Além disso, as Ações não devem ser usadas para: +As ações e todos elementos do Serviço de Ações não podem ser usados em violação do Contrato, a [Políticas de Uso Aceitável no GitHub](/github/site-policy/github-acceptable-use-policies), ou as limitações de serviço do GitHub Actions estabelecidas na [Documentação de Ações](/actions). Além disso, as Ações não devem ser usadas para: - mineração de criptomoedas; -- 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](https://bounty.github.com)); +- usar nossos servidores para interromper ou ganhar ou tentar ganhar acesso não autorizado a qualquer serviço, dispositivo, dados, conta ou rede (a menos que autorizado pelo [programa GitHub Bug Bounty](https://bounty.github.com)); - fornecimento de um aplicativo ou serviço independente ou integrado que ofereça Ações ou quaisquer elementos de Ações para fins comerciais; - qualquer atividade que coloque um peso em nossos servidores, em que esse peso é desproporcional aos benefícios oferecidos aos usuários (por exemplo, não usar Ações como uma rede de entrega de conteúdo ou como parte de um aplicativo sem servidor, mas uma Ação de baixo benefício pode ser realizada se também tiver um peso baixo); ou - qualquer outra atividade não relacionada à produção, teste, implantação ou publicação do projeto de software associado ao repositório onde as Ações do GitHub são usadas. -Para evitar violações dessas limitações e abuso de Ações do GitHub, o GitHub pode monitorar seu uso das Ações do GitHub. O uso indevido de Ações do GitHub pode resultar no encerramento de trabalhos ou restrições na sua capacidade de usar as Ações do GitHub. +Para evitar violações dessas limitações e abuso de Ações do GitHub, o GitHub pode monitorar seu uso das Ações do GitHub. O mau uso do GitHub Actions pode gerar a rescisão de trabalhos, restrições na sua capacidade de usar o GitHub Actions, ou a desabilitação de repositórios criados para executar ações de forma que viole estes Termos. #### b. Uso do pacotes -GitHub Packages is billed on a usage basis. The [Packages documentation](/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). +O GitHub Packages são cobrados com base no uso. A [Documentação de pacotes](/packages) inclui detalhes, que abrangem a largura de banda e quantidades de armazenamento (dependendo do plano da sua conta) e como monitorar seu uso de pacotes e definir limites de uso. O uso de largura de banda de pacotes é limitado pela [Política de Uso Aceitável do GitHub](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -100,10 +100,10 @@ O Banco de Dados Consultivo GitHub está licenciado sob a [licença 4.0 Creative ### 13. GitHub Enterprise Server -#### a. SQL Server Images +#### a. Imagens do servidor SQL -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. A Microsoft Corporation pode desativar o SQL Server Images a qualquer momento. +Você pode fazer o download da imagem de contêiner de edição padrão do Microsoft SQL Server para arquivos Linux ("Imagens do Servidor SQL"). Você deve desinstalar as imagens do Servidor SQL quando seu direito de usar o Software terminar. A Microsoft Corporation pode desativar o SQL Server Images a qualquer momento. -#### b. Third-party components +#### b. Componentes de terceiros O Software inclui componentes licenciados para o GitHub por terceiros, como programas de software cujas licenças exigem que o GitHub disponibilize o código-fonte desses componentes, que será fornecido mediante solicitação. diff --git a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md index adf108e020..d5a41ec910 100644 --- a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md +++ b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md @@ -11,9 +11,9 @@ versions: GitHub.com, GitHub Enterprise Server, e as informações que você enviar para qualquer produto podem estar sujeitas a regulamentações de controle de negociação, inclusive sob Regulamentos da Administração de Exportação dos EUA (EAR). Regulamentos Administrativos de Exportação (EAR). -O objetivo do GitHub é ser a plataforma global para a colaboração de desenvolvedores, não importa onde os desenvolvedores estiverem. Levamos a sério a nossa responsabilidade de examinar minuciosamente as ordens governamentais para ter a certeza de que os usuários e clientes não sejam impactados para além do que seja exigido por lei. Isso inclui manter serviços de repositórios públicos, incluindo os destinados a projetos de código aberto, disponíveis e acessíveis para apoiar comunicações pessoais que envolvam desenvolvedores em regiões sancionadas. +O objetivo do GitHub é ser a plataforma global para a colaboração de desenvolvedores, não importa onde os desenvolvedores estiverem. Levamos a sério a nossa responsabilidade de examinar minuciosamente as ordens governamentais para ter a certeza de que os usuários e clientes não sejam impactados para além do que seja exigido por lei. Isso inclui manter os serviços públicos de repositórios, incluindo aqueles para projetos de código aberto, disponíveis e acessíveis para apoiar comunicações pessoais que envolvem desenvolvedores em regiões sancionadas. Isto também significa que o GitHub defenderá para desenvolvedores de regiões sancionadas para desfrutar de maior acesso à plataforma e total acesso à comunidade global de código aberto. -Para estar em conformidade com os E.U.A. Para cumprir as leis de controle de negociação dos EUA, o GitHub realizou algumas alterações necessárias na forma como conduzimos nossos serviços. Como as leis de controle de comércio evoluem, continuaremos a trabalhar com as leis À medida que as leis de controle de negociação dos EUA evoluem, continuaremos a trabalhar com os reguladores dos EUA para saber em que medida podemos oferecer serviços gratuitos de colaboração em código aos desenvolvedores de mercados sancionados. Acreditamos que oferecer esses serviços grátis apoia os EUA. Acreditamos que oferecer esses serviços gratuitos ajuda a política externa dos EUA de incentivo ao livre fluxo de informação e à liberdade de expressão nesses mercados. Para saber mais sobre nossa abordagem e como as sanções afetam a colaboração do software global, leia nosso [blog sobre sanções](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/). +Como resultado de nossa defesa e trabalho duro com os EUA reguladores, o GitHub obteve uma licença dos EUA Controle de Ativos Externos do Departamento de Tesouro (OFAC) para restaurar nossos serviços em nuvem para desenvolvedores no Irã. E continuaremos a trabalhar com os EUA. reguladores para proteger licenças semelhantes para oferecer serviços de colaboração aos desenvolvedores da Síria e Crimeia. Estamos empenhados em defender o acesso de desenvolvedor mais amplo possível, já que acreditamos que oferecer serviços de colaboração de código para desenvolvedores de regiões sancionadas fortalece a comunidade de desenvolvedores, amplia o progresso humano e apoia o fortalecimento da política externa dos EUA de promoção da liberdade de expressão e da livre circulação da informação. Para obter informações sobre a licença que garantimos para desenvolvedores no Irã, leia [o post no blogue](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). Embora tenhamos fornecido as seguintes informações para sua conveniência, em última análise, é sua responsabilidade garantir que o seu uso de produtos e serviços GitHub esteja de acordo com todas as leis e regulamentações aplicáveis, incluindo as leis de controle exportação dos EUA. de controle de exportação dos EUA. @@ -25,9 +25,11 @@ De acordo com nossos [Termos de Serviço](/articles/github-terms-of-service), os Os usuários são responsáveis por garantir que o conteúdo que eles desenvolvem e compartilham no GitHub.com esteja em conformidade com as leis de controle de exportação dos EUA, incluindo o EAR e os Regulamentos de Tráfego Internacional de Armas dos EUA (ITAR). leis de controle de exportação, incluindo a EAR e os EUA Tráfego Internacional em Regulamentos de Armas (ITAR). A oferta de serviço hospedado na nuvem disponível no [GitHub.com](https://github.com) não foi projetado para hospedar dados sujeitos ao ITAR e, atualmente, não oferece a capacidade de restringir o acesso a repositório por país. Se você estiver procurando colaborar em ITAR ou em outros dados controlados por exportação, recomendamos que você considere o [GitHub Enterprise Server](https://enterprise.github.com), a oferta local do GitHub. -EUA As leis de controle de negociação dos EUA restringem quais serviços o GitHub.com pode tornar disponíveis para usuários em determinados países e territórios. O GitHub pode permitir aos usuários que residem normalmente em países e territórios sujeitos aos E.U.A. O GitHub pode permitir que usuários que residem normalmente em países e territórios sujeitos a sanções dos EUA acessem determinados serviços GitHub.com gratuitos para comunicação pessoal, de acordo com autorizações emitidas pelo Departamento de Controle de Ativos Estrangeiros do Departamento do Tesouro dos EUA (OFAC). Gabinete do Tesouro de Controle de Ativos Externos (OFAC). Pessoas localizadas ou normalmente residentes nesses países e territórios são proibidas de usar proxies de IP, VPNs, ou outros métodos para disfarçar sua localização ao acessar os serviços do GitHub.com para comunicações não comerciais e pessoais. +O GitHub tem agora uma licença do OFAC para fornecer serviços em nuvem aos desenvolvedores localizados ou residentes do Irã. Isto inclui todos os serviços públicos e privados para indivíduos e organizações, tanto gratuitos como remunerados. -Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA Nacionais Especialmente Designados (SDNs) e outros grupos negados ou bloqueados pelas leis dos EUA e outras aplicáveis são proibidos de acessar ou usar o GitHub.com. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo os governos de países sancionados. Além disso, GitHub.com não pode ser utilizado para fins proibidos conforme as leis de controle de exportação aplicáveis, incluindo usos finais proibidos descritos em [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). +Serviços em nuvem do GitHub, gratuitos e pagos, também estão geralmente disponíveis para desenvolvedores localizados em Cuba. + +Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA e outras leis aplicáveis, e certos funcionários do governo, podem ter restrições para acessar ou usar o GitHub.com. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo, de modo geral, os governos de países sancionados. Além disso, GitHub.com não pode ser utilizado para fins proibidos conforme as leis de controle de exportação aplicáveis, incluindo usos finais proibidos descritos em [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). #### GitHub Enterprise Server @@ -41,13 +43,13 @@ O GitHub Enterprise Server não pode ser vendido, exportado ou reexportado para #### Em que países e territórios são aplicadas sanções governamentais dos EUA? aplicadas sanções governamentais? -Crimeia, Cuba, Irã, Coreia do Norte e Síria. +Crimeia, Cuba, Irã, Coreia do Norte e Síria. No entanto, no que diz respeito ao Irã, o GitHub agora tem uma licença dos EUA. O Escritório de Controle de Ativos Externos do Departamento do Tesouro (OFAC) para fornecer serviços de nuvem a desenvolvedores localizados ou que residam em qualquer outro lugar nesse país. Serviços em nuvem do GitHub, gratuitos e pagos, também estão geralmente disponíveis para desenvolvedores localizados em Cuba. #### Como o GitHub garante que as pessoas que não vivem e/ou tenham ligações profissionais com os países e territórios sancionados ainda tenham acesso ou capacidade de recorrer? No caso raro de uma conta ser afetada não intencionalmente ou por engano, temos um processo de apelação para abordar essas instâncias. -Se um usuário individual ou administrador de organização acredita ter sido erroneamente sinalizado, então esse usuário tem a oportunidade de recorrer do sinalizador, fornecendo informações de verificação ao GitHub. Se o GitHub receber informações suficientes para verificar se o usuário ou a organização não estão afiliados a uma jurisdição sancionada ou restrita por sanções econômicas dos EUA, então o sinalizador será removido. sanções econômicas. Portanto, o sinalizador será removido. Por favor, consulte o [formulário de solicitação de apelação para conta individual](https://airtable.com/shrGBcceazKIoz6pY) e o [formulário de solicitação de apelação para conta organizacional](https://airtable.com/shrB2je5RBkqLEt5D). +Se um usuário individual ou administrador de organização acredita ter sido erroneamente sinalizado, então esse usuário tem a oportunidade de recorrer do sinalizador, fornecendo informações de verificação ao GitHub. Se o GitHub receber informações suficientes para verificar se o usuário ou organização não está afiliado a uma jurisdição não sancionada pelos EUA para a qual não temos uma licença ou seríamos, de outra forma, restringidos pelos EUA. sanções econômicas. Portanto, o sinalizador será removido. Por favor, consulte o [formulário de solicitação de apelação para conta individual](https://airtable.com/shrGBcceazKIoz6pY) e o [formulário de solicitação de apelação para conta organizacional](https://airtable.com/shrB2je5RBkqLEt5D). #### A viagem para essas regiões pode ser impactada? @@ -55,23 +57,27 @@ Viajar para essas regiões pode impactar o status de sua conta, mas a disponibil #### O que está e o que não está disponível? -O GitHub está comprometido em continuar a oferecer serviços gratuitos de repositório público para desenvolvedores com contas individuais e organizacionais em regiões sancionadas pelos EUA. Isso inclui acesso limitado a serviços gratuitos, como repositórios públicos para projetos de código aberto (e páginas públicas associadas), gists públicos e minutos de Ação gratuitos alocados, apenas para comunicações pessoais, e não para fins comerciais. +Agora, o GitHub tem uma licença da OFAC para fornecer serviços em nuvem para os desenvolvedores localizados ou residentes no Irã, país sancionado pelos EUA. A licença inclui todos os serviços públicos e privados para indivíduos e organizações, tanto grátis como pagos. Serviços em nuvem do GitHub, gratuitos e pagos, também estão geralmente disponíveis para desenvolvedores localizados em Cuba. -No entanto, devido aos Estados Unidos Devido às restrições legais de controles comerciais dos EUA, o GitHub não pode fornecer serviços de repositório privados e serviços pagos a contas em regiões sancionadas pelos EUA. regiões sancionadas como a Coreia do Norte, o Irã, Síria e a Crimeia. A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. +O GitHub tem o compromisso de continuar oferecendo serviços públicos grátis de repositórios para desenvolvedores com contas individuais e organizacionais na Síria e Crimeia. Isso inclui acesso limitado a serviços gratuitos, como repositórios públicos para projetos de código aberto (e páginas públicas associadas), gists públicos e minutos de Ação gratuitos alocados, apenas para comunicações pessoais, e não para fins comerciais. -Para contas organizacionais pagas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas em regiões sancionadas, no entanto, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados gratuitos. +Para contas organizacionais pagas nessas regiões sancionadas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas nessas regiões sancionadas, no entanto, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados grátis. -O GitHub continuará defendendo junto com os EUA. O GitHub continuará defendendo junto aos reguladores dos EUA o maior acesso possível a serviços gratuitos de colaboração de códigos para desenvolvedores em regiões sancionadas, incluindo repositórios privados gratuitos. Acreditamos que oferecer esses serviços grátis apoia os EUA. Acreditamos que oferecer esses serviços gratuitos ajuda a política externa dos EUA de incentivo ao livre fluxo de informação e à liberdade de expressão nessas regiões. +O GitHub continuará defendendo junto com os EUA. regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. de promoção da liberdade de expressão e da livre circulação da informação. + +Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. + +GitHub services are not available to developers located or otherwise resident in North Korea. #### Como você define esses usuários específicos? -Se o GitHub determinar que um usuário ou cliente está localizado em uma região sujeita às restrições de controle de negociação dos EUA, ou que um usuário está restrito pelas sanções econômicas dos EUA, então a conta afiliada será limitada para cumprir esses requisitos legais. restrições de controle comercial, ou um usuário tem restrições de outra forma nos EUA sanções econômicas. Portanto a conta afiliada foi restrita para cumprir esses requisitos legais. A determinação da localização do usuário e cliente para implementar essas restrições legais deriva de várias fontes, incluindo endereços IP e histórico de pagamentos. A nacionalidade e a etnia não são utilizadas para sinalizar usuários para restrições de sanções. +Se o GitHub determinar que um usuário ou cliente está localizado em uma região sujeita às restrições de controle de negociação dos EUA, ou que um usuário está restrito pelas sanções econômicas dos EUA, então a conta afiliada será limitada para cumprir esses requisitos legais. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. A determinação da localização do usuário e cliente para implementar essas restrições legais deriva de várias fontes, incluindo endereços IP e histórico de pagamentos. A nacionalidade e a etnia não são utilizadas para sinalizar usuários para restrições de sanções. #### Como as contas da organização são impactadas? -Se uma organização tiver sede em, ou as principais pessoas ou membros de uma organização mostram laços suficientes a, um território ou país sancionado, ou se a organização parecer estar sujeita às sanções econômicas dos EUA, então a conta da organização e a conta do proprietário afiliado serão limitadas. sanções econômicas e, posteriormente, a conta de organização e a conta de proprietário afiliado serão restritas. +If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. sanções econômicas e, posteriormente, a conta de organização e a conta de proprietário afiliado serão restritas. -A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. Para contas organizacionais pagas associadas com regiões sancionadas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas em regiões sancionadas, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados gratuitos. +A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. For paid organizational accounts associated with such sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts associated with such sanctioned regions, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. #### Os repositórios privados dos usuários com negociação restrita podem ser tornados públicos? @@ -81,3 +87,21 @@ Os usuários de contas individuais gratuitas podem tornar repositórios privados Infelizmente, a nossa interpretação da lei não nos dá a opção de permitir downloads ou exclusão de conteúdo de repositórios privados até que seja autorizado de outra forma pelo governo dos EUA. governo. Defenderemos energicamente com os EUA. Defenderemos, fortemente, junto dos órgãos reguladores dos EUA, o direito de usuários restritos à negociação protegerem o conteúdo de seus repositórios privados. Também defenderemos uma maior disponibilidade de serviços do GitHub para desenvolvedores em mercados sancionados, e reforçaremos ainda mais a importância da colaboração de códigos no apoio a comunicações pessoais para desenvolvedores em todo o mundo. +#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran? + +The license we have secured includes all public and private services, for individuals and organizations, both free and paid. + +For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students. + +Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA and other applicable law, and certain government officials may be restricted from accessing or using GitHub. + +If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. sanções econômicas. Portanto, o sinalizador será removido. + +#### Will Iranian GitHub users be able to use paid services under the license? + +Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. + +#### Can you clarify availability of GitHub to Cuban developers? + +GitHub cloud services, both free and paid, are generally available to developers located in Cuba. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo, de modo geral, os governos de países sancionados. diff --git a/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md index be828c565b..0821888cde 100644 --- a/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ b/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md @@ -31,4 +31,4 @@ Dito isto, se uma ação legal for iniciada por terceiros, incluindo a aplicaç ### 3. Renúncia limitada a outras políticas do site -Na medida em que suas atividades de pesquisa de segurança são inconsistentes com certas restrições em nossas [políticas relevantes do site](/categories/site-policy/) mas são consistentes com os termos do nosso programa de recompensa de bugs, renunciamos a essas restrições com o único e limitado propósito de permitir sua pesquisa de segurança sob este programa de recompensa de bugs. Assim como acima, em caso de dúvida, pergunte-nos primeiro! +Na medida em que suas atividades de pesquisa de segurança são inconsistentes com certas restrições em nossas [políticas relevantes do site](/categories/site-policy/) mas são consistentes com os termos do nosso programa de recompensa de erros, renunciamos a essas restrições com o único e limitado propósito de permitir sua pesquisa de segurança sob este programa de recompensa de erros. Assim como acima, em caso de dúvida, pergunte-nos primeiro! diff --git a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md index d77a4c5b28..6484f04ffd 100644 --- a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md +++ b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md @@ -11,7 +11,7 @@ versions: free-pro-team: '*' --- -Effective date: December 19, 2020 +Data de vigência: 19 de dezembro de 2020 Agradecemos por confiar seu código-fonte, seus projetos e suas informações pessoais à GitHub Inc. (“GitHub” ou “nós”). Manter suas informações pessoais em segurança é uma responsabilidade que levamos a sério, e queremos mostrar como fazemos esse trabalho. @@ -26,24 +26,24 @@ Esta é uma versão resumida das nossas diretrizes. Para obter as informações ### Sumário -| Seção | Conteúdo | -| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| [Que tipo de informação o GitHub coleta](#what-information-github-collects) | O GitHub coleta informações diretamente de você para fins de registro, pagamento, transações e perfil de usuário. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. O GitHub também pode coletar Informações Pessoais de Usuário de terceiros. Coletamos somente a quantidade mínima de informações pessoais necessárias de você, a menos que você decida compartilhar mais informações. | -| [Que tipo de informação o GitHub _não_ coleta](#what-information-github-does-not-collect) | Não coletamos informações de crianças com menos de 13 anos nem coletamos [Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/). | -| [Como o GitHub usa suas informações](#how-github-uses-your-information) | Nesta seção, descrevemos as formas como usamos suas informações, inclusive para fornecer o Serviço, para nos comunicarmos com você, para fins de segurança e conformidade, e para melhorar nosso Serviço. A seção também descreve a base jurídica na qual processamos suas informações quando tal processamento for exigido por lei. | -| [Como compartilhamos as informações obtidas](#how-we-share-the-information-we-collect) | Podemos compartilhar suas informações com terceiros diante de uma das seguintes circunstâncias: com seu consentimento, com nossos prestadores de serviços para fins de segurança, para cumprir as nossas obrigações legais, ou quando houver mudança de controle ou venda de entidades corporativas ou unidades de negócios. Não vendemos suas informações pessoais e não hospedamos anúncios no GitHub. Consulte uma lista de prestadores de serviços que acessam suas informações. | -| [Outras informações importantes](#other-important-information) | Oferecemos informações adicionais específicas relacionadas a conteúdo de repositórios, informações públicas e Organizações no GitHub. | -| [Serviços adicionais](#additional-services) | Oferecemos informações sobre ofertas de serviço adicionais, inclusive aplicativos de terceiros, GitHub Pages e aplicativos do GitHub. | -| [Como você pode acessar e controlar as informações obtidas](#how-you-can-access-and-control-the-information-we-collect) | Propomos algumas medidas para você acessar, alterar ou excluir suas informações pessoais. | -| [Uso de cookies e rastreamento](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. Temos uma página que torna o processo bastante transparente. Veja mais detalhes nesta seção. | -| [Como o GitHub protege suas informações](#how-github-secures-your-information) | Tomamos todas as medidas razoavelmente necessárias para proteger a confidencialidade, a integridade e a disponibilidade das suas informações pessoais no GitHub e para proteger a resiliência dos nossos servidores. | -| [Práticas globais de privacidade do GitHub](#githubs-global-privacy-practices) | Fornecemos os mesmos altos padrões de proteção de privacidade a todos os nossos usuários em todo o mundo. | -| [Nossa comunicação com você](#how-we-communicate-with-you) | Nossa comunicação com você ocorrerá por e-mail. É possível controlar os nossos meios de contato com você nas configurações da sua conta. | -| [Resolução de conflitos](#resolving-complaints) | Na hipótese improvável de sermos incapazes de resolver um problema de privacidade de dados de forma rápida e detalhada, indicaremos um caminho para a resolução de litígios. | -| [Mudanças nesta Declaração de Privacidade](#changes-to-our-privacy-statement) | Você receberá notificações sobre mudanças concretas nesta Declaração de Privacidade 30 dias antes de tais mudanças entrarem em vigor. Também é possível acompanhar as mudanças no nosso repositório da Política do Site. | -| [Licença](#license) | Esta Declaração de Privacidade é licenciada sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). | -| [Contato com a GitHub](#contacting-github) | Entre em contato em caso de dúvidas sobre a nossa Declaração de Privacidade. | -| [Traduções](#translations) | Acesse os links para consultar algumas traduções da Declaração de Privacidade. | +| Seção | Conteúdo | +| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [Que tipo de informação o GitHub coleta](#what-information-github-collects) | O GitHub coleta informações diretamente de você para fins de registro, pagamento, transações e perfil de usuário. Também coletamos automaticamente cookies e informações do dispositivo das suas informações de uso, sujeito, quando necessário, ao seu consentimento. O GitHub também pode coletar Informações Pessoais de Usuário de terceiros. Coletamos somente a quantidade mínima de informações pessoais necessárias de você, a menos que você decida compartilhar mais informações. | +| [Que tipo de informação o GitHub _não_ coleta](#what-information-github-does-not-collect) | Não coletamos informações de crianças com menos de 13 anos nem coletamos [Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/). | +| [Como o GitHub usa suas informações](#how-github-uses-your-information) | Nesta seção, descrevemos as formas como usamos suas informações, inclusive para fornecer o Serviço, para nos comunicarmos com você, para fins de segurança e conformidade, e para melhorar nosso Serviço. A seção também descreve a base jurídica na qual processamos suas informações quando tal processamento for exigido por lei. | +| [Como compartilhamos as informações obtidas](#how-we-share-the-information-we-collect) | Podemos compartilhar suas informações com terceiros diante de uma das seguintes circunstâncias: com seu consentimento, com nossos prestadores de serviços para fins de segurança, para cumprir as nossas obrigações legais, ou quando houver mudança de controle ou venda de entidades corporativas ou unidades de negócios. Não vendemos suas informações pessoais e não hospedamos anúncios no GitHub. Consulte uma lista de prestadores de serviços que acessam suas informações. | +| [Outras informações importantes](#other-important-information) | Oferecemos informações adicionais específicas relacionadas a conteúdo de repositórios, informações públicas e Organizações no GitHub. | +| [Serviços adicionais](#additional-services) | Oferecemos informações sobre ofertas de serviço adicionais, inclusive aplicativos de terceiros, GitHub Pages e aplicativos do GitHub. | +| [Como você pode acessar e controlar as informações obtidas](#how-you-can-access-and-control-the-information-we-collect) | Propomos algumas medidas para você acessar, alterar ou excluir suas informações pessoais. | +| [Uso de cookies e rastreamento](#our-use-of-cookies-and-tracking) | Nós só usamos cookies estritamente necessários para fornecer, proteger e melhorar nosso serviço. Temos uma página que torna o processo bastante transparente. Veja mais detalhes nesta seção. | +| [Como o GitHub protege suas informações](#how-github-secures-your-information) | Tomamos todas as medidas razoavelmente necessárias para proteger a confidencialidade, a integridade e a disponibilidade das suas informações pessoais no GitHub e para proteger a resiliência dos nossos servidores. | +| [Práticas globais de privacidade do GitHub](#githubs-global-privacy-practices) | Fornecemos os mesmos altos padrões de proteção de privacidade a todos os nossos usuários em todo o mundo. | +| [Nossa comunicação com você](#how-we-communicate-with-you) | Nossa comunicação com você ocorrerá por e-mail. É possível controlar os nossos meios de contato com você nas configurações da sua conta. | +| [Resolução de conflitos](#resolving-complaints) | Na hipótese improvável de sermos incapazes de resolver um problema de privacidade de dados de forma rápida e detalhada, indicaremos um caminho para a resolução de litígios. | +| [Mudanças nesta Declaração de Privacidade](#changes-to-our-privacy-statement) | Você receberá notificações sobre mudanças concretas nesta Declaração de Privacidade 30 dias antes de tais mudanças entrarem em vigor. Também é possível acompanhar as mudanças no nosso repositório da Política do Site. | +| [Licença](#license) | Esta Declaração de Privacidade é licenciada sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). | +| [Contato com a GitHub](#contacting-github) | Entre em contato em caso de dúvidas sobre a nossa Declaração de Privacidade. | +| [Traduções](#translations) | Acesse os links para consultar algumas traduções da Declaração de Privacidade. | ## Declaração de Privacidade do GitHub @@ -75,7 +75,7 @@ Se você tiver uma Conta paga conosco, se vender um aplicativo no [GitHub Market Se você acessar nosso Serviço ou Site, coletaremos automaticamente as mesmas informações básicas coletadas pela maioria dos serviços, sujeitando-nos ao seu consentimento, quando necessário. A coleta inclui informações sobre o seu uso do Serviço, como as páginas que você visualiza, o site referenciado, seu endereço IP, informações da sessão, e a data e hora de cada solicitação. Essas informações são obtidas igualmente de todos os visitantes do Site, independentemente de terem Conta ou não. Esses dados podem incluir Informações Pessoais de Usuário. ##### Cookies -As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service. +Conforme descrito abaixo, coletamos informações automaticamente dos cookies (como ID de cookie e configurações) para manter você conectado, lembrar suas preferências, identificar você e o seu dispositivo e para analisar o seu uso dos nossos serviços. ##### Informações do dispositivo Podemos coletar determinadas informações sobre o seu dispositivo, como endereço IP, dados de navegador ou aplicativo cliente, preferências de idioma, sistema operacional, versão de aplicativo, tipo e ID de dispositivo, e modelo e fabricante de dispositivo. Esses dados podem incluir Informações Pessoais de Usuário. @@ -235,11 +235,11 @@ Com isso, o endereço de e-mail que você informou [nas suas configurações de #### Cookies -GitHub only uses strictly necessary cookies. Cookies são pequenos arquivos de texto que os sites costumam armazenar nos discos rígidos de computadores ou dispositivos móveis de visitantes. +O GitHub só usa cookies estritamente necessários. Cookies são pequenos arquivos de texto que os sites costumam armazenar nos discos rígidos de computadores ou dispositivos móveis de visitantes. -We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers. +Usamos apenas cookies para fornecer, proteger e melhorar nossos serviços. Por exemplo, nós os usamos para manter você conectado, lembrar as suas preferências, identificar o seu dispositivo para fins de segurança, analisar o uso do nosso serviço, compilar relatórios estatísticos e fornecer informações para o desenvolvimento futuro do GitHub. Usamos os nossos próprios cookies para fins de análise, mas não utilizamos quaisquer provedores de serviços de análise de terceiros. -By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service. +Ao usar o nosso serviço, você concorda que podemos colocar esses tipos de cookies no seu computador ou dispositivo. Se você desabilitar o navegador ou a capacidade de o dispositivo de aceitar esses cookies, você não poderá efetuar o login nem usar nosso serviço. Fornecemos mais informações sobre [cookies no GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) na nossa página [Subprocessadores e Cookies do GitHub](/github/site-policy/github-subprocessors-and-cookies) que descreve os cookies que definimos, a necessidade que temos para esses cookies e a expiração desses cookies. diff --git a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md index 8738ffd486..62cc0585b7 100644 --- a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Entrada em vigor: **30 de dezembro de 2020** +Effective date: **January 29, 2021** O GitHub fornece um grande acordo de transparência em relação à forma como usamos seus dados, como os coletamos e com quem compartilhamos. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -18,31 +18,26 @@ O GitHub fornece um grande acordo de transparência em relação à forma como u Quando compartilhamos suas informações com terceiros subprocessadores, tais como nossos fornecedores e provedores de serviços, permanecemos responsáveis por elas. Trabalhamos muito duro para manter sua confiança quando trazemos novos fornecedores, e exigimos que todos os fornecedores se submetam a contratos de proteção de dados conosco que restringem seu processamento de Informações Pessoais dos Usuários (conforme definido na [Declaração de Privacidade](/articles/github-privacy-statement/)). -| Nome do subprocessador | Descrição do processamento | Local do Processamento | Localização corporativa | -|:---------------------- |:--------------------------------------------------------------------- |:---------------------- |:----------------------- | -| Automattic | Serviço de blogs | Estados Unidos | Estados Unidos | -| AWS Amazon | Hospedagem de dados | Estados Unidos | Estados Unidos | -| Braintree (PayPal) | Processador de pagamento de assinatura com cartão de crédito | Estados Unidos | Estados Unidos | -| Clearbit | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | -| Discourse | Provedor de software do fórum comunitário | Estados Unidos | Estados Unidos | -| DiscoverOrg | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | -| Eloqua | Automatização da campanha marketing | Estados Unidos | Estados Unidos | -| Google Apps | Infraestrutura interna da empresa | Estados Unidos | Estados Unidos | -| Google Analytics | Análise e desempenho | Estados Unidos | Estados Unidos | -| LinkedIn Navigator | Data enrichment service | Estados Unidos | Estados Unidos | -| Magic Robot | Relatórios de campanha (Complemento para Vendas) | Estados Unidos | Estados Unidos | -| MailChimp | Fornecedor de serviços de correio para emissão de bilhetes a clientes | Estados Unidos | Estados Unidos | -| Mailgun | Provedor de serviços de correio transacional | Estados Unidos | Estados Unidos | -| Microsoft | Microsoft Services | Estados Unidos | Estados Unidos | -| Monday.com | Colaboração da equipe e plataforma de gerenciamento de projetos | Estados Unidos | Israel | -| Nexmo | Provedor de notificação de SMS | Estados Unidos | Estados Unidos | -| Salesforce.com | Gerenciamento de relacionamento com clientes | Estados Unidos | Estados Unidos | -| Sendgrid | Provedor de serviços de correio transacional | Estados Unidos | Estados Unidos | -| Sentry.io | Provedor de monitoramento de aplicativo | Estados Unidos | Estados Unidos | -| Stripe | Provedor de pagamentos | Estados Unidos | Estados Unidos | -| Twilio | Provedor de notificação de SMS | Estados Unidos | Estados Unidos | -| Zendesk | Sistema de bilhetagem de suporte ao cliente | Estados Unidos | Estados Unidos | -| Zuora | Sistema de faturamento corporativo | Estados Unidos | Estados Unidos | +| Nome do subprocessador | Descrição do processamento | Local do Processamento | Localização corporativa | +|:------------------------ |:--------------------------------------------------------------------- |:---------------------- |:----------------------- | +| Automattic | Serviço de blogs | Estados Unidos | Estados Unidos | +| AWS Amazon | Hospedagem de dados | Estados Unidos | Estados Unidos | +| Braintree (PayPal) | Processador de pagamento de assinatura com cartão de crédito | Estados Unidos | Estados Unidos | +| Clearbit | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | +| Discourse | Provedor de software do fórum comunitário | Estados Unidos | Estados Unidos | +| Eloqua | Automatização da campanha marketing | Estados Unidos | Estados Unidos | +| Google Apps | Infraestrutura interna da empresa | Estados Unidos | Estados Unidos | +| MailChimp | Fornecedor de serviços de correio para emissão de bilhetes a clientes | Estados Unidos | Estados Unidos | +| Mailgun | Provedor de serviços de correio transacional | Estados Unidos | Estados Unidos | +| Microsoft | Microsoft Services | Estados Unidos | Estados Unidos | +| Monday.com | Colaboração da equipe e plataforma de gerenciamento de projetos | Estados Unidos | Israel | +| Nexmo | Provedor de notificação de SMS | Estados Unidos | Estados Unidos | +| Salesforce.com | Gerenciamento de relacionamento com clientes | Estados Unidos | Estados Unidos | +| Sentry.io | Provedor de monitoramento de aplicativo | Estados Unidos | Estados Unidos | +| Stripe | Provedor de pagamentos | Estados Unidos | Estados Unidos | +| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | Estados Unidos | Estados Unidos | +| Zendesk | Sistema de bilhetagem de suporte ao cliente | Estados Unidos | Estados Unidos | +| Zuora | Sistema de faturamento corporativo | Estados Unidos | Estados Unidos | Quando trouxermos um novo subprocessador que lida com as Informações Pessoais de nossos Usuários, ou removermos um subprocessador, ou mudarmos a forma como usamos um subprocessador, atualizaremos esta página. Se você tiver dúvidas ou preocupações sobre um novo subprocessador, ficaremos felizes em ajudar. Entre em contato conosco via {% data variables.contact.contact_privacy %}. @@ -50,7 +45,7 @@ Quando trouxermos um novo subprocessador que lida com as Informações Pessoais GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Consulte nossa [Declaração de privacidade](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) se você quiser saber mais informações sobre cookies e sobre como e por que os usamos. -Como o número e os nomes dos cookies podem mudar, a tabela abaixo pode ser atualizada de vez em quando. +Since the number and names of cookies may change, the table below may be updated from time to time. | Provedor de serviço | Nome do cookie | Descrição | Vencimento* | |:------------------- |:------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- | diff --git a/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index f6143c9435..74c0406bb3 100644 --- a/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ Por favor, note que a informação disponível varia de caso a caso. Algumas das ### Reembolso de custos -Reservamo-nos o direito de solicitar o reembolso dos custos administrativos associados à resposta aos pedidos de informação, tal como permitido pela lei. +Nos termos das leis estadual e federal, o GitHub pode pedir reembolso por custos associados à conformidade com uma demanda legal válida, como uma intimação, ordem de tribunal ou mandado de busca. Só cobramos a recuperação de alguns custos, e estes reembolsos cobrem apenas uma parte dos custos que efetivamente incorremos para cumprir as disposições legais. + +Embora não cobremos em situações de emergência ou em outras circunstâncias exigentes, buscamos o reembolso para todas as outras solicitações legais, de acordo com o cronograma a seguir, a menos que exigido de outra forma por lei: + +- Pesquisa inicial de até 25 identificadores: livre +- Produção de informação/dados de assinantes para até 5 contas: grátis +- Produção de informação/dados de assinante para mais de 5 contas: US$ 20 por conta +- Pesquisas secundárias: US$ 10 por pesquisa ### Conservação de dados diff --git a/translations/pt-BR/content/github/site-policy/index.md b/translations/pt-BR/content/github/site-policy/index.md index 61457e9ae8..35e6ed0bf8 100644 --- a/translations/pt-BR/content/github/site-policy/index.md +++ b/translations/pt-BR/content/github/site-policy/index.md @@ -13,17 +13,8 @@ versions: {% link_in_list /github-terms-of-service %} {% link_in_list /github-corporate-terms-of-service %} {% link_in_list /github-privacy-statement %} -{% link_in_list /github-data-protection-addendum %} {% link_in_list /global-privacy-practices %} -{% link_in_list /github-enterprise-server-license-agreement %} -{% link_in_list /github-ae-data-protection-agreement %} -{% link_in_list /github-ae-product-specific-terms %} -{% link_in_list /github-enterprise-service-level-agreement %} -{% link_in_list /github-connect-addendum-to-the-github-enterprise-license-agreement %} -{% link_in_list /github-supplemental-terms-for-microsoft-volume-licensing %} -{% link_in_list /github-enterprise-subscription-agreement %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} -{% link_in_list /github-enterprise-cloud-evaluation-agreement %} {% link_in_list /github-sponsors-additional-terms %} {% link_in_list /github-additional-product-terms %} {% link_in_list /github-logo-policy %} @@ -37,7 +28,6 @@ versions: {% link_in_list /github-subprocessors-and-cookies %} {% link_in_list /github-bug-bounty-program-legal-safe-harbor %} {% link_in_list /responsible-disclosure-of-security-vulnerabilities %} -{% link_in_list /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users %} {% link_in_list /guidelines-for-legal-requests-of-user-data %} {% link_in_list /github-government-takedown-policy %} {% link_in_list /github-acceptable-use-policies %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index 9525f6ca64..6919940a39 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -22,7 +22,7 @@ versions: {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} -### Editing or retiring a tier +### Editando ou retirar uma camada {% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 19af563a9a..40e7421eef 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -7,32 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' -permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. +permissions: Qualquer pessoa pode patrocinar contas em nome da própria conta de usuário. Os proprietários e gerentes de faturamento da organização podem patrocinar contas em nome de sua organização. --- {% data reusables.sponsors.org-sponsors-release-phase %} -### About sponsorships +### Sobre patrocínios {% data reusables.sponsors.sponsorship-details %} -You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. -- Sustaining specific libraries that your organization's work depends on -- Investing in the ecosystem you rely on as a organization (such as blockchain) -- Developing brand awareness as an organization that values open source -- Thanking open source developers for building libraries that complement the product your organization offers +Você pode patrocinar uma conta em nome de sua conta de usuário para investir em projetos dos quais você se beneficia pessoalmente. Você pode patrocinar uma conta em nome de sua organização por muitas razões. +- Sustentar bibliotecas específicas das quais o trabalho da sua organização depende +- Investir no ecossistema com o qual você conta como uma organização (como a blockchain) +- Desenvolver a conscientização da marca como uma organização que valoriza o código aberto +- Agradecer aos desenvolvedores de código aberto para a criação de bibliotecas que complementam os produtos que a sua organização oferece -You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +Você pode usar um cartão de crédito para patrocinar uma conta em {% data variables.product.product_name %}. Se sua organização desejar pagar por fatura, [entre em contato conosco](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". -When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} +Ao patrocinar uma conta usando um cartão de crédito, a alteração entrará em vigor imediatamente. {% data reusables.sponsors.prorated-sponsorship %} {% data reusables.sponsors.manage-updates-for-orgs %} -If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". +Se a conta patrocinada for retirada, a sua camada permanecerá em vigor para você até que você escolha uma camada diferente ou cancele a sua assinatura. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". -If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_sponsors %} para a sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" e "[Configurando {% data variables.product.prodname_sponsors %} para sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." +Se a conta que você deseja patrocinar não tiver um perfil em {% data variables.product.prodname_sponsors %}, você pode incentivar que participe. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_sponsors %} para a sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" e "[Configurando {% data variables.product.prodname_sponsors %} para sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -42,15 +42,15 @@ If the account you want to sponsor does not have a profile on {% data variables. {% endnote %} -### Sponsoring an account +### Patrocinar uma conta -Before you can sponsor an account, you must have a verified email address. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)". +Antes de poder patrocinar uma conta, você deve ter um endereço de e-mail verificado. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)". -1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. -1. Navigate to your sponsorship dashboard for the account. - - To sponsor a developer, under the developer's name, click **Sponsor**. ![Botão Sponsor (Patrocinar)](/assets/images/help/profile/sponsor-button.png) - - To sponsor an organization, to the right of the the organization's name, click **Sponsor**. ![Botão Sponsor (Patrocinar)](/assets/images/help/sponsors/sponsor-org-button.png) -1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) +1. Em {% data variables.product.product_name %}, acesse o perfil do usuário ou organização que deseja patrocinar. +1. Acesse o painel de patrocínio para a conta. + - Para patrocinar um desenvolvedor, sob o nome do desenvolvedor, clique em **Patrocinador**. ![Botão Sponsor (Patrocinar)](/assets/images/help/profile/sponsor-button.png) + - Para patrocinar uma organização, à direita do nome da organização, clique em **Patrocinador**. ![Botão Sponsor (Patrocinar)](/assets/images/help/sponsors/sponsor-org-button.png) +1. Opcionalmente, no lado direito da página, para patrocinar a conta em nome da sua organização, use o menu suspenso **Patrocinar como** e clique na organização. ![Menu suspenso para escolher a conta que você irá patrocinar como](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 200240de30..3360c4edcb 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -19,13 +19,13 @@ Você pode ver a análise sobre seus patrocínios atuais e anteriores, os pagame ### Visualizando atividade de patrocínio recente {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -1. Na barra lateral esquerda, clique em **Atividade**. ![Aba de atividade](/assets/images/help/sponsors/activity-tab.png) +{% data reusables.sponsors.activity-tab %} ### Exportando seus dados de patrocínio -Se você tiver patrocinadores, você poderá exportar os seus dados de patrocínio. {% data variables.product.prodname_dotcom %} enviará um e-mail com os dados de exportação de todos os seus patrocinadores para o mês que você selecionar. Depois que a exportação estiver concluída, você poderá exportar mais um mês de dados. Você pode exportar até 10 conjuntos de dados por hora para qualquer uma das suas contas patrocinadas. +Você pode exportar suas transações de patrocínio por mês. {% data variables.product.company_short %} enviará um e-mail com dados de transação para todos os seus patrocinadores do mês que você selecionar. Depois que a exportação estiver concluída, você poderá exportar mais um mês de dados. Você pode exportar até 10 conjuntos de dados por hora para qualquer uma das suas contas patrocinadas. {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Clique em **Exportar tudo**. ![Botão Exportar tudo](/assets/images/help/sponsors/export-all.png) +{% data reusables.sponsors.activity-tab %} +1. Clique em {% octicon "download" aria-label="The download icon" %} **Exportar**. ![Botão de exportação](/assets/images/help/sponsors/export-all.png) 1. Escolha um período de tempo e um formato para os dados que você gostaria de exportar, e clique em **Iniciar a exportação**. ![Opções de Exportar dados](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md index 301577ca6b..5338ab78be 100644 --- a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md @@ -21,7 +21,7 @@ Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gr {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) +4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) ### Leia mais diff --git a/translations/pt-BR/content/github/using-git/adding-a-remote.md b/translations/pt-BR/content/github/using-git/adding-a-remote.md index c689c24f72..a5d34379d9 100644 --- a/translations/pt-BR/content/github/using-git/adding-a-remote.md +++ b/translations/pt-BR/content/github/using-git/adding-a-remote.md @@ -37,7 +37,7 @@ Você pode se deparar com estes erros ao tentar adicionar um remote. Esse erro significa que você tentou adicionar um remote com um nome que já existe no repositório local: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife +$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` diff --git a/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md b/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md index 0799f74ad2..8d812510f8 100644 --- a/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/pt-BR/content/github/using-git/using-git-rebase-on-the-command-line.md @@ -124,7 +124,11 @@ Como antes, o Git mostra a mensagem do commit para você editar. Altere o texto Como você alterou o histórico do Git, o `git push origin` normal **não** funcionará. É preciso modificar o comando forçando o push das alterações mais recentes: ```shell -$ git push origin master --force +# Don't override changes +$ git push origin main --force-with-lease + +# Override changes +$ git push origin main --force ``` {% warning %} diff --git a/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md b/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md index 73bbd36def..7ce1672054 100644 --- a/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/pt-BR/content/github/using-git/which-remote-url-should-i-use.md @@ -16,7 +16,7 @@ Para obter informações sobre como configurar ou alterar URL remota, consulte " ### Clonando com as URLs de HTTPS -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. +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. 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 %} diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index 060f2c6e1e..46b5b65d1d 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -82,22 +82,22 @@ Você também pode habilitar ou desabilitar o gráfico de dependências para tod Você pode desabilitar o gráfico de dependências a qualquer momento clicando em **Desabilitar** ao lado de "Gráfico de dependência" na aba de análise & de Segurança &. -### Changing the "Used by" package +### Alterar o pacote "Usado por" -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)." +Se o gráfico de dependências estiver habilitado e o seu repositório contiver um pacote publicado em um ecossistema de pacote compatível, {% data variables.product.prodname_dotcom %} exibirá uma seção "Usado por" na barra lateral da aba do **Código** do seu repositório. Para obter mais informações sobre os ecossistemas de pacotes compatíveis, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". -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. +A seção "Usado por" mostra o número de referências públicas ao pacote que foi encontrado, e exibe os avatares de alguns dos proprietários dos projetos dependentes. -!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png) +![Seção da barra lateral "Usado por"](/assets/images/help/repository/used-by-section.png) -Clicking any item in this section takes you to the **Dependents** tab of the dependency graph. +Clicar em qualquer item desta seção irá levar você para a aba **Dependentes** do gráfico de dependências. -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. +A seção "Usado por" representa um único pacote do repositório. Se você tiver permissões de administrador em um repositório que contém vários pacotes, você poderá escolher qual pacote a seção "Usado por" representa. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -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) +4. Em "Configure as funcionalidades de segurança e análise", clique no menu suspenso na seção "Usados pelo contador" e escolha um pacote. ![Escolha um pacote "Usado por"](/assets/images/help/repository/choose-used-by-package.png) {% endif %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index df4c0cf6a5..4a98d89f91 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ O Jekyll não é oficialmente compatível com o Windows. Para obter mais informa Algumas definições de configuração não podem ser alteradas para sites do {% data variables.product.prodname_pages %}. -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ Por padrão, blocos de código no seu site serão destacados pelo Jekyll. O Jeky Se quiser usar outro realçador, como `highlight.js`, você deverá desabilitar o realce da sintaxe do Jekyll atualizando o arquivo *_config.yml* do projeto. -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md index a4b5098601..80ddb5b9f6 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/pt-BR/content/github/working-with-github-pages/about-github-pages.md @@ -25,11 +25,15 @@ Você pode hospedar seu site em no domínio `github.io` de {% data variables.product.prodname_dotcom %}de `github.io` ou no seu próprio domínio personalizado. Para obter mais informações, consulte "[Usar um domínio personalizado com o {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)". {% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} Para obter mais informações, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + Para começar, consulte "[Criar um site do {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)". -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Os proprietários da organização podem desabilitar a publicação de -sites de {% data variables.product.prodname_pages %} nos repositórios da organização. Para obter mais informações, consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". +sites de {% data variables.product.prodname_pages %} nos repositórios da organização. Para obter mais informações, consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". {% endif %} ### Tipos de site do {% data variables.product.prodname_pages %} @@ -40,6 +44,10 @@ Para publicar um site de usuário, você deve criar um repositório pertencente Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% if currentVersion == "free-pro-team@latest" %}A menos que você esteja usando um domínio personalizado, os sites de projeto estão disponíveis em `http(s)://.github.io/` ou `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Os sites de projeto estão disponíveis em `http(s)://pages.///` ou `http(s)://pages.///`.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +Se você publicar seu site em particularmente, a URL do seu site será diferente. Para obter mais informações, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} Para obter mais informações sobre como os domínios personalizados afetam o URL do seu site, consulte "[Sobre domínios personalizados e {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". {% endif %} @@ -57,7 +65,7 @@ A URL em que o site está disponível depende da habilitação do isolamento de `http(s)://pages./` | `http(s):///pages/` | Organization | `http(s)://pages./` | `http(s):///pages/` | Site do projeto pertencente a uma conta do usuário | `http(s)://pages.///` | `http(s):///pages///` Site do projeto pertencente a uma conta da organização | `http(s)://pages.///` | `http(s):///pages///` -Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" ou contate o administrador do site. +Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" ou entre em contato com o administrador do site. {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -90,9 +98,9 @@ A fonte de publicação padrão para um site de projeto é o branch `gh-pages`. Os sites de projeto também podem ser publicados do branch `master` ou de uma pasta `/docs` no branch `master`. Para publicar o site de uma dessas fontes, é preciso configurar uma fonte de publicação diferente. Para obter mais informações, consulte "[Configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". - Se você escolher a pasta `/docs` do branch `master` como fonte de publicação, {% data variables.product.prodname_pages %} lerá tudo para publicar o seu site{% if currentVersion == "free-pro-team@latest" %}, incluindo o arquivo _CNAME_ {% endif %} da pasta `/docs`.{% if currentVersion == "free-pro-team@latest" %} Por exemplo, ao editar o seu domínio personalizado através das configurações de {% data variables.product.prodname_pages %}, o domínio personalizado escreverá a `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, 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 %} +Se você escolher a pasta `/docs` do branch `master` como fonte de publicação, {% data variables.product.prodname_pages %} lerá tudo para publicar o seu site{% if currentVersion == "free-pro-team@latest" %}, incluindo o arquivo _CNAME_ {% endif %} da pasta `/docs`.{% if currentVersion == "free-pro-team@latest" %} Por exemplo, ao editar o seu domínio personalizado através das configurações de {% data variables.product.prodname_pages %}, o domínio personalizado escreverá a `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, 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 %} - Você não pode publicar seu site de projeto de qualquer outro branch, mesmo que o branch padrão não seja `master` ou `gh-pages`. +Você não pode publicar seu site de projeto de qualquer outro branch, mesmo que o branch padrão não seja `master` ou `gh-pages`. {% endif %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index 9412801a23..5735fbbf24 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/pt-BR/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ Quando você fizer push das alterações na fonte de publicação no {% data var Você pode configurar um serviço de terceiros, como o [Travis CI](https://travis-ci.org/), para exibir mensagens de erro após cada commit. 1. Se você ainda não tiver, adicione um arquivo chamado _Gemfile_ na raiz da sua fonte de publicação, com o seguinte conteúdo: - ``` + ```ruby source `https://rubygems.org` gem `github-pages` ``` 2. Configure o repositório do site para o serviço de teste de sua escolha. Por exemplo, para usar [Travis CI](https://travis-ci.org/), adicione um arquivo chamado _.travis.yml_ na raiz da fonte de publicação, com o seguinte conteúdo: - ``` + ```yaml language: ruby rvm: - 2.3 diff --git a/translations/pt-BR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index a7b1980e56..2a8e3ba5e5 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ Pessoas com permissões de gravação para um repositório podem adicionar um te {% data reusables.pages.navigate-publishing-source %} 1. Crie um novo arquivo chamado _/assets/css/style.scss_. 2. Adicione o seguinte conteúdo ao topo do arquivo: - ``` + ```scss --- --- diff --git a/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 7cfca48654..6163be6f1b 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -62,6 +62,8 @@ O tema engloba layouts, inclusões e folhas de estilo padrão que serão aplicad {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +Seu post já deve estar no seu site! Se a URL de base do seu site for `https://octocat.github.io`, o seu novo post estará localizado em `https://octocat.github.io/YYYY/MM/DD/TITLE.html`. + ### Próximas etapas {% data reusables.pages.add-jekyll-theme %} Para obter mais informações, consulte "[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". diff --git a/translations/pt-BR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/pt-BR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..1f890ebae3 --- /dev/null +++ b/translations/pt-BR/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: Alterar a visibilidade do site do GitHub Pages +intro: 'Você pode gerenciar o controle de acesso no seu site de projeto publicando o site publicamente ou privadamente.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: As pessoas com permissões de administrador em um repositório podem alterar a visibilidade de um site de {% data variables.product.prodname_pages %} +--- + +### Sobre controle de acesso para sites de {% data variables.product.prodname_pages %} + +Se o seu site de projeto for publicado de um repositório privado ou interno, pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. Com controle de acesso, você pode optar por publicar o site publicamente para qualquer pessoa na internet ou em particular para pessoas com acesso de leitura ao seu repositório. Um site publicado de forma privada pode ser usado para compartilhar sua documentação interna ou base de conhecimento com integrantes da sua empresa. Você não pode gerenciar o controle de acesso para um site da organização. Para obter mais informações sobre os tipos de sites de sites de {% data variables.product.prodname_pages %}, consulte "[Sobre o GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". + +Os sites publicados em particular estão disponíveis em um subdomínio diferente dos sites publicados em modo público. Você pode ver a URL do site nas configurações do repositório. Se você estiver usando um gerador de site estático configurado para criar o site com o nome do repositório como um caminho, talvez seja necessário atualizar as configurações para o gerador do site estático ao alterar o site para privado. Para obter mais informações, consulte "[Configurar o Jekyll no seu site de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" ou a documentação para o gerador do seu site estático. + +### Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Em "{% data variables.product.prodname_pages %}", selecione o ** visibilidade de {% data variables.product.prodname_pages %}** no menu suspenso e, em seguida, clique em uma visibilidade. ![Menu suspenso para escolher uma visibilidade para o seu site](/assets/images/help/pages/public-or-private-visibility.png) +4. Para ver seu site publicado, em "{% data variables.product.prodname_pages %}", clique na URL do seu site. ![URL do seu site publicado em modo particular](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/pt-BR/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index 00f3c3b033..deed977fc8 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/pt-BR/content/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -34,4 +34,4 @@ Antes de configurar uma fonte de publicação, certifique-se o branch{% if curre {% data reusables.pages.admin-must-push %} -If you choose the `docs` folder on {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}any{% else %}the `master`{% endif %} branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. Para obter informações, consulte [Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". +Se você escolher a pasta `docs` em {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}qualquer branch{% else %}ou `branch mestre`{% endif %} como fonte de publicação e eliminar a pasta `/docs` do branch do repositório, seu site não será criado e você receberá uma mensagem de erro de criação de página referente a uma pasta `/docs` ausente. Para obter informações, consulte [Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". diff --git a/translations/pt-BR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/pt-BR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 60a7832815..202e9bd9b0 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/pt-BR/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. No campo de nome de arquivo, digite `404.html` ou `404.md`. ![Campo de nome de arquivo](/assets/images/help/pages/404-file-name.png) 4. Se você nomeou seu arquivo como `404.md`, adicione a seguinte página inicial YAML no começo do arquivo: - ``` + ```yaml --- permalink: /404.html --- diff --git a/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index c02beb7e31..c75b0a636b 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,6 +11,8 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### Prerequisites Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." @@ -96,7 +98,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md`. +Você pode adicionar mais páginas ao seu site criando novos arquivos. Cada arquivo ficará disponível no site na mesma estrutura de diretórios que a fonte de publicação. Por exemplo, se a fonte de publicação para o seu site de projeto for o branch `gh-pages`, e você criar um novo arquivo chamado `/about/contact-us.md` no branch `gh-pages`, o arquivo estará disponível em {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. Também é possível adicionar um tema para personalizar a aparência do site. Para mais informações consulte {% if currentVersion == "free-pro-team@latest" %}"[Adicionar um tema ao site de {% data variables.product.prodname_pages %} com o seletor de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adicionar um tema ao site de {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." diff --git a/translations/pt-BR/content/github/working-with-github-pages/index.md b/translations/pt-BR/content/github/working-with-github-pages/index.md index 4bcb52d95e..0ae60db7c2 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/index.md +++ b/translations/pt-BR/content/github/working-with-github-pages/index.md @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md b/translations/pt-BR/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md index d0415191be..3d970728ba 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md +++ b/translations/pt-BR/content/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.md @@ -40,7 +40,7 @@ Para configurar um `www` ou subdomínio personalizado, como `www.example.com` ou {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.save-custom-domain %} -5. Navegue até o provedor DNS e crie um registro `CNAME` que aponte seu subdomínio para o domínio padrão do seu site. Por exemplo, se você quiser usar o subdomínio `www.example.com` para seu site de usuário, crie um registro `CNAME` que aponte `www.example.com` para `.github.io`. Se você desejar usar o subdomínio `www.anotherexample.com` no seu site da organização, crie um registro `CNAME` que aponte `www. notherexample.com` para `.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 %} +5. Navegue até o provedor DNS e crie um registro `CNAME` que aponte seu subdomínio para o domínio padrão do seu site. Por exemplo, se você quiser usar o subdomínio `www.example.com` para seu site de usuário, crie um registro `CNAME` que aponte `www.example.com` para `.github.io`. Se você desejar usar o subdomínio `www.anotherexample.com` no seu site da organização, crie um registro `CNAME` que aponte `www. notherexample.com` para `.github.io`. O registro `CNAME` sempre deve apontar para `.github.io` ou `.github.io`, excluindo o nome do repositório. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} {% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %} diff --git a/translations/pt-BR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 3b2bb2212b..e13f4cfdb9 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/pt-BR/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting Jekyll build errors for GitHub Pages sites -intro: 'You can use Jekyll build error messages to troubleshoot problems with your {% data variables.product.prodname_pages %} site.' +title: Solucionar problemas de erros de criação do Jekyll para sites do GitHub Pages +intro: 'Você pode usar mensagens de erro de criação do Jekyll para solucionar problemas com seu site do {% data variables.product.prodname_pages %}.' redirect_from: - /articles/page-build-failed-missing-docs-folder/ - /articles/page-build-failed-invalid-submodule/ @@ -31,158 +31,158 @@ versions: github-ae: '*' --- -### Troubleshooting build errors +### Solucionar problemas de erros de criação -If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you can use error messages to troubleshoot. For more information about error messages and how to view them, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." +Se o Jekyll encontrar um erro ao criar seu site do {% data variables.product.prodname_pages %} localmente ou no {% data variables.product.product_name %}, você poderá usar mensagens de erro para solucionar problemas. Para obter mais informações sobre mensagens de erro e como visualizá-las, consulte "[Sobre erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". -If you received a generic error message, check for common issues. -- You're using unsupported plugins. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% if currentVersion == "free-pro-team@latest" %} -- Your repository has exceeded our repository size limits. For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota)"{% endif %} -- You changed the `source` setting in your *_config.yml* file. {% data variables.product.prodname_pages %} overrides this setting during the build process. -- A filename in your publishing source contains a colon (`:`) which is not supported. +Se você recebeu uma mensagem de erro genérica, verifique os problemas comuns. +- Você está usando plugins incompatíveis. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% if currentVersion == "free-pro-team@latest" %} +- Seu repositório excedeu os limites de tamanho. Para obter mais informações, consulte "[Qual é a minha quota de disco?](/articles/what-is-my-disk-quota)"{% endif %} +- Você alterou a configuração `source` no arquivo *_config.yml*. {% data variables.product.prodname_pages %} substitui essa configuração durante o processo de criação. +- Um nome de arquivo na fonte de publicação contém dois pontos (`:`), o que não é permitido. -If you received a specific error message, review the troubleshooting information for the error message below. +Se você recebeu uma mensagem de erro específica, revise abaixo as informações de solução de problemas relativas à mensagem de erro. -After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}. +Depois que tiver corrigido os possíveis erros, faça push das alterações para a fonte de publicação do seu site para ativar outra criação no {% data variables.product.product_name %}. -### Config file error +### Erro no arquivo de configuração -This error means that your site failed to build because the *_config.yml* file contains syntax errors. +Este erro significa que ocorreu falha na criação do seu site porque o arquivo *_config.yml* contém erros de sintaxe. -To troubleshoot, make sure that your *_config.yml* file follows these rules: +Para solucionar problemas, verifique se o arquivo *_config.yml* segue estas regras: {% data reusables.pages.yaml-rules %} {% data reusables.pages.yaml-linter %} -### Date is not a valid datetime +### Esta é uma data/hora inválida -This error means that one of the pages on your site includes an invalid datetime. +Este erro significa que uma das páginas do seu site inclui uma data/hora inválida. -To troubleshoot, search the file in the error message and the file's layouts for calls to any date-related Liquid filters. Make sure that any variables passed into date-related Liquid filters have values in all cases and never pass `nil` or `""`. For more information, see "[Liquid filters](https://help.shopify.com/en/themes/liquid/filters)" in the Liquid documentation. +Para solucionar problemas, pesquise o arquivo na mensagem de erro e os layouts do arquivo para as exigências de qualquer filtro de data do Liquid. Verifique se alguma variável passada em filtros de data do Liquid tem valores em todos os casos e nunca passa `nil` ou `""`. Para obter mais informações, consulte "[Filtros do Liquid](https://help.shopify.com/en/themes/liquid/filters)" na documentação do Liquid. -### File does not exist in includes directory +### O arquivo não existe no diretório includes -This error means that your code references a file that doesn't exist in your *_includes* directory. +Este erro significa que o código faz referência a um arquivo que não existe no diretório *_includes*. -{% data reusables.pages.search-for-includes %} If any of the files you've referenced aren't in the *_includes* directory, copy or move the files into the *_includes* directory. +{% data reusables.pages.search-for-includes %} Se algum dos arquivos a que você fez referência não estiver no diretório *_includes*, copie ou mova os arquivos para o diretório *_includes*. -### File is a symlink +### O arquivo é um link simbólico -This error means that your code references a symlinked file that does not exist in the publishing source for your site. +Este erro significa que o código faz referência a um arquivo com link simbólico que não existe na fonte de publicação do seu site. -{% data reusables.pages.search-for-includes %} If any of the files you've referenced are symlinked, copy or move the files into the *_includes* directory. +{% data reusables.pages.search-for-includes %} Se algum dos arquivos a que você fez referência for com link simbólico, copie ou mova os arquivos para o diretório *_includes*. -### File is not properly UTF-8 encoded +### Arquivo codificado por UTF-8 incorretamente -This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols. +Este erro significa que você usou caracteres não latinos, como `日本語`, sem avisar ao computador que esperava esses símbolos. -To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file: -``` +Para solucionar problemas, force a codificação UTF-8 adicionando a seguinte linha ao arquivo *_config.yml*: +```yaml encoding: UTF-8 ``` -### Invalid highlighter language +### Linguagem inválida do realçador -This error means that you specified any syntax highlighter other than [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/) in your configuration file. +Este erro significa que você especificou algum realçador de sintaxe diferente de [Rouge](https://github.com/jneen/rouge) ou [Pygments](http://pygments.org/) no arquivo de configuração. -To troubleshoot, update your *_config.yml* file to specify [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/). For more information, see "[About {% data variables.product.product_name %} and Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)." +Para solucionar problemas, atualize o arquivo *_config.yml* para especificar [Rouge](https://github.com/jneen/rouge) ou [Pigmentos](http://pygments.org/). Para obter mais informações, consulte "[Sobre o {% data variables.product.product_name %} e o Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)". -### Invalid post date +### Data de postagem inválida -This error means that a post on your site contains an invalid date in the filename or YAML front matter. +Este erro significa que uma postagem no seu site contém uma data inválida no nome de arquivo ou na página inicial YAML. -To troubleshoot, make sure all dates are formatted as YYYY-MM-DD HH:MM:SS for UTC and are actual calendar dates. To specify a time zone with an offset from UTC, use the format YYYY-MM-DD HH:MM:SS +/-TTTT, like `2014-04-18 11:30:00 +0800`. +Para solucionar problemas, verifique se todas as datas estão no formato YYYY-MM-DD HH:MM:SS para UTC e se são datas reais do calendário. Para especificar um fuso horário com um intervalo de tempo UTC, use o formato YYYY-MM-DD HH:MM:SS +/-TTTT (ano-mês-dia horas:minutos:segundos +/-TTTT), como `2014-04-18 11:30:00 +0800`. -If you specify a date format in your *_config.yml* file, make sure the format is correct. +Se você especificar um formato de data no arquivo *_config.yml*, verifique se o formato está correto. -### Invalid Sass or SCSS +### SCSS ou Sass inválido -This error means your repository contains a Sass or SCSS file with invalid content. +Este erro significa que seu repositório contém um arquivo Sass ou SCSS com conteúdo inválido. -To troubleshoot, review the line number included in the error message for invalid Sass or SCSS. To help prevent future errors, install a Sass or SCSS linter for your favorite text editor. +Para solucionar problemas, revise o número de linha incluído na mensagem de erro referente a Sass ou SCSS inválido. Para ajudar a prevenir erros no futuro, instale um linter Sass ou SCSS para seu editor de texto favorito. -### Invalid submodule +### Submódulo inválido -This error means that your repository includes a submodule that hasn't been properly initialized. +Este erro significa que seu repositório inclui um submódulo que não foi inicializado corretamente. {% data reusables.pages.remove-submodule %} -If do you want to use the submodule, make sure you use `https://` when referencing the submodule (not `http://`) and that the submodule is in a public repository. +Caso queira utilizar o submódulo, lembre-se de usar `https://` quando fizer referência ao submódulo (a não `http://`) e de que o submódulo está em um repositório público. -### Invalid YAML in data file +### YAML inválido no arquivo de dados -This error means that one of more files in the *_data* folder contains invalid YAML. +Este erro significa que um ou mais arquivos na pasta *_data* contém YAML inválido. -To troubleshoot, make sure the YAML files in your *_data* folder follow these rules: +Para solucionar problemas, verifique se os arquivos YAML na pasta *_data* seguem estas regras: {% data reusables.pages.yaml-rules %} {% data reusables.pages.yaml-linter %} -For more information about Jekyll data files, see "[Data Files](https://jekyllrb.com/docs/datafiles/)" in the Jekyll documentation. +Para obter mais informações sobre arquivos de dados do Jekyll, consulte ""[Arquivos de dados](https://jekyllrb.com/docs/datafiles/)" na documentação do Jekyll. -### Markdown errors +### Erros de markdown -This error means that your repository contains Markdown errors. +Este erro significa que seu repositório contém erros de markdown. -To troubleshoot, make sure you are using a supported Markdown processor. For more information, see "[Setting a Markdown processor for your {% data variables.product.prodname_pages %} site using Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)." +Para solucionar problemas, verifique se você está usando um processador markdown compatível. Para obter mais informações, consulte "[Definir um processador markdown para seu site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)". -Then, make sure the file in the error message uses valid Markdown syntax. For more information, see "[Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax)" on Daring Fireball. +Em seguida, verifique se o arquivo na mensagem de erro usa uma sintaxe markdown válida. Para obter mais informações, consulte "[Markdown: sintaxe](https://daringfireball.net/projects/markdown/syntax)" no Daring Fireball. -### Missing docs folder +### Pasta docs ausente -This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch. +Este erro significa que você escolheu a pasta `docs` em um branch como a sua fonte de publicação, mas não há nenhuma pasta de `docs` na raiz do seu repositório naquele branch. -To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. If the `docs` folder was accidentally deleted, you can either: -- Use Git to revert or undo the deletion. For more information, see "[git-revert](https://git-scm.com/docs/git-revert.html)" in the Git documentation. -- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. For more information, see "[Creating new files](/articles/creating-new-files)." -- Change your publishing source. For more information, see "[Configuring a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)." +Para solucionar esse problema, se a pasta `documentação` foi movida acidentalmente, tente mover a pasta `docs` de volta para a raiz do repositório no branch que você escolheu para a sua fonte de publicação. Se a pasta `docs` tiver sido excluída acidentalmente, siga um destes procedimentos: +- Use o Git para reverter ou desfazer a exclusão. Para obter mais informações, consulte "[git-revert](https://git-scm.com/docs/git-revert.html)" na documentação do Git. +- Crie uma nova pasta de `documentação` na raiz do repositório no branch que você escolheu para a sua fonte de publicação e adicione os arquivos de origem do site à pasta. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files)". +- Altere a fonte de publicação. Para obter mais informações, consulte "[Configurar uma fonte de publicação do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)". -### Missing submodule +### Submódulo ausente -This error means that your repository includes a submodule that doesn't exist or hasn't been properly initialized. +Este erro significa que seu repositório inclui um submódulo que não existe ou não foi inicializado corretamente. {% data reusables.pages.remove-submodule %} -If you do want to use a submodule, initialize the submodule. For more information, see "[Git Tools - Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" in the _Pro Git_ book. +Se você quiser usar um submódulo, inicialize-o. Para obter mais informações, consulte "[Ferramentas Git - Submódulos](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" no livro _Pro Git_. -### Relative permalinks configured +### Permalinks relativos configurados -This errors means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your *_config.yml* file. +Este erro significa que você tem permalinks relativos, que não são compatíveis com o {% data variables.product.prodname_pages %} no arquivo *_config.yml*. -Permalinks are permanent URLs that reference a particular page on your site. Absolute permalinks begin with the root of the site, while relative permalinks begin with the folder containing the referenced page. {% data variables.product.prodname_pages %} and Jekyll no longer support relative permalinks. For more information about permalinks, see "[Permalinks](https://jekyllrb.com/docs/permalinks/)" in the Jekyll documentation. +Permalinks são URLs permanentes que fazem referência a uma determinada página no seu site. Os permalinks absolutos iniciam com a raiz do site, enquanto os permalinks relativos iniciam com a pasta que contém a página referenciada. O {% data variables.product.prodname_pages %} e o Jekyll não são mais compatíveis com permalinks relativos. Para obter mais informações sobre permalinks, consulte "[Permalinks](https://jekyllrb.com/docs/permalinks/)" na documentação do Jekyll. -To troubleshoot, remove the `relative_permalinks` line from your *_config.yml* file and reformat any relative permalinks in your site with absolute permalinks. For more information, see "[Editing files in your repository](/articles/editing-files-in-your-repository)." +Para solucionar problemas, remova a linha `relative_permalinks` do arquivo *_config.yml* e reformate os permalinks relativos no site com permalinks absolutos. Para obter mais informações, consulte "[Editar arquivos no repositório](/articles/editing-files-in-your-repository)". -### Symlink does not exist within your site's repository +### O link simbólico não existe no repositório do site -This error means that your site includes a symbolic link (symlink) that does not exist in the publishing source for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia. +Este erro significa que seu site inclui um link simbólico que não existe na fonte de publicação do site. Para obter mais informações sobre links simbólicos, consulte "[Link simbólico](https://en.wikipedia.org/wiki/Symbolic_link)" na Wikipédia. -To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the publishing source for your site. To include external assets, consider using {% if currentVersion == "free-pro-team@latest" %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %} +Para solucionar problemas, determine se o arquivo na mensagem de erro é usado para criar o site. Se ele não for ou se você não quiser que o arquivo seja um link simbólico, exclua o arquivo. Se o arquivo de link simbólico for necessário para criar seu site, verifique se o arquivo ou o diretório a que ele faz referência está na fonte de publicação do site. Para incluir ativos externos, considere usar {% if currentVersion == "free-pro-team@latest" %}`submódulo do git` ou {% endif %}um gerenciador de pacotes de terceiros como o [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Usar submódulos com {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %} -### Syntax error in 'for' loop +### Erro de sintaxe no loop 'for' -This error means that your code includes invalid syntax in a Liquid `for` loop declaration. +Este erro significa que o código inclui sintaxe inválida em uma declaração de loop `for` do Liquid. -To troubleshoot, make sure all `for` loops in the file in the error message have proper syntax. For more information about proper syntax for `for` loops, see "[Iteration tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" in the Liquid documentation. +Para solucionar problemas, verifique se todos os loops `for` no arquivo da mensagem de erro têm sintaxe adequada. Para obter mais informações sobre a sintaxe adequada para loops `for`, consulte "[Tags de Iteração](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" na documentação do Liquid. -### Tag not properly closed +### Tag fechada incorretamente -This error message means that your code includes a logic tag that is not properly closed. For example, {% raw %}`{% capture example_variable %}` must be closed by `{% endcapture %}`{% endraw %}. +Esta mensagem de erro significa que o código inclui uma tag lógica que foi fechada incorretamente. Por exemplo, {% raw %}`{% capture example_variable %}` deve ser fechada por `{% endcapture %}`{% endraw %}. -To troubleshoot, make sure all logic tags in the file in the error message are properly closed. For more information, see "[Liquid tags](https://help.shopify.com/en/themes/liquid/tags)" in the Liquid documentation. +Para solucionar problemas, verifique se todas as tags lógicas no arquivo da mensagem de erro estão fechadas corretamente. Para obter mais informações, consulte "[Tags do Liquid](https://help.shopify.com/en/themes/liquid/tags)" na documentação do Liquid. -### Tag not properly terminated +### Tag terminada incorretamente -This error means that your code includes an output tag that is not properly terminated. For example, {% raw %}`{{ page.title }` instead of `{{ page.title }}`{% endraw %}. +Este erro significa que o código inclui uma tag de saída que não foi terminada corretamente. Por exemplo, {% raw %}`{{ page.title }` em vez de `{{ page.title }}`{% endraw %}. -To troubleshoot, make sure all output tags in the file in the error message are terminated with `}}`. For more information, see "[Liquid objects](https://help.shopify.com/en/themes/liquid/objects)" in the Liquid documentation. +Para solucionar problemas, verifique se todas as tags de saída no arquivo da mensagem de erro estão terminadas com `}}`. Para obter mais informações, consulte "[Objetos do Liquid](https://help.shopify.com/en/themes/liquid/objects)" na documentação do Liquid. -### Unknown tag error +### Erro de tag desconhecida -This error means that your code contains an unrecognized Liquid tag. +Este erro significa que o código contém uma tag do Liquid não reconhecida. -To troubleshoot, make sure all Liquid tags in the file in the error message match Jekyll's default variables and there are no typos in the tag names. For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. +Para solucionar problemas, verifique se todas as tags do Liquid no arquivo da mensagem de erro correspondem a variáveis padrão do Jekyll e se não há erros de digitação nos nomes das tags. Para obter uma lista de variáveis padrão, consulte "[Variáveis](https://jekyllrb.com/docs/variables/)" na documentação do Jekyll. -Unsupported plugins are a common source of unrecognized tags. If you use an unsupported plugin in your site by generating your site locally and pushing your static files to {% data variables.product.product_name %}, make sure the plugin is not introducing tags that are not in Jekyll's default variables. For a list of supported plugins, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)." +Plugins incompatíveis são uma fonte comum de tags não reconhecidas. Se você usar um plugin incompatível ao gerar seu site localmente e fazer push dos arquivos estáticos para o {% data variables.product.product_name %}, verifique se o plugin não está inserindo tags que não estão nas variáveis padrão do Jekyll. Para obter uma lista de plugins compatíveis, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#plugins)". diff --git a/translations/pt-BR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/pt-BR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index 2c5a73deea..10b8bdb476 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/pt-BR/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: Cancelar a publicação de um site do GitHub Pages -intro: 'Você pode cancelar a publicação do seu site de {% data variables.product.prodname_pages %} para que o site não esteja mais disponível para {% if currentVersion == "free-pro-team@latest" %}o público{% else %}qualquer pessoa que usa {% data variables.product.product_location %}{% endif %}.' +intro: 'Você pode cancelar a publicação do seu site de {% data variables.product.prodname_pages %} para que não fique mais disponível.' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/pt-BR/content/github/working-with-github-support/about-github-support.md b/translations/pt-BR/content/github/working-with-github-support/about-github-support.md index 5fbbbd90c7..5cbf7e52d0 100644 --- a/translations/pt-BR/content/github/working-with-github-support/about-github-support.md +++ b/translations/pt-BR/content/github/working-with-github-support/about-github-support.md @@ -23,9 +23,9 @@ Para verificar se, atualmente, há algum incidente afetando os serviços no {% d ### Entrar em contato com o {% data variables.contact.github_support %} -As contas de usuário e organização {% data variables.product.prodname_free_user %} podem usar o {% data variables.contact.community_support_forum %} para navegar em tópicos, fazer perguntas, compartilhar soluções e interagir diretamente com {% data variables.contact.community_support %}. Você também pode entrar em contato com {% data variables.contact.contact_support %} para relatar problemas de conta, segurança e abuso. +Você pode usar {% data variables.contact.community_support_forum %} para procurar tópicos, fazer perguntas, compartilhar soluções e interagir diretamente com {% data variables.contact.community_support %}. -Em contas pagas, você pode entrar em contato com {% data variables.contact.contact_support %} e, dependendo do seu plano, entrar em contato com {% data variables.contact.premium_support %} ou {% data variables.contact.contact_ent_support %}. Para mais informações sobre contato {% data variables.contact.premium_support %}, consulte [Sobre {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud) ou [Sobre {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)." +Para relatar problemas de segurança, segurança e abuso ou receber suporte assistido para uma conta paga, acesse {% data variables.contact.contact_support_portal %}. Se você for um administrador de {% data variables.product.prodname_ghe_server %} sem uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}, acesse {% data variables.contact.contact_enterprise_portal %}. ### Conceder acesso temporário do {% data variables.contact.github_support %} a um repositório privado diff --git a/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md index b41eb1615b..ad003371e4 100644 --- a/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md +++ b/translations/pt-BR/content/github/writing-on-github/forking-and-cloning-gists.md @@ -11,7 +11,7 @@ versions: ### Bifurcar gists -Cada gist indica quais bifurcações possuem atividade, o que facilita a localização de modificações interessantes feitas por colegas de trabalho ou pessoas desconhecidas. +Cada gist indica quais bifurcações têm atividade, facilitando o processo de encontrar mudanças interessantes de outros. ![Bifurcações gist](/assets/images/help/gist/gist_forks.png) diff --git a/translations/pt-BR/content/github/writing-on-github/organizing-information-with-tables.md b/translations/pt-BR/content/github/writing-on-github/organizing-information-with-tables.md index a4e1edd0a5..540e358c83 100644 --- a/translations/pt-BR/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/pt-BR/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: Você pode criar tabelas com barras verticais `|` e hifens `-`. Os hifens são usados para criar o cabeçalho das colunas e as barras verticais, para separar as colunas. Você deve incluir uma linha em branco antes da tabela para ela ser construída corretamente. -``` +```markdown | Primeiro cabeçalho | Segundo cabeçalho | | ------------------- | ------------------- | @@ -27,7 +27,7 @@ As barras verticais em cada extremo da tabela são opcionais. As células podem ter largura variada e não precisam estar alinhadas perfeitamente com as colunas. Deve ter no mínimo três hifens em cada coluna da linha do cabeçalho. -``` +```markdown | Comando | Descrição | | --- | --- | | git status | Lista de todos os arquivos modificados ou novos | @@ -40,7 +40,7 @@ As células podem ter largura variada e não precisam estar alinhadas perfeitame Você pode usar [formatação](/articles/basic-writing-and-formatting-syntax), como links, blocos de código em linhas e estilos de texto em sua tabela: -``` +```markdown | Comando | Descrição | | --- | --- | | `git status` | Lista de todos os arquivos *modificados ou novos* | @@ -51,7 +51,7 @@ Você pode usar [formatação](/articles/basic-writing-and-formatting-syntax), c Você pode alinhar o texto à esquerda, direita ou centralizar uma coluna incluindo dois pontos `:` à esquerda, direita ou nos dois lados dos hifens que estão dentro da linha de cabeçalho. -``` +```markdown | Esquerda | Centralizado | Direita | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ Você pode alinhar o texto à esquerda, direita ou centralizar uma coluna inclui Para incluir uma barra vertical `|` como conteúdo dentro da célula, use `\` antes da barra vertical: -``` +```markdown | Nome | Caractere | | --- | --- | | Crase | ` | diff --git a/translations/pt-BR/content/graphql/README.md b/translations/pt-BR/content/graphql/README.md index f29fbc5131..0d2b935e62 100644 --- a/translations/pt-BR/content/graphql/README.md +++ b/translations/pt-BR/content/graphql/README.md @@ -1,10 +1,10 @@ # GraphQL -The `/content/graphql` directory is where the GitHub GraphQL API docs live! +O diretório `/content/graphql` é onde fica a documentação da API GraphQL do GitHub! -* The `/content/graphql/guides` and `/content/graphql/overview` directories contain articles that are human-editable. -* The `/content/graphql/reference` directory contains an article for each GraphQL data type used in the GitHub GraphQL API. Most of the content in this directory is rendered using `include` tags. +* Os diretórios `/content/graphql/guides` e `/content/graphql/overview` contêm artigos que são editáveis pelas pessoas. +* O diretório `/content/graphql/reference` contém um artigo para cada tipo de dado do GraphQL usado na API GraphQL do GitHub. A maioria do conteúdo nesse diretório é processada usando tags `include`. - The content rendered by `include` tags is sourced from the `/lib/graphql/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/graphql/README.md`](/lib/graphql/README.md). + O conteúdo processado etiquetas de `include` é fornecido no diretório `/lib/graphql/static`, que é gerado automaticamente a partir do código-fonte da API internamente no GitHub e não deve ser editado por uma pessoa. Para obter mais informações, consulte [`/lib/graphql/README.md`](/lib/graphql/README.md). - **As a result, we cannot accept contributions to GraphQL API reference content in this repository.** + **Como resultado, não podemos aceitar contribuições para o conteúdo da API do GraphQL neste repositório.** diff --git a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md index ffddcf72cb..e6b1211c57 100644 --- a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md @@ -103,6 +103,7 @@ As mutações são estruturadas da seguinte forma: 
    mutation {
   mutationName(input: {MutationNameInput!}) {
     MutationNamePayload
+  }
 }
    Neste exemplo, o objeto de entrada é `MutationNameInput` e o objeto de carga é `MutationNamePayload`. diff --git a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md index c04c3c2d45..24d34b101e 100644 --- a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md +++ b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ O GraphQL é [introspectivo](https://graphql.github.io/learn/introspection/). Is * Consulte `__schema` para listar todos os tipos definidos no esquema e obter informações sobre cada um: ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* Consulte `__type` para obter informações sobre qualquer tipo: + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* Consulte `__type` para obter informações sobre qualquer tipo: - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * Você também pode executar uma _consulta de introspeção_ do esquema através de uma solicitação do `GET`: diff --git a/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md index d6bd50ae2b..2201946979 100644 --- a/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: Fazer a migração da REST para o GraphQL representa uma mudança significativa na lógica da API. As diferenças entre a REST como um estilo e o GraphQL como uma especificação tornam difícil —e, muitas vezes indesejável—substituir as chamadas da API REST por consultas da API do GraphQL individualmente. Incluímos abaixo exemplos específicos de migração. -To migrate your code from the [REST API](/rest) to the GraphQL API: +Para fazer a migração do seu código da [API REST](/rest) para a API do GraphQL: - Revise a [especificação do GraphQL](https://graphql.github.io/graphql-spec/June2018/) -- Review GitHub's [GraphQL schema](/graphql/reference) +- Revise o [esquema do GraphQL](/graphql/reference) do GitHub - Considere como qualquer código existente que você tem atualmente interage com a API REST do GitHub -- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions +- Use [IDs dos nó global](/graphql/guides/using-global-node-ids) para fazer referência a objetos entre as versões da API As vantagens significativas do GraphQL incluem: @@ -53,12 +53,12 @@ query { } ``` -Considere outro exemplo: recuperar uma lista de pull requests e verificar se cada um é mesclável. A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): +Considere outro exemplo: recuperar uma lista de pull requests e verificar se cada um é mesclável. Uma chamada para a API REST recupera uma lista de pull requests e suas [representações resumidas](/rest#summary-representations): ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: +Determinar se um pull request pode ser mesclado demanda recuperar cada pull request individualmente para sua [representação detalhada](/rest#detailed-representations) (uma grande carga), bem como verificar seu atributo `mesclável` é verdadeiro ou falso: ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ Ao usar a **API do GraphQL**, você pode recuperar os dados com uma única consu } ``` -You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. +Você também pode estender o poder dessa consulta se [substitui uma variável](/graphql/guides/forming-calls-with-graphql#working-with-variables) para o número do pull request. ## Exemplo: Digitação não flexível Os esquemas do GraphQL são digitados de modo rígido, o que torna o gerenciamento dos dados mais seguro. -Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): +Considere um exemplo de adição de um comentário a um problema ou pull request usando uma [mutação ](/graphql/reference/mutations) do GraphQL e especificando por engano um número inteiro em vez de uma string para o valor de [`clientMutationId`](/graphql/reference/mutations#addcomment): ```graphql mutation { diff --git a/translations/pt-BR/content/graphql/guides/using-global-node-ids.md b/translations/pt-BR/content/graphql/guides/using-global-node-ids.md index e0af494556..82f4030a33 100644 --- a/translations/pt-BR/content/graphql/guides/using-global-node-ids.md +++ b/translations/pt-BR/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ Você pode acessar a maioria dos objetos do GitHub (usuários, problemas, pull r {% note %} -**Observação:** Na REST, o campo de ID do nó global é chamado `node_id`. No GraphQL, é um campo `id` na interface do `nó`. For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." +**Observação:** Na REST, o campo de ID do nó global é chamado `node_id`. No GraphQL, é um campo `id` na interface do `nó`. Para relembrar o que significa "nó" no GraphQL, consulte"[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql#node)". {% endnote %} @@ -29,7 +29,7 @@ Vamos analisar um exemplo. ### 1. Chame um ponto final da REST que retorna o ID do nó de um objeto -If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): +Se você [solicitar o usuário autenticado](/rest/reference/users#get-the-authenticated-user): ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { Este tipo de consulta—ou seja, encontrar o nó pelo ID—é conhecida como "consulta direta de nó". -When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). +Ao executar esta consulta, você verá que `__typename` é [`Usuário`](/graphql/reference/objects#user). ### 3. Faça uma pesquisa direta de nó no GraphQL @@ -122,4 +122,4 @@ Este tipo de consulta é a abordagem-padrão para consultar um objeto pelo seu I ### Usando IDs de nó global em migrações -Ao construir integrações que usam a API REST ou a API do GraphQL, considera-se uma prática recomendada persistir no ID de nó global para que você possa facilmente fazer referência a objetos entre nas versões da API. For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." +Ao construir integrações que usam a API REST ou a API do GraphQL, considera-se uma prática recomendada persistir no ID de nó global para que você possa facilmente fazer referência a objetos entre nas versões da API. Para obter mais informações sobre como lidar com a transição entre a REST e o GraphQL, consulte "[Migrando da REST para o GraphQL](/graphql/guides/migrating-from-rest-to-graphql)" diff --git a/translations/pt-BR/content/graphql/overview/resource-limitations.md b/translations/pt-BR/content/graphql/overview/resource-limitations.md index 3c9af52fe1..db47812989 100644 --- a/translations/pt-BR/content/graphql/overview/resource-limitations.md +++ b/translations/pt-BR/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## Limite de nó -To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: +Para passar a validação do [esquema](/graphql/guides/introduction-to-graphql#schema), todas as [chamadas ](/graphql/guides/forming-calls-with-graphql) da API v4 do GraphQL devem atender a esses padrões: -* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). +* Os clientes devem fornecer um `primeiro` ou `último` argumento [conexão](/graphql/guides/introduction-to-graphql#connection). * Os valores de `primeiro` e `último` devem ser entre 1 e 100. -* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). +* As chamadas individuais não podem solicitar mais de 500.000 [nós](/graphql/guides/introduction-to-graphql#node)no total. #### Calcular nós em uma chamada @@ -121,7 +121,7 @@ Estes dois exemplos mostram como calcular os nós totais em uma chamada. O [limite de taxas](/rest/overview/resources-in-the-rest-api#rate-limiting) do GraphQL API v4 é diferente dos limites de taxa do REST API v3. -Por que os limites de taxa de API são diferentes? With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). Uma chamada única e complexa do GraphQL poderia ser o equivalente a milhares de solicitações de REST. Embora uma única chamada GraphQL fique bem abaixo do limite de taxa de API REST, a consulta pode ser muito cara para os servidores do GitHub calcularem. +Por que os limites de taxa de API são diferentes? Com o [GraphQL](/graphql), uma chamada do GraphQL pode substituir [várias chamadas de REST](/graphql/guides/migrating-from-rest-to-graphql). Uma chamada única e complexa do GraphQL poderia ser o equivalente a milhares de solicitações de REST. Embora uma única chamada GraphQL fique bem abaixo do limite de taxa de API REST, a consulta pode ser muito cara para os servidores do GitHub calcularem. Para representar com precisão o custo de servidor de uma consulta, a API v4 do GraphQL calcula a **pontuação de um limite de taxa** de uma chamada com base em uma escala normalizada de pontos. Os fatores de pontuação de uma consulta no primeiro e último argumentos em uma conexão principal e suas conexões auxiliares. diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 2bc4ac1330..ab0bf83220 100644 --- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: Habilitar um link entre o GitHub Insights e o GitHub Enterprise -intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' +intro: 'Você pode habilitar um link que permitirá que os usuários naveguem de {% data variables.product.prodname_ghe_server %} para {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' permissions: 'Os administradores do site de {% data variables.product.prodname_ghe_server %} podem habilitar o link entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_insights %}.' redirect_from: @@ -14,7 +14,7 @@ Após habilitar o link, cada usuário poderá navegar diretamente de {% data var 1. Entre em contato com o shell administrativo para {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)". 2. Execute o comando a seguir. - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. Retornar para diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index 41d9c8a1bc..a6542cf8a5 100644 --- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - Você precisa instalar dependências no servidor do aplicativo. - [Docker](https://docs.docker.com/install/) 1.13.0+ - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/), disponível via apt para [Debian](https://packages.debian.org/search?keywords=netcat) e [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} diff --git a/translations/pt-BR/content/packages/guides/about-github-container-registry.md b/translations/pt-BR/content/packages/guides/about-github-container-registry.md index 2fe4f657d1..4e5acd174d 100644 --- a/translations/pt-BR/content/packages/guides/about-github-container-registry.md +++ b/translations/pt-BR/content/packages/guides/about-github-container-registry.md @@ -1,6 +1,6 @@ --- title: Sobre o GitHub Container Registry -intro: 'You can use {% data variables.product.prodname_github_container_registry %} to seamlessly host and manage Docker container images in your organization or personal user account on {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_github_container_registry %} permite que você configure quem pode gerenciar e acessar pacotes usando permissões refinadas.' +intro: 'Você pode usar {% data variables.product.prodname_github_container_registry %} para hospedar e gerenciar imagens do contêiner Docker na sua organização ou conta pessoal em {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_github_container_registry %} permite que você configure quem pode gerenciar e acessar pacotes usando permissões refinadas.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/getting-started-with-github-container-registry/about-github-container-registry @@ -21,7 +21,7 @@ versions: Para compartilhar o contexto sobre o uso do seu pacote, você pode vincular um repositório à sua imagem de contêiner no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Conectar um repositório a uma imagem de contêiner](/packages/guides/connecting-a-repository-to-a-container-image)". -{% data variables.product.prodname_github_container_registry %} has different hosting locations, permission, and visibility than other package registries. +{% data variables.product.prodname_github_container_registry %} tem locais de hospedagem diferentes, permissão e visibilidade diferentes dos outros registros de pacotes. | | Registros de pacotes | {% data variables.product.prodname_github_container_registry %} | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -29,7 +29,7 @@ Para compartilhar o contexto sobre o uso do seu pacote, você pode vincular um r | Permissões | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | Para cada imagem de container, você pode escolher o nível de acesso que os outros têm. As permissões para acesso a imagens do contêiner são separadas da sua organização e das permissões do repositório. | Visibilidade | {% data reusables.package_registry.public-or-private-packages %} | Você pode definir a visibilidade de cada uma de suas imagens de contêiner. Uma imagem privada de contêiner só é visível para pessoas e equipes às quais é fornecido acesso na sua organização. Qualquer pessoa pode ver uma imagem pública de contêiner. | acesso anônimo | N/A | Você pode acessar imagens de contêineres públicas anonimamente. -For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." +Para obter mais informações, consulte "[Sobre escopos e permissões para {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)". ### Formatos compatíveis @@ -82,7 +82,7 @@ To install or publish a package, you must use a token with the appropriate scope | `delete:packages` | Exclua versões especificadas de imagens privadas ou públicas de contêiner do {% data variables.product.prodname_github_container_registry %}. Para obter mais informações, consulte "[Excluir uma imagem de contêiner](/packages/guides/deleting-a-container-image)". | -To learn about available scopes and permissions for container images, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." +Para aprender sobre escopos e permissões disponíveis para imagens de contêiner, consulte "[Configurar controle de acesso e visibilidade para imagens do contêiner](/packages/guides/configuring-access-control-and-visibility-for-container-images)". Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token/)" e "[Escopos disponíveis](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)". diff --git a/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index 080fbaa0c6..4ae26a38b0 100644 --- a/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ Se desejar interagir com vários repositórios, você poderá adicionar cada rep Se sua instância tem o isolamento de subdomínio habilitado: {% endif %} -``` +```xml +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +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 %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +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 %} Para usar este exemplo de comando de login, substitua `NOME DE USUÁRIO` pelo seu nome de usuário de {% data variables.product.product_name %} {% if enterpriseServerVersions contains currentVersion %}, `NOME DE HOST` pela URL para {% data variables.product.product_location %},{% endif %} e `~/TOKEN. xt` pelo caminho do arquivo para o seu token de acesso pessoal para {% data variables.product.product_name %}. @@ -94,9 +106,19 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} ```shell $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 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 do docker para o pacote, crie a imagem, substituindo *PROPRIETÁRIO* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* pelo o nome do repositório que contém o seu projeto, *IMAGE_NAME* pelo o nome do pacote ou imagem, *VERSÃO* com a versão do pacote no momento da criação, {% if enterpriseServerVersions contains currentVersion %} *NOME DE HOST* pelo o nome de host de {% data variables.product.product_location %},{% endif %} e *PATH* para a imagem se não estiver no diretório de trabalho atual. @@ -105,9 +127,19 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} ```shell $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + 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 em {% data variables.product.prodname_registry %}. @@ -116,9 +148,19 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` {% else %} + + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} ```shell $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` + {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} + Se sua instância tem o isolamento de subdomínio desabilitado: + ```shell + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} {% endif %} {% note %} @@ -128,7 +170,14 @@ O {% data variables.product.prodname_registry %} aceita várias imagens do Docke #### Exemplo de publicação de uma imagem do Docker -{% data reusables.package_registry.docker_registry_deprecation_status %} +{% if enterpriseServerVersions contains currentVersion %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Esses exemplos assumem que sua instância tem o isolamento de subdomínio habilitado. +{% endif %} + + +{% 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. @@ -198,9 +247,19 @@ Você pode usar o comando `docker pull` para instalar uma imagem docker a partir $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} + +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} ```shell $ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +Se sua instância tem o isolamento de subdomínio desabilitado: +```shell +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} {% endif %} {% note %} diff --git a/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md index 4cff9b0924..a7ee1387f2 100644 --- a/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -17,13 +17,13 @@ versions: **Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### Limits for published npm versions +### Limites para versões publicadas do npm -If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage. +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. -To reduce the number of versions you have published for your npm package, consider deleting package versions. Para obter mais informações, consulte "[Excluir um pacote](/packages/manage-packages/deleting-a-package)". +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. -In the future, {% data variables.product.company_short %} will enforce a hard limit on publishing more than 1,000 versions of an npm package. When we start enforcing the 1,000 versions limit for each npm package hosted on {% data variables.product.prodname_registry %}, we will offer more guidance on how to manage your package versions. +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 "[Excluir um pacote](/packages/manage-packages/deleting-a-package)" ou "[Entrar em contato com o Suporte](/packages/learn-github-packages/about-github-packages#contacting-support)". {% endif %} @@ -166,7 +166,7 @@ Você também precisa adicionar o arquivo *.npmrc* ao seu projeto para que todas {% 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", @@ -209,6 +209,12 @@ registry=https://HOSTNAME/_registry/npm/OWNER ``` {% endif %} +{% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} +### 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 - "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md index ae268f8a43..49d7affa29 100644 --- a/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md +++ b/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -107,7 +107,7 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem 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 %} irá corresponde ao repositório baseado neste valor, em vez de usar o nome do gem.{% if enterpriseServerVersions contains currentVersion %} Substitua o *NOME DE HOST* pelo nome do host da sua instância {% data variables.product.prodname_ghe_server %}.{% endif %} -``` +```ruby gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` @@ -118,7 +118,7 @@ gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@ {% data reusables.package_registry.authenticate-step %} 2. 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 NOME* pelo pacote que deseja instalar de {% data variables.product.prodname_registry %} e *OWNER* pelo usuário ou organização que possui o repositório que contém a gema que deseja instalar.{% if enterpriseServerVersions contains currentVersion %} substitua `URL REGISTRY` 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 do {% data variables.product.prodname_ghe_server %} .{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -130,7 +130,7 @@ gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@ 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://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" diff --git a/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md index f93f99d14a..63ab1cface 100644 --- a/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md +++ b/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker 1. No seu arquivo Docker, adicione esta linha, substituindo `PROPRIETÁRIO` e `REPO` pelas suas informações: ```shell - ETIQUETA org.opencontainers.image.source https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO ``` Por exemplo, se você é o usuário de `monalisa` e proprietário de `my-repo`, você adicionaria essa linha ao seu arquivo Docker: ```shell - ETIQUETA org.opencontainers.image.source https://github.com/monalisa/my-repo + ETIQUETA org.opencontainers.image.source=https://github.com/monalisa/my-repo ``` Para obter mais informações, consulte "[ETIQUETA](https://docs.docker.com/engine/reference/builder/#label)" na documentação oficial do Docker e "[Chaves de anotação pré-definidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" no repositório `opencontainers/image-spec`. diff --git a/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md b/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md index 31b8f63889..f54f8e40e9 100644 --- a/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md +++ b/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md @@ -1,7 +1,7 @@ --- -title: Container guides for GitHub Packages -shortTitle: Container guides for GitHub Packages -intro: 'You can publish and retrieve Docker images using {% data variables.product.prodname_registry %}.' +title: Guias do contêiner para o GitHub Packages +shortTitle: Guias do contêiner para o GitHub Packages +intro: 'Você pode publicar e recuperar imagens do Docker usando {% data variables.product.prodname_registry %}.' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/packages/guides/deleting-a-container-image.md b/translations/pt-BR/content/packages/guides/deleting-a-container-image.md index 8a1584970b..b0c9aaaaa5 100644 --- a/translations/pt-BR/content/packages/guides/deleting-a-container-image.md +++ b/translations/pt-BR/content/packages/guides/deleting-a-container-image.md @@ -1,6 +1,6 @@ --- title: Excluir uma imagem de contêiner -intro: 'You can delete a specific version or all versions of a private or public container image on {% data variables.product.prodname_dotcom %}.' +intro: 'É possível excluir uma versão específica ou todas as versões de uma imagem de contêiner privado ou público em {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image @@ -20,34 +20,34 @@ Ao excluir pacotes públicos, esteja ciente de que você pode quebrar projetos q ### Excluir uma versão de uma imagem de contêiner de usuário em {% data variables.product.prodname_dotcom %} -To only delete specific versions of a container image, you can use these steps. To delete an entire package, see "[Deleting all versions of a user-owned container image on {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-a-user-owned-container-image-on-github)." +Para excluir apenas as versões específicas de uma imagem de contêiner, você pode usar estas etapas. Para excluir um pacote inteiro, consulte "[Excluir todas as versões de uma imagem do contêiner de usuário em {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-a-user-owned-container-image-on-github)". {% data reusables.package_registry.package-settings-from-user-level %} 5. À esquerda, clique em **Gerenciar versões**. -6. Optionally, to ensure you're seeing all of your package versions, use the "Type" drop down menu and select **All**. ![Package version type drop down menu showing option to list all versions](/assets/images/help/package-registry/make-all-container-versions-visible.png) -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. Opcionalmente, para garantir que você está visualizando todas as versões de seu pacote, use o menu suspenso "Tipo" e selecione **Todos**. ![Menu suspenso do tipo de versão do pacote que mostra a opção de listar todas as versões](/assets/images/help/package-registry/make-all-container-versions-visible.png) +5. À direita da versão que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Excluir versão**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-version.png) 6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) ### Excluir uma versão de uma imagem de contêiner de uma organização no {% data variables.product.prodname_dotcom %} -To only delete specific versions of a container image that you have admin , you can use these steps. To delete an entire package, see "[Deleting all versions of an organization-owned container image on {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-an-organization-owned-container-image-on-github)." +Para excluir apenas versões específicas de uma imagem contêiner que você tem administrador, você pode usar essas etapas. Para excluir um pacote inteiro, consulte "[Excluir todas as versões de uma imagem contêiner de propriedade da organização em {% data variables.product.prodname_dotcom %}](#deleting-all-versions-of-an-organization-owned-container-image-on-github)". {% data reusables.package_registry.package-settings-from-org-level %} 5. À esquerda, clique em **Gerenciar versões**. -6. Optionally, to ensure you're seeing all of your package versions, use the "Type" drop down menu and select **All**. ![Package version type drop down menu showing option to list all versions](/assets/images/help/package-registry/make-all-container-versions-visible.png) -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. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) +6. Opcionalmente, para garantir que você está visualizando todas as versões de seu pacote, use o menu suspenso "Tipo" e selecione **Todos**. ![Menu suspenso do tipo de versão do pacote que mostra a opção de listar todas as versões](/assets/images/help/package-registry/make-all-container-versions-visible.png) +5. À direita da versão que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Excluir versão**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-version.png) +6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão para confirmar a exclusão da versão do pacote](/assets/images/help/package-registry/confirm-container-package-version-deletion.png) -### Deleting all versions of a user-owned container image on {% data variables.product.prodname_dotcom %} +### Excluir todas as versões de uma imagem contêiner de usuário em {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-user-level %} -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) +5. À esquerda, clique em **Opções**. ![Opção do menu "Opções"](/assets/images/help/package-registry/options-for-container-settings.png) +6. Em "Zona de Perigo" clique em **Excluir este pacote**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-button.png) +6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua este pacote**. ![Botão para confirmar a exclusão da versão do pacote](/assets/images/help/package-registry/confirm-container-package-deletion.png) -### Deleting all versions of an organization-owned container image on {% data variables.product.prodname_dotcom %} +### Excluir todas as versões de uma imagem de contêiner pertencente à organização em {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-org-level %} -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**. ![Botão de excluir pacote](/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**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-container-package-deletion.png) +5. À esquerda, clique em **Opções**. ![Opção do menu "Opções"](/assets/images/help/package-registry/options-for-container-settings.png) +6. Em "Zona de Perigo" clique em **Excluir este pacote**. ![Botão de excluir pacote](/assets/images/help/package-registry/delete-container-package-button.png) +6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua este pacote**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-container-package-deletion.png) diff --git a/translations/pt-BR/content/packages/guides/index.md b/translations/pt-BR/content/packages/guides/index.md index 13e5e7bb73..a3dbc3a987 100644 --- a/translations/pt-BR/content/packages/guides/index.md +++ b/translations/pt-BR/content/packages/guides/index.md @@ -1,7 +1,7 @@ --- title: Guias shortTitle: Guias -intro: 'These guides help you configure {% data variables.product.prodname_actions %} or your package client to work with {% data variables.product.prodname_registry %}.' +intro: 'Esses guias ajudam você a configurar {% data variables.product.prodname_actions %} ou o cliente do seu pacote a trabalhar com {% data variables.product.prodname_registry %}.' redirect_from: - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem - /packages/using-github-packages-with-your-projects-ecosystem diff --git a/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md b/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md index 6f77e8b9bd..a1fd736888 100644 --- a/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md +++ b/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md @@ -1,7 +1,7 @@ --- -title: Package client guides for GitHub Packages -shortTitle: Package client guides for GitHub Packages -intro: 'You can publish and retrieve package client images using {% data variables.product.prodname_registry %}.' +title: Guias do cliente do pacote para o GitHub Packages +shortTitle: Guias do cliente do pacote para o GitHub Packages +intro: 'Você pode publicar e recuperar imagens de clientes do pacote usando {% data variables.product.prodname_registry %}.' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md b/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md index cdb03488b8..a56bd6518f 100644 --- a/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md +++ b/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md @@ -37,10 +37,272 @@ Você pode fazer referência ao `GITHUB_TOKEN` no seu arquivo de fluxo de trabal ### Publicar um pacote usando uma ação -Você pode publicar pacotes como parte do fluxo da sua integração contínua (CI) usando o {% data variables.product.prodname_actions %}. Por exemplo, você pode configurar um fluxo de trabalho para que sempre que um desenvolvedor fizer push do código para o branch-padrão, o fluxo de trabalho executará testes de CI. Se esses testes passarem, o fluxo de trabalho publicará uma nova versão de pacote no {% data variables.product.prodname_registry %}. Este fluxo de trabalho automatiza a criação de novas versões de pacotes somente se o código atender aos seus padrões de qualidade. +Você pode usar {% data variables.product.prodname_actions %} para publicar automaticamente pacotes como parte do fluxo de integração contínua (CI). Esta abordagem da implantação contínua (CD) permite que você automatize a criação de novas versões do pacote, se o código atender aos seus padrões de qualidade. Por exemplo, você pode criar um fluxo de trabalho que executa testes CI toda vez que um desenvolvedor faz push do código para um branch específico. Se os testes passarem, o fluxo de trabalho poderá publicar uma nova versão do pacote em {% data variables.product.prodname_registry %}. {% data reusables.package_registry.actions-configuration %} +O exemplo a seguir demonstra como você pode usar {% data variables.product.prodname_actions %} para criar e testar seu aplicativo e, em seguida, criar automaticamente uma imagem do Docker e publicá-la em {% data variables.product.prodname_registry %}: + +- Crie um novo arquivo de fluxo de trabalho no repositório (como `.github/workflows/deploy-image.yml`) e adicione o YAML a seguir: + {% raw %} + ``` + name: Create and publish a package + on: + push: + branches: ['release'] + jobs: + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [12.x, 14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + + build-and-push-image: + runs-on: ubuntu-latest + needs: run-npm-test + steps: + - name: Checkout + uses: actions/checkout@v2 + - name: Build container image + uses: docker/build-push-action@v1 + with: + username: ${{ github.actor }} + password: ${{ secrets.GITHUB_TOKEN }} + registry: docker.pkg.github.com + repository: ${{ github.repository }}/octo-image + tag_with_sha: true + tag_with_ref: true + ``` + {% endraw %} + + As configurações relevantes são explicadas na seguinte tabela:
    {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %}
    - Groups together all the steps that run in the check-bats-version job. Each line nested under this section is a separate action. + 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.
    - 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. + 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.
    - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +```
    - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +```
    - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +```
    - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - name: demo-workflow - on: - push: - jobs: - test: - runs-on: ${{ matrix.os }} - strategy: - fail-fast: false - matrix: - os: [macos-latest, ubuntu-latest] - steps: - - uses: actions/checkout@v1 - - uses: actions/setup-node@v1 - with: - node-version: 12 - - run: npm install -g bats - - run: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %}
    - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +```
    {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %}
    - Agrupa todos os passos são executados no trabalho check-bats-version. Cada linha aninhada nesta seção é uma ação separada. + 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.
    - 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. + 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.
    {% raw %} ```yaml -trabalhos: -- trabalho: scripts - pool: - vmImage: 'windows-latest' - etapas: - - script: echo "Esta etapa é executada no shell-padrão" - - bash: echo "Esta etapa é executada em bash" - - pwsh: Write-Host "Esta etapa é executada no centro do PowerShell" - - tarefa: PowerShell@2 - entrada: - script: Write-Host "Esta etapa é executada em PowerShell" +jobs: + - job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" ``` {% endraw %} {% raw %} ```yaml -trabalhos: +jobs: scripts: runs-on: windows-latest - etapas: - - executar: echo "Esta etapa é executada no shell-padrão" - - run: echo "Esta etapa é executada em bash" - shell: bash - - executar : Write-Host "Esta etapa é executada no centro do PowerShell" - shell: pwsh - - run: Write-Host "Esta etapa é executada no PowerShell" - shell: powershell + steps: + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell ``` {% endraw %} {% raw %} ```yaml -trabalhos: -- trabalho: run_command - pool: - vmImage: 'windows-latest' - trabalhos: - - script: echo "Esta etapa é executada em CMD no Windows por padrão" +jobs: + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} {% raw %} ```yaml -trabalhos: +jobs: run_command: runs-on: windows-latest steps: - - executar: echo "Esta etapa é executada no PowerShell no Windows por padrão" - - executar: echo "Esta etapa é executada em CMD no Windows explicitamente" - shell: cmd + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %} {% raw %} ```yaml -trabalhos: -- trabalho: condicional - pool: - vmImage: 'ubuntu-latest' - etapas: - - script: echo "Esta etapa é executada com str equals 'ABC' and num equals 123" - condição: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) +jobs: + - job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) ``` {% endraw %} {% raw %} ```yaml -trabalhos: - condicional: +jobs: + conditional: runs-on: ubuntu-latest - etapas: - - executar: echo "Esta etapa é executada com str equals 'ABC' and num equals 123" - if: ${{ env.str == 'ABC' && env.num == 123 }} + steps: + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %} {% raw %} ```yaml -trabalhos: -- trabalho: inicial - pool: - vmImage: 'ubuntu-latest' - etapas: - - script: echo "Este trabalho será executado primeiro." -- trabalho: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: inicial - etapas: - - script: echo "Este trabalho será executado após o trabalho inicial, em paralelo com o fanout2." -- trabalho: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: inicial - etapas: - - script: echo "Este trabalho será executado após o trabalho inicial, em paralelo com fanout1." -- trabalho: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - etapas: - - script: echo "Este trabalho será executado após fanout1 e fanout2 serem concluídos." +jobs: + - job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." + - job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." + - job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." + - job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} {% raw %} ```yaml -trabalhos: - inicial: +jobs: + initial: runs-on: ubuntu-latest - etapas: - - executar: echo "Este trabalho será executado primeiro." + steps: + - run: echo "This job will be run first." fanout1: runs-on: ubuntu-latest - needs: inicial - etapas: - - run: echo "Este trabalho será executado após o trabalho inicial, em paralelo com fanout2." + needs: initial + steps: + - run: echo "This job will run after the initial job, in parallel with fanout2." fanout2: runs-on: ubuntu-latest - needs: inicial - etapas: - - run: echo "Este trabalho será executado após o trabalho inicial, em paralelo com fanout1." + needs: initial + steps: + - run: echo "This job will run after the initial job, in parallel with fanout1." fanin: runs-on: ubuntu-latest needs: [fanout1, fanout2] - etapas: - - executar: echo "Este trabalho será executado após fanout1 e fanout2 serem concluídos." + steps: + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} {% raw %} ```yaml -trabalhos: -- trabalho: run_python - pool: - vmImage: 'ubuntu-latest' - etapas: - - tarefa: UsePythonVersion@0 - entradas: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py +jobs: + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} {% raw %} ```yaml -trabalhos: +jobs: run_python: runs-on: ubuntu-latest - etapas: - - usa: actions/setup-python@v2 - com: - python-version: '3.7' - arquitetura: 'x64' - - executar: python script.py + steps: + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} {% raw %} ```yaml -nome: Contêineres +name: Containers -em: [push] +on: [push] -trabalhos: - construir: +jobs: + build: runs-on: ubuntu-latest - contêiner: circleci/ruby:2.6.3-node-browsers-legacy + container: circleci/ruby:2.6.3-node-browsers-legacy env: PGHOST: postgres PGUSER: administrate RAILS_ENV: test - serviços: + services: postgres: - imagem: postgres:10.1-alpine + image: postgres:10.1-alpine env: POSTGRES_USER: administrate POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" - portas: - - 5432:5432 - # Adicionar uma verificação geral - opções: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 + ports: + - 5432:5432 + # Add a health check + options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 - etapas: - # Este arquivo Docker altera as configurações de USUÁRIO para circleci em vez de usar o usuário-padrão. Portanto, precisamos atualizar as permissões do arquivo para esta imagem funcionar no Actions. - # Veja https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem - - name: Configurar permissões do sistema de arquivos - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Instalar dependências - run: bundle install --path vendor/bundle - - name: Configuração do ambiente de instalação - run: cp .sample.env .env - - name: Configurar banco de dados - run: bundle exec rake db:setup - - name: Executar testes - run: bundle exec rake + steps: + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} {% raw %} ```yaml -nome: Contêineres +name: Containers -em: [push] +on: [push] -trabalhos: - criar: +jobs: + build: - estratégia: - matriz: + strategy: + matrix: ruby: [2.5, 2.6.3] runs-on: ubuntu-latest @@ -404,43 +409,43 @@ trabalhos: PGUSER: administrate RAILS_ENV: test - serviços: + services: postgres: - imagem: postgres:10.1-alpine + image: postgres:10.1-alpine env: POSTGRES_USER: administrate POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" - portas: - - 5432:5432 - # Adicionar verificação geral + ports: + - 5432:5432 + # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 - etapas: - - usa: actions/checkout@v2 - - nome: Configurar Ruby - usa: eregon/use-ruby-action@master - com: - ruby-version: ${{ matrix.ruby }} - - nome: Memorizar dependências - usa: actions/cache@v2 - com: - caminho: vendor/bundle - chave: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - nome: Instalar títulos do postgres - executar : sudo apt-get install libpq-dev - - nome: Install dependencies - executar : bundle install --path vendor/bundle - - Nome: Definir configuração do ambiente - executar: cp .sample.env .env - - nome: Configurar banco de dados - executar: bundle exec rake db:setup - - nome: Executar testes - executar: bundle exec rake - - nome: Install appraisal - executar: bundle exec appraisal install - - Nome: Run appraisal - executar: bundle exec appraisal rake + steps: + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %}
    - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +```
    - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +```
    - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +```
    - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - nome: demo-workflow - em: - push: - trabalhos: - teste: - runs-on: ${{ matrix.os }} - estratégia: - fail-fast: false - matriz: - os: [macos-latest, ubuntu-latest] - etapas: - - usa: actions/checkout@v1 - - usa: actions/setup-node@v1 - com: - node-version: 12 - - executar: npm install -g bats - - executar: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %} {% raw %} ```yaml -trabalhos: +jobs: run_python: runs-on: ubuntu-latest - etapas: - - usa: actions/setup-python@v2 - com: - python-version: '3.7' - arquitetura: 'x64' - - executar: python script.py + steps: + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %}
    - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +```
    {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %}
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + +{% raw %} +```yaml +on: + push: + branches: ['release'] +``` +{% endraw %} + + Configura o fluxo de trabalho Criar e publicar um pacote para ser executado toda vez que uma alteração é enviada para o branch denominado versão. +
    + +{% raw %} + ```yaml + run-npm-build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: npm install and build webpack + run: | + npm install + npm run build + - uses: actions/upload-artifact@main + with: + name: webpack artifacts + path: public/ + ``` + {% endraw %} + + Este trabalho instala o NPM e o usa para criar o aplicativo. +
    + +{% raw %} + ```yaml + run-npm-test: + runs-on: ubuntu-latest + needs: run-npm-build + strategy: + matrix: + os: [ubuntu-latest] + node-version: [14.x] + steps: + - uses: actions/checkout@v2 + - name: Use Node.js ${{ matrix.node-version }} + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node-version }} + - uses: actions/download-artifact@main + with: + name: webpack artifacts + path: public + - name: npm install, and test + run: | + npm install + npm test + env: + CI: true + ``` +{% endraw %} + + Este trabalho usa teste do npm para testar o código. O comando needs: run-npm-build torna esse trabalho dependente do trabalho run-npm-build. +
    + +{% raw %} + ```yaml + - name: Build container image + ``` +{% endraw %} + + Cria uma nova etapa denominada Build container image. Esta etapa é executada como parte do trabalho build-and-push-image. O comando needs: run-npm-test torna essa tarefa dependente do trabalho run-npm-test. +
    + +{% raw %} + ```yaml +uses: docker/build-push-action@v1 + ``` +{% endraw %} + + Usa a ação build-push-action do Docker para criar a imagem com base no arquivo Docker do seu repositório. Se a criação for bem-sucedida, ela faz p push da imagem para {% data variables.product.prodname_registry %}. +
    + +{% raw %} + ```yaml +with: + ``` +{% endraw %} + + Envia os parâmetros necessários para a ação build-push-action. Isto é definido nas linhas subsequentes. +
    + +{% raw %} + ```yaml +username: ${{ github.actor }} + ``` +{% endraw %} + + Define a conta de usuário que publicará os pacotes. Uma vez publicados, os pacotes pertencem à conta definida aqui. +
    + +{% raw %} + ```yaml +password: ${{ secrets.GITHUB_TOKEN }} + ``` +{% endraw %} + + Define a senha usada para acessar {% data variables.product.prodname_registry %}. +
    + +{% raw %} + ```yaml +registry: docker.pkg.github.com + ``` +{% endraw %} + + Define o registro que hospedará os pacotes resultantes. Este exemplo usa {% data variables.product.prodname_registry %}. +
    + +{% raw %} + ```yaml +repository: ${{ github.repository }}/octo-image + ``` +{% endraw %} + + Define qual repositório hospedará o pacote resultante e define o nome do pacote publicado. Substitui octo-image pelo nome que você deseja para o seu pacote. +
    + +{% raw %} + ```yaml +tag_with_sha: true + ``` +{% endraw %} + + Marca o pacote publicado com os primeiros sete caracteres do SHA do commit. Por exemplo, sha-2f2d842. +
    + +{% raw %} + ```yaml +tag_with_ref: true + ``` +{% endraw %} + + Tags o pacote publicado com a referência do Git. Este pode ser o nome do branch usado para criar o pacote. +
    + +- Este novo fluxo de trabalho será executado automaticamente toda vez que você fizer uma alteração no repositório. Você pode visualizar o progresso na aba **Ações**. +- Alguns minutos após a conclusão do fluxo de trabalho, o novo pacote ficará visível no seu repositório. Para encontrar seus pacotes disponíveis, consulte "[Visualizar os pacotes de um repositório](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)". + ### Instalar um pacote usando uma ação Você pode instalar pacotes como parte de seu fluxo de CI usando o {% data variables.product.prodname_actions %}. Por exemplo, você poderia configurar um fluxo de trabalho para que sempre que um desenvolvedor fizesse push do código para um pull request, o fluxo de trabalho resolveria as dependências, fazendo o download e instalando pacotes hospedados pelo {% data variables.product.prodname_registry %}. Em seguida, o fluxo de trabalho pode executar testes de CI que exigem as dependências. diff --git a/translations/pt-BR/content/packages/index.md b/translations/pt-BR/content/packages/index.md index 28687b92f6..c4c6eb85b0 100644 --- a/translations/pt-BR/content/packages/index.md +++ b/translations/pt-BR/content/packages/index.md @@ -12,25 +12,23 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - - - title: ghcr.io container names redirect to the container page + - title: Modo de manutenção do ghcr.io em 2021-01-09 + date: '2021-01-08' + href: 'https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/' + - title: Os nomes de contêineres de ghcr.io redirecionam para a página do contêiner date: '2020-12-14' - href: https://github.blog/changelog/2020-12-14-ghcr-io-container-names-redirect-to-the-container-page/ - - - title: Filter for tagged and untagged containers + href: 'https://github.blog/changelog/2020-12-14-ghcr-io-container-names-redirect-to-the-container-page/' + - title: Filtro para contêineres marcados e sem tags date: '2020-12-14' - href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: Packages container support is an opt-in beta - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + href: 'https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md index 021a4427ea..594b05ff4b 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md @@ -22,12 +22,19 @@ Você pode integrar {% data variables.product.prodname_registry %} com as APIs d You can host multiple packages in one repository and see more information about each package by viewing the package's README, download statistics, version history, and more. + +{% if currentVersion ver_gt "enterprise-server@2.21" %} + +![Diagrama que mostra as urls de hospedagem de GitHub Packages para npm, RubyGems, Apache Maven, Gradle, Nuget e Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% data reusables.package_registry.container-registry-beta %} -![Diagrama que mostra Node, RubyGems, Apache Maven, Gradle, Nuget e o registro do contêiner com suas urls de hospedagem](/assets/images/help/package-registry/packages-overview-diagram.png) +![Diagrama que mostra as urls de hospedagem de GitHub Packages para npm, RubyGems, Apache Maven, Gradle, Nuget e Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -109,11 +116,11 @@ Para obter mais informações sobre o isolamento de subdomínio, consulte "[Habi {% endif %} -For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Package client guides for {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)." +Para obter mais informações sobre a configuração do cliente do seu pacote para uso com {% data variables.product.prodname_registry %}, consulte "[Guias do cliente do pacote para {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)". {% if currentVersion == "free-pro-team@latest" %} -For more information about Docker and -{% data variables.product.prodname_github_container_registry %}, see "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)." +Para mais informações sobre o Docker e +{% data variables.product.prodname_github_container_registry %}, consulte "[Guias de contêiner para {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)". {% endif %} ### Autenticar-se no {% data variables.product.prodname_registry %} @@ -143,7 +150,7 @@ Para obter mais informações, consulte: ### Gerenciar pacotes -Você pode excluir uma versão de um pacote privado em {% data variables.product.product_name %} ou usar a API do GraphQL. 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 "[Excluir um pacote](/packages/manage-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/graphql/guides/forming-calls-with-graphql)". +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. 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 "[Excluir um pacote](/packages/manage-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/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)". diff --git a/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md index fb69acff2b..adb0752d26 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -1,5 +1,5 @@ --- -title: Core concepts for GitHub Packages +title: Conceitos principais para GitHub Packages intro: 'Abaixo está uma lista de termos comuns de {% data variables.product.prodname_registry %} que usamos em todos os nossos sites e documentação.' product: '{% data reusables.gated-features.packages %}' redirect_from: diff --git a/translations/pt-BR/content/packages/learn-github-packages/index.md b/translations/pt-BR/content/packages/learn-github-packages/index.md index a21e10fe4c..7cb1b5dcb6 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/index.md +++ b/translations/pt-BR/content/packages/learn-github-packages/index.md @@ -1,7 +1,7 @@ --- -title: Learn GitHub Packages -shortTitle: Learn GitHub Packages -intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.' +title: Aprenda sobre o GitHub Pckages +shortTitle: Aprenda sobre o GitHub Pckages +intro: 'Você pode saber mais sobre o GitHub Packages, incluindo a publicação de novos pacotes em {% data variables.product.prodname_registry %}.' redirect_from: - /packages/getting-started-with-github-container-registry versions: diff --git a/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md b/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md index f8be92a63f..e53a8208bf 100644 --- a/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md +++ b/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md @@ -15,7 +15,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} ### Sobre a exclusão de imagem de contêiner -To delete a container image package on {% data variables.product.product_name %}, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." +Para excluir um pacote de imagem de contêiner em {% data variables.product.product_name %}, consulte "[Excluir uma imagem de contêiner](/packages/guides/deleting-a-container-image)". {% endif %} @@ -54,7 +54,7 @@ Use a mutação `deletePackageVersion` na API do GraphQL. Você deve usar um tok Aqui está um exemplo de comando cURL para excluir uma versão de pacote com o ID de versão do pacote `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, usando um token de acesso pessoal. {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/pt-BR/content/packages/manage-packages/index.md b/translations/pt-BR/content/packages/manage-packages/index.md index b2f8bd537c..3538707b0e 100644 --- a/translations/pt-BR/content/packages/manage-packages/index.md +++ b/translations/pt-BR/content/packages/manage-packages/index.md @@ -1,6 +1,6 @@ --- -title: Managing GitHub packages -shortTitle: Managing GitHub packages +title: Gerenciar pacotes do GitHub +shortTitle: Gerenciar pacotes do GitHub intro: 'Você pode publicar novos pacotes no {% data variables.product.prodname_registry %}, visualizar e instalar pacotes existentes e, em circunstâncias especiais, excluir pacotes existentes.' redirect_from: - /github/managing-packages-with-github-packages/publishing-and-managing-packages diff --git a/translations/pt-BR/content/packages/quickstart.md b/translations/pt-BR/content/packages/quickstart.md index 19bfb06577..8d39e4b49f 100644 --- a/translations/pt-BR/content/packages/quickstart.md +++ b/translations/pt-BR/content/packages/quickstart.md @@ -1,6 +1,6 @@ --- -title: Quickstart for GitHub Packages -intro: 'Publish to {% data variables.product.prodname_registry %} in 5 minutes or less with {% data variables.product.prodname_actions %}.' +title: Inicie rapidamente para o GitHub Packages +intro: 'Publicar em {% data variables.product.prodname_registry %} em 5 minutos ou menos com {% data variables.product.prodname_actions %}.' allowTitleToDifferFromFilename: true versions: free-pro-team: '*' @@ -9,25 +9,25 @@ versions: ### Introdução -You only need an existing {% data variables.product.prodname_dotcom %} repository to publish a package to {% data variables.product.prodname_registry %}. In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. Feel free to create a new repository for this Quickstart. You can use it to test this and future {% data variables.product.prodname_actions %} workflows. +Você só precisa de um repositório de {% data variables.product.prodname_dotcom %} existente para publicar um pacote em {% data variables.product.prodname_registry %}. Neste guia, você criará um fluxo de trabalho de {% data variables.product.prodname_actions %} para testar seu código e, em seguida, publicá-lo em {% data variables.product.prodname_registry %}. Sinta-se à vontade para criar um novo repositório para esse guia de início rápido. Você pode usá-lo para testar este e os fluxos de trabalho futuros de {% data variables.product.prodname_actions %}. -### Publishing your package +### Publicar o seu pacote -1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. Create a private repository if you’d like to delete this package later, public packages cannot be deleted. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." -2. Clone the repository to your local machine. +1. Crie um novo repositório em {% data variables.product.prodname_dotcom %}, adicionando o `.gitignore` ao Node. Crie um repositório privado, se quiser excluir este pacote mais tarde. Os pacotes públicos não podem ser excluídos. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone o repositório para a sua máquina local. {% raw %} ```shell $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` {% endraw %} -3. Create an `index.js` file and add a basic alert to say "Hello world!" +3. Crie um arquivo `index.js` e adicione um alerta básico que diga "Hello world!" {% raw %} ```javascript{:copy} alert("Hello, World!"); ``` {% endraw %} -4. Initialize an npm package. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0` if you do not have any tests. Commit your changes and push them to +4. Inicializa um pacote de npm. No assistente de inicialização de pacote, insira seu pacote com o nome: _`@YOUR-USERNAME/YOUR-REPOSITORY`_ e defina o script de teste para `exit 0` se você não tiver testes. Faça o commit das alterações e envie-as por push para {% data variables.product.prodname_dotcom %}. {% raw %} ```shell @@ -45,7 +45,7 @@ You only need an existing {% data variables.product.prodname_dotcom %} repositor ``` {% endraw %} 5. Do seu repositório no {% data variables.product.prodname_dotcom %}, crie um novo arquivo no diretório `.github/workflows` denominado `release-package.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)". -6. Copy the following YAML content into the `release-package.yml` file. +6. Copie o seguinte conteúdo do YAML para o arquivo `release-package.yml`. {% raw %} ```yaml{:copy} name: Node.js Package @@ -80,31 +80,31 @@ You only need an existing {% data variables.product.prodname_dotcom %} repositor NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} ``` {% endraw %} -7. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Em seguida, para criar um pull request, clique em **Propor novo arquivo**. -8. **Merge** the pull request. -9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." +7. Vá até o final da página e selecione **Criar um novo branch para este commit e iniciar um pull request**. Em seguida, para criar um pull request, clique em **Propor novo arquivo**. +8. **Faça merge** do pull request. +9. Acesse a aba **Código** e crie uma nova versão para testar o fluxo de trabalho. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." -Creating a new release in your repository triggers the workflow to build and test your code. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. +A criação uma nova versão no seu repositório aciona o fluxo de trabalho para construir e testar seu código. Se os testes passarem, o pacote será publicado em {% data variables.product.prodname_registry %}. -### Viewing your published package +### Visualizar o seu pacote publicado -Packages are published at the repository level. You can see all the packages in a repository and search for a specific package. +Os pacotes são publicados no nível de repositório. Você pode visualizar todos os pacotes em um repositório e procurar um pacote específico. {% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %} -### Installing a published package +### Instalar um pacote publicado -Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)." +Agora que você publicou o pacote, você vai querer usá-lo como uma dependência nos seus projetos. Para obter mais informações, consulte "[Configurar npm para uso com o {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)". ### Próximas etapas -The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. +O fluxo de trabalho básico que você acabou de adicionar é executado sempre que uma nova versão for criada no seu repositório. Mas este é apenas o início do que você pode fazer com {% data variables.product.prodname_registry %}. Pode publicar o seu pacote em vários registros com um único fluxo de trabalho, acionar o fluxo de trabalho para ser executado em eventos diferentes, como um pull request mesclado, gerenciar contêineres, entre outros. -Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Pronto para começar? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}: +Combinar {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seguir as próximas etapas com {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}: -- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages -- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions -- "[Guides](/packages/guides)" for specific uses cases and examples +- "[Aprenda sobre {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para obter um tutorial aprofundado no GitHub Packages +- "[Aprenda sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obter um tutorial aprofundado no GitHub Actions +- "[Guias](/packages/guides)" para casos e exemplos específicos de uso diff --git a/translations/pt-BR/content/rest/README.md b/translations/pt-BR/content/rest/README.md index 55aaa5edda..7cf5cc93eb 100644 --- a/translations/pt-BR/content/rest/README.md +++ b/translations/pt-BR/content/rest/README.md @@ -1,10 +1,10 @@ # REST -The `/content/rest` directory is where the GitHub REST API docs live! +O diretório `/content/rest` é onde fica a documentação da API REST do GitHub! -* The `/content/rest/guides` and `/content/rest/overview` directories contain regular articles. These are human-editable. -* The `/content/rest/reference` directory contains an article for each group of endpoints in the GitHub REST API. Most of the content in this directory is rendered using `include` tags. +* Os diretórios `/content/rest/guias` e `/content/rest/overview` contêm artigos regulares. Eles podem ser editados por uma pessoa. +* O diretório `/content/rest/reference` contém um artigo para cada grupo de pontos de extremidade na API REST do GitHub. A maioria do conteúdo nesse diretório é processada usando tags `include`. - The content rendered by `include` tags is sourced from the `/lib/rest/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/rest/README.md`](/lib/rest/README.md). + O conteúdo processados com as tags `include` é fornecido no diretório `/lib/rest/static`, que é gerado automaticamente a partir do código fonte da API internamente no GitHub e não deve ser editado por uma pessoa. Para obter mais informações, consulte [`/lib/rest/README.md`](/lib/rest/README.md). - **As a result, we cannot accept contributions to REST API reference content in this repository.** + **Como resultado, não podemos aceitar contribuições para o conteúdo de referência da API REST neste repositório.** diff --git a/translations/pt-BR/content/rest/guides/basics-of-authentication.md b/translations/pt-BR/content/rest/guides/basics-of-authentication.md index 97ac13a4f7..a3608ca5a7 100644 --- a/translations/pt-BR/content/rest/guides/basics-of-authentication.md +++ b/translations/pt-BR/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ Além disso, uma vez que existe uma relação hierárquica entre os escopos, voc Verificar escopos apenas antes de fazer solicitações não é suficiente, já que é possível que os usuários mudem os escopos entre a sua verificação e a solicitação real. Caso isso aconteça, as chamadas par a API que você espera ter sucesso podem falhar com o status `404` ou `401` ou retornar um subconjunto diferente de informações. -Para ajudá-lo a gerenciar essas situações facilmente, todas as respostas da API para solicitações feitas com tokens válidos também contêm um [`cabeçalho de ` X-OAuth-Scopes][oauth scopes]. Este cabeçalho contém a lista de escopos do token que foi usado para fazer a solicitação. In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[check a token for validity\]\[/rest/reference/apps#check-a-token\]{% else %}\[check a token for validity\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Use esta informação para detectar alterações no escopo do token e informar os seus usuários sobre mudanças nas funcionalidades do aplicativo disponível. +Para ajudá-lo a gerenciar essas situações facilmente, todas as respostas da API para solicitações feitas com tokens válidos também contêm um [`cabeçalho de ` X-OAuth-Scopes][oauth scopes]. Este cabeçalho contém a lista de escopos do token que foi usado para fazer a solicitação. Além disso, a API de aplicativos OAuth fornece um ponto de extremidade para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[verifique se há validade de um token\]\[/rest/reference/apps#check-a-token\]{% else %}\[verifique se há validade de um token\]\[/rest/reference/apps#check-an-authorization\]{% endif %}. Use esta informação para detectar alterações no escopo do token e informar os seus usuários sobre mudanças nas funcionalidades do aplicativo disponível. #### Fazer solicitações autenticadas diff --git a/translations/pt-BR/content/rest/guides/delivering-deployments.md b/translations/pt-BR/content/rest/guides/delivering-deployments.md index 9117b4ce80..52036270b6 100644 --- a/translations/pt-BR/content/rest/guides/delivering-deployments.md +++ b/translations/pt-BR/content/rest/guides/delivering-deployments.md @@ -13,7 +13,7 @@ versions: -The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with the capability to launch them on a server that you own. Combinado com [a API de Status][status API], você será capaz de coordenar suas implantações no momento em que seu código chegar ao branch-padrão. +A [API de Implantações][deploy API] fornece seus projetos hospedados em {% data variables.product.product_name %} com a capacidade de lançá-los em um servidor do qual você é proprietário. Combinado com [a API de Status][status API], você será capaz de coordenar suas implantações no momento em que seu código chegar ao branch-padrão. Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos: diff --git a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md index 352e080728..972a8a74c8 100644 --- a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md @@ -232,7 +232,7 @@ Vamos combinar algumas chamadas de API para obter uma _verdadeira_ representaç ] ``` -Since we already have a list of repositories above, let's inspect each one, and call [the language listing API method][language API]: +Como já temos uma lista de repositórios acima, vamos inspecionar cada um e chamar o [método da API para listar a linguagem][language API]: ``` ruby repos.each do |repo| @@ -264,7 +264,7 @@ end language_bytes = [ :name => "language_bytes", :elements => language_byte_count] ``` -(For more information on D3 tree map magic, check out [this simple tutorial][language API].) +(Para obter mais informações sobre um mapa de árvore do D3, confira [este tutorial simples][language API].) Para concluir, passamos esta informação JSON para o mesmo modelo de ERB: diff --git a/translations/pt-BR/content/rest/guides/working-with-comments.md b/translations/pt-BR/content/rest/guides/working-with-comments.md index cdc00528b8..d7eccb43d5 100644 --- a/translations/pt-BR/content/rest/guides/working-with-comments.md +++ b/translations/pt-BR/content/rest/guides/working-with-comments.md @@ -18,7 +18,7 @@ Cada um desses tipos de comentários passa por uma parte diferente da API de {% ### Comentários do Pull Request -To access comments on a Pull Request, you'll go through [the Issues API][issues]. A princípio, isso pode parecer contraintuitivo. Mas depois que você entender que um Pull Request é apenas um problema com o código, faz sentido usar a API de problemas para criar comentários em um Pull Request. +Para acessar comentários em um Pull Request, você passará [pela API de Problemas][issues]. A princípio, isso pode parecer contraintuitivo. Mas depois que você entender que um Pull Request é apenas um problema com o código, faz sentido usar a API de problemas para criar comentários em um Pull Request. Nós demonstraremos como buscar comentários de Pull Request criando um script do Ruby usando [Octokit.rb][octokit.rb]. Você também deverá criar um [token de acesso pessoal][personal token]. @@ -44,7 +44,7 @@ Aqui, estamos especificamente chamando a API de problemas para obter os comentá ### Comentários em uma linha de Pull Request -Na visualização de diferenças, você pode iniciar uma discussão sobre um aspecto específico de uma mudança singular feita dentro do Pull Request. Estes comentários ocorrem nas linhas individuais dentro de um arquivo alterado. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. +Na visualização de diferenças, você pode iniciar uma discussão sobre um aspecto específico de uma mudança singular feita dentro do Pull Request. Estes comentários ocorrem nas linhas individuais dentro de um arquivo alterado. A URL do ponto de extremidade para esta discussão vem da [API da revisão de pull request][PR Review API]. O código a seguir busca todos os comentários de pull request feitos em arquivos, dado um único número de pull request: @@ -70,7 +70,7 @@ Você perceberá que ele é incrivelmente semelhante ao exemplo acima. A diferen ### Comentários de commit -O último tipo de comentários ocorre especificamente nos commits individuais. For this reason, they make use of [the commit comment API][commit comment API]. +O último tipo de comentários ocorre especificamente nos commits individuais. Por esta razão, eles fazem uso de [a API de comentário de commit][commit comment API]. Para recuperar os comentários em um commit, você deverá usar o SHA1 do commit. Em outras palavras, você não usará nenhum identificador relacionado ao Pull Request. Aqui está um exemplo: diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md index 7111220899..87b2b09aa5 100644 --- a/translations/pt-BR/content/rest/overview/api-previews.md +++ b/translations/pt-BR/content/rest/overview/api-previews.md @@ -83,17 +83,6 @@ Gerencie [projetos](/rest/reference/projects). **Tipo de mídia personalizada:** `cloak-preview` **Anunciado em:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) -{% if currentVersion == "free-pro-team@latest" %} - - -### Bloqueio de usuário - -Os usuários podem [bloquear outros usuários](/rest/reference/users#blocking). As organizações também podem [bloquear usuários](/rest/reference/orgs#blocking). - -**Tipo de mídia personalizado:** `giant-sentry-fist-preview` **Anunciado em:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Atualização 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Atualização 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) - -{% endif %} - ### Tópicos do repositório diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index d07518ca71..f69fb0c166 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -12,7 +12,7 @@ versions:
    O Gundamcat -

    Octokit comes in many flavors

    +

    O Octokit tem muitos sabores

    Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.


    Ruby → octokit.rb

    @@ -25,64 +25,68 @@ versions: ### Clojure -Library name | Repository |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) +Nome da biblioteca | Repositório |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) ### Dart -Library name | Repository |---|---| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) +Nome da biblioteca | Repositório |---|---| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) ### Emacs Lisp -Library name | Repository |---|---| **gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el) +Nome da biblioteca | Repositório |---|---| **gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el) ### Erlang -Library name | Repository |---|---| **octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) +Nome da biblioteca | Repositório |---|---| **octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) ### Go -Library name | Repository |---|---| **go-github**| [google/go-github](https://github.com/google/go-github) +Nome da biblioteca | Repositório |---|---| **go-github**| [google/go-github](https://github.com/google/go-github) ### Haskell -Library name | Repository |---|---| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) +Nome da biblioteca | Repositório |---|---| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) ### Java -Library name | Repository | More information |---|---|---| **GitHub Java API**| [org.eclipse.egit.github.core](https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core) | Is part of the [GitHub Mylyn Connector](https://github.com/eclipse/egit-github) and aims to support the entire GitHub v3 API. As construções estão disponíveis em [Maven Central](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.egit.github.core%22). **GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API. **JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API. +Nome da biblioteca | Repositório | Mais informações |---|---|---| **GitHub Java API**| [org.eclipse.egit.github.core](https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core) | É parte do [GitHub Mylyn Connector](https://github.com/eclipse/egit-github) e tem o objetivo de dar suporte a toda a API do GitHub v3. As construções estão disponíveis em [Maven Central](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.egit.github.core%22). **GitHub API para Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|define uma representação orientada por objeto da API do GitHub. **JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|é baseado Java7 JSON API (JSR-353), simplifica testes com uma amostra de tempo de execução do GitHub e abrange toda a API. ### JavaScript -Library name | Repository | |---|---| **NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode) **gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3) **Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github) **Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client) +Nome da biblioteca | Repositório | |---|---| **NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode) **gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3) **Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github) **Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client) ### Julia -Library name | Repository | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Nome da biblioteca | Repositório | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml -Library name | Repository | |---|---| **ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github) +Nome da biblioteca | Repositório | |---|---| **ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github) ### Perl -Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Nome da biblioteca | Repositório | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Nome da biblioteca | Repositório |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python -Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby -Library name | Repository |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +Nome da biblioteca | Repositório |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) + +### Rust + +Nome da biblioteca | Repositório |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) ### Scala -Library name | Repository |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) +Nome da biblioteca | Repositório |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) ### Shell -Library name | Repository |---|---| **ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) +Nome da biblioteca | Repositório |---|---| **ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) diff --git a/translations/pt-BR/content/rest/overview/media-types.md b/translations/pt-BR/content/rest/overview/media-types.md index 87ce065372..48b1308d5f 100644 --- a/translations/pt-BR/content/rest/overview/media-types.md +++ b/translations/pt-BR/content/rest/overview/media-types.md @@ -21,7 +21,7 @@ Os tipos mais básicos de mídia que a API suporta são: application/json application/vnd.github+json -Neither of these specify a [version][versions], so you will always get the current default JSON representation of resources. +Nenhum desses parâmetros especifica a versão [][versions]. Portanto, você sempre receberá a representação atual do JSON padrão atual de recursos. {% note %} @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### Propriedades do texto do comentário -The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: +O texto de um comentário pode ser escrito no [Linguagem de Markdown enriquecido][gfm], [problemas](/rest/reference/issues), [comentários do problema](/rest/reference/issues#comments), [comentários de pull request](/rest/reference/pulls#comments) e as APIs dos [comentários de gist](/rest/reference/gists#comments) aceitam todos esses mesmos tipos de mídia: #### Sem processar @@ -85,7 +85,7 @@ Retorna as representações de HTML e texto sem processar. A resposta incluirá ### Propriedades do Git blob -The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): +Os seguintes tipos de mídia são permitidos ao [receber um blob](/rest/reference/git#get-a-blob): #### JSON @@ -102,7 +102,7 @@ Retorna os dados do blob sem processamento. ### Commits, comparação de commit e pull requests -The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: +A [API de commits](/rest/reference/repos#commits) e [API de pull requests](/rest/reference/pulls) são compatíveis com os formatos [diff][git-diff] e [patch][git-patch]: #### diff @@ -148,3 +148,4 @@ O conteúdo do gist é codificado em base64 antes de ser enviado. Isso pode ser [git-diff]: http://git-scm.com/docs/git-diff [git-patch]: http://git-scm.com/docs/git-format-patch [versions]: /developers/overview/about-githubs-apis +[versions]: /developers/overview/about-githubs-apis diff --git a/translations/pt-BR/content/rest/overview/openapi-description.md b/translations/pt-BR/content/rest/overview/openapi-description.md index 5b1fc1673e..46c78c9713 100644 --- a/translations/pt-BR/content/rest/overview/openapi-description.md +++ b/translations/pt-BR/content/rest/overview/openapi-description.md @@ -1,27 +1,27 @@ --- -title: OpenAPI description -intro: The {% data variables.product.product_name %} REST API is fully described in an OpenAPI 3.0 compliant document. +title: Descrição da OpenAPI +intro: A API REST de {% data variables.product.product_name %} está totalmente descrita em um documento compatível com a OpenAPI 3.0. versions: free-pro-team: '*' enterprise-server: '*' --- -### About OpenAPI descriptions +### Sobre descrições da OpenAPI -[OpenAPI](https://swagger.io/docs/specification/about/) is a standard specification for describing REST APIs. OpenAPI descriptions allow both humans and machines to discover the capabilities of an API without needing to first read documentation or understand the implementation. {% data variables.product.company_short %} has made its REST API publicly available as an OpenAPI 3.0 compliant document. +[OpenAPI](https://swagger.io/docs/specification/about/) é uma especificação padrão para descrever as APIs REST. As descrições da OpenAPI permitem que tanto pessoas quanto máquinas descubram as capacidades de uma API sem precisar ler primeiro a documentação ou entender a implementação. {% data variables.product.company_short %} tornou sua API REST disponível publicamente como um documento compatível com OpenAPI 3.0. -### Getting the {% data variables.product.company_short %} OpenAPI description +### Obter a descrição da OpenAPI de {% data variables.product.company_short %} -You can find the description in the open source [REST API OpenAPI Description](https://github.com/github/rest-api-description) repository. +Você pode encontrar a descrição no repositório de código aberto no repositório da [Descrição da OpenAPI da API REST](https://github.com/github/rest-api-description). -We provide the description in two formats. The bundled version works for most cases, as it includes OpenAPI components for reuse and readability. If your tooling does not support inline references to components, we also provide a fully dereferenced version. +Fornecemos a descrição em dois formatos. A versão empacotada funciona para a maioria dos casos, pois inclui componentes da OpenAPI para reutilização e legibilidade. Se sua ferramenta de ferramentas não for compatíveis com referências e componentes dentro das linhas, nós também fornecemos uma versão totalmente sem referência. -### Using the {% data variables.product.company_short %} OpenAPI description +### Usara descrição da OpenAPI de {% data variables.product.company_short %} -There are many uses for an OpenAPI description. Por exemplo, você pode: +Existem diversos usos para a descrição da OpenAPI. Por exemplo, você pode: -* Generate your own API client. -* Validate and test a {% data variables.product.company_short %} REST API integration. -* Explore and interact with the {% data variables.product.product_name %} REST API using third-party tools, such as Insomnia or Postman. +* Gerar o seu próprio cliente da API. +* Validar e testar uma integração da API REST de {% data variables.product.company_short %}. +* Explorar e interagir com a API REST de {% data variables.product.product_name %}, usando ferramentas de terceiros, como Insomnia ou Postman. -For example, {% data variables.product.company_short %} uses the REST OpenAPI description to generate the {% data variables.product.product_name %} [REST API reference documentation](/rest/reference). +Por exemplo, {% data variables.product.company_short %} usa a descrição da OpenAPI do REST para gerar a [documentação de referência da API REST](/rest/reference) de {% data variables.product.product_name %}. diff --git a/translations/pt-BR/content/rest/overview/other-authentication-methods.md b/translations/pt-BR/content/rest/overview/other-authentication-methods.md index c3fa745650..b66b43742c 100644 --- a/translations/pt-BR/content/rest/overview/other-authentication-methods.md +++ b/translations/pt-BR/content/rest/overview/other-authentication-methods.md @@ -19,7 +19,7 @@ Em vez disso, eles devem usar o [Fluxo web do OAuth](/apps/building-oauth-apps/a {% if currentVersion == "github-ae@latest" %} -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/). +Para efetuar a autenticação, recomendamos usar tokens do [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) como um token de acesso pessoal por meio do [fluxo web do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). {% endif %} @@ -43,16 +43,16 @@ Esta abordagem é útil se suas ferramentas são compatíveis apenas com a Auten {% note %} -**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 {% data variables.product.prodname_dotcom %} 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)." +**Observação:** {% data variables.product.prodname_dotcom %} suspendeu a autenticação da senha para a API a partir de 13 de novembro 2020 para todas as contas de {% data variables.product.prodname_dotcom_the_website %}, incluindo as que estão em um plano de {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. Você deve efetuar a autenticação para a API de {% data variables.product.prodname_dotcom %} com um token da API, como um token de acesso do OAuth, token de acesso de instalação do aplicativo GitHub ou token de acesso pessoal, dependendo do que você precisa fazer com o token. Para obter mais informações, consulte "[Solução de problemas](/rest/overview/troubleshooting#basic-authentication-errors)". {% endnote %} {% endif %} {% if enterpriseServerVersions contains currentVersion %} -To use Basic Authentication with the -{% data variables.product.product_name %} API, simply send the username and -password associated with the account. +Para usar Autenticação Básica com a +API de {% data variables.product.product_name %}, basta enviar o nome de usuário e +a senha associada à conta. Por exemplo, se você estiver acessando a API via [cURL][curl], o comando a seguir faria a sua autenticação se substituísse `` pelo seu nome de usuário de {% data variables.product.product_name %}. (cURL solicitará que você insira a senha.) @@ -98,9 +98,9 @@ O valor das `organizações` é uma lista de ID de organizações separada por v {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} ### Trabalhar com autenticação de dois fatores -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{% if enterpriseServerVersions contains currentVersion %} or OAuth token instead of your username and password{% endif %}. +Quando você tem a autenticação de dois fatores habilitada, a [Autenticação básica](#basic-authentication) para _a maioria dos_ pntos de extremidade na API REST exige que você use um token de acesso pessoal{% if enterpriseServerVersions contains currentVersion %} ou token do OAuth em vez do seu nome de usuário e senha{% endif %}. -You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% if enterpriseServerVersions contains currentVersion %} 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 %}. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/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 {% data variables.product.prodname_dotcom %} API.{% if enterpriseServerVersions contains currentVersion %} 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 %} +Você pode gerar um novo token de acesso pessoal {% if currentVersion == "free-pro-team@latest" %}usando [ as configurações de desenvolvedor de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %}{% if enterpriseServerVersions contains currentVersion %} ou com o ponto de extremidade "\[Criar uma nova autorização\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" na API de Autorizações OAuth para gerar um novo token OAuth{% endif %}. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Em seguida, você usaria esses tokens para [efetuar a autenticação usando o token do OAuth][oauth-auth] com a API de {% data variables.product.prodname_dotcom %}. {% if enterpriseServerVersions contains currentVersion %} A única vez que você precisa efetuar a autenticação com seu nome de usuário e senha é quando você cria seu token do OAuth ou usa a API de Autorização do OAuth.{% endif %} {% endif %} diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 062ccc1e80..7adcd7c201 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -1,6 +1,6 @@ --- -title: Resources in the REST API -intro: 'Learn how to navigate the resources provided by the {% data variables.product.prodname_dotcom %} API.' +title: Recursos na API REST +intro: 'Aprenda a navegar nos recursos fornecidos pela API de {% data variables.product.prodname_dotcom %}.' redirect_from: - /rest/initialize-the-repo/ versions: @@ -10,28 +10,27 @@ versions: --- -This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}. +Isso descreve os recursos que formam a API REST oficial de {% data variables.product.product_name %}. Em caso de problema ou solicitação, entre em contato com {% data variables.contact.contact_support %}. -### Current version +### Versão atual -By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. -We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). +Por padrão, todas as solicitações para `{% data variables.product.api_url_code %}` recebem a versão **v3** [](/developers/overview/about-githubs-apis) da API REST. Nós incentivamos que você a [solicite explicitamente esta versão por meio do cabeçalho `Aceitar`](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -For information about GitHub's GraphQL API, see the [v4 documentation](/graphql). For information about migrating to GraphQL, see "[Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)." +Para obter informações sobre a API do GraphQL do GitHub, consulte a [documentação v4](/graphql). Para obter informações sobre migração para o GraphQL, consulte "[Fazendo a migração do REST](/graphql/guides/migrating-from-rest-to-graphql)". {% endif %} -### Schema +### Esquema -{% if currentVersion == "free-pro-team@latest" %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`. All data is -sent and received as JSON. +{% if currentVersion == "free-pro-team@latest" %}Todo o acesso à API é feito por meio de HTTPS, e{% else %}A API é{% endif %} acessada a partir de `{% data variables.product.api_url_code %}`. Todos os dados são +enviados e recebidos como JSON. ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs +$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > HTTP/1.1 200 OK > Server: nginx @@ -50,55 +49,43 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs > X-Content-Type-Options: nosniff ``` -Blank fields are included as `null` instead of being omitted. +Os campos em branco são incluídos como `null` em vez de serem omitidos. -All timestamps return in ISO 8601 format: +Todos os registros de tempo são retornados no formato ISO 8601: YYYY-MM-DDTHH:MM:SSZ -For more information about timezones in timestamps, see [this section](#timezones). +Para obter mais informações sobre fusos horários nos registros de tempo, consulte [esta seção](#timezones). -#### Summary representations +#### Apresentações resumidas -When you fetch a list of resources, the response includes a _subset_ of the -attributes for that resource. This is the "summary" representation of the -resource. (Some attributes are computationally expensive for the API to provide. -For performance reasons, the summary representation excludes those attributes. -To obtain those attributes, fetch the "detailed" representation.) +Ao buscar uma lista de recursos, a resposta inclui um _subconjunto_ dos atributos para esse recurso. Esta é a representação "resumo" do recurso. (Alguns atributos são computacionalmente caros para a API fornecer. Por razões de desempenho, a representação resumida exclui esses atributos. Para obter esses atributos, busque a representação "detalhada".) -**Example**: When you get a list of repositories, you get the summary -representation of each repository. Here, we fetch the list of repositories owned -by the [octokit](https://github.com/octokit) organization: +**Exemplo**: ao receber uma lista de repositórios, você recebe a representação resumida de cada repositório. Aqui, buscamos a lista de repositórios pertencentes a à organização do [octokit](https://github.com/octokit): GET /orgs/octokit/repos -#### Detailed representations +#### Representações detalhadas -When you fetch an individual resource, the response typically includes _all_ -attributes for that resource. This is the "detailed" representation of the -resource. (Note that authorization sometimes influences the amount of detail -included in the representation.) +Ao buscar um recurso individual, a resposta normalmente inclui _todos os_ atributos para esse recurso. Esta é a representação "detalhada" do recurso. (Note que a autorização por vezes influencia o valor de detalhes incluído na representação.) -**Example**: When you get an individual repository, you get the detailed -representation of the repository. Here, we fetch the -[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository: +**Exemplo**: ao receber um repositório individual, você recebe a representação detalhada do repositório. Aqui, nós buscamos o repositório [octokit/octokit.rb](https://github.com/octokit/octokit.rb): GET /repos/octokit/octokit.rb -The documentation provides an example response for each API method. The example -response illustrates all attributes that are returned by that method. +A documentação fornece um exemplo de resposta para cada método da API. O exemplo da resposta ilustra todos os atributos retornados por esse método. -### Authentication +### Autenticação -{% if currentVersion == "github-ae@latest" %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places. This is to prevent the accidental leakage of private repositories to unauthorized users. +{% if currentVersion == "github-ae@latest" %} Recomendamos efetuar a autenticação na API REST de {% data variables.product.product_name %}, criando um token OAuth2 por meio do [fluxo do aplicativo web](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} Existem duas maneiras de efetuar a autenticação por meio da API REST de {% data variables.product.product_name %}.{% endif %} As solicitações que exigem autenticação retornarão `404 Not Found`, em vez de `403 Forbidden` em alguns lugares. Isso é para evitar a fuga acidental de repositórios privados para usuários não autorizados. -#### Basic authentication +#### Autenticação básica ```shell $ curl -u "username" {% data variables.product.api_url_pre %} ``` -#### OAuth2 token (sent in a header) +#### Token do OAuth2 (enviado em um cabeçalho) ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} @@ -106,11 +93,11 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. {% note %} -Note: GitHub recommends sending OAuth tokens using the Authorization header. +Observação: O GitHub recomenda enviar tokens do OAuth usando o cabeçalho de autorização. {% endnote %} -Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications. +Leia [mais sobre o OAuth2](/apps/building-oauth-apps/). Observe que os tokens do OAuth2 podem ser adquiridos usando o [fluxo de aplicação web](/developers/apps/authorizing-oauth-apps#web-application-flow) para aplicativos de produção. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} #### OAuth2 key/secret @@ -121,23 +108,23 @@ Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens c curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' ``` -Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users. +Usar o seu `client_id` e `client_secret` _ não_ autenticam você como usuário. Isso apenas irá identificar o seu aplicativo OAuth para aumentar o seu limite de taxa. As permissões só são concedidas a usuários, não aplicativos, e você só obterá dados que um usuário não autenticado visualizaria. Por este motivo, você só deve usar a chave/segredo OAuth2 em cenários de servidor para servidor. Não compartilhe o segredo do cliente do aplicativo OAuth com os seus usuários. -You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/enterprise/admin/installation/enabling-private-mode)". +Você não conseguirá efetuar a autenticação usando sua chave e segredo do OAuth2 enquanto estiver no modo privado e essa tentativa de autenticação irá retornar `401 Unauthorized`. Para obter mais informações, consulte "[Habilitar o modo privado](/enterprise/admin/installation/enabling-private-mode)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} -Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Leia [Mais informações sobre limitação da taxa não autenticada](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). {% endif %} -#### Failed login limit +#### Falha no limite de login -Authenticating with invalid credentials will return `401 Unauthorized`: +A autenticação com credenciais inválidas retornará `401 Unauthorized`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar +$ curl -I {% data variables.product.api_url_pre %} -u foo:bar > HTTP/1.1 401 Unauthorized > { @@ -146,9 +133,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar > } ``` -After detecting several requests with invalid credentials within a short period, -the API will temporarily reject all authentication attempts for that user -(including ones with valid credentials) with `403 Forbidden`: +Após detectar várias solicitações com credenciais inválidas em um curto período de tempo, a API rejeitará temporariamente todas as tentativas de autenticação para esse usuário (incluindo aquelas com credenciais válidas) com `403 Forbidden`: ```shell $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} @@ -160,216 +145,192 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > } ``` -### Parameters +### Parâmetros -Many API methods take optional parameters. For `GET` requests, any parameters not -specified as a segment in the path can be passed as an HTTP query string -parameter: +Muitos métodos de API tomam parâmetros opcionais. Para solicitações tipo `GET`, todos os parâmetros não especificados como um segmento no caminho podem ser passados como um parâmetro de string de consulta de HTTP: ```shell $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" ``` -In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner` -and `:repo` parameters in the path while `:state` is passed in the query -string. +Neste exemplo, os valores 'vmg' e 'redcarpet' são fornecidos para os parâmetros `:owner` e `:repo` no caminho enquanto `:state` é passado na string da consulta. -For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON -with a Content-Type of 'application/json': +Para solicitações de `POST`, `PATCH`, `PUT`e `EXCLUIR`, os parâmetros não incluídos na URL devem ser codificados como JSON com um Content-Type de 'application/json': ```shell $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.api_url_pre %}/authorizations ``` -### Root endpoint +### Ponto de extremidade raiz -You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports: +Você pode emitir uma solicitação `GET` para o ponto de extremidade de raiz para obter todas as categorias do ponto de extremidade com a qual a API REST é compatível: ```shell $ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} -u username:token {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u username:password {% endif %}{% data variables.product.api_url_pre %} ``` -### GraphQL global node IDs +### IDs de nós globais do GraphQL -See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. +Consulte o guia em "[Usar IDs do nó globais ](/graphql/guides/using-global-node-ids)" para obter informações detalhadas sobre como encontrar `node_id`s através da API REST e usá-los em operações do GraphQL. -### Client errors +### Erros do cliente -There are three possible types of client errors on API calls that -receive request bodies: +Há três tipos possíveis de erros de cliente na chamadas da API que recebem textos: -1. Sending invalid JSON will result in a `400 Bad Request` response. +1. O envio de um JSON inválido resultará em uma resposta     400 Bad Request`.

    - HTTP/1.1 400 Bad Request - Content-Length: 35 +
     HTTP/1.1 400 Bad Request
+ Content-Length: 35
 
-        {"message":"Problems parsing JSON"}
+ {"message":"Problems parsing JSON"}
+`
    -2. Sending the wrong type of JSON values will result in a `400 Bad - Request` response. +2 - HTTP/1.1 400 Bad Request - Content-Length: 40 +Enviar o tipo incorreto de valores do JSON resultará em uma resposta `400 Bad +Request`. + + HTTP/1.1 400 Bad Request + Content-Length: 40 + + {"message":"Body should be a JSON object"} - {"message":"Body should be a JSON object"} +3 -3. Sending invalid fields will result in a `422 Unprocessable Entity` - response. +O envio de campos inválidos resultará em uma resposta `422 Unprocessable Entity`. + + HTTP/1.1 422 Unprocessable Entity + Content-Length: 149 + + { + "message": "Validation Failed", + "errors": [ + { + "resource": "Issue", + "field": "title", + "code": "missing_field" + } + ] + } + - HTTP/1.1 422 Unprocessable Entity - Content-Length: 149 +Todos objetos de erro têm propriedades de recurso e campo para que seu cliente possa dizer qual é o problema. Também há um código de erro para informar o que há de errado com o campo. Estes são os possíveis códigos de validação: - { - "message": "Validation Failed", - "errors": [ - { - "resource": "Issue", - "field": "title", - "code": "missing_field" - } - ] - } +| Nome do código de erro | Descrição | +| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `missing` | Um recurso não existe. | +| `missing_field` | Não foi definido um campo obrigatório em um recurso. | +| `invalid` | Formatação de um campo é inválida. Revise a documentação para obter informações mais específicas. | +| `already_exists` | Outro recurso tem o mesmo valor que este campo. Isso pode acontecer em recursos que precisam ter alguma chave única (como nomes de etiqueta). | +| `unprocessable` | As entradas fornecidas eram inválidas. | -All error objects have resource and field properties so that your client -can tell what the problem is. There's also an error code to let you -know what is wrong with the field. These are the possible validation error -codes: +Os recursos também podem enviar erros de validação personalizados (em que o `código` é `personalizado`). Os erros personalizados sempre terão um campo de `mensagem` que descreve o erro e a maioria dos erros também incluirá um campo de `documentation_url` que aponta para algum conteúdo que pode ajudá-lo a resolver o erro. -Error code name | Description ------------|-----------| -`missing` | A resource does not exist. -`missing_field` | A required field on a resource has not been set. -`invalid` | The formatting of a field is invalid. Review the documentation for more specific information. -`already_exists` | Another resource has the same value as this field. This can happen in resources that must have some unique key (such as label names). -`unprocessable` | The inputs provided were invalid. +### Redirecionamentos HTTP -Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error. +API v3 usa redirecionamento HTTP quando apropriado. Os clientes devem assumir que qualquer solicitação pode resultar em redirecionamento. Receber um redirecionamento de HTTP *não* é um erro e os clientes devem seguir esse redirecionamento. As respostas de redirecionamento terão um campo do cabeçalho do tipo `Localização` que contém o URI do recurso ao qual o cliente deve repetir as solicitações. -### HTTP redirects +| Código de status | Descrição | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `301` | Redirecionamento permanente. O URI que você usou para fazer a solicitação foi substituído pelo especificado no campo do cabeçalho `Localização`. Este e todas as solicitações futuras deste recurso devem ser direcionadas para o novo URI. | +| `302`, `307` | Redirecionamento temporário. A solicitação deve ser repetida literalmente para o URI especificado no campo de cabeçalho `Localização`, mas os clientes devem continuar a usar o URI original para solicitações futuras. | -API v3 uses HTTP redirection where appropriate. Clients should assume that any -request may result in a redirection. Receiving an HTTP redirection is *not* an -error and clients should follow that redirect. Redirect responses will have a -`Location` header field which contains the URI of the resource to which the -client should repeat the requests. +Outros códigos de status de redirecionamento podem ser usados de acordo com a especificação HTTP 1.1. -Status Code | Description ------------|-----------| -`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI. -`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests. +### Verbos HTTP -Other redirection status codes may be used in accordance with the HTTP 1.1 spec. +Quando possível, a API v3 se esforça para usar verbos HTTP apropriados para cada ação. -### HTTP verbs +| Verbo | Descrição | +| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `HEAD` | Pode ser emitido contra qualquer recurso para obter apenas as informações de cabeçalho HTTP. | +| `GET` | Usado para recuperar recursos. | +| `POST` | Usado para criar recursos. | +| `PATCH` | Usado para atualizar recursos com dados parciais do JSON. Por exemplo, um recurso de um problema tem atributos de `título` e `texto`. Uma solicitação de `PATCH` pode aceitar um ou mais dos atributos para atualizar o recurso. | +| `PUT` | Usado para substituir recursos ou coleções. Para as solicitações de `PUT` sem atributo de `texto`, certifique-se de definir o cabeçalho `Content-Length` como zero. | +| `DELETE` | Usado para excluir recursos. | -Where possible, API v3 strives to use appropriate HTTP verbs for each -action. +### Hipermídia -Verb | Description ------|----------- -`HEAD` | Can be issued against any resource to get just the HTTP header info. -`GET` | Used for retrieving resources. -`POST` | Used for creating resources. -`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource. -`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero. -`DELETE` |Used for deleting resources. +Todos os recursos podem ter uma ou mais propriedades `*_url` vinculando outros recursos. Estes tem o objetivo de fornecer URLs explícitas para que os clientes API apropriados não precisem construir URLs por conta própria. É altamente recomendável que os clientes da API os utilizem. Fazer isso tornará as futuras atualizações da API mais fáceis para os desenvolvedores. Espera-se que todas as URLs sejam modelos de URI [RFC 6570][rfc] adequados. -### Hypermedia - -All resources may have one or more `*_url` properties linking to other -resources. These are meant to provide explicit URLs so that proper API clients -don't need to construct URLs on their own. It is highly recommended that API -clients use these. Doing so will make future upgrades of the API easier for -developers. All URLs are expected to be proper [RFC 6570][rfc] URI templates. - -You can then expand these templates using something like the [uri_template][uri] -gem: +Então você pode expandir estes modelos usando algo como o [uri_template][uri] gem: >> tmpl = URITemplate.new('/notifications{?since,all,participating}') >> tmpl.expand => "/notifications" - + >> tmpl.expand :all => 1 => "/notifications?all=1" - + >> tmpl.expand :all => 1, :participating => 1 => "/notifications?all=1&participating=1" -[rfc]: http://tools.ietf.org/html/rfc6570 -[uri]: https://github.com/hannesg/uri_template +### Paginação -### Pagination - -Requests that return multiple items will be paginated to 30 items by -default. You can specify further pages with the `page` parameter. For some -resources, you can also set a custom page size up to 100 with the `per_page` parameter. -Note that for technical reasons not all endpoints respect the `per_page` parameter, -see [events](/rest/reference/activity#events) for example. +Pedidos que retornam vários itens serão paginados para 30 itens por padrão. Você pode especificar mais páginas com o parâmetro `page`. Para alguns recursos, você também pode definir um tamanho de página até 100 com o parâmetro `per_page`. Observe que, por razões técnicas, nem todos os pontos de extremidade respeitam o parâmetro `per_page`, veja [eventos](/rest/reference/activity#events) por exemplo. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Note that page numbering is 1-based and that omitting the `page` -parameter will return the first page. +Observe que a numeração da página é baseada em 1 e que, ao omitir o parâmetro `page`, retornará a primeira página. -Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set. -With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page. -Instead, you can traverse the results by using the `before` or `after` parameters. +Alguns pontos de extremidade usam paginação baseada no cursor. Um cursor é uma string que aponta para uma localização no conjunto de resultados. Com paginação baseada em cursor, não há um conceito fixo de "páginas" no conjunto de resultados. Portanto, você não pode navegar para uma página específica. Em vez disso, você pode percorrer os resultados usando os parâmetros `antes` ou `após`. -For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. +Para obter mais informações sobre paginação, confira nosso guia sobre [Passar com paginação][pagination-guide]. -#### Link header +#### Cabeçalho do link {% note %} -**Note:** It's important to form calls with Link header values instead of constructing your own URLs. +**Observação:** É importante formar chamadas com valores de cabeçalho de link, em vez de construir suas próprias URLs. {% endnote %} -The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. For example: +O [cabeçalho do link](http://tools.ietf.org/html/rfc5988) inclui informações de paginação. Por exemplo: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" -_The example includes a line break for readability._ +_O exemplo inclui uma quebra de linha para legibilidade._ -Or, if the endpoint uses cursor-based pagination: +Ou, se o ponto de extremidade usar paginação baseada em cursor: Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", -This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). +Este `Link` de resposta contém um ou mais links de relações de [hipermídia](/rest#hypermedia), alguns dos quais podem exigir expansão como [modelos de URI](http://tools.ietf.org/html/rfc6570). -The possible `rel` values are: +Os valores de `rel` possíveis são: -Name | Description ------------|-----------| -`next` |The link relation for the immediate next page of results. -`last` |The link relation for the last page of results. -`first` |The link relation for the first page of results. -`prev` |The link relation for the immediate previous page of results. +| Nome | Descrição | +| --------- | ---------------------------------------------------------------- | +| `avançar` | A relação de link para a próxima página de resultados. | +| `last` | A relação de link para a última página de resultados. | +| `first` | A relação de link para a primeira página de resultados. | +| `prev` | A relação de link para a página de resultados anterior imediata. | -### Rate limiting +### Limite de taxa -For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user. +Para solicitações de API que usam a Autenticação Básica ou OAuth, você pode criar até 5.000 solicitações por hora. As solicitações de autenticação são associadas ao usuário autenticado, independentemente de [Autenticação Básica](#basic-authentication) ou [um token do OAuth](#oauth2-token-sent-in-a-header) ter sido usado. Isto significa que todos os aplicativos OAuth autorizados por um usuário compartilham a mesma cota de 5.000 solicitações por hora quando eles são autenticados com diferentes tokens pertencentes ao mesmo usuário. {% if currentVersion == "free-pro-team@latest" %} -For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour. +Para usuários que pertencem a uma conta {% data variables.product.prodname_ghe_cloud %}, solicitações feitas usando um token OAuth para recursos pertencentes à mesma conta de {% data variables.product.prodname_ghe_cloud %} têm um aumento de 15.000 solicitações por hora no limite. {% endif %} -For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests. +Para solicitações não autenticadas, o limite de taxa permite até 60 solicitações por hora. Solicitações não autenticadas estão associadas ao endereço IP original, e não ao usuário que faz solicitações. {% data reusables.enterprise.rate_limit %} -Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). +Observe que [a API de pesquisa tem regras de limite de taxa personalizadas](/rest/reference/search#rate-limit). -The returned HTTP headers of any API request show your current rate limit status: +Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu status atual de limite de taxa: ```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat +$ curl -I {% data variables.product.api_url_pre %}/users/octocat > HTTP/1.1 200 OK > Date: Mon, 01 Jul 2013 17:27:06 GMT > Status: 200 OK @@ -378,20 +339,20 @@ $ curl -i {% data variables.product.api_url_pre %}/users/octocat > X-RateLimit-Reset: 1372700873 ``` -Header Name | Description ------------|-----------| -`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour. -`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window. -`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time). +| Nome do Cabeçalho | Descrição | +| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-RateLimit-Limit` | O número máximo de solicitações que você pode fazer por hora. | +| `X-RateLimit-Remaining` | O número de solicitações restantes na janela de limite de taxa atual. | +| `X-RateLimit-Reset` | O tempo em que a janela de limite de taxa atual é redefinida em [segundos no tempo de computação de UTC](http://en.wikipedia.org/wiki/Unix_time). | -If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object. +Se você precisar de outro formato de tempo, qualquer linguagem de programação moderna pode fazer o trabalho. Por exemplo, se você abrir o console em seu navegador, você pode facilmente obter o tempo de redefinição como um objeto de tempo do JavaScript. ``` javascript new Date(1372700873 * 1000) // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT) ``` -If you exceed the rate limit, an error response returns: +Se você exceder o limite de taxa, uma resposta do erro retorna: ```shell > HTTP/1.1 403 Forbidden @@ -407,11 +368,11 @@ If you exceed the rate limit, an error response returns: > } ``` -You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. +Você pode [verificar o status do seu limite de taxa](/rest/reference/rate-limit) sem a incorrer em uma consulta da API. -#### Increasing the unauthenticated rate limit for OAuth applications +#### Aumentar o limite de taxa não autenticado para aplicativos OAuth -If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route. +Se o seu aplicativo OAuth precisar fazer chamadas não autenticadas com um limite de taxa mais alto, você poderá passar o ID e o segredo do cliente do seu aplicativo antes do encaminhamento de pontos de extremidade. ```shell $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos @@ -425,21 +386,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} {% note %} -**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls. +**Observação:** Nunca compartilhe seu segredo de cliente com alguém ou o inclua no código do navegador do lado do cliente. Use o método mostrado aqui apenas para chamadas de servidor para servidor. {% endnote %} -#### Staying within the rate limit +#### Manter-se dentro do limite de taxa -If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests). +Se você exceder seu limite de taxa usando a Autenticação Básica ou OAuth, você poderá corrigir o problema armazenando respostas da API e usando [solicitações condicionais](#conditional-requests). -#### Abuse rate limits +#### Abusar dos limites de taxa -In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in abuse rate limiting. +A fim de fornecer serviço de qualidade no {% data variables.product.product_name %}, podem-se aplicar limites de taxa adicionais podem a algumas ações ao usar a API. Por exemplo, usar a API para criar rapidamente conteúdo, fazer sondagem de modo agressivo em vez de usar webhooks, fazer várias solicitações simultâneas ou solicitar repetidamente dados caros do ponto de vista computacional podem resultar na limitação da taxa de abuso. -Abuse rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/). +O abuso dos limites de taxa não são destinados a interferir no uso legítimo da API. Seus limites de taxa normais devem ser o único limite em que você deve focar. Para garantir que você está agindo como um bom cidadão da API, confira nossas [Diretrizes sobre práticas recomendadas](/guides/best-practices-for-integrators/). -If your application triggers this rate limit, you'll receive an informative response: +Se seu aplicativo acionar este limite de taxa, você receberá uma resposta informativa: ```shell > HTTP/1.1 403 Forbidden @@ -454,22 +415,20 @@ If your application triggers this rate limit, you'll receive an informative resp {% if currentVersion == "free-pro-team@latest" %} -### User agent required +### Agente de usuário obrigatório -All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent` -header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your -application, for the `User-Agent` header value. This allows us to contact you if there are problems. +Todas as solicitações da API DEVEM incluir um cabeçalho válido de `User-Agent`. As requisições sem o cabeçalho do `User-Agent` serão rejeitadas. Pedimos que use seu nome de usuário de {% data variables.product.product_name %} ou o nome de seu aplicativo, para o valor do cabeçalho `User-Agent`. Isso nos permite entrar em contato com você, em caso de problemas. -Here's an example: +Aqui está um exemplo: ```shell User-Agent: Awesome-Octocat-App ``` -cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: +A cURL envia um cabeçalho válido do `User-Agent` por padrão. Se você fornecer um cabeçalho inválido de `User-Agent` via cURL (ou via um cliente alternativo), você receberá uma resposta `403 Forbidden`: ```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta +$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > HTTP/1.0 403 Forbidden > Connection: close > Content-Type: text/html @@ -481,27 +440,22 @@ $ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta {% endif %} -### Conditional requests +### Solicitações condicionais -Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values -of these headers to make subsequent requests to those resources using the -`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource -has not changed, the server will return a `304 Not Modified`. +A maioria das respostas retorna um cabeçalho de Etag`. Muitas respostas também retornam um cabeçalho Last-Modified`. Você pode usar os valores desses cabeçalhos para fazer solicitações subsequentes para esses recursos usando os cabeçalhos `If-None-Match` e `If-Modified-Desde`, respectivamente. Se o recurso não foi alterado, o servidor retornará `304 não modificado`. {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Note**: Making a conditional request and receiving a 304 response does not -count against your [Rate Limit](#rate-limiting), so we encourage you to use it -whenever possible. +**Observação**: Fazer uma solicitação condicional e receber uma resposta 304 não conta para o seu [Limite de Taxa](#rate-limiting). Portanto, recomendamos que você o utilize sempre que possível. {% endtip %} {% endif %} ```shell -$ curl -i {% data variables.product.api_url_pre %}/user +$ curl -I {% data variables.product.api_url_pre %}/user > HTTP/1.1 200 OK > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -512,7 +466,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" @@ -523,7 +477,7 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b > X-RateLimit-Remaining: 4996 > X-RateLimit-Reset: 1372700873 -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" +$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" > HTTP/1.1 304 Not Modified > Cache-Control: private, max-age=60 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT @@ -534,28 +488,23 @@ $ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T > X-RateLimit-Reset: 1372700873 ``` -### Cross origin resource sharing +### Compartilhamento de recursos de origem cruzada -The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from -any origin. -You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or -[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the -HTML 5 Security Guide. +A API é compatível com Compartilhamento de Recursos de Origens Cruzadas (CORS) para solicitações de AJAX de qualquer origem. You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or [this intro](http://code.google.com/p/html5security/wiki/CrossOriginRequestSecurity) from the HTML 5 Security Guide. -Here's a sample request sent from a browser hitting -`http://example.com`: +Aqui está uma solicitação de exemplo enviada a partir de uma consulta em `http://exemplo.com`: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" HTTP/1.1 302 Found Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval ``` -This is what the CORS preflight request looks like: +A solicitação pré-voo de CORS se parece com isso: ```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS +$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS HTTP/1.1 204 No Content Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With @@ -564,13 +513,9 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra Access-Control-Max-Age: 86400 ``` -### JSON-P callbacks +### Chamadas de retorno do JSON-P -You can send a `?callback` parameter to any GET call to have the results -wrapped in a JSON function. This is typically used when browsers want -to embed {% data variables.product.product_name %} content in web pages by getting around cross domain -issues. The response includes the same data output as the regular API, -plus the relevant HTTP Header information. +Você pode enviar um parâmetro `?callback` para qualquer chamada de GET para envolver os resultados em uma função JSON. Isso é normalmente usado quando os navegadores querem que incorporem {% data variables.product.product_name %} conteúdo em páginas da web, contornando problemas de de domínio cruzado. A resposta inclui a mesma saída de dados da API regular, mais as informações relevantes do cabeçalho de HTTP. ```shell $ curl {% data variables.product.api_url_pre %}?callback=foo @@ -591,7 +536,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo > }) ``` -You can write a JavaScript handler to process the callback. Here's a minimal example you can try out: +Você pode escrever um manipulador do JavaScript para processar o retorno de chamada. Aqui está um exemplo pequeno que você pode experimentar: @@ -602,28 +547,26 @@ You can write a JavaScript handler to process the callback. Here's a minimal exa console.log(meta); console.log(data); } - + var script = document.createElement('script'); script.src = '{% data variables.product.api_url_code %}?callback=foo'; - + document.getElementsByTagName('head')[0].appendChild(script); - +

    Open up your browser's console.

    -All of the headers are the same String value as the HTTP Headers with one -notable exception: Link. Link headers are pre-parsed for you and come -through as an array of `[url, options]` tuples. +Todos os cabeçalhos têm o mesmo valor d a string que os cabeçalhos de HTTP com uma exceção notável: Link. Cabeçalhos de link são pré-analisados para você e chegam como um array de tuplas de `[url, options]`. -A link that looks like this: +Um link que se parece com isto: Link: ; rel="next", ; rel="foo"; bar="baz" -... will look like this in the Callback output: +... será mostrado assim na saída da chamada de retorno: ```json { @@ -645,37 +588,40 @@ A link that looks like this: } ``` -### Timezones +### Fusos horários -Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for API calls. +Algumas solicitações que criam novos dados, como a criação de um novo commit, permitem que você forneça informações do fuso horário ao especificar ou marcas de tempo. Aplicamos as seguintes regras, por ordem de prioridade, para determinar as informações do fuso horário para chamadas de API. -* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) -* [Using the `Time-Zone` header](#using-the-time-zone-header) -* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user) -* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information) +* [Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) +* [Usar o cabeçalho `Time-Zone`](#using-the-time-zone-header) +* [Usar o último fuso horário conhecido para o usuário](#using-the-last-known-timezone-for-the-user) +* [Definir como padrão UTC sem outras informações de fuso horário](#defaulting-to-utc-without-other-timezone-information) -#### Explicitly providing an ISO 8601 timestamp with timezone information +#### Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário -For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). +Para chamadas de API que permitem que uma marca de tempo seja especificada, usamos essa marca de tempo exata. Um exemplo disso é a [API de Commits](/rest/reference/git#commits). -These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. +Essas marcas de tempo se parecem com `2014-02-27T15:05:06+01:00`. Veja também [este exemplo](/rest/reference/git#example-input) para saber como essas marcas de tempo podem ser especificadas. -#### Using the `Time-Zone` header +#### Usar o cabeçalho `Time-Zone` -It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +É possível fornecer um cabeçalho `Time-Zone` que define um fuso horário de acordo com a lista [ de nomes do banco de dados Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```shell $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. +Isso significa que geramos uma marca de tempo no momento em que sua chamada de API é feita no fuso horário que este cabeçalho define. Por exemplo, o [API de Conteúdo](/rest/reference/repos#contents) gera um commit do git para cada adição ou alteração e usa a hora atual como marca de tempo. Este cabeçalho determinará o fuso horário usado para gerar essa marca de tempo atual. -#### Using the last known timezone for the user +#### Usar o último fuso horário conhecido para o usuário -If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website. +Se nenhum cabeçalho `Time-Zone` for especificado e você fizer uma chamada autenticada para a API, nós usaremos o último fuso horário conhecido para o usuário autenticado. O último fuso horário conhecido é atualizado sempre que você navegar no site de {% data variables.product.product_name %}. -#### Defaulting to UTC without other timezone information +#### Definir como padrão UTC sem outras informações de fuso horário -If the steps above don't result in any information, we use UTC as the timezone to create the git commit. +Se as etapas acima não resultarem em nenhuma informação, usaremos UTC como o fuso horário para criar o commit do git. + +[rfc]: http://tools.ietf.org/html/rfc6570 +[uri]: https://github.com/hannesg/uri_template [pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/pt-BR/content/rest/overview/troubleshooting.md b/translations/pt-BR/content/rest/overview/troubleshooting.md index a1cdb2c8d3..f68f11208d 100644 --- a/translations/pt-BR/content/rest/overview/troubleshooting.md +++ b/translations/pt-BR/content/rest/overview/troubleshooting.md @@ -13,52 +13,52 @@ versions: Se você estiver encontrando algumas situações estranhas na API, aqui está uma lista de resoluções de alguns dos problemas que você pode estar enfrentando. -### `404` error for an existing repository +### Erro `404` para um repositório existente Normalmente, enviamos um erro `404` quando seu cliente não está autenticado corretamente. Nesses casos, você pode esperar ver um `403 Forbidden`. No entanto, como não queremos fornecer _nenhuma_ informação sobre repositórios privados, a API retorna um erro `404`. Para solucionar o problema, verifique se [você está efetuando a autenticação corretamente](/guides/getting-started/), se [seu token de acesso do OAuth tem os escopos necessários](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) e se as [restrições de aplicativos de terceiros][oap-guide] não estão bloqueando o acesso. -### Not all results returned +### Nem todos os resultados retornados A maioria das chamadas da API que acessam uma lista de recursos (_por exemplo,_, usuários, issues, _etc._) é compatível com a paginação. Se você está fazendo solicitações e recebendo um conjunto incompleto de resultados, provavelmente você só está vendo a primeira página. Você precisará solicitar as páginas restantes para obter mais resultados. É importante *não* tentar adivinhar o formato da URL de paginação. Nem todas as chamadas de API usam a mesma estrutura. Em vez disso, extraia as informações de paginação do [Cabeçalho do link](/rest#pagination), que é enviado com cada solicitação. {% if currentVersion == "free-pro-team@latest" %} -### Basic authentication errors +### Erros de autenticação básica -On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work. +Em 13 de novembro de 2020 a autenticação de nome de usuário e senha da API REST e da API de Autorizações OAuth tornaram-se obsoletas e já não funcionaram mais. -#### Using `username`/`password` for basic authentication +#### Usar `nome de usuário`/`senha` para autenticação básica -If you're using `username` and `password` for API calls, then they are no longer able to authenticate. Por exemplo: +Se você estiver usando um `nome de usuário` e `senha` para chamadas de API, eles não são conseguirão mais efetuar a autenticação. Por exemplo: ```bash curl -u my_user:my_password https://api.github.com/user/repos ``` -Instead, use a [personal access token](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development: +Em vez disso, use um [token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) ao testar pontos de extremidade ou fazer desenvolvimento local: ```bash curl -H 'Authorization: token my_access_token' https://api.github.com/user/repos ``` -For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header: +Para aplicativos OAuth, você deve usar o [fluxo de aplicativo web](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para gerar um token do OAuth para usar no cabeçalho da chamada da API: ```bash curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos ``` -#### Calls to OAuth Authorizations API +#### Chamadas para API de autorização do OAuth -If you're making [OAuth Authorization API](/enterprise-server/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: +Se você estiver fazendo chamadas de [API de autorização do OAuth](/enterprise-server/rest/reference/oauth-authorizations) para gerenciar as autorizações do seu aplicativo OAuth ou para gerar tokens de acesso de forma similar a este exemplo: ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' ``` -Then you must switch to the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate access tokens. +Você deverá alternar para o fluxo do aplicativo web [](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para gerar tokens de acesso. {% endif %} diff --git a/translations/pt-BR/content/rest/reference/code-scanning.md b/translations/pt-BR/content/rest/reference/code-scanning.md index 4c8232da7e..d7b11664ca 100644 --- a/translations/pt-BR/content/rest/reference/code-scanning.md +++ b/translations/pt-BR/content/rest/reference/code-scanning.md @@ -2,6 +2,7 @@ title: Varredura de código redirect_from: - /v3/code-scanning +product: '{% data reusables.gated-features.code-scanning %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/pt-BR/content/rest/reference/gists.md b/translations/pt-BR/content/rest/reference/gists.md index 61bdce933c..1ff371cc24 100644 --- a/translations/pt-BR/content/rest/reference/gists.md +++ b/translations/pt-BR/content/rest/reference/gists.md @@ -8,43 +8,43 @@ versions: github-ae: '*' --- -### Autenticação +### Authentication -You can read public gists {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}and create them for anonymous users without a token.{% else %} anonymously, but you must be signed into GitHub to create gists.{% endif %} To read or write gists on a user's behalf, you need the gist OAuth scope and a token. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)." +You can read public gists {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}and create them for anonymous users without a token.{% else %} anonymously, but you must be signed into GitHub to create gists.{% endif %} To read or write gists on a user's behalf, you need the gist OAuth scope and a token. For more information, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps)." -### Truncamento +### Truncation -A API de Gist fornece até um megabyte de conteúdo para cada arquivo no gist. Cada arquivo retornado por um gist através da API tem uma chave denominada `truncada`. Se `truncado` for `verdadeiro`, significa que arquivo é muito grande e apenas uma parte do conteúdo foi retornado em `conteúdo`. +The Gist API provides up to one megabyte of content for each file in the gist. Each file returned for a gist through the API has a key called `truncated`. If `truncated` is `true`, the file is too large and only a portion of the contents were returned in `content`. -Se você precisar do conteúdo completo do arquivo, você pode fazer uma solicitação `GET` para a URL especificada por `raw_url`. Tenha em mente que, para arquivos maiores que dez megabytes, você deverá clonar o gist através da URL fornecida por `git_pull_url`. +If you need the full contents of the file, you can make a `GET` request to the URL specified by `raw_url`. Be aware that for files larger than ten megabytes, you'll need to clone the gist via the URL provided by `git_pull_url`. -Além do conteúdo de um arquivo específico ser truncado, toda a lista de arquivos pode ser truncada se o número total exceder 300 arquivos. Se a chave de nível superior `truncado` é `verdadeira`, apenas os primeiros 300 arquivos foram retornados na lista de arquivos. Se você precisar buscar todos os arquivos do gist, você deverá clonar o gist através da URL fornecida por `git_pull_url`. +In addition to a specific file's contents being truncated, the entire files list may be truncated if the total number exceeds 300 files. If the top level `truncated` key is `true`, only the first 300 files have been returned in the files list. If you need to fetch all of the gist's files, you'll need to clone the gist via the URL provided by `git_pull_url`. -### Tipos de mídia personalizados para gists +### Custom media types for gists -Estes são os tipos de mídia compatíveis para buscar conteúdo geral. +These are the supported media types for fetching gist contents. application/vnd.github.VERSION.raw application/vnd.github.VERSION.base64 -Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)". +For more information, see "[Media types](/rest/overview/media-types)." {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Comentários +## Comments -### Tipos de mídia personalizados para comentários do Gist +### Custom media types for Gist comments -Estes são os tipos de mídia compatíveis para comentários de gist. +These are the supported media types for gist comments. application/vnd.github.VERSION.raw application/vnd.github.VERSION.base64 -Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia 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 == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/interactions.md b/translations/pt-BR/content/rest/reference/interactions.md index 39199f965a..294d206538 100644 --- a/translations/pt-BR/content/rest/reference/interactions.md +++ b/translations/pt-BR/content/rest/reference/interactions.md @@ -6,7 +6,7 @@ versions: free-pro-team: '*' --- -Os usuários interagem com repositórios comentando, abrindo problemas e criando pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict interaction with public repositories to a certain type of user. +Os usuários interagem com repositórios comentando, abrindo problemas e criando pull requests. As APIs de interações permitem que as pessoas com acesso de proprietário ou administrador restrinjam temporariamente a interação com repositórios públicos para um determinado tipo de usuário. {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -14,13 +14,13 @@ Os usuários interagem com repositórios comentando, abrindo problemas e criando ## organização -The Organization Interactions API allows organization owners to temporarily restrict which type of user can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users: +A API de Interações da Organização permite que os proprietários da organização restrinjam temporariamente quais tipos de usuário podem comentar, abrir problemas ou criar pull requests nos repositórios públicos da organização. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}: * {% data reusables.interactions.existing-user-limit-definition %} na organização. * {% data reusables.interactions.contributor-user-limit-definition %} na organização. * {% data reusables.interactions.collaborator-user-limit-definition %} na organização. -Setting the interaction limit at the organization level will overwrite any interaction limits that are set for individual repositories owned by the organization. To set different interaction limits for individual repositories owned by the organization, use the [Repository](#repository) interactions endpoints instead. +Definir o limite de interação no nível da organização sobrescreverá quaisquer limites de interação definidos para repositórios individuais pertencentes à organização. Para definir diferentes limites de interação para repositórios individuais pertencentes à organização, use os pontos de extremidade das interações do [Repositório](#repository). {% for operation in currentRestOperations %} {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} @@ -28,13 +28,13 @@ Setting the interaction limit at the organization level will overwrite any inter ## Repositório -The Repository Interactions API allows people with owner or admin access to temporarily restrict which type of user can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users: +A API de Interações do Repositório permite que pessoas com acesso de proprietário ou administrador restrinjam temporariamente qual tipo de usuário pode comentar, abrir problemas ou criar pull requests em um repositório público. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}: * {% data reusables.interactions.existing-user-limit-definition %} in the respository. * {% data reusables.interactions.contributor-user-limit-definition %} in the respository. * {% data reusables.interactions.collaborator-user-limit-definition %} in the respository. -If an interaction limit is enabled for the user or organization that owns the repository, the limit cannot be changed for the individual repository. Instead, use the [User](#user) or [Organization](#organization) interactions endpoints to change the interaction limit. +Se um limite de interação for habilitado para o usuário ou organização proprietária do repositório, o limite não poderá ser alterado para o repositório individual. Em vez disso, use os pontos de extremidade de [Usuário](#user) ou [Organização](#organization) para alterar o limite de interação. {% for operation in currentRestOperations %} {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %} @@ -42,13 +42,13 @@ If an interaction limit is enabled for the user or organization that owns the re ## Usuário -The User Interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users: +A API de Interações do Usuário permite restringir temporariamente que tipo de usuário pode comentar, abrir problemas ou criar pull requests nos seus repositórios públicos. {% data reusables.interactions.interactions-detail %} Veja mais sobre os tipos de usuários de {% data variables.product.product_name %}: -* {% data reusables.interactions.existing-user-limit-definition %} from interacting with your repositories. -* {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories. -* {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories. +* {% data reusables.interactions.existing-user-limit-definition %} de interagir com seus repositórios. +* {% data reusables.interactions.contributor-user-limit-definition %} de interagir com seus repositórios. +* {% data reusables.interactions.collaborator-user-limit-definition %} de interagir com seus repositórios. -Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the [Repository](#repository) interactions endpoints instead. +Definir o limite de interação no nível do usuário sobrescreverá quaisquer limites de interação definidos para repositórios individuais pertencentes ao usuário. Para definir diferentes limites de interação para repositórios individuais pertencentes ao usuário, use os pontos de extremidade das interações do [Repositório](#repository). {% for operation in currentRestOperations %} {% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/orgs.md b/translations/pt-BR/content/rest/reference/orgs.md index bd237b7609..d54652fd33 100644 --- a/translations/pt-BR/content/rest/reference/orgs.md +++ b/translations/pt-BR/content/rest/reference/orgs.md @@ -38,7 +38,7 @@ O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer ## Webhooks -Os webhooks da organização permitem que você receba cargas de HTTP do tipo `POST` sempre que certos eventos ocorrerem dentro da organização. Subscribing to these events makes it possible to build integrations that react to events on {% data variables.product.product_name %}. Para obter mais informações sobre ações que você pode assinar, consulte "[ tipos de evento de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". +Os webhooks da organização permitem que você receba cargas de HTTP do tipo `POST` sempre que certos eventos ocorrerem dentro da organização. Assinar esses eventos viabiliza a construção de integrações que reagem aos eventos em {% data variables.product.product_name %}. Para obter mais informações sobre ações que você pode assinar, consulte "[ tipos de evento de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". ### Escopos & Restrições 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 609107932d..d8bb08c821 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 @@ -107,7 +107,7 @@ _Pesquisar_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permissão em "ações" - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Colaboradores_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Comentários de commit_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -822,7 +828,7 @@ _Equipes_ {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Permission on "secret scanning alerts" +### Permissão em "alertas de varredura de segredo" - [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) @@ -836,6 +842,9 @@ _Equipes_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/pt-BR/content/rest/reference/repos.md b/translations/pt-BR/content/rest/reference/repos.md index 10c1988d33..67a2f1ffa6 100644 --- a/translations/pt-BR/content/rest/reference/repos.md +++ b/translations/pt-BR/content/rest/reference/repos.md @@ -1,5 +1,5 @@ --- -title: Repositórios +title: Repositories allowTitleToDifferFromFilename: true redirect_from: - /v3/repos @@ -19,24 +19,25 @@ versions: {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %} {% endfor %} -## Colaboradores +## Collaborators {% for operation in currentRestOperations %} {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} {% endfor %} -## Comentários +## Comments -### Tipos de mídia personalizados para comentários de commit +### Custom media types for commit comments -Estes são os tipos de mídia compatíveis com os comentários do commit. Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/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 obter mais informações, consulte "[tipos de mídia 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 %} @@ -44,14 +45,14 @@ Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/ ## Commits -A API de Commits do repositório é compatível com a listagem, visualização e comparação de commits em um repositório. +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 %} {% if currentVersion == "free-pro-team@latest" %} -## Comunidade +## Community {% for operation in currentRestOperations %} {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %} @@ -59,54 +60,56 @@ A API de Commits do repositório é compatível com a listagem, visualização e {% endif %} -## Conteúdo +## Contents -Estes pontos de extremidade da API permitem criar, modificar e excluir conteúdo codificado em Base64 em um repositório. Para solicitar o formato sem processar ou HTML interpretado (quando compatível), use os tipos de mídia personalizados para o conteúdo do repositório. +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 mídia personalizados para conteúdo do repositório +### Custom media types for repository contents -Os [LEIAMEs](/rest/reference/repos#get-a-repository-readme), [arquivos](/rest/reference/repos#get-repository-content) e [links simbólicos](/rest/reference/repos#get-repository-content) são compatíveis com os seguintes tipos de mídia 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 -Use o tipo de mídia `.raw` para recuperar o conteúdo do arquivo. +Use the `.raw` media type to retrieve the contents of the file. -Para arquivos de markup, como Markdown ou AsciiDoc, você pode recuperar o HTML interpretado usando o tipo de mídia `.html`. As linguagens de markup são processadas em HTML usando nossa [biblioteca de markup](https://github.com/github/markup) de código aberto. +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 os objetos](/rest/reference/repos#get-repository-content) são compatíveis com o seguinte tipo de mídia personalizado: +[All objects](/rest/reference/repos#get-repository-content) support the following custom media type: application/vnd.github.VERSION.object -Use o parâmetro do tipo de mídia do `objeto` para recuperar o conteúdo em um formato de objeto consistente independentemente do tipo de conteúdo. Por exemplo, em vez de um array de objetos para um diretório, a resposta será um objeto com um atributo de `entrada` contendo o array 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. -Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/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 %} -## Chaves de implantação +## Deploy keys {% data reusables.repositories.deploy-keys %} -Chaves de implantação podem ser configuradas usando os seguintes pontos de extremidades da API ou usando o GitHub. Para saber como configurar as chaves de implantação no GitHub, consulte "[Gerenciar chaves de implantação](/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 %} -## Implantações +## Deployments -As implantações são solicitações para implantar um ref específico (branch, SHA, tag). O GitHub envia um [ evento de `implantação`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) pelo qual os serviços externos podem ouvir e atuar quando novas implantações são criadas. As implantações permitem que os desenvolvedores e as organizações construam ferramentas associadas em torno de implantações sem ter que se preocupar com os detalhes de implementação da entrega de diferentes tipos de aplicativos (p. ex., web, nativo). +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). -Os status de implantação externos permitem marcar implantações com `error`, `failure`, `pending`, `in_progress`, `queued` ou `success` afirmar que os sistemas que estão escutando os eventos [`deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) podem consumir. +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. -Os status de implantação também podem incluir uma `descrição` opcional e `log_url`, que são altamente recomendados porque tornam o status de implantação mais útil. O `log_url` é a URL completa para a saída de implantação e a `descrição` é um resumo de alto nível do que aconteceu com a implantação. +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. -O GitHub envia os eventos de `implantação` e `deployment_status` quando novas implantações de status de implantação são criadas. Esses eventos permitem que as integrações de terceiros recebam resposta para solicitações de implantação e atualizem o status de implantação conforme o progresso é feito. +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. -Abaixo está um diagrama de sequência sobre para como essas interações funcionariam. +Below is a simple sequence diagram for how these interactions would work. ``` +---------+ +--------+ +-----------+ +-------------+ @@ -135,45 +138,49 @@ Abaixo está um diagrama de sequência sobre para como essas interações funcio | | | | ``` -Tenha em mente que o GitHub nunca terá acesso aos seus servidores. Cabe à sua integração de terceiros interagir com os eventos de implantação. Vários sistemas podem ouvir eventos de implantação, e cabe a cada um desses sistemas decidir se serão responsáveis por retirar o código dos seus servidores, criar 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. -Observe que o `escopo do OAuth` [repo_deployment](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a implantações e status de implantações **sem** conceder acesso ao código do repositório, enquanto os escopos `public_repo` e `repo` também concedem permissão para o 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 `public_repo` and `repo` scopes grant permission to code as well. -### Implantações inativas +### Inactive deployments -Ao definir o estado de uma implantação como `sucesso`, todas as implantações de ambiente de não produção e não transitórias no mesmo repositório irão tornar-se `inativas`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. -Você pode informar que um ambiente transitório não existe mais definindo seu `estado` como `inativo`. Definir o `estado` como `inativo` mostra a implantação como `destruída` em {% data variables.product.prodname_dotcom %} e remove o acesso a ela. +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 %} -## Bifurcações +## Forks {% for operation in currentRestOperations %} {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %} {% endfor %} -## Convites +## Invitations -A API de Convites do Repositório permite que usuários ou serviços externos convidem outros usuários para colaborar em um repositório. Os usuários convidados (ou serviços externos em nome dos usuários convidados) podem optar por aceitar ou recusar os convites. +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. -Observe que o [Escopo OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` concede acesso direcionado aos convites **sem** conceder também acesso ao código do repositório. enquanto o escopo `repo` concede permissão ao código e aos convites convites. +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. -### Convidar um usuário para um repositório +### Invite a user to a repository -Use o ponto de extremidade da API para adicionar um colaborador. Para obter mais informações, consulte "[Adicionar um colaborador de repositório](/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 %} {% endfor %} -## Mesclar +## Merging -A API de merge do repositório é compatível com o merge de branches em um repositório. Isso realiza, essencialmente, a mesma coisa que mesclar um branch em outro em um repositório local e, em seguida, fazer push para {% data variables.product.product_name %}. O benefício é que o merge é realizado no lado do servidor e não é necessário um repositório local. Isso o torna mais apropriado para automação e outras ferramentas em que a manutenção de repositórios locais seria pesada 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. -O usuário autenticado será o autor de qualquer merge feito por meio deste ponto de extremidade. +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 %} @@ -181,30 +188,30 @@ O usuário autenticado será o autor de qualquer merge feito por meio deste pont ## Pages -A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. As informações sobre o site e as criações só podem ser acessadas por proprietários autenticados, mesmo que os sites sejam públicos. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/github/working-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, even though the websites are public. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." -Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} com uma chave de `status` na sua resposta, o valor pode ser: -* `null`: O site ainda não foi criado. -* `queued`: A criação foi solicitada, mas ainda não começou. -* `building`:A criaçãoestá em andamento. -* `built`: O site foi criado. -* `errored`: Indica que ocorreu um erro durante a criação. +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. -Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} que devolvem as informações do site do GitHub Pages, as respostas do JSON incluem esses campos: -* `html_url`: A URL absoluta (incluindo o esquema) do site de páginas interpretadas. Por exemplo, `https://username.github.io`. -* `source`: Um objeto que contém o branch de origem e o diretório do site de páginas interpretadas. Isto inclui: - - `branch`: O branch do repositório utilizado para publicar os [arquivos de origem do site](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por exemplo, _principal_ ou _gh-pages_. - - `path`: O diretório do repositório a partir do qual o site é publicado. Será `/` ou `/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](/github/working-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 %} -## Versões +## Releases {% note %} -**Observação:** A API de versões substitui a API de Downloads. Você pode recuperar a contagem de download e a URL de download do navegador a partir dos pontos de extremidades nesta API que retornam versões e liberam ativos. +**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 %} @@ -212,50 +219,68 @@ Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %} {% endfor %} -## Estatísticas +## Statistics -A API de Estatísticas do Repositório permite que você recupere os dados que o {% data variables.product.product_name %} usa para visualizar diferentes tipos de atividade do repositório. +The Repository Statistics API allows you to fetch the data that {% data variables.product.product_name %} uses for visualizing different +types of repository activity. -### Umas palavras sobre o armazenamento em cache +### A word about caching -Computar as estatísticas do repositório é uma operação cara. Por esse motivo, tentamos retornar dados armazenados em cache sempre que possível. Se os dados não forem armazenados em cache nas estatísticas de um repositório, você receberá uma resposta de `202`; um trabalho em segundo plano também é acionado para começar a compilar estas estatísticas. Dê ao trabalho alguns instantes para que seja concluído e, em seguida, envie a solicitação novamente. Se o trabalho foi concluído, essa solicitação receberá uma resposta de `200` com as estatísticas no texto da resposta. +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. -As estatísticas do repositório são armazenadas em cache pelo SHA do branch-padrão do repositório; fazer push para o branch-padrão redefine o armazenamento em cache de estatísticas. +Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache. -### As estatísticas excluem alguns tipos de commits +### Statistics exclude some types of commits -As estatísticas expostas pela API correspondem às estatísticas mostradas pelos [diferentes gráficos de repositórios](/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). -Resumo: -- Todas as estatísticas excluem commits de merge. -- As estatísticas do contribuidor também excluem commits vazios. +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 %} -## Status +## Statuses -A API de status permite que serviços externos marquem commits com status de `erro`, `falha`, `pendente` ou `sucesso`, o que é refletido em pull requests que envolvem esses commits. +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. -Os status também podem incluir uma `descrição` opcional e `target_url`, e é altamente recomendável fornecê-los, pois tornam o status muito mais útil na interface de usuário do 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 exemplo, um uso comum é para serviços de integração contínua para marcar commits como criações que passam ou que falham usando o status. O `target_url` seria a URL completa para a saída da criação, e a `descrição` seria o resumo de alto nível do que aconteceu com a criação. +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. -Os status podem incluir um `contexto` para indicar qual serviço está fornecendo esse status. Por exemplo, você pode fazer com que o seu serviço de integração contínua faça push status com um contexto de `ci`, e uma ferramenta de auditoria de segurança faça push dos status com um contexto de `segurança`. Você pode usar [Obter o status combinado para uma referência específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) para recuperar todo o status de um commit. +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. -Observe que o `escopo do OAuth` [repo:status](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a status **sem** conceder acesso ao código do repositório, enquanto o escopo `repo` concede permissão para o código e para status. +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. -Se você está desenvolvendo um aplicativo GitHub e deseja fornecer informações mais detalhadas sobre um serviço externo, você deverá usar a [API de verificação](/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 %} {% if currentVersion == "free-pro-team@latest" %} -## Tráfego +## Traffic -Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. Para obter mais informações, consulte "Visualizar tráfego para um repositório. " +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 %} @@ -264,41 +289,41 @@ Para repositórios aos quais você tem acesso de push, a API de tráfego fornece ## Webhooks -A API de Webhooks do Repositório permite que os administradores do repositório gerenciem os hooks post-receive de um repositório. Os webhooks podem ser gerenciados usando a API de HTTP do JSON ou a API de [SubHubbub](#PubSubHubbub). +The Repository Webhooks API allows repository admins to manage the post-receive hooks for a repository. Webhooks can be managed using the JSON HTTP API, or the [PubSubHubbub](#PubSubHubbub) API. -Se você deseja configurar um único webhook para receber eventos de todos os repositórios da organização, consulte nossa documentação de API para [Webhooks de organização](/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). {% for operation in currentRestOperations %} {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -### Receber Webhooks +### Receiving Webhooks -Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por 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. -#### Cabeçalhos de webhook +#### Webhook headers -{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para obter informações. +{% 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 -O GitHub também pode servir como um centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos os repositórios. O PSHB é um simples protocolo de publicação/assinatura que permite o registro de servidores para receber atualizações quando um tópico é atualizado. As atualizações são enviadas com uma solicitação HTTP do tipo POST para uma URL de chamada de retorno. As URLs dos tópicos dos pushes de um repositório do GitHub estão neste 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}` -O evento pode ser qualquer evento de webhook disponível. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/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 resposta +#### Response format -O formato padrão é o que [os hooks post-receive existentes devem esperar](/post-receive-hooks/): Um texto JSON enviado como parâmetro `payload` em um POST. Você também pode especificar para receber o texto do JSON sem processar com um cabeçalho `Aceitar` ou uma extensão `.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 -#### URLs de chamada de retorno -As URLs de chamada de retorno podem usar o protocolo `http://`. +#### Callback URLs -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %}You can also `github://` callbacks to specify a GitHub service. +Callback URLs can use the `http://` protocol. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %}You can also `github://` callbacks to specify a GitHub service. {% data reusables.apps.deprecating_github_services_ghe %} {% endif %} @@ -306,12 +331,13 @@ As URLs de chamada de retorno podem usar o protocolo `http://`. http://postbin.org/123 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} - # Send updates to Campfire github://campfire?subdomain=github&room=Commits&token=abc123 + # Send updates to Campfire + github://campfire?subdomain=github&room=Commits&token=abc123 {% endif %} -#### Assinar +#### Subscribing -O ponto de extremidade do GitHub PubSubHubbub é: `{% data variables.product.api_url_code %}/hub`. Uma solicitação bem-sucedida com o curl parece como: +The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like: ``` shell curl -u "user" -i \ @@ -321,13 +347,13 @@ curl -u "user" -i \ -F "hub.callback=http://postbin.org/123" ``` -Solicitações do PubSubHubbub podem ser enviadas várias vezes. Se o hook já existe, ele será modificado de acordo com a solicitação. +PubSubHubbub requests can be sent multiple times. If the hook already exists, it will be modified according to the request. -##### Parâmetros +##### Parameters -| Nome | Tipo | Descrição | -| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `hub.mode` | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`. | -| `hub.topic` | `string` | **Obrigatório**. A URI do repositório do GitHub a ser assinada. O caminho deve estar no formato `/{owner}/{repo}/events/{event}`. | -| `hub.callback` | `string` | A URI para receber as atualizações do tópico. | -| `hub.secret` | `string` | Uma chave secreta compartilhada que gera um HMAC de SHA1 do conteúdo do texto de saída. Você pode verificar se um push veio do GitHub, comparando o texto da solicitação sem processamento com o conteúdo do cabeçalho `X-Hub-Signature`. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. | +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 SHA1 HMAC of the outgoing body content. You can verify a push came from GitHub by comparing the raw request body with the contents of the `X-Hub-Signature` header. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details. diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md index b823f590ca..90e43e509c 100644 --- a/translations/pt-BR/content/rest/reference/search.md +++ b/translations/pt-BR/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: 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**. -Você pode restringir sua pesquisa usando as consultas. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." +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)". ### Resultados da pesquisa de classificação @@ -18,7 +18,7 @@ A menos que outra opção de ordenamento seja fornecida como um parâmetro de co ### Limite de taxa -A API de pesquisa tem um limite de taxa personalizado. 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. Para solicitações não autenticadas, o limite de taxa permite que você faça até 10 solicitações por minuto. +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. {% data reusables.enterprise.rate_limit %} @@ -28,7 +28,7 @@ Veja a [documentação do limite de taxa](/rest/reference/rate-limit) para obter 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. -A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. O formato da consulta de pesquisa é: +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 é: ``` SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N @@ -40,7 +40,7 @@ Por exemplo, se você quisesse pesquisar todos os _repositórios_ de propriedade GitHub Octocat in:readme user:defunkt ``` -**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. Por exemplo: +**Observação:** Certifique-se de usar o codificador HTML preferido do seu idioma para construir suas strings de consulta. Por exemplo: ```javascript // JavaScript const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); diff --git a/translations/pt-BR/content/rest/reference/secret-scanning.md b/translations/pt-BR/content/rest/reference/secret-scanning.md index 01661c31b2..8541eb3698 100644 --- a/translations/pt-BR/content/rest/reference/secret-scanning.md +++ b/translations/pt-BR/content/rest/reference/secret-scanning.md @@ -7,6 +7,6 @@ versions: {% data reusables.secret-scanning.api-beta %} -The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)." +A API de {% data variables.product.prodname_secret_scanning %} permite que você recupere e atualize os alertas de varredura de segredos de um repositório privado. Para obter mais informações sobre a verificação secreta de repositórios privados, consulte "[Proteger o seu repositório](/github/administering-a-repository/securing-your-repository). ". {% include rest_operations_at_current_path %} diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md index c1550a7045..e015aaa86f 100644 --- a/translations/pt-BR/content/rest/reference/teams.md +++ b/translations/pt-BR/content/rest/reference/teams.md @@ -16,7 +16,7 @@ Esta API só está disponível para os integrantes autenticados da [organizaçã ## Discussões -A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe. +A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. Para aprender mais sobre comentários em uma publicação de discussão, consulte [a API de comentários de discussão em equipe](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/users.md b/translations/pt-BR/content/rest/reference/users.md index 45c8ad48ac..4f9e6ebe85 100644 --- a/translations/pt-BR/content/rest/reference/users.md +++ b/translations/pt-BR/content/rest/reference/users.md @@ -8,7 +8,7 @@ versions: github-ae: '*' --- -Muitos dos recursos na API de usuários fornecem um atalho para obter informações sobre o usuário autenticado atualmente. If a request URL does not include a `{username}` parameter then the response will be for the logged in user (and you must pass [authentication information](/rest/overview/resources-in-the-rest-api#authentication) with your request).{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} Additional private information, such as whether a user has two-factor authentication enabled, is included when authenticated through basic auth or OAuth with the `user` scope.{% endif %} +Muitos dos recursos na API de usuários fornecem um atalho para obter informações sobre o usuário autenticado atualmente. Se uma URL de solicitação não incluir um parâmetro `{username}`, a resposta será para o usuário conectado (e você deve passar [informações de autenticação](/rest/overview/resources-in-the-rest-api#authentication) com sua solicitação).{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} Informações privadas adicionais, como se um usuário tem autenticação de dois fatores habilitada, estão incluídas quando a autenticação é efetuada por meio da autenticação básica ou OAuth com o escopo do `usuário` .{% endif %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml index ec1b5ac095..cbd1a81d57 100644 --- a/translations/pt-BR/data/glossaries/external.yml +++ b/translations/pt-BR/data/glossaries/external.yml @@ -35,7 +35,7 @@ - term: bio description: >- - Descrição gerada pelo usuário em um perfil: https://help.github.com/articles/adding-a-bio-to-your-profile/ + A descrição gerada pelo usuário em um perfil: [Adicionando uma biografia ao seu perfil](/articles/adding-a-bio-to-your-profile) - term: ciclo de cobrança description: Intervalo de tempo do seu plano de cobrança. @@ -123,7 +123,7 @@ - term: commit description: >- - Commit, ou "revisão", é uma alteração individual em um arquivo (ou conjunto de arquivos). Quando você faz um commit para salvar seu trabalho, o Git cria um ID exclusivo (também conhecido como "SHA" ou "hash") que mantém um registro das alterações, dos autores e de quando as alterações foram feitas. Em geral, os commits têm uma mensagem que mostra uma breve descrição das alterações. + Commit, ou "revisão", é uma alteração individual em um arquivo (ou conjunto de arquivos). Quando você faz um commit para salvar seu trabalho, o Git cria um ID exclusivo (também conhecido como "SHA" ou "hash") que permite que você mantenha um registro das alterações, dos autores e de quando as alterações foram feitas. Em geral, os commits têm uma mensagem que mostra uma breve descrição das alterações. - term: autor do commit description: Usuário que fez o commit. @@ -156,7 +156,7 @@ - term: contribuições description: >- - Atividades específicas no GitHub que: - Adicionarão um quadrado ao gráfico de contribuição de um usuário: "[O que conta como contribuição](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Adicionarão atividades à linha do tempo de um usuário no perfil: "[Atividade de contribuição](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" + Atividades específicas no GitHub que irão: - Adicionar um quadrado ao gráfico de contribuição de um usuário: "[O que conta como uma contribuição](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Adicionar atividades à linha do tempo de um usuário em seu perfil: "[Atividade de contribuição](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - term: contribuidor description: >- @@ -229,7 +229,7 @@ Branch usado para testar novos recursos ou corrigir problemas que não estejam em produção. Também é conhecido como branch de tópico. - term: bloco de código isolado - description: 'Bloco de código com recuo que você pode criar com markdown em estilo GitHub usando barra inversa tripla \`\`\ antes e depois do bloco de código. Consulte este [example] (https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' + description: 'Um bloco de código recuado que você pode criar com Markdown em estilo GitHub usando barras inversas triplas \`\`\` antes e depois do bloco de código. Veja este [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' - term: fetch description: >- @@ -252,7 +252,7 @@ - term: Gist description: >- - Gist é um arquivo compartilhável que você pode editar, clonar e bifurcar no GitHub. É possível deixar um gist público ou secreto, embora os secretos sempre fiquem disponíveis para qualquer pessoa que tenha a URL. + Um gist é um arquivo compartilhável que você pode editar, clonar e bifurcar no GitHub. Você pode criar um gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} ou secreto, embora os gists secretos estejam disponíveis para {% if currentVersion == "github-ae@latest" %}qualquer membro corporativo{% else %}qualquer pessoa{% endif %} com a URL. - term: Git description: >- @@ -390,7 +390,7 @@ - term: main description: >- - The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. + Branch de desenvolvimento padrão. Sempre que um repositório do Git é criado, um branch "principal" também é criado e passa a ser o branch ativo. Contém o desenvolvimento local na maioria dos casos, embora isso ocorra meramente por convenção e não seja obrigatório. - term: mestre description: >- @@ -436,7 +436,7 @@ - term: notificação description: >- - Atualizações enviadas pela web ou por e-mail, dependendo das suas configurações, que informam sobre as atividades do seu interesse. + Atualizações, entregues pela web ou e-mail dependendo de suas configurações, que dão a você informações sobre as atividades em que você tem interesse. - term: aplicativo OAuth description: >- diff --git a/translations/pt-BR/data/glossaries/internal.yml b/translations/pt-BR/data/glossaries/internal.yml index aa9c2cccb2..5980c780f9 100644 --- a/translations/pt-BR/data/glossaries/internal.yml +++ b/translations/pt-BR/data/glossaries/internal.yml @@ -110,7 +110,7 @@ description: Unidade de processamento central. - term: auxiliar de credenciais - description: Programa que armazena e regula as credenciais do Git. + description: Um programa que armazena e obtém credenciais do Git. - term: creole description: >- @@ -739,7 +739,7 @@ - term: WYSIWYG description: >- - What You See Is What You Get, acrônimo indicativo de que o texto na tela é exatamente igual ao texto exibido após a renderização. + O que você vê é o que você obtém. Uma sigla significa que o texto na tela parece exatamente como será quando ele for processado. - term: XenServer description: Plataforma de virtualização. diff --git a/translations/pt-BR/data/learning-tracks/README.md b/translations/pt-BR/data/learning-tracks/README.md new file mode 100644 index 0000000000..598fdfa116 --- /dev/null +++ b/translations/pt-BR/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Trilhos de aprendizado (também conhecido como caminhos de aprendizado) + +Os trilhos de aprendizado são uma coleção de artigos que ajudam você a dominar um assunto específico. Os caminhos de aprendizado são definidos por produto. \ No newline at end of file diff --git a/translations/pt-BR/data/learning-tracks/actions.yml b/translations/pt-BR/data/learning-tracks/actions.yml index db126f55d5..832b11e287 100644 --- a/translations/pt-BR/data/learning-tracks/actions.yml +++ b/translations/pt-BR/data/learning-tracks/actions.yml @@ -1,7 +1,7 @@ --- getting_started: title: 'Primeiros passos com {% data variables.product.prodname_actions %}' - description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.' + description: 'Descubra as possibilidades de {% data variables.product.prodname_actions %} criando seu primeiro fluxo de trabalho.' guides: - /actions/learn-github-actions/introduction-to-github-actions - /actions/learn-github-actions/finding-and-customizing-actions @@ -9,8 +9,8 @@ getting_started: - /actions/learn-github-actions/managing-complex-workflows - /actions/learn-github-actions/security-hardening-for-github-actions continuous_integration: - title: 'Build and test code' - description: 'You can create custom continuous integration (CI) workflows right in your repository.' + title: 'Criar e testar código' + description: 'É possível criar fluxos de trabalho personalizados de integração contínua (CI) diretamente no seu repositório.' guides: - /actions/guides/about-continuous-integration - /actions/guides/setting-up-continuous-integration-using-workflow-templates @@ -23,16 +23,23 @@ continuous_integration: - /actions/guides/building-and-testing-java-with-gradle - /actions/guides/building-and-testing-java-with-ant continuous_deployment: - title: 'Automate your deployments' - description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' + title: 'Automatize as suas implantações' + description: 'Aprenda a automatizar a publicação de versões para o seu projeto com um fluxo de trabalho personalizado de implantação contínua (CD) em {% data variables.product.prodname_actions %}.' guides: - /actions/guides/about-packaging-with-github-actions - /actions/guides/publishing-nodejs-packages - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Implantar na nuvem' + description: 'Aprenda como usar {% data variables.product.prodname_actions %} para criar um aplicativo e implantá-lo em várias plataformas baseadas na nuvem.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine hosting_your_own_runners: - title: 'Host 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.' guides: - /actions/hosting-your-own-runners/about-self-hosted-runners @@ -44,8 +51,8 @@ hosting_your_own_runners: - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners create_actions: - title: 'Create an action' - description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' + title: 'Crie uma ação' + description: 'Você tem alguma ideia para uma ação nova? Você construiu algo personalizado para seu projeto? Aprenda como criar ações compartilháveis e publicá-las no GitHub Marketplace.' guides: - /actions/creating-actions/about-actions - /actions/creating-actions/creating-a-docker-container-action diff --git a/translations/pt-BR/data/release-notes/2-20/0.yml b/translations/pt-BR/data/release-notes/2-20/0.yml index f3e2ef1aa5..840753ba44 100644 --- a/translations/pt-BR/data/release-notes/2-20/0.yml +++ b/translations/pt-BR/data/release-notes/2-20/0.yml @@ -1,44 +1,43 @@ ---- -date: '11-02-2020' +date: '2020-02-11' sections: features: - - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' - - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' - - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + - 'Em um branch de repositório, os administradores do repositório podem rejeitar qualquer push que contenha um commit de merge, habilitando "Exigir histórico linear" ao usar [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Os administradores de repositório podem conceder a todos os usuários com acesso push a capacidade de fazer push forçado para um branch protegido, habilitando "Permitir pushes forçados" e usando [regras de proteção de branch](https://help. ithub.com/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Os administradores do repositório podem conceder a todos os usuários com acesso push a capacidade de excluir um branch protegido, habilitando "Permitir exclusões" e usando [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Os administradores podem definir um limite "maxobjectsize" nos repositórios, [limitando o tamanho do commits de push](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) para um repositório que não estão em [Git LFS](https://help.github. om/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Os proprietários da organização podem criar um conjunto de etiquetas-padrão ao criar um novo repositório.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' security_fixes: - - Packages have been updated to the latest security versions. + - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' - - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" - - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' - - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" - - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' - - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' - - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' - - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' - - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' - - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' - - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' - - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + - 'Quando um integrante de uma organização tentou visualizar um repositório público nessa organização, um prompt SSO poderia corromper a exibição da página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - 'Ao visualizar o perfil de usuários, os links para as equipes dos usuários poderiam estar corrompidos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}' + - 'Usuários com a função "manter" não conseguiram editar os tópicos do repositório. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - 'Um usuário que não é um administrador em uma organização receberá um erro 500 ao tentar acessar a página de inscrição. {% comment %} https://github. om/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}' + - 'O pop-up de histórico de edição não apareceria nos comentários do gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'Foi possível registrar uma nova conta com um e-mail que já foi registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'Um serviço de armazenamento estava atingindo um limite de descritor de arquivos e deixando o kernel pendurado e outros serviços de log de erros. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'Quando uma referência de link automático fazia parte de uma url, era possível remover o hiperlink. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'Ao adicionar um comentário a um pull request, a seção "Problemas vinculados" da barra lateral poderia desaparecer. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'Ao editar um convite existente de organização para um usuário, é possível que um cabeçalho duplicado apareça na tabela "Equipes". {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'O serviço "resqued" conseguiu parar de registrar eventos quando as filas se tornaram grandes demais. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Certificados autoassinados não são gerados automaticamente ao executar o comando `ghe-config-apply` para cluster e alta disponibilidade. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' changes: - - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' - - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' - - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' - - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' - - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' - - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' - - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + - 'Nenhum logotipo será exibido para um tópico se um não tiver sido carregado. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'Ao ver um problema em um navegador móvel, os metadados do problema serão listados na parte superior da página. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'O domínio de nível superior do Cônsul mudou de ".consul" para ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'O serviço de hookshot não depende mais do ElasticSearch e usa apenas o MySQL como uma loja de banco de dados. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Implementou-se uma distinção visual aprimorada entre problema, projeto e discussão nos cartões de notas do projeto. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'Em uma revisão de pull request, um aviso é exibido se um comentário linha múltipla for truncado. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Os usuários podem ver seus logs de auditoria na aba "Log de segurança" nas suas configurações pessoais. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Entradas duplicadas de webhook no banco de dados podem gerar falha de atualizações de versões anteriores. (atualizada 2020-02-26) + - 'As atualizações e as definições de atualização irão falhar se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer merge de pull requests. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/1.yml b/translations/pt-BR/data/release-notes/2-20/1.yml index 343d6b8786..863011a60f 100644 --- a/translations/pt-BR/data/release-notes/2-20/1.yml +++ b/translations/pt-BR/data/release-notes/2-20/1.yml @@ -1,21 +1,20 @@ ---- -date: '27-02-2020' +date: '2020-02-27' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' bugs: - - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' - - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' - - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + - 'A restauração a partir de backups geraria uma falha com um erro de "Invalid RDB version number". {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Atualizar uma réplica de HA atrasou indefinidamente a espera para o MySQL iniciar. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'Os comentários de revisão de PR com valores inesperados para "position" ou "original_position" geraram falha nas importações. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'As entradas duplicadas de webhook no banco de dados podem gerar falha de atualizações de versões anteriores. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'As atualizações e as definições de atualização irão falhar se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer merge de pull requests. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/10.yml b/translations/pt-BR/data/release-notes/2-20/10.yml index d8ca3f980d..518926744f 100644 --- a/translations/pt-BR/data/release-notes/2-20/10.yml +++ b/translations/pt-BR/data/release-notes/2-20/10.yml @@ -1,21 +1,20 @@ ---- -date: '23-06-2020' +date: '2020-06-23' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' bugs: - - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" - - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + - 'Eventos de registro excessivamente grandes podem gerar instabilidade no encaminhamento do registro quando UDP foi usado como o mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'A suspensão automática de um usuário através de SSO não foi concluída se o atributo de chaves SSH já tinha chaves associadas à conta do usuário. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}' + - 'O hash de permissão do repositório da API REST não indicou acesso para membros de negócios que têm acesso a repositórios internos. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'A visualização de uma descrição do aplicativo GitHub escrita em markdown não foi processada corretamente. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'O log de auditoria não incluiu eventos de alteração de proteção de branch. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - 'Tentar atribuir a revisão de código a um integrante de uma equipe vazia geraria "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}' + - 'A atribuição da revisão do código que usa o algoritmo de balanceamento de carga pode ser atribuída repetidamente ao mesmo integrante da equipe. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/11.yml b/translations/pt-BR/data/release-notes/2-20/11.yml index 8965ed161c..5456f56910 100644 --- a/translations/pt-BR/data/release-notes/2-20/11.yml +++ b/translations/pt-BR/data/release-notes/2-20/11.yml @@ -1,19 +1,18 @@ ---- -date: '09-07-2020' +date: '2020-07-09' sections: security_fixes: - - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + - '**MEDIUM:** foi atualizado para a versão 1.16.1 e dirigiu o CVE-2019-20372. (atualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' bugs: - - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' - - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' - - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + - 'O gráfico de dependências não foi detectado quando implantado em uma configuração de cluster com vários nós de Redis. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certos arquivos de registro não giraram a cada 7 dias. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'A reutilização rápida de portas de origem de webhook resultaram em conexões rejeitadas. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Trabalhos em segundo plano incorretos podem tentar ser executados em instâncias configuradas como réplicas passivas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Os repositórios internos não foram incluídos corretamente nos resultados de pesquisa para as orgs habilitadas com SAML. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/12.yml b/translations/pt-BR/data/release-notes/2-20/12.yml index 55a7c1bcea..a0af2cb8cf 100644 --- a/translations/pt-BR/data/release-notes/2-20/12.yml +++ b/translations/pt-BR/data/release-notes/2-20/12.yml @@ -1,17 +1,16 @@ ---- -date: '21-07-2020' +date: '2020-07-21' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' bugs: - - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + - 'Os gráficos do monitor do console de gerenciamento às vezes não seriam exibidos corretamente em telas maiores. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'Não era possível usar o fluxo de criação do manifesto do aplicativo GitHub em alguns cenários quando uma política de Cookie do SameSite foi aplicada. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' changes: - - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + - 'Melhorias no dimensionamento do HAProxy {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/13.yml b/translations/pt-BR/data/release-notes/2-20/13.yml index 6a3fd499f1..76399853c2 100644 --- a/translations/pt-BR/data/release-notes/2-20/13.yml +++ b/translations/pt-BR/data/release-notes/2-20/13.yml @@ -1,22 +1,21 @@ ---- -date: '11-08-2020' +date: '2020-08-11' sections: security_fixes: - - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + - '**CRÍTICO:** Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Pages e permite que um invasor execute comandos como parte de criação de um site do GitHub Pages. Esse problema deve-se a uma dependência desatualizada e vulnerável usada no processo de criação de páginas. Para explorar essa vulnerabilidade, um invasor precisará de permissão para criar e construir um site do GitHub Pages na instância do GitHub Enterprise Server. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server. Para mitigar essa vulnerabilidade, a Kramdown foi atualizada para abordar o CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**ALTO:** Um invasor pode injetar um argumento malicioso em um subcomando do Git quando executado no GitHub Enterprise Server. Isso pode permitir que o invasor sobrescreva arquivos arbitrários com conteúdo controlado parcialmente pelo usuário e potencialmente execute comandos arbitrários na instância do GitHub Enterprise Server. Para explorar essa vulnerabilidade, um invasor precisaria de permissão para acessar repositórios dentro da instância do GitHub Enterprise Server. No entanto, devido a outras proteções em vigor, não conseguimos identificar uma forma de explorar ativamente esta vulnerabilidade. Esta vulnerabilidade foi relatada por meio do programa GitHub Security Bug Bounty {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' bugs: - - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + - 'Um erro de configuração do Cônsul impediu que algumas tarefas de segundo plano fossem processadas em instâncias autônomas. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'O cálculo de alocação de memória de serviço poderia determinar uma alocação de memória incorreta ou ilimitada para um serviço resultando em desempenho de sistema pobre. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'A plataforma de virtualização para sistemas oVirt KVM não foi detectada corretamente, gerando problemas durante as atualizações. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - 'A mensagem de erro para autenticação inválida com uma senha via linha de comando Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}' + - 'O GitHub Connect estava usando um ponto obsoleto da API do GitHub.com. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Os problemas não puderam ser classificados por *Atualizações recentes* nos repositórios migrados para uma nova instância. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/github/pull/149330 {% endcomment %}' + - 'A página 404 continha links de contato e links status do GitHub.com na nota de rodapé. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/14.yml b/translations/pt-BR/data/release-notes/2-20/14.yml index 9278f5df95..976753b25d 100644 --- a/translations/pt-BR/data/release-notes/2-20/14.yml +++ b/translations/pt-BR/data/release-notes/2-20/14.yml @@ -1,13 +1,12 @@ ---- -date: '12-08-2020' +date: '2020-08-12' sections: bugs: - - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + - 'Resolveu um problema que poderia gerar alto uso da CPU ao gerar modelos de configuração do sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Alterações recentes nas alocações de memória podem gerar uma degradação no desempenho do sistema {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/16.yml b/translations/pt-BR/data/release-notes/2-20/16.yml index 3e39a00d39..deee6c4ab3 100644 --- a/translations/pt-BR/data/release-notes/2-20/16.yml +++ b/translations/pt-BR/data/release-notes/2-20/16.yml @@ -1,13 +1,12 @@ ---- -date: '08-09-2020' +date: '2020-09-08' sections: bugs: - - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + - 'Uma verificação de saúde do serviço causou o crescimento da sessão, o que gerou um esgotamento do sistema de arquivos. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - 'A atualização que usa um hotpatch pode falhar com um erro: `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/17.yml b/translations/pt-BR/data/release-notes/2-20/17.yml index c3a1844547..a2ef290194 100644 --- a/translations/pt-BR/data/release-notes/2-20/17.yml +++ b/translations/pt-BR/data/release-notes/2-20/17.yml @@ -1,13 +1,12 @@ ---- -date: '23-09-2020' +date: '2020-09-23' sections: security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + - '**MÉDIO**: ImageMagick foi atualizado para o endereço [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/18.yml b/translations/pt-BR/data/release-notes/2-20/18.yml index a49ccb6fb3..374207ae75 100644 --- a/translations/pt-BR/data/release-notes/2-20/18.yml +++ b/translations/pt-BR/data/release-notes/2-20/18.yml @@ -1,26 +1,25 @@ ---- -date: '09-10-2020' +date: '2020-10-09' sections: security_fixes: - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - 'Um usuário cujo nome de usuário de diretório de LDAP padronizado em um login da conta GHES existente pode efetuar a autenticação na conta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + - 'O menu suspenso formato do ID do nome no Console de Gerenciamento seria redefinido para "não especificado" depois de configurá-lo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Salvar as configurações por meio do [console de gerenciamento](/admin/configuration/accessing-the-management-console) acrescentaria uma nova linha aos arquivos [certificado TLS/SSL e chave](/admin/configuration/configuring-tls) que acionou o recarregamento desnecessário de alguns serviços. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Os logs do sistema para o gráfico de dependência não estavam girando, permitindo um crescimento no armazenamento ilimitado. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Os links para as Consultorias de Segurança GitHub usariam uma URL com o nome de host da instância do GitHub Enterprise Server em vez do GitHub.com, direcionando o usuário para uma URL inexistente. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'Ao importar um repositório com "ghe-migrator" poderá gerar uma exceção inesperada quando os dados inconsistentes estão presentes. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Ao usar "ghe-migrator" para importar solicitações de revisão de PR, os registros associados com usuários excluídos resultariam em registros estranhos do banco de dados. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'Ao importar usuários com "ghe-migrator", ocorreria o erro de "E-mail é inválido" se o endereço de e-mail gerado pelo sistema tivesse mais de 100 caracteres. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Registrar a atividade do webhook poderia usar uma grande quantidade de espaço no disco e fazer com que o disco raiz ficasse cheio. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' changes: - - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + - 'O suporte é adicionado ao tipo de instância do AWS EC2 `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'Os manifestos do aplicativo GitHub agora incluem o campo "request_oauth_on_install". {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/19.yml b/translations/pt-BR/data/release-notes/2-20/19.yml index 6fab675bea..401e533cae 100644 --- a/translations/pt-BR/data/release-notes/2-20/19.yml +++ b/translations/pt-BR/data/release-notes/2-20/19.yml @@ -1,14 +1,13 @@ ---- -date: '20-10-2020' +date: '2020-10-20' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' bugs: - - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + - 'A mensagem da conta corporativa "Confirmar requisito de dois fatores" estava incorreta. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/2.yml b/translations/pt-BR/data/release-notes/2-20/2.yml index 32b64d7d47..b41cb1a5ae 100644 --- a/translations/pt-BR/data/release-notes/2-20/2.yml +++ b/translations/pt-BR/data/release-notes/2-20/2.yml @@ -1,28 +1,27 @@ ---- -date: '10-03-2020' +date: '2020-03-10' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' bugs: - - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' - - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' - - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' - - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' - - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' - - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' - - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' - - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' - - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + - 'Em alguns casos, as entradas de log encaminhadas, principalmente para audit.log estavam truncadas. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'O utilitário "ghe-license-check" da linha de comando retornou um erro "Arquivo de licença inválido" para algumas licenças válidas, gerando a falha de alterações de configuração. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Os logs de exceção de Alambic não foram encaminhados pelo Syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'O [evento "org_block"](https://developer.github.com/v3/activity/events/types/#orgblockevent) não está disponível, mas estava aparecendo nos aplicativos GitHub no GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'As respostas às consultas do GraphQL às vezes retornaram identificadores de nó não comparados para objetos `ProtectedBranch`. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'A credencial do aplicativo GitHub usada pelo GitHub Connect falhou ao atualizar imediatamente após a expiração. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Deixar um comentário em resposta a um comentário de pull request criou, de forma intermitente, uma revisão de pull request pendente. {% comment %} https://github.com/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Ao usar o ghe-migrator ou exportar do GitHub.com, uma exportação falha silenciosamente na exportação de anexos que não são imagens. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'O hook de pre-receive retornou 500 erros na interface de usuário da web quando foram encontrados caracteres UTF-8. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' changes: - - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + - 'O utilitário da linha de comando `ghe-license-usage ` incliu uma opção `--unencrypted` nova para proporcionar visibilidade no arquivo de uso da licença exportado. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'As atualizações e as definições de atualização irão falhar se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer merge de pull requests. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/20.yml b/translations/pt-BR/data/release-notes/2-20/20.yml index e07b39c737..01122c4f75 100644 --- a/translations/pt-BR/data/release-notes/2-20/20.yml +++ b/translations/pt-BR/data/release-notes/2-20/20.yml @@ -1,16 +1,15 @@ ---- -date: '03-11-2020' +date: '2020-11-03' sections: security_fixes: - - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' + - '**MÉDIO:** Alto uso de CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN resultando em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - '**BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' bugs: - - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + - 'Os usuários suspensos foram incluídos na lista de usuários sugeridos, ocultando potencialmente usuários não suspensos. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/21.yml b/translations/pt-BR/data/release-notes/2-20/21.yml index 3efb239e52..7fdd9bf91c 100644 --- a/translations/pt-BR/data/release-notes/2-20/21.yml +++ b/translations/pt-BR/data/release-notes/2-20/21.yml @@ -1,15 +1,14 @@ ---- -date: '17-11-2020' +date: '2020-11-17' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/22.yml b/translations/pt-BR/data/release-notes/2-20/22.yml index 3042cc087d..e11a740e44 100644 --- a/translations/pt-BR/data/release-notes/2-20/22.yml +++ b/translations/pt-BR/data/release-notes/2-20/22.yml @@ -1,19 +1,18 @@ ---- -date: '03-12-2020' +date: '2020-12-03' sections: bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'O serviço de autorização foi detectado como não saudável devido a uma condição de raça no bootstrap que gerou a reinicialização do serviço. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'Um comportamento subjacente fez com que um serviço se tornasse indisponível durante o processo de atualização do hotpatch {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'Um subconjunto de registros de encaminhamento de certificados SSL não foi aplicado corretamente. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Notificações de e-mail enviadas aos usuários suspensos quando foram removidos de uma equipe ou de uma organização. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'A forma como os certificados SSH foram aplicados entre organizações e empresas foi inconsistente. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'Quando uma conta teve o limite de taxa limitado devido ao uso de senhas incorretas, ela pôde ser bloqueada por até 24 horas. {% comment %} https://github. om/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'A sincronização de pull request em repositórios com muitas referências pode fazer com que as filas de trabalhador sejam atrasadas. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'Ao efetuar o login após tentar visitar uma página específica, as pessoas eram enviadas para a página inicial em vez de serem enviadas para o seu destino pretendido. {% comment %} https://github. O/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/23.yml b/translations/pt-BR/data/release-notes/2-20/23.yml index eba26c163e..102d790d96 100644 --- a/translations/pt-BR/data/release-notes/2-20/23.yml +++ b/translations/pt-BR/data/release-notes/2-20/23.yml @@ -1,13 +1,12 @@ ---- -date: '17-12-2020' +date: '2020-12-17' sections: security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/3.yml b/translations/pt-BR/data/release-notes/2-20/3.yml index 152f8862a0..ac451b6545 100644 --- a/translations/pt-BR/data/release-notes/2-20/3.yml +++ b/translations/pt-BR/data/release-notes/2-20/3.yml @@ -1,15 +1,14 @@ ---- -date: '12-03-2020' +date: '2020-03-12' sections: bugs: - - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + - 'As atualizações e as atualizações de configurações poderiam falhar se as configurações em segundo plano do trabalhador tivessem sido personalizadas. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer merge de pull requests. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/4.yml b/translations/pt-BR/data/release-notes/2-20/4.yml index a2a4dddbad..571f3d8b57 100644 --- a/translations/pt-BR/data/release-notes/2-20/4.yml +++ b/translations/pt-BR/data/release-notes/2-20/4.yml @@ -1,18 +1,17 @@ ---- -date: '25-03-2020' +date: '2020-03-25' sections: bugs: - - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' - - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' - - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + - 'As solicitações de autenticação do SAML e Metadados não foram estritamente codificadas, o que fez com que alguns provedores de identidade não processem corretamente as solicitações de autenticação iniciadas pelo provedor de serviços. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - 'As exportações do `ghe-migrator` não continham usuários de marco que poderiam interromper as operações de importação. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'Ao fazer push em um Gist, uma exceção pode ser acionada durante o hook de post-receive. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` pode falhar ao tentar exibir repositórios que não foram totalmente replicados. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer merge de pull requests. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/5.yml b/translations/pt-BR/data/release-notes/2-20/5.yml index d7fa4e230c..577dea2f15 100644 --- a/translations/pt-BR/data/release-notes/2-20/5.yml +++ b/translations/pt-BR/data/release-notes/2-20/5.yml @@ -1,20 +1,19 @@ ---- -date: '07-04-2020' +date: '2020-04-07' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' bugs: - - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' - - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' - - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + - 'Uma opção máxima de tamanho de objeto Git de 100 Mb não pôde ser selecionada para um repositório, quando a conta corporativa global definiu uma opção de tamanho de objeto do Git diferente de 100 Mb. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Os resultados da API de problemas e de pull requests podem ter comportamento inconsistente ao ordenar pelo campo `updated_at`. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'O campo `package` das vulnerabilidades de segurança não pôde ser consultado por meio da API do GraphQL. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'A alteração um repositório de *público* para *interno* exibiu uma mensagem de cobrança irrelevante. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Ao fazer a atualização de versões anteriores, os trabalhadores de segundo plano podem gerar, o que impede funcionalidades essenciais como fazer merge de pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/6.yml b/translations/pt-BR/data/release-notes/2-20/6.yml index e51046e01c..c0350f9aab 100644 --- a/translations/pt-BR/data/release-notes/2-20/6.yml +++ b/translations/pt-BR/data/release-notes/2-20/6.yml @@ -1,27 +1,26 @@ ---- -date: '23-04-2020' +date: '2020-04-23' sections: security_fixes: - - '**HIGH**: OpenSSL has been updated to address [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' - - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' - - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + - '**ALTO**: O OpenSSL foi atualizado para o endereço [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' + - '**ALTO**: O Git foi atualizado para o endereço [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) e [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). Novas restrições impedem que repositórios maliciosos sejam carregados para a instância do servidor, protegendo clientes que ainda não foram corrigidos. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**BAIXO**: ImageMagick foi atualizado para o endereço [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' bugs: - - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" - - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + - 'O usuário do git não tinha permissões para invocar os processos necessários para converter repositórios existentes usando Subversion, do formato da v4 ao LRS da v3. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'Uma incompatibilidade nas configurações do MySQL pode fazer com que os backups falhem em grandes instalações. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'Ao atualizar de versões anteriores, trabalhadores em segundo plano às vezes não seriam gerados, o que impediu as funcionalidades essenciais como mesclar pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - 'Quando uma licença do GitHub Enterprise Server continha caracteres diferentes dos da ASCII, as solicitações do tipo "GET" para o ponto de extremidade `/setup/api/settings` da API do console de gerenciamento resultaria em um erro de servidor interno. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}' + - 'O console de recuperação solicitaria uma senha de raiz, mesmo que a conta raiz tenha sido bloqueada. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'Um arquivo de CODEOWNERS com uma marca de ordem inicial UTF-8 fez com que todas as regras de todos os códigos fossem ignoradas. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' changes: - - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}" + - 'Quando o trabalho do cron do orchestrator-cliente falhou, vários e-mails foram enviados para a conta raiz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - 'Quando um provedor de identidade externo controlou o status de administrador do site do usuário, os usuários não puderem ser rebaixados por meio do utilitário da linha de comando. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/7.yml b/translations/pt-BR/data/release-notes/2-20/7.yml index eb697aace6..730ffbdac2 100644 --- a/translations/pt-BR/data/release-notes/2-20/7.yml +++ b/translations/pt-BR/data/release-notes/2-20/7.yml @@ -1,21 +1,20 @@ ---- -date: '05-05-2020' +date: '2020-05-05' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' bugs: - - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' - - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' - - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' - - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' - - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + - '`ghe-repl-start` e `ghe-repl-status` exibiram erros de sintaxe. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'Se um repositório tiver a configuração "excluir branches de cabeçalhos automaticamente" habilitada, o branch do cabeçalho não foi excluído automaticamente quando um pull request foi mesclado pela instalação do aplicativo GitHub. {% comment %} https://github. O/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'Quando um integrante da organização foi restabelecido, a carga do webhook relatou o usuário `fantasma` como o remetente e não como usuário real que executa a restauração. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'Se um repositório tiver a configuração "excluir branches de cabeçalhos automaticamente" habilitada, o branch do cabeçalho não foi excluído automaticamente quando o repositório do cabeçalho era diferente do repositório de base. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'A coleção de lixo de arquivos temporários pode gerar um erro de validação de licença. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'Em algumas situações, inclusive quando um repositório é criado pela primeira vez, o hook de pre-receive seria executado sem um valor preenchido para a variável de ambiente GITHUB_REPO_PUBLIC. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/8.yml b/translations/pt-BR/data/release-notes/2-20/8.yml index 65c54e653e..db80bec829 100644 --- a/translations/pt-BR/data/release-notes/2-20/8.yml +++ b/translations/pt-BR/data/release-notes/2-20/8.yml @@ -1,20 +1,19 @@ ---- -date: '19-05-2020' +date: '2020-05-19' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' bugs: - - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' - - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' - - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' - - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + - 'Depois que o arquivo de licença foi atualizado, os serviços não foram recarregados adequadamente, o que gerou perda de funcionalidades. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'As solicitações da API interna que atualizam as informações do Gráfico de Dependência poderiam falhar se o texto da resposta fosse muito grande. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'O argumento de `afiliações` para algumas conexões do repositório do GraphQL não foi respeitado. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'A suspensão automática de um usuário através do SSO não foi concluída, caso o atributo de e-mail do SAML tenha um revestimento diferente do do e-mail do usuário do GitHub. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restaurar a associação de um usuário a uma organização não instrumentou o ator em cargas de webhook e log de auditoria. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/9.yml b/translations/pt-BR/data/release-notes/2-20/9.yml index faacf79cb1..e1f7da7cbf 100644 --- a/translations/pt-BR/data/release-notes/2-20/9.yml +++ b/translations/pt-BR/data/release-notes/2-20/9.yml @@ -1,17 +1,16 @@ ---- -date: '02-06-2020' +date: '2020-06-02' sections: security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + - '**ALTO:** Uma vulnerabilidade de controle de acesso imprópria foi identificada na API do GitHub Enterprise Server que permitiu que um integrante da organização aumentasse as permissões e recebesse acesso a repositórios não autorizados dentro de uma organização. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à versão 2.21. Emitimos [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) em resposta a este problema. A vulnerabilidade foi relatada por meio do [programa Bug Bounty do GitHub](https://bounty. ithub.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' bugs: - - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + - 'As instâncias do GitHub Enterprise Server voltadas para a Internet podem ser indexadas pelos mecanismos de busca. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'O gráfico de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/0.yml b/translations/pt-BR/data/release-notes/2-21/0.yml index f3552d808f..42f8fd9df2 100644 --- a/translations/pt-BR/data/release-notes/2-21/0.yml +++ b/translations/pt-BR/data/release-notes/2-21/0.yml @@ -1,26 +1,25 @@ ---- -date: '09-06-2020' +date: '2020-06-09' sections: features: - - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' - - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' - - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' - - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' - - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Os usuários podem [gerenciar notificações](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) em problemas, pull requests e outros assuntos ao navegar a partir de uma notificação na web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Usuários podem [converter um pull request novamente para uma "Rascunho"](https://github.blog/changelog/2020-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Sugestões de linha múltipla](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-disponibiliy/) permitem que um usuário sugira uma mudança específica em várias linhas de código ao analisar um pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Os usuários com acesso de gravação em um repositório podem [ocultar um comentário em um problema ou pull request como "Duplicado" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'Quando [criar um repositório a partir de um modelo](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) um usuário pode optar por incluir todos os branches, em vez de apenas o branch padrão. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Os cartões de projeto incluem uma seção de pull requests vinculados](https://github. log/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) para que um usuário possa ver qual trabalho de desenvolvimento está relacionado ao problema diretamente no quadro de projeto. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'Há um novo conjunto de [pontos extremidade para "Excluir reações"](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) na API de Reações. Os pontos de extremidade "Excluir reações" existentes serão suspensos no início de 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'Há um novo conjunto de [pontos de extremidade da API de equipes](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) que permitirá que o GitHub dimensione e apoie a API de equipes no longo prazo. Os pontos de extremidade da API serão suspensos no início de 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' security_fixes: - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' bugs: - - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'If a user with push access minimized another user''s comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}' - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Long filenames could cause overflow issues when showing the ''Changed since last view'' label or the ''Show rich'' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}' - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' @@ -63,10 +62,10 @@ sections: - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/1.yml b/translations/pt-BR/data/release-notes/2-21/1.yml index f70397b28a..09c1fed908 100644 --- a/translations/pt-BR/data/release-notes/2-21/1.yml +++ b/translations/pt-BR/data/release-notes/2-21/1.yml @@ -1,20 +1,19 @@ ---- -date: '23-06-2020' +date: '2020-06-23' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' bugs: - - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + - 'Eventos de registro excessivamente grandes podem gerar instabilidade no encaminhamento do registro quando UDP foi usado como o mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'O serviço de comunicação interno usado para acessar o MySQL pode ser reiniciado com mais frequência do que o necessário, incluindo parte do processo de atualização, que pode fazer com que a atualização falhe parcialmente. Reduzimos a taxa de reinicialização e tornamos o código mais robusto. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - 'A suspensão automática de um usuário através de SSO não foi concluída se o atributo de chaves SSH já tinha chaves associadas à conta do usuário. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}' + - 'O hash de permissão do repositório da API REST não indicou acesso para membros de negócios que têm acesso a repositórios internos. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'A política da conta corporativa "Exclusão de problema do repositório" não refletiu a configuração salva no momento. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'O log de auditoria não incluiu eventos de alteração de proteção de branch. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/10.yml b/translations/pt-BR/data/release-notes/2-21/10.yml index a8408ed42b..95d45c5286 100644 --- a/translations/pt-BR/data/release-notes/2-21/10.yml +++ b/translations/pt-BR/data/release-notes/2-21/10.yml @@ -1,15 +1,14 @@ ---- -date: '20-10-2020' +date: '2020-10-20' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' bugs: - - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + - 'A mensagem da conta corporativa "Confirmar requisito de dois fatores" estava incorreta. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/11.yml b/translations/pt-BR/data/release-notes/2-21/11.yml index 88d9575ebc..10708e361a 100644 --- a/translations/pt-BR/data/release-notes/2-21/11.yml +++ b/translations/pt-BR/data/release-notes/2-21/11.yml @@ -1,18 +1,17 @@ ---- -date: '03-11-2020' +date: '2020-11-03' sections: security_fixes: - - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' + - '**MÉDIO:** Alto uso de CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN resultando em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - '**BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' bugs: - - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + - 'Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'Um método métrico de coleta em segundo plano para aumentar a utilização da CPU. (atualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP da fonte real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/12.yml b/translations/pt-BR/data/release-notes/2-21/12.yml index d27dfc69ec..b394db5e4e 100644 --- a/translations/pt-BR/data/release-notes/2-21/12.yml +++ b/translations/pt-BR/data/release-notes/2-21/12.yml @@ -1,16 +1,15 @@ ---- -date: '17-11-2020' +date: '2020-11-17' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + - 'Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 em vez do endereço IP da fonte real. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/13.yml b/translations/pt-BR/data/release-notes/2-21/13.yml index cbfb87c249..8d5fc176e7 100644 --- a/translations/pt-BR/data/release-notes/2-21/13.yml +++ b/translations/pt-BR/data/release-notes/2-21/13.yml @@ -1,19 +1,18 @@ ---- -date: '03-12-2020' +date: '2020-12-03' sections: bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'O serviço de autorização foi detectado como não saudável devido a uma condição de raça no bootstrap que gerou a reinicialização do serviço. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'Um comportamento subjacente fez com que um serviço se tornasse indisponível durante o processo de atualização do hotpatch {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'Um subconjunto de registros de encaminhamento de certificados SSL não foi aplicado corretamente. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Notificações de e-mail enviadas aos usuários suspensos quando foram removidos de uma equipe ou de uma organização. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'A forma como os certificados SSH foram aplicados entre organizações e empresas foi inconsistente. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'Quando uma conta teve o limite de taxa limitado devido ao uso de senhas incorretas, ela pôde ser bloqueada por até 24 horas. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'A sincronização de pull request em repositórios com muitas referências pode fazer com que as filas de trabalhador sejam atrasadas. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'Ao efetuar o login após tentar visitar uma página específica, as pessoas eram enviadas para a página inicial em vez de serem enviadas para o seu destino pretendido. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/14.yml b/translations/pt-BR/data/release-notes/2-21/14.yml index 9bd0fa2e0d..937f171c22 100644 --- a/translations/pt-BR/data/release-notes/2-21/14.yml +++ b/translations/pt-BR/data/release-notes/2-21/14.yml @@ -1,13 +1,12 @@ ---- -date: '17-12-2020' +date: '2020-12-17' sections: security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/2.yml b/translations/pt-BR/data/release-notes/2-21/2.yml index 887f56c697..da587a3cfe 100644 --- a/translations/pt-BR/data/release-notes/2-21/2.yml +++ b/translations/pt-BR/data/release-notes/2-21/2.yml @@ -1,20 +1,19 @@ ---- -date: '09-07-2020' +date: '2020-07-09' sections: security_fixes: - - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + - '**MEDIUM:** foi atualizado para a versão 1.16.1 e dirigiu o CVE-2019-20372. (atualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' bugs: - - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' - - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + - 'Certos arquivos de registro não giraram a cada 7 dias. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'A reutilização rápida de portas de origem de webhook resultou em conexões rejeitadas. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Os trabalhos em segundo plano incorretos podem tentar ser executados em instâncias configuradas como réplicas passivas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'A VPN entre nós pode tornar-se instável, fazendo com que erros sejam registrados e espaço livre no volume raiz seja esgotado. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Os repositórios internos não foram incluídos corretamente nos resultados de pesquisa para as orgs habilitadas com SAML. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/3.yml b/translations/pt-BR/data/release-notes/2-21/3.yml index 86d4d282fb..a0ef24b138 100644 --- a/translations/pt-BR/data/release-notes/2-21/3.yml +++ b/translations/pt-BR/data/release-notes/2-21/3.yml @@ -1,17 +1,16 @@ ---- -date: '21-07-2020' +date: '2020-07-21' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' bugs: - - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + - 'Os gráficos do monitor do console de gerenciamento às vezes não seriam exibidos corretamente em telas maiores. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'Não era possível usar o fluxo de criação do manifesto do aplicativo GitHub em alguns cenários quando uma política de Cookie do SameSite foi aplicada. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - 'Em algumas circunstâncias, o acesso à página de "Explorar" geraria um erro no aplicativo. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/4.yml b/translations/pt-BR/data/release-notes/2-21/4.yml index 0d262d293d..998c3fd246 100644 --- a/translations/pt-BR/data/release-notes/2-21/4.yml +++ b/translations/pt-BR/data/release-notes/2-21/4.yml @@ -1,16 +1,15 @@ ---- -date: '11-08-2020' +date: '2020-08-11' sections: security_fixes: - - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + - '**CRÍTICO:** Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Pages e permite que um invasor execute comandos como parte de criação de um site do GitHub Pages. Esse problema deve-se a uma dependência desatualizada e vulnerável usada no processo de criação de páginas. Para explorar essa vulnerabilidade, um invasor precisará de permissão para criar e construir um site do GitHub Pages na instância do GitHub Enterprise Server. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server. Para mitigar essa vulnerabilidade, a Kramdown foi atualizada para abordar o CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**ALTO:** Alto: Um invasor pode injetar um argumento malicioso em um subcomando do Git quando executado no GitHub Enterprise Server. Isso pode permitir que o invasor sobrescreva arquivos arbitrários com conteúdo controlado parcialmente pelo usuário e potencialmente execute comandos arbitrários na instância do GHES. Para explorar essa vulnerabilidade, um invasor precisaria de permissão para acessar repositórios dentro da instância do GitHub Enterprise Server. No entanto, devido a outras proteções em vigor, não conseguimos identificar uma forma de explorar ativamente esta vulnerabilidade. Esta vulnerabilidade foi relatada por meio do programa GitHub Security Bug Bounty {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' bugs: - - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Um erro de configuração do Cônsul impediu que algumas tarefas de segundo plano fossem processadas em instâncias autônomas. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'O cálculo de alocação de memória de serviço poderia determinar uma alocação de memória incorreta ou ilimitada para um serviço resultando em desempenho de sistema pobre. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'A plataforma de virtualização para sistemas oVirt KVM não foi detectada corretamente, gerando problemas durante as atualizações. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - 'A mensagem de erro para autenticação inválida com uma senha via linha de comando do Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}' + - 'Criar um problema em um repositório de usuário que usa o recurso de modelo do problema pode falhar com um erro de servidor interno. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' @@ -19,9 +18,9 @@ sections: - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/5.yml b/translations/pt-BR/data/release-notes/2-21/5.yml index 89f7156e55..57da462c18 100644 --- a/translations/pt-BR/data/release-notes/2-21/5.yml +++ b/translations/pt-BR/data/release-notes/2-21/5.yml @@ -1,15 +1,14 @@ ---- -date: '12-08-2020' +date: '2020-08-12' sections: bugs: - - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + - 'Resolveu um problema que poderia gerar alto uso da CPU ao gerar modelos de configuração do sistema. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Alterações recentes nas alocações de memória podem gerar uma degradação no desempenho do sistema {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Problemas temporários de conectividade durante a execução de migrações de banco de dados podem gerar perda de dados. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/7.yml b/translations/pt-BR/data/release-notes/2-21/7.yml index 629d651529..5ca05349fe 100644 --- a/translations/pt-BR/data/release-notes/2-21/7.yml +++ b/translations/pt-BR/data/release-notes/2-21/7.yml @@ -1,14 +1,13 @@ ---- -date: '08-09-2020' +date: '2020-09-08' sections: bugs: - - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + - 'Uma verificação de saúde do serviço causou o crescimento da sessão, o que gerou um esgotamento do sistema de arquivos. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - 'A atualização que usa um hotpatch pode falhar com um erro: `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/8.yml b/translations/pt-BR/data/release-notes/2-21/8.yml index d09450096e..bf155ba240 100644 --- a/translations/pt-BR/data/release-notes/2-21/8.yml +++ b/translations/pt-BR/data/release-notes/2-21/8.yml @@ -1,16 +1,15 @@ ---- -date: '23-09-2020' +date: '2020-09-23' sections: security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + - '**MÉDIO**: ImageMagick foi atualizado para o endereço [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' bugs: - - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + - 'Os administradores não conseguiram ver webhooks de repositório entregues e, ao invés disso, viram "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/9.yml b/translations/pt-BR/data/release-notes/2-21/9.yml index 1792704db3..e459d81edd 100644 --- a/translations/pt-BR/data/release-notes/2-21/9.yml +++ b/translations/pt-BR/data/release-notes/2-21/9.yml @@ -1,29 +1,28 @@ ---- -date: '09-10-2020' +date: '2020-10-09' sections: security_fixes: - - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - 'Um usuário cujo nome de usuário de diretório de **LDAP** padronizado em um login da conta GHES existente pode efetuar a autenticação na conta existente. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' - - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + - 'O menu suspenso de formato do ID do nome no Console de Gerenciamento seria redefinido para "não especificado" depois de configurá-lo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Salvar as configurações por meio do [console de gerenciamento](/admin/configuration/accessing-the-management-console) acrescentaria uma nova linha aos arquivos [certificado TLS/SSL e chave](/admin/configuration/configuring-tls) que acionou o recarregamento desnecessário de alguns serviços. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Os logs do sistema para o gráfico de dependência não estavam girando, permitindo um crescimento no armazenamento ilimitado. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'A atualização poderia falhar se a configuração de substituição dos trabalhadores resgatados estiver em uso. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'Ao importar um repositório com "ghe-migrator" poderá gerar uma exceção inesperada quando os dados inconsistentes estão presentes. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Os links para as Consultorias de Segurança GitHub usariam uma URL com o nome de host da instância do GitHub Enterprise Server em vez do GitHub.com, direcionando o usuário para uma URL inexistente. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'A página de configurações de segurança da conta corporativa mostrou um link para "Visualizar as configurações atuais das organizações" para a configuração da "Autenticação de dois fatores" quando o modo de autenticação em uso não é compatível com autenticação de dois fatores. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'Ao usar "ghe-migrator" para importar solicitações de revisão de PR, os registros associados com usuários excluídos resultariam em registros estranhos do banco de dados. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'Ao importar usuários com "ghe-migrator", ocorreria o erro de "E-mail é inválido" se o endereço de e-mail gerado pelo sistema tivesse mais de 100 caracteres. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Registrar a atividade do webhook poderia usar uma grande quantidade de espaço no disco e fazer com que o disco raiz ficasse cheio. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' changes: - - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + - 'O suporte é adicionado ao tipo de instância do AWS EC2 `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'Os manifestos do aplicativo GitHub agora incluem o campo "request_oauth_on_install". {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/0.yml b/translations/pt-BR/data/release-notes/2-22/0.yml index f25e465abd..602ee375fe 100644 --- a/translations/pt-BR/data/release-notes/2-22/0.yml +++ b/translations/pt-BR/data/release-notes/2-22/0.yml @@ -1,84 +1,71 @@ ---- -intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. -date: '23-09-2020' +intro: O GitHub está animado para apresentar o GitHub Enterprise Server 2.2.0. +date: '2020-09-23' sections: features: - - - heading: GitHub Actions Beta + - heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - - heading: GitHub Packages Beta + - heading: GitHub Packages Beta notes: - | [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - - heading: Advanced Security Code Scanning Beta + - heading: Varredura avançada de segurança de código beta notes: - | [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - - - heading: Pull Request Retargeting + - heading: Redirecionamento de pull request notes: - | - When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - - heading: Suspend and Unsuspend an App Installation + Quando um [branch do cabeçalho do pull request](https://docs.github.com/en/enterprise/2. 2/usuário/github/colaboração-with-issues-and-pull-requests/about-branches#working-with-branches) é mesclado e excluído, todos os outros pull requests no mesmo repositório que apontam para este branch agora são redirecionados para o branch de base do pull request mesclado. Anteriormente, esses pull requests eram fechados. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - heading: Suspender e cancelar a suspensão da instalação de aplicativos notes: - | - Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - - heading: Improved Large Scale Performance + Os administradores e usuários podem [suspender o acesso de qualquer aplicativo do GitHub](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) durante o tempo necessário e [cancelar a suspensão do aplicativo](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) no comando por meio das das Configurações e da API. Os aplicativos suspensos não podem acessar a API do GitHub ou eventos de webhook. Você pode fazer isso em vez de desinstalar um aplicativo, que cancela a autorização de todos os usuários. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - heading: Desempenho aprimorado em grande escala notes: - | We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}'' Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - - heading: View All of Your Users + - heading: Visualizar todos os seus usuários notes: - | - For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' + Para equipes excepcionalmente grandes, os administradores podem [ajustar o padrão máximo de 1.500 para as listas de usuários](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' changes: - - - heading: Administration Changes + - heading: Alterações na administração notes: - - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} - - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'Os trabalhadores compartilhados foram habilitados para tornar as atualizações ao vivo mais resilientes, compartilhando conexões entre as abas. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %}' + - 'The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %}' - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %}' - - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} - - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} - - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %} - - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} - - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - 'You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %}' + - 'Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository''s settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %}' + - 'A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %}' + - 'The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %}' + - 'The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %}' - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}' - - - heading: Security Changes + - heading: Security Changes notes: - - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} - - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %} - - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} - - - heading: Developer Changes + - 'Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %}' + - 'When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %}' + - 'Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %}' + - heading: Developer Changes notes: - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %}' - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' - - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - 'Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %}' - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - - heading: Users and organizations can add Twitter usernames to their GitHub profiles + - heading: Users and organizations can add Twitter usernames to their GitHub profiles notes: - '[Developers and organizations can now add their Twitter username to their profile](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}' - - - heading: API Changes + - heading: API Changes notes: - | #### Graduated Previews @@ -90,41 +77,49 @@ sections: #### GraphQL Schema Changes * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + - heading: VMware Network Driver Changes + notes: + - | + The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + + ``` + WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. + For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. + Proceed with installation? [y/N] + ``` + + The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} - - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} - - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} - - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + - 'The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %}' + - 'The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %}' + - 'A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %}' + - 'If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner''s "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %}' + - 'Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %}' deprecations: - - - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 notes: - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' - - - heading: Deprecation of Legacy GitHub App Webhook Events + - heading: Deprecation of Legacy GitHub App Webhook Events notes: - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' - - - heading: Deprecation of Legacy GitHub Apps Endpoint + - heading: Deprecation of Legacy GitHub Apps Endpoint notes: - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' - - - heading: Deprecation of OAuth Application API + - heading: Deprecation of OAuth Application API notes: - - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - #- type: Backup and Disaster recovery - #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + - 'GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' + backups: + - 'GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/).' known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} - - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %}' + - 'Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %}' - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' - - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} - - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} + - 'GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %}' + - 'On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization''s dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/1.yml b/translations/pt-BR/data/release-notes/2-22/1.yml index 1bd076d4ab..dbc5b4fd91 100644 --- a/translations/pt-BR/data/release-notes/2-22/1.yml +++ b/translations/pt-BR/data/release-notes/2-22/1.yml @@ -1,71 +1,70 @@ ---- -date: '09-10-2020' +date: '2020-10-09' sections: security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - '**MÉDIO**: ImageMagick foi atualizado para o endereço [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'As solicitações de uma integração do aplicativo GitHub para atualizar um token de acesso do OAuth seriam aceitas se forem enviadas com um Id de cliente e segredo de cliente do OAuth diferente e válido que foram usados para criar o token de atualização. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'Um usuário cujo nome de usuário de diretório de LDAP padronizado em um login da conta GHES existente pode efetuar a autenticação na conta existente. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - | - The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + O menu suspenso de formato do ID do nome no Console de Gerenciamento seria redefinido para "não especificado" depois de configurá-lo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - | - Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + A atualização que usa um hotpatch pode falhar com um erro: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + Salvar as configurações por meio do [console de gerenciamento](/admin/configuration/accessing-the-management-console) acrescentaria uma nova linha aos arquivos [certificado TLS/SSL e chave](/admin/configuration/configuring-tls) que acionou o recarregamento desnecessário de alguns serviços. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | - System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + Os logs do sistema para o gráfico de dependência não estavam girando, permitindo um crescimento no armazenamento ilimitado. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | - The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + O gráfico de desempenho do MS SQL Server mostrou estatísticas da instância primária, mesmo quando uma réplica foi selecionada. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} - | - `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + `ghe-actions-precheck` irá sair silenciosamente sem executar as verificações de armazenamento se as Ações não foram habilitadas. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} - | - Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + A atualização poderia falhar se a configuração de substituição dos trabalhadores resgatados estiver em uso. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} - | - Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + Alguns serviços em execução em contêineres não enviaram registros para o jornal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} - | - Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + Os links para as Consultorias de Segurança GitHub usariam uma URL com o nome de host da instância do GitHub Enterprise Server em vez do GitHub.com, direcionando o usuário para uma URL inexistente. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} - | - When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + Ao importar um repositório com "ghe-migrator" poderá gerar uma exceção inesperada quando os dados inconsistentes estão presentes. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} - | - The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + A página de configurações de segurança da conta corporativa mostrou um link para "Visualizar as configurações atuais das organizações" para a configuração da "Autenticação de dois fatores" quando o modo de autenticação em uso não é compatível com autenticação de dois fatores. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} - | - OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + Os tokens de atualização do OAuth seriam removidos prematuramente. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} - | - Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + A pesquisa tarefas de reparo geraria exceções durante a fase de migração da configuração. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} - | - On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + Na página de configurações dos aplicativos GitHub, a aba "Funcionalidades Beta" não estava visível em algumas circunstâncias. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} - | - When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + Ao usar "ghe-migrator" para importar solicitações de revisão de PR, os registros associados com usuários excluídos resultariam em registros estranhos do banco de dados. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} - | - When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + Ao importar usuários com "ghe-migrator", ocorreria o erro de "E-mail é inválido" se o endereço de e-mail gerado pelo sistema tivesse mais de 100 caracteres. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} - | - Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + Registrar a atividade do webhook poderia usar uma grande quantidade de espaço no disco e fazer com que o disco raiz ficasse cheio. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} - | - Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + Os usuários experimentaram desempenho mais lento de recuperação de clone do Git em uma instância com réplicas de alta disponibilidade devido às leituras serem encaminhadas para um nó diferente. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} - | - The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + A página de Configurações do repositório de um repositório para um usuário ou organização de sites do GitHub Pages falharia com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} - | - Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + As operações de manutenção da rede de repositório podem ficar presas no estado "em execução". {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} - | - A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + O fato de um repositório ser excluído imediatamente após o upload da varredura de um código pode haver gerado uma parada no processamento dos resultados dos resultados de verificação de código para todos os repositórios. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} - | - When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + Quando um grande número de resultados de verificação de código foi enviado ao mesmo tempo, o tempo de processamento de lotes pode expirar, gerando uma parada no processamento dos resultados de varredura do código. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - | [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - | GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} changes: - - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} - - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} - - GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %} + - 'O suporte é adicionado ao tipo de instância do AWS EC2 `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'Os manifestos do aplicativo GitHub agora incluem o campo "request_oauth_on_install". {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %}' + - 'GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' + - 'On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization''s dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/2.yml b/translations/pt-BR/data/release-notes/2-22/2.yml index cb8c4025e8..1d7a3fa944 100644 --- a/translations/pt-BR/data/release-notes/2-22/2.yml +++ b/translations/pt-BR/data/release-notes/2-22/2.yml @@ -1,8 +1,7 @@ ---- -date: '20-10-2020' +date: '2020-10-20' sections: security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' bugs: - | If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} @@ -19,11 +18,11 @@ sections: - | On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' + - 'On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization''s dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/3.yml b/translations/pt-BR/data/release-notes/2-22/3.yml index 58ccdc054d..ed2b038671 100644 --- a/translations/pt-BR/data/release-notes/2-22/3.yml +++ b/translations/pt-BR/data/release-notes/2-22/3.yml @@ -1,23 +1,22 @@ ---- -date: '03-11-2020' +date: '2020-11-03' sections: security_fixes: - | **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - | - **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + **BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - | - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} + Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} bugs: - - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} - - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} - - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} - - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + - 'GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' + - 'Os arquivos de configuração para o GitHub Actions não foram copiados para a réplica ao configurar as réplicas de alta disponibilidade, gerando, potencialmente erros durante `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %}' + - 'On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization''s dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %}' + - 'Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'Um método métrico de coleta em segundo plano para aumentar a utilização da CPU. (atualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP da fonte real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/4.yml b/translations/pt-BR/data/release-notes/2-22/4.yml index 5323f58085..ad176a9e83 100644 --- a/translations/pt-BR/data/release-notes/2-22/4.yml +++ b/translations/pt-BR/data/release-notes/2-22/4.yml @@ -1,16 +1,15 @@ ---- -date: '17-11-2020' +date: '2020-11-17' sections: security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' bugs: - - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} - - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} - - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} - - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + - 'Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Após atualizar o GHES com um hotpatch, os comandos `ghe-actions-precheck` e `ghe-packages-precheck` falhariam com o erro `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %}' + - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 em vez do endereço IP da fonte real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %}' known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/5.yml b/translations/pt-BR/data/release-notes/2-22/5.yml index ad39fe92d9..ecd318d528 100644 --- a/translations/pt-BR/data/release-notes/2-22/5.yml +++ b/translations/pt-BR/data/release-notes/2-22/5.yml @@ -1,22 +1,21 @@ ---- -date: '03-12-2020' +date: '2020-12-03' sections: bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' - - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' - - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' - - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + - 'O serviço de autorização foi detectado como não saudável devido a uma condição de raça no bootstrap que gerou a reinicialização do serviço. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'O processo de atualização do Elasticsearch não foi capturado pelo ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Habilitar o GitHub Actions em uma configuração atualizada de alta disponibilidade gerou erros na replicação. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'Um comportamento subjacente fez com que um serviço se tornasse indisponível durante o processo de atualização do hotpatch {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Os usuários que se conectam a uma réplica ativa receberiam um erro ao conectar ao websocket das atualizações ao vivo. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'Um subconjunto de registros de encaminhamento de certificados SSL não foi aplicado corretamente. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Notificações de e-mail enviadas aos usuários suspensos quando foram removidos de uma equipe ou de uma organização. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'A forma como os certificados SSH foram aplicados entre organizações e empresas foi inconsistente. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'Quando uma conta teve o limite de taxa limitado devido ao uso de senhas incorretas, ela pôde ser bloqueada por até 24 horas. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'A sincronização de pull request em repositórios com muitas referências pode fazer com que as filas de trabalhador sejam atrasadas. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'Ao efetuar o login após tentar visitar uma página específica, as pessoas eram enviadas para a página inicial em vez de serem enviadas para o seu destino pretendido. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'Para instâncias de GHES que usam autenticação integrada com um provedor de identidade do SAML interno, os usuários sem um endereço de e-mail associado não podem criar um commit a partir da interface web. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/6.yml b/translations/pt-BR/data/release-notes/2-22/6.yml index f3fc5db2c9..eccedd90f4 100644 --- a/translations/pt-BR/data/release-notes/2-22/6.yml +++ b/translations/pt-BR/data/release-notes/2-22/6.yml @@ -1,18 +1,17 @@ ---- -date: '17-12-2020' +date: '2020-12-17' sections: security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' bugs: - - 'Requests for some file resources like a zip archive or raw file could enter a redirection loop. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' + - 'As solicitações de alguns recursos de arquivo como um arquivo zip ou um arquivo não processado podem entrar em um loop de redirecionamento. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - 'A timeout could prevent some Issues and Pull Requests searches from providing complete search results. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - 'Custom tabs with non-alphabetic characters in small screens did not render correctly. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - 'An underlying behavior was causing failures when pushing content to a Git LFS-enabled repository. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - 'In some rare cases issues could cause a 500 error when accessed via the web interface. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' known_issues: - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/3-0/0-rc1.yml b/translations/pt-BR/data/release-notes/3-0/0-rc1.yml new file mode 100644 index 0000000000..f1a0683507 --- /dev/null +++ b/translations/pt-BR/data/release-notes/3-0/0-rc1.yml @@ -0,0 +1,145 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Package Registry + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. 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 variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Alterações na administração + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - 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. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/pt-BR/data/release-notes/3-0/0-rc2.yml b/translations/pt-BR/data/release-notes/3-0/0-rc2.yml new file mode 100644 index 0000000000..0e6ed5fd3f --- /dev/null +++ b/translations/pt-BR/data/release-notes/3-0/0-rc2.yml @@ -0,0 +1,25 @@ +--- +date: '2021-01-29' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +sections: + bugs: + - + heading: Fixes for known issues from Release Candidate 1 + notes: + - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. + - The "Mandatory message viewed" audit log event was not being saved. + - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' + - Removing yourself as an enterprise owner returned a 404. + - + heading: Fixes for other issues + notes: + - Issues with migrations and upgrades to 3.0.0 have been fixed. + - Backup Utilities versioning now works for release candidate versions. + - Generating a support bundle resulted in an error in the orchestrator logs. + - A large restore could result in Redis running out of memory. + - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. + - GitHub Actions can only be enabled if the required storage is also configured. + - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + known_issues: + - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/translations/pt-BR/data/reusables/actions/actions-not-verified.md b/translations/pt-BR/data/reusables/actions/actions-not-verified.md index 76e742631a..4c83acf907 100644 --- a/translations/pt-BR/data/reusables/actions/actions-not-verified.md +++ b/translations/pt-BR/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Qualquer pessoa pode publicar uma ação em {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +Qualquer pessoa pode publicar uma ação em {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md b/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md index fecdc8ac9c..4babe46a83 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md @@ -1 +1,12 @@ -1. Em "Políticas", selecione uma opção. ![Habilita, desabilita ou limita ações para esta conta corporativa](/assets/images/help/organizations/enterprise-actions-policy.png) +1. Under "Policies", select your options. + + You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + + {% if currentVersion ver_gt "enterprise-server@2.21" %} + {% note %} + + **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + + {% endnote %} + {% endif %} + ![Habilita, desabilita ou limita ações para esta conta corporativa](/assets/images/help/organizations/enterprise-actions-policy.png) diff --git a/translations/pt-BR/data/reusables/actions/enterprise-beta.md b/translations/pt-BR/data/reusables/actions/enterprise-beta.md index d86df3736c..4ec540e93d 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-beta.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. Para revisar os requisitos de armazenamento externo e solicitar acesso ao beta, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/code-scanning/beta.md b/translations/pt-BR/data/reusables/code-scanning/beta.md index aaeb4a91f1..7d1b5dbc94 100644 --- a/translations/pt-BR/data/reusables/code-scanning/beta.md +++ b/translations/pt-BR/data/reusables/code-scanning/beta.md @@ -1,8 +1,8 @@ -{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Nota:** {% data variables.product.prodname_code_scanning_capc %} está atualmente em versão beta e sujeito a alterações. Para obter mais informações sobre a participação no beta, [inscreva-se aqui](https://resources.github.com/beta-signup/). +**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/pt-BR/data/reusables/code-scanning/not-available.md b/translations/pt-BR/data/reusables/code-scanning/not-available.md index 652243c6a1..44df542f07 100644 --- a/translations/pt-BR/data/reusables/code-scanning/not-available.md +++ b/translations/pt-BR/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md new file mode 100644 index 0000000000..c5142332f6 --- /dev/null +++ b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + +{% endnote %} diff --git a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md index dc1266d067..ba307a636c 100644 --- a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". +When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. diff --git a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md index 913ff0dd66..1110f87bdb 100644 --- a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md @@ -1,34 +1,35 @@ -The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. +The following table shows, for each package manager: +- The YAML value to use in the *dependabot.yml* file +- The supported versions of the package manager +- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +- Whether vendored dependencies are supported -| Gerenciador de pacotes | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | -| -------------------------------- |:-----------------------------------------------------------------:|:---------:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir: `hex` | | | -| Elm: `elm` | **✓** | | -| git submodule: `gitsubmodule` | **✓** | | -| GitHub Actions: `github-actions` | **✓** | | -| Go modules: `gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +| Gerenciador de pacotes | YAML value | Supported versions | Private repositories | Vendoring | +| ---------------------- | ---------------- | ------------------------- |:--------------------:|:---------:| +| bundler | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1,v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | +| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | +| Go modules | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | see (A) below | **✓** | | +| Maven | `maven` | see (B) below | **✓** | | +| npm | `npm` | v6 | **✓** | | +| NuGet | `nuget` | <= 4.8.
    see (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**Observação**: {% data variables.product.prodname_dependabot %} também é compatível os seguintes gerentes de pacote: +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn` (apenas v1) (especifique `npm`) +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --`.gradle.kts` files, for Kotlin projects (specify `gradle`) - --`pipenv`, `pip-compile` e `poetry` (especifique `pip`) - -Por exemplo, se você usa o `poetry` para gerenciar suas dependências do Python e quer que {% data variables.product.prodname_dependabot %} monitore seu arquivo de manifesto de dependência para novas versões, use `pacote-ecosystem: "pip"` no seu arquivo *dependabot.yml*. - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. Por exemplo, se você usa o `poetry` para gerenciar suas dependências do Python e quer que {% data variables.product.prodname_dependabot %} monitore seu arquivo de manifesto de dependência para novas versões, use `pacote-ecosystem: "pip"` no seu arquivo *dependabot.yml*. diff --git a/translations/pt-BR/data/reusables/desktop/delete-tag.md b/translations/pt-BR/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..40d455b880 --- /dev/null +++ b/translations/pt-BR/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Right-click the commit. + + - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) + - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/education/about-github-education-link.md b/translations/pt-BR/data/reusables/education/about-github-education-link.md index ee42ff7b3e..9f5fe24818 100644 --- a/translations/pt-BR/data/reusables/education/about-github-education-link.md +++ b/translations/pt-BR/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Antes de solicitar um desconto individual, verifique se sua comunidade de estudos já não é nossa parceira como uma escola {% data variables.product.prodname_education %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)". +Antes de solicitar um desconto individual, verifique se sua comunidade de estudos já não é nossa parceira como uma escola {% data variables.product.prodname_education %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)". diff --git a/translations/pt-BR/data/reusables/education/apply-for-team.md b/translations/pt-BR/data/reusables/education/apply-for-team.md index 70d120b7eb..1fe3d598ae 100644 --- a/translations/pt-BR/data/reusables/education/apply-for-team.md +++ b/translations/pt-BR/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Solicite o [{% data variables.product.prodname_team %}](/articles/github-s-products) grátis, que permite usuários e repositórios privados ilimitados. Para obter mais informações, consulte "[Aplicar um desconto para educador ou pesquisador](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)". +- Solicite o [{% data variables.product.prodname_team %}](/articles/github-s-products) grátis, que permite usuários e repositórios privados ilimitados. Para obter mais informações, consulte "[Aplicar um desconto para educador ou pesquisador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)". diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-administrators.md index b4d889bf00..e1d93dc87d 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-administrators.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/enterprise-administrators.md @@ -1 +1 @@ -{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}Currently, there are two administrative roles available in enterprises: enterprise owners, who can access and manage all settings across the enterprise, and billing managers, who can access and manage only the enterprise's billing settings. {% endif %}Enterprise owners can {% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}also {% endif %} see all of the members and outside collaborators for every organization owned by the enterprise. +{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}Atualmente, existem duas funções administrativas disponíveis nas empresas: proprietários empresariais, que podem acessar e gerenciar todas as configurações na empresa e gerentes de cobrança, que podem acessar e gerenciar apenas as configurações de cobrança da empresa. {% endif %}Os proprietários da empresas podem {% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}também {% endif %} ver todos os integrantes e colaboradores externos para cada organização pertencente à empresa. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index 21c5a40e61..afcce00090 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Nota:**O fornecimento de usuários para contas corporativas está atualmente em versão beta privada e sujeita a alterações. Para solicitar acesso ao beta, [contact our account management team](https://enterprise.github.com/contact) (entre em contato com nossa equipe de gerenciamento de conta). +**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. Para solicitar acesso ao beta, [contact our account management team](https://enterprise.github.com/contact) (entre em contato com nossa equipe de gerenciamento de conta). {% endnote %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 41ce997740..29c948b6c8 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,5 +1,6 @@ -- [Requisitos mínimos](#minimum-requirements) -- [Recursos do beta em {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222) +- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} +- [Optional features](#optional-features){% endif %} - [Armazenamento](#storage) - [CPU e memória](#cpu-and-memory) @@ -7,10 +8,10 @@ Recomendamos diferentes configurações de hardware, dependendo do número de licenças de usuário para {% data variables.product.product_location %}. Se você fornecer mais recursos do que os requisitos mínimos, sua instância terá um desempenho e uma escala melhores. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} If you enable the beta for {% data variables.product.prodname_actions %}, review the following requirements and recommendations. +{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - Você deve configurar pelo menos um executor para fluxos de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- Você deve configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +- Você deve configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". - You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. | Máximo de trabalhos por minuto | Additional vCPUs | Additional memory | @@ -28,9 +29,9 @@ Recomendamos um SSD de alto desempenho com operações de alta entrada/saída po A sua instância exige um disco de dados persistente separado do disco raiz. Para obter mais informações, consulte "[System overview](/enterprise/admin/guides/installation/system-overview)." -{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} -Se você habilitar o beta de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22, você precisará configurar o armazenamento externo do blob. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_actions %} e configurar o armazenamento](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)". +If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". {% endif %} @@ -48,4 +49,4 @@ O {% data variables.product.prodname_ghe_server %} exige mais recursos de CPU e {% endwarning %} -Você pode aumentar os recursos de memória ou da CPU na sua instância. Para obter mais informações, consulte "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources). +Você pode aumentar os recursos de memória ou da CPU na sua instância. Para obter mais informações, consulte "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md index cf565549b2..461702e2fd 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,12 +1,23 @@ -{% if currentVersion == "enterprise-server@2.22" %} +{% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note**: If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Os requisitos mínimos para uma instância com recursos beta habilitados estão em **negrito** na tabela a seguir. For more information about the features in beta, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." +**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." {% endnote %} -| {% endif %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} +| Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | +|:---------------------------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------------:| +| Teste, demonstração ou 10 usuários leves | 2
    ou [**4**](#optional-features) | 16 GB
    ou [**32 GB**](#optional-features) | 100 GB
    ou [**150 GB**](#optional-features) | 200 GB | +| 10-3000 | 4
    ou [**8**](#optional-features) | 32 GB
    ou [**48 GB**](#optional-features) | 250 GB
    ou [**300 GB**](#optional-features) | 200 GB | +| 3000-5000 | 8
    ou [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 12
    ou [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 16
    ou [**20**](#optional-features) | 128 GB
    ou [**160 GB**](#optional-features) | 1000 GB | 200 GB | + +{% else %} + | Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | |:---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------:| ------------------:| | Teste, demonstração ou 10 usuários leves | 2{% if currentVersion == "enterprise-server@2.22" %}
    ou [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
    ou [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
    ou [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | @@ -15,6 +26,8 @@ | 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
    ou [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | | 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
    ou [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
    ou [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | +{% endif %} + For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." {% if currentVersion == "enterprise-server@2.22" %} @@ -25,4 +38,12 @@ You can sign up for beta features available in {% data variables.product.prodnam If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} + +#### Optional features + +You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". + {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md index 70a7cf3f46..c0a2c4832d 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. SSH em {% data variables.product.product_location %}. +1. SSH em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 8fb642aeb2..0cdbb1f880 100644 --- a/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. Para importar os dados de migração arquivados para uma instância do {% data variables.product.prodname_ghe_server %} consulte "[Importing migration data to {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)". +1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[Preparing to migrate data to your enterprise](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/pt-BR/data/reusables/gated-features/code-scanning.md b/translations/pt-BR/data/reusables/gated-features/code-scanning.md index 328f24279e..69e6abf27f 100644 --- a/translations/pt-BR/data/reusables/gated-features/code-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/code-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_code_scanning_capc %} está disponível {% if currentVersion == "free-pro-team@latest" %}em repositórios públicos, e em repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.gated-features.more-info %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/gated-features/environments.md b/translations/pt-BR/data/reusables/gated-features/environments.md index 77cd45f6aa..916fe9c1d3 100644 --- a/translations/pt-BR/data/reusables/gated-features/environments.md +++ b/translations/pt-BR/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/private-pages.md b/translations/pt-BR/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..3fb7f0a3a7 --- /dev/null +++ b/translations/pt-BR/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/pt-BR/data/reusables/gated-features/protected-branches.md b/translations/pt-BR/data/reusables/gated-features/protected-branches.md index 6cbe4e3a9f..ffae769bab 100644 --- a/translations/pt-BR/data/reusables/gated-features/protected-branches.md +++ b/translations/pt-BR/data/reusables/gated-features/protected-branches.md @@ -1 +1 @@ -Os branches protegidos estão disponíveis em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %} {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md index 5f48619eca..696d1f2755 100644 --- a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md @@ -1 +1 @@ -{% data variables.product.prodname_secret_scanning_caps %} está disponível em repositórios públicos e em repositórios privados pertencentes a organizações com uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_secret_scanning_caps %} está disponível {% if currentVersion == "free-pro-team@latest" %}em repositórios públicos, e em repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md index 0e89045792..535fa5cd9d 100644 --- a/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -Depois de criar um gist, não é possível convertê-lo de público para secreto. +After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-billing.md b/translations/pt-BR/data/reusables/github-actions/actions-billing.md index e822bf0930..04d5d9ded7 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-billing.md +++ b/translations/pt-BR/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -O uso de {% data variables.product.prodname_actions %} é grátis para repositórios públicos e executores auto-hospedados. Para repositórios privados, cada conta {% data variables.product.prodname_dotcom %} recebe uma certa quantidade de minutos e armazenamento gratuitos, dependendo do produto usado com a conta. Any usage beyond the included amounts is controlled by spending limits. +{% data variables.product.prodname_actions %} usage is free for both public repositories and self-hosted runners. Para repositórios privados, cada conta {% data variables.product.prodname_dotcom %} recebe uma certa quantidade de minutos e armazenamento gratuitos, dependendo do produto usado com a conta. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md b/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md index 4d8dedb905..222a659fb1 100644 --- a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ O modelo de fluxo de trabalho inicial configura o `PATH` para conter OpenJDK 8 p Por exemplo, para usar a versão 9.0. do JDK para a plataforma x64, você pode usar os parâmetros `setup-java` e configurar os de `java-version` e `architecture` para `'9.0.4'` e `x64`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md b/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md index e6db4f8803..0114ffafd7 100644 --- a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a private preview only. Any users or organizations that are already using this runner can continue using it, but we're not accepting any further users or organizations at this time. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md index b1977a35f2..6db69c0441 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-azure-permissions.md @@ -1,4 +1,4 @@ -Para habilitar a sincronização de equipes para Azure AD, sua instalação Azure AD precisa das seguintes permissões: +Para habilitar a sincronização de equipes para Azure AD, sua instalação Azure AD precisa das seguintes permissões. - Ler os perfis completos de todos os usuários - Entrar e ler o perfil do usuário - Ler dados do diretório diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md index 11ee9d9ae5..24e48ac246 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm.md @@ -1,3 +1,3 @@ -5. Para confirmar a sincronização de equipes: +5. Confirm team synchronization. - Se você tiver acesso ao IdP, clique em **Enable team synchronization** (Habilitar sincronização de equipes). Você será redirecionado para a página do SAML SSO do provedor de identidade e precisará selecionar sua conta e revisar as permissões solicitadas. - Se você não tiver acesso ao IdP, copie o link de redirecionamento do IdP e compartilhe-o com o administrador do IdP para continuar habilitando a sincronização de equipes. ![Botão de redirecionamento Enable team synchronization (Habilitar sincronização de equipes)](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md index 1bac09c271..2943695c94 100644 --- a/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md +++ b/translations/pt-BR/data/reusables/large_files/can-include-lfs-objects-archives.md @@ -1,4 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Você pode escolher se Os objetos de {% data variables.large_files.product_name_short %} estão incluídos nos arquivos do código-fonte, como arquivos ZIP e tarballs, que {% data variables.product.product_name %} cria para o seu repositório. Para obter mais informações, consulte " [Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

    diff --git a/translations/pt-BR/data/reusables/marketplace/launch-with-free.md b/translations/pt-BR/data/reusables/marketplace/launch-with-free.md index 2151c241cc..15e06d0cb2 100644 --- a/translations/pt-BR/data/reusables/marketplace/launch-with-free.md +++ b/translations/pt-BR/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md b/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md index c012314953..1ed5f3afb9 100644 --- a/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md +++ b/translations/pt-BR/data/reusables/organizations/can-require-ssh-cert.md @@ -1 +1 @@ -Você pode exigir que os integrantes usem certificados SSH para acessar os recursos da organização, a menos que o SSH esteja desabilitado no seu repositório. +You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. diff --git a/translations/pt-BR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/pt-BR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md index 06455dd8c1..29620e32dc 100644 --- a/translations/pt-BR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ b/translations/pt-BR/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -1 +1 @@ -Se você não é um gestor de cobrança da organização, peça ao seu cliente para ter um *proprietário* da organização [adicione você à organização como gerente de cobrança](/articles/adding-a-billing-manager-to-your-organization). +If you're not a billing manager for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/pt-BR/data/reusables/organizations/team-synchronization.md b/translations/pt-BR/data/reusables/organizations/team-synchronization.md index e66864f92f..b59010df12 100644 --- a/translations/pt-BR/data/reusables/organizations/team-synchronization.md +++ b/translations/pt-BR/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" %} -Você pode usar a sincronização de equipe para adicionar e remover automaticamente os membros da equipe em uma organização por meio de um provedor de identidade. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." +You can use team synchronization to automatically add and remove organization members to teams through an identity provider. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md index 445ac117f3..3f98063d34 100644 --- a/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md +++ b/translations/pt-BR/data/reusables/package_registry/packages-ghes-release-stage.md @@ -1,7 +1,7 @@ -{% if enterpriseServerVersions contains currentVersion %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Observação:** {% data variables.product.prodname_registry %} está atualmente em beta para {% data variables.product.prodname_ghe_server %} 2.22. Para participar da versão beta da sua instância, use o [formulário de inscrição](https://resources.github.com/beta-signup/). +**Observação:** {% data variables.product.prodname_registry %} está atualmente em beta para {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your {% data variables.product.product_location %}, use the [sign-up form](https://resources.github.com/beta-signup/). {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/pages/about-private-publishing.md b/translations/pt-BR/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..f1f13531ce --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. diff --git a/translations/pt-BR/data/reusables/pages/choose-visibility.md b/translations/pt-BR/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..a33d2bf8fb --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Em "{% data variables.product.prodname_pages %}", selecione o ** visibilidade de {% data variables.product.prodname_pages %}** no menu suspenso e, em seguida, clique em uma visibilidade. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..fc98787aaa --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md b/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md index 7620878dbc..04d4ddeb1c 100644 --- a/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. If you have sensitive data in your site's repository, you may want to remove it before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..3edff9a8bb --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}. Se você não vir suas alterações no navegador após uma hora, consulte "[Sobre erros de criação do Jekyll para sites de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/visit-site.md b/translations/pt-BR/data/reusables/pages/visit-site.md index 07236da819..7518f7f0bf 100644 --- a/translations/pt-BR/data/reusables/pages/visit-site.md +++ b/translations/pt-BR/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% note %} - **Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}. Se você não vir suas alterações no navegador após uma hora, consulte "[Sobre erros de criação do Jekyll para sites de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/pt-BR/data/reusables/profile/profile-readme.md b/translations/pt-BR/data/reusables/profile/profile-readme.md index b19f129859..2c6a027c88 100644 --- a/translations/pt-BR/data/reusables/profile/profile-readme.md +++ b/translations/pt-BR/data/reusables/profile/profile-readme.md @@ -1 +1 @@ -Se você adicionar um arquivo LEIAME à raiz de um repositório público com o mesmo nome de usuário, esse LEIAME aparecerá automaticamente na sua página de perfil. You can edit your profile README with {% data variables.product.company_short %} Flavored Markdown to create a personalized section on your profile. Para obter mais informações, consulte "[Gerenciar seu perfil LEIAME](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". +Se você adicionar um arquivo README à raiz de um repositório público com o mesmo nome de usuário, esse README aparecerá automaticamente na sua página de perfil. Você pode editar seu perfil README com {% data variables.product.company_short %} Flavored Markdown para criar uma seção personalizada no seu perfil. Para obter mais informações, consulte "[Gerenciar seu perfil README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)." diff --git a/translations/pt-BR/data/reusables/project-management/project-board-visibility.md b/translations/pt-BR/data/reusables/project-management/project-board-visibility.md index 3692d90c14..b3eea8ab50 100644 --- a/translations/pt-BR/data/reusables/project-management/project-board-visibility.md +++ b/translations/pt-BR/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -Por padrão, o quadro de projeto é privado e fica visível apenas para pessoas com permissões de leitura, gravação ou de administrador ao quadro de projeto. Um quadro de projeto público fica visível para qualquer pessoa com o URL do quadro de projeto. +Por padrão, o quadro de projeto é privado e fica visível apenas para pessoas com permissões de leitura, gravação ou de administrador ao quadro de projeto. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. diff --git a/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md index 4aee111bdd..fddcf2d586 100644 --- a/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ Ao selecionar a opção **Rebase e merge** em um pull request no {% data variabl Para fazer rebase e merge de pull requests, você deve ter [permissões de gravação](/articles/repository-permission-levels-for-an-organization/) no repositório, e o repositório deve [permitir o merge de rebase](/articles/configuring-commit-rebasing-for-pull-requests/). -O comportamento de rebase e merge em {% data variables.product.product_name %} é ligeiramente diferente do `rebase do git`. O rebase e o merge em {% data variables.product.prodname_dotcom %} sempre atualizará as informações do autor do commit e criará novos SHAs, enquanto `rebase do git` fora do {% data variables.product.prodname_dotcom %} não altera a informação do committer quando a rebase acontece em cima de um commit de ancestral. Para obter mais informações sobre `rebase do git`, consulte [o capítulo "Rebase do Git" no _livro_ Pro Git](https://git-scm.com/docs/git-rebase). +O comportamento de rebase e merge em {% data variables.product.product_name %} é ligeiramente diferente do `rebase do git`. O rebase e o merge em {% data variables.product.prodname_dotcom %} sempre atualizará as informações do autor do commit e criará novos SHAs, enquanto `rebase do git` fora do {% data variables.product.prodname_dotcom %} não altera a informação do committer quando a rebase acontece em cima de um commit de ancestral. For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). Para obter uma representação visual do `rebase do git`, consulte [o capítulo "Branches do Git - Rebase" do livro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md index dd4d5866e6..7fc764345d 100644 --- a/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ b/translations/pt-BR/data/reusables/pull_requests/required-checks-must-pass-to-merge.md @@ -1 +1 @@ -Se as verificações de status forem necessárias para um repositório, as verificações de status necessárias devem passar antes que você possa fazer merge do seu branch no branch protegido. Para obter mais informações, consulte "[Sobre verificações de status obrigatórias](/articles/about-required-status-checks)". +Se as verificações de status forem necessárias para um repositório, as verificações de status necessárias devem passar antes que você possa fazer merge do seu branch no branch protegido. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". diff --git a/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md index 75c4abeb18..3526e39a78 100644 --- a/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/pt-BR/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1,3 +1 @@ -Os administradores do repositório podem exigir que todos os pull requests recebam um número específico de revisões de aprovações de pessoas com permissões de *gravação* ou *administrador* no repositório ou de um proprietário do código designado, antes de serem mesclados em um branch protegido. Para obter mais informações, consulte "[Sobre branches protegidos](/articles/about-protected-branches)". - -Quando as revisões necessárias estão ativadas, qualquer pessoa com acesso ao repositório poderá aprovar alterações em um pull request. No entanto você não conseguirá fazer merge do seu pull request até que o número necessário de revisores com permissões de *gravação* ou *admin* no repositório aprove as alterações do seu pull request na sua revisão. Para obter mais informações sobre os níveis de permissão do repositório, consulte "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization/)". Se a revisão for necessária de um proprietário do código designado e o pull request afetar o código que tem um proprietário designado, a aprovação deste proprietário será obrigatória. +Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. diff --git a/translations/pt-BR/data/reusables/repositories/branch-rules-example.md b/translations/pt-BR/data/reusables/repositories/branch-rules-example.md index 9cadc0abab..ea81704455 100644 --- a/translations/pt-BR/data/reusables/repositories/branch-rules-example.md +++ b/translations/pt-BR/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -Você pode criar uma regra de branch em um repositório para um branch específico, todos os branches, ou qualquer branch que corresponda a um padrão de nomenclatura especificado com a sintaxe fnmatch. Por exemplo, para exigir que qualquer branch que contenha a palavra `versão` tenha pelo menos duas revisões de pull request antes do merge, você pode criar uma regra de branch para `*versão*`. +You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. diff --git a/translations/pt-BR/data/reusables/repositories/dependency-review.md b/translations/pt-BR/data/reusables/repositories/dependency-review.md index e780074c3c..1650483939 100644 --- a/translations/pt-BR/data/reusables/repositories/dependency-review.md +++ b/translations/pt-BR/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ {% if currentVersion == "free-pro-team@latest" %} Additionally, -{% data variables.product.prodname_dotcom %} can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would introduce a vulnerability into your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% data variables.product.prodname_dotcom %} can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would introduce a vulnerability into your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/relative-links.md b/translations/pt-BR/data/reusables/repositories/relative-links.md index 04d1b025e2..d532da34de 100644 --- a/translations/pt-BR/data/reusables/repositories/relative-links.md +++ b/translations/pt-BR/data/reusables/repositories/relative-links.md @@ -1,6 +1,6 @@ É possível definir links relativos e caminhos de imagens em seus arquivos representados para ajudar os leitores a acessar outros arquivos no repositório. -Um link relativo é um link que é relativo ao arquivo atual. Por exemplo, se você tiver um arquivo LEIAME na raiz do seu repositório e tiver outro arquivo em _docs/CONTRIBUTING.md_, o link relativo para _CONTRIBUTING.md_ no seu README pode se parecer com isso: +Um link relativo é um link que é relativo ao arquivo atual. Por exemplo, se você tiver um arquivo README na raiz do seu repositório e tiver outro arquivo em _docs/CONTRIBUTING.md_, o link relativo para _CONTRIBUTING.md_ no seu README pode se parecer com isso: ``` [Diretrizes de contribuição para este projeto](docs/CONTRIBUTING.md) diff --git a/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md index b7c5860f68..cfe413d8a0 100644 --- a/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/pt-BR/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -Depois que todos os revisores necessários tiverem aprovado um pull request, você não conseguirá fazer o merge se houver outros pull requests abertos com revisões pendentes ou rejeitadas e esses pull requests tiverem um branch principal apontando para o mesmo commit. Alguém com as permissões de *gravação* ou *admin* deverá aprovar ou ignorar a revisão de bloqueio nos outros pull requests antes que você possa fazer o merge. +Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. diff --git a/translations/pt-BR/data/reusables/repositories/section-links.md b/translations/pt-BR/data/reusables/repositories/section-links.md index 2ed662658f..fbf15f7f9a 100644 --- a/translations/pt-BR/data/reusables/repositories/section-links.md +++ b/translations/pt-BR/data/reusables/repositories/section-links.md @@ -1,3 +1,3 @@ Você pode vincular diretamente a uma seção de um arquivo interpretado, passando o mouse sobre o título da seção para expor o link: -![Link da seção no arquivo LEIAME para o repositório github/scientist](/assets/images/help/repository/readme-links.png) +![Link da seção no arquivo README para o repositório github/scientist](/assets/images/help/repository/readme-links.png) diff --git a/translations/pt-BR/data/reusables/repositories/workflow-notifications.md b/translations/pt-BR/data/reusables/repositories/workflow-notifications.md index 9884c951fb..fbf7214e60 100644 --- a/translations/pt-BR/data/reusables/repositories/workflow-notifications.md +++ b/translations/pt-BR/data/reusables/repositories/workflow-notifications.md @@ -1,3 +1,5 @@ Se você habilitar o e-mail ou as notificações da web para {% data variables.product.prodname_actions %}, você receberá uma notificação quando qualquer fluxo de trabalho que tenha sido acionado for concluído. A notificação incluirá o status da execução do fluxo de trabalho (incluindo execuções bem-sucedidas, com falhas, neutras e canceladas). Também pode optar por receber uma notificação apenas quando a execução de um fluxo de trabalho falhar. +Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} + Você também pode visualizar o status do fluxo de trabalho executado na aba Ações de um repositório. Para obter mais informações, consulte "[Gerenciar a execução de fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". diff --git a/translations/pt-BR/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/pt-BR/data/reusables/saml/about-user-provisioning-enterprise-account.md index fa41235d0c..2f4d7a21f6 100644 --- a/translations/pt-BR/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/pt-BR/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -Se você usar o Okta como seu IdP, você poderá usar o SCIM para gerenciar a associação à organização na conta corporativa. O SCIM convida automaticamente as pessoas ou remove pessoas de organizações na sua conta corporativa com base no fato de serem integrantes do grupo que correspondem a cada organização em seu IdP. +If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. O SCIM convida automaticamente as pessoas ou remove pessoas de organizações na sua conta corporativa com base no fato de serem integrantes do grupo que correspondem a cada organização em seu IdP. diff --git a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md index f99d2436af..be784eeb4f 100644 --- a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -O SAML SSO concede aos proprietários corporativos da organização em {% data variables.product.prodname_dotcom %} uma forma de controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. diff --git a/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md b/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md index f1a2af7d12..dbc00526e1 100644 --- a/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md +++ b/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md @@ -1 +1 @@ -You must periodically authenticate with your SAML IdP to authenticate and gain access to {% if currentVersion == "free-pro-team@latest" %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. {% if currentVersion == "free-pro-team@latest" %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} +Você deve efetuar a autenticação periodicamente com seu IdP do SAML para autenticar e obter acesso aos {% if currentVersion == "free-pro-team@latest" %} recursos da organização em {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que você identifique-se novamente para continuar. {% if currentVersion == "free-pro-team@latest" %}Você pode visualizar e gerenciar as suas sessões ativas do SAML nas suas configurações de segurança. Para obter mais informações, consulte "[Visualizar e gerenciar suas sessões ativas do SAML.](/articles/viewing-and-managing-your-active-saml-sessions){% endif %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta.md b/translations/pt-BR/data/reusables/secret-scanning/beta.md index e4664002b6..82fdadded9 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/beta.md +++ b/translations/pt-BR/data/reusables/secret-scanning/beta.md @@ -1,5 +1,8 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios privados está atualmente em beta e sujeitos a alterações. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. {% endnote %} + +{% endif %} diff --git a/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md index fff14d2294..7dfe029929 100644 --- a/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ b/translations/pt-BR/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md @@ -1,5 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" %} {% note %} **Nota**: Você não pode desabilitar alguns recursos de segurança e análise que estão habilitados por padrão para repositórios públicos. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md b/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md index 579e36cf57..6acae625a5 100644 --- a/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md +++ b/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md @@ -1,4 +1,4 @@ -1. Navigate to your sponsorship dashboard for the account. +1. Acesse o painel de patrocínio para a conta. - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![Botão de Patrocínio](/assets/images/help/profile/sponsoring-button.png) - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![Botão de Patrocínio](/assets/images/help/sponsors/org-sponsoring-button.png) 1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/pt-BR/data/reusables/support/ghae-priorities.md b/translations/pt-BR/data/reusables/support/ghae-priorities.md index 21df4d4ca4..76aadfdb77 100644 --- a/translations/pt-BR/data/reusables/support/ghae-priorities.md +++ b/translations/pt-BR/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ | Prioridade | Descrição | Exemplos | |:---------------------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} não pode ser acessado ou há uma falha total e esta afeta diretamente a operação do seu negócio.

    _Depois que você arquivar um tíquete de suporte, entre em contato com {% data variables.contact.github_support %} por telefone._ |
    • Erros ou falhas que afetam a funcionalidade central do Git ou do aplicativo web para todos os usuários
    • Degradação grave da rede ou desempenho para a maioria dos usuários
    • Armazenamento esgotado ou que se preenche rapidamente
    • Incidentes de segurança conhecidos ou uma violação do acesso
    | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falha em um ambiente de produção, com impacto limitado nos seus processos de negócios ou afeta apenas determinados clientes. |
    • Redução de desempenho que reduz a produtividade para muitos usuários
    • Problemas de redundância reduzidos provenientes de falhas ou degradação de serviço
    • Erros ou falhas que impactam a produção
    • Problemas de segurança de configuração de {% data variables.product.product_name %}
    | +| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} falha em um ambiente de produção, com impacto limitado nos seus processos de negócios ou afeta apenas determinados clientes. |
    • Redução de desempenho que reduz a produtividade para muitos usuários
    • Problemas de redundância reduzidos provenientes de falhas ou degradação de serviço
    • Erros ou falhas que impactam a produção
    • {% data variables.product.product_name %} configuration security concerns
    | | {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} está passando por problemas e erros limitados ou moderados com {% data variables.product.product_name %} ou você tem preocupações ou dúvidas gerais sobre a operação de {% data variables.product.product_name %}. |
    • Orientação sobre a utilização das APIs e recursos de {% data variables.product.prodname_dotcom %} ou questões sobre a integração de fluxos de trabalho de negócios
    • Problemas com ferramentas de usuário e métodos de coleta de dados
    • Atualizações
    • Relatórios de erros, perguntas gerais de segurança ou outras questões relacionadas a recursos
      • | | {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} está funcionando como esperado. No entanto, você tem uma dúvida ou sugestão sobre {% data variables.product.product_name %} que não é sensível ao tempo, ou não bloqueia a produtividade da sua equipe. |
      • Solicitações de recursos e feedback de produtos
      • Dúvidas gerais sobre a configuração geral ou o uso de {% data variables.product.product_name %}
      • Notificar {% data variables.contact.github_support %} de qualquer alteração planejada
      | diff --git a/translations/pt-BR/data/reusables/user-settings/edit_marketplace_listing.md b/translations/pt-BR/data/reusables/user-settings/edit_marketplace_listing.md index 45342c5709..d5de218f74 100644 --- a/translations/pt-BR/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/pt-BR/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. Role para baixo até a seção do Marketplace e clique em **Editar listagem do Mercado**. A seção do Marketplace só é visível se você permitiu que seu aplicativo fosse instalado por qualquer usuário ou organização ao registrar o aplicativo. Para obter mais informações, consulte a lista dos [requisitos do Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link para editar sua listagem do GitHub Marketplace](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. A seção do Marketplace só é visível se você permitiu que seu aplicativo fosse instalado por qualquer usuário ou organização ao registrar o aplicativo. Para obter mais informações, consulte a lista dos [requisitos do Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link para editar sua listagem do GitHub Marketplace](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md index 175cb8150b..f458924c12 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Tecla | Tipo | Descrição | -| ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `Ação` | `string` | A ação que foi executada. Pode ser `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked` ou `reopened`. Se a ação é `closed` e a chave `merged` é `false`, o pull request foi fechado com commits não mesclados. Se a ação for `closed` e a chave `merged` for `verdadeira`, o pull request foi mesclado. | +| Tecla | Tipo | Descrição | +| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação que foi executada. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. Se a ação é `closed` e a chave `merged` é `false`, o pull request foi fechado com commits não mesclados. Se a ação for `closed` e a chave `merged` for `verdadeira`, o pull request foi mesclado. | diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index f959350afe..6c6b5845e9 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -4,7 +4,7 @@ header: contact: Contato notices: ghae_silent_launch: GitHub AE is currently under limited release. Please contact our Sales Team to find out more. - release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' + release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "About upgrades to new releases."''' localization_complete: Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco. localization_in_progress: Olá! No momento, esta página ainda está sendo desenvolvida ou traduzida. Para obter as informações mais recentes, acesse a documentação em inglês. early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' @@ -132,3 +132,25 @@ product_landing: quick_start: QuickStart reference_guides: Reference guides overview: Visão Geral +product_sublanding: + start: Start + start_path: Start path + learning_paths: Learning paths + learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. + more_guides: mais guias + load_more: Load more guides + all_guides: All Guides + no_result: Sorry, there is no guide that match your filter. + filters: + type: Tipo + topic: Topic + all: Todas + guide_types: + overview: Visão Geral + quick_start: QuickStart + tutorial: Tutorial + how_to: How-to guide + reference: Referência +learning_track_nav: + prevGuide: Previous guide + nextGuide: Next guide diff --git a/translations/pt-BR/data/variables/action_code_examples.yml b/translations/pt-BR/data/variables/action_code_examples.yml index cb6d66ecf9..8f9aecb699 100644 --- a/translations/pt-BR/data/variables/action_code_examples.yml +++ b/translations/pt-BR/data/variables/action_code_examples.yml @@ -292,7 +292,7 @@ - title: Distribute funding in free and open source projects description: Continuous Distribution of funding to project contributors and dependencies - languages: 'Python, Docerfile, Shell, Ruby' + languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: - sponsors @@ -311,7 +311,7 @@ - title: Codeowner validator description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations - languages: 'Go, Shell, Makefile, Docerfile' + languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners diff --git a/translations/pt-BR/data/variables/gists.yml b/translations/pt-BR/data/variables/gists.yml index d263d6bccf..12c745fd3c 100644 --- a/translations/pt-BR/data/variables/gists.yml +++ b/translations/pt-BR/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[Página inicial do gist](https://gist.github.com/){% else %}página inicial do gist, `http(s)://[hostname]/gist` ou `http(s)://gist.[hostname]` se os subdomínios estiverem habilitados {% endif %} + {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %} gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Pesquisa do Gist](https://gist.github.com/search){% else %}Pesquisa do Gist, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` se os subdomínios estiverem habilitados{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %} discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Descubra, `http(s)://[hostname]/gist/discover` ou `http(s)://gist.[hostname]/discover` se os subdomínios estiverem habilitados{% endif %} + {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index e9fc1d446a..9f88ea0a03 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -61,6 +61,7 @@ prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'aplicativo GitHub' prodname_github_apps: 'Aplicativos do GitHub' prodname_oauth_app: 'aplicativo OAuth' +prodname_oauth_apps: 'Aplicativos OAuth' #API and developer docs prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs' prodname_support_forum_with_url: '[Fórum de Suporte e Desenvolvimento de API GitHub](https://github.community/c/github-api-development-and-support/37)' @@ -84,6 +85,7 @@ prodname_insights: 'GitHub Insights' prodname_sponsors: 'GitHub Sponsors' prodname_matching_fund: 'Fundo Correspondentes para Patrocinadores do GitHub' #GitHub Advanced Security +prodname_GH_advanced_security: 'Segurança Avançada GitHub' prodname_advanced_security: 'Segurança Avançada' #Codespaces prodname_codespaces: 'Codespaces' diff --git a/translations/pt-BR/data/variables/release_candidate.yml b/translations/pt-BR/data/variables/release_candidate.yml index ec65ef6f94..71234017da 100644 --- a/translations/pt-BR/data/variables/release_candidate.yml +++ b/translations/pt-BR/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.0 diff --git a/translations/ru-RU/content/actions/creating-actions/about-actions.md b/translations/ru-RU/content/actions/creating-actions/about-actions.md index 3ba6a3504e..ddfc2300dc 100644 --- a/translations/ru-RU/content/actions/creating-actions/about-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/about-actions.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - Action development + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ steps: #### Using a commit's SHA for release management -Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation. +Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value.{% else %}Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation.{% endif %} ```yaml steps: diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md index ee6eadec26..f450b029b0 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -5,7 +5,9 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Action development --- {% data reusables.actions.enterprise-beta %} @@ -65,12 +67,12 @@ Before you begin, you'll create a {% data variables.product.product_name %} repo required: true default: 'World' outputs: - random-number: + random-number: description: "Random number" value: ${{ steps.random-number-generator.outputs.random-id }} runs: using: "composite" - steps: + steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - id: random-number-generator @@ -122,7 +124,7 @@ jobs: uses: actions/hello-world-composite-run-steps-action@v1 with: who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} + - run: echo random-number ${{ steps.foo.outputs.random-number }} shell: bash ``` {% endraw %} diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md index ac11463d80..eb46bcbc68 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md @@ -1,6 +1,6 @@ --- title: Creating a Docker container action -intro: 'This guide shows you the minimal steps required to build a Docker container action.' +intro: This guide shows you the minimal steps required to build a Docker container action. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Action development + - Докер --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ Before you begin, you'll need to create a GitHub repository. 1. From your terminal, change directories into your new repository. - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ Before you begin, you'll need to create a GitHub repository. In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)." **Файл Dockerfile** -```dockerfile +```dockerfile{:copy} # Container image that runs your code FROM alpine:3.10 @@ -65,7 +68,7 @@ Create a new `action.yml` file in the `hello-world-docker-action` directory you {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ Next, the script gets the current time and sets it as an output variable that ac 1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory. -1. Make your `entrypoint.sh` file executable: - - ```shell - chmod +x entrypoint.sh - ``` - 1. Add the following code to your `entrypoint.sh` file. **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" time=$(date) echo "::set-output name=time::$time" ``` - 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. Make your `entrypoint.sh` file executable by running the following command on your system. + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### Creating a README 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. @@ -130,7 +132,7 @@ In your `hello-world-docker-action` directory, create a `README.md` file that sp - An example of how to use your action in a workflow. **README.md** -```markdown +```markdown{:copy} # Hello world docker action This action prints "Hello World" or "Hello" + the name of a person to greet to the log. @@ -160,7 +162,7 @@ From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and 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 entrypoint.sh Dockerfile README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1 @@ -175,11 +177,11 @@ Now you're ready to test your action out in a workflow. When an action is in a p #### Example using a public action -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. +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. {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### Example using a private action -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. +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. {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md index ac6cd8748b..99b90997f1 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Action development + - JavaScript --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md index f336e760fa..6fda8bdecd 100644 --- a/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -8,7 +8,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'ссылка' +type: reference --- {% data reusables.actions.enterprise-beta %} @@ -48,20 +48,21 @@ The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Dock If you configure your container to use the _exec_ form of the `ENTRYPOINT` instruction, the `args` configured in the action's metadata file won't run in a command shell. If the action's `args` contain an environment variable, the variable will not be substituted. For example, using the following _exec_ format will not print the value stored in `$GITHUB_SHA`, but will instead print `"$GITHUB_SHA"`. -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` If you want variable substitution, then either use the _shell_ form or execute a shell directly. For example, using the following _exec_ format, you can execute a shell to print the value stored in the `GITHUB_SHA` environment variable. -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction: ##### Example *Dockerfile* -``` + +```dockerfile # Container image that runs your code FROM debian:9.5-slim diff --git a/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md index df854ddf2c..1b140c3d07 100644 --- a/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,11 +41,13 @@ For more information, see "[Creating a JavaScript action](/articles/creating-a-j If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. Например: +{% raw %} ``` if ; then echo "Game over!" exit 1 fi ``` +{% endraw %} For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)." diff --git a/translations/ru-RU/content/actions/guides/about-continuous-integration.md b/translations/ru-RU/content/actions/guides/about-continuous-integration.md index cf8d21e5a4..287eaa8a9d 100644 --- a/translations/ru-RU/content/actions/guides/about-continuous-integration.md +++ b/translations/ru-RU/content/actions/guides/about-continuous-integration.md @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - CI + - CD --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md b/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md index fc8e30e426..374e15b5a7 100644 --- a/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - Упаковка --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/about-service-containers.md b/translations/ru-RU/content/actions/guides/about-service-containers.md index b705735032..eb9310acb9 100644 --- a/translations/ru-RU/content/actions/guides/about-service-containers.md +++ b/translations/ru-RU/content/actions/guides/about-service-containers.md @@ -8,7 +8,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - Containers + - Докер --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ You can use the `services` keyword to create service containers that are part of This example creates a service called `redis` in a job called `container-job`. The Docker host in this example is the `node:10.18-jessie` container. {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -89,7 +92,7 @@ When you specify the Docker host port but not the container port, the container This example maps the service container `redis` port 6379 to the Docker host port 6379. {% raw %} -```yaml +```yaml{:copy} name: Redis Service Example on: push diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md index c9a67cf085..9382136910 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CI + - Java + - Ant --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ To get started quickly, you can choose the preconfigured Ant template when you c You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ The starter workflow will run the default target specified in your _build.xml_ f If you use different commands to build your project, or you want to run a different target, you can specify those. For example, you may want to run the `jar` target that's configured in your _build-ci.xml_ file. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ After your build has succeeded and your tests have passed, you may want to uploa Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You can upload the contents of that directory using the `upload-artifact` action. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md index 92bb9e22c2..11a74747da 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CI + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ To get started quickly, you can choose the preconfigured Gradle template when yo You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ The starter workflow will run the `build` task by default. In the default Gradle If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your _ci.gradle_ file. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. + # Restoring these files from a GitHub Actions cache might cause problems for future builds. + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` directory of the runner's home directory. The cache key will be the hashed contents of the gradle build files, so changes to them will invalidate the cache. +This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache. ### Packaging workflow data as artifacts @@ -122,7 +135,7 @@ After your build has succeeded and your tests have passed, you may want to uploa Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md index bd75623a94..db15f79038 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CI + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ To get started quickly, you can choose the preconfigured Maven template when you You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ The starter workflow will run the `package` target by default. In the default Ma If you use different commands to build your project, or you want to use a different target, you can specify those. For example, you may want to run the `verify` target that's configured in a _pom-ci.xml_ file. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. For more information, see "Caching dependencies to speed up workflows" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -122,7 +126,7 @@ After your build has succeeded and your tests have passed, you may want to uploa Maven will usually create output files like JARs, EARs, or WARs in the `target` directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory called `staging`. Then you can upload the contents of that directory using the `upload-artifact` action. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-net.md b/translations/ru-RU/content/actions/guides/building-and-testing-net.md index e244b11f7d..73a2e0b621 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-net.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. -The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action. #### Using multiple .NET versions diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md index 7a1bb014a9..7c660cf58a 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md @@ -8,7 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CI + - Node + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -77,7 +81,7 @@ The template includes a matrix strategy that builds and tests your code with fou 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 "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." {% raw %} -```yaml +```yaml{:copy} strategy: matrix: node-version: [10.x, 12.x, 14.x, 15.x] @@ -93,7 +97,7 @@ steps: Alternatively, you can build and test with exact Node.js versions. -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -102,7 +106,7 @@ strategy: Or, you can build and test using a single version of Node.js too. {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -136,7 +140,7 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install). -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -150,7 +154,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -166,7 +170,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -179,7 +183,7 @@ steps: Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file. -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -201,7 +205,7 @@ In the example below, the secret `NPM_TOKEN` stores the npm authentication token 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -220,7 +224,7 @@ steps: The example above creates an *.npmrc* file with the following contents: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -231,7 +235,7 @@ always-auth=true When using {% data variables.product.prodname_dotcom %}-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" and the [`cache` action](https://github.com/marketplace/actions/cache). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -256,7 +260,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md b/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md index fc03f41966..ac78e5d897 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md @@ -7,7 +7,10 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee -type: 'руководство' +type: tutorial +topics: + - CI + - Powershell --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-python.md b/translations/ru-RU/content/actions/guides/building-and-testing-python.md index 9c4c0c9703..5fd5281ed6 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-python.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-python.md @@ -7,7 +7,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CI + - Python --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ We recommend that you have a basic understanding of Python, PyPy, and pip. До To get started quickly, add the template to the `.github/workflows` directory of your repository. {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -94,7 +97,7 @@ If you are using a self-hosted runner, you can configure the runner to use the ` #### Using multiple Python versions {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -126,7 +129,7 @@ jobs: 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 +```yaml{:copy} name: Python package on: [push] @@ -158,7 +161,7 @@ If you specify a version of Python that is not available, `setup-python` fails w 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 +```yaml{:copy} name: Python package on: [push] @@ -196,7 +199,7 @@ We recommend using `setup-python` to configure the version of Python used in you 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -213,7 +216,7 @@ steps: After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -234,7 +237,7 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can 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). {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Setup Python @@ -271,7 +274,7 @@ You can use the same commands that you use locally to build and test your code. 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -295,7 +298,7 @@ steps: 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 +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -318,7 +321,7 @@ steps: 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 +```yaml{:copy} name: Python package on: [push] @@ -352,7 +355,7 @@ You can upload artifacts to view after a workflow completes. For example, you ma 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 +```yaml{:copy} name: Python package on: [push] @@ -365,26 +368,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} ``` {% endraw %} @@ -395,7 +398,7 @@ You can configure your workflow to publish your Python package to any package re You can store any access tokens or credentials needed to publish your package using secrets. The following example creates and publishes a package to PyPI using `twine` and `dist`. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." {% raw %} -```yaml +```yaml{:copy} name: Upload Python Package on: diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md index 8dc0c358f9..839b0ff44c 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md @@ -5,7 +5,10 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CI + - Ruby --- {% data reusables.actions.enterprise-beta %} @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -63,7 +63,7 @@ jobs: The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index daffa2cb6b..3cbdf80461 100644 --- a/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -9,7 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: 'руководство' +type: tutorial +topics: + - Workflows --- ### About caching workflow dependencies @@ -68,7 +70,7 @@ For more information, see [`actions/cache`](https://github.com/actions/cache). This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file. {% raw %} -```yaml +```yaml{:copy} name: Caching with npm on: push @@ -124,14 +126,14 @@ A cache key can include any of the contexts, functions, literals, and operators Using expressions to create a `key` allows you to automatically create a new cache when dependencies have changed. For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file. {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`. -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ You can provide a list of restore keys to use when there is a cache miss on `key #### Example using multiple restore keys {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | The runner evaluates the expressions, which resolve to these `restore-keys`: {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md b/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md index fa571dc029..1668ca64eb 100644 --- a/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Containers + - Докер --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL service example on: push @@ -94,7 +97,7 @@ jobs: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} jobs: # Label of the container job container-job: @@ -124,7 +127,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -159,7 +162,7 @@ When you run a job directly on the runner machine, you'll need to map the ports {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL Service Example on: push @@ -220,7 +223,7 @@ jobs: The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)." -```yaml +```yaml{:copy} jobs: # Label of the runner job runner-job: @@ -251,7 +254,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -287,7 +290,7 @@ You can modify *client.js* to include any PostgreSQL operations needed by your w {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md b/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md index ed162bb97a..776e92ec19 100644 --- a/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md +++ b/translations/ru-RU/content/actions/guides/creating-redis-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Containers + - Докер --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -91,7 +94,7 @@ jobs: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} jobs: # Label of the container job container-job: @@ -118,7 +121,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -152,7 +155,7 @@ When you run a job directly on the runner machine, you'll need to map the ports {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis runner example on: push @@ -210,7 +213,7 @@ jobs: The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)." -```yaml +```yaml{:copy} jobs: # Label of the runner job runner-job: @@ -238,7 +241,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -274,7 +277,7 @@ You can modify *client.js* to include any Redis operations needed by your workfl {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // Creates a new Redis client diff --git a/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md index a4c7ce00e0..9930521a1d 100644 --- a/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Amazon ECS --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md b/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md index 32ac95fb40..d41b31850f 100644 --- a/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Azure App Service --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md index 3628c6eaa1..68f42d9dd8 100644 --- a/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/index.md b/translations/ru-RU/content/actions/guides/index.md index 6c9940f419..88a57ba8c8 100644 --- a/translations/ru-RU/content/actions/guides/index.md +++ b/translations/ru-RU/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/ru-RU/content/actions/guides/publishing-docker-images.md b/translations/ru-RU/content/actions/guides/publishing-docker-images.md index 0b906c5d9c..f6bef54741 100644 --- a/translations/ru-RU/content/actions/guides/publishing-docker-images.md +++ b/translations/ru-RU/content/actions/guides/publishing-docker-images.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Упаковка + - Publishing + - Докер --- {% data reusables.actions.enterprise-beta %} @@ -55,7 +59,7 @@ The `build-push-action` options required for Docker Hub are: * `repository`: Your Docker Hub repository in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -93,7 +97,7 @@ The `build-push-action` options required for {% data variables.product.prodname_ * `repository`: Must be set in the format `OWNER/REPOSITORY/IMAGE_NAME`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `repository` option should be set to `octo-org/octo-repo/octo-image`. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -126,7 +130,7 @@ In a single workflow, you can publish your Docker image to multiple registries b The following example workflow uses the `build-push-action` steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries. {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: diff --git a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md index bcfeb2b04c..a7229923e8 100644 --- a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Упаковка + - Publishing + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ Each time you create a new release, you can trigger a workflow to publish your p You can define a new Maven repository in the publishing block of your _build.gradle_ file that points to your package repository. For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _build.gradle_ could specify a repository with the name `"OSSRH"`. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -67,7 +72,7 @@ In the deploy step, you’ll need to set environment variables for the username {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -105,7 +110,7 @@ The `GITHUB_TOKEN` exists in your repository by default and has read and write p For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -126,7 +131,7 @@ publishing { With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -162,7 +167,7 @@ For example, if you deploy to the Central Repository through the OSSRH hosting p If your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example. {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -191,7 +196,7 @@ publishing { With this configuration, you can create a workflow that publishes your package to both the Maven Central Repository and {% data variables.product.prodname_registry %} by running the `gradle publish` command. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md index 07ffac448c..a12f63a31a 100644 --- a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Упаковка + - Publishing + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +52,7 @@ In this workflow, you can use the `setup-java` action. This action installs the For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _pom.xml_ could specify a distribution management repository with the `id` of `ossrh`. {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ In the deploy step, you’ll need to set the environment variables to the userna {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ For a Maven-based project, you can make use of these settings by creating a dist For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _pom.xml_ would look similar to the below example. {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ For example, if your organization is named "octocat" and your repository is name With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by making use of the automatically generated _settings.xml_. {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ You can publish your packages to both the Maven Central Repository and {% data v Ensure your _pom.xml_ file includes a distribution management repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider. For example, if you deploy to the Central Repository through the OSSRH hosting project, you might want to specify it in a distribution management repository with the `id` set to `ossrh`, and you might want to specify {% data variables.product.prodname_registry %} in a distribution management repository with the `id` set to `github`. {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md index ac54eaf68b..696c0a57aa 100644 --- a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md @@ -8,7 +8,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Упаковка + - Publishing + - Node + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -54,7 +59,7 @@ If you're publishing a package that includes a scope prefix, include the scope i This example stores the `NPM_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -78,7 +83,7 @@ jobs: In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents: -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -114,7 +119,7 @@ If you want to publish your package to a different repository, you must use a pe This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -140,7 +145,7 @@ jobs: The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file. -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -151,7 +156,7 @@ always-auth=true If you use the Yarn package manager, you can install and publish packages using Yarn. {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -167,7 +172,7 @@ jobs: node-version: '12.x' registry-url: 'https://registry.npmjs.org' # Defaults to the user or organization that owns the workflow file - scope: '@octocat' + scope: '@octocat' - run: yarn - run: yarn publish env: @@ -196,7 +201,7 @@ When you use the `scope` input to the `setup-node` action, the action creates an This workflow calls the `setup-node` action two times. Each time the `setup-node` action runs, it overwrites the *.npmrc* file. The *.npmrc* file references the token that allows you to perform authenticated operations against the package registry from the `NODE_AUTH_TOKEN` environment variable. The workflow sets the `NODE_AUTH_TOKEN` environment variable each time the `npm publish` command is run, first with a token to publish to npm (`NPM_TOKEN`) and then with a token to publish to {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`). {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: diff --git a/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 0a5c6a8bbb..554d123c37 100644 --- a/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,7 +11,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Workflows + - CI --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md index 1f8698cda6..6ff60f2588 100644 --- a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,7 +11,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Workflows --- {% data reusables.actions.enterprise-beta %} @@ -79,7 +81,7 @@ This example shows you how to create a workflow for a Node.js project that build The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also and uploads the `code-coverage.html` report as another artifact. -```yaml +```yaml{:copy} name: Node CI on: [push] @@ -114,7 +116,7 @@ jobs: 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' uses: actions/upload-artifact@v2 with: @@ -183,7 +185,7 @@ Job 3 displays the result uploaded in the previous job: The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`. -```yaml +```yaml{:copy} name: Share data between jobs on: [push] diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 90e07d9e6b..de63903828 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +38,7 @@ If setting environment variables is not practical, you can set the proxy configu An example _.env_ proxy configuration is shown below: -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index e371928144..77537c94ae 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -64,8 +64,11 @@ These labels operate cumulatively, so a self-hosted runner’s labels must match ### Routing precedence for self-hosted runners -If you use both repository-level and organization-level runners, {% data variables.product.prodname_dotcom %} follows an order of precedence when routing jobs to self-hosted runners: +When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels: -1. The job's `runs-on` labels are processed. {% data variables.product.prodname_dotcom %} then attempts to locate a runner that matches the label requirements: -2. The job is sent to a repository-level runner that matches the job labels. If no repository-level runner is available (either busy, offline, or no matching labels): -3. The job is sent to an organization-level runner that matches the job labels. If no organization-level runner is available, the job request fails with an error. +1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}. +2. The job is then sent to the first matching runner that is online and idle. + - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners. + - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners. + - If there are no matching runners at any level, the job will fail. + - If the job remains queued for more than 24 hours, the job will fail. diff --git a/translations/ru-RU/content/actions/index.md b/translations/ru-RU/content/actions/index.md index 39b2e0d291..6fffe233c7 100644 --- a/translations/ru-RU/content/actions/index.md +++ b/translations/ru-RU/content/actions/index.md @@ -10,21 +10,22 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: + - + title: Environments, environment protection rules and environment secrets (beta) + date: '2020-12-15' + href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ - title: Workflow visualization date: '2020-12-08' @@ -33,10 +34,6 @@ changelog: title: Removing set-env and add-path commands on November 16 date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Ubuntu-latest workflows will use Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ @@ -73,7 +70,7 @@ versions: {% render 'code-example-card' for actionsCodeExamples as example %}
    - +
    {% octicon "search" width="24" %}
    diff --git a/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md index 442799764b..1e37e74eb0 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -5,7 +5,9 @@ intro: '{% data variables.product.prodname_actions %} are designed to help you b versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md index 3c30b355f5..90d8410b43 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} @@ -68,7 +70,7 @@ steps: #### Using SHAs -If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. This example targets an action's SHA: +If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA: ```yaml steps: diff --git a/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md index 444cf11661..eb2b76c22c 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -9,7 +9,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - Fundamentals --- {% data reusables.actions.enterprise-beta %} @@ -147,7 +149,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s ``` - Groups together all the steps that run in the check-bats-version job. Each line nested under this section is a separate action. + 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. @@ -180,7 +182,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s ``` - 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. + 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. diff --git a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md index 4fa6171158..5b0ad3909f 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 938adb3f83..68fec2ac9c 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Azure Pipelines + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -62,16 +67,16 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: scripts - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in the default shell" - - bash: echo "This step runs in bash" - - pwsh: Write-Host "This step runs in PowerShell Core" - - task: PowerShell@2 - inputs: - script: Write-Host "This step runs in PowerShell" + - job: scripts + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in the default shell" + - bash: echo "This step runs in bash" + - pwsh: Write-Host "This step runs in PowerShell Core" + - task: PowerShell@2 + inputs: + script: Write-Host "This step runs in PowerShell" ``` {% endraw %} @@ -82,13 +87,13 @@ jobs: scripts: runs-on: windows-latest steps: - - run: echo "This step runs in the default shell" - - run: echo "This step runs in bash" - shell: bash - - run: Write-Host "This step runs in PowerShell Core" - shell: pwsh - - run: Write-Host "This step runs in PowerShell" - shell: powershell + - run: echo "This step runs in the default shell" + - run: echo "This step runs in bash" + shell: bash + - run: Write-Host "This step runs in PowerShell Core" + shell: pwsh + - run: Write-Host "This step runs in PowerShell" + shell: powershell ``` {% endraw %} @@ -123,11 +128,11 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_command - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in CMD on Windows by default" + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} @@ -138,9 +143,9 @@ jobs: run_command: runs-on: windows-latest steps: - - run: echo "This step runs in PowerShell on Windows by default" - - run: echo "This step runs in CMD on Windows explicitly" - shell: cmd + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %} @@ -171,12 +176,12 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: conditional - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This step runs with str equals 'ABC' and num equals 123" - condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) + - job: conditional + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This step runs with str equals 'ABC' and num equals 123" + condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123)) ``` {% endraw %} @@ -187,8 +192,8 @@ jobs: conditional: runs-on: ubuntu-latest steps: - - run: echo "This step runs with str equals 'ABC' and num equals 123" - if: ${{ env.str == 'ABC' && env.num == 123 }} + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %} @@ -217,29 +222,29 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: initial - pool: - vmImage: 'ubuntu-latest' - steps: - - script: echo "This job will be run first." -- job: fanout1 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout2." -- job: fanout2 - pool: - vmImage: 'ubuntu-latest' - dependsOn: initial - steps: - - script: echo "This job will run after the initial job, in parallel with fanout1." -- job: fanin: - pool: - vmImage: 'ubuntu-latest' - dependsOn: [fanout1, fanout2] - steps: - - script: echo "This job will run after fanout1 and fanout2 have finished." + - job: initial + pool: + vmImage: 'ubuntu-latest' + steps: + - script: echo "This job will be run first." + - job: fanout1 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout2." + - job: fanout2 + pool: + vmImage: 'ubuntu-latest' + dependsOn: initial + steps: + - script: echo "This job will run after the initial job, in parallel with fanout1." + - job: fanin: + pool: + vmImage: 'ubuntu-latest' + dependsOn: [fanout1, fanout2] + steps: + - script: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -250,22 +255,22 @@ jobs: initial: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." fanout1: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout2." + - run: echo "This job will run after the initial job, in parallel with fanout2." fanout2: runs-on: ubuntu-latest needs: initial steps: - - run: echo "This job will run after the initial job, in parallel with fanout1." + - run: echo "This job will run after the initial job, in parallel with fanout1." fanin: runs-on: ubuntu-latest needs: [fanout1, fanout2] steps: - - run: echo "This job will run after fanout1 and fanout2 have finished." + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %} @@ -294,15 +299,15 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_python - pool: - vmImage: 'ubuntu-latest' - steps: - - task: UsePythonVersion@0 - inputs: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} @@ -313,11 +318,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 81211bae37..2ab59b3ab8 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - CircleCI + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -258,24 +263,24 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem - - name: Setup file system permissions - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} @@ -412,35 +417,35 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - - uses: actions/checkout@v2 - - name: Setup Ruby - uses: eregon/use-ruby-action@master - with: - ruby-version: ${{ matrix.ruby }} - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: vendor/bundle - key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - name: Install postgres headers - run: sudo apt-get install libpq-dev - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake - - name: Install appraisal - run: bundle exec appraisal install - - name: Run appraisal - run: bundle exec appraisal rake + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 9e486eb227..8d0d950df5 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,7 +4,12 @@ intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share sev versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - GitLab + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,12 +340,12 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} @@ -371,7 +376,7 @@ GitLab CI/CD script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -424,12 +429,12 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js tags: - docker ``` diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index c35f28f041..e1708a3e76 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Jenkins + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ Jenkins lets you send builds to a single build agent, or you can distribute them Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}. | Jenkins | {% data variables.product.prodname_actions %} -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### Using sections to organize pipelines @@ -51,7 +56,6 @@ Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% d | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### Using directives Jenkins uses directives to manage _Declarative Pipelines_. These directives define the characteristics of your workflow and how it will execute. The table below demonstrates how these directives map to concepts within {% data variables.product.prodname_actions %}. @@ -69,7 +73,6 @@ Jenkins uses directives to manage _Declarative Pipelines_. These directives defi | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### Using sequential stages #### Parallel job processing @@ -114,23 +117,23 @@ Jenkins Pipeline - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +``` @@ -150,25 +153,24 @@ Jenkins Pipeline - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +``` @@ -188,30 +190,28 @@ Jenkins Pipeline - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +``` @@ -231,26 +231,27 @@ Jenkins Pipeline - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - name: demo-workflow - on: - push: - jobs: - test: - runs-on: ${{ matrix.os }} - strategy: - fail-fast: false - matrix: - os: [macos-latest, ubuntu-latest] - steps: - - uses: actions/checkout@v1 - - uses: actions/setup-node@v1 - with: - node-version: 12 - - run: npm install -g bats - - run: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index f63ba3fd2f..1955f591cc 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'руководство' +type: tutorial +topics: + - Travis CI + - Migration + - CI + - CD --- ### Introduction @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -155,9 +160,9 @@ git: {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %} @@ -207,10 +212,10 @@ When working with different languages in {% data variables.product.prodname_acti Например: ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` ### Error handling in {% data variables.product.prodname_actions %} @@ -275,11 +280,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} @@ -345,20 +350,20 @@ Travis CI - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +``` @@ -378,24 +383,24 @@ Travis CI {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md index d9a3598533..2d561318f7 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -8,7 +8,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview +topics: + - Безопасность --- {% data reusables.actions.enterprise-beta %} @@ -54,11 +56,13 @@ This means that a compromise of a single action within a workflow can be very si Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail. {% endwarning %} + {% endif %} * **Audit the source code of the action** @@ -140,4 +144,4 @@ The following tables describe the {% data variables.product.prodname_actions %} | `action:org.runner_group_removed` | Triggered when an organization admin removes a self-hosted runner group. | | `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | | `action:org.runner_group_runners_added` | Triggered when an organization admin [adds 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). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/ru-RU/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index 162499b98a..523e8d551c 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///workflows//badge.svg This Markdown example adds a status badge for a workflow with the name "Greet Everyone." The `OWNER` of the repository is the `actions` organization and the `REPOSITORY` name is `hello-world`. -``` +```markdown ![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ This Markdown example adds a status badge for a workflow with the name "Greet Ev This Markdown example adds a status badge for a workflow with the file path `.github/workflows/main.yml`. The `OWNER` of the repository is the `actions` organization and the `REPOSITORY` name is `hello-world`. -``` +```markdown ![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ This Markdown example adds a status badge for a workflow with the file path `.gi This Markdown example adds a status badge for a branch with the name `feature-1`. -``` +```markdown ![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ This Markdown example adds a status badge for a branch with the name `feature-1` This Markdown example adds a badge that displays the status of workflow runs triggered by the `pull_request` event. -``` +```markdown ![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 081baff4a2..9fd8b65408 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -18,7 +18,7 @@ To run a workflow manually, the workflow must be configured to run on the `workf To trigger the `workflow_dispatch` event on {% data variables.product.prodname_dotcom %}, your workflow must be in the default branch. Follow these steps to manually trigger a workflow run. -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ru-RU/content/actions/quickstart.md b/translations/ru-RU/content/actions/quickstart.md index 12893c57bd..35dcfc45b2 100644 --- a/translations/ru-RU/content/actions/quickstart.md +++ b/translations/ru-RU/content/actions/quickstart.md @@ -7,6 +7,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 403079128a..92d109a73d 100644 --- a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -186,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -348,7 +348,7 @@ The value for `array` can be an array or a string. All values in `array` are con `join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted' -#### toJson +#### toJSON `toJSON(value)` @@ -358,13 +358,13 @@ Returns a pretty-print JSON representation of `value`. You can use this function `toJSON(job)` might return `{ "status": "Success" }` -#### fromJson +#### fromJSON `fromJSON(value)` -Returns a JSON object for `value`. You can use this function to provide a JSON object as an evaluated expression. +Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string. -##### Пример +##### Example returning a JSON object This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`. @@ -384,12 +384,33 @@ jobs: needs: job1 runs-on: ubuntu-latest strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} steps: - run: build ``` {% endraw %} +##### Example returning a JSON data type + +This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer. + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... +``` +{% endraw %} + #### hashFiles `hashFiles(path)` diff --git a/translations/ru-RU/content/actions/reference/environment-variables.md b/translations/ru-RU/content/actions/reference/environment-variables.md index 34fef4132b..86e024515c 100644 --- a/translations/ru-RU/content/actions/reference/environment-variables.md +++ b/translations/ru-RU/content/actions/reference/environment-variables.md @@ -21,15 +21,25 @@ versions: 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)." ```yaml -steps: - - name: Hello world - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +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. + +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 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV` environment file{% else %} `set-env` workflow command{% endif %} to set an environment variable that the following steps in a workflow can use. The {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}environment file{% else %} `set-env` command{% endif %} 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)." ### Default environment variables diff --git a/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md index 9d4eb18a9f..2ad8a688d4 100644 --- a/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md @@ -257,7 +257,7 @@ During the execution of a workflow, the runner generates temporary files that ca **Warning:** 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 ``` @@ -272,11 +272,19 @@ Creates or updates an environment variable for any actions running next in a job #### Пример -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` - -Running `$action_state` in a future step will now return `yellow` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} #### Multiline strings @@ -291,7 +299,7 @@ For multiline strings, you may use a delimiter with the following syntax. ##### Пример 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 id: step_one diff --git a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md index 5b5d69a686..443bc35ca8 100644 --- a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ The name of your workflow. {% data variables.product.prodname_dotcom %} displays ### `on` -**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)." +**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 %} @@ -286,7 +286,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al ### `jobs..runs-on` -**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. +**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. {% data reusables.actions.enterprise-github-hosted-runners %} @@ -299,6 +299,7 @@ Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} ##### Пример @@ -518,7 +519,7 @@ Actions are either JavaScript files or Docker containers. If the action you're u ```yaml steps: # Reference a specific commit - - uses: actions/setup-node@74bc508 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e # Reference the major version of a release - uses: actions/setup-node@v1 # Reference a minor version of a release @@ -700,12 +701,24 @@ steps: 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}`. +Например: + +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +The command used, `perl` in this example, must be installed on the runner. 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)." + #### Exit codes and error action preference 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`: - - Fail-fast behavior using `set -e o pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms. + - 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. @@ -1186,7 +1199,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.
    `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 tags with major version 1 or 2 | `v1.10.1`

    `v2.0.0` | +| `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` | #### Patterns to match file paths diff --git a/translations/ru-RU/content/admin/configuration/command-line-utilities.md b/translations/ru-RU/content/admin/configuration/command-line-utilities.md index 23452731fd..3c80d2f809 100644 --- a/translations/ru-RU/content/admin/configuration/command-line-utilities.md +++ b/translations/ru-RU/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` Allows you to find the uuid of your node in `cluster.conf`. -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -545,8 +545,8 @@ ghe-dpages status ``` To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node: -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -571,16 +571,16 @@ ghe-spokes route To evacuate storage services on a cluster node: -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage This utility allows you to evacuate all storage services before evacuating a cluster node. -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md b/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md index 03d990e4b9..53849b5f1e 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ For more information about contacting support, see "[About {% data variables.con - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server. - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails. - {% note %} - - **Note:** If you select the **Send from author** checkbox in a repository’s **Services** email webhook, outbound email for that repository will send from the author and not from the no-reply email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)." - - {% endnote %} - 6. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. ![Checkbox to discard emails addressed to the no-reply email address](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. Under **Support**, choose a type of link to offer additional support to your users: - **Email:** An internal email address. @@ -155,7 +149,7 @@ You'll notice that `metroplex` catches the inbound message, processes it, then m #### Verify your DNS settings -In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incom emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." +In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." #### Check firewall or AWS Security Group settings diff --git a/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index 2c87343625..a2104514d1 100644 --- a/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -10,7 +10,7 @@ versions: ### About high availability replication for clusters -You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests without data loss. +You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage. In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests. diff --git a/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md index 7868b4b8b1..c429e92707 100644 --- a/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ If you're taking a node offline that has any data services (like git, pages, or ghe-spokes evac-status ``` For {% data variables.product.prodname_pages %} + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} For storage ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ If you're taking a node offline that has any data services (like git, pages, or 3. After the copying is complete, you can evacuate the storage service. Run any of the following commands: For Git + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} For {% data variables.product.prodname_pages %} + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} For storage, take the node offline + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} then evacuate + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md b/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md index 0fdc22d211..3cb2e45ce2 100644 --- a/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ The names of the nodes can be any valid hostname you choose. The names are set a Specify the first cluster node you configured as the MySQL primary via `mysql-server` and `mysql-master`. -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md index e199c06033..f3b1d55da6 100644 --- a/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md @@ -123,7 +123,6 @@ When you contact {% data variables.contact.enterprise_support %}, you can choose ### Дополнительная литература {% if enterpriseServerVersions contains currentVersion %} -- [Frequently asked questions about {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) - 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)"{% if enterpriseServerVersions contains currentVersion %} - "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} diff --git a/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index e917e17ebb..0fb01b0c5a 100644 --- a/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -63,7 +63,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac * 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 on your enterprise instance, 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/docker-build-push-action@v1 ``` diff --git a/translations/ru-RU/content/admin/overview/about-github-ae.md b/translations/ru-RU/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..d2656304e5 --- /dev/null +++ b/translations/ru-RU/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: About GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} is the most secure and compliant way to use {% data variables.product.prodname_dotcom %}.' +versions: + github-ae: '*' +--- + +### About {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase developer velocity, automate entire workflows, secure your code, and collaborate in developers’ favorite tool. + +{% data variables.product.prodname_ghe_managed %} provides your organization with all the power of [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). With {% data variables.product.prodname_ghe_managed %}, you can also meet security and compliance goals with a suite of features and certifications that put you in control. + +### A highly available and planet-scale cloud + +{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. + +### Data residency + +All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region. + +### Encryption on your terms + +All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." + +### Isolated accounts + +All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." + +### Restricted network access + +Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." + +### Commercial and government environments + +{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization. + +### Premium Plus support + +Premium Plus support is available for all {% data variables.product.prodname_ghe_managed %} customers, to ensure you have the fastest and most personal support experience. A dedicated Account Manager will work with you to help you get the most out of {% data variables.product.prodname_dotcom %}. Our support team will resolve issues any time of day, in the shortest possible time. + +### About billing for {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.about-billing %} For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." \ No newline at end of file diff --git a/translations/ru-RU/content/admin/overview/index.md b/translations/ru-RU/content/admin/overview/index.md index bc184ca3e3..32364e4aaf 100644 --- a/translations/ru-RU/content/admin/overview/index.md +++ b/translations/ru-RU/content/admin/overview/index.md @@ -12,6 +12,7 @@ For more information, or to purchase {% data variables.product.prodname_enterpri ### Table of Contents +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} diff --git a/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md b/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md index 078a1b54ae..fced028207 100644 --- a/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ If you'd like to renew or add user licenses to {% data variables.product.prodnam {% data reusables.enterprise-accounts.license-tab %} 12. Under "Quick links", click **Update license**. ![Update license link](/assets/images/enterprise/business-accounts/update-license-link.png) 13. To select your license, click **License file**, or drag your license file onto **License file**. ![Upload license file](/assets/images/enterprise/management-console/upload-license.png) -14. Click **Upload**. ![Begin upgrade](/assets/images/enterprise/management-console/begin-upload.png) +14. Click **Upload**. ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %} ### Viewing license usage @@ -70,3 +72,23 @@ You can download a JSON file from {% data variables.product.prodname_ghe_server {% data reusables.enterprise-accounts.license-tab %} 10. Under "Enterprise Server Instances", click **Add server usage**. ![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. Upload the JSON file you downloaded from {% data variables.product.prodname_ghe_server %}. ![Drag and drop or select a file to upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### Устранение проблем + +In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Restart the services for Git authentication and the HTTP server. + + {% warning %} + + **Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again. + +{% endif %} diff --git a/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md index 8a1cc8e8da..8a570dac4d 100644 --- a/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -58,7 +58,8 @@ Outside of the values that are provided to `stdin`, there are additional variabl | $GITHUB_VIA | Method used to create the ref.
    **Possible values:**
    - `auto-merge deployment api`
    - `blob edit`
    - `branch merge api`
    - `branches page delete button`
    - `git refs create api`
    - `git refs delete api`
    - `git refs update api`
    - `merge api`
    - `pull request branch delete button`
    - `pull request branch undo button`
    - `pull request merge api`
    - `pull request merge button`
    - `pull request revert button`
    - `releases delete button`
    - `stafftools branch restore`
    - `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | The number of push options that were sent by the client. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. | | $GIT_PUSH_OPTION_N | Where N is an integer starting at 0, this variable contains the push option string that was sent by the client. The first option that was sent is stored in GIT_PUSH_OPTION_0, the second option that was sent is stored in GIT_PUSH_OPTION_1, and so on. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. |{% endif %} +| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. +{% endif %} ### Setting permissions and pushing a pre-receive hook to {% data variables.product.prodname_ghe_server %} @@ -93,30 +94,30 @@ You can test a pre-receive hook script locally before you create or update it on 2. Create a file called `Dockerfile.dev` containing: - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository: + 3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository: - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 diff --git a/translations/ru-RU/content/admin/user-management/audited-actions.md b/translations/ru-RU/content/admin/user-management/audited-actions.md index d49ce13fdc..bca021c936 100644 --- a/translations/ru-RU/content/admin/user-management/audited-actions.md +++ b/translations/ru-RU/content/admin/user-management/audited-actions.md @@ -80,7 +80,7 @@ versions: | Name | Description | | ------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | -| `repo.archive` | 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.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. | @@ -89,7 +89,7 @@ versions: | `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.unarchive` | 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)."{% if enterpriseServerVersions contains currentVersion %} +| `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)."{% if enterpriseServerVersions contains currentVersion %} | `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)." | diff --git a/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md index 85e0aac11a..6999e4ae24 100644 --- a/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,11 +33,11 @@ If you don't have private mode enabled, the migration script will have no effect 1. Connect to the administrative shell. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)." 2. Navigate to the `/data/github/current` directory. - ``` + ```shell cd /data/github/current ``` 3. Run the migration command. - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` diff --git a/translations/ru-RU/content/admin/user-management/viewing-push-logs.md b/translations/ru-RU/content/admin/user-management/viewing-push-logs.md index 0b1a5270f2..b7c0a9041d 100644 --- a/translations/ru-RU/content/admin/user-management/viewing-push-logs.md +++ b/translations/ru-RU/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ Push log entries show: ### Viewing a repository's push logs +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. 1. Navigate to a repository. -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. In the upper-right corner of the repository's page, click +{% octicon "rocket" aria-label="The rocket ship" %}. + ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. In the left sidebar, click **Push Log**. ![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### Viewing a repository's push logs on the command-line -1. SSH into your appliance. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -2. In the appropriate Git repository, open the audit log file: +{% data reusables.enterprise_installation.ssh-into-instance %} +1. In the appropriate Git repository, open the audit log file: ```shell ghe-repo owner/repository -c "less audit_log" ``` diff --git a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 992a23ba0d..6e8a51401d 100644 --- a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ versions: ![Viewing a tag in the history](/assets/images/help/desktop/viewing-tags-in-history.png) 3. All tags associated with the commit are visible in that commit's metadata. ![Viewing a tag in the commit](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### Deleting tags + +{% note %} + +**Note**: You can only delete tags associated with commits that have not yet been pushed. + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md index b3c1436812..57212884e4 100644 --- a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -80,7 +80,7 @@ The `hook_attributes` object has the following key: This example uses a form on a web page with a button that triggers the `POST` request for a user account: -``` +```html Create a GitHub App Manifest:
    @@ -111,7 +111,7 @@ This example uses a form on a web page with a button that triggers the `POST` re ``` This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. -``` +```html Create a GitHub App Manifest:
    diff --git a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md index d2bbcdffea..8a297611c1 100644 --- a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -435,7 +435,7 @@ The code above gets the full repository name and the head SHA of the commit from ### Step 2.3. Running RuboCop -Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). +Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) for details and an example of the JSON format. +The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. Because this code stores the RuboCop results in a `@report` variable, it can safely remove the checkout of the repository. This code also parses the JSON so you can easily access the keys and values in your GitHub App using the `@output` variable. @@ -588,7 +588,7 @@ This code limits the total number of annotations to 50. But you can modify this When the `offense_count` is zero, the CI test is a `success`. If there are errors, this code sets the conclusion to `neutral` in order to prevent strictly enforcing errors from code linters. But you can change the conclusion to `failure` if you would like to ensure that the check suite fails when there are linting errors. -When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. +When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. This code also iterates through each error in the `offenses` array and collects the location of the offense and error message. After extracting the information needed, the code creates an annotation for each error and stores it in the `annotations` array. Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same. @@ -718,13 +718,13 @@ If the annotations are related to a file already included in the PR, the annotat If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button. -The RuboCop tool [offers](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. +The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set. In order to commit files, Git must know which [username](/articles/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. Например: -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 237d0f86bb..c47c9dc75c 100644 --- a/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ An _authorized_ OAuth App has access to all of the user's or organization owner' | Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. | | Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |{% endif %} +| {% data variables.product.prodname_github_app %}s can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_app %}s authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. +{% endif %} ### Requesting permission levels for resources diff --git a/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index c8b96a6040..79bf7b4c98 100644 --- a/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -89,7 +89,7 @@ Expiring user tokens are currently part of the user-to-server token expiration b 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 the beta for expiring user-to-server access tokens. -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", diff --git a/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md b/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md index 1ad70da5ab..aaf68b93b0 100644 --- a/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ To learn about publishing {% data variables.product.prodname_actions %} in {% da ### Приложения -Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." +Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. + +To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments. + +To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)." + +#### New to apps? If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." +#### GitHub Apps vs. OAuth Apps + {% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." -If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. - -### Publishing an app to {% data variables.product.prodname_marketplace %} +### Publishing an app to {% data variables.product.prodname_marketplace %} overview When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: @@ -38,13 +46,9 @@ When you have finished creating your app, you can share it with other users by p 1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." - 1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." - -An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." ### Seeing how your app is performing @@ -52,3 +56,7 @@ You can access metrics and transactions for your listing. Дополнитель - "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" - "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" + +### Contacting Support + +If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. diff --git a/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md b/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..b02ef692eb --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: About marketplace badges +intro: 'Learn about the badges that you may see for some apps and actions listings on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### For GitHub Apps + +Apps with the {% octicon "verified" aria-label="The verified badge" %}, are owned by an organization that has: +- Confirmed their domain +- Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization +- Required two-factor authentication for their organization. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + +![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +To learn how you can add this badge to your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### For GitHub actions + +Actions with the {% octicon "verified" aria-label="The verified badge" %}, or verified creator badge, indicate that {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization. + +![Verified creator badge for GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +For information on how to publish a GitHub action to {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." + +### About the previous verification process for apps + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**Note:** The new publisher verification process for apps replaces the previous process where individual apps were verified. The new publisher verification process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..0438d7a166 --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Applying for publisher verification for your organization +intro: 'To offer paid plans for your app or to include a marketplace badge in your app listing, you must complete the publisher verification process for your organization.' +versions: + free-pro-team: '*' +--- + +Publisher verification ensures that {% data variables.product.prodname_dotcom %} has a way to contact you, that you've enabled two-factor authentication for your organization, and that your organization's domain has been verified. + +Once your organization has been verified, you can publish paid plans for your app. For information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)." + +### Requesting publisher verification + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. In the left sidebar, click **Developer settings**. ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) +1. Under "Publisher Verification", complete the information in the checklist: + - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. + - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." + - Submit a verified domain. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + + ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) + +1. Click **Request Verification**. {% data variables.product.company_short %} will review your details and let you know once your publisher verification is complete. + +### Дополнительная литература + +For information about the process of publishing apps, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)." diff --git a/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 52c2c64dc9..033802f582 100644 --- a/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ Once you've created a {% data variables.product.prodname_marketplace %} draft li ### Submitting your app -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. ### Removing a {% data variables.product.prodname_marketplace %} listing diff --git a/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview.md b/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..5b8799f9d9 --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,8 @@ +--- +title: GitHub Marketplace Overview +intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/developers/github-marketplace/index.md b/translations/ru-RU/content/developers/github-marketplace/index.md index 51116f4b8e..d60a3b79ce 100644 --- a/translations/ru-RU/content/developers/github-marketplace/index.md +++ b/translations/ru-RU/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md index aed7c5d235..4bcccd4e00 100644 --- a/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ To protect your customers, we recommend that you also follow security best pract ### Requirements for paid apps -In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transfering ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." + +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." + +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: - {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. - {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. - All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. -- Publishing organizations must have a verified domain and must enable two-factor authentication. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." -When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} diff --git a/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 9ab919817d..52f91dd1ab 100644 --- a/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,11 +19,13 @@ versions: ### About setting pricing plans -If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." -{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." +To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." +If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. + +![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png) ### About saving pricing plans diff --git a/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md index b25c4580ae..6b338d826b 100644 --- a/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: Submitting your listing for publication -intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +intro: 'To finish your app listing submission, you can request a review by an onboarding expert.' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +Once your app listing meets the {% data variables.product.prodname_marketplace %} requirements, you can submit your app. For an overview of the app listing requirements, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +1. In the top left of the app listing page, click **Overview**. For information on finding your app listing page, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + ![Overview option for the marketplace draft listing](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) +2. To submit your your completed app listing, click **Request review**. -{% data reusables.marketplace.launch-with-free %} + !["Publish your app to Marketplace" checklist with submission button at the bottom](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -After you submit your listing for review, an onboarding expert will reach out to you with additional information. - -For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." - -### Prerequisites for publishing with verification - -Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." - -If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. - -### Transferring an app to an organization before you submit - -You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: - -1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" - -1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" +An onboarding expert will reach out to you with additional information. diff --git a/translations/ru-RU/content/developers/overview/secret-scanning.md b/translations/ru-RU/content/developers/overview/secret-scanning.md index bf0a60000a..e34d1eaca0 100644 --- a/translations/ru-RU/content/developers/overview/secret-scanning.md +++ b/translations/ru-RU/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: Secret scanning intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. Secret scanning happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our secret scanning. +{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}. When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice. -When a match of your secret format is found in a private repository configured for secret scanning, then repository admins are alerted and can view and manage the secret scanning results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from secret scanning](/github/administering-a-repository/managing-alerts-from-secret-scanning)". +When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." {% note %} -**Note:** Secret scanning for private repositories is currently in beta. +**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. {% endnote %} -This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the secret scanning program. +This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. -### The secret scanning process +### The {% data variables.product.prodname_secret_scanning %} process -##### How secret scanning works in a public repository +##### How {% data variables.product.prodname_secret_scanning %} works in a public repository -The following diagram summarizes the secret scanning process for public repositories, with any matches sent to a service provider's verify endpoint. +The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint. -![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "Secret scanning flow") +![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow") -### Joining the secret scanning program on {% data variables.product.prodname_dotcom %} +### Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %} 1. Contact {% data variables.product.prodname_dotcom %} to get the process started. 1. Identify the relevant secrets you want to scan for and create regular expressions to capture them. -1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the secret scanning message payload. +1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the {% data variables.product.prodname_secret_scanning %} message payload. 1. Implement signature verification in your secret alert service. 1. Implement secret revocation and user notification in your secret alert service. +1. Provide feedback for false positives (optional). #### Contact {% data variables.product.prodname_dotcom %} to get the process started -To get the enrollment process started, email secret-scanning@github.com. +To get the enrollment process started, email secret-scanning@github.com. -You will receive details on the secret scanning program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. +You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. #### Identify your secrets and create regular expressions -To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the secret scanning program: +To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program: * A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later. * A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives. * The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type. -Send this information to secret-scanning@github.com. +Send this information to secret-scanning@github.com. #### Create a secret alert service @@ -61,7 +62,7 @@ Create a public, internet accessible HTTP endpoint at the URL you provided to us ##### Example POST sent to your endpoint -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ You can retrieve the {% data variables.product.prodname_dotcom %} secret scannin Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set. **Sample message sent to verify endpoint** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -278,4 +279,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### Implement secret revocation and user notification in your secret alert service -For secret scanning in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. +For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. + +#### Provide feedback for false positives + +We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at secret-scanning@github.com. + +When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats. + +You can send us the raw token: + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256: + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +A few important points: +- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both. +- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm. +- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed. + +{% note %} + +**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at secret-scanning@github.com. + +{% endnote %} + diff --git a/translations/ru-RU/content/discussions/index.md b/translations/ru-RU/content/discussions/index.md index 66dca4f270..429f32ddbd 100644 --- a/translations/ru-RU/content/discussions/index.md +++ b/translations/ru-RU/content/discussions/index.md @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -43,7 +43,7 @@ versions: {% render 'discussions-community-card' for discussionsCommunityExamples as example %}
    {% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
    {% octicon "search" width="24" %}
    diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..72f6d0950d --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +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 + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +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 %} + +**Note:** As an instructor, you can't create {% data variables.product.prodname_dotcom %} accounts for your students. Students must create their own {% data variables.product.prodname_dotcom %} accounts. + +{% endnote %} diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..1dad791c70 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: About Campus Experts +intro: 'As a student, learn the skills you need to build your school''s technology community and a real-world portfolio, with {% data variables.product.prodname_dotcom %} Campus Experts training.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +Learn public speaking skills, technical writing, community leadership, and software development skills as a {% data variables.product.prodname_dotcom %} Campus Expert. For more information, see "[Campus Experts](https://education.github.com/students/experts)." diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..2e5d35535f --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: About GitHub Education for educators and researchers +intro: '{% data variables.product.prodname_education %} offers a variety of tools to help educators and researchers work more effectively inside and outside of the classroom.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} for educators + +With {% data variables.product.prodname_education %}'s tools and services for educators of all levels, you can: + - Use [{% data variables.product.prodname_classroom %}](https://classroom.github.com) to distribute code, give students feedback, and collect assignments on {% data variables.product.prodname_dotcom %}. + - Join our [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) to discuss current trends in technology education with your peers from around the world. + - Access and adapt our [open source lesson plans](https://education.github.community/t/open-source-lesson-plans/1591) for teaching Git and {% data variables.product.prodname_dotcom %}. + - [Request a {% data variables.product.prodname_dotcom %} swag bag](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) with educational materials and goodies for your students. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} for researchers + +With {% data variables.product.prodname_education %}'s tools and services for researchers, you can: + - Collaborate with others on your research work around the world on {% data variables.product.prodname_dotcom %}. + - [Learn](https://education.github.com/stories) how academic institutions around the world are using {% data variables.product.prodname_dotcom %} for their research. + {% data reusables.education.apply-for-team %} + +### Дополнительная литература + +- "[About {% data variables.product.prodname_education %} for students](/articles/about-github-education-for-students)" diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..4dafd10e0b --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: About GitHub Education for students +intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience. + +{% data reusables.education.about-github-education-link %} + +Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for the {% data variables.product.prodname_student_pack %}, which offers free access to tools and services used by professional developers. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +If you're a member of a FIRST robotics club, your mentor can apply for an educator discount so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[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)." + +### Дополнительная литература + +- "[About {% data variables.product.prodname_education %} for educators and researchers](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..c3a05c2f23 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Education +intro: '{% data variables.product.prodname_education %} offers a special free product for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community and agree to specific program requirements.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +If your school agrees to meet certain requirements, your secondary school, university, or bootcamp can get {% data variables.product.prodname_education %}, which offers the best of {% data variables.product.prodname_dotcom %} for free, including: +- {% data variables.product.prodname_ghe_cloud %} and/or {% data variables.product.prodname_ghe_server %} +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} +- Leadership development and technical training for students with the Campus Experts program + +For more information, see the [official {% data variables.product.prodname_education %}](https://education.github.com/partners/schools) page. + +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)." + +To learn more about training programs for student leaders and teachers, see "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" and "[Campus Advisors](https://education.github.com/teachers/advisors)." + +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_education %} 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/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[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/)." diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..c87df0a1b8 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: Apply for a student developer pack +intro: 'As a student, you can apply for the {% data variables.product.prodname_student_pack %}, which includes offers and benefits from {% data variables.product.prodname_dotcom %} partners.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Требования + +To be eligible for the {% data variables.product.prodname_student_pack %}, you must: +- Be currently enrolled in a degree or diploma granting course of study such as a high school, secondary school, college, university, homeschool, or similar educational institution +- Have a verifiable school-issued email address or upload documents that prove your current student status +- Have a [{% data variables.product.prodname_dotcom %} user account](/articles/signing-up-for-a-new-github-account) +- Be at least 13 years old + +Documents that prove your current student status include a picture of your school ID with current enrollment date, class schedule, transcript, and affiliation or enrollment verification letter. + +During your tenure as a student, you may be prompted to periodically re-verify your current academic status. + +{% note %} + +**Note:** You cannot transfer academic discounts from one account to another. If you have more than one account you want to apply the discount to, consider [merging](/articles/merging-multiple-user-accounts) your user accounts and [renaming](/articles/changing-your-github-username) the retained account if desired. + +{% endnote %} + +For information about renewing your {% data variables.product.prodname_student_pack %}, see "[Expiration and renewals](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)." + +### Applying for a {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. Under "Which best describes your academic status?", select **Student**. ![Select academic status](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Expiration and renewals + +Once your {% data variables.product.prodname_student_pack %} access expires, you may reapply if you're still eligible, although some of our partner offers cannot renew. Most of the timed offers from our partners start once you set them up. For more information, see the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) page. + +To see when your free access to the {% data variables.product.prodname_student_pack %} expires, visit your account's [billing settings](https://github.com/settings/billing). + +### Дополнительная литература + +- "[Why wasn't my application for a {% data variables.product.prodname_student_pack %} approved?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..23cf685691 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: Apply for an educator or researcher discount +intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### About educator and researcher discounts + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Applying for an educator or researcher discount + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Upgrading your organization + +After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade. + +#### Upgrading an existing organization + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Upgrading a new organization + +{% data reusables.education.upgrade-page %} +1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**. ![Create an organization button](/assets/images/help/education/create-org-button.png) +3. Read the information, then click **Create organization**. ![Create organization button](/assets/images/help/education/create-organization-button.png) +4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**. +5. Follow the prompts to create your organization. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Дополнительная литература + +- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..9dda1a2a4f --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Explore +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Table of Contents + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..c532b9a6e6 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub at your educational institution +intro: 'Maximize the benefits of using {% data variables.product.prodname_dotcom %} at your institution for your students, instructors, and IT staff with {% data variables.product.prodname_education %} and our various training programs for students and instructors.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..8512b9b548 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub for your schoolwork +intro: 'As a student, use {% data variables.product.prodname_dotcom %} to collaborate on your school projects and build real-world experience.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..3dc25db887 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: Use GitHub in your classroom and research +intro: 'As an educator or researcher, use {% data variables.product.prodname_dotcom %} to collaborate on your work in a classroom, student or research group, and more.' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..9a1c2a5047 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +title: Why wasn't my application for a student developer pack approved? +intro: 'Review common reasons that applications for the {% data variables.product.prodname_student_pack %} are not approved and learn tips for reapplying successfully.' +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear academic affiliation documents + +If the image you uploaded doesn't clearly identify your current academic status, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If your school issues email addresses prior to paid student enrollment, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain please ask your school IT staff to contact us. + +### Academic email address already used + +If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %} until that discount expires. + +{% note %} + +**Note:** It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/articles/github-terms-of-service/#3-account-requirements) to maintain more than one individual account. + +{% endnote %} + +If you have more than one personal user account, you must merge your accounts. To retain the discount, keep the account that was granted the discount. You can rename the retained account and keep your contribution history by adding all your email addresses to the retained account. + +Дополнительные сведения см. в: +- "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)" +- "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)" +- "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account)" + +### Ineligible student status + +You're ineligible for a {% data variables.product.prodname_student_pack %} if: +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- You're under 13 years old. + +Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools). + +### Дополнительная литература + +- "[How to get the GitHub Student Developer Pack without a student ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/)" on {% data variables.product.prodname_blog %} +- "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..10bef00cd7 --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: Why wasn't my application for an educator or researcher discount approved? +intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully. +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear proof of affiliation documents + +If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information. + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain, please ask your school IT staff to contact us. + +### Non-student applying for Student Developer Pack + +Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status. + +### Дополнительная литература + +- "[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)" diff --git a/translations/ru-RU/content/education/guides.md b/translations/ru-RU/content/education/guides.md index 0265b53633..50b347ee8e 100644 --- a/translations/ru-RU/content/education/guides.md +++ b/translations/ru-RU/content/education/guides.md @@ -12,8 +12,8 @@ Teachers, students, and researchers can use tools from {% data variables.product - [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) -- [Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) +- [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) ### Run a software development course with {% data variables.product.company_short %} @@ -32,7 +32,7 @@ Administer a classroom, assign and review work from your students, and teach the Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. - [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/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [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) @@ -41,5 +41,5 @@ Incorporate {% data variables.product.prodname_dotcom %} into your education, an 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) -- [About Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) -- [About Campus Advisors](/education/teach-and-learn-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/ru-RU/content/education/index.md b/translations/ru-RU/content/education/index.md index c3827df288..782c20b772 100644 --- a/translations/ru-RU/content/education/index.md +++ b/translations/ru-RU/content/education/index.md @@ -6,16 +6,16 @@ introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom @@ -41,5 +41,5 @@ versions: free-pro-team: '*' --- - + diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 86285be4fd..1eb11adb6f 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ For more information about teaching with {% data variables.product.prodname_clas ### Дополнительная литература -- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" +- "[Explore the benefits of teaching and learning with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index f0150b6df5..5993e0476f 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -140,6 +140,6 @@ You can see the teams that are working on or have submitted an assignment in the ### Дополнительная литература -- "[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)" +- "[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/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index a2a6085963..27229530de 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,8 +11,6 @@ You can use a template repository on {% data variables.product.product_name %} a To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." - ### Дополнительная литература - "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index 854d759837..a093ccc2f3 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -120,5 +120,5 @@ You can see whether a student has joined the classroom and accepted or submitted ### Дополнительная литература -- "[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)" +- "[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/ru-RU/content/education/manage-coursework-with-github-classroom/index.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/index.md index f5a8689fa7..7b1446bd31 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 6e051e9d2d..e5dbcf02c1 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -4,5 +4,8 @@ intro: Learn how to set up your classroom and assignments. mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/ru-RU/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index c50733a5fb..ae131dc20e 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -33,8 +33,8 @@ You can filter email notifications you receive for pushes to a repository. For m {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address. ![Email address textbox](/assets/images/help/settings/email_services_addresses.png) -6. If you operate your own server, you can verify the integrity of emails via the **Secret** token. This token is sent with the email as the `Approved` header. If the `Approved` header matches the token you sent, you can trust that the email is from {% data variables.product.product_name %}. ![Email secret textbox](/assets/images/help/settings/email_services_token.png) -7. Click **Save settings**. ![Save settings button](/assets/images/help/settings/save_notification_settings.png) +1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}. ![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png) +7. Click **Setup notifications**. ![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png) ### Дополнительная литература {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} diff --git a/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md index 998ba16e7a..829c7139fe 100644 --- a/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,7 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." diff --git a/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md b/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md index 0748625b6b..8dcd7efdd5 100644 --- a/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md @@ -4,6 +4,7 @@ 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: free-pro-team: '*' + enterprise-server: '>=3.1' --- ### About renaming branches @@ -19,3 +20,15 @@ If you rename a branch, {% data variables.product.prodname_dotcom %} will automa 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) + +### Updating a local clone after a branch name changes + +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. + +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 +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 83fc9b9b0a..a7784464e4 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: About authentication with SAML single sign-on -intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' +intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on @@ -9,6 +9,8 @@ versions: github-ae: '*' --- +### About authentication with SAML SSO + {% if currentVersion == "github-ae@latest" %} SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. @@ -31,13 +33,17 @@ If you have recently authenticated with your organization's SAML IdP in your bro {% data reusables.saml.you-must-periodically-authenticate %} -To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default. +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +To use a new or existing personal access token or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}. +### About {% data variables.product.prodname_oauth_apps %} and SAML SSO + +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO. + +After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). {% endif %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index d3bd28cdfe..f78f1ad73c 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ This article tells you how to make commits with sensitive data unreachable from #### Using the BFG -The [BFG Repo-Cleaner](http://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. For example, to remove your file with sensitive data and leave your latest commit untouched, run: +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. 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 @@ -46,7 +46,7 @@ After the sensitive data is removed, you must force push your changes to {% data $ git push --force ``` -See the [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. +See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. #### Using filter-branch diff --git a/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index 7b94a6fb5c..018516c319 100644 --- a/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ When you block a user, you can choose to block them indefinitely or for a specif {% tip %} -**Tip:** If you're blocking a user because of a heated conversation, consider [locking the conversation](/articles/locking-conversations) so only collaborators can comment. +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/github/building-a-strong-community/locking-conversations)." {% endtip %} At the time that you block a user from your organization: - The user stops watching your organization's repositories - The user's stars and issue assignments are removed from your repositories -- The user's forks of your organization's repositories are deleted - The user's votes on discussions or comments in your organization's repositories are deleted - The user is removed as a collaborator on your organization's repositories - The user's contributions to your organization's repositories are no longer counted as contributions for them diff --git a/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index c6446b198b..e89e172ff0 100644 --- a/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/ru-RU/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### About blocking users -You can block a user in your account settings or from the user's profile. {% data variables.product.prodname_dotcom %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can [choose to display a warning](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings) on any repositories with prior contributions from a blocked user. You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content. +You can block a user in your account settings or from the user's profile. {% data variables.product.prodname_dotcom %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see "[Blocking a user in your account settings](#blocking-a-user-in-your-account-settings)." You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content. {% tip %} -**Tip:** If you're blocking a user because of a heated conversation, consider [locking the conversation](/articles/locking-conversations) so only collaborators can comment. +**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/github/building-a-strong-community/locking-conversations)." {% endtip %} @@ -22,8 +22,6 @@ When you block a user: - The user stops watching and unpins your repositories - The user is not able to join any organizations you are an owner of - The user's stars and issue assignments are removed from your repositories -- The user's forks of your repositories are deleted -- You delete any forks of the user's repositories - The user's votes on discussions or comments in your repositories are deleted - The user is removed as a collaborator on your repositories - The user's contributions to your repositories are no longer counted as contributions for them diff --git a/translations/ru-RU/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/ru-RU/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 77d6f3b744..c1f25b6bde 100644 --- a/translations/ru-RU/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/ru-RU/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ You can add YAML frontmatter to each issue template to pre-fill the issue title, Here is example YAML front matter. -``` +```yaml --- name: Tracking issue about: Use this template for tracking new features. diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index 4174e52f52..4453c97203 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ For example, if you and another person both edited the file _styleguide.md_ on t 4. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts. 5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`. - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge: ```shell diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 85001ffa31..5b78492e23 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ Pre-receive hooks run tests on code pushed to a repository to ensure contributio If your push isn't accepted, you'll see an error message corresponding to the failed pre-receive hook. -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md index 3a21217379..80251eb493 100644 --- a/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,7 +19,7 @@ You can discover, browse, and install apps and actions created by others on {% d {% data reusables.actions.actions-not-verified %} -Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Building and listing a tool on {% data variables.product.prodname_marketplace %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index e94a6b5c8a..f2d7f5abc3 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ To integrate {% data variables.product.prodname_code_scanning %} into your CI sy In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -39,7 +39,7 @@ The {% data variables.product.prodname_codeql_runner %} automatically detects an To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are `cpp`, `csharp`, `go`, `java`, `javascript`, and `python`. -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -55,7 +55,7 @@ If you also are using a configuration file for custom settings, and you are also In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. -``` +```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 ``` @@ -68,7 +68,7 @@ The configuration file is a YAML file. It uses syntax similar to the workflow sy Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. -``` +```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml ``` @@ -84,7 +84,7 @@ For many common build systems, the {% data variables.product.prodname_codeql_run The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. -``` +```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 256db1838f..a0c5739aa3 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ You can set up {% data variables.product.prodname_code_scanning %} to check the 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### About alerts details 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 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. diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 4bccd25f77..0b377144c3 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -93,6 +93,8 @@ You can configure where the {% data variables.product.prodname_codeql_runner %} To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Basic example This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 80c5b6b9a4..5b6f36c087 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -40,6 +40,8 @@ If you upload a SARIF file without fingerprint data using the `/code-scanning/sa If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### Supported SARIF output file properties If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}. @@ -82,6 +84,8 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr #### `result` object +{% data reusables.code-scanning.upload-sarif-alert-limit %} + | Name | Description | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | @@ -89,7 +93,7 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | | `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | | `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | -| `locations[]` | **Required.** The set of locations where the result was detected. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | | `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | | `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | | `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 65f590f3d9..0cdbbed200 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -39,6 +39,8 @@ The `upload-sarif` action can be configured to run when the `push` and `schedule If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)." +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### Example workflow for SARIF files generated outside of a repository You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository. diff --git a/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md index b923b08a6c..bfffd2ff7e 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/ru-RU/content/github/getting-started-with-github/about-github-advanced-security.md @@ -10,7 +10,7 @@ versions: {% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." For information about permission requirements for actions related to security features, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." ### About {% data variables.product.prodname_advanced_security %} features diff --git a/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md index 6d38b73c1a..19943c46a0 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ Familiarize yourself with Git by visiting the [official Git project site](https: {% endif %} -Become better acquainted with {% data variables.product.product_name %} through our [bootcamp](/categories/bootcamp/) 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. +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, forks, and pull requests -Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/articles/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 quick references about the [command line](https://hub.github.com) as well as {% data variables.product.prodname_dotcom %} [checklists, cheat sheets, and more](https://services.github.com/on-demand/resources). +Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/articles/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/). #### Tune in @@ -41,9 +39,9 @@ Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides ch ### Training -#### Free classes +#### Free courses -{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://services.github.com/on-demand/) including {% data variables.product.prodname_dotcom %} 101: [Introduction](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %} 102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop), and {% data variables.product.prodname_dotcom %} 103: [Command Line](https://services.github.com/on-demand/github-cli). +{% 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 %}. #### {% data variables.product.prodname_dotcom %}'s web-based educational programs diff --git a/translations/ru-RU/content/github/getting-started-with-github/git-cheatsheet.md b/translations/ru-RU/content/github/getting-started-with-github/git-cheatsheet.md index 38afdb9b1a..3be24decfb 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/ru-RU/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -Learning all available Git commands at once can be a daunting task. Keep one of our [Git Cheat Sheets](https://services.github.com/on-demand/resources/cheatsheets/) nearby for reference. The Using Git Cheat Sheet is available in several languages. For more information, see the [resources page on the GitHub Services website](https://services.github.com/on-demand/resources/). +Learning all available Git commands at once can be a daunting task. Our cheat sheets provide a quick reference for the commands you'll use most often: see "[Git Cheat Sheets](https://training.github.com/)." The "Using Git" cheat sheet is available in several languages. In addition, take a look at our [Git and GitHub learning resources](/articles/git-and-github-learning-resources/) page that links to guides, videos and more. diff --git a/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md b/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md index becafddba7..4f14fddd35 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md +++ b/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md @@ -85,6 +85,7 @@ In addition to the features available with {% data variables.product.prodname_te - {% data variables.contact.enterprise_support %}. For more information, see "{% data variables.product.prodname_ghe_cloud %} support" and "{% data variables.product.prodname_ghe_cloud %} Addendum." - 50,000 {% data variables.product.prodname_actions %} minutes - 50GB {% data variables.product.prodname_registry %} storage +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime - The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." diff --git a/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md index d643b718b8..b25a360f4e 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -76,7 +76,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | control shift p or command shift p | Toggles between the **Write** and **Preview** comment tabs | | 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)."{% if currentVersion == "free-pro-team@latest" %} -| control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} +| control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/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)." | ### Issue and pull request lists @@ -111,7 +112,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | 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**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| 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 %} +| 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 %} ### Project boards diff --git a/translations/ru-RU/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/ru-RU/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 97371e6b4b..1da7e43bf8 100644 --- a/translations/ru-RU/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/ru-RU/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,7 +45,7 @@ versions: 7. At the top of your {% data variables.product.product_name %} repository'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](/articles/adding-a-remote) where your local repository will be pushed. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -83,7 +83,7 @@ versions: 7. At the top of your {% data variables.product.product_name %} repository'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](/articles/adding-a-remote) where your local repository will be pushed. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -121,7 +121,7 @@ versions: 7. At the top of your {% data variables.product.product_name %} repository'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](/articles/adding-a-remote) where your local repository will be pushed. ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md index 518caf7a83..8e4fb807ef 100644 --- a/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### About navigating code on {% data variables.product.prodname_dotcom %} -Navigating code functions use the open source library [`semantic`](https://github.com/github/semantic). The following languages are supported: +Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). The following languages are supported: - C# - CodeQL - Go diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index c8beaa69ea..46af6876b3 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -47,6 +47,8 @@ For a list of the ecosystems that {% data variables.product.product_name %} can 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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." + {% 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 %} diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index 317b266183..52de99845b 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ When you publish a security advisory, you notify your community about the securi Before you publish a security advisory, you can privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a security vulnerability](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)." +{% warning %} + +**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to. + +We recommend you take the following steps in these different situations: + +- If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready. +- If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication. +- If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue. + +{% endwarning %} + When you publish a draft advisory from a public repository, everyone is able to see: - The current version of the advisory data. diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 0ca44a070d..f86a309d4e 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -133,7 +133,8 @@ Email notifications from {% data variables.product.product_name %} contain the f | `To` field | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
    • `assign`: You were assigned to an issue or pull request.
    • `author`: You created an issue or pull request.
    • `comment`: You commented on an issue or pull request.
    • `manual`: There was an update to an issue or pull request you manually subscribed to.
    • `mention`: You were mentioned on an issue or pull request.
    • `push`: Someone committed to a pull request you're subscribed to.
    • `review_requested`: You or a team you're a member of was requested to review a pull request.
      • {% if currentVersion != "github-ae@latest" %}
    • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
      • {% endif %}
    • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
    • `subscribed`: There was an update in a repository you're watching.
    • `team_mention`: A team you belong to was mentioned on an issue or pull request.
    • `your_activity`: You opened, commented on, or closed an issue or pull request.
    | | `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} +| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} ### Choosing your notification settings diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/ru-RU/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 7b0010fe5f..9814328468 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: To transfer an open issue to another repository, you must have write permissions on the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." -You can only transfer issues between repositories owned by the same user or organization account.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} +You can only transfer issues between repositories owned by the same user or organization account. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)." diff --git a/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index 88539a2e5f..fbe45f4df0 100644 --- a/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,7 +25,8 @@ Email notifications from {% data variables.product.product_name %} contain the f | `To` field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. | | `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
    • `assign`: You were assigned to an issue or pull request.
    • `author`: You created an issue or pull request.
    • `comment`: You commented on an issue or pull request.
    • `manual`: There was an update to an issue or pull request you manually subscribed to.
    • `mention`: You were mentioned on an issue or pull request.
    • `push`: Someone committed to a pull request you're subscribed to.
    • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive security alerts for.
    • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
    • `subscribed`: There was an update in a repository you're watching.
    • `team_mention`: A team you belong to was mentioned on an issue or pull request.
    • `your_activity`: You opened, commented on, or closed an issue or pull request.
    | | `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} +| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% endif %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index d4ec220a4a..a2969d10c3 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ You can narrow your results to only include issues that are linked to a pull req | `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 %} +| `-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 %} ### Search by label diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index b8d96745e0..789fc5f9d1 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### Discounts for personal accounts -In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." +In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)." ### Discounts for schools and universities -Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[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)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/). +Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[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)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/). ### Discounts for nonprofits and libraries diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md index a3ee6b1216..a51df67c98 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..d2fefbaa88 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses +{% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/unpublishing-a-github-pages-site)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Click **Save**. + +### Дополнительная литература + +- "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)" diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 45c69b63f1..3cbdd65c14 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late {% if currentVersion == "free-pro-team@latest" %} -| Organization action | Owners | Members | Billing managers | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:-------:|:--------------------------------------------------:| -| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-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](/articles/about-your-organization-s-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 domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" 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** | | -| [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** | | -| See all organization members and teams | **X** | **X** | | -| @mention any visible team | **X** | **X** | | -| Can be made a *team maintainer* | **X** | **X** | | -| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | -| View and post public team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | **X** | | -| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | -| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/articles/managing-disruptive-comments)" for details) | **X** | | | -| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/managing-disruptive-comments/#hiding-a-comment)" for details) | **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** | | |{% if currentVersion == "free-pro-team@latest" %} -| 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** | | |{% endif %} -| 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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | -| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | -| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-teams/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** | | |{% if currentVersion != "github-ae@latest" %} -| 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** | | | -| 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** | | |{% endif %} -| [Manage the forking policy](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Limit activity in public repositories in an organization](/articles/limiting-interactions-in-your-organization) | **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 the default branch name (see "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" for details) | **X** | | | +| Organization action | Owners | Members | Billing managers | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:-------:|:----------------:| +| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-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](/articles/about-your-organization-s-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 domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" 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** | | +| [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** | | +| See all organization members and teams | **X** | **X** | | +| @mention any visible team | **X** | **X** | | +| Can be made a *team maintainer* | **X** | **X** | | +| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/articles/managing-disruptive-comments)" for details) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/managing-disruptive-comments/#hiding-a-comment)" for details) | **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](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/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](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" for details) | **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](/github/setting-up-and-managing-organizations-and-teams/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** | | | +| 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** | | | +| [Manage the forking policy](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limit activity in public repositories in an organization](/articles/limiting-interactions-in-your-organization) | **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 the default branch name (see "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/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](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" for details) | **X** | | | {% else %} -| 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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Configure code review assignments (see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} -| Add collaborators to **all repositories** | **X** | | -| Access the organization audit log | **X** | | -| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" 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** | -| 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](/articles/about-team-discussions)" for details) | **X** | **X** | | -| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | -| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/articles/managing-disruptive-comments) | **X** | | | -| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/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** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configure code review assignments (see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Add collaborators to **all repositories** | **X** | | +| Access the organization audit log | **X** | | +| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" 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** | +| 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](/articles/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/articles/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/articles/managing-disruptive-comments)) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/articles/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** | | |{% if currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} {% endif %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 1fcbaea87e..8c0f383a5c 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: Repository permission levels for an organization intro: 'You can customize access to each repository in your organization with granular permission levels, giving people access to the features and tasks they need.' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,95 +43,124 @@ In addition to managing organization-level settings, organization owners have ad {% endwarning %} ### Repository access for each permission level +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} -| Repository action | Read | Приоритизация | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Edit wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Report abusive or spammy content](/articles/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** |{% if currentVersion == "free-pro-team@latest" %} -| [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](/articles/requesting-a-pull-request-review) | | **X** | **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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/articles/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](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [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** |{% if currentVersion == "free-pro-team@latest" %} -| Limit [interactions in a repository](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [Enable the dependency graph](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) for a private repository | | | | | **X** | -| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** | -| [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** | -| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository, and also resolve, revoke or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [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 %} -| [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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [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 %} +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} +| +{% endif %} +| Repository action | Read | Приоритизация | Write | Maintain | Admin | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Edit wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Report abusive or spammy content](/articles/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** |{% if currentVersion == "free-pro-team@latest" %} +| [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](/articles/requesting-a-pull-request-review) | | **X** | **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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/articles/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](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [Delete packages](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [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** |{% if currentVersion == "free-pro-team@latest" %} +| Limit [interactions in a repository](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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** |{% if currentVersion == "free-pro-team@latest" %} +| 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** |{% if currentVersion == "free-pro-team@latest" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_advanced_security %} features. + +| Repository action | Read | Приоритизация | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** | +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [Enable the dependency graph](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) for a private repository | | | | | **X** | +| [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [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** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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** | +| [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 %} +{% endif %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index e43cb2c7d5..35098cf093 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -27,46 +27,46 @@ The audit log lists events triggered by activities that affect your organization 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 | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| [`учетная запись`](#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-category-actions) | Contains all activities related to your organization's billing. | -| [`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. | -| [`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)." | +| Category name | Description | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`учетная запись`](#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-category-actions) | Contains all activities related to your organization's billing. | +| [`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. | +| [`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. | -| [`перехватчик`](#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. | -| [`проблема`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} -| [`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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-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. | +| [`перехватчик`](#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. | +| [`проблема`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} +| [`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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} | [`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. |{% if currentVersion == "free-pro-team@latest" %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. |{% if currentVersion == "free-pro-team@latest" %} | [`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-category-actions) | Contains all activities related to project boards. | -| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. | +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | +| [`проект`](#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.{% if currentVersion == "free-pro-team@latest" %} -| [`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_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 %}{% if currentVersion != "github-ae@latest" %} -| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | -| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | -| [`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)." |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | +| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | | +| [`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)." |{% endif %}{% if currentVersion != "github-ae@latest" %} | [`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 %}{% if currentVersion == "free-pro-team@latest" %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [`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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [`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. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [`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-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. | +| [`команда`](#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. Например: @@ -128,7 +128,7 @@ To ensure a secure IP and maintain compliance for your organization, you can use {% data reusables.audit_log.audit-log-api-info %} {% if currentVersion == "free-pro-team@latest" %} -Note that you can't retrieve Git events using the GraphQL API. +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. @@ -141,7 +141,7 @@ For example, you can make a GraphQL request to see all the new organization memb {% note %} -**Note**: The audit log REST API is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. +**Note:** The audit log REST API is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. {% endnote %} @@ -250,7 +250,7 @@ An overview of some of the most common actions that are recorded as events in th {% note %} -**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. +**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a public beta for users of {% data variables.product.prodname_ghe_cloud %} only. For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. @@ -308,11 +308,11 @@ For more information about the audit log REST API, see "[Organizations](/rest/re {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} #### `members_can_create_pages` category actions -For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." | Действие | Description | |:----------- |:---------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -345,7 +345,8 @@ For more information, see "[Restricting publication of {% data variables.product | `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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | | `remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret.{% endif %}{% if currentVersion == "free-pro-team@latest"%} -| `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_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/){% if currentVersion != "github-ae@latest" %} 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{% if currentVersion != "github-ae@latest" %} 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 %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). |{% endif %}{% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index f8e9441c10..63c954cdef 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -20,12 +20,12 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. -| IdP | SAML | User provisioning | Team synchronization | -| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | User provisioning | Team synchronization | +| -------------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index 39d222f390..9b07ba7649 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -33,7 +33,9 @@ For more information about {% data variables.product.prodname_enterprise %}, see To use the {% data variables.product.prodname_enterprise %} portion of the license, the 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 %}. -Organization owners can invite new members to an organization by email address. The email address that the organization owner invites must match the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN), which should be an 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. +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. + +While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. For more information, see "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)." diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 89bf76b52c..2d0386ccce 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ GitHub will display your profile README on your profile page if all of the follo The generated README file is pre-populated with a template to give you some inspiration for your profile README. ![README file with pre-populated template](/assets/images/help/repository/personal-repository-readme-template.png) +For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](http://www.emoji-cheat-sheet.com/)." + ### Removing a profile README The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply: diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 1d674cf9b1..708e5d2d8c 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,20 +30,23 @@ The repository owner has full control of the repository. In addition to the acti | {% if currentVersion == "free-pro-team@latest" %}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)" |{% if currentVersion == "free-pro-team@latest" %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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)" |{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} | 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 %}{% if currentVersion == "free-pro-team@latest" %} -| Delete packages | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} +| Delete packages | "[Deleting a package](/github/managing-packages-with-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)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | Receive | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 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 %} +| 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 | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | @@ -64,8 +67,9 @@ Collaborators can also perform the following actions. | Действие | More information | |:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} -| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Managing disruptive comments](/github/building-a-strong-community/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)" | @@ -79,7 +83,8 @@ Collaborators can also perform the following actions. | Create and edit a wiki for the repository | "[About wikis](/github/building-a-strong-community/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)" |{% if currentVersion == "free-pro-team@latest" %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| 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)" | ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md index eca5d3f1b2..48115cd1c3 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -1,6 +1,6 @@ --- title: Types of emails GitHub sends -intro: 'There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, and marketing communications.' +intro: 'There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, customer research invitations, and marketing communications.' redirect_from: - /articles/types-of-emails-github-sends versions: @@ -25,6 +25,17 @@ You can also choose which type of email updates you'd like to receive on convers If you've upgraded to paid products or features, then you'll receive billing receipts at the account's primary email address. For more information, see "[Setting your billing email](/articles/setting-your-billing-email)." +### Customer research emails + +{% data variables.product.product_name %} occasionally seeks customers to participate in research sessions to help us build a better GitHub. These are conducted remotely, open to customers worldwide, and may include: + +- Feedback surveys +- Research interviews +- Usability testing sessions +- Previewing early prototypes or concepts + +These emails are infrequent and you can choose whether or not to participate. If you're interested in additional opportunities to participate in research sessions, you may add yourself to the GitHub Customer Research Panel. For more information, see "[GitHub Customer Experience Research](https://cxr.github.com)." + ### Marketing emails {% data variables.product.product_name %} occasionally sends these types of marketing emails: diff --git a/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md b/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md index 28803d95d9..9c532abadc 100644 --- a/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md @@ -55,7 +55,7 @@ Actions and any elements of the Actions service may not be used in violation of - 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 - any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used. -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, or restrictions in your ability to use GitHub Actions. +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. #### b. Packages Usage GitHub Packages is billed on a usage basis. The [Packages documentation](/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). diff --git a/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md b/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md index cc88aa48cb..9961ee2fbd 100644 --- a/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ru-RU/content/github/site-policy/github-and-trade-controls.md @@ -27,7 +27,9 @@ Users are responsible for ensuring that the content they develop and share on Gi GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid. -Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). +GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. Furthermore, GitHub.com may not be used for purposes prohibited under applicable export control laws, including prohibited end uses described in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). #### Корпоративный сервер GitHub @@ -41,13 +43,13 @@ GitHub Enterprise Server may not be sold to, exported, or re-exported to any cou #### On which countries and territories are U.S. government sanctions applied? -Crimea, Cuba, Iran, North Korea, and Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. +Crimea, Cuba, Iran, North Korea, and Syria. With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. #### How is GitHub ensuring that folks not living in and/or having professional links to the sanctioned countries and territories still have access or ability to appeal? In the rare instance that an account is affected unintentionally or in error, we have an appeal process to address such instances. -If an individual user or organization administrator believes that they have been flagged in error, then that user has the opportunity to appeal the flag by providing verification information to GitHub. If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction or otherwise restricted by U.S. economic sanctions, then the flag will be removed. Please see [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY) and [organizational account appeals request form](https://airtable.com/shrB2je5RBkqLEt5D). +If an individual user or organization administrator believes that they have been flagged in error, then that user has the opportunity to appeal the flag by providing verification information to GitHub. If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction for which we do not have a license or otherwise restricted by U.S. economic sanctions, then the flag will be removed. Please see [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY) and [organizational account appeals request form](https://airtable.com/shrB2je5RBkqLEt5D). #### Will traveling in these regions be impacted? @@ -55,13 +57,17 @@ Travel in these regions may impact your account status, but availability may be #### What is available and not available? -GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. However, Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. +GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba. -GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in U.S.-sanctioned regions. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. +GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in Syria and Crimea. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes. For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in sanctioned regions, such as Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. +GitHub will continue advocating with U.S. regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information. + +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. + +GitHub services are not available to developers located or otherwise resident in North Korea. #### How do you define these specific users? @@ -89,8 +95,13 @@ For example, a developer in Iran may sign up for a Free or Pro plan for their in Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub. -If GitHub determines that an individual falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. +If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed. #### Will Iranian GitHub users be able to use paid services under the license? Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. We accept all major credit cards, but third parties process payments for us, so payments are subject to the terms and conditions of our payment processors. Those third parties may include restrictions that block payments from Iran. + +#### Can you clarify availability of GitHub to Cuban developers? + +GitHub cloud services, both free and paid, are generally available to developers located in Cuba. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. diff --git a/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md index d54b593789..d2d929d2ca 100644 --- a/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **January 6, 2021** +Effective date: **January 29, 2021** GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -18,28 +18,26 @@ GitHub provides a great deal of transparency regarding how we use your data, how When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the [Privacy Statement](/articles/github-privacy-statement/)). -| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location | -|:-------------------- |:-------------------------------------------------- |:---------------------- |:------------------ | -| Automattic | Blogging service | United States | United States | -| AWS Amazon | Data hosting | United States | United States | -| Braintree (PayPal) | Subscription credit card payment processor | United States | United States | -| Clearbit | Marketing data enrichment service | United States | United States | -| Discourse | Community forum software provider | United States | United States | -| Eloqua | Marketing campaign automation | United States | United States | -| Google Apps | Internal company infrastructure | United States | United States | -| Google Analytics | Analytics and performance | United States | United States | -| MailChimp | Customer ticketing mail services provider | United States | United States | -| Mailgun | Transactional mail services provider | United States | United States | -| Microsoft | Microsoft Services | United States | United States | -| Monday.com | Team collaboration and project management platform | United States | Israel | -| Nexmo | SMS notification provider | United States | United States | -| Salesforce.com | Customer relations management | United States | United States | -| Sendgrid | Transactional mail services provider | United States | United States | -| Sentry.io | Application monitoring provider | United States | United States | -| Stripe | Payment provider | United States | United States | -| Twilio | SMS notification provider | United States | United States | -| Zendesk | Customer support ticketing system | United States | United States | -| Zuora | Corporate billing system | United States | United States | +| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location | +|:------------------------ |:--------------------------------------------------------------- |:---------------------- |:------------------ | +| Automattic | Blogging service | United States | United States | +| AWS Amazon | Data hosting | United States | United States | +| Braintree (PayPal) | Subscription credit card payment processor | United States | United States | +| Clearbit | Marketing data enrichment service | United States | United States | +| Discourse | Community forum software provider | United States | United States | +| Eloqua | Marketing campaign automation | United States | United States | +| Google Apps | Internal company infrastructure | United States | United States | +| MailChimp | Customer ticketing mail services provider | United States | United States | +| Mailgun | Transactional mail services provider | United States | United States | +| Microsoft | Microsoft Services | United States | United States | +| Monday.com | Team collaboration and project management platform | United States | Israel | +| Nexmo | SMS notification provider | United States | United States | +| Salesforce.com | Customer relations management | United States | United States | +| Sentry.io | Application monitoring provider | United States | United States | +| Stripe | Payment provider | United States | United States | +| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | United States | United States | +| Zendesk | Customer support ticketing system | United States | United States | +| Zuora | Corporate billing system | United States | United States | When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via {% data variables.contact.contact_privacy %}. @@ -47,7 +45,7 @@ When we bring on a new subprocessor who handles our Users' Personal Information, GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. -Since the number and names of cookies may change,the table below may be updated from time to time. +Since the number and names of cookies may change, the table below may be updated from time to time. | Service Provider | Cookie Name | Description | Expiration* | |:---------------- |:------------------------------------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------- | diff --git a/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 8f50e7c5d4..605e7bd22d 100644 --- a/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ Please note that the information available will vary from case to case. Some of ### Cost reimbursement -We reserve the right to seek reimbursement for administrative costs associated with responding to requests for information, as allowed by law. +Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. + +While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: + +- Initial search of up to 25 identifiers: Free +- Production of subscriber information/data for up to 5 accounts: Free +- Production of subscriber information/data for more than 5 accounts: $20 per account +- Secondary searches: $10 per search ### Data preservation diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 69bff67d4a..ddaa3f6ce3 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -22,7 +22,7 @@ You can sponsor an account on behalf of your user account to invest in projects - Developing brand awareness as an organization that values open source - Thanking open source developers for building libraries that complement the product your organization offers -You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." diff --git a/translations/ru-RU/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/ru-RU/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index a03eb6041a..3c9c5730ff 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/ru-RU/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ You can configure most Jekyll settings, such as your site's theme and plugins, b Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites. -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file. -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md b/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md index e4caf3934c..4dfe811416 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md +++ b/translations/ru-RU/content/github/working-with-github-pages/about-github-pages.md @@ -25,11 +25,15 @@ 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 %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Organization owners can disable the publication of -{% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." +{% 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](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} ### Types of {% data variables.product.prodname_pages %} sites @@ -40,6 +44,10 @@ To publish a user site, you must create a repository owned by your user account The source files for a project site are stored in the same repository as their project. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +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](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} 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 %} @@ -90,9 +98,9 @@ The default publishing source for a project site is the `gh-pages` branch. If th Project sites can also be published from the `master` branch or a `/docs` folder on the `master` branch. To publish your site from one of these sources, you must configure a different publishing source. 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)." - If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} 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 %} +If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} 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 %} - You cannot publish your project site from any other branch, even if the default branch is not `master` or `gh-pages`. +You cannot publish your project site from any other branch, even if the default branch is not `master` or `gh-pages`. {% endif %} diff --git a/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index dc00414587..d1d49acece 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ru-RU/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ You can see build failures (but not build warnings) for your site on {% data var You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit. 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. 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 diff --git a/translations/ru-RU/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ru-RU/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 3dca446bce..0d67085588 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/ru-RU/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ People with write permissions for a repository can add a theme to a {% data vari {% data reusables.pages.navigate-publishing-source %} 1. Create a new file called _/assets/css/style.scss_. 2. Add the following content to the top of the file: - ``` + ```scss --- --- diff --git a/translations/ru-RU/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ru-RU/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..b19019da27 --- /dev/null +++ b/translations/ru-RU/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. You can see your site's URL in the repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. To see your published site, under "{% data variables.product.prodname_pages %}", click your site's URL. ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/ru-RU/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ru-RU/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 69be0c6220..9d3107cdb0 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/ru-RU/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. In the file name field, type `404.html` or `404.md`. ![File name field](/assets/images/help/pages/404-file-name.png) 4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file: - ``` + ```yaml --- permalink: /404.html --- diff --git a/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 6570bb70f9..0d52fe4c3d 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,6 +11,8 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### Требования Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." @@ -95,7 +97,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md`. +You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. You can also add a theme to customize your site’s look and feel. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." diff --git a/translations/ru-RU/content/github/working-with-github-pages/index.md b/translations/ru-RU/content/github/working-with-github-pages/index.md index ce33893982..9e1df64984 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/index.md +++ b/translations/ru-RU/content/github/working-with-github-pages/index.md @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/ru-RU/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 3b2bb2212b..22f7e9a648 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/ru-RU/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -78,7 +78,7 @@ This error means that your code references a symlinked file that does not exist This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols. To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file: -``` +```yaml encoding: UTF-8 ``` diff --git a/translations/ru-RU/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ru-RU/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index b6c6be96fc..c3203ee9a9 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/ru-RU/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: Unpublishing a GitHub Pages site -intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available to {% if currentVersion == "free-pro-team@latest" %}the public{% else %}everyone using {% data variables.product.product_location %}{% endif %}.' +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index 9596f7de91..9a4310a8ff 100644 --- a/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -13,7 +13,7 @@ versions: 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 # The largest heading ## The second largest heading ###### The smallest heading @@ -37,7 +37,7 @@ You can indicate emphasis with bold, italic, or strikethrough text. You can quote text with a `>`. -``` +```markdown In the words of Abraham Lincoln: > Pardon my French @@ -55,7 +55,7 @@ In the words of Abraham Lincoln: You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted. -``` +```markdown Use `git status` to list all new or modified files that haven't yet been committed. ``` @@ -102,7 +102,7 @@ You can create an inline link by wrapping link text in brackets `[ ]`, and then You can make an unordered list by preceding one or more lines of text with `-` or `*`. -``` +```markdown - George Washington - John Adams - Thomas Jefferson @@ -112,7 +112,7 @@ You can make an unordered list by preceding one or more lines of text with `-` o To order your list, precede each line with a number. -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams @@ -126,7 +126,7 @@ You can create a nested list by indenting one or more list items below another i 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. First list item - First nested list item - Second nested list item @@ -140,7 +140,7 @@ To create a nested list in the comment editor on {% data variables.product.produ 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. First list item - First nested list item ``` @@ -149,7 +149,7 @@ In this example, you could add a nested list item under the list item `100. Firs You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven spaces (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. -``` +```markdown 100. First list item - First nested list item - Second nested list item diff --git a/translations/ru-RU/content/github/writing-on-github/organizing-information-with-tables.md b/translations/ru-RU/content/github/writing-on-github/organizing-information-with-tables.md index 3cb57b0c9c..ee2ef8440f 100644 --- a/translations/ru-RU/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/ru-RU/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: You can create tables with pipes `|` and hyphens `-`. Hyphens are used to create each column's header, while pipes separate each column. You must include a blank line before your table in order for it to correctly render. -``` +```markdown | First Header | Second Header | | ------------- | ------------- | @@ -27,7 +27,7 @@ The pipes on either end of the table are optional. Cells can vary in width and do not need to be perfectly aligned within columns. There must be at least three hyphens in each column of the header row. -``` +```markdown | Command | Description | | --- | --- | | git status | List all new or modified files | @@ -40,7 +40,7 @@ Cells can vary in width and do not need to be perfectly aligned within columns. You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table: -``` +```markdown | Command | Description | | --- | --- | | `git status` | List all *new or modified* files | @@ -51,7 +51,7 @@ You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as You can align text to the left, right, or center of a column by including colons `:` to the left, right, or on both sides of the hyphens within the header row. -``` +```markdown | Left-aligned | Center-aligned | Right-aligned | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ You can align text to the left, right, or center of a column by including colons To include a pipe `|` as content within your cell, use a `\` before the pipe: -``` +```markdown | Name | Character | | --- | --- | | Backtick | ` | diff --git a/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md b/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md index 017b674775..069cb73fd6 100644 --- a/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md +++ b/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This * Query `__schema` to list all types defined in the schema and get details about each: ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* Query `__type` to get details about any type: + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* Query `__type` to get details about any type: - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * You can also run an _introspection query_ of the schema via a `GET` request: diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index a4cfdabbeb..e3d8eea29a 100644 --- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -14,7 +14,7 @@ After you enable the link, each user can navigate directly from {% data variable 1. Connect to the administrative shell for {% data variables.product.prodname_ghe_server %}. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." 2. Run the following command. - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. Return to diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index 2a9ef548cf..5f9c30dc5a 100644 --- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - You must install dependencies on the application server. - [Docker](https://docs.docker.com/install/) 1.13.0+ - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/), available via apt for [Debian](https://packages.debian.org/search?keywords=netcat) and [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} diff --git a/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index 1a8ae48f06..aeaf4fb7af 100644 --- a/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ If you want to interact with multiple repositories, you can add each repository If your instance has subdomain isolation enabled: {% endif %} -``` +```xml "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` @@ -119,7 +119,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y {% data reusables.package_registry.authenticate-step %} 2. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -131,7 +131,7 @@ You can use gems from {% data variables.product.prodname_registry %} much like y 3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html). - ``` + ```ruby source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" diff --git a/translations/ru-RU/content/packages/index.md b/translations/ru-RU/content/packages/index.md index 1defcebba0..3d492fe556 100644 --- a/translations/ru-RU/content/packages/index.md +++ b/translations/ru-RU/content/packages/index.md @@ -12,13 +12,18 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: + - + title: ghcr.io maintenance mode on 2021-01-09 + date: '2021-01-08' + href: https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/ - title: ghcr.io container names redirect to the container page date: '2020-12-14' @@ -27,10 +32,6 @@ changelog: title: Filter for tagged and untagged containers date: '2020-12-14' href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: Packages container support is an opt-in beta - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md b/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md index dec649cf0b..f76f5eaefa 100644 --- a/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md +++ b/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md @@ -54,7 +54,7 @@ Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token. {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md index 6dc2e0240c..2d0f25d9c9 100644 --- a/translations/ru-RU/content/rest/overview/libraries.md +++ b/translations/ru-RU/content/rest/overview/libraries.md @@ -79,6 +79,10 @@ Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https: Library name | Repository |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +### Rust + +Library name | Repository |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) + ### Scala Library name | Repository |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) diff --git a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md index 5c0aec4d8b..221fa5c97d 100644 --- a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md @@ -107,7 +107,7 @@ _Поиск_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permission on "actions" - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Collaborators_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _Branches_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _Commit comments_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -836,6 +842,9 @@ _Teams_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ru-RU/data/glossaries/external.yml b/translations/ru-RU/data/glossaries/external.yml index aca717cf82..9e966271a0 100644 --- a/translations/ru-RU/data/glossaries/external.yml +++ b/translations/ru-RU/data/glossaries/external.yml @@ -35,7 +35,7 @@ - term: биография description: >- - Описание, созданное пользователем, которое находится в профиле: https://help.github.com/articles/adding-a-bio-to-your-profile/ + The user-generated description found on a profile: [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile) - term: расчётный период description: Период времени для вашего конкретного плана выставления счетов. @@ -156,7 +156,7 @@ - term: вклад description: >- - Конкретные действия в GitHub, в результате которых: – Добавляется квадрат к графику вклада пользователя: «[Что считается вкладом] (https://help.github.com/articles/viewing-contributions-on-your-profile/#what -counts-as-a-impact)» – Добавляются действия в историю действий пользователя в его профиле: «[Связанные с вкладом действия](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)» + Specific activities on GitHub that will: - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - term: участник description: >- @@ -229,7 +229,7 @@ Ветвь, используемая для тестирования новой функции или исправления проблемы, которая не находится в эксплуатации. Также называется тематической ветвью. - term: огороженный блок кода - description: 'Специальный блок кода можно создать в GitHub Flavored Markdown с помощью трех апострофов \`\`\` до и после блока кода. См. [example](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' + description: 'An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' - term: выбрать description: >- diff --git a/translations/ru-RU/data/learning-tracks/README.md b/translations/ru-RU/data/learning-tracks/README.md new file mode 100644 index 0000000000..ec0f70309e --- /dev/null +++ b/translations/ru-RU/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Learning Tracks (aka Learning Paths) + +Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. \ No newline at end of file diff --git a/translations/ru-RU/data/learning-tracks/actions.yml b/translations/ru-RU/data/learning-tracks/actions.yml index 678519414c..c825769cc8 100644 --- a/translations/ru-RU/data/learning-tracks/actions.yml +++ b/translations/ru-RU/data/learning-tracks/actions.yml @@ -31,6 +31,13 @@ continuous_deployment: - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Deploy to the cloud' + description: 'Learn how to use {% data variables.product.prodname_actions %} to build an application and deploy it to various cloud-based platforms.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine 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/translations/ru-RU/data/release-notes/2-20/18.yml b/translations/ru-RU/data/release-notes/2-20/18.yml index 3aab7ba337..f38b400522 100644 --- a/translations/ru-RU/data/release-notes/2-20/18.yml +++ b/translations/ru-RU/data/release-notes/2-20/18.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/9.yml b/translations/ru-RU/data/release-notes/2-21/9.yml index 46656c9e6b..a712183036 100644 --- a/translations/ru-RU/data/release-notes/2-21/9.yml +++ b/translations/ru-RU/data/release-notes/2-21/9.yml @@ -6,7 +6,7 @@ sections: - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-22/1.yml b/translations/ru-RU/data/release-notes/2-22/1.yml index fbd3988c3d..8edfa619f0 100644 --- a/translations/ru-RU/data/release-notes/2-22/1.yml +++ b/translations/ru-RU/data/release-notes/2-22/1.yml @@ -12,7 +12,7 @@ sections: - | Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | diff --git a/translations/ru-RU/data/release-notes/3-0/0-rc1.yml b/translations/ru-RU/data/release-notes/3-0/0-rc1.yml new file mode 100644 index 0000000000..b80e1e12ec --- /dev/null +++ b/translations/ru-RU/data/release-notes/3-0/0-rc1.yml @@ -0,0 +1,145 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. 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 variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: Изменения API + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - 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. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ru-RU/data/release-notes/3-0/0-rc2.yml b/translations/ru-RU/data/release-notes/3-0/0-rc2.yml new file mode 100644 index 0000000000..0e6ed5fd3f --- /dev/null +++ b/translations/ru-RU/data/release-notes/3-0/0-rc2.yml @@ -0,0 +1,25 @@ +--- +date: '2021-01-29' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +sections: + bugs: + - + heading: Fixes for known issues from Release Candidate 1 + notes: + - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. + - The "Mandatory message viewed" audit log event was not being saved. + - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' + - Removing yourself as an enterprise owner returned a 404. + - + heading: Fixes for other issues + notes: + - Issues with migrations and upgrades to 3.0.0 have been fixed. + - Backup Utilities versioning now works for release candidate versions. + - Generating a support bundle resulted in an error in the orchestrator logs. + - A large restore could result in Redis running out of memory. + - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. + - GitHub Actions can only be enabled if the required storage is also configured. + - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + known_issues: + - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/translations/ru-RU/data/reusables/actions/actions-not-verified.md b/translations/ru-RU/data/reusables/actions/actions-not-verified.md index 3107e5a79f..1eebaf90f5 100644 --- a/translations/ru-RU/data/reusables/actions/actions-not-verified.md +++ b/translations/ru-RU/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/ru-RU/data/reusables/code-scanning/not-available.md b/translations/ru-RU/data/reusables/code-scanning/not-available.md index 6531f5e1d0..0e4d2ac82f 100644 --- a/translations/ru-RU/data/reusables/code-scanning/not-available.md +++ b/translations/ru-RU/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." {% endnote %} {% endif %} diff --git a/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md new file mode 100644 index 0000000000..c5142332f6 --- /dev/null +++ b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + +{% endnote %} diff --git a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md index a217ad81ee..72facd7034 100644 --- a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md @@ -1,34 +1,35 @@ -The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. +The following table shows, for each package manager: +- The YAML value to use in the *dependabot.yml* file +- The supported versions of the package manager +- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +- Whether vendored dependencies are supported -| Package manager | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | -| -------------------------------- |:-----------------------------------------------------------------:|:---------:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir: `hex` | | | -| Elm: `elm` | **✓** | | -| git submodule: `gitsubmodule` | **✓** | | -| GitHub Actions: `github-actions` | **✓** | | -| Go modules: `gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +| Package manager | YAML value | Supported versions | Private repositories | Vendoring | +| --------------------------------- | ---------------- | ------------------------- |:--------------------:|:---------:| +| Средство увязки программ в пакеты | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1,v2 | **✓** | | +| Докер | `докер` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | +| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | +| Go modules | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | see (A) below | **✓** | | +| Maven | `maven` | see (B) below | **✓** | | +| npm | `npm` | v6 | **✓** | | +| NuGet | `nuget` | <= 4.8.
    see (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**Note**: {% data variables.product.prodname_dependabot %} also supports the following package managers: +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn` (v1 only) (specify `npm`) +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --`.gradle.kts` files, for Kotlin projects (specify `gradle`) - --`pipenv`, `pip-compile`, and `poetry` (specify `pip`) - -For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file. diff --git a/translations/ru-RU/data/reusables/desktop/delete-tag.md b/translations/ru-RU/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..40d455b880 --- /dev/null +++ b/translations/ru-RU/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Right-click the commit. + + - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) + - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/education/about-github-education-link.md b/translations/ru-RU/data/reusables/education/about-github-education-link.md index 67fa09ec6a..84a5d61418 100644 --- a/translations/ru-RU/data/reusables/education/about-github-education-link.md +++ b/translations/ru-RU/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_education %} school. For more information, see "[About {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)." +Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_education %} school. For more information, see "[About {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)." diff --git a/translations/ru-RU/data/reusables/education/apply-for-team.md b/translations/ru-RU/data/reusables/education/apply-for-team.md index 88fdff7f90..272564d3d5 100644 --- a/translations/ru-RU/data/reusables/education/apply-for-team.md +++ b/translations/ru-RU/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." +- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[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)." diff --git a/translations/ru-RU/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/ru-RU/data/reusables/enterprise_installation/ssh-into-instance.md index 9dcd8e90d3..c5e62f493a 100644 --- a/translations/ru-RU/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/ru-RU/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. SSH into {% data variables.product.product_location %}. +1. SSH into {% data variables.product.product_location %}. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/ru-RU/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/ru-RU/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 77593c5d20..0cdbb1f880 100644 --- a/translations/ru-RU/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/ru-RU/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. To import the archived migration data to a {% data variables.product.prodname_ghe_server %} instance, see "[Importing migration data to {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)". +1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[Preparing to migrate data to your enterprise](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/ru-RU/data/reusables/gated-features/private-pages.md b/translations/ru-RU/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..3fb7f0a3a7 --- /dev/null +++ b/translations/ru-RU/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/ru-RU/data/reusables/github-actions/actions-billing.md b/translations/ru-RU/data/reusables/github-actions/actions-billing.md index 4e12946e9b..249d4b339a 100644 --- a/translations/ru-RU/data/reusables/github-actions/actions-billing.md +++ b/translations/ru-RU/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. +{% data variables.product.prodname_actions %} usage is free for both public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md b/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md index 2ad79b4182..33c7bd3120 100644 --- a/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ The starter workflow template sets up the `PATH` to contain OpenJDK 8 for the x6 For example, to use version 9.0.4 of the JDK for the x64 platform, you can use the `setup-java` action and configure the `java-version` and `architecture` parameters to `'9.0.4'` and `x64`. {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md b/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md index e6db4f8803..0114ffafd7 100644 --- a/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a private preview only. Any users or organizations that are already using this runner can continue using it, but we're not accepting any further users or organizations at this time. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/ru-RU/data/reusables/marketplace/launch-with-free.md b/translations/ru-RU/data/reusables/marketplace/launch-with-free.md index 2151c241cc..15e06d0cb2 100644 --- a/translations/ru-RU/data/reusables/marketplace/launch-with-free.md +++ b/translations/ru-RU/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/ru-RU/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/ru-RU/data/reusables/organizations/reseller-ask-to-become-billing-manager.md index 30ba905e4b..29620e32dc 100644 --- a/translations/ru-RU/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ b/translations/ru-RU/data/reusables/organizations/reseller-ask-to-become-billing-manager.md @@ -1 +1 @@ -If you're not a billing manger for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). +If you're not a billing manager for the organization, ask your client to have an *owner* of the organization [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/ru-RU/data/reusables/pages/about-private-publishing.md b/translations/ru-RU/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..f1f13531ce --- /dev/null +++ b/translations/ru-RU/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. diff --git a/translations/ru-RU/data/reusables/pages/choose-visibility.md b/translations/ru-RU/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..bd794a90d7 --- /dev/null +++ b/translations/ru-RU/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..fc98787aaa --- /dev/null +++ b/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md b/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md index 7620878dbc..04d4ddeb1c 100644 --- a/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %}. If you have sensitive data in your site's repository, you may want to remove it before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/ru-RU/data/reusables/pages/twenty-minutes-to-publish.md b/translations/ru-RU/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..3e7a2fd5a4 --- /dev/null +++ b/translations/ru-RU/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**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 %}. If your don't see your changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/pages/visit-site.md b/translations/ru-RU/data/reusables/pages/visit-site.md index 7ef1b070cb..6e94a9bfd9 100644 --- a/translations/ru-RU/data/reusables/pages/visit-site.md +++ b/translations/ru-RU/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% note %} - **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 %}. If your don't see your changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/ru-RU/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/ru-RU/data/reusables/pull_requests/rebase_and_merge_summary.md index 284f536db2..cd6ca3efd4 100644 --- a/translations/ru-RU/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/ru-RU/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ When you select the **Rebase and merge** option on a pull request on {% data var To rebase and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow rebase merging](/articles/configuring-commit-rebasing-for-pull-requests/). -The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [the "Git rebase" chapter from the _Pro Git_ book](https://git-scm.com/docs/git-rebase). +The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). For a visual representation of `git rebase`, see [The "Git Branching - Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/ru-RU/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/ru-RU/data/reusables/saml/about-user-provisioning-enterprise-account.md index 918dab289f..c83e052fa8 100644 --- a/translations/ru-RU/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/ru-RU/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -If you use Okta as your IdP, you can use SCIM to manage organization membership in your enterprise account. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. +If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP. diff --git a/translations/ru-RU/data/reusables/user-settings/edit_marketplace_listing.md b/translations/ru-RU/data/reusables/user-settings/edit_marketplace_listing.md index 7b7bf4115a..306c505acf 100644 --- a/translations/ru-RU/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/ru-RU/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. Scroll down to the Marketplace section and click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app. For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md index db0159f7a9..4b0bdb1926 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Клавиша | Тип | Description | -| ---------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `действие` | `строка` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| Клавиша | Тип | Description | +| ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `действие` | `строка` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml index 2f05bd3a73..f29f6523f2 100644 --- a/translations/ru-RU/data/ui.yml +++ b/translations/ru-RU/data/ui.yml @@ -138,9 +138,19 @@ product_sublanding: learning_paths: Learning paths learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. more_guides: more guides - guideTypes: + load_more: Load more guides + all_guides: All Guides + no_result: Sorry, there is no guide that match your filter. + filters: + type: Тип + topic: Topic + all: All + guide_types: overview: Обзор quick_start: Quickstart tutorial: Руководство how_to: How-to guide reference: Reference +learning_track_nav: + prevGuide: Previous guide + nextGuide: Next guide diff --git a/translations/ru-RU/data/variables/product.yml b/translations/ru-RU/data/variables/product.yml index 8ad45b6cef..ab42a8fb10 100644 --- a/translations/ru-RU/data/variables/product.yml +++ b/translations/ru-RU/data/variables/product.yml @@ -61,6 +61,7 @@ prodname_marketplace: 'Магазин GitHub' prodname_github_app: 'Приложение GitHub' prodname_github_apps: 'GitHub Apps' prodname_oauth_app: 'Приложение OAuth' +prodname_oauth_apps: 'OAuth Apps' #API and developer docs prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs' prodname_support_forum_with_url: '[GitHub API Development and Support Forum](https://github.community/c/github-api-development-and-support/37)' diff --git a/translations/zh-CN/content/actions/creating-actions/about-actions.md b/translations/zh-CN/content/actions/creating-actions/about-actions.md index 4acf4eba0b..c01f9a5441 100644 --- a/translations/zh-CN/content/actions/creating-actions/about-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/about-actions.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - '操作开发' + - '基础' --- {% data reusables.actions.enterprise-beta %} @@ -124,7 +127,7 @@ steps: #### 使用提交的 SHA 进行发行版管理 -每个 Git 提交都会收到一个计算出来的 SHA 值，该值是唯一且不可更改的。 您操作的用户可能更喜欢依赖提交的 SHA 值，因为此方法会比指定可删除或移动的标记更可靠。 但是，这意味着用户将不会收到对该操作所做的进一步更新。 使用提交的完整 SHA 值而不是缩写值可以帮助防止人们使用缩写相同的恶意提交。 +每个 Git 提交都会收到一个计算出来的 SHA 值，该值是唯一且不可更改的。 您操作的用户可能更喜欢依赖提交的 SHA 值，因为此方法会比指定可删除或移动的标记更可靠。 但是，这意味着用户将不会收到对该操作所做的进一步更新。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}您必须使用提交的完整 SHA 值，而不是缩写值。{% else %}使用提交的完整 SHA 值而不使用缩写值有助于防止他人使用相同缩写值进行恶意提交。{% endif %} ```yaml steps: diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md index 6b2ccdaf0d..e3e843c6d8 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md @@ -1,11 +1,13 @@ --- title: 创建组合运行步骤操作 -intro: '在本指南中，您将学习如何构建组合运行步骤操作。' +intro: 在本指南中，您将学习如何构建组合运行步骤操作。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 操作开发 --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md index 11dd9b3de1..89729e512c 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md @@ -1,6 +1,6 @@ --- title: 创建 Docker 容器操作 -intro: '本指南向您展示构建 Docker 容器操作所需的最少步骤。' +intro: 本指南向您展示构建 Docker 容器操作所需的最少步骤。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 操作开发 + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -39,7 +42,7 @@ type: 'tutorial' 1. 从您的终端，将目录更改为新仓库。 - ```shell + ```shell{:copy} cd hello-world-docker-action ``` @@ -48,7 +51,7 @@ type: 'tutorial' 在新的 `hello-world-docker-action` 目录中，创建新的 `Dockerfile` 文件。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。 **Dockerfile** -```dockerfile +```dockerfile{:copy} # 运行代码的容器图像 FROM alpine:3.10 @@ -65,7 +68,7 @@ ENTRYPOINT ["/entrypoint.sh"] {% raw %} **action.yml** -```yaml +```yaml{:copy} # action.yml name: 'Hello World' description: 'Greet someone and record the time' @@ -97,25 +100,24 @@ runs: 1. 在 `hello-world-docker-action` 目录中创建一个新的 `entrypoint.sh` 文件。 -1. 使 `entrypoint.sh` 文件可执行： - - ```shell - chmod +x entrypoint.sh - ``` - 1. 将以下代码添加到 `entrypoint.sh` 文件。 **entrypoint.sh** - ```shell + ```shell{:copy} #!/bin/sh -l echo "Hello $1" time=$(date) echo "::set-output name=time::$time" ``` - 如果 `entrypoint.sh` 执行没有任何错误，则操作的状态设置为 `success`。 您还可以在操作的代码中显式设置退出代码以提供操作的状态。 更多信息请参阅“[设置操作的退出代码](/actions/creating-actions/setting-exit-codes-for-actions)”。 +1. Make your `entrypoint.sh` file executable by running the following command on your system. + + ```shell{:copy} + $ chmod +x entrypoint.sh + ``` + ### 创建自述文件 要让人们了解如何使用您的操作，您可以创建自述文件。 自述文件在您计划公开分享操作时最有用，但也是提醒您或您的团队如何使用该操作的绝佳方式。 @@ -130,7 +132,7 @@ runs: - 如何在工作流程中使用操作的示例。 **README.md** -```markdown +```markdown{:copy} # Hello world docker action This action prints "Hello World" or "Hello" + the name of a person to greet to the log. @@ -160,7 +162,7 @@ with: 最佳做法是同时为操作版本添加版本标记。 有关对操作进行版本管理的详细信息，请参阅“[关于操作](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)”。 -```shell +```shell{:copy} git add action.yml entrypoint.sh Dockerfile README.md git commit -m "My first action is ready" git tag -a -m "My first action release" v1 @@ -175,11 +177,11 @@ git push --follow-tags #### 使用公共操作的示例 -以下工作流程代码使用公共 [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) 仓库中完整的 hello world 操作。 将以下工作流程示例代码复制到 `.github/workflows/main.yml` 文件中，但将 `actions/hello-world-docker-action` 替换为您的仓库和操作名称。 您还可以将 `who-to-greet` 输入替换为您的名称。 +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. 将以下工作流程示例代码复制到 `.github/workflows/main.yml` 文件中，但将 `actions/hello-world-docker-action` 替换为您的仓库和操作名称。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: @@ -200,11 +202,11 @@ jobs: #### 使用私有操作的示例 -将以下示例工作流程代码复制到操作仓库中的 `.github/workflows/main.yml` 文件。 您还可以将 `who-to-greet` 输入替换为您的名称。 +将以下示例工作流程代码复制到操作仓库中的 `.github/workflows/main.yml` 文件。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% if currentVersion == "free-pro-team@latest" %}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** -```yaml +```yaml{:copy} on: [push] jobs: diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md index 6ac8369ec2..96320aca48 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md @@ -1,6 +1,6 @@ --- title: 创建 JavaScript 操作 -intro: '在本指南中，您将了解如何使用操作工具包构建 JavaScript 操作。' +intro: 在本指南中，您将了解如何使用操作工具包构建 JavaScript 操作。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-javascript-action @@ -10,7 +10,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 操作开发 + - JavaScript --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 56f10a66f2..dae207c3af 100644 --- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -1,14 +1,14 @@ --- title: Dockerfile 对 GitHub 操作的支持 shortTitle: Docker -intro: '为 Docker 容器创建 `Dockerfile` 时， 您应该知道一些 Docker 指令如何与 GitHub 操作及操作的元数据文件交互。' +intro: 为 Docker 容器创建 `Dockerfile` 时， 您应该知道一些 Docker 指令如何与 GitHub 操作及操作的元数据文件交互。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/building-actions/dockerfile-support-for-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} @@ -48,20 +48,21 @@ Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPO 如果您配置容器使用 _exec_ 形式的 `ENTRYPOINT` 指令，在操作元数据文件中配置的 `args` 不会在命令 shell 中运行。 如果操作的 `args` 包含环境变量，不会替换该变量。 例如，使用以下 _exec_ 格式将不会打印存储在 `$GITHUB_SHA` 中的值， 但会打印 `"$GITHUB_SHA"`。 -``` +```dockerfile ENTRYPOINT ["echo $GITHUB_SHA"] ``` 如果要替代变量，则可使用 _shell_ 形式或直接执行 shell。 例如，使用以下 _exec_ 格式可以执行 shell 来打印存储在 `GITHUB_SHA` 环境变量中的值。 -``` +```dockerfile ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] ``` 要将操作元数据文件中定义的 `args` 提供到在 `ENTRYPOINT` 中使用 _exec_ 形式的 Docker 容器，建议创建一个可从 `ENTRYPOINT` 指令调用、名为 `entrypoint.sh` 的 shell 脚本。 ##### 示例 *Dockerfile* -``` + +```dockerfile # Container image that runs your code FROM debian:9.5-slim diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 6ac4b60449..012a99fb50 100644 --- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -11,7 +11,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'reference' +type: reference --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md index 424a4937fa..cd0e3d73fc 100644 --- a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -41,11 +41,13 @@ try { 如果要创建 Docker 容器操作，您可以在 `entrypoint.sh` 脚本中设置失败退出代码。 例如： +{% raw %} ``` if ; then echo "Game over!" exit 1 fi ``` +{% endraw %} 更多信息请参阅“[创建 Docker 容器操作](/articles/creating-a-docker-container-action)”。 diff --git a/translations/zh-CN/content/actions/guides/about-continuous-integration.md b/translations/zh-CN/content/actions/guides/about-continuous-integration.md index 8c7e5af352..fbf3b5f568 100644 --- a/translations/zh-CN/content/actions/guides/about-continuous-integration.md +++ b/translations/zh-CN/content/actions/guides/about-continuous-integration.md @@ -11,6 +11,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md b/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md index 3222d22887..9b8fd10d10 100644 --- a/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md +++ b/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - '打包' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/about-service-containers.md b/translations/zh-CN/content/actions/guides/about-service-containers.md index 42e392f307..620d285786 100644 --- a/translations/zh-CN/content/actions/guides/about-service-containers.md +++ b/translations/zh-CN/content/actions/guides/about-service-containers.md @@ -9,6 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +50,7 @@ type: 'overview' 本例在作业 `container-job` 中创建一个名为 `redis` 的服务。 本例中的 Docker 主机是 `node:10.18-jessie` 容器。 {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -89,7 +92,7 @@ jobs: 此示例映射服务容器 `redis` 端口 6379 到 Docker 主机端口 6379。 {% raw %} -```yaml +```yaml{:copy} name: Redis Service Example on: push diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md index efb60e9ae4..b93b6f796b 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Java + - Ant --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ type: 'tutorial' 您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。 {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ jobs: 如果使用不同的命令来构建项目，或者想要运行不同的目标，则可以指定这些命令。 例如，您可能想要运行在 _build-ci.xml_ 文件中配置的 `jar` 目标。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -97,7 +101,7 @@ steps: Ant 通常会在 `build/jar` 目录中创建 JAR、EAR 或 WAR 等输出文件。 您可以使用 `upload-artifact` 操作上传该目录的内容。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md index 8168fcc6cc..6a1aa4d265 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ type: 'tutorial' 您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。 {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ jobs: 如果使用不同的命令来构建项目，或者想要使用不同的任务，则可以指定这些命令。 例如，您可能想要运行在 _ci.gradle_ 文件中配置的 `package` 任务。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: 使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以缓存依赖项以加速工作流程运行。 运行成功后，您的本地 Gradle 缓存将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程包仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -105,15 +109,24 @@ steps: - name: Cache Gradle packages uses: actions/cache@v2 with: - path: ~/.gradle/caches - key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }} - restore-keys: ${{ runner.os }}-gradle + path: | + ~/.gradle/caches + ~/.gradle/wrapper + key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }} + restore-keys: | + ${{ runner.os }}-gradle- - name: Build with Gradle run: ./gradlew build + - name: Cleanup Gradle Cache + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. + # Restoring these files from a GitHub Actions cache might cause problems for future builds. + run: | + rm -f ~/.gradle/caches/modules-2/modules-2.lock + rm -f ~/.gradle/caches/modules-2/gc.properties ``` {% endraw %} -此工作流程将保存本地 Gradle 缓存的内容，位于运行器主目录的 `.gradle/caches` 目录中。 缓存密钥将是 gradle 构建文件的哈希内容，因此更改它们将使缓存失效。 +This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache. ### 将工作流数据打包为构件 @@ -122,7 +135,7 @@ steps: Gradle 通常会在 `build/libs` 目录中创建 JAR、EAR 或 WAR 等输出文件。 您可以使用 `upload-artifact` 操作上传该目录的内容。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md index 6b49fe092c..2f0394281e 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +42,7 @@ type: 'tutorial' 您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。 {% raw %} -```yaml +```yaml{:copy} name: Java CI on: [push] @@ -79,7 +83,7 @@ jobs: 如果使用不同的命令来构建项目，或者想要使用不同的目标，则可以指定这些命令。 例如，您可能想要运行在 _pom-ci.xml_ 文件中配置的 `verify` 目标。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 @@ -95,7 +99,7 @@ steps: 使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以缓存依赖项以加速工作流程运行。 运行成功后，您的本地 Maven 仓库将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程 Maven 仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 1.8 @@ -122,7 +126,7 @@ steps: Maven 通常会在 `target` 目录中创建 JAR、EAR 或 WAR 等输出文件。 要将这些项目上传为构件，可以将它们复制到包含要上传的构件的新目录中。 例如，您可以创建一个名为 `staging` 的目录。 然后您可以使用 `upload-artifact` 操作上传该目录的内容。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-net.md b/translations/zh-CN/content/actions/guides/building-and-testing-net.md index 8ddd5accf2..0920b18bcf 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-net.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: - name: Setup .NET Core SDK ${{ matrix.dotnet }} uses: actions/setup-dotnet@v1.6.0 with: - dotnet-version: {{ matrix.dotnet-version }} + dotnet-version: ${{ matrix.dotnet-version }} - name: Install dependencies run: dotnet restore - name: Build @@ -58,7 +58,7 @@ jobs: To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job. -The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-dotnet). +The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action. #### Using multiple .NET versions diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md index 6769fa2be6..bf4620724a 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md @@ -8,7 +8,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Node + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -77,7 +81,7 @@ The template includes a matrix strategy that builds and tests your code with fou 每个作业都可以使用 `matrix` 上下文访问矩阵 `node-version` 阵列中定义的值。 `setup-node` 操作使用上下文作为 `node-version` 输入。 `setup-node` 操作在构建和测试代码之前使用不同的 Node.js 版本配置每个作业。 有关矩阵策略和上下文的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)”和“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 {% raw %} -```yaml +```yaml{:copy} strategy: matrix: node-version: [10.x, 12.x, 14.x, 15.x] @@ -93,7 +97,7 @@ steps: 您也可以构建和测试精确的 Node.js 版本。 -```yaml +```yaml{:copy} strategy: matrix: node-version: [8.16.2, 10.17.0] @@ -102,7 +106,7 @@ strategy: 或者，您也可以使用单个版本的 Node.js 构建和测试。 {% raw %} -```yaml +```yaml{:copy} name: Node.js CI on: [push] @@ -136,7 +140,7 @@ jobs: 此示例安装 *package.json* 文件中定义的依赖项。 更多信息请参阅 [`npm install`](https://docs.npmjs.com/cli/install)。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -150,7 +154,7 @@ steps: 使用 `npm ci` 将版本安装到 *package-lock.json* 或 *npm-shrinkwraw.json* 文件并阻止更新锁定文件。 使用 `npm ci` 通常比运行 `npm install` 更快。 更多信息请参阅 [`npm ci`](https://docs.npmjs.com/cli/ci.html) 和“[引入 `npm ci` 以进行更快、更可靠的构建](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)”。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -166,7 +170,7 @@ steps: 此示例安装 *package.json* 文件中定义的依赖项。 更多信息请参阅 [`yarn install`](https://yarnpkg.com/en/docs/cli/install)。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -179,7 +183,7 @@ steps: 或者，您可以传递 `--frozen-lockfile` 来安装 *yarn.lock* 文件中的版本，并阻止更新 *yarn.lock* 文件。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -201,7 +205,7 @@ steps: 在安装依赖项之前，使用 `setup-node` 操作创建 *.npmrc* 文件。 该操作有两个输入参数。 `node-version` 参数设置 Node.js 版本，`registry-url` 参数设置默认注册表。 如果包注册表使用作用域，您必须使用 `scope` 参数。 更多信息请参阅 [`npm-scope`](https://docs.npmjs.com/misc/scope)。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -220,7 +224,7 @@ steps: 上面的示例创建了一个包含以下内容的 *.npmrc* 文件： -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true @@ -231,7 +235,7 @@ always-auth=true 使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以使用唯一密钥缓存依赖项， 并在使用`缓存`操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js @@ -256,7 +260,7 @@ steps: 您可以使用与本地相同的命令来构建和测试代码。 例如，如果您运行 `npm run build` 来运行 *package.json* 文件中定义的构建步骤，运行 `npm test` 来运行测试套件，则要在工作流程文件中添加以下命令。 -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Use Node.js diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md b/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md index 15f0d06c90..ad04d114c3 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md @@ -7,7 +7,10 @@ versions: enterprise-server: '>=2.22' authors: - potatoqualitee -type: 'tutorial' +type: tutorial +topics: + - CI + - Powershell --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-python.md b/translations/zh-CN/content/actions/guides/building-and-testing-python.md index 3aae7481b7..8c8e0bac7f 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-python.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-python.md @@ -7,7 +7,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Python --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ type: 'tutorial' 要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。 {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -100,7 +103,7 @@ jobs: {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -138,7 +141,7 @@ jobs: {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -176,7 +179,7 @@ jobs: {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -223,7 +226,7 @@ jobs: {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -246,7 +249,7 @@ steps: {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -273,7 +276,7 @@ Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 您需 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Setup Python @@ -318,7 +321,7 @@ steps: {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -348,7 +351,7 @@ steps: {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up Python @@ -377,7 +380,7 @@ steps: {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -417,7 +420,7 @@ jobs: {% raw %} -```yaml +```yaml{:copy} name: Python package on: [push] @@ -430,26 +433,26 @@ jobs: matrix: python-version: [2.7, 3.5, 3.6, 3.7, 3.8] - steps: - - uses: actions/checkout@v2 - - name: Setup Python # Set Python version - uses: actions/setup-python@v2 - with: - python-version: ${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v2 - with: - name: pytest-results-${{ matrix.python-version }} - path: junit/test-results-${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: ${{ always() }} + steps: + - uses: actions/checkout@v2 + - name: Setup Python # Set Python version + uses: actions/setup-python@v2 + with: + python-version: ${{ matrix.python-version }} + # Install pip and pytest + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install pytest + - name: Test with pytest + run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml + - name: Upload pytest test results + uses: actions/upload-artifact@v2 + with: + name: pytest-results-${{ matrix.python-version }} + path: junit/test-results-${{ matrix.python-version }}.xml + # Use always() to always run this step to publish test results when there are test failures + if: ${{ always() }} ``` @@ -466,7 +469,7 @@ jobs: {% raw %} -```yaml +```yaml{:copy} name: Upload Python Package on: diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md index b451a5b836..ea1db762fb 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md @@ -5,7 +5,10 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CI + - Ruby --- {% data reusables.actions.enterprise-beta %} @@ -46,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -63,7 +63,7 @@ jobs: 指定 Ruby 版本的最简单方法是使用 Ruby 组织在 GitHub 上提供的 `ruby/setup-ruby` 操作。 该操作将任何受支持的 Ruby 版本添加到工作流程中运行的每个作业的 `PATH`。 更多信息请参阅 [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)。 -使用 Ruby 的 `ruby/setup-ruby` 操作或 GitHub 的 `actions/setup-ruby` 操作是 Python 与 GitHub Actions 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Ruby 行为一致。 +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. `setup-ruby` 操作采用 Ruby 版本作为输入，并在运行器上配置该版本。 @@ -119,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies @@ -316,4 +313,3 @@ jobs: GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}" ``` {% endraw %} - diff --git a/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md index f1be01c12b..485a5038b8 100644 --- a/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md @@ -1,7 +1,7 @@ --- title: 缓存依赖项以加快工作流程 shortTitle: 缓存依赖项 -intro: '为了使工作流程更快、更高效，可以为依赖项及其他经常重复使用的文件创建和使用缓存。' +intro: 为了使工作流程更快、更高效，可以为依赖项及其他经常重复使用的文件创建和使用缓存。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows @@ -9,7 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: 'tutorial' +type: tutorial +topics: + - 工作流程 --- ### 关于缓存工作流程依赖项 @@ -68,7 +70,7 @@ type: 'tutorial' 此示例在 `package-lock.json` 文件中的包更改时，或运行器的操作系统更改时，创建一个新的缓存。 缓存键使用上下文和表达式生成一个键值，其中包括运行器的操作系统和 `package-lock.json` 文件的 SHA-256 哈希。 {% raw %} -```yaml +```yaml{:copy} name: Caching with npm on: push @@ -124,14 +126,14 @@ jobs: 使用表达式创建 `key` 允许您在依赖项更改时自动创建新缓存。 例如，您可以使用计算 npm `package-lock.json` 文件哈希的表达式创建 `key`。 {% raw %} -``` +```yaml npm-${{ hashFiles('package-lock.json') }} ``` {% endraw %} {% data variables.product.prodname_dotcom %} 评估表达式 `hash "package-lock.json"` 以派生最终 `key`。 -``` +```yaml npm-d5ea0750 ``` @@ -144,7 +146,7 @@ npm-d5ea0750 #### 使用多个恢复键值的示例 {% raw %} -``` +```yaml restore-keys: | npm-foobar-${{ hashFiles('package-lock.json') }} npm-foobar- @@ -155,7 +157,7 @@ restore-keys: | 运行器将评估表达式，解析为以下 `restore-keys`： {% raw %} -``` +```yaml restore-keys: | npm-foobar-d5ea0750 npm-foobar- diff --git a/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md index 3400e60c58..36c82f6c74 100644 --- a/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ type: 'tutorial' {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL service example on: push @@ -94,7 +97,7 @@ jobs: {% data reusables.github-actions.postgres-label-description %} -```yaml +```yaml{:copy} jobs: # Label of the container job container-job: @@ -124,7 +127,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -159,7 +162,7 @@ PostgreSQL 文档中的服务的主机名是您在工作流程中配置的标签 {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: PostgreSQL Service Example on: push @@ -220,7 +223,7 @@ jobs: 工作流程将 PostgreSQL 服务容器上的端口 5432 映射到 Docker 主机。 有关 `ports` 关键字的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。 -```yaml +```yaml{:copy} jobs: # Label of the runner job runner-job: @@ -251,7 +254,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -287,7 +290,7 @@ steps: {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const { Client } = require('pg'); const pgclient = new Client({ diff --git a/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md b/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md index 0480c25436..892c28bd91 100644 --- a/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md +++ b/translations/zh-CN/content/actions/guides/creating-redis-service-containers.md @@ -9,7 +9,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Containers + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -37,7 +40,7 @@ type: 'tutorial' {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis container example on: push @@ -91,7 +94,7 @@ jobs: {% data reusables.github-actions.redis-label-description %} -```yaml +```yaml{:copy} jobs: # Label of the container job container-job: @@ -118,7 +121,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -152,7 +155,7 @@ Redis 服务的主机名是您在工作流程中配置的标签，本例中为 ` {% data reusables.github-actions.copy-workflow-file %} {% raw %} -```yaml +```yaml{:copy} name: Redis runner example on: push @@ -210,7 +213,7 @@ jobs: 工作流程将 Redis 服务容器上的端口 6379 映射到 Docker 主机。 有关 `ports` 关键字的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。 -```yaml +```yaml{:copy} jobs: # Label of the runner job runner-job: @@ -238,7 +241,7 @@ jobs: {% data reusables.github-actions.service-template-steps %} -```yaml +```yaml{:copy} steps: # Downloads a copy of the code in your repository before running CI tests - name: Check out repository code @@ -274,7 +277,7 @@ steps: {% data reusables.github-actions.service-container-add-script %} -```javascript +```javascript{:copy} const redis = require("redis"); // Creates a new Redis client diff --git a/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md index 5a2ccfd00d..4f147b3a36 100644 --- a/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Amazon ECS --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md b/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md index 49de2609ea..ceabf77aa0 100644 --- a/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Azure App Service --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md index f192717241..dfa7c9b2a5 100644 --- a/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -5,6 +5,11 @@ product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: tutorial +topics: + - CD + - Containers + - Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/index.md b/translations/zh-CN/content/actions/guides/index.md index 045f218b3c..5b73023a7c 100644 --- a/translations/zh-CN/content/actions/guides/index.md +++ b/translations/zh-CN/content/actions/guides/index.md @@ -21,9 +21,46 @@ learningTracks: - getting_started - continuous_integration - continuous_deployment + - deploy_to_the_cloud - hosting_your_own_runners - create_actions layout: product-sublanding +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/guides/setting-up-continuous-integration-using-workflow-templates + - /actions/guides/building-and-testing-python + - /actions/guides/building-and-testing-nodejs + - /actions/guides/about-packaging-with-github-actions + - /actions/guides/publishing-docker-images + - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/guides/about-continuous-integration + - /actions/guides/building-and-testing-powershell + - /actions/guides/building-and-testing-ruby + - /actions/guides/building-and-testing-java-with-maven + - /actions/guides/building-and-testing-java-with-gradle + - /actions/guides/building-and-testing-java-with-ant + - /actions/guides/publishing-nodejs-packages + - /actions/guides/publishing-java-packages-with-maven + - /actions/guides/publishing-java-packages-with-gradle + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/guides/about-service-containers + - /actions/guides/creating-redis-service-containers + - /actions/guides/creating-postgresql-service-containers + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/creating-actions/about-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-run-steps-action + - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/learn-github-actions/migrating-from-circleci-to-github-actions + - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions + - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions --- diff --git a/translations/zh-CN/content/actions/guides/publishing-docker-images.md b/translations/zh-CN/content/actions/guides/publishing-docker-images.md index e6aeab7fd8..e37eaec9fd 100644 --- a/translations/zh-CN/content/actions/guides/publishing-docker-images.md +++ b/translations/zh-CN/content/actions/guides/publishing-docker-images.md @@ -7,7 +7,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 打包 + - Publishing + - Docker --- {% data reusables.actions.enterprise-beta %} @@ -55,7 +59,7 @@ Docker Hub 需要的 `build-push-action` 选项包括： * `repository`：`DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY` 格式的 Docker Hub 仓库。 {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -93,7 +97,7 @@ jobs: * `repository`：必须以 `OWNER/REPOSITORY/IMAGE_NAME` 格式设置。 例如，对于 `http://github.com/octo-org/octo-repo` 上名为 `octo-image` stored on {% data variables.product.prodname_dotcom %} 的映像，`repository` 选项应设置为 `octo-org/octo-repo/octo-image`。 {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: @@ -126,7 +130,7 @@ jobs: 下面的示例工作流程使用前面章节中的 `build-push-action` 步骤（“[发布映像到 Docker Hub](#publishing-images-to-docker-hub)”和“[发布映像到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”）来创建同时推送到两个注册表的单一工作流程。 {% raw %} -```yaml +```yaml{:copy} name: Publish Docker image on: release: diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md index 65372e3185..9905cf3a8d 100644 --- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 打包 + - Publishing + - Java + - Gradle --- {% data reusables.actions.enterprise-beta %} @@ -43,7 +48,7 @@ _build.gradle_ 文件还包含 Gradle 将在其中部署包的分发管理仓库 您可以在 _build.gradle_ 文件的发布块中定义指向包仓库的新 Maven 仓库。 例如，如果您通过 OSSRH 托管项目部署到 Maven 中心仓库，则 _build.gradle_ 可以指定名称为 `"OSSRH"` 的仓库。 {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -67,7 +72,7 @@ publishing { {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -105,7 +110,7 @@ jobs: 例如，如果组织名为“octocat”且仓库名为“hello-world”，则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。 {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -126,7 +131,7 @@ publishing { 使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -162,7 +167,7 @@ jobs: 如果组织名为“octocat”且仓库名为“hello-world”，则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。 {% raw %} -```groovy +```groovy{:copy} publishing { ... @@ -191,7 +196,7 @@ publishing { 使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md index 8190da631d..f35b52091a 100644 --- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md @@ -7,7 +7,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 打包 + - Publishing + - Java + - Maven --- {% data reusables.actions.enterprise-beta %} @@ -47,7 +52,7 @@ _pom.xml_ 文件还包含 Maven 将在其中部署包的分配管理仓库的配 例如，如果您通过 OSSRH 托管项目部署到 Maven 中心仓库，则 _pom.xml_ 可以指定 `id` 为 `ossrh` 的分发管理仓库。 {% raw %} -```xml +```xml{:copy} ... @@ -67,7 +72,7 @@ _pom.xml_ 文件还包含 Maven 将在其中部署包的分配管理仓库的配 {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository on: release: @@ -113,7 +118,7 @@ jobs: 例如，如果组织名为“octocat”且仓库名为“hello-world”，则 _pom.xml_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。 {% raw %} -```xml +```xml{:copy} ... @@ -130,7 +135,7 @@ jobs: 通过此配置，您可以创建一个工作流程，以使用自动生成的 _settings.xml_ 将包发布到 {% data variables.product.prodname_registry %}。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to GitHub Packages on: release: @@ -165,7 +170,7 @@ jobs: 确保 _pom.xml_ 文件包含用于 {% data variables.product.prodname_dotcom %} 仓库和 Maven 中心仓库提供商的分发管理仓库。 例如，如果您通过 OSSRH 托管项目部署到中心仓库，您可能想通过将 `id` 设置为 `ossrh` 在分发管理仓库中指定它，并且想通过将 `id` 设置为 `github` 在分发管理仓库中指定 {% data variables.product.prodname_registry %}。 {% raw %} -```yaml +```yaml{:copy} name: Publish package to the Maven Central Repository and GitHub Packages on: release: diff --git a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md index cc9d59aa49..255bb3493c 100644 --- a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md @@ -8,7 +8,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 打包 + - Publishing + - Node + - JavaScript --- {% data reusables.actions.enterprise-beta %} @@ -54,7 +59,7 @@ type: 'tutorial' 此示例将 `NPM_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -78,7 +83,7 @@ jobs: 在上面的示例中，`setup-node` 操作在运行器上创建一个包含以下内容的 *.npmrc* 文件： -``` +```ini //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -114,7 +119,7 @@ If you want to publish your package to a different repository, you must use a pe 此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -140,7 +145,7 @@ jobs: `setup-node` 操作在运行器上创建 *.npmrc* 文件。 使用 `scope` 输入到 `setup-node` 操作时，*.npmrc* 文件包含作用域前缀。 默认情况下，`setup-node` 操作在 *.npmrc* 文件中将作用域设置为包含该工作流程文件的帐户。 -``` +```ini //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true @@ -151,7 +156,7 @@ always-auth=true 如果您使用 Yarn 包管理器，可以使用 Yarn 安装和发布包。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: @@ -161,13 +166,13 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - # 设置 .npmrc 文件以发布到 npm + # Setup .npmrc file to publish to npm - uses: actions/setup-node@v1 with: node-version: '12.x' registry-url: 'https://registry.npmjs.org' - # 默认为拥有工作流程文件的用户或组织 - scope: '@octocat' + # Defaults to the user or organization that owns the workflow file + scope: '@octocat' - run: yarn - run: yarn publish env: @@ -196,7 +201,7 @@ jobs: 此工作流程将调用 `setup-node` 操作两次。 每当 `setup-node` 操作运行时，都会覆盖 *.npmrc* 文件。 *.npmrc* 文件引用的令牌允许您对 `NODE_AUTH_TOKEN` 环境变量中的包注册表执行验证的操作。 工作流程在 `npm publish` 命令每次运行时设置 `NODE_AUTH_TOKEN` 环境变量，先通过令牌发布到 npm (`NPM_TOKEN`)，然后通过令牌发布到 {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`)。 {% raw %} -```yaml +```yaml{:copy} name: Node.js Package on: release: diff --git a/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 018c15b188..d8e5422e7c 100644 --- a/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,7 +11,10 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 工作流程 + - CI --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md index e0ff4a2380..8793363e67 100644 --- a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -11,7 +11,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - 工作流程 --- {% data reusables.actions.enterprise-beta %} @@ -79,7 +81,7 @@ type: 'tutorial' 工作流程上传 `dist` 目录中的生产构件，但不包括任何 markdown 文件。 它还会上传 `code-coverage.html` 报告作为另一个构件。 -```yaml +```yaml{:copy} name: Node CI on: [push] @@ -114,7 +116,7 @@ jobs: 您可以为工作流程创建的单个构件自定义保留期。 使用工作流程创建新构件时，可以同时使用 `retention-days` with the `upload-artifact` 操作。 此示例演示如何为名为 `my-artifact` 的构件设置 5 天的自定义保留期： -``` +```yaml{:copy} - name: 'Upload Artifact' uses: actions/upload-artifact@v2 with: @@ -183,7 +185,7 @@ jobs: 此工作流程示例中执行的完整数学运算为 `(3 + 7) x 9 = 90`。 -```yaml +```yaml{:copy} name: Share data between jobs on: [push] diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index 33b7eb195e..10e4c9a3bf 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial defaultPlatform: linux --- diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 3b1d6efe96..0eb1538a0d 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 816985f81b..1df50312f8 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 176352878c..0a4a0f5265 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -6,7 +6,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +38,7 @@ type: 'tutorial' 示例 _.env_ 代理配置如下所示： -``` +```ini https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index aaa0c1ce6c..bcbbe12492 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -4,7 +4,7 @@ intro: 您可以使用标签以基于其特性来组织自托管运行器。 versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 57d2d2fdd0..0ce4af807a 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -1,13 +1,13 @@ --- title: 在工作流程中使用自托管的运行器 -intro: '要在工作流程中使用自托管的运行器，您可以使用标签为作业指定运行器类型。' +intro: 要在工作流程中使用自托管的运行器，您可以使用标签为作业指定运行器类型。 redirect_from: - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial --- {% data reusables.actions.enterprise-beta %} @@ -64,8 +64,11 @@ runs-on: [self-hosted, linux, x64, gpu] ### 自托管运行器的路由优先级 -如果同时使用仓库级和组织级的运行器，{% data variables.product.prodname_dotcom %} 在将作业传送给自托管运行器时遵循优先顺序： +When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels: -1. 作业的 `runs-on` 标签经过处理。 {% data variables.product.prodname_dotcom %} 然后会尝试查找符合标签要求的运行器： -2. 作业将发送到与作业标签匹配的仓库级运行器。 如果没有仓库级运行程序可用（忙、脱机或没有匹配的标签）： -3. 作业将发送到与作业标签匹配的组织级运行器。 如果没有组织级运行器可用，作业请求将失败并出错。 +1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}. +2. The job is then sent to the first matching runner that is online and idle. + - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners. + - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners. + - If there are no matching runners at any level, the job will fail. + - If the job remains queued for more than 24 hours, the job will fail. diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md index f35c7690d4..f3bad193b7 100644 --- a/translations/zh-CN/content/actions/index.md +++ b/translations/zh-CN/content/actions/index.md @@ -10,21 +10,22 @@ featuredLinks: - /actions/learn-github-actions - /actions/guides/about-continuous-integration - /actions/guides/about-packaging-with-github-actions - gettingStarted: - - /actions/managing-workflow-runs - - /actions/hosting-your-own-runners guideCards: - /actions/guides/setting-up-continuous-integration-using-workflow-templates - /actions/guides/publishing-nodejs-packages - /actions/guides/building-and-testing-powershell popular: - /actions/reference/workflow-syntax-for-github-actions - - /actions/reference/events-that-trigger-workflows - /actions/learn-github-actions + - /actions/reference/events-that-trigger-workflows - /actions/reference/context-and-expression-syntax-for-github-actions - - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables + - /actions/reference/encrypted-secrets changelog: + - + title: Environments, environment protection rules and environment secrets (beta) + date: '2020-12-15' + href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ - title: 工作流程可视化 date: '2020-12-08' @@ -33,10 +34,6 @@ changelog: title: 11 月 16 日删除 set-env 和 add-path 命令 date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Ubuntu-latest 工作流程将使用 Ubuntu-20.04 - date: '2020-10-29' - href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ @@ -73,7 +70,7 @@ versions: {% render 'code-example-card' for actionsCodeExamples as example %}
    - +
    {% octicon "search" width="24" %}
    diff --git a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md index 41e016dccf..a88ec0f932 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - '基础' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md index 8b339cffc8..bbc2eead71 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - '基础' --- {% data reusables.actions.enterprise-beta %} @@ -68,7 +70,7 @@ steps: #### 使用 SHA -如果需要更可靠的版本控制，应使用与操作版本关联的 SHA 值。 SHA 是不可变的，因此比标记或分支更可靠。 但是，此方法意味着您不会自动接收操作的更新，包括重要的 Bug 修复和安全更新。 此示例针对操作的 SHA： +如果需要更可靠的版本控制，应使用与操作版本关联的 SHA 值。 SHA 是不可变的，因此比标记或分支更可靠。 但是，此方法意味着您不会自动接收操作的更新，包括重要的 Bug 修复和安全更新。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA: ```yaml steps: diff --git a/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md index b1b91b2cbe..83461cc14f 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -10,6 +10,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - '基础' --- {% data reusables.actions.enterprise-beta %} @@ -147,7 +149,7 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 ``` - 将 check-bats-version 作业中运行的所有步骤组合在一起。 此部分下嵌套的每行都是一个单独的操作。 + 将 check-bats-version 作业中运行的所有步骤组合在一起。 Each item nested under this section is a separate action or shell command. @@ -180,7 +182,7 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 ``` - run 关键字指示作业在运行器上执行命令。 在这种情况下，使用 npm 来安装 bats 软件测试包。 + run 关键字指示作业在运行器上执行命令。 在这种情况下，使用 npm 来安装 bats 软件测试包。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md index 366d26f478..0ac1aed42f 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md @@ -6,6 +6,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'how_to' +topics: + - '工作流程' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index 3f299ece38..dc16f928e8 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -1,12 +1,17 @@ --- title: 从 CircleCI 迁移到 GitHub 操作 -intro: 'GitHub 操作和 CircleCI 在配置上具有若干相似之处，这使得迁移到 GitHub 操作相对简单。' +intro: GitHub 操作和 CircleCI 在配置上具有若干相似之处，这使得迁移到 GitHub 操作相对简单。 redirect_from: - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - CircleCI + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -258,24 +263,24 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem - - name: Setup file system permissions - run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - - uses: actions/checkout@v2 - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake + # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. + # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions + run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp + - uses: actions/checkout@v2 + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake ``` {% endraw %} @@ -412,35 +417,35 @@ jobs: POSTGRES_DB: ruby25 POSTGRES_PASSWORD: "" ports: - - 5432:5432 + - 5432:5432 # Add a health check options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5 steps: - - uses: actions/checkout@v2 - - name: Setup Ruby - uses: eregon/use-ruby-action@master - with: - ruby-version: ${{ matrix.ruby }} - - name: Cache dependencies - uses: actions/cache@v2 - with: - path: vendor/bundle - key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} - - name: Install postgres headers - run: sudo apt-get install libpq-dev - - name: Install dependencies - run: bundle install --path vendor/bundle - - name: Setup environment configuration - run: cp .sample.env .env - - name: Setup database - run: bundle exec rake db:setup - - name: Run tests - run: bundle exec rake - - name: Install appraisal - run: bundle exec appraisal install - - name: Run appraisal - run: bundle exec appraisal rake + - uses: actions/checkout@v2 + - name: Setup Ruby + uses: eregon/use-ruby-action@master + with: + ruby-version: ${{ matrix.ruby }} + - name: Cache dependencies + uses: actions/cache@v2 + with: + path: vendor/bundle + key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }} + - name: Install postgres headers + run: sudo apt-get install libpq-dev + - name: Install dependencies + run: bundle install --path vendor/bundle + - name: Setup environment configuration + run: cp .sample.env .env + - name: Setup database + run: bundle exec rake db:setup + - name: Run tests + run: bundle exec rake + - name: Install appraisal + run: bundle exec appraisal install + - name: Run appraisal + run: bundle exec appraisal rake ``` {% endraw %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 0c45970d40..3eb7b38c32 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -4,7 +4,12 @@ intro: '{% data variables.product.prodname_actions %} 和 GitLab CI/CD 具有一 versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - GitLab + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -60,8 +65,8 @@ job1: jobs: job1: steps: - - uses: actions/checkout@v2 - - run: echo "Run your script here" + - uses: actions/checkout@v2 + - run: echo "Run your script here" ``` {% endraw %} @@ -257,24 +262,24 @@ jobs: build_a: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - run: echo "This job will be run first." build_b: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first, in parallel with build_a" + - run: echo "This job will be run first, in parallel with build_a" test_ab: runs-on: ubuntu-latest needs: [build_a,build_b] steps: - - run: echo "This job will run after build_a and build_b have finished" + - run: echo "This job will run after build_a and build_b have finished" deploy_ab: runs-on: ubuntu-latest needs: [test_ab] steps: - - run: echo "This job will run after test_ab is complete" + - run: echo "This job will run after test_ab is complete" ``` {% endraw %} @@ -335,12 +340,12 @@ test_async: ```yaml jobs: test_async: - - name: Cache node modules - uses: actions/cache@v2 - with: - path: ~/.npm - key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} - restore-keys: v1-npm-deps- + - name: Cache node modules + uses: actions/cache@v2 + with: + path: ~/.npm + key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }} + restore-keys: v1-npm-deps- ``` {% endraw %} @@ -371,7 +376,7 @@ GitLab CI/CD script: artifacts: paths: - - math-homework.txt + - math-homework.txt ``` {% endraw %} @@ -424,12 +429,12 @@ container-job: services: - postgres script: - # Performs a clean installation of all dependencies - # in the `package.json` file - - npm ci - # Runs a script that creates a PostgreSQL client, - # populates the client with data, and retrieves data - - node client.js + # Performs a clean installation of all dependencies + # in the `package.json` file + - npm ci + # Runs a script that creates a PostgreSQL client, + # populates the client with data, and retrieves data + - node client.js tags: - docker ``` diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index 5bb48f709a..43e73f1102 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Jenkins + - Migration + - CI + - CD --- {% data reusables.actions.enterprise-beta %} @@ -37,8 +42,8 @@ Jenkins 可让您发送版本到单个构建代理，或者您可以在多个代 同样， {% data variables.product.prodname_actions %} 可以向 {% data variables.product.prodname_dotcom %} 托管或自托管的运行器发送作业，您可以根据不同的属性使用标签对运行器分类。 下表比较了如何对 Jenkins 和 {% data variables.product.prodname_actions %} 实施分布式构建概念。 | Jenkins | {% data variables.product.prodname_actions %} -| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | +| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners)
    [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) | #### 使用区段组织管道 @@ -51,7 +56,6 @@ Jenkins 将其 Declarative Pipelines 分为多个区段。 同样，{% data vari | [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) | | [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps) | [`jobs..steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) | - ### 使用指令 Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工作流程的特性及其执行方式。 下表演示这些指令如何映射到 {% data variables.product.prodname_actions %} 中的概念。 @@ -69,7 +73,6 @@ Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工 | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input) | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) | | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when) | [`jobs..if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) | - ### 使用连续阶段 #### 并行作业处理 @@ -114,23 +117,23 @@ Jenkins Pipeline - ```yaml - pipeline { - agent any - triggers { - cron('H/15 * * * 1-5') - } - } - ``` +```yaml +pipeline { + agent any + triggers { + cron('H/15 * * * 1-5') + } +} +``` - ```yaml - on: +```yaml +on: schedule: - - cron: '*/15 * * * 1-5' - ``` + - cron: '*/15 * * * 1-5' +``` @@ -150,25 +153,24 @@ Jenkins Pipeline - ```yaml - pipeline { - agent any - environment { - MAVEN_PATH = '/usr/local/maven' - } +```yaml +pipeline { + agent any + environment { + MAVEN_PATH = '/usr/local/maven' } - ``` +} +``` - ```yaml - jobs: - maven-build: +```yaml +jobs: + maven-build: env: MAVEN_PATH: '/usr/local/maven' - - ``` +``` @@ -188,30 +190,28 @@ Jenkins Pipeline - ```yaml - pipeline { - triggers { - upstream( - upstreamProjects: 'job1,job2', - threshold: hudson.model.Result.SUCCESS) - } - } +```yaml +pipeline { + triggers { + upstream( + upstreamProjects: 'job1,job2', + threshold: hudson.model.Result.SUCCESS + ) } - - ``` +} +``` - ```yaml - jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] - - ``` +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + needs: [job1, job2] +``` @@ -231,26 +231,27 @@ Jenkins Pipeline - ```yaml +```yaml pipeline { -agent none -stages { - stage('Run Tests') { - matrix { - axes { - axis { - name: 'PLATFORM' - values: 'macos', 'linux' + agent none + stages { + stage('Run Tests') { + matrix { + axes { + axis { + name: 'PLATFORM' + values: 'macos', 'linux' + } } - } - agent { label "${PLATFORM}" } - stages { - stage('test') { - tools { nodejs "node-12" } - steps { - dir("scripts/myapp") { - sh(script: "npm install -g bats") - sh(script: "bats tests") + agent { label "${PLATFORM}" } + stages { + stage('test') { + tools { nodejs "node-12" } + steps { + dir("scripts/myapp") { + sh(script: "npm install -g bats") + sh(script: "bats tests") + } } } } @@ -258,33 +259,32 @@ stages { } } } -} - ``` +``` {% raw %} - ```yaml - name: demo-workflow - on: - push: - jobs: - test: - runs-on: ${{ matrix.os }} - strategy: - fail-fast: false - matrix: - os: [macos-latest, ubuntu-latest] - steps: - - uses: actions/checkout@v1 - - uses: actions/setup-node@v1 - with: - node-version: 12 - - run: npm install -g bats - - run: bats tests - working-directory: scripts/myapp - ``` +```yaml +name: demo-workflow +on: + push: +jobs: + test: + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [macos-latest, ubuntu-latest] + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm install -g bats + - run: bats tests + working-directory: scripts/myapp +``` {% endraw %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 5dd0564e81..4e7434b3e3 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -6,7 +6,12 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' +type: tutorial +topics: + - Travis CI + - Migration + - CI + - CD --- ### 简介 @@ -69,8 +74,8 @@ Travis CI ```yaml matrix: include: - - rvm: 2.5 - - rvm: 2.6.3 + - rvm: 2.5 + - rvm: 2.6.3 ``` {% endraw %} @@ -109,8 +114,8 @@ Travis CI ```yaml branches: only: - - main - - 'mona/octocat' + - main + - 'mona/octocat' ``` {% endraw %} @@ -119,7 +124,7 @@ branches: ```yaml on: push: - branches: + branches: - main - 'mona/octocat' ``` @@ -155,9 +160,9 @@ git: {% raw %} ```yaml - - uses: actions/checkout@v2 - with: - submodules: false +- uses: actions/checkout@v2 + with: + submodules: false ``` {% endraw %} @@ -207,10 +212,10 @@ Travis CI 和 {% data variables.product.prodname_actions %} 可以将自定义 例如： ```yaml - steps: - - name: Run build script - run: ./.github/scripts/build.sh - shell: bash +steps: + - name: Run build script + run: ./.github/scripts/build.sh + shell: bash ``` ### {% data variables.product.prodname_actions %} 中的错误处理 @@ -275,11 +280,11 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %} @@ -345,20 +350,20 @@ Travis CI - ```yaml +```yaml env: - MAVEN_PATH="/usr/local/maven" - ``` +``` - ```yaml - jobs: - maven-build: - env: - MAVEN_PATH: '/usr/local/maven' - ``` +```yaml +jobs: + maven-build: + env: + MAVEN_PATH: '/usr/local/maven' +``` @@ -378,24 +383,24 @@ Travis CI {% raw %} - ```yaml +```yaml install: - - npm install + - npm install script: - - npm run build - - npm test - ``` + - npm run build + - npm test +``` {% endraw %} {% raw %} - ```yaml +```yaml name: Node.js CI on: [push] jobs: - build: - runs-on: ubuntu-latest - steps: + build: + runs-on: ubuntu-latest + steps: - uses: actions/checkout@v2 - name: Use Node.js uses: actions/setup-node@v1 @@ -404,7 +409,7 @@ jobs: - run: npm install - run: npm run build - run: npm test - ``` +``` {% endraw %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md index e78bdb9259..c2d283ad54 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' type: 'overview' +topics: + - '安全' --- {% data reusables.actions.enterprise-beta %} @@ -54,11 +56,13 @@ type: 'overview' 将操作固定到全长提交 SHA 是当前将操作用作不可变版本的唯一方法。 固定到特定 SHA 有助于降低恶意执行者向操作仓库添加后门的风险，因为他们需要为有效的 Git 对象负载生成 SHA-1 冲突。 + {% if currentVersion ver_lt "enterprise-server@3.1" %} {% warning %} **警告** 提交 SHA 的简短版本不安全，绝不可用于指定操作的 Git 引用。 由于仓库网络的工作方式，任何用户都可以复刻仓库，将精心编写的提交推送到与短 SHA 冲突的仓库。 这会导致该 SHA 上的后续克隆失败，因为它成为不明确的提交。 因此，使用缩短的 SHA 的任何工作流程将立即失败。 {% endwarning %} + {% endif %} * **审核操作的源代码** @@ -113,7 +117,7 @@ type: 'overview' 例如，您可以使用审核日志跟踪 `action:org.update_actions_secret` 事件，以跟踪组织机密的更改： ![审核日志条目](/assets/images/help/repository/audit-log-entries.png) -以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 有关使用审核日志的更多信息，请参阅“[查看组织的审核日志](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)”。 +以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." #### 机密管理的事件 | 操作 | 描述 | @@ -140,4 +144,4 @@ type: 'overview' | `action:org.runner_group_removed` | 组织管理员删除自托管运行器组时触发。 | | `action:org.runner_group_renamed` | 组织管理员重命名自托管运行器组时触发。 | | `action:org.runner_group_runners_added` | 组织管理员[添加自托管运行器到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)时触发。 | -| `action:org.runner_group_runners_removed` | 组织管理员从组中删除自托管运行器时触发。 | +| `action:org.runner_group_runners_removed` | 组织管理员从组中删除自托管运行器时触发。 | diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md b/translations/zh-CN/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md index 8a2b673839..2883a30ee5 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/adding-a-workflow-status-badge.md @@ -34,7 +34,7 @@ https://github.com///workflows//badge.svg 此 Markdown 示例为名为 "Greet Everyone" 的工作流程添加状态徽章。 仓库的 `OWNER` 为 `actions` 组织，`REPOSITORY` 名称为 `hello-world`。 -``` +```markdown ![example workflow name](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg) ``` @@ -42,7 +42,7 @@ https://github.com///workflows//badge.svg 此 Markdown 示例为文件路径为 `.github/workflows/main.yml` 的工作流程添加状态徽章。 仓库的 `OWNER` 为 `actions` 组织，`REPOSITORY` 名称为 `hello-world`。 -``` +```markdown ![example workflow file path](https://github.com/actions/hello-world/workflows/.github/workflows/main.yml/badge.svg) ``` @@ -50,7 +50,7 @@ https://github.com///workflows//badge.svg 此 Markdown 示例为名为 `feature-1` 的分支添加状态徽章。 -``` +```markdown ![example branch parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?branch=feature-1) ``` @@ -58,6 +58,6 @@ https://github.com///workflows//badge.svg 此 Markdown 示例添加显示通过 `pull_request` 事件触发运行的工作流程状态的徽章。 -``` +```markdown ![example event parameter](https://github.com/actions/hello-world/workflows/Greet%20Everyone/badge.svg?event=pull_request) ``` diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 75d37ca3bb..b9ef3a5929 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -18,7 +18,7 @@ versions: 要在 {% data variables.product.prodname_dotcom %} 上触发 `Workflow_spoch` 事件，您的工作流程必须在默认分支中。 按照以下步骤手动触发工作流程运行。 -{% data reusables.repositories.permissions-statement-read %} +{% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index 7e5df38e5b..2f913e932d 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -7,6 +7,9 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' +type: 'quick_start' +topics: + - '基础' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 972fec2790..96fa339d1b 100644 --- a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -186,27 +186,27 @@ jobs: steps: - name: Dump GitHub context env: - GITHUB_CONTEXT: ${{ toJson(github) }} + GITHUB_CONTEXT: ${{ toJSON(github) }} run: echo "$GITHUB_CONTEXT" - name: Dump job context env: - JOB_CONTEXT: ${{ toJson(job) }} + JOB_CONTEXT: ${{ toJSON(job) }} run: echo "$JOB_CONTEXT" - name: Dump steps context env: - STEPS_CONTEXT: ${{ toJson(steps) }} + STEPS_CONTEXT: ${{ toJSON(steps) }} run: echo "$STEPS_CONTEXT" - name: Dump runner context env: - RUNNER_CONTEXT: ${{ toJson(runner) }} + RUNNER_CONTEXT: ${{ toJSON(runner) }} run: echo "$RUNNER_CONTEXT" - name: Dump strategy context env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} + STRATEGY_CONTEXT: ${{ toJSON(strategy) }} run: echo "$STRATEGY_CONTEXT" - name: Dump matrix context env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} + MATRIX_CONTEXT: ${{ toJSON(matrix) }} run: echo "$MATRIX_CONTEXT" ``` {% endraw %} @@ -348,7 +348,7 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') `join(github.event.issue.labels.*.name, ', ')` 可能返回 'bug, help wanted' -#### toJson +#### toJSON `toJSON(value)` @@ -358,13 +358,13 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') `toJSON(job)` 可能返回 `{ "status": "Success" }` -#### fromJson +#### fromJSON `fromJSON(value)` -返回 `value` 的 JSON 对象。 您可以使用此函数提供 JSON 对象作为评估的表达式。 +Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string. -##### 示例 +##### Example returning a JSON object 此工作流程在一个作业中设置 JSON矩阵，并使用输出和 `fromJSON` 将其传递到下一个作业。 @@ -384,12 +384,33 @@ jobs: needs: job1 runs-on: ubuntu-latest strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} + matrix: ${{fromJSON(needs.job1.outputs.matrix)}} steps: - run: build ``` {% endraw %} +##### Example returning a JSON data type + +This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer. + +{% raw %} +```yaml +name: print +on: push +env: + continue: true + time: 3 +jobs: + job1: + runs-on: ubuntu-latest + steps: + - continue-on-error: ${{ fromJSON(env.continue) }} + timeout-minutes: ${{ fromJSON(env.time) }} + run: echo ... +``` +{% endraw %} + #### hashFiles `hashFiles(path)` diff --git a/translations/zh-CN/content/actions/reference/environment-variables.md b/translations/zh-CN/content/actions/reference/environment-variables.md index 5ad15c65e0..7441e43781 100644 --- a/translations/zh-CN/content/actions/reference/environment-variables.md +++ b/translations/zh-CN/content/actions/reference/environment-variables.md @@ -21,15 +21,25 @@ versions: 要设置自定义环境变量，您需要在工作流程文件中指定变量。 您可以使用 [`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) 和 [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) 关键字定义步骤、作业或整个工作流程的环境变量。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)”。 ```yaml -steps: - - name: Hello world - run: echo Hello world $FIRST_NAME $middle_name $Last_Name! +jobs: + weekday_job: + runs-on: ubuntu-latest env: - FIRST_NAME: Mona - middle_name: The - Last_Name: Octocat + DAY_OF_WEEK: Mon + steps: + - name: "Hello world when it's Monday" + if: env.DAY_OF_WEEK == 'Mon' + run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" + env: + FIRST_NAME: Mona + middle_name: The + Last_Name: Octocat ``` +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. + +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. + 您也可以使用 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV` environment file{% else %} `set-env` 工作流程命令{% endif %} 设置工作流程中的以下步骤可以使用的环境变量。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}环境文件{% else %} `set-env` 命令{% endif %}可直接由操作使用，或使用 `run` 关键字作为工作流程文件中的 shell 命令。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)”。 ### 默认环境变量 diff --git a/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md index d01e75b9ff..8a03e7f70c 100644 --- a/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md @@ -257,7 +257,7 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro **警告：**Powershell 默认不使用 UTF-8。 请确保使用正确的编码写入文件。 例如，在设置路径时需要设置 UTF-8 编码： -``` +```yaml steps: - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` @@ -272,11 +272,19 @@ steps: #### 示例 -```bash -echo "action_state=yellow" >> $GITHUB_ENV +{% raw %} ``` - -在未来步骤中运行 `$action_state` 现在会返回 `yellow` +steps: + - name: Set the value + id: step_one + run: | + echo "action_state=yellow" >> $GITHUB_ENV + - name: Use the value + id: step_two + run: | + echo "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} #### 多行字符串 @@ -291,7 +299,7 @@ echo "action_state=yellow" >> $GITHUB_ENV ##### 示例 在此示例中， 我们使用 `EOF` 作为分隔符，并将 `JSON_RESPONSE` 环境变量设置为 cURL 响应的值。 -``` +```yaml steps: - name: Set the value id: step_one diff --git a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md index 979993124e..afd0397037 100644 --- a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ versions: ### `on` -**必要** 触发工作流程的 {% data variables.product.prodname_dotcom %} 事件的名称。 您可以提供单一事件 `string`、事件的 `array`、事件 `types` 的 `array` 或事件配置 `map`，以安排工作流程的运行，或将工作流程的执行限于特定文件、标记或分支更改。 有关可用事件的列表，请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows)”。 +**必填**。 The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. 您可以提供单一事件 `string`、事件的 `array`、事件 `types` 的 `array` 或事件配置 `map`，以安排工作流程的运行，或将工作流程的执行限于特定文件、标记或分支更改。 有关可用事件的列表，请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows)”。 {% data reusables.github-actions.actions-on-examples %} @@ -286,7 +286,7 @@ jobs: ### `jobs..runs-on` -**必需**运行作业的机器类型。 机器可以是 {% data variables.product.prodname_dotcom %} 托管的运行器或自托管的运行器。 +**必填**。 The type of machine to run the job on. 机器可以是 {% data variables.product.prodname_dotcom %} 托管的运行器或自托管的运行器。 {% data reusables.actions.enterprise-github-hosted-runners %} @@ -299,6 +299,7 @@ jobs: {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} ##### 示例 @@ -518,7 +519,7 @@ steps: ```yaml steps: # Reference a specific commit - - uses: actions/setup-node@74bc508 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e # Reference the major version of a release - uses: actions/setup-node@v1 # Reference a minor version of a release @@ -700,12 +701,24 @@ steps: 您可以使用 `command […options] {0} [..more_options]` 将 `shell` 值设置为模板字符串。 {% data variables.product.prodname_dotcom %} 将字符串的第一个用空格分隔的词解释为命令，并在 `{0}` 处插入临时脚本的文件名。 +例如： + +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +The command used, `perl` in this example, must be installed on the runner. 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)." + #### 退出代码和错误操作首选项 至于内置的 shell 关键词，我们提供由 {% data variables.product.prodname_dotcom %} 托管运行程序执行的以下默认值。 在运行 shell 脚本时，您应该使用这些指南。 - `bash`/`sh`： - - 使用 `set -e o pipefail` 的快速失败行为：`bash` 和内置 `shell` 的默认值。 它还是未在非 Windows 平台上提供选项时的默认值。 + - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. 它还是未在非 Windows 平台上提供选项时的默认值。 - 您可以向 shell 选项提供模板字符串，以退出快速失败并接管全面控制权。 例如 `bash {0}`。 - sh 类 shell 使用脚本中最后执行的命令的退出代码退出，也是操作的默认行为。 运行程序将根据此退出代码将步骤的状态报告为失败/成功。 @@ -1177,16 +1190,16 @@ volumes: #### 匹配分支和标记的模式 -| 模式 | 描述 | 示例匹配 | -| ------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -| `功能/*` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 | `feature/my-branch`

    `feature/your-branch` | -| `功能/**` | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。 | `feature/beta-a/my-branch`

    `feature/your-branch`

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

    `releases/mona-the-octcat` | 匹配分支或标记名称的确切名称。 | `main`

    `releases/mona-the-octocat` | -| `'*'` | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `main`

    `releases` | -| `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | `all/the/branches`

    `every/tag` | -| `'*功能'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `mona-feature`

    `feature`

    `ver-10-feature` | -| `v2*` | 匹配以 `v2` 开头的分支和标记名称。 | `v2`

    `v2.0`

    `v2.9` | -| `v[12].[0-9]+.[0-9]+` | 将所有语义版本控制标记与主要版本 1 或 2 匹配 | `v1.10.1`

    `v2.0.0` | +| 模式 | 描述 | 示例匹配 | +| ------------------------------------------------------ | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `功能/*` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 | `feature/my-branch`

    `feature/your-branch` | +| `功能/**` | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。 | `feature/beta-a/my-branch`

    `feature/your-branch`

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

    `releases/mona-the-octcat` | 匹配分支或标记名称的确切名称。 | `main`

    `releases/mona-the-octocat` | +| `'*'` | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `main`

    `releases` | +| `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | `all/the/branches`

    `every/tag` | +| `'*功能'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `mona-feature`

    `feature`

    `ver-10-feature` | +| `v2*` | 匹配以 `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` | #### 匹配文件路径的模式 diff --git a/translations/zh-CN/content/admin/configuration/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/command-line-utilities.md index b5bbf5bb12..a2811d3487 100644 --- a/translations/zh-CN/content/admin/configuration/command-line-utilities.md +++ b/translations/zh-CN/content/admin/configuration/command-line-utilities.md @@ -76,8 +76,8 @@ $ ghe-config -l ``` 允许您在 `cluster.conf` 中查找节点的 uuid。 -``` shell - $ ghe-config _hostname_.uuid +```shell + $ ghe-config HOSTNAME.uuid ``` {% if currentVersion ver_gt "enterprise-server@2.21" %} @@ -545,8 +545,8 @@ ghe-dpages status ``` 要在撤出集群节点之前撤出 {% data variables.product.prodname_pages %} 存储服务： -``` shell -ghe-dpages evacuate pages-server- +```shell +ghe-dpages evacuate pages-server-UUID ``` #### ghe-spokes @@ -571,16 +571,16 @@ ghe-spokes route 要撤出集群节点上的存储服务： -``` shell -ghe-spokes server evacuate git-server- +```shell +ghe-spokes server evacuate git-server-UUID ``` #### ghe-storage 此实用程序允许您在撤出集群节点之前撤出所有存储服务。 -``` shell -ghe-storage evacuate storage-server- +```shell +ghe-storage evacuate storage-server-UUID ``` ### Git diff --git a/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md b/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md index b0e987cc33..c31c77e41f 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md +++ b/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md @@ -41,12 +41,6 @@ versions: - 在 **Authentication** 下拉菜单中，选择您的 SMTP 服务器使用的加密类型。 - 在 **No-reply email address** 字段中，输入要在所有通知电子邮件的 From 和 To 字段中使用的电子邮件地址。 - {% note %} - - **注**：如果您在仓库的 **Services** 电子邮件 web 挂钩中选中 **Send from author** 复选框，则该仓库的出站电子邮件将从作者而不是无回复电子邮件地址发送。 更多信息请参阅“[关于推送到仓库的电子邮件通知](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)。” - - {% endnote %} - 6. 如果您想丢弃发送到无回复电子邮件地址的所有传入电子邮件，请选中 **Discard email addressed to the no-reply email address**。 ![用于丢弃发送到无回复电子邮件地址的电子邮件的复选框](/assets/images/enterprise/management-console/discard-noreply-emails.png) 7. 在 **Support** 下，选择用于向您的用户提供附加支持的链接类型： - **Email**：内部电子邮件地址。 @@ -155,7 +149,7 @@ Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asm #### 验证 DNS 设置 -为了正确处理入站电子邮件，您必须配置有效的 A 记录（或 CNAME）和 MX 记录。 更多信息请参阅“[配置 DNS 和防火墙设置以允许传入的电子邮件](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)”。 +为了正确处理入站电子邮件，您必须配置有效的 A 记录（或 CNAME）和 MX 记录。 For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." #### 检查防火墙或 AWS 安全组设置 diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md index b219fe0cb2..9b794775cc 100644 --- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md @@ -10,7 +10,7 @@ versions: ### 关于集群的高可用性复制 -您可以配置 {% data variables.product.prodname_ghe_server %} 的群集部署以实现高可用性，其中一组相同的被动节点与活动群集中的节点同步。 如果硬件或软件故障影响具有活动群集的数据中心，您可以手动故障转移到副本节点，继续处理用户请求，而不会丢失数据。 +您可以配置 {% data variables.product.prodname_ghe_server %} 的群集部署以实现高可用性，其中一组相同的被动节点与活动群集中的节点同步。 If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage. 在高可用性模式下，每个活动节点定期与相应的被动节点同步。 被动节点在待机状态下运行，不服务于应用程序或处理用户请求。 diff --git a/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md index 12065cd31c..387c7b6a4b 100644 --- a/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md +++ b/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md @@ -25,9 +25,11 @@ versions: ghe-spokes evac-status ``` 对于 {% data variables.product.prodname_pages %} + {% raw %} ``` echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y ``` + {% endraw %} 对于存储 ``` ghe-storage evacuation-status @@ -36,18 +38,26 @@ versions: 3. 复制完成后，您可以撤出存储服务。 运行以下任意命令： 对于 Git + {% raw %} ``` ghe-spokes server evacuate git-server- ``` + {% endraw %} 对于 {% data variables.product.prodname_pages %} + {% raw %} ``` ghe-dpages evacuate pages-server- ``` + {% endraw %} 对于存储，请使节点离线 + {% raw %} ``` ghe-storage offline storage-server- ``` + {% endraw %} 然后撤出 + {% raw %} ``` ghe-storage evacuate storage-server- ``` + {% endraw %} diff --git a/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md b/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md index 96595a66ec..c65a41db23 100644 --- a/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md +++ b/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md @@ -45,7 +45,7 @@ versions: 通过 `mysql-server` 和 `mysql-master` 指定您配置为 MySQL 主要节点的第一个集群节点。 -``` +```ini [cluster] mysql-master = ghe-data-node-1 redis-master = ghe-data-node-1 diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md index 9d761de2d9..845fdc9058 100644 --- a/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md @@ -123,7 +123,6 @@ versions: ### 延伸阅读 {% if enterpriseServerVersions contains currentVersion %} -- [关于 {% data variables.product.prodname_ghe_server %} 的常见问题](https://enterprise.github.com/faq) - 关于“[{% data variables.product.prodname_ghe_server %} 许可协议](https://enterprise.github.com/license)”中支持的第 10 节{% endif %} - "[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %} - “[准备提交事件单](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)”{% endif %} diff --git a/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md index 531d5feb68..8b4fd3075e 100644 --- a/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -63,7 +63,7 @@ However, if you want stricter control over which actions are allowed in your ent * 将 `--repo-name` 参数替换为 `--repo-name-list` 或 `--repo-name-list-file` 便可同步多个操作。 更多信息请参阅 [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync)。 1. 在企业实例上创建操作仓库后，企业中的人员可以使用目标仓库在其工作流程中引用操作。 对于上面显示的示例操作： - ``` + ```yaml uses: synced-actions/docker-build-push-action@v1 ``` diff --git a/translations/zh-CN/content/admin/overview/about-github-ae.md b/translations/zh-CN/content/admin/overview/about-github-ae.md new file mode 100644 index 0000000000..11d18f22af --- /dev/null +++ b/translations/zh-CN/content/admin/overview/about-github-ae.md @@ -0,0 +1,46 @@ +--- +title: About GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} is the most secure and compliant way to use {% data variables.product.prodname_dotcom %}.' +versions: + github-ae: '*' +--- + +### 关于 {% data variables.product.prodname_ghe_managed %} + +{% data reusables.github-ae.github-ae-enables-you %} + +{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase developer velocity, automate entire workflows, secure your code, and collaborate in developers’ favorite tool. + +{% data variables.product.prodname_ghe_managed %} provides your organization with all the power of [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). With {% data variables.product.prodname_ghe_managed %}, you can also meet security and compliance goals with a suite of features and certifications that put you in control. + +### A highly available and planet-scale cloud + +{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. + +### Data residency + +All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region. + +### Encryption on your terms + +All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. 更多信息请参阅“[为企业配置数据加密](/admin/configuration/configuring-data-encryption-for-your-enterprise)”。 + +### Isolated accounts + +All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." + +### Restricted network access + +Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”。 + +### Commercial and government environments + +{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization. + +### Premium Plus support + +Premium Plus support is available for all {% data variables.product.prodname_ghe_managed %} customers, to ensure you have the fastest and most personal support experience. A dedicated Account Manager will work with you to help you get the most out of {% data variables.product.prodname_dotcom %}. Our support team will resolve issues any time of day, in the shortest possible time. + +### 关于 {% data variables.product.prodname_ghe_managed %} 的计费 + +{% data reusables.github-ae.about-billing %} For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." \ No newline at end of file diff --git a/translations/zh-CN/content/admin/overview/index.md b/translations/zh-CN/content/admin/overview/index.md index d415cc1e5b..be87877361 100644 --- a/translations/zh-CN/content/admin/overview/index.md +++ b/translations/zh-CN/content/admin/overview/index.md @@ -12,6 +12,7 @@ versions: ### 目录 +{% link_in_list /about-github-ae %} {% link_in_list /about-enterprise-accounts %} {% link_in_list /managing-your-github-enterprise-license %} {% link_in_list /managing-billing-for-your-enterprise %} diff --git a/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md b/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md index 4a8b3a069a..927ff1e128 100644 --- a/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md +++ b/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md @@ -41,7 +41,9 @@ versions: {% data reusables.enterprise-accounts.license-tab %} 12. 在“Quick links”下，单击 **Update license**。 ![更新许可链接](/assets/images/enterprise/business-accounts/update-license-link.png) 13. 要选择许可，请单击 **License file（许可文件）**，或将许可文件拖到 **License file（许可文件）**上。 ![上传许可文件](/assets/images/enterprise/management-console/upload-license.png) -14. 单击 **Upload（上传）**。 ![开始升级](/assets/images/enterprise/management-console/begin-upload.png) +14. 单击 **Upload（上传）**。 ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) + +{% if enterpriseVersion ver_lt "enterprise-server@3.0" %}If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)."{% endif %} ### 查看许可使用情况 @@ -70,3 +72,23 @@ versions: {% data reusables.enterprise-accounts.license-tab %} 10. 在“Enterprise Server Instances（Enterprise Server 实例）”下，单击 **Add server usage（添加服务器使用情况）**。 ![Upload GitHub Enterprise Servers usage 链接](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) 11. 上传从 {% data variables.product.prodname_ghe_server %} 下载的 JSON 文件。 ![拖放或选择要上传的文件](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) + +{% if currentVersion ver_lt "enterprise-server@3.0" %} + +### 疑难解答 + +In some scenarios, the web UI for {% data variables.product.prodname_ghe_server %} may not immediately reflect your new license. You can force the system to detect the license by restarting two system services. + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Restart the services for Git authentication and the HTTP server. + + {% warning %} + + **Warning**: Running the following command will result in a few minutes of user-facing downtime for {% data variables.product.prodname_ghe_server %}. Run the command with care. + + {% endwarning %} + + sudo systemctl restart github-gitauth github-unicorn +1. After {% data variables.product.prodname_ghe_server %} returns you to a prompt, try accessing {% data variables.product.prodname_ghe_server %} via the command line or web UI again. + +{% endif %} diff --git a/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md index 621386099b..fe77e9a446 100644 --- a/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -58,7 +58,8 @@ versions: | $GITHUB_VIA | 用于创建 ref 的方法。
    **可选值：**
    - `auto-merge deployment api`
    - `blob edit`
    - `branch merge api`
    - `branches page delete button`
    - `git refs create api`
    - `git refs delete api`
    - `git refs update api`
    - `merge api`
    - `pull request branch delete button`
    - `pull request branch undo button`
    - `pull request merge api`
    - `pull request merge button`
    - `pull request revert button`
    - `releases delete button`
    - `stafftools branch restore`
    - `slumlord (#{sha})` | | $GIT_PUSH_OPTION_COUNT | 客户端发送的推送选项数。 关于推送选项的更多信息，请参阅 Git 文档中的“[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)”。 | | $GIT_PUSH_OPTION_N | 其中 N 是一个从 0 开始的整数，此变量包含客户端发送的推送选项字符串。 发送的第一个选项存储在 GIT_PUSH_OPTION_0 中，发送的第二个选项存储在 GIT_PUSH_OPTION_1 中，依此类推。 关于推送选项的更多信息，请参阅 Git 文档中的“[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)”。 |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | 推送更改的客户端发送的 user-agent 字符串。 |{% endif %} +| $GIT_USER_AGENT | 推送更改的客户端发送的 user-agent 字符串。 +{% endif %} ### 设置权限并将预接收挂钩推送到 {% data variables.product.prodname_ghe_server %} @@ -93,30 +94,30 @@ versions: 2. 创建一个名为 `Dockerfile.dev` 的文件，其中包含： - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ - mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" + ```dockerfile + FROM gliderlabs/alpine:3.3 + RUN \ + apk add --no-cache git openssh bash && \ + ssh-keygen -A && \ + sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ + adduser git -D -G root -h /home/git -s /bin/bash && \ + passwd -d git && \ + su git -c "mkdir /home/git/.ssh && \ + ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ + mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ + mkdir /home/git/test.git && \ + git --bare init /home/git/test.git" - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git + VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] + WORKDIR /home/git - CMD ["/usr/sbin/sshd", "-D"] - ``` + CMD ["/usr/sbin/sshd", "-D"] + ``` -3. 创建一个名为 `always_reject.sh` 的测试预接收脚本。 此示例脚本将拒绝所有推送，这对于锁定仓库非常有用： + 3. 创建一个名为 `always_reject.sh` 的测试预接收脚本。 此示例脚本将拒绝所有推送，这对于锁定仓库非常有用： - ``` - #!/usr/bin/env bash + ```shell + #!/usr/bin/env bash echo "error: rejecting all pushes" exit 1 diff --git a/translations/zh-CN/content/admin/user-management/audited-actions.md b/translations/zh-CN/content/admin/user-management/audited-actions.md index eda254a8bd..1fa9160730 100644 --- a/translations/zh-CN/content/admin/user-management/audited-actions.md +++ b/translations/zh-CN/content/admin/user-management/audited-actions.md @@ -80,7 +80,7 @@ versions: | 名称 | 描述 | | ------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.access` | 仓库的可见性已更改为私有{% if enterpriseServerVersions contains currentVersion %}、公共{% endif %} 或内部。 | -| `repo.archive` | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。 | +| `repo.archived` | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。 | | `repo.add_member` | 已向仓库添加协作者。 | | `repo.config` | 站点管理员已阻止强制推送。 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。 | | `repo.create` | 已创建仓库。 | @@ -89,7 +89,7 @@ versions: | `repo.rename` | 已重命名仓库。 | | `repo.transfer` | 用户已接受接收传输仓库的请求。 | | `repo.transfer_start` | 用户已发送向另一用户或组织传输仓库的请求。 | -| `repo.unarchive` | 已取消存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。{% if enterpriseServerVersions contains currentVersion %} +| `repo.unarchived` | 已取消存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。{% if enterpriseServerVersions contains currentVersion %} | `repo.config.disable_anonymous_git_access` | 已为仓库禁用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” | | `repo.config.enable_anonymous_git_access` | 已为仓库启用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。” | | `repo.config.lock_anonymous_git_access` | 已锁定仓库的匿名 Git 读取权限设置，阻止仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 | diff --git a/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md b/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md index 6ad50001f8..54c14b3f91 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md @@ -33,11 +33,11 @@ versions: 1. 连接到管理 shell。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)。” 2. 导航至 `/data/github/current` 目录。 - ``` + ```shell cd /data/github/current ``` 3. 运行迁移命令。 - ``` + ```shell sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log ``` diff --git a/translations/zh-CN/content/admin/user-management/viewing-push-logs.md b/translations/zh-CN/content/admin/user-management/viewing-push-logs.md index ea8f61c04a..c211feeb80 100644 --- a/translations/zh-CN/content/admin/user-management/viewing-push-logs.md +++ b/translations/zh-CN/content/admin/user-management/viewing-push-logs.md @@ -22,16 +22,19 @@ versions: ### 查看仓库的推送日志 +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. 1. 导航到仓库。 -{% data reusables.enterprise_site_admin_settings.access-settings %} +1. In the upper-right corner of the repository's page, click +{% octicon "rocket" aria-label="The rocket ship" %}。 + ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} 4. 在左侧边栏中，单击 **Push Log**。 ![Push Log 选项卡](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% if enterpriseServerVersions contains currentVersion %} ### 在命令行上查看仓库的推送日志 -1. 通过 SSH 登录您的设备。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。 -2. 在相应的 Git 仓库中，打开审核日志文件： +{% data reusables.enterprise_installation.ssh-into-instance %} +1. 在相应的 Git 仓库中，打开审核日志文件： ```shell ghe-repo owner/repository -c "less audit_log" ``` diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 6365584fc8..8b28df3c07 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -33,3 +33,14 @@ versions: ![查看历史记录中的标记](/assets/images/help/desktop/viewing-tags-in-history.png) 3. 与提交相关的所有标记均在提交元数据中可见。 ![查看提交中的标记](/assets/images/help/desktop/viewing-tags-in-commit.png) + +### 删除标记 + +{% note %} + +**注**：您只能删除与尚未推送的提交关联的标记。 + +{% endnote %} + +{% data reusables.desktop.history-tab %} +{% data reusables.desktop.delete-tag %} diff --git a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md index 49d058670c..cbfbf4a4bc 100644 --- a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md @@ -213,7 +213,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### 设备流程的速率限制 -When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. +当用户在浏览器上提交验证码时，每个应用程序在一个小时内的提交速率限制为 50 个。 如果您在请求之间所需的最短时间段（或 `interval`）内发出多个访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`)，您将达到速率限制并收到 `slow_down` 错误响应。 `slow_down` 错误响应将给最近的`间隔`增加 5 秒。 更多信息请参阅“[设备流程的错误](#errors-for-the-device-flow)”。 diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md index 80a92d8860..e374ae0a1f 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -80,7 +80,7 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app 此示例使用网页上的表单，其中包含一个按钮，该按钮可触发用户帐户的 `POST` 请求： -``` +```html Create a GitHub App Manifest:
    @@ -111,7 +111,7 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app ``` 此示例使用网页上的表单，其中包含一个按钮，该按钮可触发组织帐户的 `POST` 请求： 将 `ORGANIZATION` 替换为要在其中创建应用程序的组织帐户的名称。 -``` +```html Create a GitHub App Manifest:
    diff --git a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 655dc278f0..a3c961420e 100644 --- a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -24,7 +24,7 @@ CI 服务器托管运行 CI 测试的代码，如代码语法检查（检查样 [检查 API](/rest/reference/checks) 允许您设置针对仓库中的每个代码提交自动运行的 CI 测试。 检查 API 在拉取请求的 **Checks（检查）**选项卡中报告 GitHub 上每个检查的详细信息。 使用检查 API，您可以创建带有特定代码行附加细节的注释。 注释在 **Checks（检查）**选项卡中可见。 当您为拉取请求中的文件创建注释时，注释也会显示在 **Files changed（文件已更改）**选项卡中。 -_检查套件_是一组_检查运行_（单个 CI 测试）。 套件和运行都包含 GitHub 上的拉取请求中可见的_状态_。 您可以使用状态来确定何时代码提交引入错误。 对[受保护分支](/rest/reference/repos#branches)使用这些状态可防止用户草率地合并拉取请求。 See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details. +_检查套件_是一组_检查运行_（单个 CI 测试）。 套件和运行都包含 GitHub 上的拉取请求中可见的_状态_。 您可以使用状态来确定何时代码提交引入错误。 对[受保护分支](/rest/reference/repos#branches)使用这些状态可防止用户草率地合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 每当有新代码推送到仓库时，检查 API 会将 [`check_suite` web 挂钩事件](/webhooks/event-payloads/#check_suite)发送到仓库中安装的所有 GitHub 应用程序。 要接收所有检查 API 事件操作，应用程序必须具有 `checks:write` 权限。 GitHub 使用默认流程自动为仓库中的新代码提交创建 `check_suite` 事件，但您可以根据需要[更新检查套件的仓库首选项](/rest/reference/checks#update-repository-preferences-for-check-suites)。 以下是默认流程的工作方式： @@ -434,7 +434,7 @@ clone_repository(full_repo_name, repository, head_sha) ### 步骤 2.3. 运行 RuboCop -太好了！ 您正在克隆仓库并使用 CI 服务器创建检查运行。 现在，您将了解 [RuboCop 语法检查](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker)和[检查 API 注释](/rest/reference/checks#create-a-check-run)的实质内容。 +太好了！ 您正在克隆仓库并使用 CI 服务器创建检查运行。 现在，您将了解 [RuboCop 语法检查](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker)和[检查 API 注释](/rest/reference/checks#create-a-check-run)的实质内容。 下面的代码运行 RuboCop 并以 JSON 格式保存样式代码错误。 将此代码添加到您在[上一步](#step-22-cloning-the-repository)中添加的 `clone_repository` 调用之下，更新要完成检查运行的代码之上。 @@ -446,7 +446,7 @@ logger.debug @report @output = JSON.parse @report ``` -上面的代码在仓库目录中的所有文件上运行 RuboCop 。 选项 `--format json` 是将分析结果的副本保存为机器可解析格式的方便方法。 有关 JSON 格式的详细信息和示例，请参阅 [RuboCop 文档](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter)。 +上面的代码在仓库目录中的所有文件上运行 RuboCop 。 选项 `--format json` 是将分析结果的副本保存为机器可解析格式的方便方法。 有关 JSON 格式的详细信息和示例，请参阅 [RuboCop 文档](https://docs.rubocop.org/rubocop/formatters.html#json-formatter)。 由于此代码将 RuboCop 结果存储在 `@report` 变量中，因此可以安全地删除仓库的检出。 此代码还解析 JSON，因此您可以使用 `@output` 变量轻松访问 GitHub 应用程序中的键和值。 @@ -587,7 +587,7 @@ end 当 `offense_count` 为零时，CI 测试为 `success`。 如果存在错误，此代码会将结论设置为 `neutral`，以防止严格执行来自代码语法检查的错误。 但如果您想确保检查套件在发现分析错误时失败，您可以将结论更改为 `failure`。 -当报告错误时，上面的代码将遍历 RuboCop 报告中的 `files` 数组。 对于每个文件，它会提取文件路径，并将注释级别设置为 `notice`。 您可以更进一步，为每种类型的 [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/) 设置特定的警告级别，但本快速入门为简单起见，将所有错误都设置为 `notice` 级别。 +当报告错误时，上面的代码将遍历 RuboCop 报告中的 `files` 数组。 对于每个文件，它会提取文件路径，并将注释级别设置为 `notice`。 您可以更进一步，为每种类型的 [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html) 设置特定的警告级别，但本快速入门为简单起见，将所有错误都设置为 `notice` 级别。 此代码还会遍历 `offenses` 数组中的每个错误，并收集超限和错误消息的位置。 提取所需的信息后，代码将为每个错误创建一个注释，并将其存储在 `annotations` 数组中。 由于注释只支持同一行上的开始和结束列，因此，只有在开始和结束行的值相同的情况下，才会将 `start_column` 和 `end_column` 添加到 `annotation` 对象中。 @@ -717,13 +717,13 @@ $ ruby template_server.rb 如果您走到了这一步，为您点赞！ 👏 您已经创建了 CI 测试。 在本节中，您将添加另外一个功能，即使用 RuboCop 自动修复它发现的错误。 您在[上一节](#step-25-updating-the-check-run-with-ci-test-results)中已经添加了“Fix this（修复此问题）”按钮。 现在，您将添加代码以处理当有人单击“Fix this（修复此问题）”按钮时触发的 `requested_action` 检查运行事件。 -RuboCop 工具[提供](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) `--auto-correct` 命令行选项，以自动修复它发现的错误。 使用 `--auto-correct` 功能时，更新将应用于服务器上的本地文件。 在 RuboCop 发挥作用之后，您需要将更改推送到 GitHub。 +RuboCop 工具[提供](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) `--auto-correct` 命令行选项，以自动修复它发现的错误。 使用 `--auto-correct` 功能时，更新将应用于服务器上的本地文件。 在 RuboCop 发挥作用之后，您需要将更改推送到 GitHub。 要推送到仓库，您的应用程序必须具备“仓库内容”的写入权限。 您在[步骤 2.2 中重新设置了该权限。 将仓库克隆](#step-22-cloning-the-repository)为**Read & write（读取和写入）**，现在所有设置就绪。 要提交文件，Git 必须知道哪些[用户名](/articles/setting-your-username-in-git/)和[电子邮件](/articles/setting-your-commit-email-address-in-git/)与提交关联。 在 `.env` 文件中再添加两个变量，以存储名称 (`GITHUB_APP_USER_NAME`) 和电子邮件 (`GITHUB_APP_USER_EMAIL`) 设置。 您的名称可以是应用程序名称，电子邮件可以是您在本例中想使用的任何电子邮件地址。 例如： -``` +```ini GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` diff --git a/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index f375058c3b..6f1faf18d3 100644 --- a/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -58,7 +58,8 @@ _授权的_ OAuth 应用程序有权访问用户或组织所有者可访问的 | 安装令牌在预定义的时间（当前为 1 小时）后过期。 | OAuth 令牌在被客户撤销之前一直保持活动状态。 | | {% data reusables.apps.api-rate-limits-non-ghec %}{% if currentVersion == "free-pro-team@latest" %} 更高的速率限制适用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[GitHub 应用程序的速率限制](/developers/apps/rate-limits-for-github-apps)”。{% endif %} | OAuth 令牌使用用户的每小时 5,000 个请求的速率限制。 | | 速率限制的增加可在 GitHub 应用程序级别（影响所有安装）和单个安装级别上授予。 | 速率限制的增加按 OAuth 应用程序授予。 授予该 OAuth 应用程序的每个令牌都会获得增加的上限。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| {% data variables.product.prodname_github_app %} 可以代表用户进行身份验证，这称为用户到服务器请求。 授权流程与 OAuth 应用程序授权流程相同。 用户到服务器令牌可能会过期，可通过刷新令牌进行续订。 更多信息请参阅“[刷新用户到服务器访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”和“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 | {% data variables.product.prodname_oauth_app %} 使用的 OAuth 流程代表用户授权 {% data variables.product.prodname_oauth_app %}。 这与用于 {% data variables.product.prodname_github_app %} 用户到服务器授权中使用的流程相同。 |{% endif %} +| {% data variables.product.prodname_github_app %} 可以代表用户进行身份验证，这称为用户到服务器请求。 授权流程与 OAuth 应用程序授权流程相同。 用户到服务器令牌可能会过期，可通过刷新令牌进行续订。 更多信息请参阅“[刷新用户到服务器访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”和“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 | {% data variables.product.prodname_oauth_app %} 使用的 OAuth 流程代表用户授权 {% data variables.product.prodname_oauth_app %}。 这与用于 {% data variables.product.prodname_github_app %} 用户到服务器授权中使用的流程相同。 +{% endif %} ### 请求资源的权限级别 diff --git a/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index ae8667bbce..d155eaa9b3 100644 --- a/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -89,7 +89,7 @@ versions: 默认情况下，响应采用以下形式。 响应参数 `expires_in`、`refresh_token` 和 `refresh_token_expires_in` 仅当您启用过期用户到服务器访问令牌测试版功能时才会返回。 -``` +```json { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", diff --git a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md index f961f5cde1..65216f54ee 100644 --- a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md @@ -38,41 +38,41 @@ X-Accepted-OAuth-Scopes: user ### 可用作用域 -| 名称 | 描述 | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 名称 | 描述 | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`（无作用域）`** | 授予对公共信息的只读访问权限（包括公开的用户个人资料、公共仓库信息和 gist）{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} | **`site_admin`** | 授予站点管理员对 [{% data variables.product.prodname_ghe_server %} 管理 API 端点](/rest/reference/enterprise-admin)的访问权限。{% endif %} -| **`repo`** | 授予对私有和公共仓库的完全访问权限。 这包括对公共和私有仓库及组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。 | -|  `repo:status` | 授予对公共和私有仓库提交状态的读取/写入权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | -|  `repo_deployment` | 授予对公共和私有仓库[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | -|  `public_repo` | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。 | +| **`repo`** | 授予对私有和公共仓库的完全访问权限。 这包括对公共和私有仓库及组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。 | +|  `repo:status` | 授予对公共和私有仓库提交状态的读取/写入权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | +|  `repo_deployment` | 授予对公共和私有仓库[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | +|  `public_repo` | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。 | |  `repo:invite` | 授予接受/拒绝仓库协作邀请的权限。 仅在授予其他用户或服务对邀请的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -|  `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 %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@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`** | 授予对公共和私有仓库中仓库挂钩的读取、写入、ping 和删除权限。 `repo` 和 `public_repo` 作用域授予对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 | -|  `write:repo_hook` | 授予对公共或私有仓库中挂钩的读取、写入和 ping 权限。 | -|  `read:repo_hook` | 授予对公共或私有仓库中挂钩的读取和 ping 权限。 | -| **`admin:org`** | 全面管理组织及其团队、项目和成员。 | -|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 | -|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 | -| **`admin:public_key`** | 全面管理公钥。 | -|  `write:public_key` | 创建、列出和查看公钥的详细信息。 | -|  `read:public_key` | 列出和查看公钥的详细信息。 | -| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 | -| **`gist`** | 授予对 gist 的写入权限。 | -| **`通知`** | 授予：
    * 对用户通知的读取权限
    * 对线程的标记读取权限
    * 对仓库的关注和取消关注权限，以及
    * 对线程订阅的读取、写入和删除权限。 | -| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 | -|  `read:user` | 授予读取用户个人资料数据的权限。 | -|  `user:email` | 授予对用户电子邮件地址的读取权限。 | -|  `user:follow` | 授予关注或取消关注其他用户的权限。 | -| **`delete_repo`** | 授予删除可管理仓库的权限。 | -| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 | +|  `security_events` | 授予：
    对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限
    对 [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) 中安全事件的读取和写入权限
    仅在授予其他用户或服务对安全事件的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | 授予对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限。 仅在授予其他用户或服务对安全事件的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% endif %} +| **`admin:repo_hook`** | 授予对公共和私有仓库中仓库挂钩的读取、写入、ping 和删除权限。 `repo` 和 `public_repo` 作用域授予对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 | +|  `write:repo_hook` | 授予对公共或私有仓库中挂钩的读取、写入和 ping 权限。 | +|  `read:repo_hook` | 授予对公共或私有仓库中挂钩的读取和 ping 权限。 | +| **`admin:org`** | 全面管理组织及其团队、项目和成员。 | +|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 | +|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 | +| **`admin:public_key`** | 全面管理公钥。 | +|  `write:public_key` | 创建、列出和查看公钥的详细信息。 | +|  `read:public_key` | 列出和查看公钥的详细信息。 | +| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 | +| **`gist`** | 授予对 gist 的写入权限。 | +| **`通知`** | 授予：
    * 对用户通知的读取权限
    * 对线程的标记读取权限
    * 对仓库的关注和取消关注权限，以及
    * 对线程订阅的读取、写入和删除权限。 | +| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 | +|  `read:user` | 授予读取用户个人资料数据的权限。 | +|  `user:email` | 授予对用户电子邮件地址的读取权限。 | +|  `user:follow` | 授予关注或取消关注其他用户的权限。 | +| **`delete_repo`** | 授予删除可管理仓库的权限。 | +| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 | |  `read:discussion` | 授予对团队讨论的读取权限。{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 | -| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 | +| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 | +| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 | | **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除包](/github/managing-packages-with-github-packages/deleting-a-package)”。{% endif %} -| **`admin:gpg_key`** | 全面管理 GPG 密钥。 | -|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 | +| **`admin:gpg_key`** | 全面管理 GPG 密钥。 | +|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 | |  `read:gpg_key` | 列出和查看 GPG 密钥的详细信息。{% if currentVersion == "free-pro-team@latest" %} | **`工作流程`** | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流程文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容)，则工作流程文件可以在没有此作用域的情况下提交。 工作流程文件可能公开 `GITHUB_TOKEN`，它可能具有一组不同的作用域，更多信息请参阅 https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token。{% endif %} diff --git a/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md b/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md index 4c93f7e866..bc11cc044f 100644 --- a/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md @@ -18,15 +18,23 @@ versions: ### 应用 -任何人都可以在 {% data variables.product.prodname_marketplace %} 上与其他用户分享其应用程序，但只有经 {% data variables.product.company_short %} 验证的上架产品才能包含付费计划。 更多信息请参阅“[关于经验证的创作者](/developers/github-marketplace/about-verified-creators)”。 +任何人都可以在 {% data variables.product.prodname_marketplace %} 上与其他用户分享其应用程序，但只有组织拥有的应用程序才能出售。 + +要发布应用程序付费计划并显示 Marketplace 徽章，您必须完成发布者验证过程。 更多信息请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”或“[上架应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 + +组织满足要求后，组织中具有所有者权限的人可以发布其任何应用程序的付费计划。 每个具有付费计划的应用程序还要完成财务手续才能启用付款。 + +要发布具有免费计划的应用程序，只需满足上架任何应用程序的一般要求即可。 更多信息请参阅“[所有 GitHub Marketplace 上架产品的要求](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)”。 + +#### 不熟悉应用程序？ 如果您有兴趣为 {% data variables.product.prodname_marketplace %} 创建应用程序，但对于 {% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_app %} 比较陌生，请参阅“[构建 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”或“[构建 {% data variables.product.prodname_oauth_app %}](/developers/apps/building-oauth-apps)”。 +#### GitHub 应用程序与 OAuth 应用程序 + {% data reusables.marketplace.github_apps_preferred %}，尽管您可以在 {% data variables.product.prodname_marketplace %} 中上架 OAuth 和 {% data variables.product.prodname_github_app %}。 更多信息请参阅“[{% data variables.product.prodname_github_apps %} 与 {% data variables.product.prodname_oauth_app %} 之间的差异](/apps/differences-between-apps/)”和“[将 {% data variables.product.prodname_oauth_app %} 迁移到 {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)”。 -如果您对 {% data variables.product.prodname_marketplace %} 有疑问，请直接联系 {% data variables.contact.contact_support %}。 - -### 将应用程序发布到 {% data variables.product.prodname_marketplace %} +### 将应用程序发布到 {% data variables.product.prodname_marketplace %} 概述 完成创建应用程序后，您可以将其发布到 {% data variables.product.prodname_marketplace %}，以便与其他用户分享它。 过程归纳如下： @@ -38,13 +46,9 @@ versions: 1. 添加定价计划。 更多信息请参阅“[为上架产品设置定价计划](/developers/github-marketplace/setting-pricing-plans-for-your-listing)”。 -1. 检查您的应用程序是否满足在 {% data variables.product.prodname_marketplace %} 中作为免费或付费应用程序上架的要求。 更多信息请参阅“[上架应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 - 1. 阅读并接受“[{% data variables.product.prodname_marketplace %} 开发者协议](/articles/github-marketplace-developer-agreement/)”的条款。 -1. 提交要在 {% data variables.product.prodname_marketplace %} 中发布的上架信息，如果要出售应用程序，还需要请求验证。 更多信息请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication)”。 - -上架专家将联系您，提出一些问题或要求您完成其他步骤。 例如，如果您添加了付费计划，则需要完成验证过程并完成财务手续。 一旦您的上架信息得到批准，应用程序将发布到 {% data variables.product.prodname_marketplace %}。 +1. 提交要在 {% data variables.product.prodname_marketplace %} 中发布的上架信息。 更多信息请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication)”。 ### 查看应用程序的表现 @@ -52,3 +56,7 @@ versions: - “[查看上架产品的指标](/developers/github-marketplace/viewing-metrics-for-your-listing)” - “[查看上架产品的交易](/developers/github-marketplace/viewing-transactions-for-your-listing)” + +### 联系支持 + +如果您对 {% data variables.product.prodname_marketplace %} 有疑问，请直接联系 {% data variables.contact.contact_support %}。 diff --git a/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md b/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md new file mode 100644 index 0000000000..e1abdf4ddb --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md @@ -0,0 +1,43 @@ +--- +title: 关于 Marketplace 徽章 +intro: '了解您可能在 {% data variables.product.prodname_marketplace %} 上的某些应用程序和操作上架信息中看到的徽章。' +redirect_from: + - /developers/github-marketplace/about-verified-creator-badges +versions: + free-pro-team: '*' +--- + +### 对于 GitHub 应用程序 + +带有 {% octicon "verified" aria-label="The verified badge" %} 的应用程序由满足以下条件的组织所拥有： +- 已确认其域 +- 已确认其电子邮件地址可用于 {% data variables.product.prodname_dotcom %} 支持人员联系该组织 +- 对其组织要求双重身份验证 更多信息请参阅“[您的组织中需要双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)”。 + +![GitHub 应用程序的 Marketplace 徽章](/assets/images/marketplace/apps-with-verified-publisher-badge.png) + +要了解如何将此徽章添加到您的应用程序，请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。 + +有关在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求，请参阅“[在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。 + +有关如何查找要使用的应用程序，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)”。 + +### 对于 GitHub Actions + +带有 {% octicon "verified" aria-label="The verified badge" %} 或已验证创作者徽章的操作表示 {% data variables.product.prodname_dotcom %} 已验证操作的创建者为合作伙伴组织。 + +![GitHub Actions 的已验证创作者徽章](/assets/images/marketplace/verified-creator-badge-for-actions.png) + +有关如何向 {% data variables.product.prodname_marketplace %} 发布 GitHub Actions，请参阅“[在 GitHub Marketplace 中发布操作](/actions/creating-actions/publishing-actions-in-github-marketplace)”。 + +### 关于以前的应用程序验证流程 + +除了已验证创建者徽章外，您还将看到未验证和已验证的应用程序徽章。 这些应用程序是使用针对单个应用程序进行验证的旧方法来发布的。 + +![绿色的已验证和灰色的未验证徽章](/assets/images/marketplace/marketplace_verified_badges.png) + +{% note %} + +**注：**新的发布者验证流程将取代以前针对单个应用程序的验证流程。 新的发布者验证流程类似于操作的验证流程。 在旧流程下验证的应用程序将不会受到流程变更的影响。 {% data variables.product.prodname_marketplace %} 团队将联系您，提供如何迁移到基于组织的验证的详细信息。 + +{% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md new file mode 100644 index 0000000000..132f027e2a --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: 为组织申请发布者验证 +intro: '要为应用程序提供付费计划或在应用程序上架信息中包含 Marketplace 徽章，您必须完成组织的发布者验证流程。' +versions: + free-pro-team: '*' +--- + +发布者验证确保 {% data variables.product.prodname_dotcom %} 有方法联系您、您已经为组织启用双重身份验证并且您组织的域已通过验证。 + +一旦您的组织通过验证，您就可以为应用程序发布付费计划。 更多信息请参阅“[为上架产品设置定价计划](/developers/github-marketplace/setting-pricing-plans-for-your-listing)”。 + +要为应用程序提供付费计划，该应用程序必须为组织所有，并且您必须拥有该组织的所有者权限。 如果您的应用程序目前由用户帐户所有，您需要将该应用程序的所有权转让给组织。 更多信息请参阅“[转让 GitHub 应用程序的所有权](/developers/apps/transferring-ownership-of-a-github-app)”或“[转让 OAuth 应用程序的所有权](/developers/apps/transferring-ownership-of-an-oauth-app)”。 + +### 请求发布者验证 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +1. 在左侧边栏中，单击 **Developer settings**。 ![组织设置侧边栏中的开发者设置选项](/assets/images/marketplace/developer-settings-in-org-settings.png) +1. 在“Developer settings（开发者设置）”下，单击 **Publisher Verification（发布者验证）**。 ![组织设置侧边栏中的发布者验证选项](/assets/images/marketplace/publisher-verification-settings-option.png) +1. 在“Publisher Verification（发布者验证）”下，填写检查列表中的信息： + - 确保您的基本个人资料信息正确无误。 另外，确保您添加了接收 {% data variables.product.company_short %} 的更新和支持信息的最合适电子邮件地址。 + - 确保为您的组织启用双重身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)”。 + - 提交经过验证的域。 相关信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 + + ![发布者验证检查列表](/assets/images/marketplace/publisher-verification-checklist.png) + +1. 单击 **Request Verification（申请验证）**。 {% data variables.product.company_short %} 将检查您的详细信息，并在您的发布者验证完成后通知您。 + +### 延伸阅读 + +有关发布应用程序的流程，请参阅“[关于 GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)”。 diff --git a/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index d8fc7aacee..55c43e7607 100644 --- a/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,7 +60,7 @@ versions: ### 提交应用程序 -完成 {% data variables.product.prodname_marketplace %} 上架信息后，您可以在 **Overview（概览）**页面中提交您的上架信息以供审查。 您需要阅读并接收“[{% data variables.product.prodname_marketplace %} 开发者协议](/articles/github-marketplace-developer-agreement/)”，然后才可以单击 **Submit for review（提交审查）**。 提交应用程序以供审查后，上架专家将与您联系，提供有关上架流程的其他信息。 有关上架和安全审查流程的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} 入门指南](/marketplace/getting-started/)”。 +完成 {% data variables.product.prodname_marketplace %} 上架信息后，您可以在 **Overview（概览）**页面中提交您的上架信息以供审查。 您需要阅读并接收“[{% data variables.product.prodname_marketplace %} 开发者协议](/articles/github-marketplace-developer-agreement/)”，然后才可以单击 **Submit for review（提交审查）**。 提交应用程序以供审查后，上架专家将与您联系，提供有关上架流程的其他信息。 ### 删除 {% data variables.product.prodname_marketplace %} 上架信息 diff --git a/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview.md b/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview.md new file mode 100644 index 0000000000..b1bc82ae9c --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview.md @@ -0,0 +1,8 @@ +--- +title: GitHub Marketplace 概述 +intro: '了解如何在 {% data variables.product.prodname_marketplace %} 上与 {% data variables.product.company_short %} 社区分享您的应用程序或操作。' +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/developers/github-marketplace/index.md b/translations/zh-CN/content/developers/github-marketplace/index.md index d31b78bf1e..1d0f7d5d4f 100644 --- a/translations/zh-CN/content/developers/github-marketplace/index.md +++ b/translations/zh-CN/content/developers/github-marketplace/index.md @@ -9,9 +9,12 @@ versions: free-pro-team: '*' --- -{% topic_link_in_list /creating-apps-for-github-marketplace %} +{% topic_link_in_list /github-marketplace-overview %} {% link_in_list /about-github-marketplace %} - {% link_in_list /about-verified-creators %} + {% link_in_list /about-marketplace-badges %} + {% link_in_list /applying-for-publisher-verification-for-your-organization %} + +{% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /requirements-for-listing-an-app %} {% link_in_list /security-best-practices-for-apps %} {% link_in_list /customer-experience-best-practices-for-apps %} diff --git a/translations/zh-CN/content/developers/github-marketplace/receiving-payment-for-app-purchases.md b/translations/zh-CN/content/developers/github-marketplace/receiving-payment-for-app-purchases.md index dc98c350d7..8445620a44 100644 --- a/translations/zh-CN/content/developers/github-marketplace/receiving-payment-for-app-purchases.md +++ b/translations/zh-CN/content/developers/github-marketplace/receiving-payment-for-app-purchases.md @@ -13,14 +13,14 @@ versions: -After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process. +为含有付费计划的应用程序创建 {% data variables.product.prodname_marketplace %} 上架信息并得到批准后，您需要向 {% data variables.product.product_name %} 提供付款详细信息以完成财务手续。 -Once your revenue reaches a minimum of $500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs. +一旦您当月的收入达到最低 500 美元，您将收到 {% data variables.product.company_short %} 的电子付款。 此金额为 Marketplace 交易的收入减去 {% data variables.product.company_short %} 为顾及运营成本而收取的金额。 -For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward. +对于 2021 年 1 月 1 日之前发生的交易，{% data variables.product.company_short %} 扣留交易收入的 25%。 对于该日期之后发生的交易，{% data variables.product.company_short %} 仅扣留 5%。 这一变化将反映在 2021 年 1 月底收到的付款中。 {% note %} -**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/github/site-policy/github-marketplace-developer-agreement)." +**注：**有关当前定价和付款条款的详细信息，请参阅“[{% data variables.product.prodname_marketplace %} 开发者协议](/github/site-policy/github-marketplace-developer-agreement)”。 {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md index bf3f0debce..7deea47e66 100644 --- a/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -48,18 +48,21 @@ versions: ### 付费应用程序的要求 -除了上述对所有应用程序的要求之外，作为付费服务在 {% data variables.product.prodname_marketplace %} 上提供的每个应用程序还必须满足以下要求： +要在 {% data variables.product.prodname_marketplace %} 上发布应用程序的付费计划，您的应用程序必须由身份为经验证发布者的组织所拥有。 有关验证流程或转让应用程序所有权的更多信息，请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。 + +如果您的应用程序已发布，并且您是经验证的发布者，则您可以使用定价计划编辑器发布新的付费计划。 更多信息请参阅“[为上架产品设置定价计划](/developers/github-marketplace/setting-pricing-plans-for-your-listing)”。 + +要发布付费应用程序（或提供付费计划的应用程序），您还必须满足以下要求： - {% data variables.product.prodname_github_app %} 应至少有 100 个安装设施。 - {% data variables.product.prodname_oauth_app %} 应至少有 200 个用户。 - 所有付费应用程序必须处理关于新购买、升级、降级、取消和免费试用的 {% data variables.product.prodname_marketplace %} 购买事件。 更多信息请参阅下面的“[付费应用程序的计费要求](#billing-requirements-for-paid-apps)”。 -- 发布组织必须具有经过验证的域，并且必须启用双重身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)”。 -当您准备在 {% data variables.product.prodname_marketplace %} 上发布应用程序时，您必须请求验证上架信息。 +当您准备在 {% data variables.product.prodname_marketplace %} 上发布应用程序时，您必须请求验证应用程序上架信息。 {% note %} -验证过程对组织开放。 {% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何进行验证，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 +**注：**{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何将应用程序转让给组织，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index b625589a71..18cba3fad5 100644 --- a/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -19,12 +19,14 @@ versions: ### 关于设置定价计划 -如果要在 {% data variables.product.prodname_marketplace %} 上出售应用程序，则需要在发布应用程序上架信息时请求验证。 在验证过程中，上架专家会检查组织的身份和安全设置。 上架专家还将引导组织完成财务手续。 更多信息请参阅“[在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。 - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何进行验证，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 - {% data variables.product.prodname_marketplace %} 提供几种不同类型的定价计划。 更多信息请参阅“[{% data variables.product.prodname_marketplace %} 的定价计划](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)”。 +要为应用程序提供付费计划，该应用程序必须由已完成发布者验证流程并满足特定条件的组织所拥有。 更多信息请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”和“[在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。 + +如果含有付费计划的应用程序已发布，并且您是经验证的发布者，则您可以在 Marketplace 应用程序上架设置中的“Edit a pricing plan（编辑定价计划）”页面发布新的付费计划。 + +![发布此计划按钮](/assets/images/marketplace/publish-this-plan-button.png) + ### 关于保存定价计划 您可以将定价计划保存为草稿或已发布状态。 如果尚未提交 {% data variables.product.prodname_marketplace %} 上架信息以供审批，则已发布的计划与计划草案的运作方式相同，直到您的上架信息得到批准并显示在 {% data variables.product.prodname_marketplace %} 上。 计划草案允许您创建和保存新的定价计划，而无需在您的 {% data variables.product.prodname_marketplace %} 上架页面上提供它们。 一旦您在已发布的上架信息中发布定价计划，它就可以立即供客户购买。 您最多可以发布 10 个定价计划。 diff --git a/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md index 09942f2a8a..d2fbb3500a 100644 --- a/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md +++ b/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -1,6 +1,6 @@ --- title: 提交要发布的上架信息 -intro: '您可以提交上架产品以供 {% data variables.product.prodname_dotcom %} 社区使用。' +intro: '要完成应用程序上架信息提交，您可以请求上架专家进行审查。' redirect_from: - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - /developers/github-marketplace/submitting-your-listing-for-review @@ -8,30 +8,14 @@ versions: free-pro-team: '*' --- +在您的应用程序上架信息满足 {% data variables.product.prodname_marketplace %} 要求后，您可以提交该应用程序。 关于应用程序上架要求的概述，请参阅“[上架应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 +1. 在应用程序上架信息页面的左上角，单击 **Overview（概述）**。 有关查找应用程序上架信息页面的信息，请参阅“[起草应用程序上架信息](/developers/github-marketplace/drafting-a-listing-for-your-app)”。 -完成应用程序的上架信息后，您将会看到两个按钮，允许您请求在验证或不验证的情况下发布上架产品。 如果您在上架信息中发布了任何付费定价计划，则“发布而不验证”的 **Request（请求）**按钮将被禁用。 + ![Marketplace 上架信息草稿的选项概述](/assets/images/marketplace/edit-marketplace-listing-overview.png) -![未经验证和已验证请求按钮](/assets/images/marketplace/marketplace-request-button.png) +2. 要提交已完成的应用程序上架信息，请单击 **Request review（请求审查）**。 -{% data reusables.marketplace.launch-with-free %} + !["将应用程序发布到 Marketplace"检查列表，底部有提交按钮](/assets/images/marketplace/publish-your-app-checklist-and-submission.png) -提交上架信息以供审查后，上架专家将联系您，要求您提供更多信息。 - -有关创建和提交上架信息的流程概述，请参阅“[关于 {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)”。 - -### 请求验证发布的前提条件 - -请求验证上架信息之前，您需要将 {% data variables.product.prodname_marketplace %} 帐单流程和 web 挂钩集成到应用程序中。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 - -如果已满足上架要求并且已集成 {% data variables.product.prodname_marketplace %} API，请继续提交您的上架信息。 更多信息请参阅“[上架应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 - -{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何执行此操作的信息，请参阅下面的“[在提交之前将应用程序转让给组织](#transferring-an-app-to-an-organization-before-you-submit)”。 - -### 在提交之前将应用程序转让给组织 - -无法出售由用户帐户拥有的应用程序。 您需要将应用程序转让给已成为经验证创建者的组织，或者可请求验证应用程序上架信息的组织。 更多信息请参阅： - -1. “[从头开始创建组织](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)” - -1. “[转让 GitHub 应用程序的所有权](/developers/apps/transferring-ownership-of-a-github-app)”或“[转让 OAuth 应用程序的所有权](/developers/apps/transferring-ownership-of-an-oauth-app)” +上架专家将联系您并提供更多信息。 diff --git a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index 12d3e480fc..c211742c78 100644 --- a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- title: 查看上架产品的交易 -intro: '{% data variables.product.prodname_marketplace %} 交易页面允许您下载和查看 {% data variables.product.prodname_marketplace %} 上架产品的所有交易。 You can view transactions for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.' +intro: '{% data variables.product.prodname_marketplace %} 交易页面允许您下载和查看 {% data variables.product.prodname_marketplace %} 上架产品的所有交易。 您可以查看 {% data variables.product.prodname_github_app %} 在过去一天（24 小时）、一周、一月或整个上架期间的交易。' redirect_from: - /marketplace/github-marketplace-transactions versions: diff --git a/translations/zh-CN/content/developers/overview/secret-scanning.md b/translations/zh-CN/content/developers/overview/secret-scanning.md index eb3e2161cf..3afa2f91ab 100644 --- a/translations/zh-CN/content/developers/overview/secret-scanning.md +++ b/translations/zh-CN/content/developers/overview/secret-scanning.md @@ -1,6 +1,7 @@ --- title: 秘密扫描 intro: '作为服务提供者，您可以与 {% data variables.product.prodname_dotcom %} 合作，通过密码扫描保护您的密码令牌格式，该扫描将搜索意外提交的密码格式，并且可以发送到服务提供者的验证端点。' +miniTocMaxHeadingLevel: 4 redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -8,52 +9,52 @@ versions: free-pro-team: '*' --- - -{% data variables.product.prodname_dotcom %} 扫描仓库查找已知的密码格式，以防止欺诈性使用意外提交的凭据。 默认情况下，密码扫描发生在公共仓库上，但仓库管理员或组织所有者可以在私有仓库上启用它。 作为服务提供者，您可以与 {% data variables.product.prodname_dotcom %} 合作，让您的密码格式包含在我们的密码扫描中。 +{% data variables.product.prodname_dotcom %} 扫描仓库查找已知的密码格式，以防止欺诈性使用意外提交的凭据。 {% data variables.product.prodname_secret_scanning_caps %} 默认情况下发生在公共仓库上，但仓库管理员或组织所有者可以在私有仓库上启用它。 作为服务提供者，您可以与 {% data variables.product.prodname_dotcom %} 合作，让您的密码格式包含在我们的 {% data variables.product.prodname_secret_scanning %} 中。 在公共仓库中找到密码格式的匹配项时，将发送有效负载到您选择的 HTTP 端点。 -在配置为密码扫描的私有仓库中找到密码格式的匹配项时，仓库管理员将收到警报，并且可以查看和管理 {% data variables.product.prodname_dotcom %} 上的密码扫描结果。 更多信息请参阅“[管理来自密码扫描的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。 +在配置为 {% data variables.product.prodname_secret_scanning %} 的私有仓库中找到密码格式的匹配项时，仓库管理员将收到警报，并且可以查看和管理 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_secret_scanning %} 结果。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。 {% note %} -**注：**私有仓库的密码扫描目前处于测试阶段。 +**注：**私有仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于测试阶段。 {% endnote %} -本文介绍作为服务提供者如何与 {% data variables.product.prodname_dotcom %} 合作并加入密码扫描计划。 +本文介绍作为服务提供者如何与 {% data variables.product.prodname_dotcom %} 合作并加入 {% data variables.product.prodname_secret_scanning %} 计划。 -### 密码扫描流程 +### {% data variables.product.prodname_secret_scanning %} 流程 -##### 密码扫描在公共仓库中的工作方式 +##### {% data variables.product.prodname_secret_scanning %} 如何在公共仓库中工作 -下图总结了在公共仓库中进行密码扫描并将任何匹配项发送到服务提供者的验证端点的流程。 +下图总结了在公共仓库中进行 {% data variables.product.prodname_secret_scanning %} 并将任何匹配项发送到服务提供者的验证端点的流程。 -![显示扫描密码并向服务提供者的验证端点发送匹配项的流程图](/assets/images/secret-scanning-flow.png "密码扫描流程") +![显示扫描密码并向服务提供者的验证端点发送匹配项的流程图](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} 流程") -### 在 {% data variables.product.prodname_dotcom %} 上加入密码扫描计划 +### 在 {% data variables.product.prodname_dotcom %} 上加入 {% data variables.product.prodname_secret_scanning %} 计划 1. 联系 {% data variables.product.prodname_dotcom %} 以启动流程。 1. 识别要扫描的相关密码，并创建正则表达式来捕获它们。 -1. 针对在公共仓库中发现的密码匹配项，创建一个密码警报服务，以便从 {% data variables.product.prodname_dotcom %} 接受包含密码扫描消息有效负载的 web 挂钩。 +1. 针对在公共仓库中发现的密码匹配项，创建一个密码警报服务，以便从 {% data variables.product.prodname_dotcom %} 接受包含 {% data variables.product.prodname_secret_scanning %} 消息有效负载的 web 挂钩。 1. 在密码警报服务中实施签名验证。 1. 在密码警报服务中实施密码撤销和用户通知。 +1. 提供误报的反馈（可选）。 #### 联系 {% data variables.product.prodname_dotcom %} 以启动流程 -要启动注册流程，请发送电子邮件至 secret-scanning@github.com。 +要启动注册流程，请发送电子邮件至 secret-scanning@github.com。 -您将收到有关密码扫描计划的详细信息，您需要同意 {% data variables.product.prodname_dotcom %} 的参与条款才能继续。 +您将收到有关 {% data variables.product.prodname_secret_scanning %} 计划的详细信息，您需要同意 {% data variables.product.prodname_dotcom %} 的参与条款才能继续。 #### 识别您的密码并创建正则表达式 -要扫描您的密码，{% data variables.product.prodname_dotcom %} 需要您要包含在密码扫描计划中的每个密码的以下信息： +要扫描您的密码，{% data variables.product.prodname_dotcom %} 需要您要包含在 {% data variables.product.prodname_secret_scanning %} 计划中的每个密码的以下信息： * 密码类型的唯一、人类可读的名称。 稍后我们将使用它来生成消息有效负载中的 `Type` 值。 * 查找密码类型的正则表达式。 尽可能精确，因为这样可以减少误报的数量。 * 从 {% data variables.product.prodname_dotcom %} 接收消息的端点的 URL。 对于每个密码类型，这不必是唯一的。 -将此信息发送到 secret-scanning@github.com。 +将此信息发送到 secret-scanning@github.com。 #### 创建密码警报服务 @@ -61,7 +62,7 @@ versions: ##### 发送到端点的 POST 示例 -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -94,7 +95,7 @@ Content-Length: 0123 假设您收到以下消息，下面的代码段演示如何执行签名验证。 该代码还假设您已经使用生成的 PAT 设置了一个名为 `GITHUB_PRODUCTION_TOKEN` 的环境变量 (https://github.com/settings/tokens)。 该令牌不需要设置任何权限。 **发送到验证端点的消息示例** -``` +```http POST / HTTP/1.1 Host: HOST Accept: */* @@ -319,4 +320,44 @@ puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), #### 在密码警报服务中实施密码撤销和用户通知 -对于公共仓库中的密码扫描，您可以增强密码警报服务，以撤销泄露的密码并通知受影响的用户。 如何在密码警报服务中实现此功能取决于您，但我们建议您考虑 {% data variables.product.prodname_dotcom %}向您发送的公开和泄露示警消息所涉及的任何密码。 +对于公共仓库中的 {% data variables.product.prodname_secret_scanning %}，您可以增强密码警报服务，以撤销泄露的密码并通知受影响的用户。 如何在密码警报服务中实现此功能取决于您，但我们建议您考虑 {% data variables.product.prodname_dotcom %}向您发送的公开和泄露示警消息所涉及的任何密码。 + +#### 提供误报的反馈 + +我们在合作伙伴响应中收集有关检测到的各个密码有效性的反馈。 如果您愿意参与，请发送电子邮件到 secret-scanning@github.com。 + +向您报告密码时，我们会发送一个 JSON 数组，其中有包含令牌、类型标识符和提交 URL 的每个元素。 当您向我们发送反馈时，您将向我们发送有关检测到的令牌是真凭据还是假凭据的信息。 我们接受以下格式的反馈。 + +您可以向我们发送原始令牌： + +``` +[ + { + "token_raw": "The raw token", + "token_type": "ACompany_API_token", + "label": "true_positive" + } +] +``` +您还可以使用 SHA-256 对原始令牌执行单向加密哈希后，以哈希形式提供令牌： + +``` +[ + { + "token_hash": "The SHA-256 hashed form of the raw token", + "token_type": "ACompany_API_token", + "label": "false_positive" + } +] +``` +几个要点： +- 您应该只向我们发送令牌的原始形式 ("token_raw") 或哈希形式，而不要同时发送这两种形式。 +- 对于原始令牌的哈希形式，您只能使用 SHA-256 对令牌进行哈希处理，而不能使用任何其他哈希算法。 +- 用标签指示令牌为实报 ("true_positive") 还是误报 ("false_positive")。 只允许使用这两个小写的文字字符串。 + +{% note %} + +**注：**对于提供误报数据的合作伙伴，我们的请求超时设置为更高（即 30 秒）。 如果您需要超过 30 秒的超时设置，请发送电子邮件至 secret-scanning@github.com。 + +{% endnote %} + diff --git a/translations/zh-CN/content/discussions/index.md b/translations/zh-CN/content/discussions/index.md index 2193cabe0b..a264b69de0 100644 --- a/translations/zh-CN/content/discussions/index.md +++ b/translations/zh-CN/content/discussions/index.md @@ -22,7 +22,7 @@ featuredLinks: - /discussions/guides/finding-discussions-across-multiple-repositories - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: free-pro-team: '*' @@ -43,7 +43,7 @@ versions: {% render 'discussions-community-card' for discussionsCommunityExamples as example %}
    {% if discussionsCommunityExamples.length > 6 %} - + {% endif %}
    {% octicon "search" width="24" %}
    diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..49c74187ef --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -0,0 +1,18 @@ +--- +title: 关于 Campus Advisors +intro: '作为讲师或辅导员，可在您的学校通过 Campus Advisors 培训和支持学习使用 {% data variables.product.prodname_dotcom %}。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-advisors + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +教授、教师和辅导员可使用 Campus Advisors 在线培训掌握 Git 和 {% data variables.product.prodname_dotcom %}，通过 {% data variables.product.prodname_dotcom %} 学习最佳教学方法。 更多信息请参阅 "[Campus Advisors](https://education.github.com/teachers/advisors)"。 + +{% note %} + +**注：**作为讲师，无法为学生创建 {% data variables.product.prodname_dotcom %} 帐户。 学生必须创建自己的 {% data variables.product.prodname_dotcom %} 帐户。 + +{% endnote %} diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..20d9a1647b --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -0,0 +1,12 @@ +--- +title: 关于 Campus Experts +intro: '作为学生，可通过 {% data variables.product.prodname_dotcom %} Campus Experts 培训学习必要的技能来构建学校的技术社区和实际作品集。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-campus-experts + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +作为 {% data variables.product.prodname_dotcom %} Campus Expert，学习公共演讲技能、技术写作、社区领导和软件开发技能。 更多信息请参阅 "[Campus Experts](https://education.github.com/students/experts)"。 diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..ebf4eeb164 --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,32 @@ +--- +title: 关于适用于教育者和研究人员的 GitHub Education +intro: '{% data variables.product.prodname_education %} 提供各种工具帮助教育者和研究人员在课堂内外更有效地工作。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 适用于教育者的 {% data variables.product.prodname_education %} + +利用 {% data variables.product.prodname_education %} 适用于各级教育者的工具和服务，您可以： + - 使用 [{% data variables.product.prodname_classroom %}](https://classroom.github.com) 分发代码、向学生提供反馈以及收集 {% data variables.product.prodname_dotcom %} 中的作业。 + - 加入我们的 [{% data variables.product.prodname_education_community %}](https://education.github.com/forum)，以与全球各地的同行讨论技术教育的当前趋势。 + - 访问和调整我们用于教授 Git 和 {% data variables.product.prodname_dotcom %} 的[开源课程计划](https://education.github.community/t/open-source-lesson-plans/1591)。 + - [申请 {% data variables.product.prodname_dotcom %} swag 包](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33)，其中包括学生用教育资料和重要工具。 + {% data reusables.education.apply-for-team %} + +### 适用于研究人员的 {% data variables.product.prodname_education %} + +利用 {% data variables.product.prodname_education %} 适用于研究人员的工具和服务，您可以： + - 在 {% data variables.product.prodname_dotcom %} 上与世界各地的其他人协作处理研究工作。 + - [了解](https://education.github.com/stories)全球各地的学术机构如何使用 {% data variables.product.prodname_dotcom %} 进行研究。 + {% data reusables.education.apply-for-team %} + +### 延伸阅读 + +- "[关于学生版 {% data variables.product.prodname_education %}](/articles/about-github-education-for-students)" diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..c1695512cc --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -0,0 +1,22 @@ +--- +title: 关于学生版 GitHub Education +intro: '{% data variables.product.prodname_education %} 让学生免费使用 {% data variables.product.prodname_dotcom %} 合作伙伴的各种开发工具，为他们提供真实的体验。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education-for-students + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +将 {% data variables.product.prodname_dotcom %} 用于学校项目是一种与别人协作的实用方式，可创建展示真实世界的作品集。 + +{% data reusables.education.about-github-education-link %} + +拥有 {% data variables.product.prodname_dotcom %} 帐户的每个人都可通过 {% data variables.product.prodname_free_user %} 在无限的公共和私有仓库中协作。 作为学生，您也可以申请 {% data variables.product.prodname_student_pack %}，以免费使用专业开发者使用的工具和服务。 更多信息请参阅“[申请学生开发包](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)”和 [{% data variables.product.prodname_education %}](https://education.github.com/pack)。 + +如果您是 FIRST 机器人俱乐部的成员，您的辅导员可以申请教育者折扣，这样您的团队可以免费使用 {% data variables.product.prodname_team %}（允许无限的用户和私有仓库） 进行协作。 更多信息请参阅“[申请教育者或研究人员折扣](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)”。 + +### 延伸阅读 + +- "[关于教育者和研究人员版 {% data variables.product.prodname_education %}](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md new file mode 100644 index 0000000000..54488e2584 --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -0,0 +1,24 @@ +--- +title: 关于 GitHub Education +intro: '{% data variables.product.prodname_education %} 为希望为其社区最大利用 {% data variables.product.prodname_dotcom %} 并且同意特定计划要求的学校提供特殊的免费产品。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +如果您的学校同意遵守特定要求，则您的中学、大学或训练营可获得 {% data variables.product.prodname_education %}，其中免费提供最佳 {% data variables.product.prodname_dotcom %}，包括： +- {% data variables.product.prodname_ghe_cloud %} 和/或 {% data variables.product.prodname_ghe_server %} +- 通过 Campus Advisor 计划为教师提供 Git 和 {% data variables.product.prodname_dotcom %} 培训 +- 自动访问高级 {% data variables.product.prodname_education %} 功能，如 {% data variables.product.prodname_student_pack %} +- 通过 Campus Experts 计划为学生提供领导力发展和技术培训 + +更多信息请参阅[官方 {% data variables.product.prodname_education %}](https://education.github.com/partners/schools) 网页。 + +教师可以使用 {% data variables.product.prodname_education %} 管理软件开发课程。 {% data variables.product.prodname_classroom %} 可用于发布代码、提供反馈，以及使用 {% data variables.product.product_name %} 管理课程。 更多信息请参阅“[使用 {% data variables.product.prodname_classroom %} 管理课程](/education/manage-coursework-with-github-classroom)”。 + +要详细了解学生领导者和教师的培训计划，请参阅 "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" 和 "[Campus Advisors](https://education.github.com/teachers/advisors)"。 + +如果您是学生或教师并且您的学校未作为 {% data variables.product.prodname_education %} 学校与 {% data variables.product.prodname_dotcom %} 合作，您也可以个人申请使用 {% data variables.product.prodname_dotcom %} 的折扣。 更多信息请参阅“[使用 {% data variables.product.prodname_dotcom %} 做家庭作业](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)”或“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)”。 diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..344baf6c43 --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,54 @@ +--- +title: 申请学生开发包 +intro: '作为学生，可以申请 {% data variables.product.prodname_student_pack %}，其中包括 {% data variables.product.prodname_dotcom %} 合作伙伴的特惠和福利。' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 要求 + +要获得申请 {% data variables.product.prodname_student_pack %} 的资格，必须： +- 现正攻读学位或文凭授予课程，如高中、初中、大专、大学、自主学习或类似教育机构 +- 具有学校发放的可验证电子邮件地址，或者上传能证明您目前学生身份的文档 +- 拥有 [{% data variables.product.prodname_dotcom %} 用户帐户](/articles/signing-up-for-a-new-github-account) +- 至少年满 13 岁 + +证明您现任学生身份的文件包括具有当前注册日期的学校 ID 照片、班级课程表、成绩单以及附属关系或入学签到函。 + +在作为学生期间，可能会提示您定期重新验证目前的学业身份。 + +{% note %} + +**注：**不能在不同帐户之间转让学生折扣。 如有多个帐户想申请折扣，请考虑[合并](/articles/merging-multiple-user-accounts)您的用户帐户并根据需要[重命名](/articles/changing-your-github-username)保留的帐户。 + +{% endnote %} + +有关续订 {% data variables.product.prodname_student_pack %} 的信息，请参阅“[到期和续订](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)”。 + +### 申请 {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. 在 "Which best describes your academic status?"（哪一项最准确描述了您的学业身份？）下，选择 **Student（学生）**。 ![选择学籍](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### 到期和续订 + +在您的 {% data variables.product.prodname_student_pack %} 访问权限到期后，如果您仍有资格，您可以重新申请，但有些合作伙伴可能不提供续订服务。 合作伙伴的大多数计时特惠在您设置后便开始。 更多信息请参阅 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) 页面。 + +要查看您对 {% data variables.product.prodname_student_pack %} 的免费访问何时到期，请访问您帐户的[帐单设置](https://github.com/settings/billing)。 + +### 延伸阅读 + +- "[我的 {% data variables.product.prodname_student_pack %} 申请为什么未获得批准？](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..2644965d95 --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,58 @@ +--- +title: 申请教育者或研究人员折扣 +intro: '如果您是教育者或研究人员，可以为组织申请免费获取 {% data variables.product.prodname_team %}。' +redirect_from: + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### 关于教育者和研究人员折扣 + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +有关在 {% data variables.product.product_name %} 上创建用户帐户的更多信息，请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/github/getting-started-with-github/signing-up-for-a-new-github-account)”。 + +### 申请教育者或研究人员折扣 + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### 升级组织 + +在教育者或研究人员折扣申请获得批准后，您可以将用于学习社区的组织升级到 {% data variables.product.prodname_team %}，以便免费访问无限的用户和具有完全功能的私有仓库。 您可以升级现有组织或创建新组织进行升级。 + +#### 升级现有组织 + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### 升级新组织 + +{% data reusables.education.upgrade-page %} +1. 单击 {% octicon "plus" aria-label="The plus symbol" %} **Create an organization（创建组织）**。 ![创建组织按钮](/assets/images/help/education/create-org-button.png) +3. 阅读信息，然后单击 **Create organization（创建组织）**。 ![创建组织按钮](/assets/images/help/education/create-organization-button.png) +4. 在“Choose a plan（选择计划）”下，单击 **选择 {% data variables.product.prodname_free_team %}**。 +5. 按照提示创建组织。 +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### 延伸阅读 + +- "[为什么我的教育者或研究人员折扣申请未获得批准？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %} 视频](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md new file mode 100644 index 0000000000..563fec4118 --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: 探索通过 GitHub Education 教学和学习的好处 +shortTitle: 探索 +intro: 了解 {% data variables.product.prodname_education %} 如何使您的课堂、功课或研究受益，以及如何申请免费使用 {% data variables.product.company_short %} 合作伙伴的各种开发工具。 +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### 目录 + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..71ecc8543e --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,12 @@ +--- +title: 在教育机构使用 GitHub +intro: '通过 {% data variables.product.prodname_education %} 以及我们针对学生和讲师的各种培训计划，利用 {% data variables.product.prodname_dotcom %} 使您机构的学生、讲师和 IT 员工最大限度地获益。' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..bed1f2dbdf --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,12 @@ +--- +title: 使用 GitHub 做功课 +intro: '作为学生，使用 {% data variables.product.prodname_dotcom %} 在您的学校项目上协作，并构建真实世界的体验。' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..97f56b2915 --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,12 @@ +--- +title: 在课堂上和研究中使用 GitHub +intro: '作为教育工作者或研究人员，使用 {% data variables.product.prodname_dotcom %} 在课堂上、学生或研究小组中协作完成您的工作等等。' +mapTopic: true +redirect_from: + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..69a6277b8c --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,68 @@ +--- +title: 为什么我的学生开发包申请未获得批准？ +intro: '查看申请 {% data variables.product.prodname_student_pack %}未获批准的常见原因，并了解成功重新申请的窍门。' +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 +versions: + free-pro-team: '*' +--- + +{% tip %} + +**提示：** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 学术关联文档不明确 + +如果您上传的图像没有明确地确定您当前的学术地位，则我们需要您的学术地位的进一步证明。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 使用具有未经验证域的学术电子邮件 + +如果您的学术电子邮件地址有未经验证的域，则我们需要您的学术地位的进一步证明。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 使用来自电子邮件政策宽松的学校的学术电子邮件 + +如果您的学校在付费学生注册之前发出电子邮件地址，则我们需要您的学术地位的进一步证明。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +如果您有关于学校域的其他疑问或问题，请让学校的 IT 人员联系我们。 + +### 学术电子邮件地址已占用 + +如果您的学术电子邮件地址已用于为其他 {% data variables.product.prodname_dotcom %} 帐户申请 {% data variables.product.prodname_student_pack %}，则该折扣到期之前，您无法重复使用该学术电子邮件地址成功申请其他 {% data variables.product.prodname_student_pack %}。 + +{% note %} + +**注：**维护多个个人帐户违反了 {% data variables.product.prodname_dotcom %} [服务条款](/articles/github-terms-of-service/#3-account-requirements)。 + +{% endnote %} + +如果您有多个个人用户帐户，则必须合并您的帐户。 要保留折扣，请保留已授予折扣的帐户。 您可以通过将所有电子邮件地址添加到保留的帐户来重命名保留的帐户，并保留您的贡献历史记录。 + +更多信息请参阅： +- “[合并多个用户帐户](/articles/merging-multiple-user-accounts)” +- “[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)” +- “[添加电子邮件地址到 {% data variables.product.prodname_dotcom %} 帐户](/articles/adding-an-email-address-to-your-github-account)” + +### 学生身份不合格 + +以下情况时，您没有资格获得 {% data variables.product.prodname_student_pack %}： +- 您已注册参加不属于 [{% data variables.product.prodname_dotcom %} 校园计划](https://education.github.com/schools)的非正式学习计划，但未注册参加授予学位或文凭的学习课程。 +- 您未满 13 岁。 + +您的讲师仍可申请 {% data variables.product.prodname_education %} 折扣供课堂使用。 如果您是编程学校或训练营的学生，并且您的学校参加 [{% data variables.product.prodname_dotcom %} 校园计划](https://education.github.com/schools)，您将有资格获得 {% data variables.product.prodname_student_pack %}。 + +### 延伸阅读 + +- “[申请学生开发包](/articles/applying-for-a-student-developer-pack)” +- “[申请学生开发包](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)” diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..7b3368038c --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,46 @@ +--- +title: 为什么我的教育工作者或研究人员折扣申请未获得批准？ +intro: 查看申请教育工作者或研究人员折扣未获批准的常见原因，并了解成功重新申请的窍门。 +redirect_from: + - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**提示：** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 关联文档证明不明确 + +如果您上传的图像无法明确地确定您目前在学校或大学工作，则必须重新申请并上传您的教职员 ID 或雇主证明信的其他图像，其中须含有明确信息。 + +{% data reusables.education.pdf-support %} + +### 使用具有未经验证域的学术电子邮件 + +如果您的学术电子邮件地址有未经验证的域，则我们可能需要您的学术地位的进一步证明。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### 使用来自电子邮件政策宽松的学校的学术电子邮件 + +如果您学校的校友和退休教师终身可以访问学校发出的电子邮件地址，则我们可能需要您的学术地位的进一步证明。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +如果您有关于学校域的其他疑问或问题，请让学校的 IT 人员联系我们。 + +### 非学生申请学生开发包 + +教育工作者或研究人员没有资格获得 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)随附的合作伙伴优惠。 当您重新申请时，确保选择 **Faculty（教职工）**来描述您的学术地位。 + +### 延伸阅读 + +- “[申请教育工作者或研究人员折扣](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)” diff --git a/translations/zh-CN/content/education/guides.md b/translations/zh-CN/content/education/guides.md index 1a64df81ed..1fb0b3562b 100644 --- a/translations/zh-CN/content/education/guides.md +++ b/translations/zh-CN/content/education/guides.md @@ -12,8 +12,8 @@ versions: - [注册新 {% data variables.product.prodname_dotcom %} 帐户](/github/getting-started-with-github/signing-up-for-a-new-github-account) - [Git 和 {% data variables.product.prodname_dotcom %} 快速入门 ](/github/getting-started-with-github/quickstart) -- [申请教育者或研究人员折扣](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) -- [申请学生开发包](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) +- [申请教育者或研究人员折扣](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) +- [申请学生开发包](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) ### 使用 {% data variables.product.company_short %} 运行软件开发课程 @@ -32,7 +32,7 @@ versions: 将 {% data variables.product.prodname_dotcom %} 并入您的教育，并使用与专业人士相同的工具。 - [Git 和 {% data variables.product.prodname_dotcom %} 学习资源](/github/getting-started-with-github/git-and-github-learning-resources) -- [使用 {% data variables.product.prodname_dotcom %} 做功课](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork) +- [使用 {% data variables.product.prodname_dotcom %} 做功课](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork) - [试用 {% data variables.product.prodname_desktop %}](/desktop) - [试用 {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) @@ -41,5 +41,5 @@ versions: 参与社区，从 {% data variables.product.company_short %} 获得培训，并学习或教授新技能。 - [{% data variables.product.prodname_education_community %}](https://education.github.community) -- [关于 Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) -- [关于 Campus Advisors](/education/teach-and-learn-with-github-education/about-campus-advisors) +- [关于 Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) +- [关于 Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) diff --git a/translations/zh-CN/content/education/index.md b/translations/zh-CN/content/education/index.md index 55254ec12e..92489bafe5 100644 --- a/translations/zh-CN/content/education/index.md +++ b/translations/zh-CN/content/education/index.md @@ -6,16 +6,16 @@ introLinks: quickstart: /education/quickstart featuredLinks: guides: - - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack - - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount - - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution guideCards: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /github/getting-started-with-github/git-and-github-learning-resources - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom popular: - - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research - /desktop - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom @@ -41,5 +41,5 @@ versions: free-pro-team: '*' --- - + diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index c2ed5aa2e5..29f78c591e 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ versions: ### 延伸阅读 -- "[使用 {% data variables.product.prodname_education %} 教学和学习](/education/teach-and-learn-with-github-education)" +- "[探索使用 {% data variables.product.prodname_education %} 教学的好处](/education/teach-and-learn-with-github-education)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 98e08b1a2b..f41c1f0504 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -140,6 +140,6 @@ redirect_from: ### 延伸阅读 -- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" - "[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" - {% data variables.product.prodname_education %} 社区中的[在小组作业中使用现有团队吗？](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md index c88a18f54f..8689e90b07 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -11,8 +11,6 @@ redirect_from: 要将模板仓库用于作业，模板仓库必须由您的组织拥有，或者模板仓库的可见性必须是公共的。 -{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} 更多信息请参阅“[配置作业仓库的默认设置](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)”。 - ### 延伸阅读 - "[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index d6f715b922..969d76dd1c 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -120,5 +120,5 @@ redirect_from: ### 延伸阅读 -- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)" +- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" - "[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md index 6814b44119..5f0749d6d7 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md @@ -19,7 +19,6 @@ versions: {% link_in_list /create-an-assignment-from-a-template-repository %} {% link_in_list /leave-feedback-with-pull-requests %} {% link_in_list /use-autograding %} - {% link_in_list /configure-default-settings-for-assignment-repositories %} {% link_in_list /connect-a-learning-management-system-to-github-classroom %} {% topic_link_in_list /integrate-github-classroom-with-an-ide %} diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index 2d7b187420..76cfa929ce 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -102,5 +102,5 @@ redirect_from: {% data reusables.classroom.click-settings %} 1. 在“Delete this classroom（删除此教室）”右侧，单击 **Delete classroom（删除教室）**。 !["删除仓库"按钮](/assets/images/help/classroom/click-delete-classroom-button.png) 1. **阅读警告**。 -1. 要验证删除的是否为正确的教室，请键入要删除的教室的名称。 ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. 要验证删除的是否为正确的教室，请键入要删除的教室的名称。 ![用于删除包含警告的教室的模式和教室名称的文本字段](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) 1. 单击 **Delete classroom（删除教室）**。 !["删除教室"按钮](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md index 6261f33645..851bcd2e3f 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -4,5 +4,8 @@ intro: 了解如何设置课堂和作业。 mapTopic: true versions: free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories + - /education/manage-coursework-with-github-classroom/probot-settings --- diff --git a/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index cc15409f9f..c59981920c 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -33,8 +33,8 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 5. 输入最多两个您希望通知发送到的电子邮件地址，用空格分隔。 如果要将电子邮件发送到两个以上的帐户，请将其中一个电子邮件地址设为群组电子邮件地址。 ![电子邮件地址文本框](/assets/images/help/settings/email_services_addresses.png) -6. 如果您操作自己的服务器，可通过**秘密**令牌验证电子邮件的真实性。 此令牌随电子邮件作为 `Approved` 标头发送。 如果 `Approved` 标头与您发送的令牌匹配，则可以信任该电子邮件来自 {% data variables.product.product_name %}。 ![电子邮件密码文本框](/assets/images/help/settings/email_services_token.png) -7. 单击 **Save settings（保存设置）**。 ![Save settings 按钮](/assets/images/help/settings/save_notification_settings.png) +1. 如果您操作自己的服务器，可通过 **Approved 标头**验证电子邮件的真实性。 **Approved 标头**是您在此字段中输入的令牌或密码，它将随电子邮件一起发送。 如果电子邮件的 `Approved` 标头与令牌匹配，则可以信任该电子邮件来自 {% data variables.product.product_name %}。 ![电子邮件已批准标头文本框](/assets/images/help/settings/email_services_approved_header.png) +7. 单击 **Setup notifications（设置通知）**。 ![设置通知按钮](/assets/images/help/settings/setup_notifications_settings.png) ### 延伸阅读 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} diff --git a/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md b/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md index b6e3fde060..2aa6238a53 100644 --- a/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md +++ b/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md @@ -23,7 +23,7 @@ redirect_from: {% endnote %} {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 您也可以重命名默认分支。 更多信息请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md b/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md index 0357c13f70..56f33a1c34 100644 --- a/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md +++ b/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md @@ -4,6 +4,7 @@ intro: 您可以更改仓库中分支的名称。 permissions: 拥有仓库写入权限的人可重命名仓库中的分支。 具有管理员权限的人可以重命名默认分支。 versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- ### 关于重命名分支 @@ -19,3 +20,15 @@ versions: 1. 在分支列表中，在要重命名的分支的右侧，单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![要重命名的分支右侧的铅笔图标](/assets/images/help/branch/branch-rename-edit.png) 1. 为分支输入新名称。 ![输入新分支名称的文本字段](/assets/images/help/branch/branch-rename-type.png) 1. 查看有关本地环境的信息，然后单击 **Rename branch（重命名分支）**。 ![本地环境信息和"重命名分支"按钮](/assets/images/help/branch/branch-rename-rename.png) + +### 在分支名称更改后更新本地克隆 + +在您重命名 {% data variables.product.product_name %} 仓库中的分支后，拥有该仓库本地克隆的所有协作者都需要更新克隆。 + +从计算机上的仓库本地克隆中，运行以下命令以更新默认分支的名称。 + +```shell +$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME +$ git fetch origin +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +``` diff --git a/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 181d3ac5b1..5a0b476dc1 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -28,7 +28,7 @@ versions: #### 使用 BFG -[BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) 是一种由开源社区构建和维护的工具。 它提供一种更快、更简单的 `git filter-branch` 替代方法，用于删除不需要的数据。 例如，要删除包含敏感数据的文件并保持最新提交不变，请运行： +[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) 是一种由开源社区构建和维护的工具。 它提供一种更快、更简单的 `git filter-branch` 替代方法，用于删除不需要的数据。 例如，要删除包含敏感数据的文件并保持最新提交不变，请运行： ```shell $ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA @@ -46,7 +46,7 @@ $ bfg --replace-text passwords.txt $ git push --force ``` -有关完整的使用和下载说明，请参阅 [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) 的文档。 +有关完整的使用和下载说明，请参阅 [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) 的文档。 #### 使用 filter-branch diff --git a/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md b/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md index 385dfeb41a..b91ba15871 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md +++ b/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-organization.md @@ -13,14 +13,13 @@ versions: {% tip %} -**提示：** 如果您因为言辞激烈的对话而阻止用户，请考虑[锁定对话](/articles/locking-conversations)，以限制为只有协作者才能评论。 +**提示：** 如果您因为言辞激烈的对话而阻止用户，请考虑锁定对话，以限制为只有协作者才能评论。 更多信息请参阅“[锁定对话](/github/building-a-strong-community/locking-conversations)”。 {% endtip %} 阻止用户访问组织时： - 该用户停止关注您组织的仓库。 - 该用户的星标和议题分配从您的仓库中删除 -- 该用户组织仓库的分叉被删除 - 该用户对您组织仓库中的讨论或评论的投票将被删除 - 该用户在您组织仓库中的协作者身份被删除 - 该用户对您组织的仓库的贡献不再计为他们的贡献 diff --git a/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index b1d70722b3..de16c4b49b 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/zh-CN/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -9,11 +9,11 @@ versions: ### 关于阻止用户 -您可以在您的帐户设置中或从用户的个人资料中阻止用户。 {% data variables.product.prodname_dotcom %} 在您阻止用户时不会通知用户。 如果要避免与您阻止的用户参与相同的项目，您可以选择对于被阻止用户先前参与的任何仓库[显示警告](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings)。 您仍然可以在共享空间中看到被阻止用户的活动，被阻止的用户也可以删除他们现有的内容。 +您可以在您的帐户设置中或从用户的个人资料中阻止用户。 {% data variables.product.prodname_dotcom %} 在您阻止用户时不会通知用户。 如果要避免与您阻止的人参与同一个项目，您可以选择针对被阻止用户先前参与的任何仓库显示警告。 更多信息请参阅“[在帐户设置中阻止用户](#blocking-a-user-in-your-account-settings)”。 您仍然可以在共享空间中看到被阻止用户的活动，被阻止的用户也可以删除他们现有的内容。 {% tip %} -**提示：** 如果您因为言辞激烈的对话而阻止用户，请考虑[锁定对话](/articles/locking-conversations)，以限制为只有协作者才能评论。 +**提示：** 如果您因为言辞激烈的对话而阻止用户，请考虑锁定对话，以限制为只有协作者才能评论。 更多信息请参阅“[锁定对话](/github/building-a-strong-community/locking-conversations)”。 {% endtip %} @@ -22,8 +22,6 @@ versions: - 该用户停止关注并取消固定您的仓库 - 用户无法加入您是所有者的任何组织 - 该用户的星标和议题分配从您的仓库中删除 -- 该用户对您的仓库的复刻被删除 -- 您删除用户仓库的任何复刻 - 该用户对您仓库中的讨论或评论的投票将被删除 - 该用户在您的仓库中的协作者身份被删除 - 该用户对您仓库的贡献不再计为他们的贡献 diff --git a/translations/zh-CN/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/zh-CN/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index 9d59afea69..2dafb24d0b 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/zh-CN/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -18,7 +18,7 @@ versions: 下面是 YAML 前页的示例。 -``` +```yaml --- name: Tracking issue about: Use this template for tracking new features. diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 8780a5135e..d999762e33 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -1,6 +1,6 @@ --- -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.' +title: 自动合并拉取请求 +intro: '您可以通过启用拉取请求自动合并（使拉取请求在满足所有合并要求时自动合并）来提高开发速度。' product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' @@ -8,31 +8,31 @@ versions: {% data reusables.pull_requests.auto-merge-release-phase %} -### About auto-merge +### 关于自动合并 -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. +如果启用拉取请求自动合并，则拉取请求在满足所有必需审查并且状态检查通过时将自动合并。 自动合并使您无需等待满足要求，可以继续执行其他任务。 -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)." +在使用拉取请求自动合并之前，必需对仓库启用自动合并。 更多信息请参阅“[管理仓库中的拉取请求自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)”。 -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). +您可以通过[联系我们](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback)提供关于自动合并的反馈。 -### Enabling auto-merge +### 启用自动合并 -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. 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. 更多信息请参阅“[关于拉取请求合并](/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) +1. 在“Pull Requests（拉取请求）”列表中，单击要自动合并的拉取请求。 +1. （可选）要选择合并方法，请选择 **Enable auto-merge（启用自动合并）**下拉菜单，然后单击合并方法。 更多信息请参阅“[关于拉取请求合并](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)”。 !["启用自动合并"下拉菜单](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png) +1. 单击 **Enable auto-merge（启用自动合并）**。 ![启用自动合并的按钮](/assets/images/help/pull_requests/enable-auto-merge-button.png) +1. 如果选择合并或压缩并合并方法，请输入提交消息和说明，然后选择要创作合并提交的电子邮件地址。 ![输入提交消息和说明并选择提交作者电子邮件的字段](/assets/images/help/pull_requests/pull-request-information-fields.png) +1. 单击 **Confirm auto-merge（确认自动合并）**。 ![确认自动合并的按钮](/assets/images/help/pull_requests/confirm-auto-merge-button.png) -### Disabling auto-merge +### 禁用自动合并 -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. 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) +1. 在“Pull Requests（拉取请求）”列表中，单击要禁用自动合并的拉取请求。 +1. 在合并框中，单击 **Disable auto-merge（禁用自动合并）**。 ![禁用自动合并的按钮](/assets/images/help/pull_requests/disable-auto-merge-button.png) diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md index 138a8e2c0b..3ef9ab923a 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line.md @@ -46,14 +46,14 @@ versions: 4. 打开您首选的文本编辑器，例如 [Atom](https://atom.io/)，然后导航到有合并冲突的文件。 5. 要在文件中查看合并冲突的开头，请在文件中搜索冲突标记 `<<<<<<<`。 当您在文本编辑器中打开文件时，您会在行 `<<<<<<< HEAD` 后看到头部或基础分支。 接下来，您将看到 `=======`，它将您的更改与其他分支中的更改分开，后跟 `>>>>>>> BRANCH-NAME`。 在本例中，一个人在基础或头部分支中编写“open an issue”，而另一个人在比较分支或 `branch-a` 中编写“ask your question in IRC”。 - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` + ``` + If you have questions, please + <<<<<<< HEAD + open an issue + ======= + ask your question in IRC. + >>>>>>> branch-a + ``` {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} 在本例中，两个更改均整合到最终合并： ```shell diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md index 44864ce1f9..521c008164 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks.md @@ -11,7 +11,7 @@ versions: 如果不接受推送，您将看到对应失败预接收挂钩的错误消息。 -``` +```shell $ git push Counting objects: 3, done. Delta compression using up to 4 threads. diff --git a/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md index 5830a1483b..2ba04498fa 100644 --- a/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -19,7 +19,7 @@ versions: {% data reusables.actions.actions-not-verified %} -任何人都可以在 {% data variables.product.prodname_marketplace %} 上列出免费的 {% data variables.product.prodname_github_app %} 或 {% data variables.product.prodname_oauth_app %}。 付费应用程序的发布者由 {% data variables.product.company_short %} 验证，这些应用程序的列表显示有认证的创建者徽章 {% octicon "verified" aria-label="Verified creator badge" %}。 您还将看到未验证和已验证应用程序的徽章。 这些应用程序是使用以前个别应用程序验证方法来发布的。 关于当前流程的更多信息，请参阅“[关于已验证的创建者](/developers/github-marketplace/about-verified-creators)”和“[列出应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 +任何人都可以在 {% data variables.product.prodname_marketplace %} 上列出免费的 {% data variables.product.prodname_github_app %} 或 {% data variables.product.prodname_oauth_app %}。 付费应用程序的发布者由 {% data variables.product.company_short %} 验证，这些应用程序的上架信息显示 Marketplace 徽章 {% octicon "verified" aria-label="Verified creator badge" %}。 您还将看到未验证和已验证应用程序的徽章。 这些应用程序是使用以前个别应用程序验证方法来发布的。 关于当前流程的更多信息，请参阅“[关于 GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)”和“[上架应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 ### 在 {% data variables.product.prodname_marketplace %} 上创建和列出工具 diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md index 0de052636d..70c7a64884 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing access and security for Codespaces -intro: You can manage the repositories that codespaces can access. +title: 管理代码空间的访问和安全 +intro: 您可以管理代码空间可以访问的仓库。 product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,30 +8,30 @@ versions: {% note %} -**Note:** Access and security for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**注意：**{% data variables.product.prodname_codespaces %} 访问和安全目前处于测试阶段，可能会更改。 {% endnote %} -### Managing security and access for your user account +### 管理用户帐户的安全和访问 -When you enable access and security for a repository owned by your user account, any codespaces you create for that repository will have read and write permissions to all other repositories you own. You can enable access and security for none of your repositories, all of your repositories, or specific repositories. You should only enable access and security for repositories you trust. +为用户帐户拥有的仓库启用访问和安全后，您为该仓库创建的任何代码空间都将对您拥有的所有其他仓库具有读取和写入权限。 您可以不对任何仓库、对所有仓库或特定仓库启用访问和安全。 您应该只对您信任的仓库启用访问和安全。 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-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 you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) +1. 在“Access and security（访问和安全）”下，为用户帐户选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问您拥有的其他仓库。 对于您要允许其代码空间访问您拥有的其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) -### Managing security and access for your organization +### 管理组织的安全和访问 -Organization owners can manage security and access for {% data variables.product.prodname_codespaces %}. +组织所有者可以管理 {% data variables.product.prodname_codespaces %} 的安全和访问。 -When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will have read and write permissions to all other repositories the organization owns. You can enable access and security for none of your organization's repositories, all of your organization's repositories, or specific repositories. You should only enable access and security for repositories you trust. +为组织拥有的仓库启用访问和安全后，则为该仓库创建的任何代码空间都将对该组织拥有的所有其他仓库具有读取和写入权限。 您可以不对组织的任何仓库、对组织的所有仓库或特定仓库启用访问和安全。 您应该只对您信任的仓库启用访问和安全。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.click-codespaces %} -5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces. - ![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.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-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) +5. 要代表您的组织批准[预发布计划服务条款](/github/site-policy/github-pre-release-program)并启用 {% data variables.product.prodname_codespaces %}，请在“User permissions（用户权限）”下，选择 **Selected users（所选用户）**，然后输入要授予访问权限的每个人的用户名。 对要授予组织代码空间访问权限的所有用户重复此操作。 + !["所选用户"单选按钮](/assets/images/help/organizations/select-selected-users-radio-button.png) +1. 在“Access and security（访问和安全）”下，为组织选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) +1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问组织拥有的其他仓库。 对于您要允许其代码空间访问其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md index ad4d6a4a16..dfabd33e51 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing encrypted secrets for Codespaces -intro: You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. +title: 管理代码空间的加密密码 +intro: 您可以在代码空间中存储要通过环境变量访问的敏感信息（如令牌）。 product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,46 +8,46 @@ versions: {% note %} -**Note:** Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**注意：**{% data variables.product.prodname_codespaces %} 加密密码目前处于测试阶段，可能会更改。 {% endnote %} -### About encrypted secrets for {% data variables.product.prodname_codespaces %} +### 关于 {% data variables.product.prodname_codespaces %} 的加密密码 -You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. +您可以将要在代码空间中使用的加密密码添加到您的用户帐户。 例如，您可能想要存储和访问以下敏感信息作为加密密码。 -- Personal access tokens to cloud services -- Service principals -- Subscription identifiers +- 对云服务的个人访问令牌 +- 服务主体 +- 订阅标识符 -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. +您可以选择哪些仓库应有权访问每个密码。 然后，您可以在为有权访问密码的仓库创建的任何代码空间中使用该密码。 -### Adding a secret +### 添加密码 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Under "Name", type a name for your secret. !["Name" textbox](/assets/images/help/settings/codespaces-secret-name-field.png) +1. 在“Codespaces secrets（代码空间密码）”的右侧，单击 **New secret（新建密码）**。 !["新建密码"按钮](/assets/images/help/settings/codespaces-new-secret-button.png) +1. 在“Name（名称）”下，输入密码的名称。 !["名称"文本框](/assets/images/help/settings/codespaces-secret-name-field.png) {% data reusables.user_settings.codespaces-secret-value %} {% data reusables.user_settings.codespaces-secret-repository-access %} 1. 单击 **Add secret（添加密码）**。 -### Editing a secret +### 编辑密码 -You can update the value of an existing secret, and you can change which repositories can access a secret. +您可以更新现有密码的值，也可以更改哪些仓库可以访问密码。 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +1. 在“Codespaces secrets（代码空间密码）”下您要编辑的密码右侧，单击 **Update（更新）**。 !["更新" 按钮](/assets/images/help/settings/codespaces-secret-update-button.png) +1. 在“Value（值）”下，单击 **enter a new value（输入新值）**。 !["输入新值" 链接](/assets/images/help/settings/codespaces-secret-update-value-text.png) {% data reusables.user_settings.codespaces-secret-value %} {% data reusables.user_settings.codespaces-secret-repository-access %} -1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. （可选）要删除密码对仓库的访问权限，请取消选择仓库。 ![删除对仓库访问权限的复选框](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) 1. 单击 **Save changes（保存更改）**。 -### Deleting a secret +### 删除密码 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. 阅读警告，然后单击 **OK（确定）**。 ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) +1. 在“Codespaces secrets（代码空间密码）”下您要删除的密码右侧，单击 **Delete（删除）**。 !["删除" 按钮](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. 阅读警告，然后单击 **OK（确定）**。 ![确认删除密码](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md index a326f5be89..476d79fe0f 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing GPG verification for Codespaces -intro: You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source. +title: 管理代码空间的 GPG 验证 +intro: 您可以允许 {% data variables.product.company_short %} 自动使用 GPG 对在代码空间中所做的提交进行签名，以便其他人可以确信更改来自受信任的源。 product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,13 +8,13 @@ versions: {% note %} -**Note:** GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change. +**注意：**{% data variables.product.prodname_codespaces %} 的 GPG 验证目前处于测试阶段，可能会更改。 {% endnote %} -After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." +启用 GPG 验证后，{% data variables.product.company_short %} 将自动对您在 {% data variables.product.prodname_codespaces %} 中所做的提交进行签名，并且该提交在 {% data variables.product.product_name %} 上具有已验证状态。 默认情况下，GPG 验证对您创建的代码空间禁用。 您可以选择对所有仓库或特定仓库允许 GPG 验证。 仅对您信任的仓库启用 GPG 验证。 有关 {% data variables.product.product_name %} 签名提交的更多信息，请参阅“[关于提交签名验证](/github/authenticating-to-github/about-commit-signature-verification)”。 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) +1. 在“GPG verification（GPG 验证）”下，选择您想要的 GPG 验证设置。 ![管理 GPG 验证的单选按钮](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) +1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击想要启用 GPG 验证的仓库。 对您要启用 GPG 验证的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 5110a6aca1..34e56b50c8 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -21,7 +21,7 @@ versions: 一般情况下，调用 {% data variables.product.prodname_codeql_runner %} 如下所示。 -``` +```shell $ /path/to-runner/codeql-runner-OS ``` @@ -40,7 +40,7 @@ $ /path/to-runner/codeql-runner-OS 要覆盖自动语言检测，请运行 `init` 命令：带 `--languages` 标志，后跟以逗号分隔的语言关键字列表。 受支持语言的关键字是 `cpp`、`csharp`、`go`、`java`、`javascript` 和 `python`。 -``` +```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` @@ -56,7 +56,7 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java 在下面的示例中，`+` 符号可确保 {% data variables.product.prodname_codeql_runner %} 结合使用额外查询与所引用配置文件中指定的任何查询。 -``` +```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 ``` @@ -69,7 +69,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c 使用 `init` 命令的 `--config-file` 标志指定配置文件。 标志 `--config-file` 的值是您要使用的配置文件的路径。 此示例加载配置文件 _.github/codeql/codeql-config.yml_。 -``` +```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml ``` @@ -85,7 +85,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c `autobuild` 进程仅尝试为仓库构建_一种_编译语言。 自动选择用于分析的语言是涵盖文件最多的语言。 如果您要明确选择某种语言，请使用 `autobuild` 命令的 `--language` 标志。 -``` +```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 30fabe29bd..2a46d7a8fa 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -20,6 +20,8 @@ redirect_from: 默认情况下， {% data variables.product.prodname_code_scanning %} 定期在默认分支和拉取请求中分析您的代码。 有关管理拉取请求中的警报的更多信息，请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### 关于警报详细信息 每个警报都会高亮显示代码的问题以及识别该问题的工具名称。 您可以看到触发警报的代码行以及警报的属性，例如问题的严重程度和性质。 警报还会告知该问题第一次被引入的时间。 对于由 {% data variables.product.prodname_codeql %} 分析确定的警报，您还会看到如何解决问题的信息。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 3a898491ba..519f8796c6 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -93,6 +93,8 @@ chmod +x codeql-runner-linux 要查看运行器的命令行引用，请使用 `-h` 标志。 例如，要列出所有运行的命令：`codeql-runner-OS -h`，或列出所有可用于 `init` 命令运行的标志：`codeql-runner-OS init -h`（其中 `OS` 因使用的可执行文件而异）。 更多信息请参阅“[在 CI 系统中配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)”。 +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### 基本示例 此示例在 Linux CI 服务器上对托管在 `{% data variables.command_line.git_url_example %}` 上的 `octo-org/example-repo` 仓库运行 {% data variables.product.prodname_codeql %} 分析。 这个过程非常简单，因为仓库只包含可通过 {% data variables.product.prodname_codeql %} 直接分析的语言，而无需构建（例如 Go、JavaScript、Python 和 TypeScript）。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 6492795d3d..ca00fde0d5 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -40,6 +40,8 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 您可以根据 {% data variables.product.prodname_dotcom %} 引入规则测试 SARIF 文件是否兼容 {% data variables.product.prodname_code_scanning %}。 有关更多信息，请访问 [Microsoft SARIF 验证程序](https://sarifweb.azurewebsites.net/)。 +{% data reusables.code-scanning.upload-sarif-alert-limit %} + ### 支持的 SARIF 输出文件属性 如果您使用 {% data variables.product.prodname_codeql %} 以外的代码分析引擎，则可以查看受支持的 SARIF 属性来优化您的分析结果在 {% data variables.product.prodname_dotcom %} 中的显示方式。 @@ -82,6 +84,8 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS #### `result` 对象 +{% data reusables.code-scanning.upload-sarif-alert-limit %} + | 名称 | 描述 | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ruleId` | **可选。**规则的唯一标识符 (`reportingDescriptor.id`)。 更多信息请参阅 [`reportingDescriptor` 对象](#reportingdescriptor-object)。 {% data variables.product.prodname_code_scanning_capc %} 使用规则标识符在 {% data variables.product.prodname_dotcom %} 上按规则过滤结果。 | @@ -89,7 +93,7 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS | `rule` | **可选。**用于定位此结果的规则 (reportingdescriptor) 的引用。 更多信息请参阅 [`reportingDescriptor` 对象](#reportingdescriptor-object)。 | | `level` | **可选。**结果的严重程度。 此级别覆盖规则定义的默认严重程度。 {% data variables.product.prodname_code_scanning_capc %} 使用级别在 {% data variables.product.prodname_dotcom %} 上按严重程度过滤结果。 | | `message.text` | **必选。**描述结果的消息。 {% data variables.product.prodname_code_scanning_capc %} 显示消息文本作为结果的标题。 当可见空间有限时，仅显示消息的第一句。 | -| `locations[]` | **必选。**检测到结果的位置集。 应只包含一个位置，除非只能通过在每个指定位置进行更改来更正问题。 **注：**{% data variables.product.prodname_code_scanning %} 至少需要一个位置才能显示结果。 {% data variables.product.prodname_code_scanning_capc %} 将使用此属性来决定要用结果注释哪个文件。 仅使用此数组的第一个值。 所有其他值都被忽略。 | +| `locations[]` | **必填。**>最多可以检测到 10 个结果的位置集。 应只包含一个位置，除非只能通过在每个指定位置进行更改来更正问题。 **注：**{% data variables.product.prodname_code_scanning %} 至少需要一个位置才能显示结果。 {% data variables.product.prodname_code_scanning_capc %} 将使用此属性来决定要用结果注释哪个文件。 仅使用此数组的第一个值。 所有其他值都被忽略。 | | `partialFingerprints` | **必选。**用于跟踪结果的唯一标识的一组字符串。 {% data variables.product.prodname_code_scanning_capc %} 使用 `partialFingerprints` 准确地识别在提交和分支之间相同的结果。 {% data variables.product.prodname_code_scanning_capc %} 将尝试使用 `partialFingerprints`（如果存在）。 如果您使用 `upload-action` 上传第三方 SARIF 文件，该操作将为您创建 `partialFingerprints`（如果它们未包含在 SARIF 文件中）。 更多信息请参阅“[使用指纹防止重复警报](#preventing-duplicate-alerts-using-fingerprints)”。 **注：**{% data variables.product.prodname_code_scanning_capc %} 只使用 `primaryLocationLineHash`。 | | `codeFlows[].threadFlows[].locations[]` | **可选。**`threadFlow` 对象的 `location` 对象数组，它描述程序通过执行线程的进度。 `codeFlow` 对象描述用于检测结果的代码执行模式。 如果提供了代码流，{% data variables.product.prodname_code_scanning %} 将在 {% data variables.product.prodname_dotcom %} 上扩展代码流以获取相关结果。 更多信息请参阅 [`location` 对象](#location-object)。 | | `relatedLocations[]` | 与此结果相关的一组位置。 当相关位置嵌入在结果消息中时，{% data variables.product.prodname_code_scanning_capc %} 将链接到这些位置。 更多信息请参阅 [`location` 对象](#location-object)。 | diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 9361ebae6a..c2cd337211 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -39,6 +39,8 @@ versions: 如果您的 SARIF 文件不含 `partialFingerprints`，则 `upload-sarif` 操作将为您计算 `partialFingerprints` 字段，并尝试防止重复警报。 {% data variables.product.prodname_dotcom %} 仅当仓库同时包含 SARIF 文件和静态分析中使用的源代码时才能创建 `partialFingerprints`。 有关防止重复警报的更多信息，请参阅“[关于代码扫描的 SARIF 支持](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)”。 +{% data reusables.code-scanning.upload-sarif-alert-limit %} + #### 在存储库外部生成的 SARIF 文件的工作流程示例 您可以创建一个新的工作流程，以在将 SARIF 文件提交到仓库后上传它们。 这在 SARIF 文件生成为仓库外部的构件时很有用。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md index 87ae5d07fb..85160884ca 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md +++ b/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md @@ -1,6 +1,6 @@ --- -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. These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.' +title: 关于 GitHub 高级安全 +intro: '{% data variables.product.prodname_dotcom %} 为拥有 {% data variables.product.prodname_advanced_security %} 许可的客户提供额外的安全功能。 这些功能还对 {% data variables.product.prodname_dotcom_the_website %} 上的公共仓库启用。' versions: free-pro-team: '*' enterprise-server: '>=3.0' @@ -8,41 +8,41 @@ versions: ### 关于 {% data variables.product.prodname_GH_advanced_security %} -{% 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, for example: dependency graph and {% data variables.product.prodname_dependabot_alerts %}. 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 %}. (That is, private and internal repositories on {% data variables.product.prodname_dotcom_the_website %}, and all repositories on {% data variables.product.prodname_ghe_server %}.) +{% data variables.product.prodname_dotcom %} 有许多功能可帮助您改进和维护代码的质量。 其中某些功能包含在所有计划中，例如依赖关系图和 {% data variables.product.prodname_dependabot_alerts %}。 其他功能需要 {% data variables.product.prodname_GH_advanced_security %} 许可才能在 {% data variables.product.prodname_dotcom_the_website %} 公共仓库以外的仓库上运行。 （即，{% data variables.product.prodname_dotcom_the_website %} 上的私有和内部仓库，以及 {% data variables.product.prodname_ghe_server %} 上的所有仓库。） -For an overview of all security features, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)." +关于所有安全功能的概述，请参阅“[关于保护仓库](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)”。 有关安全功能相关操作的权限要求的信息，请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)”。 -### About {% data variables.product.prodname_advanced_security %} features +### 关于 {% data variables.product.prodname_advanced_security %} 功能 -A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: +{% data variables.product.prodname_GH_advanced_security %} 许可提供以下额外功能： -- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. 更多信息请参阅“[关于 {% 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 %}** - 搜索代码中潜在的安全漏洞和编码错误。 更多信息请参阅“[关于 {% 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 %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. 更多信息请参阅“[关于 {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)”。 +- **{% data variables.product.prodname_secret_scanning_caps %}** - 检测已检入仓库的密码（例如密钥和令牌）。 更多信息请参阅“[关于 {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)”。 {% if currentVersion == "free-pro-team@latest" %} -- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 +- **依赖项审查** - 在合并拉取请求之前显示依赖项更改的全部影响以及任何有漏洞版本的详情。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 {% endif %} -For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." +有关正在开发中的 {% data variables.product.prodname_advanced_security %} 功能，请参阅“[{% data variables.product.prodname_dotcom %} 公开路线图](https://github.com/github/roadmap)”。 {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_server %} +### 在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_advanced_security %} 功能 -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)." +站点管理员必须为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_advanced_security %}，您才能使用这些功能。 更多信息请参阅“[配置高级安全功能](/admin/configuration/configuring-advanced-security-features)”。 -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](/github/setting-up-and-managing-organizations-and-teams/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)." -For information about purchasing a license for +设置系统后，您可以在组织或仓库级别启用和禁用这些功能。 更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 +有关购买 -{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% data variables.product.prodname_GH_advanced_security %} 许可的信息，请联系 {% data variables.contact.contact_enterprise_sales %}。 {% endif %} -### Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %} +### 在 {% data variables.product.prodname_dotcom_the_website %} 上启用 {% data variables.product.prodname_advanced_security %} 功能 -For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public. +对于 {% data variables.product.prodname_dotcom_the_website %} 上的公共仓库，这些功能是永久性的，仅当您更改项目的可见性使代码不再公开时才会禁用。 -For all other repositories, once you have a license, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/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)." -For information about purchasing a license for +对于所有其他仓库，一旦您拥有许可，就可以在组织或仓库级别启用和禁用这些功能。 {% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 +有关购买 -{% data variables.product.prodname_GH_advanced_security %}, contact {% data variables.contact.contact_enterprise_sales %}. +{% data variables.product.prodname_GH_advanced_security %} 许可的信息，请联系 {% data variables.contact.contact_enterprise_sales %}。 {% endif %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md index b7284d81a8..a4cc007b30 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -25,15 +25,13 @@ authors: {% endif %} -通过我们的[训练营](/categories/bootcamp/)文章熟悉使用 {% data variables.product.product_name %}。 参阅我们的 [{% data variables.product.prodname_dotcom %} 流程](https://guides.github.com/introduction/flow)查看流程介绍。 阅读我们的[概述指南](https://guides.github.com)了解基本概念。 +通过我们的[使用入门](/categories/getting-started-with-github/)文章更好地熟悉 {% data variables.product.product_name %}。 参阅我们的 [{% data variables.product.prodname_dotcom %} 流程](https://guides.github.com/introduction/flow)查看流程介绍。 阅读我们的[概述指南](https://guides.github.com)了解基本概念。 {% data reusables.support.ask-and-answer-forum %} #### 分支、复刻和拉取请求 -使用交互式工具了解 [Git 分支](http://learngitbranching.js.org/)。 阅读有关[复刻](/articles/about-forks)和[拉取请求](/articles/using-pull-requests)的相关信息并了解[如何在 {% data variables.product.prodname_dotcom %} 上使用拉取请求](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github)。 - -访问有关[命令行](https://hub.github.com)的快速参考，以及 {% data variables.product.prodname_dotcom %} [检查清单、备忘清单等](https://services.github.com/on-demand/resources)。 +使用交互式工具了解 [Git 分支](http://learngitbranching.js.org/)。 阅读有关[复刻](/articles/about-forks)和[拉取请求](/articles/using-pull-requests)的相关信息并了解[如何在 {% data variables.product.prodname_dotcom %} 上使用拉取请求](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github)。 Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). #### 收看视频 @@ -41,9 +39,9 @@ authors: ### 培训 -#### 免费课程 +#### Free courses -{% data variables.product.product_name %} 提供一系列交互式[按需培训课程](https://services.github.com/on-demand/)，包括 {% data variables.product.prodname_dotcom %} 101：[简介](https://services.github.com/on-demand/intro-to-github/)、{% data variables.product.prodname_dotcom %} 102：[GitHub Desktop](https://services.github.com/on-demand/github-desktop) 和 {% data variables.product.prodname_dotcom %} 103：[命令行](https://services.github.com/on-demand/github-cli)。 +{% 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 %}. #### {% data variables.product.prodname_dotcom %} 基于 web 的教育课程 @@ -51,7 +49,7 @@ authors: #### 为您的公司提供培训 -{% data variables.product.prodname_dotcom %} 提供[现场课程](https://services.github.com/#offerings)，我们安排经验丰富的教育工作者现场讲授。 如需询问有关培训的问题，请[联系我们](https://services.github.com/#contact)。 +{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. 如需询问有关培训的问题，请[联系我们](https://services.github.com/#contact)。 ### 其他资源 diff --git a/translations/zh-CN/content/github/getting-started-with-github/git-cheatsheet.md b/translations/zh-CN/content/github/getting-started-with-github/git-cheatsheet.md index c0fda49b8e..7584906e71 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/git-cheatsheet.md +++ b/translations/zh-CN/content/github/getting-started-with-github/git-cheatsheet.md @@ -8,6 +8,6 @@ versions: github-ae: '*' --- -很快掌握所有可用的 Git 命令可能是一项艰巨的任务。 请在手头备一份 [Git 备忘清单](https://services.github.com/on-demand/resources/cheatsheets/)以便参考。 Using Git Cheat Sheet（使用 Git 备忘清单）有多种语言版本。 更多信息请参阅 [GitHub Services 网站上的资源页面](https://services.github.com/on-demand/resources/)。 +很快掌握所有可用的 Git 命令可能是一项艰巨的任务。 我们的备忘清单为您提供最常用命令的快速参考：请参阅“[Git 备忘清单](https://training.github.com/)”。 “Using Git（使用 Git）”备忘清单有多种语言版本。 此外，您可以查看我们的 [Git 和 GitHub 学习资源](/articles/git-and-github-learning-resources/)页面，其中包含许多指南和视频等资源的链接。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md b/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md index f26634bbe4..8648e46e34 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md +++ b/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md @@ -85,6 +85,7 @@ versions: - {% data variables.contact.enterprise_support %}. 更多信息请参阅“{% data variables.product.prodname_ghe_cloud %} 支持”和“{% data variables.product.prodname_ghe_cloud %} 附录”。 - 50,000 {% data variables.product.prodname_actions %} 分钟 - 50GB {% data variables.product.prodname_registry %} 存储空间 +- {% data variables.product.prodname_pages %} 站点的访问控制。 更多信息请参阅“更改 {% data variables.product.prodname_pages %} 站点的可见性” - 99.9% 月持续运行时间的服务等级协议 - 通过企业帐户集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单的选项。 更多信息请参阅“关于企业帐户”。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md index 9f8104c532..c5afd95246 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md +++ b/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md @@ -76,7 +76,8 @@ versions: | control shift p 或 command shift p | 在 **Write（撰写）**和 **Preview（预览）**评论选项卡之间切换 | | control enter | 提交评论 | | control .，然后 control [已保存回复编号] | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% if currentVersion == "free-pro-team@latest" %} -| control g 或 command g | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)”。 |{% endif %} +| control g 或 command g | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)”。 +{% endif %} | r | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 | ### 议题和拉取请求列表 @@ -111,7 +112,8 @@ versions: | k | 将所选内容在列表中向上移动 | | cmd + shift + enter | 添加一条有关拉取请求差异的评论 | | alt 并单击 | 通过按下 `alt` 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| 单击，然后按住 shift 并单击 | 单击一个行号，按住 shift，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。”|{% endif %} +| 单击，然后按住 shift 并单击 | 单击一个行号，按住 shift，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。” +{% endif %} ### 项目板 diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 8a3398259d..1ac09ee4db 100644 --- a/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -45,7 +45,7 @@ versions: 7. 在 {% data variables.product.product_name %} 仓库的 Quick Setup（快速设置）页面顶部，单击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 复制远程仓库 URL。 ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. 在终端上，[添加远程仓库的 URL](/articles/adding-a-remote)（将在该 URL 推送本地仓库）。 ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -83,7 +83,7 @@ versions: 7. 在 {% data variables.product.product_name %} 仓库的 Quick Setup（快速设置）页面顶部，单击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 复制远程仓库 URL。 ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. 在命令提示中，[添加远程仓库的 URL](/articles/adding-a-remote)（将在该 URL 推送本地仓库）。 ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL @@ -121,7 +121,7 @@ versions: 7. 在 {% data variables.product.product_name %} 仓库的 Quick Setup（快速设置）页面顶部，单击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 复制远程仓库 URL。 ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) 8. 在终端上，[添加远程仓库的 URL](/articles/adding-a-remote)（将在该 URL 推送本地仓库）。 ```shell - $ git remote add origin remote repository URL + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md index 2efb71d008..e16f8f9140 100644 --- a/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md @@ -1,6 +1,6 @@ --- -title: Deleting files in a repository -intro: 'You can delete an individual file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory{% endif %} in your repository on {% data variables.product.product_name %}.' +title: 删除仓库中的文件 +intro: '您可以删除 {% data variables.product.product_name %} 仓库中的单个文件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}或整个目录{% endif %}。' redirect_from: - /articles/deleting-files - /github/managing-files-in-a-repository/deleting-files @@ -9,18 +9,18 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' -permissions: People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository. +permissions: 具有写入权限的人可以删除仓库中的文件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}或目录{% endif %}。 --- -### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion +### 关于文件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}和目录{% endif %}删除 -You can delete an individual file in your repository{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or an entire directory, including all the files in the directory{% endif %}. +您可以删除仓库中的单个文件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}或整个目录，包括目录中的所有文件{% endif %}。 -If you try to delete a file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} in a repository that you don’t have write permissions to, we'll fork the project to your user account and help you send a pull request to the original repository after you commit your change. 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。 +如果您尝试在您没有写入权限的仓库中删除文件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}或目录{% endif %}，我们会将项目复刻到您的用户帐户，并在您提交更改后帮助您向原始仓库发送拉取请求。 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。 -If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directory{% endif %} you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. 更多信息请参阅“[从仓库中删除敏感数据](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)”。 +如果您删除的文件{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}或目录{% endif %}包含敏感数据，则该数据仍然可以在仓库的 Git 历史记录中访问。 要从 {% data variables.product.product_name %} 中彻底删除文件，您必须从仓库的历史记录中删除该文件。 更多信息请参阅“[从仓库中删除敏感数据](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)”。 -### Deleting a file +### 删除文件 1. 浏览到要删除仓库中的文件。 2. 在文件顶部，单击 @@ -31,11 +31,11 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_ {% data reusables.files.propose_file_change %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Deleting a directory +### 删除目录 -1. Browse to the directory in your repository that you want to delete. -1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**. ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png) -1. Review the files you will delete. +1. 浏览到仓库中要删除的目录。 +1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Delete directory（删除目录）**。 ![删除目录的按钮](/assets/images/help/repository/delete-directory-button.png) +1. 审查要删除的文件。 {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md index cbcfa0a747..032bac346a 100644 --- a/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md @@ -9,7 +9,7 @@ versions: ### 关于在 {% data variables.product.prodname_dotcom %} 上导航代码 -导航代码功能使用开源库 [`semantic`](https://github.com/github/semantic)。 支持以下语言： +代码导航使用开源库 [`tree-sitter`](https://github.com/tree-sitter/tree-sitter)。 支持以下语言： - C# - CodeQL - Go diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md index a72ee07684..998132fd0b 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -8,17 +8,17 @@ versions: {% data variables.product.prodname_dotcom %} 提供以下工具来删除和避免有漏洞依赖项。 #### 依赖关系图 -依赖项图是存储在仓库中的清单和锁定文件的摘要。 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 %}. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 +依赖项图是存储在仓库中的清单和锁定文件的摘要。 它显示您的代码库所依赖的生态系统和软件包（其依赖项）以及依赖于您的项目的仓库和包（其从属项）。 依赖关系图中的信息用于依赖项审查和 {% data variables.product.prodname_dependabot %}。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 -#### 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. 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 +#### 依赖项审查 +通过检查拉取请求的依赖项审查，可以避免将依赖项的漏洞引入到代码库中。 如果拉取请求添加了有漏洞依赖项，或者将依赖项更改为有漏洞的版本，这将在依赖项审查中高亮显示。 您可以在合并拉取请求之前将依赖项更改为修补版本。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 #### {% data variables.product.prodname_dependabot_alerts %} -{% data variables.product.prodname_dotcom %} 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. 该警报包括指向项目中受影响的文件的链接，以及有关修复的版本的信息。 {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 +检测到仓库中存在有漏洞依赖项时，{% data variables.product.prodname_dotcom %} 可创建 {% data variables.product.prodname_dependabot_alerts %}。 警报显示在仓库的 Security（安全）选项卡上。 该警报包括指向项目中受影响的文件的链接，以及有关修复的版本的信息。 {% data variables.product.prodname_dotcom %} 还根据仓库维护员的通知首选项通知他们。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 #### {% data variables.product.prodname_dependabot_security_updates %} -When {% data variables.product.prodname_dotcom %} 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. 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 +当 {% data variables.product.prodname_dotcom %} 针对仓库中的有漏洞依赖项生成 {% data variables.product.prodname_dependabot %} 警报时，{% data variables.product.prodname_dependabot %} 可以自动尝试为您修复它。 {% data variables.product.prodname_dependabot_security_updates %} 是自动生成的拉取请求，用于将有漏洞依赖项更新到修复版本。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 #### {% data variables.product.prodname_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)." +启用 {% data variables.product.prodname_dependabot_version_updates %} 帮助您维护依赖项。 有了 {% data variables.product.prodname_dependabot_version_updates %}，每当 {% data variables.product.prodname_dotcom %} 发现过时的依赖项，它就会提出拉取请求，以将清单更新到依赖项的最新版本。 而 {% data variables.product.prodname_dependabot_security_updates %} 只是提出拉取请求以修复有漏洞依赖项。 更多信息请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates)”。 diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md index babf154b69..89b9c024fb 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/publishing-a-security-advisory.md @@ -24,6 +24,18 @@ versions: 在发布安全通告之前，您可以私下协作在临时私有复刻中修复漏洞。 更多信息请参阅“[在临时私有复刻中协作以解决安全漏洞](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”。 +{% warning %} + +**Warning**: Whenever possible, you should always add a fix version to a security advisory prior to publishing the advisory. If you don't, the advisory will be published without a fixed version, and {% data variables.product.prodname_dependabot %} will alert your users about the issue, without offering any safe version to update to. + +We recommend you take the following steps in these different situations: + +- If a fix version is imminently available, and you are able to, wait to disclose the issue when the fix is ready. +- If a fix version is in development but not yet available, mention this in the advisory, and edit the advisory later, after publication. +- If you are not planning to fix the issue, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue. + +{% endwarning %} + 从公共仓库发布通告草稿时，每个人都可以看到： - 通告数据的当前版本。 diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md index 62d95cd923..892cfd22f0 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md @@ -133,7 +133,8 @@ versions: | `To` 字段 | 此字段直接连接到线程。{% if currentVersion != "github-ae@latest" %} 如果您回复电子邮件，将在对话中添加一个新的评论。{% endif %} | `Cc` 地址 | 如果您订阅了对话，{% data variables.product.product_name %} 将会 `Cc` 给您。 第二个 `Cc` 电子邮件地址与通知原因匹配。 这些通知原因的后缀是 {% data variables.notifications.cc_address %}。 可能的通知原因包括：
    • `assign`：您被分配到议题或拉取请求。
    • `author`：您创建了议题或拉取请求。
    • `comment`：您评论了议题或拉取请求。
    • `manual`：您手动订阅的议题或拉取请求有更新。
    • `mention`：您提及了议题或拉取请求。
    • `push`：有人提交了您订阅的拉取请求。
    • `review_requested`：您或您所在的团队已请求审查拉取请求。
      • {% if currentVersion != "github-ae@latest" %}
    • `security_alert`：{% data variables.product.prodname_dotcom %} 检测到您要接收其漏洞警报的仓库中存在漏洞。
      • {% endif %}
    • `state_change`：您订阅的议题或拉取请求已关闭或打开。
    • `subscribed`：您查看的仓库有更新。
    • `team_mention`：您所属的团队在议题或拉取请求中被提及。
    • `your_activity`：您打开、评论或关闭了议题或拉取请求。
    | | `mailing list` 字段 | 此字段识别仓库名称及其所有者。 此地址的格式始终是 `<仓库名称>.<仓库所有者>.{% data variables.command_line.backticks %}`。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `X-GitHub-Severity` 字段 | {% data reusables.repositories.security-alerts-x-github-severity %} 可能的严重程度等级包括：
    • `低`
    • `中`
    • `高`
    • `严重`
    更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 |{% endif %} +| `X-GitHub-Severity` 字段 | {% data reusables.repositories.security-alerts-x-github-severity %} 可能的严重程度等级包括：
    • `低`
    • `中`
    • `高`
    • `严重`
    更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 +{% endif %} ### 选择通知设置 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index a4d183fd28..add7fb85dc 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -11,7 +11,7 @@ versions: 要将打开的议题转让给另一个仓库，必须对议题所在的仓库以及议题要转让到的仓库都有写入权限。 更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)”。 -只能在同一用户或组织帐户拥有的仓库之间转让议题。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}不能将议题从私有仓库转让到公共仓库。{% endif %} +您只能在同一用户或组织帐户拥有的仓库之间转让议题。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can't transfer an issue from a private repository to a public repository.{% endif %} 转让议题时，评论和受理人将保留。 不会保留议题的标签和里程碑。 此议题将留在任何用户拥有或组织范围的项目板上，并从任何仓库项目板中删除。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 diff --git a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md index 767f0108df..0d04ffba73 100644 --- a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md +++ b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md @@ -25,7 +25,8 @@ versions: | `To` 字段 | 此字段直接连接到线程。 如果您回复电子邮件，将会为对话添加新评论。 | | `Cc` 地址 | 如果您订阅了对话，{% data variables.product.product_name %} 将会 `Cc` 给您。 第二个 `Cc` 电子邮件地址与通知原因匹配。 这些通知原因的后缀是 {% data variables.notifications.cc_address %}。 可能的通知原因包括：
    • `assign`：您被分配到议题或拉取请求。
    • `author`：您创建了议题或拉取请求。
    • `comment`：您评论了议题或拉取请求。
    • `manual`：您手动订阅的议题或拉取请求有更新。
    • `mention`：您提及了议题或拉取请求。
    • `push`：有人提交了您订阅的拉取请求。
    • `review_requested`：您或您所在的团队已请求审查拉取请求。
    • `security_alert`：{% data variables.product.prodname_dotcom %} 检测到您要接收其漏洞警报的仓库中存在漏洞。
    • `state_change`：您订阅的议题或拉取请求已关闭或打开。
    • `subscribed`：您查看的仓库有更新。
    • `team_mention`：您所属的团队在议题或拉取请求中被提及。
    • `your_activity`：您打开、评论或关闭了议题或拉取请求。
    | | `mailing list` 字段 | 此字段识别仓库名称及其所有者。 此地址的格式始终是 `<仓库名称>.<仓库所有者>.{% data variables.command_line.backticks %}`。 |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| `X-GitHub-Severity` 字段 | {% data reusables.repositories.security-alerts-x-github-severity %} 可能的严重程度等级包括：
    • `低`
    • `中`
    • `高`
    • `严重`
    更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 |{% endif %} +| `X-GitHub-Severity` 字段 | {% data reusables.repositories.security-alerts-x-github-severity %} 可能的严重程度等级包括：
    • `低`
    • `中`
    • `高`
    • `严重`
    更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 +{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 05df7ddbea..63bf50a0c2 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -131,7 +131,8 @@ versions: | `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) 匹配 `desktop/desktop` 仓库中通过关闭引用链接到拉取请求的开放议题。 | | `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) 匹配 `desktop/desktop` 仓库中链接到拉取请求可能已关闭的议题的已关闭拉取请求。 | | `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) 匹配 `desktop/desktop` 仓库中未通过关闭引用链接到拉取请求的开放议题。 | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) 匹配 `desktop/desktop` 仓库中未链接至拉取请求可能关闭的议题的开放拉取请求。 |{% endif %} +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) 匹配 `desktop/desktop` 仓库中未链接至拉取请求可能关闭的议题的开放拉取请求。 +{% endif %} ### 按标签搜索 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md index 07c5185093..bb8e58e9cf 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -93,7 +93,7 @@ versions: {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} {% link_in_list /managing-the-display-of-member-names-in-your-organization %} {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} - {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} + {% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} {% link_in_list /integrating-jira-with-your-organization-project-board %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..e1a0fc2666 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/unpublishing-a-github-pages-site)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. + ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. + ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Click **Save**. + +### Further reading + +- "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md index 0e42e82682..edbe7be95e 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -1,23 +1,23 @@ --- -title: Managing updates from accounts your organization sponsors -intro: You can manage the email address that receives updates from accounts your organization sponsors. +title: 管理组织赞助帐户的更新 +intro: 您可以管理用于接收组织赞助帐户更新的电子邮件地址。 versions: free-pro-team: '*' -permissions: Organization owners can manage updates from accounts the organization sponsors. +permissions: 组织所有者可管理组织赞助帐户的更新。 --- {% data reusables.sponsors.org-sponsors-release-phase %} -The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates. +组织赞助的开发者和组织可向您发送有关其工作的更新。 您可以管理用于接收这些更新的电子邮件地址。 -You can also disable updates from accounts your organization sponsors. 更多信息请参阅“[管理您的赞助](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)”。 +您也可以禁用组织赞助帐户的更新。 更多信息请参阅“[管理您的赞助](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)”。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} -1. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. 在“Sponsors update email (Private)（赞助更新电子邮件（私有））”下，输入要用于接收组织赞助帐户更新的电子邮件地址。 ![输入用于接收被赞助帐户更新的电子邮件地址的文本框](/assets/images/help/sponsors/organization-update-email-textbox.png) 1. 单击 **Update profile（更新个人资料）**。 ![更新个人资料按钮](/assets/images/help/organizations/update-profile-button.png) ### 延伸阅读 -- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" \ No newline at end of file +- "[使用 {% data variables.product.prodname_sponsors %} 支持开源社区](/github/supporting-the-open-source-community-with-github-sponsors)" \ No newline at end of file diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 77db5ca749..fe5361dcd2 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -23,99 +23,102 @@ versions: {% if currentVersion == "free-pro-team@latest" %} -| 组织操作 | 所有者 | 成员 | 帐单管理员 | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:--------------------------------------------------:| -| 创建仓库（详细信息请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”） | **X** | **X** | | -| 查看和编辑帐单信息 | **X** | | **X** | -| 邀请人员加入组织 | **X** | | | -| 编辑和取消邀请加入组织 | **X** | | | -| 从组织删除成员 | **X** | | | -| 恢复组织的前成员 | **X** | | | -| 添加和删除**所有团队**的人员 | **X** | | | -| 将组织成员升级为*团队维护员* | **X** | | | -| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”） | **X** | | | -| 设置预定提醒（请参阅“[管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)”） | **X** | | | -| 添加协作者到**所有仓库** | **X** | | | -| 访问组织审核日志 | **X** | | | -| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | -| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”） | **X** | | | -| 将电子邮件通知限制为经验证的域（更多信息请参阅“[将电子邮件通知限制为经批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”） | **X** | | | -| 删除**所有团队** | **X** | | | -| 删除组织帐户，包括所有仓库 | **X** | | | -| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | | -| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | | -| 查看所有组织成员和团队 | **X** | **X** | | -| @提及任何可见团队 | **X** | **X** | | -| 可成为*团队维护员* | **X** | **X** | | -| 查看组织洞见（详细信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)”） | **X** | **X** | | -| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | **X** | | -| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | | | -| 编辑和删除**所有团队**的团队讨论（详细信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments)”） | **X** | | | -| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments/#hiding-a-comment)”） | **X** | **X** | | -| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | |{% if currentVersion == "free-pro-team@latest" %} -| 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”） | **X** | | |{% endif %} -| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | | -| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”） | **X** | **X** | | -| 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)”） | **X** | | | -| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)”） | **X** | | | -| 禁止从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[为组织禁止发布 {% data variables.product.prodname_pages %} 站点](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | | | -| 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | **X** | | | -| 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | -| [管理用户对组织的 SAML 访问](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | -| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** | | | -| 转让仓库 | **X** | | | -| 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序 | **X** | | | -| 列出 {% data variables.product.prodname_marketplace %} 中的应用程序 | **X** | | |{% if currentVersion != "github-ae@latest" %} -| 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | **X** | | | -| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”） | **X** | | |{% endif %} -| [管理复刻策略](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [限制组织中公共仓库的活动](/articles/limiting-interactions-in-your-organization) | **X** | | | -| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | | -| 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | | -| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | | -| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | | -| 启用团队同步（详情请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”） | **X** | | | +| 组织操作 | 所有者 | 成员 | 帐单管理员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:| +| 创建仓库（详细信息请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”） | **X** | **X** | | +| 查看和编辑帐单信息 | **X** | | **X** | +| 邀请人员加入组织 | **X** | | | +| 编辑和取消邀请加入组织 | **X** | | | +| 从组织删除成员 | **X** | | | +| 恢复组织的前成员 | **X** | | | +| 添加和删除**所有团队**的人员 | **X** | | | +| 将组织成员升级为*团队维护员* | **X** | | | +| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”） | **X** | | | +| 设置预定提醒（请参阅“[管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)”） | **X** | | | +| 添加协作者到**所有仓库** | **X** | | | +| 访问组织审核日志 | **X** | | | +| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | +| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”） | **X** | | | +| 将电子邮件通知限制为经验证的域（更多信息请参阅“[将电子邮件通知限制为经批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”） | **X** | | | +| 删除**所有团队** | **X** | | | +| 删除组织帐户，包括所有仓库 | **X** | | | +| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | | +| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | | +| 查看所有组织成员和团队 | **X** | **X** | | +| @提及任何可见团队 | **X** | **X** | | +| 可成为*团队维护员* | **X** | **X** | | +| 查看组织洞见（详细信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)”） | **X** | **X** | | +| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | **X** | | +| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | | | +| 编辑和删除**所有团队**的团队讨论（详细信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments)”） | **X** | | | +| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments/#hiding-a-comment)”） | **X** | **X** | | +| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | | +| 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”） | **X** | | | +| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | | +| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”） | **X** | **X** | | +| 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)”） | **X** | | | +| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)”） | **X** | | | +| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | | | +| 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | **X** | | | +| 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [管理用户对组织的 SAML 访问](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** | | | +| 转让仓库 | **X** | | | +| 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序 | **X** | | | +| 列出 {% data variables.product.prodname_marketplace %} 中的应用程序 | **X** | | | +| 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | **X** | | | +| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”） | **X** | | | +| [管理复刻策略](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | +| [限制组织中公共仓库的活动](/articles/limiting-interactions-in-your-organization) | **X** | | | +| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | | +| 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | | +| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | | +| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | | +| 启用团队同步（详情请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”） | **X** | | | {% else %} -| 组织操作 | 所有者 | 成员 | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:---------------------------------------------------------------------------------------------------:| -| 邀请人员加入组织 | **X** | | -| 编辑和取消邀请加入组织 | **X** | | -| 从组织删除成员 | **X** | | | -| 恢复组织的前成员 | **X** | | | -| 添加和删除**所有团队**的人员 | **X** | | -| 将组织成员升级为*团队维护员* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”） | **X** | |{% endif %} -| 添加协作者到**所有仓库** | **X** | | -| 访问组织审核日志 | **X** | | -| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | -| 删除**所有团队** | **X** | | -| 删除组织帐户，包括所有仓库 | **X** | | -| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | -| 查看所有组织成员和团队 | **X** | **X** | -| @提及任何可见团队 | **X** | **X** | -| 可成为*团队维护员* | **X** | **X** | -| 转让仓库 | **X** | | -| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** | | -| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | | -| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | **X** | | -| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | | | -| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments)” | **X** | | | -| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments/#hiding-a-comment)”） | **X** | **X** | **X** | -| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | | -| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | |{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -| 禁止从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[为组织禁止发布 {% data variables.product.prodname_pages %} 站点](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | | |{% endif %} -| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | -| 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | -| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | |{% endif %} +| 组织操作 | 所有者 | 成员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------------------------------------------------------------------------:| +| 邀请人员加入组织 | **X** | | +| 编辑和取消邀请加入组织 | **X** | | +| 从组织删除成员 | **X** | | | +| 恢复组织的前成员 | **X** | | | +| 添加和删除**所有团队**的人员 | **X** | | +| 将组织成员升级为*团队维护员* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”） | **X** | +{% endif %} +| 添加协作者到**所有仓库** | **X** | | +| 访问组织审核日志 | **X** | | +| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | +| 删除**所有团队** | **X** | | +| 删除组织帐户，包括所有仓库 | **X** | | +| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | +| 查看所有组织成员和团队 | **X** | **X** | +| @提及任何可见团队 | **X** | **X** | +| 可成为*团队维护员* | **X** | **X** | +| 转让仓库 | **X** | | +| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** | | +| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | | +| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | **X** | | +| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/articles/about-team-discussions)”） | **X** | | | +| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments)”） | **X** | | | +| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/articles/managing-disruptive-comments/#hiding-a-comment)”） | **X** | **X** | **X** | +| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | | +| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | +{% endif %} +| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | +| 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | +| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | +{% endif %} {% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 2e2297fd96..f739d32bfd 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -1,6 +1,7 @@ --- title: 组织的仓库权限级别 intro: '您可以通过细化权限级别自定义组织中每个仓库的权限，从而为每个用户提供所需的功能和任务权限。' +miniTocMaxHeadingLevel: 4 redirect_from: - /articles/repository-permission-levels-for-an-organization-early-access-program/ - /articles/repository-permission-levels-for-an-organization @@ -42,95 +43,124 @@ versions: {% endwarning %} ### 每个权限级别的仓库权限 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} -| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| -| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | -| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | -| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | -| 打开议题 | **X** | **X** | **X** | **X** | **X** | -| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | -| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | -| 受理议题 | **X** | **X** | **X** | **X** | **X** | -| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | -| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | -| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 查看 [GitHub 操作工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 编辑 wiki | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [举报滥用或垃圾内容](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| 应用/忽略标签 | | **X** | **X** | **X** | **X** | -| 创建、编辑、删除标签 | | | **X** | **X** | **X** | -| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %} -| 应用里程碑 | | **X** | **X** | **X** | **X** | -| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| 申请[拉取请求审查](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | -| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | -| [隐藏任何人的评论](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [锁定对话](/articles/locking-conversations) | | | **X** | **X** | **X** | -| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | -| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [将拉取请求草稿标记为可供审查](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| [将拉取请求转换为草稿](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | -| 对拉取请求[应用建议的更改](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| 创建[状态检查](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 创建、编辑、运行、重新运行和取消 [GitHub 操作工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| 创建和编辑发行版 | | | **X** | **X** | **X** | -| 查看发行版草稿 | | | **X** | **X** | **X** | -| 编辑仓库的说明 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [删除包](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} -| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | -| 启用项目板 | | | | **X** | **X** | -| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | -| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 限制[仓库中的交互](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** |{% endif %} -| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | -| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | -| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | -| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | -| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | -| 更改仓库设置 | | | | | **X** | -| 管理团队和协作者对仓库的权限 | | | | | **X** | -| 编辑仓库的默认分支 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **X** | -| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **X** | **X** | **X** |{% endif %} -| 管理 web 挂钩和部署密钥 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 为私有仓库[启用依赖关系图](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | -| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | | | | | **X** | -| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** | -| [管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** | -| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报，并解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %} -| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** |{% endif %} -| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | -| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | -| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库 | | | **X** | **X** | **X** | -| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %} +**注：**使用安全功能所需的仓库权限列于下面的“[安全功能的权限要求](#permission-requirements-for-security-features)”。 + +{% endnote %} +| +{% endif %} +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | +| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | +| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | +| 打开议题 | **X** | **X** | **X** | **X** | **X** | +| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | +| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | +| 受理议题 | **X** | **X** | **X** | **X** | **X** | +| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | +| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | +| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 查看 [GitHub 操作工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| 编辑 wiki | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [举报滥用或垃圾内容](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| 应用/忽略标签 | | **X** | **X** | **X** | **X** | +| 创建、编辑、删除标签 | | | **X** | **X** | **X** | +| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +{% endif %} +| 应用里程碑 | | **X** | **X** | **X** | **X** | +| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| 申请[拉取请求审查](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | +| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | +| [隐藏任何人的评论](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [锁定对话](/articles/locking-conversations) | | | **X** | **X** | **X** | +| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | +| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [将拉取请求草稿标记为可供审查](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [将拉取请求转换为草稿](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | +| 对拉取请求[应用建议的更改](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | +| 创建[状态检查](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 创建、编辑、运行、重新运行和取消 [GitHub 操作工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +{% endif %} +| 创建和编辑发行版 | | | **X** | **X** | **X** | +| 查看发行版草稿 | | | **X** | **X** | **X** | +| 编辑仓库的说明 | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| [删除包](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %} +| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | +| 启用项目板 | | | | **X** | **X** | +| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | +| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 限制[仓库中的交互](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | | **X** | **X** +{% endif %} +| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | +| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | +| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | +| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | +| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | +| 更改仓库设置 | | | | | **X** | +| 管理团队和协作者对仓库的权限 | | | | | **X** | +| 编辑仓库的默认分支 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **X** | +| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **X** | **X** | **X** +{% endif %} +| 管理 web 挂钩和部署密钥 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} +| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** +{% endif %} +| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | +| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | +| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库 | | | **X** | **X** | **X** | +| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### 安全功能的权限要求 + +在本节中，您可以找到一些安全功能所需的仓库权限级别，例如 {% data variables.product.prodname_dependabot %} 和 {% data variables.product.prodname_advanced_security %} 功能。 + +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:---------------------------------------------------------------------------------------------------------------------:|{% if currentVersion == "free-pro-team@latest" %} +| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | | | | | **X** | +| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | +| [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** | +| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | +| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** | +| 为私有仓库[启用依赖关系图](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | +| [查看依赖项审查](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +{% endif %} +{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md index d536781184..cf2a82f136 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain.md @@ -15,7 +15,7 @@ versions: 外部协作者不受限于已验证域的电子邮件通知。 有关外部协作者的更多信息，请参阅“[组织的权限级别](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)”。 -如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." +如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 更多信息请参阅“[验证企业帐户的域](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)”。 ### 将电子邮件通知限于已批准的域 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md index ed41be65ce..c9accc36e9 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain.md @@ -14,7 +14,7 @@ versions: 验证组织域的所有权后，将在组织的资料中显示“Verified（已验证）”徽章。 如果您的组织位于 {% data variables.product.prodname_ghe_cloud %} 上并且已同意公司服务条款，则组织所有者将能够通过查看验证域内每个成员的电子邮件地址来验证组织成员的身份。 更多信息请参阅“[关于组织的资料页面](/articles/about-your-organization-s-profile/)”和“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。 -如果您的组织由企业帐户拥有，则“已验证”徽章将显示在组织的基本资料上，除了显示组织的任何已验证域之外，还能够显示企业帐户的任何已验证域。 For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." +如果您的组织由企业帐户拥有，则“已验证”徽章将显示在组织的基本资料上，除了显示组织的任何已验证域之外，还能够显示企业帐户的任何已验证域。 更多信息请参阅“[验证企业帐户的域](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)”。 {% data reusables.organizations.verified-domains-details %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md index 8515671786..21271412e3 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md @@ -1,31 +1,31 @@ --- -title: About identity and access management for your enterprise account -intro: You can centrally manage access to your enterprise's resources, organization membership, and team membership using your identity provider (IdP). +title: 关于企业帐户的身份和访问管理 +intro: 您可以使用身份提供程序 (IdP) 集中管理对企业资源、组织成员身份和团队成员身份的访问。 product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' --- -### About identity and access management for your enterprise account +### 关于企业帐户的身份和访问管理 -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} 更多信息请参阅“[为企业帐户中的组织启用 SAML 单点登录](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)”。 -After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. +启用 SAML SSO 后，根据使用的 IDP，您可能能够启用额外的身份和访问管理功能。 -{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.about-user-provisioning-enterprise-account %}更多信息请参阅“[关于企业帐户中组织的用户配置](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)”。 -If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." +如果使用 Azure AD 作为 IDP，您可以使用团队同步来管理每个组织中的团队成员身份。 {% data reusables.identity-and-permissions.about-team-sync %} 更多信息请参阅“[管理企业帐户中组织的团队同步](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 -### Supported IdPs +### 支持的 IdP -We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。 +我们测试并正式支持以下 IdP。 对于 SAML SSO，我们向执行 SAML 2.0 标准的所有身份提供程序提供有限的支持。 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。 -| IdP | SAML | User provisioning | 团队同步 | -| -------------------------------------------- |:--------------------------------------------------------------:|:--------------------------------------------------------------:|:-------------------------------------------------------------:| -| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | -| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} -| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| IdP | SAML | 用户预配 | 团队同步 | +| -------------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} [Beta](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md index 340cafd61d..bb61acc0fc 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: About user provisioning for organizations in your enterprise account -intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP). +title: 关于企业帐户中组织的用户预配 +intro: 您可以直接从身份提供程序 (IdP) 管理企业帐户中的组织成员身份。 product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' @@ -12,7 +12,7 @@ versions: {% data reusables.scim.enterprise-account-scim %}（可选）您也可以启用 SAML 预配和单独取消预配。 -If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. 如果启用 SAML 预配，则每当企业成员访问受企业帐户 SAML 配置保护的资源时，该 SAML 断言都将触发预配。 +如果您在 IdP 中为 {% data variables.product.product_name %} 应用程序配置 SCIM，则每次更改 IdP 中的组成员身份时，IdP 都会向 {% data variables.product.prodname_dotcom %} 发出 SCIM 调用来更新相应的组织成员身份。 如果启用 SAML 预配，则每当企业成员访问受企业帐户 SAML 配置保护的资源时，该 SAML 断言都将触发预配。 对于每个 SCIM 呼叫或 SAML 断言，{% data variables.product.product_name %} 都将检查用户所属的 IdP 组并执行以下操作： diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md index 5ccf47f7ad..6a78ea296c 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Configuring identity and access management for your enterprise account -intro: You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise. +title: 为企业帐户配置身份和访问管理 +intro: 您可以为企业管理 SAML 单点登录、用户预配和团队同步。 product: '{% data reusables.gated-features.enterprise-accounts %}' mapTopic: true versions: diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index d32250482f..7649f151f7 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -1,13 +1,13 @@ --- title: 为企业帐户中的组织启用 SAML 单点登录 -intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +intro: '通过跨企业帐户拥有的所有组织的 IDP 启用 SAML 单点登录 (SSO) 和集中身份验证，可以控制并保护对资源（如仓库、议题和拉取请求）的访问。' product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account. +permissions: 企业所有者可以对企业帐户中的组织启用 SAML 单点登录。 versions: free-pro-team: '*' --- -### About SAML single sign-on for enterprise accounts +### 关于企业帐户的 SAML 单点登录 {% data reusables.saml.dotcom-saml-explanation %}更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)”。 @@ -19,7 +19,7 @@ versions: {% data reusables.scim.enterprise-account-scim %} 如果您没有参与私人测试，那么 SIM 卡不支持企业账户。 更多信息请参阅“[关于企业帐户中组织的用户配置](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)”。 -### Enabling SAML single-sign on for organizations in your enterprise account +### 为企业帐户中的组织启用 SAML 单点登录 {% note %} @@ -27,7 +27,7 @@ versions: {% endnote %} -For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)." +有关如何使用 Okta 启用 SAML 的更多详细信息，请参阅“[使用 Okta 为企业帐户配置 SAML 单点登录和 SCIM](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} @@ -35,8 +35,8 @@ For more detailed information about how to enable SAML using Okta, see "[Configu 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} 5. 在“SAML single sign-on”（SAML 单点登录）下，选择 **Enable SAML authentication（启用 SAML 身份验证）**。 ![用于启用 SAML SSO 的复选框](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) 6. 在 **Sign on URL（登录 URL）**字段中，为单点登录请求输入您的 IdP 的 HTTPS 端点。 此值可在 IdP 配置中找到。 ![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![SAML 签发者姓名字段](/assets/images/help/saml/saml_issuer.png) +7. （可选）在 **Issuer（签发者）**字段中，输入 SAML 签发者 URL 以验证已发送消息的真实性。 ![SAML 签发者姓名字段](/assets/images/help/saml/saml_issuer.png) 8. 在 **Public Certificate（公共证书）**下，粘贴证书以验证 SAML 响应。 ![身份提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png) -9. 要验证来自 SAML 签发者的请求的完整性，请单击 {% octicon "pencil" aria-label="The edit icon" %}。 Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![SAML 签发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) +9. 要验证来自 SAML 签发者的请求的完整性，请单击 {% octicon "pencil" aria-label="The edit icon" %}。 然后，在“Signature Method（签名方法）”和“Digest Method（摘要方法）”下拉菜单中，选择 SAML 签发者使用的哈希算法。 ![SAML 签发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) 10. 在为企业启用 SAML SSO 之前，单击 **Test SAML configuration（测试 SMAL 配置）** ，以确保已输入的信息正确。 ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png) 11. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md index ae108398db..27331169a0 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md @@ -33,7 +33,9 @@ versions: 要使用许可的 {% data variables.product.prodname_enterprise %} 部分，订阅者在 {% data variables.product.prodname_dotcom_the_website %} 上的用户帐户必须是或成为 {% data variables.product.prodname_dotcom_the_website %} 上的企业所拥有组织的成员。 -组织所有者可以通过电子邮件地址邀请新成员加入组织。 组织所有者邀请的电子邮件地址必须匹配 {% data variables.product.prodname_vs %} 订阅者的用户主名 (UPN)，它应该是一个电子邮件地址。 订阅者可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的现有用户帐户或创建一个新帐户来接受邀请。 +组织所有者可以通过电子邮件地址邀请新成员加入组织。 订阅者可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的现有用户帐户或创建一个新帐户来接受邀请。 + +虽然不是必需的，但我们建议组织所有者将邀请发送到 {% data variables.product.prodname_vs %} 订阅者的用户主名 (UPN) 使用的同一电子邮件地址。 当 {% data variables.product.product_name %} 上的电子邮件地址与订阅者的 UPN 匹配时，您可以确保组织的其他成员不会索要该订阅者的许可证。 更多信息请参阅“[邀请用户加入组织](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)”、“[注册 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)”和“[管理电子邮件首选项](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index 8f683ebc63..a4778a1724 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -1,15 +1,15 @@ --- title: 管理企业帐户中组织的团队同步 -intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.' +intro: '您可以启用身份提供程序 (IdP) 与 {% data variables.product.product_name %} 之间的团队同步，以允许企业帐户拥有的组织通过 IdP 组管理团队成员身份。' product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Enterprise owners can manage team synchronization for an enterprise account. +permissions: 企业所有者可以管理企业帐户的团队同步。 versions: free-pro-team: '*' --- -### About team synchronization for enterprise accounts +### 关于企业帐户的团队同步 -If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. +如果使用 Azure AD 作为 IdP，您可以为企业帐户启用团队同步，以允许组织所有者和团队维护员将企业帐户拥有的组织中的团队与 IdP 组同步。 {% data reusables.identity-and-permissions.about-team-sync %} @@ -37,5 +37,5 @@ If you use Azure AD as your IdP, you can enable team synchronization for your en {% data reusables.identity-and-permissions.team-sync-confirm-saml %} {% data reusables.identity-and-permissions.enable-team-sync-azure %} {% data reusables.identity-and-permissions.team-sync-confirm %} -7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![启用特定 IdP 租户团队同步且含有批准或取消请求选项的待处理请求](/assets/images/help/teams/approve-team-synchronization.png) +7. 查看要连接到企业帐户的 IdP 租户的详细信息，然后单击 **Approve（批准）**。 ![启用特定 IdP 租户团队同步且含有批准或取消请求选项的待处理请求](/assets/images/help/teams/approve-team-synchronization.png) 8. 要禁用团队同步，单击 **Disable team synchronization（禁用团队同步）**。 ![禁用团队同步](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index a6e3e46cd6..33310895b1 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -1,23 +1,23 @@ --- -title: Restricting email notifications for your enterprise account to approved domains -intro: "You can prevent your enterprise's information from leaking into personal accounts by restricting email notifications about activity in organizations owned by your enterprise account to verified domains." +title: 将企业帐户的电子邮件通知限制为已批准的域 +intro: "通过将有关企业帐户所拥有组织中活动的电子邮件通知限制为经过验证的域，可以防止企业的信息泄漏到个人帐户。" product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' -permissions: Enterprise owners can restrict email notifications for an enterprise account. +permissions: 企业所有者可以限制企业帐户的电子邮件通知。 --- {% data reusables.enterprise-accounts.verifying-domains-release-phase %} -### About email restrictions for your enterprise account +### 关于企业帐户的电子邮件限制 -When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +当您将电子邮件通知限制为已验证域时，企业成员只能使用与已验证域关联的电子邮件地址来接收有关企业帐户所拥有组织中活动的电子邮件通知。 可以从企业帐户继承域，也可以为特定组织配置域。 有关组织电子邮件限制的更多信息，请参阅“[将电子邮件通知限制为已批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”。 -If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization. +如果对企业帐户启用了电子邮件限制，则组织所有者无法禁用该企业帐户拥有的任何组织的电子邮件限制。 如果发生更改导致某个组织没有已验证的域（从拥有该组织的企业帐户继承的域或特定组织的域），则该组织的电子邮件限制将被禁用。 -### Restricting email notifications for your enterprise account +### 限制企业帐户的电子邮件通知 -Before you can restrict email notifications for your enterprise account, you must verify at least one domain for the enterprise account. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." +在限制企业帐户的电子邮件通知之前，必须至少验证企业帐户的一个域。 更多信息请参阅“[验证企业帐户的域](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index e45f2fc0a5..658ab89dc0 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -1,10 +1,10 @@ --- -title: Verifying your enterprise account's domain -intro: 'You can confirm the identity of organizations owned by your enterprise account by verifying ownership of your domain names with {% data variables.product.company_short %}.' +title: 验证企业帐户的域 +intro: '您可以通过使用 {% data variables.product.company_short %} 验证域名所有权来确认企业帐户拥有的组织的身份。' product: '{% data reusables.gated-features.enterprise-accounts %}' versions: free-pro-team: '*' -permissions: Enterprise owners can verify an enterprise account's domain. +permissions: 企业所有者可以验证企业帐户的域。 redirect_from: - /github/articles/verifying-your-enterprise-accounts-domain - /early-access/github/articles/verifying-your-enterprise-accounts-domain @@ -14,19 +14,19 @@ redirect_from: ### 关于域验证 -You can confirm that the websites and email addresses listed on the profiles of any organization owned by your enterprise account are controlled by your enterprise by verifying the domains. Verified domains for an enterprise account apply to every organization owned by the enterprise account, and organization owners can verify additional domains for their organizations. 更多信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 +您可以通过验证域，确认企业控制的企业帐户所拥有的任何组织资料中列出的网站和电子邮件地址。 企业帐户的已验证域适用于企业帐户拥有的每个组织，组织所有者可以验证其组织的其他域。 更多信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 -After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %} +验证企业帐户域的所有权后，每个在其资料中列出域的组织资料中将显示"已验证"徽章。 {% data reusables.organizations.verified-domains-details %} -Organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. +组织所有者将能够通过查看已验证域中的每个成员的电子邮件地址来验证组织成员的身份。 -After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account to approved domains](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)." +验证企业帐户的域后，您可以将企业帐户拥有的所有组织的电子邮件通知限制为已验证域。 更多信息请参阅“[将企业帐户的电子邮件通知限制为已批准的域](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)”。 -Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications from any domains verified for the enterprise account, in addition to any domains verified for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +即使您不限制企业帐户的电子邮件通知，但如果组织所有者限制了组织的电子邮件通知，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 有关限制组织通知的更多信息，请参阅“[将电子邮件通知限制为已批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”。 -### Verifying your enterprise account's domain +### 验证企业帐户的域 -To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service. +要验证企业帐户的域，您必须具有使用域托管服务修改域记录的权限。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} @@ -34,9 +34,9 @@ To verify your enterprise account's domain, you must have access to modify domai 1. 单击 **Add a domain（添加域）**。 ![添加域按钮](/assets/images/help/enterprises/add-a-domain-button.png) {% data reusables.organizations.add-domain %} {% data reusables.organizations.add-dns-txt-record %} -1. 等待 DNS 配置更改，最多可能需要 72 小时。 You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. 您应看到命令输出中列出的新 TXT 记录。 +1. 等待 DNS 配置更改，最多可能需要 72 小时。 您可以通过在命令行上运行 `dig` 命令来确认您的 DNS 配置已更改，将 `ENTERPRISE-ACCOUNT` 替换为您企业帐户的名称，将 `example.com` 替换为要验证的域。 您应看到命令输出中列出的新 TXT 记录。 ```shell dig _github-challenge-ENTERPRISE-ACCOUNT.example.com +nostats +nocomments +nocmd TXT ``` {% data reusables.organizations.continue-verifying-domain %} -1. Optionally, after the "Verified" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service. ![已验证徽章](/assets/images/help/organizations/verified-badge.png) \ No newline at end of file +1. （可选）组织的资料上显示“Verified（已验证）”徽章后，从域托管服务的 DNS 记录中删除 TXT 条目。 ![已验证徽章](/assets/images/help/organizations/verified-badge.png) \ No newline at end of file diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md index 0eef53fee2..c0f1e57d8a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme.md @@ -49,6 +49,8 @@ versions: 生成的自述文件用模板预先填充，为您创建个人资料自述文件提供一些启发。 ![带有预填充模板的自述文件](/assets/images/help/repository/personal-repository-readme-template.png) +有关所有可用表情符号及其代码的摘要，请参阅“[表情符号备忘清单](http://www.emoji-cheat-sheet.com/)” 。 + ### 删除个人资料自述文件 如果以下任何一项适用，个人资料自述文件将从您的 {% data variables.product.prodname_dotcom %} 个人资料中被删除： diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 933de4126e..448b934644 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -30,20 +30,23 @@ versions: | {% if currentVersion == "free-pro-team@latest" %}邀请协作者{% else %}添加协作者{% endif %} | | | "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | 更改仓库的可见性 | “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” |{% if currentVersion == "free-pro-team@latest" %} -| 限制与仓库的交互 | "[限制仓库中的交互](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| 重命名分支，包括默认分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" |{% endif %} +| 限制与仓库的交互 | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 重命名分支，包括默认分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" +{% endif %} | 合并受保护分支上的拉取请求（即使没有批准审查） | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)" | | 删除仓库 | "[删除仓库](/github/administering-a-repository/deleting-a-repository)" | | 管理仓库的主题 | "[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} | 管理仓库的安全性和分析设置 | "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 为私有仓库启用依赖项图 | “[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)” |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| 删除包 | “[删除包](/github/managing-packages-with-github-packages/deleting-a-package)” |{% endif %} +| 删除包 | “[删除包](/github/managing-packages-with-github-packages/deleting-a-package)” +{% endif %} | 自定义仓库的社交媒体预览 | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | | 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | 接收 | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}有漏洞依赖项{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %} | "[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | -| 管理私有仓库的数据使用 | “[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)”|{% endif %} +| 管理私有仓库的数据使用 | “[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)” +{% endif %} | 定义仓库的代码所有者 | "[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | | 存档仓库 | "[关于存档仓库](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | 创建安全通告 | "[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | @@ -62,25 +65,27 @@ versions: 协作者还可以执行以下操作。 -| 操作 | 更多信息 | -|:--------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 复刻仓库 | "[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" %} -| 重命名除默认分支以外的分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" |{% endif %} -| 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 |
    • "[关于议题](/github/managing-your-work-on-github/about-issues)"
    • "[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[管理破坏性评论](/github/building-a-strong-community/managing-disruptive-comments)"
    | -| 在仓库中创建、分配、关闭和重新打开议题 | "[使用议题管理工作](/github/managing-your-work-on-github/managing-your-work-with-issues)" | -| 在仓库中管理议题和拉取请求的标签 | "[标记议题和拉取请求](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | -| 在仓库中管理议题和拉取请求的里程碑 | "[创建和编辑议题及拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | -| 将仓库中的议题或拉取请求标记为重复项 | "[关于重复的议题和拉取请求](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| 操作 | 更多信息 | +|:--------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 复刻仓库 | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| 重命名除默认分支以外的分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" +{% endif %} +| 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 |
    • "[关于议题](/github/managing-your-work-on-github/about-issues)"
    • "[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[管理破坏性评论](/github/building-a-strong-community/managing-disruptive-comments)"
    | +| 在仓库中创建、分配、关闭和重新打开议题 | "[使用议题管理工作](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| 在仓库中管理议题和拉取请求的标签 | "[标记议题和拉取请求](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| 在仓库中管理议题和拉取请求的里程碑 | "[创建和编辑议题及拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| 将仓库中的议题或拉取请求标记为重复项 | "[关于重复的议题和拉取请求](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | | 在仓库中创建、合并和关闭拉取请求 | "[通过拉取请求提议工作更改](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% if currentVersion == "free-pro-team@latest" %} | 启用或禁用自动合并拉取请求 | "[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %} -| 将建议的更改应用于仓库中的拉取请求 | "[在拉取请求中加入反馈](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | -| 从仓库的复刻创建拉取请求 | "[从复刻创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | -| 提交影响拉取请求可合并性的拉取请求审查 | "[审查拉取请求中提议的更改](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | -| 为仓库创建和编辑 wiki | "[关于 wikis](/github/building-a-strong-community/about-wikis)" | -| 为仓库创建和编辑发行版 | “[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)” | +| 将建议的更改应用于仓库中的拉取请求 | "[在拉取请求中加入反馈](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | +| 从仓库的复刻创建拉取请求 | "[从复刻创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| 提交影响拉取请求可合并性的拉取请求审查 | "[审查拉取请求中提议的更改](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| 为仓库创建和编辑 wiki | "[关于 wikis](/github/building-a-strong-community/about-wikis)" | +| 为仓库创建和编辑发行版 | “[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)” | | 作为仓库的代码所有者 | "[关于代码所有者](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %} -| 发布、查看或安装包 | "[发布和管理包](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} -| 作为仓库协作者删除自己 | "[从协作者的仓库删除您自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | +| 发布、查看或安装包 | "[发布和管理包](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" +{% endif %} +| 作为仓库协作者删除自己 | "[从协作者的仓库删除您自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md index 3ae12d62a5..8992790549 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md @@ -1,6 +1,6 @@ --- title: GitHub 发送的电子邮件类型 -intro: '您可以从 {% data variables.product.product_name %} 收到几种类型的电子邮件，包括通知、帐户信息和营销通信。' +intro: '您可以从 {% data variables.product.product_name %} 收到几种类型的电子邮件，包括通知、帐户信息、客户研究邀请和营销通信。' redirect_from: - /articles/types-of-emails-github-sends versions: @@ -25,6 +25,17 @@ versions: 如果您已升级为付费产品或功能，则将在帐户的主电子邮件地址收到帐单收据。 更多信息请参阅“[设置帐单邮箱](/articles/setting-your-billing-email)”。 +### 客户研究电子邮件 + +{% data variables.product.product_name %} 有时会寻求客户参加研究会议，以帮助我们构建更好的 GitHub。 这些会议是远程进行的，对世界各地的客户开放，可能包括： + +- 反馈调查 +- 研究访谈 +- 可用性测试会议 +- 预览早期原型或概念 + +这些电子邮件并不常见，您可以选择是否参与。 如果您对参加研究会议的机会感兴趣，您可以加入 GitHub 客户研究小组。 更多信息请参阅“[GitHub 客户体验研究](https://cxr.github.com)”。 + ### 营销电子邮件 {% data variables.product.product_name %} 偶尔会发送以下类型的营销电子邮件： diff --git a/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md b/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md index 5fb314384f..de1cd64215 100644 --- a/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md +++ b/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md @@ -55,7 +55,7 @@ GitHub Actions 按用量计费。 [Actions 文档](/actions)包含详细信息 - 任何给我们的服务器带来负担的活动，如果这种负担与提供给用户的收益不成比例（例如，不要将 Action 用作内容交付网络或作为无服务器应用程序的一部分，但收益低负担也低的 Action 可能没问题）；或 - 与使用 GitHub Actions 的仓库相关的软件项目创建、测试、部署或发布无关的任何其他活动。 -为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 滥用 GitHub Actions 可能会导致作业终止，或者您使用 GitHub Actions 的权限受限。 +为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 滥用 GitHub Actions 可能导致作业终止、使用 GitHub Actions 的权限受到限制，或者禁用以违反这些条款的方式运行 Actions 的仓库。 #### b. Packages 的使用 GitHub Packages 按用量计费。 [Packages 文档](/packages)包含详细信息，包括带宽和存储量（取决于您的帐户计划）以及如何监控您的 Packages 使用和设置使用限制。 Packages 带宽使用受 [GitHub 可接受使用政策](/github/site-policy/github-acceptable-use-policies)限制。 diff --git a/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md b/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md index ff692bdcd1..9e0582e4e9 100644 --- a/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md +++ b/translations/zh-CN/content/github/site-policy/github-and-trade-controls.md @@ -27,7 +27,9 @@ GitHub 的愿景是成为开发者合作的全球平台，不管开发者居住 GitHub 现在获得了 OFAC 的许可，可以为位于或居住在伊朗的开发者提供云服务。 这包括为个人和组织提供的一切免费和有偿的公共和私人服务。 -特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub.com。 此外，用户不得为包括受制裁国政府在内的这类当事方或代表他们使用 GitHub.com。 此外，GitHub.com 不得用于适用的出口管制法律所禁止的目的，包括 [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) 中所述的被禁止最终用途。 +GitHub 云服务（包括付费和免费）也向古巴的开发者普遍开放。 + +特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub.com。 此外，用户不得为通常包括受制裁国政府在内的这类当事方或代表他们使用 GitHub.com。 此外，GitHub.com 不得用于适用的出口管制法律所禁止的目的，包括 [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) 中所述的被禁止最终用途。 #### GitHub Enterprise Server @@ -41,13 +43,13 @@ GitHub Enterprise Server 不能出售、出口或再出口到 EAR 的补充编 #### 美国政府对哪些国家和地区 实行制裁？ -克里米亚、古巴、伊朗、朝鲜和叙利亚。 但是，就伊朗而言，GitHub 现在已获得美国 财政部外国资产控制办公室 (OFAC) 的许可，可为位于该国或居住在该国的开发者提供云服务。 +克里米亚、古巴、伊朗、朝鲜和叙利亚。 但是，就伊朗而言，GitHub 现在已获得美国 财政部外国资产控制办公室 (OFAC) 的许可，可为位于该国或居住在该国的开发者提供云服务。 GitHub 云服务（包括付费和免费）也向古巴的开发者普遍开放。 #### GitHub 如何确保不在受制裁国家及地区生活和/或与受制裁国家及地区有专业联系的民间团体仍然能够访问或上诉？ 在很少的情况下，会有帐户无意或错误地受到影响，此时我们有上诉流程来处理这种情况。 -如果个别用户或组织管理员认为他们被错误标记，则该用户有机会向 GitHub 提供验证信息，对该标记提出上诉。 如果 GitHub 收到充分的信息，能够核实用户或组织不属于美国制裁的地区或美国经济制裁限制的地区，则会撤销该标记。 经济制裁限制的地区，则会撤销该标记。 请参阅[个别帐户上诉申请表](https://airtable.com/shrGBcceazKIoz6pY)和[组织帐户上诉申请表](https://airtable.com/shrB2je5RBkqLEt5D)。 +如果个别用户或组织管理员认为他们被错误标记，则该用户有机会向 GitHub 提供验证信息，对该标记提出上诉。 如果 GitHub 收到充分的信息，能够核实用户或组织不属于我们未获得许可的美国制裁地区或美国 经济制裁限制的地区，则会撤销该标记。 请参阅[个别帐户上诉申请表](https://airtable.com/shrGBcceazKIoz6pY)和[组织帐户上诉申请表](https://airtable.com/shrB2je5RBkqLEt5D)。 #### 到这些地区旅行是否会受到影响？ @@ -55,13 +57,17 @@ GitHub Enterprise Server 不能出售、出口或再出口到 EAR 的补充编 #### 什么可用和不可用？ -GitHub 现在获得了 OFAC 的许可，可以向位于或居住在美国制裁国家——伊朗的开发者提供云服务。 该许可为个人和组织提供的一切免费和有偿的公共和私人服务。 但是，特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub。 +GitHub 现在获得了 OFAC 的许可，可以向位于或居住在美国制裁国家——伊朗的开发者提供云服务。 该许可为个人和组织提供的一切免费和有偿的公共和私人服务。 GitHub 云服务（包括付费和免费）也向古巴的开发者普遍开放。 -GitHub 承诺继续向受美国制裁地区拥有个人和组织帐户的开发者免费提供公共仓库服务。 包括有限制地访问免费服务，例如用于开源项目（和相关公共页面）的公共仓库、公共Gist 以及分配的免费操作分钟数，但只能用于个人通信，而不得用于商业目的。 +GitHub 承诺继续向叙利亚和克里米亚拥有个人和组织帐户的开发者免费提供公共仓库服务。 包括有限制地访问免费服务，例如用于开源项目（和相关公共页面）的公共仓库、公共Gist 以及分配的免费操作分钟数，但只能用于个人通信，而不得用于商业目的。 对于这些受制裁地区的付费组织级帐户，用户对其公共仓库的访问有限，这些仓库已降级为存档的只读仓库。 但是，对于这些受制裁地区的免费组织级帐户，用户仍然可以完全访问用于开源项目（和相关公共页面）的免费公共仓库、公共 Gist 和分配的免费操作分钟数。 -GitHub will continue advocating with U.S. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. 监管机构提倡让受制裁地区的开发者尽可能获得代码协作服务，例如 Syria 和 Crimea，包括访问私有仓库。 我们相信，提供这些服务可以促进人类进步、国际交流和美国一贯的 促进言论自由和信息自由流通的一贯外交政策。 +GitHub will continue advocating with U.S. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. 监管机构提倡让叙利亚和克里米亚的开发者尽可能获得代码协作服务，包括访问私有仓库。 我们相信，提供这些服务可以促进人类进步、国际交流和美国一贯的 促进言论自由和信息自由流通的一贯外交政策。 + +特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub。 用户不得为通常包括受制裁国政府在内的这类当事方或代表他们使用 GitHub.com。 + +GitHub 服务不适用于位于朝鲜或以其他方式居住在朝鲜的开发者。 #### 如何定义这些特定用户？ @@ -89,8 +95,13 @@ GitHub will continue advocating with U.S. regulators for the greatest possible a 特别指定国民 (SDN) 、根据美国和其他适用法律被拒绝或封锁的其他方 以及某些政府官员可能会被限制访问或使用 GitHub。 -如果 GitHub 确定某人属于受限制类别（SDN、其他被阻止的当事方或某些政府官员），则他们的帐户将被标记，并且他们将无法使用任何 GitHub 功能。 如果他们认为自己被错误标记，他们有机会使用我们的[个人帐户申诉申请表](https://airtable.com/shrGBcceazKIoz6pY)向 GitHub 提供验证信息，对此类标记提出申诉。 如果 GitHub 收到足够的信息，核实此人不属于受美国限制的类别 经济制裁限制的地区，则会撤销该标记。 +如果 GitHub 确定个人或组织属于受限制类别（SDN、其他被阻止的当事方或某些政府官员），则他们的帐户将被标记，并且他们将无法使用任何 GitHub 功能。 如果他们认为自己被错误标记，他们有机会使用我们的[个人帐户申诉申请表或组织帐户申诉申请表](https://airtable.com/shrGBcceazKIoz6pY)向 GitHub 提供验证信息，对此类标记提出申诉。 如果 GitHub 收到足够的信息，核实此人不属于受美国限制的类别 经济制裁限制的地区，则会撤销该标记。 #### 伊朗 GitHub 用户能否在许可下使用付费服务？ 根据我们从 OFAC 获得的许可，我们正在为伊朗用户恢复所有云服务，包括付费服务。 我们接受所有主要的信用卡，但是第三方为我们处理付款，因此付款受付款处理方的条款和条件的约束。 这些第三方可能规定阻止伊朗付款的限制。 + +#### 您能向古巴开发者说明 GitHub 的可用性吗？ + +GitHub 云服务（包括付费和免费）向位于古巴的开发者普遍开放。 +特别指定国民 (SDN) 、被美国拒绝或阻止的其他方 以及某些政府官员可能会被限制访问或使用 GitHub。 此外，用户不得为通常包括受制裁国政府在内的这类当事方或代表他们使用 GitHub.com。 diff --git a/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md index 41837df359..8125642cc8 100644 --- a/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -生效日期：**2021 年 1 月 6 日** +生效日期：**2021 年 1 月 29 日** GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享您的数据方面提供很大的透明度。 为此，我们提供此页面，以详细介绍了我们的[子处理商](#github-subprocessors)，以及我们如何使用 [cookie](#cookies-on-github)。 @@ -18,28 +18,26 @@ GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享 我们与第三方子处理商（例如我们的供应商和服务提供商）分享您的信息时，我们仍对您的信息负责。 我们在引入新供应商时，会竭尽所能保持您的信任，并且要求所有供应商与我们签订数据保护协议，以约束他们对用户个人信息（定义见[隐私声明](/articles/github-privacy-statement/)）的处理。 -| 子处理商名称 | 处理说明 | 处理地点 | 公司地点 | -|:------------------ |:------------ |:---- |:---- | -| Automattic | 博客服务 | 美国 | 美国 | -| AWS Amazon | 数据托管 | 美国 | 美国 | -| Braintree (PayPal) | 订阅费用信用卡支付处理商 | 美国 | 美国 | -| Clearbit | 营销数据充实服务 | 美国 | 美国 | -| Discourse | 社区论坛软件提供商 | 美国 | 美国 | -| Eloqua | 营销活动自动化 | 美国 | 美国 | -| Google Apps | 公司内部基础设施 | 美国 | 美国 | -| Google Analytics | 网站分析和性能 | 美国 | 美国 | -| MailChimp | 客户事件单邮件服务提供商 | 美国 | 美国 | -| Mailgun | 交易邮件服务提供商 | 美国 | 美国 | -| Microsoft | Microsoft 服务 | 美国 | 美国 | -| Monday.com | 团队协作和项目管理平台 | 美国 | 以色列 | -| Nexmo | 短信通知提供商 | 美国 | 美国 | -| Salesforce.com | 客户关系管理 | 美国 | 美国 | -| Sendgrid | 交易邮件服务提供商 | 美国 | 美国 | -| Sentry.io | 应用程序监控提供商 | 美国 | 美国 | -| Stripe | 支付服务提供商 | 美国 | 美国 | -| Twilio | 短信通知提供商 | 美国 | 美国 | -| Zendesk | 客户支持事件单系统 | 美国 | 美国 | -| Zuora | 公司计费系统 | 美国 | 美国 | +| 子处理商名称 | 处理说明 | 处理地点 | 公司地点 | +|:------------------------ |:----------------- |:---- |:---- | +| Automattic | 博客服务 | 美国 | 美国 | +| AWS Amazon | 数据托管 | 美国 | 美国 | +| Braintree (PayPal) | 订阅费用信用卡支付处理商 | 美国 | 美国 | +| Clearbit | 营销数据充实服务 | 美国 | 美国 | +| Discourse | 社区论坛软件提供商 | 美国 | 美国 | +| Eloqua | 营销活动自动化 | 美国 | 美国 | +| Google Apps | 公司内部基础设施 | 美国 | 美国 | +| MailChimp | 客户事件单邮件服务提供商 | 美国 | 美国 | +| Mailgun | 交易邮件服务提供商 | 美国 | 美国 | +| Microsoft | Microsoft 服务 | 美国 | 美国 | +| Monday.com | 团队协作和项目管理平台 | 美国 | 以色列 | +| Nexmo | 短信通知提供商 | 美国 | 美国 | +| Salesforce.com | 客户关系管理 | 美国 | 美国 | +| Sentry.io | 应用程序监控提供商 | 美国 | 美国 | +| Stripe | 支付服务提供商 | 美国 | 美国 | +| Twilio & Twilio Sendgrid | 短信通知提供商和交易邮件服务提供商 | 美国 | 美国 | +| Zendesk | 客户支持事件单系统 | 美国 | 美国 | +| Zuora | 公司计费系统 | 美国 | 美国 | 在我们引入新的子处理商来处理用户个人信息、删除子处理商或更改使用子处理商的方式时，我们将更新本页面。 如果您对新的子处理商有疑问或疑虑，我们乐意提供帮助。 请通过 {% data variables.contact.contact_privacy %} 联系我们。 diff --git a/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index d723d4476e..12ba7d8a73 100644 --- a/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -146,7 +146,14 @@ versions: ### 费用补偿 -我们保留按照法律规定寻求补偿与回应信息要求有关的管理费用的权利。 +根据州和联邦法律，GitHub 可以要求补偿与遵守有效法律要求（如传票、法院命令或搜查令）相关的费用。 我们只收取部分费用，这些补偿只包括我们为遵守法律命令而实际发生的一部分费用。 + +虽然我们在紧急情况下不收费，但除非法律另有要求，否则我们将根据以下安排要求补偿为满足所有其他法律要求产生的费用： + +- 最多 25 个标识符的初始搜索：免费 +- 最多 5 个帐户的订阅者信息/数据制作：免费 +- 为 5 个以上帐户制作订阅者信息/数据：每个帐户 20 美元 +- 二次搜索：每次搜索 10 美元 ### 数据保存 diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md index 57b1b5a4d6..97e4ce83ac 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -1,13 +1,13 @@ --- -title: Attributing sponsorships to your organization -intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +title: 将赞助归因于组织 +intro: '您可以将您某个组织支付的赞助归因于另一个组织。' versions: free-pro-team: '*' -permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +permissions: 对两个组织具有组织所有者权限的人可以将一个组织的赞助归因于另一个组织。 --- -1. Navigate to the organization whose sponsorships you want to attribute to another organization. -1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) -1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) -1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) -1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file +1. 导航到要将其赞助归因于另一个组织的组织。 +1. 在组织名称下，单击 {% octicon "heart" aria-label="The heart icon" %} **Sponsoring（赞助）**。 !["赞助" 选项卡](/assets/images/help/sponsors/sponsoring-tab.png) +1. 在右上角，单击 {% octicon "gear" aria-label="The gear icon" %} **Settings（设置）**。 !["设置"按钮](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. 在“Link sponsorships to another account（将赞助链接到另一个帐户）”下，使用下拉菜单，然后单击要将此组织的赞助归因到的组织。 ![选择帐户的下拉菜单](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. 单击 **Link account（链接帐户）**。 !["链接帐户"按钮](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index f8f6517e56..24afc80e09 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -22,7 +22,7 @@ permissions: 任何人都可以代表自己的用户帐户赞助帐户。 组织 - 作为重视开源的组织，培养品牌知名度 - 感谢开源开发者构建库来补充您的组织提供的产品 -您可以使用信用卡赞助 {% data variables.product.product_name %} 上的帐户。 如果您的组织要开发票，请[联系我们](https://support.github.com/contact/org-sponsors-waitlist)。 +您可以使用信用卡赞助 {% data variables.product.product_name %} 上的帐户。 如果您的组织希望按发票付款，请[联系我们](https://support.github.com/contact/org-sponsors-waitlist)。 {% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md index 352e1e62c0..770d1324ab 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-github-pages-and-jekyll.md @@ -38,7 +38,7 @@ Windows 并未正式支持 Jekyll。 更多信息请参阅 Jekyll 文档中的 对于 {% data variables.product.prodname_pages %} 站点，有些配置设置不能更改。 -``` +```yaml lsi: false safe: true source: [your repo's top level directory] @@ -112,7 +112,7 @@ kramdown: 如果想使用其他突显工具，如 `highlight.js`，则必须更新项目的 *_config.yml* 文件来禁用 Jekyll 的语法突显。 -``` +```yaml kramdown: syntax_highlighter_opts: disable : true diff --git a/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md index a6bf36fdf7..ce8191070f 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/zh-CN/content/github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites.md @@ -44,13 +44,13 @@ versions: 您可以配置第三方服务（例如 [Travis CI](https://travis-ci.org/)）以在每次提交后显示错误消息。 1. 如果尚未在发布源的根目录中添加名为 _Gemfile_、包含以下内容的文件，请添加： - ``` + ```ruby source `https://rubygems.org` gem `github-pages` ``` 2. 为您选择的测试服务配置站点仓库。 例如，要使用 [Travis CI](https://travis-ci.org/)，请在发布源的根目录下添加一个名为 _.travis.yml_、包含以下内容的文件： - ``` + ```yaml language: ruby rvm: - 2.3 diff --git a/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md index e9e69f89f7..940d60d30e 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -40,7 +40,7 @@ versions: {% data reusables.pages.navigate-publishing-source %} 1. 创建一个名为 _/assets/css/style.scss_ 的新文件。 2. 在文件顶部添加以下内容： - ``` + ```scss --- --- diff --git a/translations/zh-CN/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..af2df207c4 --- /dev/null +++ b/translations/zh-CN/content/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,27 @@ +--- +title: 更改 GitHub Pages 站点的可见性 +intro: '您可以通过公开或私下发布站点来管理项目站点的访问控制。' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: 拥有仓库管理员权限的人可以更改 {% data variables.product.prodname_pages %} 站点的可见性。 +--- + +### 关于 {% data variables.product.prodname_pages %} 站点的访问控制 + +如果您的项目站点是从使用 {% data variables.product.prodname_ghe_cloud %} 的组织拥有的私有或内部仓库发布的，您可以管理站点的访问控制。 通过访问控制，您可以选择将站点公开发布给互联网上的任何人，也可以选择私下发布给对仓库拥有读取权限的人。 私下发布的站点可用于与企业成员分享您的内部文档或知识库。 您无法管理组织站点的访问控制。 有关 {% data variables.product.prodname_pages %} 站点类型的更多信息，请参阅“[关于 GitHub Pages](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 + +私下发布的站点与公开发布的站点位于不同的子域中。 您可以在仓库设置中查看站点的 URL。 如果您使用配置为以仓库名称为路径来构建站点的静态站点生成器，则在将站点更改为私有站点时可能需要更新静态站点生成器的设置。 更多信息请参阅“[在 {% data variables.product.prodname_pages %} 站点中配置 Jekyll](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)”或静态站点生成器的文档。 + +### 更改 {% data variables.product.prodname_pages %} 站点的可见性 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +3. 在 "{% data variables.product.prodname_pages %}" 下，选择 **{% data variables.product.prodname_pages %} visibility（可见性）**下拉菜单，然后单击可见性。 ![选择站点可见性的下拉菜单](/assets/images/help/pages/public-or-private-visibility.png) +4. 要查看您已发布的站点，请在“{% data variables.product.prodname_pages %}”下点击您的站点 URL。 ![私下发布站点的 URL](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/zh-CN/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index 4a0970534b..09b37e3147 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -16,7 +16,7 @@ versions: {% data reusables.files.add-file %} 3. 在文件名字段中，键入 `404.html` 或 `404.md`。 ![文件名字段](/assets/images/help/pages/404-file-name.png) 4. 如果将文件命名为 `404.md`，请将以下 YAML 前页添加到文件的开头： - ``` + ```yaml --- permalink: /404.html --- diff --git a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 84434b743d..92085b6c2d 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -11,6 +11,8 @@ versions: github-ae: '*' --- +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + ### 基本要求 必须安装 Jekyll 和 Git 后才可使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅 Jekyll 文档中的[安装](https://jekyllrb.com/docs/installation/)和“[设置 Git](/articles/set-up-git)”。 @@ -95,7 +97,8 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md` 下。 +您可以通过创建更多新文件向网站添加更多页面。 每个文件都将在网站上与发布源相同的目录结构中。 例如，如果项目网站的发布源是 `gh-pages` 分支，并且您在 `gh-pages` 分支上创建了名为 `/about/contact-us.md` 的新文件，该文件将在 {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html` 下。 您还可以添加主题以自定义网站的外观。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" %}“[使用主题选择器添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}”[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}”。 diff --git a/translations/zh-CN/content/github/working-with-github-pages/index.md b/translations/zh-CN/content/github/working-with-github-pages/index.md index cab57a854a..913bc15487 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/index.md +++ b/translations/zh-CN/content/github/working-with-github-pages/index.md @@ -25,6 +25,7 @@ versions: {% link_in_list /creating-a-github-pages-site %} {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} + {% link_in_list /changing-the-visibility-of-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} diff --git a/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 3e47fc7041..71f3a7e73d 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/zh-CN/content/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -78,7 +78,7 @@ versions: 此错误意味着您使用了非拉丁字符（如 `日本語`）但没有告诉计算机预期这些符号。 要排除故障，请将以下行添加到 *_config.yml* 文件以实施 UTF-8 编码： -``` +```yaml encoding: UTF-8 ``` diff --git a/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md index d67f7dc2ee..6407bfc682 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- title: 取消发布 GitHub Pages 站点 -intro: '您可以取消发布 {% data variables.product.prodname_pages %} 站点，使该站点不再对{% if currentVersion == "free-pro-team@latest" %}公众{% else %}所有 {% data variables.product.product_location %} 用户{% endif %}开放。' +intro: '您可以取消发布 {% data variables.product.prodname_pages %} 站点，使该站点不再可用。' redirect_from: - /articles/how-do-i-unpublish-a-project-page/ - /articles/unpublishing-a-project-page/ diff --git a/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md index aa5eb8a220..57b6494f3f 100644 --- a/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md @@ -13,7 +13,7 @@ versions: 要创建标题，请在标题文本前添加一至六个 `#` 符号。 您使用的 `#` 数量将决定标题的大小。 -``` +```markdown # 最大标题 ## 第二大标题 ###### 最小标题 @@ -37,7 +37,7 @@ versions: 您可以使用 `>` 来引用文本。 -``` +```markdown 用 Abraham Lincoln 的话来说： > 原谅我爆粗口 @@ -55,7 +55,7 @@ versions: 使用单反引号可标注句子中的代码或命令。 反引号中的文本不会被格式化。 -``` +```markdown 使用 `git status` 列出尚未提交的所有新文件或已修改文件。 ``` @@ -102,7 +102,7 @@ git commit 通过在一行或多行文本前面添加 `-` 或 `*` 可创建无序列表。 -``` +```markdown - George Washington - John Adams - Thomas Jefferson @@ -112,7 +112,7 @@ git commit 要对列表排序，请在每行前面添加一个编号。 -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams @@ -126,7 +126,7 @@ git commit 要通过 {% data variables.product.product_name %} 上的 web 编辑器或使用等宽字体的文本编辑器（例如 [Atom](https://atom.io/)）创建嵌套列表，您可以直观地对齐列表。 在嵌套列表项的前面键入空格字符，直至列表标记字符（`-` 或 `*`）位于其上方条目中第一个文本字符的正下方。 -``` +```markdown 1. 第一个列表项 - 第一个嵌套列表项 - 第二个嵌套列表项 @@ -140,7 +140,7 @@ git commit 在此例中，您可以通过缩进嵌套列表项至少五个空格，在列表项 `100. 第一个列表项`的下面添加一个嵌套列表项，因为在`第一个列表项`的前面有五个字符 (`100.`) 。 -``` +```markdown 100. 第一个列表项 - 第一个嵌套列表项 ``` @@ -149,7 +149,7 @@ git commit 您可以使用相同的方法创建多层级嵌套列表。 例如，由于在第一个嵌套列表项中，嵌套列表项内容`第一个嵌套列表项`之前有七个空格 (`␣␣␣␣␣-␣`)，因此需要将第二个嵌套列表项缩进七个空格。 -``` +```markdown 100. 第一个列表项 - 第一个嵌套列表项 - 第二个嵌套列表项 diff --git a/translations/zh-CN/content/github/writing-on-github/organizing-information-with-tables.md b/translations/zh-CN/content/github/writing-on-github/organizing-information-with-tables.md index 6447495b0a..25b46f6e3c 100644 --- a/translations/zh-CN/content/github/writing-on-github/organizing-information-with-tables.md +++ b/translations/zh-CN/content/github/writing-on-github/organizing-information-with-tables.md @@ -13,7 +13,7 @@ versions: 您可以用竖线 `|` 和横线 `-` 创建表格。 横线用于创建每列的标题，而竖线用于分隔每列。 必须在表格前包含空白链接，以便其正确呈现。 -``` +```markdown | First Header | Second Header | | ------------- | ------------- | @@ -27,7 +27,7 @@ versions: 单元格的宽度可以不同，无需在列内准确对齐。 标题行的第一列中必须至少有三个横线。 -``` +```markdown | Command | Description | | --- | --- | | git status | List all new or modified files | @@ -40,7 +40,7 @@ versions: 您可以在表格中使用[格式](/articles/basic-writing-and-formatting-syntax)，如链接、内联代码块和文本样式： -``` +```markdown | Command | Description | | --- | --- | | `git status` | List all *new or modified* files | @@ -51,7 +51,7 @@ versions: 您可以在标头行中横线的左侧、右侧或两侧加入冒号 `:`，靠左、靠右或居中对齐列中的文本。 -``` +```markdown | Left-aligned | Center-aligned | Right-aligned | | :--- | :---: | ---: | | git status | git status | git status | @@ -62,7 +62,7 @@ versions: 要包含竖线 `|` 作为单元格中的内容，请在竖线前使用 `\`： -``` +```markdown | Name | Character | | --- | --- | | Backtick | ` | diff --git a/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md b/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md index f9653b6aa6..2189d57d0a 100644 --- a/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md +++ b/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md @@ -80,9 +80,25 @@ GraphQL 是一种[内省](https://graphql.github.io/learn/introspection/)语言 * 查询 `__schema`，列出架构中定义的所有类型并获取关于每个类型的详细信息： ```graphql -query { - __schema { - types { + query { + __schema { + types { + name + kind + description + fields { + name + } + } + } + } + ``` + +* 查询 `__type`，获取关于任何类型的详细信息： + + ```graphql + query { + __type(name: "Repository") { name kind description @@ -91,22 +107,6 @@ query { } } } -} - ``` - -* 查询 `__type`，获取关于任何类型的详细信息： - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} ``` * 您也可以通过 `GET` 请求对架构运行_内省查询_ ： diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index 76ac03cc7b..4f76cd7f20 100644 --- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -14,7 +14,7 @@ versions: 1. 连接到 {% data variables.product.prodname_ghe_server %} 的管理 shell。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。 2. 运行以下命令。 - ``` + ```shell ghe-config 'app.github.insights-available' 'true' && ghe-config-apply ``` 3. 返回到 diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md index 9dfb222ad9..8b0768da96 100644 --- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md +++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md @@ -16,6 +16,7 @@ versions: - 您必须在应用程序服务器上安装依赖项。 - [Docker](https://docs.docker.com/install/) 1.13.0+ - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+ + - [netcat](http://netcat.sourceforge.net/)，通过 apt 用于 [Debian](https://packages.debian.org/search?keywords=netcat) 和 [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) {% note %} diff --git a/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md index a4b907c82f..c04348392b 100644 --- a/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -38,7 +38,7 @@ versions: 有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 {% endif %} -``` +```xml {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} -These examples assume your instance has subdomain isolation enabled. +这些示例假设您的实例已启用子域隔离。 {% endif %} diff --git a/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md index 91e1531e08..8f542643aa 100644 --- a/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -79,12 +79,12 @@ versions: ### 发布包 -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}. +您可以通过使用 *nuget.config* 文件进行身份验证{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}或使用包含 {% data variables.product.prodname_dotcom %} 个人访问令牌 (PAT) 的 `--api-key` 命令行选项，向 {% data variables.product.prodname_registry %} 发布包{% endif %}。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### Publishing a package using a GitHub PAT as your API key +#### 使用 GitHub PAT 作为 API 密钥发布包 -If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +如果您还没有用于 {% data variables.product.prodname_dotcom %} 帐户的 PAT，请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 1. 创建一个新项目。 ```shell @@ -95,7 +95,7 @@ If you don't already have a PAT to use for your {% data variables.product.prodna dotnet pack --configuration Release ``` -3. Publish the package using your PAT as the API key. +3. 使用您的 PAT 作为 API 密钥发布包。 ```shell dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" ``` @@ -104,7 +104,7 @@ If you don't already have a PAT to use for your {% data variables.product.prodna {% endif %} -#### Publishing a package using a *nuget.config* file +#### 使用 *nuget.config* 文件发布包 发布时，您需要将 *csproj* 文件中的 `OWNER` 值用于您的 *nuget.config* 身份验证文件。 在 *.csproj* 文件中指定或增加版本号，然后使用 `dotnet pack` 命令创建该版本的 *.nuspec* 文件。 有关创建包的更多信息，请参阅 Microsoft 文档中的“[创建和发布包](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)”。 diff --git a/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md index 3dcf4e1a13..d74fbff80d 100644 --- a/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -21,9 +21,9 @@ versions: 如果您发布超过 1,000npm 软件包版本到 {% data variables.product.prodname_registry %}，在使用过程中可能会出现性能问题和超时。 -要减少为 npm 包发布的版本数，请考虑删除包版本。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”。 +将来，为了提高服务的性能，您将无法在 {% data variables.product.prodname_dotcom %} 上发布超过 1，000 个版本的包。 在达到此限制之前发布的任何版本仍将是可读的。 -将来，{% data variables.product.company_short %} 将对发布超过 1,000 个版本 npm 包实施硬性限制。 当我们开始对 {% data variables.product.prodname_registry %} 上托管的每个 npm 包实施 1,000 个版本限制时，我们将提供有关如何管理包版本的更多指导。 +如果达到此限制，请考虑删除包版本或联系支持人员寻求帮助。 实施此限制后，我们的文档将就此限制进行更新。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”或“[联系支持人员](/packages/learn-github-packages/about-github-packages#contacting-support)”。 {% endif %} @@ -166,7 +166,7 @@ $ npm login --scope=@OWNER --registry=https://HOSTNAME/_regist {% data reusables.package_registry.add-npmrc-to-repo-step %} 4. 配置项目中的 *package.json* 使用要安装的包。 要将包依赖项添加到 {% data variables.product.prodname_registry %} 的 *package.json* 文件，请指定完整的作用域内包名称，例如 `@my-org/server`。 对于来自 *npmjs.com* 的包，请指定全名，例如 `@babel/core` 或 `@lodash`。 例如，以下 *package.json* 将 `@octo-org/octo-app` 包用作依赖项。 - ``` + ```json { "name": "@my-org/server", "version": "1.0.0", @@ -210,9 +210,9 @@ registry=https://HOSTNAME/_registry/npm/OWNER {% endif %} {% if currentVersion == "enterprise-server@3.0" or currentVersion ver_gt "enterprise-server@3.0" %} -### Using the official NPM registry +### 使用官方 NPM 注册表 -{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% data variables.product.prodname_registry %} 允许您访问 `registry.npmjs.com` 上的官方 NPM 注册表，前提是您的 {% data variables.product.prodname_ghe_server %} 管理员已启用此功能。 更多信息请参阅[连接到官方 NPM 注册表](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry)。 {% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/packages/index.md b/translations/zh-CN/content/packages/index.md index 7894a8d27b..663c06b049 100644 --- a/translations/zh-CN/content/packages/index.md +++ b/translations/zh-CN/content/packages/index.md @@ -12,13 +12,18 @@ featuredLinks: - /packages/manage-packages/installing-a-package popular: - /packages/guides/configuring-npm-for-use-with-github-packages - - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-docker-for-use-with-github-packages + - /packages/learn-github-packages - /packages/guides/configuring-apache-maven-for-use-with-github-packages guideCards: - /packages/guides/configuring-npm-for-use-with-github-packages - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: + - + title: 2021-01-09 的 ghcr.io 维护模式 + date: '2021-01-08' + href: https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09/ - title: ghcr.io 容器名称重定向到容器页 date: '2020-12-14' @@ -27,10 +32,6 @@ changelog: title: 过滤已标记和未标记的容器 date: '2020-12-14' href: https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers/ - - - title: 包容器支持是一个选择性测试版 - date: '2020-11-17' - href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md index eb4d90d700..bfbe056655 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md @@ -25,7 +25,7 @@ versions: {% if currentVersion ver_gt "enterprise-server@2.21" %} -![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/ghes-packages-diagram.png) +![显示托管 npm、Rubygems、Apache Maven、Gradle、Nuget 和 Docker 的 URL 的 GitHub Packages 图表](/assets/images/help/package-registry/ghes-packages-diagram.png) {% endif %} @@ -34,7 +34,7 @@ versions: {% data reusables.package_registry.container-registry-beta %} -![Diagram showing the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) +![显示托管 npm、Rubygems、Apache Maven、Gradle、Nuget 和 Docker 的 URL 的 GitHub Packages 图表](/assets/images/help/package-registry/packages-overview-diagram.png) {% endif %} @@ -150,7 +150,7 @@ versions: ### 管理包 -You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API. 使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”和“[使用 GraphQL 进行调用](/graphql/guides/forming-calls-with-graphql)”。 +您可以在 {% data variables.product.product_name %} 用户界面中或使用 GraphQL API 删除私有包的版本。 使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”和“[使用 GraphQL 进行调用](/graphql/guides/forming-calls-with-graphql)”。 您可以配置 web 挂钩来订阅与包相关的事件，例如包的发布或更新等事件。 更多信息请参阅“[`package` web 挂钩事件](/webhooks/event-payloads/#package)”。 diff --git a/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md b/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md index 5ac6b85867..1a7ac7b052 100644 --- a/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md +++ b/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md @@ -54,7 +54,7 @@ versions: 以下是使用个人访问令牌，通过 cURL 命令删除包版本的示例，包版本 ID 为 `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`。 {% if currentVersion == "free-pro-team@latest" %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ @@ -64,7 +64,7 @@ https://api.github.com/graphql {% else %} -``` +```shell curl -X POST \ -H "Accept: application/vnd.github.package-deletes-preview+json" \ -H "Authorization: bearer TOKEN" \ diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md index 6da1c33ad0..f5029067e6 100644 --- a/translations/zh-CN/content/rest/overview/libraries.md +++ b/translations/zh-CN/content/rest/overview/libraries.md @@ -79,6 +79,10 @@ Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https: Library name | Repository |---|---| **GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github) **Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee) +### Rust + +Library name | Repository |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) + ### Scala Library name | Repository |---|---| **Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat) **Github4s**|[47deg/github4s](https://github.com/47deg/github4s) diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md index 31af636998..d3b9c86692 100644 --- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md @@ -107,7 +107,7 @@ _搜索_ - [`GET /search/topics`](/rest/reference/search#search-topics) - [`GET /search/users`](/rest/reference/search#search-users) -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### 有关“操作”的权限 - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read) @@ -202,6 +202,9 @@ _分支_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _协作者_ - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write) @@ -347,6 +350,9 @@ _分支_ - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write) - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write) - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write) +{% endif %} _提交注释_ - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write) @@ -836,6 +842,9 @@ _团队_ - [`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_id`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read) +- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write) +- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (:read) +- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (:write) {% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml index 070d56e434..c80d00de25 100644 --- a/translations/zh-CN/data/glossaries/external.yml +++ b/translations/zh-CN/data/glossaries/external.yml @@ -35,7 +35,7 @@ - term: 个人简历 description: >- - 个人资料中用户生成的描述：https://help.github.com/articles/adding-a-bio-to-your-profile/ + 个人资料中用户生成的描述：[为个人资料添加简介](/articles/adding-a-bio-to-your-profile) - term: 结算周期 description: 特定结算方案的时间间隔。 @@ -156,7 +156,7 @@ - term: 贡献 description: >- - GitHub 上的特定活动，将会：- 添加方块到用户的贡献图："[计为贡献的活动](https://help.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - 添加活动到用户个人资料上的时间表："[贡献活动](https://help.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" + GitHub 上的特定活动，将会：- 添加方块到用户的贡献图："[计为贡献的活动](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - 添加活动到用户个人资料上的时间表："[贡献活动](/articles/viewing-contributions-on-your-profile/#contribution-activity)" - term: 贡献者 description: >- @@ -229,7 +229,7 @@ 用于试验新功能或修复未正式使用的议题的分支。也称为主题分支。 - term: 围栏代码块 - description: '您可以在代码块前后使用三个反引号 \`\`\`，通过 GitHub Flavored Markdown 创建缩进代码块。请参阅此 [example](https://help.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)。' + description: '您可以在代码块前后使用三个反引号 \`\`\`，通过 GitHub Flavored Markdown 创建缩进代码块。请参阅此 [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)。' - term: 获取 description: >- diff --git a/translations/zh-CN/data/learning-tracks/README.md b/translations/zh-CN/data/learning-tracks/README.md new file mode 100644 index 0000000000..ec0f70309e --- /dev/null +++ b/translations/zh-CN/data/learning-tracks/README.md @@ -0,0 +1,3 @@ +# Learning Tracks (aka Learning Paths) + +Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. \ No newline at end of file diff --git a/translations/zh-CN/data/learning-tracks/actions.yml b/translations/zh-CN/data/learning-tracks/actions.yml index 211a50ea95..6fd065913c 100644 --- a/translations/zh-CN/data/learning-tracks/actions.yml +++ b/translations/zh-CN/data/learning-tracks/actions.yml @@ -31,6 +31,13 @@ continuous_deployment: - /actions/guides/publishing-java-packages-with-maven - /actions/guides/publishing-java-packages-with-gradle - /actions/guides/publishing-docker-images +deploy_to_the_cloud: + title: 'Deploy to the cloud' + description: 'Learn how to use {% data variables.product.prodname_actions %} to build an application and deploy it to various cloud-based platforms.' + guides: + - /actions/guides/deploying-to-amazon-elastic-container-service + - /actions/guides/deploying-to-azure-app-service + - /actions/guides/deploying-to-google-kubernetes-engine hosting_your_own_runners: title: 'Host your own runners' description: '您可以创建自托管的运行器，在一个可高度自定义的环境中运行工作流程。' diff --git a/translations/zh-CN/data/release-notes/2-20/18.yml b/translations/zh-CN/data/release-notes/2-20/18.yml index 3aab7ba337..9e121bf06a 100644 --- a/translations/zh-CN/data/release-notes/2-20/18.yml +++ b/translations/zh-CN/data/release-notes/2-20/18.yml @@ -3,10 +3,10 @@ date: '2020-10-09' sections: security_fixes: - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/9.yml b/translations/zh-CN/data/release-notes/2-21/9.yml index 46656c9e6b..d81e068978 100644 --- a/translations/zh-CN/data/release-notes/2-21/9.yml +++ b/translations/zh-CN/data/release-notes/2-21/9.yml @@ -3,10 +3,10 @@ date: '2020-10-09' sections: security_fixes: - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-22/1.yml b/translations/zh-CN/data/release-notes/2-22/1.yml index fbd3988c3d..59bdec1b8d 100644 --- a/translations/zh-CN/data/release-notes/2-22/1.yml +++ b/translations/zh-CN/data/release-notes/2-22/1.yml @@ -5,14 +5,14 @@ sections: - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - | The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - | Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | diff --git a/translations/zh-CN/data/release-notes/3-0/0-rc1.yml b/translations/zh-CN/data/release-notes/3-0/0-rc1.yml new file mode 100644 index 0000000000..1d9293905b --- /dev/null +++ b/translations/zh-CN/data/release-notes/3-0/0-rc1.yml @@ -0,0 +1,145 @@ +--- +date: '2021-01-12' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +sections: + features: + - + heading: GitHub Actions + notes: + - | + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. + + This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + + - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. + - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. + - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). + - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). + - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Users can now use private images in container jobs and services. + - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). + - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - You can now create reusable actions using shell scripts with compose run steps. + - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. + - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. + + {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Packages + notes: + - | + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. + + When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) + + {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. + - + heading: GitHub Mobile beta + notes: + - | + [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. 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 variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. + - + heading: Advanced Security Secret Scanning beta + notes: + - | + [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. + + Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. + - + heading: Advanced Security Code Scanning + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" + changes: + - + heading: Administration Changes + notes: + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. + - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. + - + heading: Security Changes + notes: + - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - A datacenter must be explicitly defined on all nodes before enabling an active replica. + - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. + - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. + - + heading: Developer Changes + notes: + - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases + - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. + - + heading: API Changes + notes: + - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' + - + heading: Default branch renaming + notes: + - | + Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. + + Existing repositories are unaffected by these settings, and their default branch name will not be changed. + + {% note %} + + The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. + + {% endnote %} + + This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). + bugs: + - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. + - A PATCH request to the webhook configuration API no longer erases the webhook secret. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Deprecation of support for Semiotic + notes: + - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - + heading: Deprecation of workflow commands + notes: + - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Release Candidate 1 does not support Cluster mode. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. + - 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. + - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance + - The "Mandatory message viewed" audit log event is not being saved + - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' + - Backup-utils can trigger unnecessary emails to administrators + - Incorrect Packages settings are being displayed in the Organization member view page + - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. + - '`ghe-config-apply` occassionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. + - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. + - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. + - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/zh-CN/data/release-notes/3-0/0-rc2.yml b/translations/zh-CN/data/release-notes/3-0/0-rc2.yml new file mode 100644 index 0000000000..0e6ed5fd3f --- /dev/null +++ b/translations/zh-CN/data/release-notes/3-0/0-rc2.yml @@ -0,0 +1,25 @@ +--- +date: '2021-01-29' +release_candidate: true +intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +sections: + bugs: + - + heading: Fixes for known issues from Release Candidate 1 + notes: + - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. + - The "Mandatory message viewed" audit log event was not being saved. + - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' + - Removing yourself as an enterprise owner returned a 404. + - + heading: Fixes for other issues + notes: + - Issues with migrations and upgrades to 3.0.0 have been fixed. + - Backup Utilities versioning now works for release candidate versions. + - Generating a support bundle resulted in an error in the orchestrator logs. + - A large restore could result in Redis running out of memory. + - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. + - GitHub Actions can only be enabled if the required storage is also configured. + - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + known_issues: + - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/translations/zh-CN/data/reusables/actions/actions-not-verified.md b/translations/zh-CN/data/reusables/actions/actions-not-verified.md index b2616e93e0..3511941c3f 100644 --- a/translations/zh-CN/data/reusables/actions/actions-not-verified.md +++ b/translations/zh-CN/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -任何人都可以在 {% data variables.product.prodname_marketplace %} 中发布操作。 {% data variables.product.prodname_dotcom %} 验证一些合作伙伴组织，这些组织显示为已验证的创建者。 +任何人都可以在 {% data variables.product.prodname_marketplace %} 中发布操作。 {% data variables.product.prodname_dotcom %} 验证一些合作伙伴组织，这些组织显示为已验证的创建者。 diff --git a/translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md b/translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md index 7f3bcdf222..c5879f373d 100644 --- a/translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md +++ b/translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md @@ -1,3 +1,3 @@ -If you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions. 更多信息请参阅“[允许特定操作运行](#allowing-specific-actions-to-run)”。 +如果您选择 **Allow select actions（允许选择操作）**，则允许本地操作，并且还有允许其他特定操作的其他选项。 更多信息请参阅“[允许特定操作运行](#allowing-specific-actions-to-run)”。 如果只允许本地操作，则策略会阻止对 {% data variables.product.prodname_dotcom %} 创建的操作的所有访问。 例如，[`actions/checkout`](https://github.com/actions/checkout) 不可访问。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md b/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md index 60785cd321..3a355bfd32 100644 --- a/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md @@ -1,4 +1,4 @@ -When you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions: +选择 **Allow select actions（允许选择操作）**时，允许本地操作，并且还有允许其他特定操作的其他选项。 - **允许 {% data variables.product.prodname_dotcom %} 创建的操作：** 您可以允许 {% data variables.product.prodname_dotcom %} 创建的所有操作用于工作流程。 {% data variables.product.prodname_dotcom %} 创建的操作位于 `actions` 和 `github` 组织中。 更多信息请参阅 [`actions`](https://github.com/actions) 和 [`github`](https://github.com/github) 组织。 - **Allow Marketplace actions by verified creators（允许已验证的创作者的 Marketplace 操作）：**您可以允许已验证的创作者创建的所有 {% data variables.product.prodname_marketplace %} 操作用于工作流程。 如果 GitHub 验证该操作的创建者为合作伙伴组织，{% octicon "verified" aria-label="The verified badge" %} 徽章将显示在 {% data variables.product.prodname_marketplace %} 中的操作旁边。 diff --git a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md index af689fad90..26ea19355f 100644 --- a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,9 +1,9 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**弃用通知：** {% data variables.product.prodname_dotcom %} 将停止使用查询参数向 API 验证。 向 API 验证应使用 [HTTP 基本身份验证](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)完成。{% if currentVersion == "free-pro-team@latest" %} 使用查询参数向 API 验证在 2021 年 5 月 5 日将不再有效。 {% endif %}有关详细信息，包括预定的限电，请参阅[博客文章](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)。 +**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). -{% if enterpriseServersions contains currentversion or currentversion == "github-ae@latest" %} 使用查询参数向 API 验证仍然可用，但出于安全考虑不再支持。 相反，我们建议集成商在标头中移动其访问令牌 `client_id` 或 `client_secret`。 {% data variables.product.prodname_dotcom %} 将宣布删除通过查询参数进行身份验证，并且会提前通知。 {% endif %} +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} {% endwarning %} {% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/not-available.md b/translations/zh-CN/data/reusables/code-scanning/not-available.md index 621faf031e..b2bd05e8bd 100644 --- a/translations/zh-CN/data/reusables/code-scanning/not-available.md +++ b/translations/zh-CN/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning.` check that {% data variables.product.prodname_GH_advanced_security %} is enabled. 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 +**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md new file mode 100644 index 0000000000..c5142332f6 --- /dev/null +++ b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + +{% endnote %} diff --git a/translations/zh-CN/data/reusables/community/interaction-limits-duration.md b/translations/zh-CN/data/reusables/community/interaction-limits-duration.md index fb858accd8..76379bdb92 100644 --- a/translations/zh-CN/data/reusables/community/interaction-limits-duration.md +++ b/translations/zh-CN/data/reusables/community/interaction-limits-duration.md @@ -1 +1 @@ -When you enable an interaction limit, you can choose a duration for the limit: 24 hours, 3 days, 1 week, 1 month, or 6 months. \ No newline at end of file +启用交互限制时，可以选择限制的持续时间：24 小时、3 天、1 周、1 个月或 6 个月。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/community/interaction-limits-restrictions.md b/translations/zh-CN/data/reusables/community/interaction-limits-restrictions.md index 1be2648d16..cb08659629 100644 --- a/translations/zh-CN/data/reusables/community/interaction-limits-restrictions.md +++ b/translations/zh-CN/data/reusables/community/interaction-limits-restrictions.md @@ -1 +1 @@ -Enabling an interaction limit for a repository restricts certain users from commenting, opening issues, creating pull requests, reacting with emojis, editing existing comments, and editing titles of issues and pull requests. \ No newline at end of file +启用仓库的交互限制会限制某些用户评论、打开议题、创建拉取请求、使用表情符号做出反应、编辑现有注释以及编辑议题和拉取请求的标题。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/community/set-interaction-limit.md b/translations/zh-CN/data/reusables/community/set-interaction-limit.md index 468a068f70..3d8de5032d 100644 --- a/translations/zh-CN/data/reusables/community/set-interaction-limit.md +++ b/translations/zh-CN/data/reusables/community/set-interaction-limit.md @@ -1 +1 @@ -5. Under "Temporary interaction limits", to the right of the type of interaction limit you want to set, use the **Enable** drop-down menu, then click the duration you want for your interaction limit. \ No newline at end of file +5. 在要设置的交互限制类型右侧的“Temporary interaction limits（临时交互限制）”下，使用 **Enable（启用）**下拉菜单，然后单击交互限制的持续时间。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/community/types-of-interaction-limits.md b/translations/zh-CN/data/reusables/community/types-of-interaction-limits.md index 6ff0d36548..778a450840 100644 --- a/translations/zh-CN/data/reusables/community/types-of-interaction-limits.md +++ b/translations/zh-CN/data/reusables/community/types-of-interaction-limits.md @@ -1,4 +1,4 @@ -There are three types of interaction limits. +交互限制有三种类型。 - **Limit to existing users（限于现有用户）**：限制帐户存在时间不到 24 小时、之前没有贡献也不是协作者的用户的活动。 - - **Limit to prior contributors**: Limits activity for users who have not previously contributed to the default branch of the repository and are not collaborators. - - **Limit to repository collaborators**: Limits activity for users who do not have write access to the repository. \ No newline at end of file + - **Limit to prior contributors（限于之前的贡献者）**：限制之前没有参与仓库的默认分支也不是协作者的用户的活动。 + - **Limit to repository collaborators（限于仓库协作者）**：限制对仓库没有写入权限的用户的活动。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md index 18554c0ce1..4cf3d5173e 100644 --- a/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)." +在运行安全性或版本更新时，有些生态系统必须能够解决来自其来源的所有依赖项，以验证版本更新是否成功。 如果清单或锁定文件包含任何私有依赖项，{% data variables.product.prodname_dependabot %} 必须能够访问这些依赖项所在的位置。 组织所有者可以授予 {% data variables.product.prodname_dependabot %} 访问包含同一个组织内项目依赖项的私有仓库. 更多信息请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)”。 -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. +目前，{% data variables.product.prodname_dependabot %} 版本更新不支持包含私人注册表中依赖项的清单或锁定文件，或者私有 {% data variables.product.prodname_dotcom %} 仓库中属于不同于依赖项目的组织。 diff --git a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md index 3ad535c2ca..b2a7c4d273 100644 --- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md +++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md @@ -1,34 +1,35 @@ -下表显示对于每个包管理器，{% data variables.product.prodname_dependabot %} 是否支持：私有 {% data variables.product.prodname_dotcom %} 仓库中的依赖项，以及供应的依赖项。 +The following table shows, for each package manager: +- The YAML value to use in the *dependabot.yml* file +- The supported versions of the package manager +- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +- Whether vendored dependencies are supported -| 包管理器 | 私有 {% data variables.product.prodname_dotcom %} 仓库 | 供应 | -| -------------------------- |:--------------------------------------------------:|:-----:| -| Bundler: `bundler` | | **✓** | -| Cargo: `cargo` | **✓** | | -| Composer: `composer` | **✓** | | -| Docker: `docker` | **✓** | | -| Elixir：`hex` | | | -| Elm: `elm` | **✓** | | -| Git 子模块：`gitsubmodule` | **✓** | | -| GitHub 操作：`github-actions` | **✓** | | -| Go 模块：`gomod` | **✓** | **✓** | -| Gradle: `gradle` | **✓** | | -| Maven: `maven` | **✓** | | -| Mix: `mix` | **✓** | | -| npm: `npm` | **✓** | | -| NuGet: `nuget` | **✓** | | -| pip: `pip` | | | -| Terraform: `terraform` | **✓** | | +| 包管理器 | YAML value | Supported versions | Private repositories | 供应 | +| -------------- | ---------------- | ------------------------- |:--------------------:|:-----:| +| Bundler | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1,v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | +| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | +| Go modules | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | see (A) below | **✓** | | +| Maven | `maven` | see (B) below | **✓** | | +| npm | `npm` | v6 | **✓** | | +| NuGet | `nuget` | <= 4.8.
    see (C) below | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -{% note %} +(A) {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). -**注**：{% data variables.product.prodname_dependabot %} 也支持以下软件包管理器： +(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. --`yarn`（仅限 v1）（指定 `npm`） +(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. --`.gradle.kts` 文件，用于 Kotlin 项目（指定 `gradle`） - --`pipenv`、`pip-compile` 和 `poetry`（指定 `pip`） - -例如，如果您使用 `poetry` 来管理 Python 依赖项，并且希望 {% data variables.product.prodname_dependabot %} 监控新版本的依赖项清单文件，请在 *dependabot.yml* 文件中使用 `package-ecosystem: "pip"`。 - -{% endnote %} +For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. 例如，如果您使用 `poetry` 来管理 Python 依赖项，并且希望 {% data variables.product.prodname_dependabot %} 监控新版本的依赖项清单文件，请在 *dependabot.yml* 文件中使用 `package-ecosystem: "pip"`。 diff --git a/translations/zh-CN/data/reusables/desktop/delete-tag.md b/translations/zh-CN/data/reusables/desktop/delete-tag.md new file mode 100644 index 0000000000..40d455b880 --- /dev/null +++ b/translations/zh-CN/data/reusables/desktop/delete-tag.md @@ -0,0 +1,4 @@ +1. Right-click the commit. + + - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) + - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/education/about-github-education-link.md b/translations/zh-CN/data/reusables/education/about-github-education-link.md index faea1133c4..89779dbe78 100644 --- a/translations/zh-CN/data/reusables/education/about-github-education-link.md +++ b/translations/zh-CN/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -在申请个人折扣之前，请检查您的学习社区是否已作为 {% data variables.product.prodname_education %} 学校与我们合作。 更多信息请参阅“[关于 {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)”。 +在申请个人折扣之前，请检查您的学习社区是否已作为 {% data variables.product.prodname_education %} 学校与我们合作。 更多信息请参阅“[关于 {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)”。 diff --git a/translations/zh-CN/data/reusables/education/apply-for-team.md b/translations/zh-CN/data/reusables/education/apply-for-team.md index 3e298c49a7..4c3c8e68b2 100644 --- a/translations/zh-CN/data/reusables/education/apply-for-team.md +++ b/translations/zh-CN/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- 申请免费 [{% data variables.product.prodname_team %}](/articles/github-s-products)，允许无限制的用户和私有仓库。 更多信息请参阅“[申请教育者或研究人员折扣](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)”。 +- 申请免费 [{% data variables.product.prodname_team %}](/articles/github-s-products)，允许无限制的用户和私有仓库。 更多信息请参阅“[申请教育者或研究人员折扣](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)”。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md index 0e4fae8c9d..1c21b4eb95 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md @@ -1 +1 @@ -{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。 +{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServersions contains currentversion or currentversion == "free promo-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/pages-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/pages-tab.md index 5d9fb29f64..1d8c3f713a 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/pages-tab.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/pages-tab.md @@ -1 +1 @@ -1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Pages**. ![Pages tab in the enterprise sidebar](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file +1. 在“{% octicon "law" aria-label="The law icon" %} Policies（政策）”下，单击 **Pages（页面）**。 ![企业边栏中的 Pages（页面）选项卡](/assets/images/enterprise/business-accounts/pages-tab.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-managed/about-billing.md b/translations/zh-CN/data/reusables/enterprise-managed/about-billing.md index 9e7ed843b2..3fc998bc74 100644 --- a/translations/zh-CN/data/reusables/enterprise-managed/about-billing.md +++ b/translations/zh-CN/data/reusables/enterprise-managed/about-billing.md @@ -1 +1 @@ -You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file +您将每月收到一张 {% data variables.product.prodname_ghe_managed %} 账单，费用按每个许可用户每天计算。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md index 539eb03977..123e6c1792 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,4 +1,4 @@ -1. SSH 连接到 {% data variables.product.product_location %}。 +1. SSH 连接到 {% data variables.product.product_location %}。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)。” ```shell $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/zh-CN/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/zh-CN/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 960f85c97d..ba2a195e16 100644 --- a/translations/zh-CN/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/zh-CN/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. 要将存档的迁移数据导入到 {% data variables.product.prodname_ghe_server %} 实例，请参阅“[将迁移数据导入到 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)”。 +1. 要将存档的迁移数据导入到 {% data variables.product.prodname_ghe_server %} 实例，请参阅“[准备将数据迁移到企业](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)”。 diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-ssh-access.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-ssh-access.md index 4e1057532c..1ac24b1177 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-ssh-access.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-ssh-access.md @@ -1 +1 @@ -SSH access allows you to run the {% data variables.product.product_name %} command line utilities to troubleshoot, run backups, and configure replication. \ No newline at end of file +SSH 访问可让您运行 {% data variables.product.product_name %} 命令行实用程序，以进行故障排除、运行备份及配置复制。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-management-console.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-management-console.md index 8c622226c6..2e408d584b 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-management-console.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-management-console.md @@ -1 +1 @@ -You can use the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL. \ No newline at end of file +您可以使用 {% data variables.enterprise.management_console %} 管理域、身份验证和 SSL 等虚拟设备设置。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md index bab0827c40..cf1b6b6221 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md @@ -1 +1 @@ -You can use the site admin dashboard to manage users, organizations, and repositories in your enterprise directly in {% data variables.product.product_name %}. \ No newline at end of file +您可以直接在 {% data variables.product.product_name %} 中使用站点管理面板来管理您企业中的用户、组织和仓库。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/gated-features/private-pages.md b/translations/zh-CN/data/reusables/gated-features/private-pages.md new file mode 100644 index 0000000000..3fb7f0a3a7 --- /dev/null +++ b/translations/zh-CN/data/reusables/gated-features/private-pages.md @@ -0,0 +1 @@ +Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md b/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md index 71a6466439..097473e2bb 100644 --- a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md @@ -5,7 +5,7 @@ 例如，要使用 9.0.4 版本的 JDK，用于 x64 平台，您可以使用 `setup-java` 操作，将 `java-version` 和 `architecture` 参数配置为 `'9.0.4'` 和 `x64`。 {% raw %} -```yaml +```yaml{:copy} steps: - uses: actions/checkout@v2 - name: Set up JDK 9.0.4 for x64 diff --git a/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md b/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md index e6db4f8803..782f89496d 100644 --- a/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. +**注：**MacOS 11.0 虚拟环境目前仅作为私人预览提供。 任何已经在使用此运行器的用户或组织都可以继续使用它。 但我们目前不接受任何其他用户或组织。 `macos-latest` YAML 工作流程标签仍使用 MacOS 10.15 虚拟环境。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/github-ae/about-billing.md b/translations/zh-CN/data/reusables/github-ae/about-billing.md index 9e7ed843b2..3fc998bc74 100644 --- a/translations/zh-CN/data/reusables/github-ae/about-billing.md +++ b/translations/zh-CN/data/reusables/github-ae/about-billing.md @@ -1 +1 @@ -You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day. \ No newline at end of file +您将每月收到一张 {% data variables.product.prodname_ghe_managed %} 账单，费用按每个许可用户每天计算。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/github-ae/github-ae-enables-you.md b/translations/zh-CN/data/reusables/github-ae/github-ae-enables-you.md index dd699d9ad6..44ee1d4d6b 100644 --- a/translations/zh-CN/data/reusables/github-ae/github-ae-enables-you.md +++ b/translations/zh-CN/data/reusables/github-ae/github-ae-enables-you.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_managed %} enables you to move your software development to the cloud while meeting the most stringent security and compliance requirements. +{% data variables.product.prodname_ghe_managed %} 可让您将软件开发移动到云端，同时满足最严格的安全和合规要求。 diff --git a/translations/zh-CN/data/reusables/marketplace/launch-with-free.md b/translations/zh-CN/data/reusables/marketplace/launch-with-free.md index 16053ece27..66c3a85d59 100644 --- a/translations/zh-CN/data/reusables/marketplace/launch-with-free.md +++ b/translations/zh-CN/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -您可以请求发布，无论是否经过验证。 无需验证即可请求发布，可以快速启动应用程序的免费版本。 如果您随后请求发布并验证，则当您完成验证和财务入职时，您的列表将更新，以包括已验证的创建者徽章和任何付费定价计划。 +您可以请求发布，无论是否经过验证。 无需验证即可请求发布，可以快速启动应用程序的免费版本。 如果您随后请求发布并验证，则当您完成验证和财务入职时，您的列表将更新，以包括已验证的 Marketplace 徽章和任何付费定价计划。 diff --git a/translations/zh-CN/data/reusables/notifications-v2/custom-notifications-beta.md b/translations/zh-CN/data/reusables/notifications-v2/custom-notifications-beta.md index dbcee80cfe..328cb7b4b4 100644 --- a/translations/zh-CN/data/reusables/notifications-v2/custom-notifications-beta.md +++ b/translations/zh-CN/data/reusables/notifications-v2/custom-notifications-beta.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Custom notifications are currently in beta and subject to change. +**注意：**自定义通知目前处于测试阶段，可能会更改。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md index 61fc77479d..d3e50c0e62 100644 --- a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -11,7 +11,7 @@ {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} -By default, if your site administrator has configured email for notifications on your instance, you will receive +默认情况下，如果站点管理员配置了使用电子邮件接收实例通知，您将 {% data variables.product.prodname_dependabot_alerts %} 的通知： - 通过电子邮件收到通知， 每次发现{% if currentVersion ver_gt "enterprise-server@2.23" %}关键或严重性{% endif %}高的漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） - 在用户界面中接收通知，如有任何漏洞依赖项，将在仓库的文件和代码视图中显示警告（**UI 警报**选项） diff --git a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md index 75bd1537f3..6ccacc726b 100644 --- a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. 更多信息请参阅“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。 +**注：**要使用 {% data variables.product.prodname_github_container_registry %}，您必须为您的帐户启用该功能。 更多信息请参阅“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。 {% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/about-private-publishing.md b/translations/zh-CN/data/reusables/pages/about-private-publishing.md new file mode 100644 index 0000000000..f1f13531ce --- /dev/null +++ b/translations/zh-CN/data/reusables/pages/about-private-publishing.md @@ -0,0 +1 @@ +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. diff --git a/translations/zh-CN/data/reusables/pages/choose-visibility.md b/translations/zh-CN/data/reusables/pages/choose-visibility.md new file mode 100644 index 0000000000..fe6015b739 --- /dev/null +++ b/translations/zh-CN/data/reusables/pages/choose-visibility.md @@ -0,0 +1 @@ +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. 在 "{% data variables.product.prodname_pages %}" 下，选择 **{% data variables.product.prodname_pages %} visibility（可见性）**下拉菜单，然后单击可见性。 For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md new file mode 100644 index 0000000000..fc98787aaa --- /dev/null +++ b/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md b/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md index 78e3599281..bf1041637e 100644 --- a/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/zh-CN/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ - {% warning %} +{% warning %} - **警告**：{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}如果您的站点管理员启用了公共页面，{% endif %}{% data variables.product.prodname_pages %} 站点将在互联网上公开，即使其仓库是私有的{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}或内部的{% endif %}。 如果站点的仓库中有敏感数据，您可能想要在发布前删除它。 更多信息请参阅{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}“[为企业配置 {% data variables.product.prodname_pages %}](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)”和{% endif %}“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 +**警告**：{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}如果您的站点管理员启用了公共页面，{% endif %}{% data variables.product.prodname_pages %} 站点{% if currentVersion == "free-pro-team@latest" %} 默认{% endif %}在互联网上公开，即使站点的仓库是私有或内部的。{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} 否则，如果{% else %} 如果{% endif %} 您的站点仓库中有敏感数据，则您可能要在发布前删除该数据。 更多信息请参阅{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}“[为企业配置 {% data variables.product.prodname_pages %}](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)”和{% endif %}“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}”和“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。{% else %}”。{% endif %} - {% endwarning %} +{% endwarning %} diff --git a/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md b/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md new file mode 100644 index 0000000000..997f93586a --- /dev/null +++ b/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md @@ -0,0 +1 @@ +**注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 20 分钟才会发布。 如果一小时后仍然在浏览器中看不到您的更改，请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/visit-site.md b/translations/zh-CN/data/reusables/pages/visit-site.md index 54c45ed48e..c6804fd146 100644 --- a/translations/zh-CN/data/reusables/pages/visit-site.md +++ b/translations/zh-CN/data/reusables/pages/visit-site.md @@ -2,6 +2,6 @@ {% note %} - **注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 20 分钟才会发布。 如果一小时后仍然在浏览器中看不到您的更改，请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。 + {% data reusables.pages.twenty-minutes-to-publish %} {% endnote %} diff --git a/translations/zh-CN/data/reusables/project-management/project-board-visibility.md b/translations/zh-CN/data/reusables/project-management/project-board-visibility.md index aa02576e2d..adfe0c3840 100644 --- a/translations/zh-CN/data/reusables/project-management/project-board-visibility.md +++ b/translations/zh-CN/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -默认情况下，您的项目板为私有，只有对项目板具有读取、写入或管理权限的人才能看到。 {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL. +默认情况下，您的项目板为私有，只有对项目板具有读取、写入或管理权限的人才能看到。 {% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}项目板对具有项目板 URL 的{% if currentVersion == "github-ae@latest" %}任何企业成员{% else %}任何人{% endif %}可见。 diff --git a/translations/zh-CN/data/reusables/pull_requests/re-request-review.md b/translations/zh-CN/data/reusables/pull_requests/re-request-review.md index b04a7a46ce..226d666710 100644 --- a/translations/zh-CN/data/reusables/pull_requests/re-request-review.md +++ b/translations/zh-CN/data/reusables/pull_requests/re-request-review.md @@ -1 +1 @@ -You can re-request a review, for example, after you've made substantial changes to your pull request. To request a fresh review from a reviewer, in the sidebar of the **Conversation** tab, click the {% octicon "sync" aria-label="The sync icon" %} icon. +您可以重新请求审查，例如在对您的拉取请求做出实质性更改之后。 要向审查者请求新的审查，请在 **Conversation（对话）**侧栏中单击 {% octicon "sync" aria-label="The sync icon" %} 图标。 diff --git a/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md index ec450ed471..93c18a9fe8 100644 --- a/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ 要变基并合并拉取请求，必须在仓库中拥有[写入权限](/articles/repository-permission-levels-for-an-organization/)，并且仓库必须[允许变基合并](/articles/configuring-commit-rebasing-for-pull-requests/)。 -{% data variables.product.product_name %} 上的变基和合并行为与 `git rebase` 略有偏差。 {% data variables.product.prodname_dotcom %} 上的变基和合并始终会更新提交者信息并创建新的提交 SHA，而 {% data variables.product.prodname_dotcom %} 外部的 `git rebase` 在提交原型上发生变基时不改变提交者信息。 有关 `git rebase` 的更多信息，请参阅 _Pro Git_ 一书中的[“Git 变基”一章](https://git-scm.com/docs/git-rebase)。 +{% data variables.product.product_name %} 上的变基和合并行为与 `git rebase` 略有偏差。 {% data variables.product.prodname_dotcom %} 上的变基和合并始终会更新提交者信息并创建新的提交 SHA，而 {% data variables.product.prodname_dotcom %} 外部的 `git rebase` 在提交原型上发生变基时不改变提交者信息。 For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). 有关 `git rebase` 的可视表示，请参阅 _Pro Git_ 一书中的[“Git 分支 - 变基”一章](https://git-scm.com/book/en/Git-Branching-Rebasing)。 diff --git a/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md index 3526e39a78..55036b3123 100644 --- a/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ b/translations/zh-CN/data/reusables/pull_requests/required-reviews-for-prs-summary.md @@ -1 +1 @@ -Repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request into a protected branch. You can require approving reviews from people with write permissions in the repository or from a designated code owner. +仓库管理员可以要求所有拉取请求在有人将拉取请求合并到受保护分支之前获得特定数量的批准审查。 您可以要求仓库中具有写入权限的人或指定代码所有者批准审查。 diff --git a/translations/zh-CN/data/reusables/repositories/administrators-can-disable-issues.md b/translations/zh-CN/data/reusables/repositories/administrators-can-disable-issues.md index 4352c32d54..aa1700fc37 100644 --- a/translations/zh-CN/data/reusables/repositories/administrators-can-disable-issues.md +++ b/translations/zh-CN/data/reusables/repositories/administrators-can-disable-issues.md @@ -1 +1 @@ -Repository administrators can disable issues for a repository. 更多信息请参阅“[禁用议题](/github/managing-your-work-on-github/disabling-issues)”。 +仓库管理员可以禁用仓库的议题。 更多信息请参阅“[禁用议题](/github/managing-your-work-on-github/disabling-issues)”。 diff --git a/translations/zh-CN/data/reusables/repositories/branch-rules-example.md b/translations/zh-CN/data/reusables/repositories/branch-rules-example.md index ea81704455..cde81be34a 100644 --- a/translations/zh-CN/data/reusables/repositories/branch-rules-example.md +++ b/translations/zh-CN/data/reusables/repositories/branch-rules-example.md @@ -1 +1 @@ -You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with `fnmatch` syntax. For example, to protect any branches containing the word `release`, you can create a branch rule for `*release*`. +您可以在仓库中为特定分支、所有分支或者与使用 `fnmatch` 语法指定的命名模式匹配的任何分支创建分支保护规则。 例如，要保护包含文字 `release` 的任何分支，您可以为 `*release*` 创建分支规则。 diff --git a/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md index cfe413d8a0..bc6ed67dd0 100644 --- a/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md +++ b/translations/zh-CN/data/reusables/repositories/review-policy-overlapping-commits.md @@ -1 +1 @@ -Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first. +即使在所有必需的审查者已经批准拉取请求之后，如果还有其他打开的拉取请求有头部分支指向同一待处理或拒绝审查的评论，协作者也不能合并拉请求。 具有写入权限的人必须先批准或取消对其他拉取请求的阻止审查。 diff --git a/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 1562d46e0c..fc4b2184eb 100644 --- a/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}如果你的仓库中有需要线性提交历史记录的受保护分支规则，必须允许压缩合并和/或变基合并。 For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}如果你的仓库中有需要线性提交历史记录的受保护分支规则，必须允许压缩合并和/或变基合并。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。{% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/workflow-notifications.md b/translations/zh-CN/data/reusables/repositories/workflow-notifications.md index 0645c355d9..3eb77f4f70 100644 --- a/translations/zh-CN/data/reusables/repositories/workflow-notifications.md +++ b/translations/zh-CN/data/reusables/repositories/workflow-notifications.md @@ -1,5 +1,5 @@ 如果为 {% data variables.product.prodname_actions %} 启用电子邮件或 web 通知，则在触发的任何工作流程运行完成时，您将收到通知。 通知将包括工作流程运行的状态（包括成功、失败、中立和取消的运行）。 您也可以选择仅在工作流程运行失败时接收通知。 -Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} +计划工作流程的通知将发送给最初创建该工作流程的用户。 如有不同的用户更新工作流程文件中的计划任务语法，后续通知将改为发送给该用户。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 如果预定的工作流程禁用后重新启用， 通知将发送给重新启用工作流程的用户，而不是最后修改计划任务语法的用户。{% endif %} 您也可以在仓库的 Actions（操作）选项卡上查看工作流程的状态。 更多信息请参阅“[管理工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)”。 diff --git a/translations/zh-CN/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/zh-CN/data/reusables/saml/about-user-provisioning-enterprise-account.md index 8ef6699edb..447496cfee 100644 --- a/translations/zh-CN/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ b/translations/zh-CN/data/reusables/saml/about-user-provisioning-enterprise-account.md @@ -1 +1 @@ -如果您使用 Okta 作为您的 IdP，您可以使用 SCIM 管理企业帐户中的组织成员资格。 SCIM 会自动邀请人们访问企业帐户中的组织或从中删除人员，具体根据他们是否是对应于 IdP 中每个组织的组成员。 +如果您使用 Okta 作为 IdP 并参与企业帐户的私有测试版，您可以使用 SCIM 管理企业帐户组织中的成员身份。 SCIM 会自动邀请人们访问企业帐户中的组织或从中删除人员，具体根据他们是否是对应于 IdP 中每个组织的组成员。 diff --git a/translations/zh-CN/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md b/translations/zh-CN/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md index e60bce6013..1d63c50e35 100644 --- a/translations/zh-CN/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md +++ b/translations/zh-CN/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md @@ -1 +1 @@ -You'll configure identity and access management for {% data variables.product.product_name %} by entering the details for your SAML IdP during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)." +您将在初始化过程中输入SAML IdP 的详细信息，以配置 {% data variables.product.product_name %} 的身份和访问管理。 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)。” diff --git a/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md b/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md index 08c138d1ba..42f71d5627 100644 --- a/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md +++ b/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md @@ -1 +1 @@ -{% data variables.product.product_name %} uses SAML SSO for user authentication. You can centrally manage access to {% data variables.product.prodname_ghe_managed %} from an IdP that supports the SAML 2.0 standard. +{% data variables.product.product_name %} 使用 SAML SSO 进行用户身份验证。 您可以从支持 SAML 2.0 标准的 IdP 集中管理对 {% data variables.product.prodname_ghe_managed %} 的访问。 diff --git a/translations/zh-CN/data/reusables/saml/assert-the-administrator-attribute.md b/translations/zh-CN/data/reusables/saml/assert-the-administrator-attribute.md index ff9e3bc75d..e962d26afa 100644 --- a/translations/zh-CN/data/reusables/saml/assert-the-administrator-attribute.md +++ b/translations/zh-CN/data/reusables/saml/assert-the-administrator-attribute.md @@ -1 +1 @@ -To make a person an enterprise owner, you must delegate ownership permission in your IdP. Include the `administrator` attribute in the SAML assertion for the user account on the IdP, with the value of `true`. For more information about enterprise owners, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +要使某人成为企业所有者，您必须在 IdP 中委派所有权权限。 在 IdP 用户帐户的 SAML 声明中包含 `administrator` 属性，其值为 `true`。 有关企业所有者的更多信息，请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)”。 diff --git a/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md index 058bee4daa..3eba650d23 100644 --- a/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md +++ b/translations/zh-CN/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md @@ -1 +1 @@ -If you can't sign into your enterprise because {% data variables.product.product_name %} can't communicate with your SAML IdP, you can contact {% data variables.contact.github_support %}, who can help you access {% data variables.product.product_name %} to update the SAML SSO configuration. 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。 +如果您因 {% data variables.product.product_name %} 无法与您的 SAML IDP 通信而无法登录企业，您可以联系 {% data variables.contact.github_support %} 帮助您访问 {% data variables.product.product_name %} SAML SSO 配置。 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。 diff --git a/translations/zh-CN/data/reusables/saml/create-a-machine-user.md b/translations/zh-CN/data/reusables/saml/create-a-machine-user.md index 0f0bdbf11d..9b1479accf 100644 --- a/translations/zh-CN/data/reusables/saml/create-a-machine-user.md +++ b/translations/zh-CN/data/reusables/saml/create-a-machine-user.md @@ -1 +1 @@ -Create and use a dedicated machine user account on your IdP to associate with the first enterprise owner account on {% data variables.product.product_name %}. Store the credentials for the user account securely in a password manager. +在您的 IdP 上创建并使用一个专用的机器用户帐户来关联到 {% data variables.product.product_name %} 上的第一个企业所有者帐户。 将用户帐户的凭据安全地存储在密码管理器中。 diff --git a/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md b/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md index be784eeb4f..49c7524fe5 100644 --- a/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/zh-CN/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML 单点登录 (SSO) 为 {% data variables.product.prodname_dotcom %} 上的组织所有者和企业所有者提供一种控制安全访问仓库、议题和拉取请求等组织资源的方法。 diff --git a/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md b/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md index 632a7d42d9..359c8d3e18 100644 --- a/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md +++ b/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md @@ -1 +1 @@ -You must periodically authenticate with your SAML IdP to authenticate and gain access to {% if currentVersion == "free-pro-team@latest" %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. 此登录期的持续时间由 IdP 指定，一般为 24 小时。 此定期登录要求会限制访问的时长，您必须重新验证身份后才可继续访问。 {% if currentVersion == "free-pro-team@latest" %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} +您必须定期向 SAML IdP 身份验证并访问 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %} 上的组织资源 {% elsif currentversion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}。 此登录期的持续时间由 IdP 指定，一般为 24 小时。 此定期登录要求会限制访问的时长，您必须重新验证身份后才可继续访问。 {% if currentversion == "free proteam@latest" %}您可以在安全设置中查看和管理正在进行的 SAML 会话。 更多信息请参阅“[查看和管理活动的 SAML 会话](/articles/viewing-and-managing-your-active-saml-sessions)”。{% endif %} diff --git a/translations/zh-CN/data/reusables/scim/after-you-configure-saml.md b/translations/zh-CN/data/reusables/scim/after-you-configure-saml.md index 85246f3cf0..acb23087fd 100644 --- a/translations/zh-CN/data/reusables/scim/after-you-configure-saml.md +++ b/translations/zh-CN/data/reusables/scim/after-you-configure-saml.md @@ -1 +1 @@ -By default, your IdP does not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application. {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}provisions access to your resources on {% else %}creates a user account {% endif %}using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% if currentVersion == "free-pro-team@latest" %}your resources on {% endif %} {% data variables.product.product_name %} and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to {% data variables.product.product_name %}, and you must manually {% if currentVersion == "free-pro-team@latest" %}deprovision access {% else %}deactivate the user account on {% endif %}{% data variables.product.product_name %} during offboarding. You can use SCIM to provision and deprovision {% if currentVersion == "free-pro-team@latest" %}access to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %} {% else %}user accounts and access for {% data variables.product.product_name %} {% endif %}automatically when you assign or unassign the application on your IdP. \ No newline at end of file +默认情况下，当您分配或取消分配应用程序时，您的 IdP 不会自动与 {% data variables.product.product_name %} 通信。 第一次有人浏览 {% if currentVersion == "free-pro-team@latest" %}您在 {% endif %} {% data variables.product.product_name %} 上的资源并通过 IdP 验证登录时，{% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}使用 SAML 实时 (JIT) 预配来预配访问您的资源{% else %}创建用户帐户 {% endif %}。 当您授予 {% data variables.product.product_name %} 的访问权限时，您可能需要手动通知用户，并且在停用期间必须手动 {% if currentVersion == "free-pro-team@latest" %}解除预配访问 {% else %}停用 {% endif %}{% data variables.product.product_name %} 上的用户帐户。 当您在 IdP 上分配或取消分配应用程序时，您可以使用 SCIM 在 {% data variables.product.prodname_dotcom_the_website %} 上自动预配和解除预配 {% if currentVersion == "free-pro-team@latest" %}对您的企业拥有的组织的访问 {% else %}{% data variables.product.product_name %} 的用户帐户和访问{% endif %}。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/scim/supported-idps.md b/translations/zh-CN/data/reusables/scim/supported-idps.md index 84aea5e724..5d83959797 100644 --- a/translations/zh-CN/data/reusables/scim/supported-idps.md +++ b/translations/zh-CN/data/reusables/scim/supported-idps.md @@ -1,4 +1,4 @@ -The following IdPs can provision or deprovision user accounts on {% data variables.product.product_location %} using SCIM. +下面的 IdP 可以使用 SCM 在 {% data variables.product.product_location %} 上预配或解除预配用户帐户。 {% if currentVersion == "github-ae@latest" %} - Azure AD diff --git a/translations/zh-CN/data/reusables/secret-scanning/api-beta.md b/translations/zh-CN/data/reusables/secret-scanning/api-beta.md index 510473ea8d..447a6731fd 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/api-beta.md +++ b/translations/zh-CN/data/reusables/secret-scanning/api-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. +**注意：**{% data variables.product.prodname_secret_scanning %} API 目前处于测试阶段，可能会更改。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/beta.md b/translations/zh-CN/data/reusables/secret-scanning/beta.md index 82fdadded9..88bda856db 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/beta.md +++ b/translations/zh-CN/data/reusables/secret-scanning/beta.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned{% if currentVersion ver_gt "enterprise-server@2.22" %} public and{% endif %} private repositories is currently in beta and subject to change. +**注：**组织拥有的{% if currentVersion ver_gt "enterprise-server@2.22" %}公共和{% endif %}私有仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于测试阶段，可能会更改。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/support/ghae-priorities.md b/translations/zh-CN/data/reusables/support/ghae-priorities.md index e2a72ac7d5..8127afb41e 100644 --- a/translations/zh-CN/data/reusables/support/ghae-priorities.md +++ b/translations/zh-CN/data/reusables/support/ghae-priorities.md @@ -1,6 +1,6 @@ -| 优先级 | 描述 | 示例 | -|:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.

    _After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ |
    • 影响所有用户的核心 Git 或 web 应用程序功能的错误或中断
    • Severe network or performance degradation for majority of users
    • 用完或快速占用存储空间
    • Known security incidents or a breach of access
    | -| {% data variables.product.support_ticket_priority_high %} - Sev B | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers. |
    • 性能下降，影响许多用户的工作效率
    • Reduced redundancy concerns from failures or service degradation
    • Production-impacting bugs or errors
    • {% data variables.product.product_name %} configuration security concerns
    | -| {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}. |
    • Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows
    • Issues with user tools and data collection methods
    • 升级
    • Bug reports, general security questions, or other feature related questions
      • | -| {% data variables.product.support_ticket_priority_low %} - Sev D | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
      • Feature requests and product feedback
      • General questions on overall configuration or use of {% data variables.product.product_name %}
      • Notifying {% data variables.contact.github_support %} of any planned changes
      | +| 优先级 | 描述 | 示例 | +|:----------------------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.support_ticket_priority_urgent %} - 严重程度 A | {% data variables.product.product_name %} 无法访问或完全失败，故障直接影响您的业务操作。

      _在您提交支持工单后，通过电话联系 {% data variables.contact.github_support %} 。_ |
      • 影响所有用户的核心 Git 或 web 应用程序功能的错误或中断
      • 影响大多数用户的网络或性能严重下降
      • 用完或快速占用存储空间
      • 已知安全事件或无法访问
      | +| {% data variables.product.support_ticket_priority_high %} - 严重程度 B | {% data variables.product.product_name %} 在生产环境中失败，对您的业务流程影响有限，或仅影响到某些客户。 |
      • 性能下降，影响许多用户的工作效率
      • 减少故障或服务降级导致的冗余问题
      • 影响生产的 bug 或错误
      • {% data variables.product.product_name %} 配置安全问题
      | +| {% data variables.product.support_ticket_priority_normal %} - 严重程度 C | {% data variables.product.product_name %} 遇到 {% data variables.product.product_name %} 出现有限或中度的问题和错误，或您对 {% data variables.product.product_name %} 有一般的关注或问题。 |
      • 有关使用 {% data variables.product.prodname_dotcom %} API 和功能的建议，或有关集成业务工作流程的问题
      • 用户工具和数据收集方法的问题
      • 升级
      • Bug 报告、一般安全问题或其他功能相关问题
        • | +| {% data variables.product.support_ticket_priority_low %} - 严重程度 D | {% data variables.product.product_name %} 按预期运行，但您有关于 {% data variables.product.product_name %} 的问题或建议，该问题或建议不具有时间敏感性， 或不以其他方式阻止您的团队的生产力。 |
        • 功能请求和产品反馈
        • 关于 {% data variables.product.product_name %} 的整体配置或使用的一般性问题
        • 通知 {% data variables.contact.github_support %} 任何计划中的更改
        | diff --git a/translations/zh-CN/data/reusables/support/government-response-times-may-vary.md b/translations/zh-CN/data/reusables/support/government-response-times-may-vary.md index a171b413d8..3b50e55c7c 100644 --- a/translations/zh-CN/data/reusables/support/government-response-times-may-vary.md +++ b/translations/zh-CN/data/reusables/support/government-response-times-may-vary.md @@ -1,7 +1,7 @@ {% if currentVersion == "github-ae@latest" %} {% note %} -**Note:** Response times and hours of operation may differ for {% data variables.product.prodname_ghe_managed %} for Government. Your Technical Support Account Manager (TSAM) will confirm during your onboarding. +**注：**对政府而言，响应时间和工作时间可能因 {% data variables.product.prodname_ghe_managed %} 而异。 您的技术支持客户经理 (TSAM) 将在您入职期间确认。 {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user-settings/edit_marketplace_listing.md b/translations/zh-CN/data/reusables/user-settings/edit_marketplace_listing.md index c35b32dbea..6a8c55b075 100644 --- a/translations/zh-CN/data/reusables/user-settings/edit_marketplace_listing.md +++ b/translations/zh-CN/data/reusables/user-settings/edit_marketplace_listing.md @@ -1 +1 @@ -5. 向下滚动到 Marketplace 部分，然后单击 **Edit Marketplace listing（编辑 Marketplace 上架信息）**。 只有在注册您的应用程序时允许任何用户或组织安装该应用程序，Marketplace 部分才可见。 更多信息请参阅 [Marketplace 要求](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/)列表。 ![编辑 GitHub Marketplace 上架信息的链接](/assets/images/marketplace/marketplace_edit_listing_text.png) +5. 在应用设置登录页上，向下滚动到 Marketplace 部分，然后单击 **List in Marketplace（Marketplace 中的商品）**。 如果已有 Marketplace 上架信息草稿，请单击 **Edit Marketplace listing（编辑 Marketplace 上架信息）**。 只有在注册您的应用程序时允许任何用户或组织安装该应用程序，Marketplace 部分才可见。 更多信息请参阅 [Marketplace 要求](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/)列表。 ![编辑 GitHub Marketplace 上架信息的链接](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md index 93d25e699a..293058d64a 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下项之一：`opened`、`edited`、`closed`、`assigned`、`unassigned`、`review_requested`、`review_request_removed`、`ready_for_review`、`labeled`、`unlabeled`、`synchronize`、`locked`、`unlocked` 或 `reopened`。 如果操作为 `closed`，并且 `merged` 键为 `false`，则拉取请求随未合并的提交而关闭。 如果操作为 `closed`，并且 `merged` 键为 `true`，则拉取请求被合并。 | +| 键 | 类型 | 描述 | +| -------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作内容. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. 如果操作为 `closed`，并且 `merged` 键为 `false`，则拉取请求随未合并的提交而关闭。 如果操作为 `closed`，并且 `merged` 键为 `true`，则拉取请求被合并。 | diff --git a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md index a58983f8a4..c689bb3644 100644 --- a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -1,4 +1,4 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | ----------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. This can be either `created`, `resolved`, or `reopened`. | -| `警报` | `对象` | The secret scanning alert involved in the event. | +| 键 | 类型 | 描述 | +| -------- | ----- | -------------------------------------------------- | +| `action` | `字符串` | 执行的操作内容. 可以是 `created`、`resolved` 或 `reopened` 之一。 | +| `警报` | `对象` | 事件中涉及的密码扫描警报。 | diff --git a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md index e57ad29240..b189db8516 100644 --- a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -1 +1 @@ -Activity related to secret scanning alerts in a repository. 活动类型在有效负载对象的操作属性中指定。 For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” +与仓库中的密码扫描警报相关的活动。 活动类型在有效负载对象的操作属性中指定。 更多信息请参阅“[关于密码扫描](/github/administering-a-repository/about-secret-scanning)”。 diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index 4a82e2e98e..6570d67a67 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -138,9 +138,19 @@ product_sublanding: learning_paths: 学习路径 learning_paths_desc: 学习路径是一系列帮助您掌握特定主题的指南。 more_guides: 更多指南 - guideTypes: + load_more: 加载更多指南 + all_guides: 所有指南 + no_result: 抱歉，没有与过滤条件匹配的指南。 + filters: + type: 类型 + topic: Topic + all: 所有 + guide_types: overview: 概览 quick_start: 快速入门 tutorial: 教程 how_to: 操作方法指南 reference: 参考 +learning_track_nav: + prevGuide: 上一个指南 + nextGuide: 下一个指南 diff --git a/translations/zh-CN/data/variables/action_code_examples.yml b/translations/zh-CN/data/variables/action_code_examples.yml index 6978c32a73..11401c6912 100644 --- a/translations/zh-CN/data/variables/action_code_examples.yml +++ b/translations/zh-CN/data/variables/action_code_examples.yml @@ -1,62 +1,62 @@ --- - - title: Example services - description: Example workflows using service containers + title: 示例服务 + description: 使用服务容器的示例工作流程 languages: JavaScript href: actions/example-services tags: - - service containers + - 服务容器 - - title: Declaratively setup GitHub Labels - description: GitHub Action to declaratively setup labels across repos + title: 声明设置 GitHub 标签 + description: 声明设置跨仓库标签的 GitHub Actions languages: JavaScript href: lannonbr/issue-label-manager-action tags: - issues - labels - - title: Declaratively sync GitHub labels - description: GitHub Action to sync GitHub labels in the declarative way + title: 声明同步 GitHub 标签 + description: 以声明方式同步 GitHub 标签的 GitHub Actions languages: 'Go, Dockerfile' href: micnncim/action-label-syncer tags: - issues - labels - - title: Add releases to GitHub - description: Publish Github releases in an action + title: 向 GitHub 添加版本 + description: 在操作中发布 Github 版本 languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: - 发行版 - - publishing + - 发布 - - title: Publish a docker image to Dockerhub - description: A Github Action used to build and publish Docker images + title: 向 Dockerhub 发布 Docker 映像 + description: 用于生成和发布 Docker 映像的 Github 操作 languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: - docker - - publishing + - 发布 - 构建 - - title: Create an issue using content from a file - description: A GitHub action to create an issue using content from a file + title: 使用文件中的内容创建议题 + description: 使用文件中的内容创建议题的 GitHub 操作 languages: 'JavaScript, Python' href: peter-evans/create-issue-from-file tags: - issues - - title: Publish GitHub Releases with Assets - description: GitHub Action for creating GitHub Releases + title: 使用资产发布 GitHub 版本 + description: 用于创建 GitHub 版本的 GitHub 操作 languages: 'TypeScript, Shell, JavaScript' href: softprops/action-gh-release tags: - 发行版 - - publishing + - 发布 - title: GitHub Project Automation+ - description: Automate GitHub Project cards with any webhook event + description: 使用任何 web 挂钩事件自动执行 GitHub 项目卡 languages: JavaScript href: alex-page/github-project-automation-plus tags: @@ -65,8 +65,8 @@ - issues - 拉取请求 - - title: Run GitHub Actions Locally with a web interface - description: Runs GitHub Actions workflows locally (local) + title: 使用 Web 界面在本地运行 GitHub Actions + description: 本地运行 GitHub Actions 工作流程（本地） languages: 'JavaScript, HTML, Dockerfile, CSS' href: phishy/wflow tags: @@ -74,8 +74,8 @@ - devops - docker - - title: Run your GitHub Actions locally - description: Run GitHub Actions Locally in Terminal + title: 在本地运行 GitHub Actions + description: 在终端中本地运行 GitHub Actions languages: 'Go, Shell' href: nektos/act tags: @@ -83,47 +83,47 @@ - devops - docker - - title: Build and Publish Android debug APK - description: Build and release debug APK from your Android project + title: 生成和发布 Android 调试 APK + description: 从 Android 项目生成和发布调试 APK languages: 'Shell, Dockerfile' href: ShaunLWM/action-release-debugapk tags: - android - 构建 - - title: Generate sequential build numbers for GitHub Actions - description: GitHub action for generating sequential build numbers. + title: 为 GitHub Actions 生成序列生成编号 + description: 用于生成序列生成编号的 GitHub 操作。 languages: JavaScript href: einaregilsson/build-number tags: - 构建 - automation - - title: GitHub actions to push back to repository - description: Push Git changes to GitHub repository without authentication difficulties + title: 要推回到仓库的 GitHub 操作 + description: 将 Git 更改推送到 GitHub 仓库，而不会遇到身份验证困难 languages: 'JavaScript, Shell' href: ad-m/github-push-action tags: - - publishing + - 发布 - - title: Generate release notes based on your events - description: Action to auto generate a release note based on your events + title: 根据您的事件生成发行说明 + description: 根据事件自动生成发行说明的操作 languages: 'Shell, Dockerfile' href: Decathlon/release-notes-generator-action tags: - 发行版 - - publishing + - 发布 - - title: Create a GitHub wiki page based on the provided markdown file - description: Create a GitHub wiki page based on the provided markdown file + title: 基于提供的 markdown 文件创建 GitHub wiki 页面 + description: 基于提供的 markdown 文件创建 GitHub wiki 页面 languages: 'Shell, Dockerfile' href: Decathlon/wiki-page-creator-action tags: - wiki - - publishing + - 发布 - - title: Label your Pull Requests auto-magically (using committed files) - description: Github action to label your pull requests auto-magically (using committed files) + title: 自动标记您的拉取请求（使用提交的文件） + description: 自动标记拉取请求（使用提交的文件）的 Github 操作 languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -131,32 +131,32 @@ - issues - labels - - title: Add Label to your Pull Requests based on the author team name - description: Github action to label your pull requests based on the author name + title: 根据作者团队名称向拉取请求添加标签 + description: 根据作者名称标记拉取请求的 Github 操作 languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: - 拉取请求 - labels - - title: Get a list of file changes with a PR/Push - description: This action gives you will get outputs of the files that have changed in your repository + title: 使用 PR/Push 获取文件更改列表 + description: 此操作可让您获取仓库已更改的文件的输出 languages: 'TypeScript, Shell, JavaScript' href: trilom/file-changes-action tags: - 工作流程 - 仓库 - - title: Private actions in any workflow - description: Allows private GitHub Actions to be easily reused + title: 任何工作流程中的私人操作 + description: 允许轻松重复利用私人 GitHub Actions languages: 'TypeScript, JavaScript, Shell' href: InVisionApp/private-action-loader tags: - 工作流程 - tools - - title: Label your issues using the issue's contents - description: A GitHub Action to automatically tag issues with labels and assignees + title: 使用议题的内容标记您的议题 + description: 使用标签和受理人自动标记议题的 GitHub 操作 languages: 'JavaScript, TypeScript' href: damccorm/tag-ur-it tags: @@ -165,16 +165,16 @@ - labels - issues - - title: Rollback a GitHub Release - description: A GitHub Action to rollback or delete a release + title: 回滚 GitHub 版本 + description: 回滚或删除版本的 GitHub 操作 languages: 'JavaScript' href: author/action-rollback tags: - 工作流程 - 发行版 - - title: Lock closed issues and Pull Requests - description: GitHub Action that locks closed issues and pull requests after a period of inactivity + title: 锁定已关闭的议题和拉取请求 + description: 在一段时间不活动后锁定关闭的议题和拉取请求的 GitHub 操作 languages: 'JavaScript' href: dessant/lock-threads tags: @@ -182,8 +182,8 @@ - 拉取请求 - 工作流程 - - title: Get Commit Difference Count Between Two Branches - description: This GitHub Action compares two branches and gives you the commit count between them + title: 获取两个分支之间的提交差异数 + description: 此 GitHub 操作比较两个分支，并提供它们之间的提交数 languages: 'JavaScript, Shell' href: jessicalostinspace/commit-difference-action tags: @@ -191,8 +191,8 @@ - 差异 - 工作流程 - - title: Generate Release Notes Based on Git References - description: GitHub Action to generate changelogs, and release notes + title: 基于 Git 引用生成发行说明 + description: 生成变更日志和发行说明的 GitHub 操作 languages: 'JavaScript, Shell' href: metcalfc/changelog-generator tags: @@ -201,8 +201,8 @@ - 工作流程 - 变更日志 - - title: Enforce Policies on GitHub Repositories and Commits - description: Policy enforcement for your pipelines + title: 对 GitHub 仓库和提交实施策略 + description: 管道的策略实施 languages: 'Go, Makefile, Dockerfile, Shell' href: talos-systems/conform tags: @@ -210,8 +210,8 @@ - build-automation - 工作流程 - - title: Auto Label Issue Based - description: Automatically label an issue based on the issue description + title: 基于议题自动标记 + description: 根据议题描述自动标记议题 languages: 'TypeScript, JavaScript, Dockerfile' href: Renato66/auto-label tags: @@ -219,8 +219,8 @@ - 工作流程 - automation - - title: Update Configured GitHub Actions to the Latest Versions - description: CLI tool to check whehter all your actions are up-to-date or not + title: 将配置的 GitHub Actions 更新到最新版本 + description: 用于检查所有操作是否为最新的 CLI 工具 languages: 'C#, Inno Setup, PowerSHell, Shell' href: fabasoad/ghacu tags: @@ -228,8 +228,8 @@ - cli - 工作流程 - - title: Create Issue Branch - description: GitHub Action that automates the creation of issue branches + title: 创建议题分支 + description: 自动创建议题分支的 GitHub 操作 languages: 'JavaScript, Shell' href: robvanderleek/create-issue-branch tags: @@ -237,16 +237,16 @@ - issues - labels - - title: Remove old artifacts - description: Customize artifact cleanup + title: 删除旧构件 + description: 自定义构件清理 languages: 'JavaScript, Shell' href: c-hive/gha-remove-artifacts tags: - 构件 - 工作流程 - - title: Sync Defined Files/Binaries to Wiki or External Repositories - description: GitHub Action to automatically sync changes to external repositories, like the wiki, for example + title: 将定义的文件/二进制文件同步到 Wiki 或外部仓库 + description: 自动将更改同步到外部仓库（例如 wiki）的 GitHub 操作 languages: 'Shell, Dockerfile' href: kai-tub/external-repo-sync-action tags: @@ -254,8 +254,8 @@ - sync - 工作流程 - - title: Create/Update/Delete a GitHub Wiki page based on any file - description: Updates your GitHub wiki by using rsync, allowing for exclusion of files and directories and actual deletion of files + title: 基于任何文件创建/更新/删除 GitHub Wiki 页面 + description: 使用 rsync 更新 GitHub wiki，允许排除文件和目录以及实际删除文件 languages: 'Shell, Dockerfile' href: Andrew-Chen-Wang/github-wiki-action tags: @@ -264,7 +264,7 @@ - 工作流程 - title: Prow GitHub Actions - description: Automation of policy enforcement, chat-ops, and automatic PR merging + description: 策略实施、聊天操作和自动 PR 合并的自动化 languages: 'TypeScript, JavaScript' href: jpmcb/prow-github-actions tags: @@ -272,8 +272,8 @@ - prow - 工作流程 - - title: Check GitHub Status in your Workflow - description: Check GitHub Status in your workflow + title: 检查工作流程中的 GitHub 状态 + description: 检查工作流程中的 GitHub 状态 languages: 'TypeScript, JavaScript' href: crazy-max/ghaction-github-status tags: @@ -281,8 +281,8 @@ - 监视 - 工作流程 - - title: Manage labels on GitHub as code - description: GitHub Action to manage labels (create/rename/update/delete) + title: 将 GitHub 上的标签作为代码管理 + description: 用于管理标签的 GitHub 操作（创建/重命名/更新/删除） languages: 'TypeScript, JavaScript' href: crazy-max/ghaction-github-labeler tags: @@ -290,8 +290,8 @@ - 工作流程 - automation - - title: Distribute funding in free and open source projects - description: Continuous Distribution of funding to project contributors and dependencies + title: 在免费和开源项目中分配资金 + description: 持续向项目贡献者和依赖项分配资金 languages: 'Python, Dockerfile, Shell, Ruby' href: protontypes/libreselery tags: @@ -299,8 +299,8 @@ - funding - payment - - title: Herald rules for GitHub - description: Add reviewers, subscribers, labels and assignees to your PR + title: GitHub 的 Herald 规则 + description: 将审查者、订阅者、标签和受理人添加到您的 PR languages: 'TypeScript, JavaScript' href: gagoar/use-herald-action tags: @@ -309,17 +309,17 @@ - assignees - 拉取请求 - - title: Codeowner validator - description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations + title: 代码所有者验证器 + description: 确保 GitHub CODEOWNERS 文件的正确性，支持公共和私有 GitHub 仓库以及 GitHub Enterprise 安装 languages: 'Go, Shell, Makefile, Dockerfile' href: mszostok/codeowners-validator tags: - codeowners - - validate + - 验证 - 工作流程 - - title: Copybara Action - description: Move and transform code between repositories (ideal to maintain several repos from one monorepo) + title: Copybara 操作 + description: 在仓库之间移动和转化代码（非常适合从单个仓库维护几个仓库） languages: 'TypeScript, JavaScript, Shell' href: olivr/copybara-action tags: @@ -327,9 +327,9 @@ - copybara - 工作流程 - - title: Deploy static files to GitHub Pages - description: GitHub Action to publish website to GitHub Pages automatically + title: 将静态文件部署到 GitHub Pages + description: 用于将网站自动发布到 GitHub Pages 的 GitHub 操作 languages: 'TypeScript, JavaScript' href: peaceiris/actions-gh-pages tags: - - publishing + - 发布 diff --git a/translations/zh-CN/data/variables/discussions_community_examples.yml b/translations/zh-CN/data/variables/discussions_community_examples.yml index 8b3594f2ec..577f78ada5 100644 --- a/translations/zh-CN/data/variables/discussions_community_examples.yml +++ b/translations/zh-CN/data/variables/discussions_community_examples.yml @@ -2,37 +2,37 @@ - #Images and descriptions are pulled directly from the repo repo: vercel/next.js - description: The React Framework + description: React 框架 - repo: gatsbyjs/gatsby - description: Build blazing fast, modern apps and websites with React + description: 使用 React 构建快速、现代的应用和网站 - repo: nodejs/node description: Node.js JavaScript runtime ✨🐢🚀✨ - repo: tailwindlabs/tailwindcss - description: A utility-first CSS framework for rapid UI development. + description: 用于快速 UI 发展的实用程序优先 CSS 框架。 - repo: laravel/framework - description: Laravel is a web application framework with expressive, elegant syntax. + description: Laravel 是一个 Web 应用程序框架，采用富有表现力、优雅的语法。 - repo: prisma/prisma - description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite + description: Node.js 和 TypeScript 的现代数据库访问（ORM 替代方法） | PostgreSQL, MySQL, MariaDB & SQLite - repo: dotnet/csharplang - description: 'The official repo for the design of the C# programming language' + description: 'C# 编程语言设计的官方存储库' - repo: home-assistant/frontend - description: '🍭 Frontend for Home Assistant' + description: '🍭 Home Assistant 的前端' - repo: jspsych/jsPsych - description: A JavaScript library for creating and running behavioral experiments in a web browser + description: 用于在 Web 浏览器中创建和运行行为实验的 JavaScript 库 - repo: adonisjs/core - description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' + description: '🚀 高度集中于开发者人体工程学、稳定性和信心的 Node.js 框架' - repo: ImageMagick/ImageMagick description: '🧙‍♂️ ImageMagick 7' - repo: react-hook-form/react-hook-form - description: '📋 React Hooks for forms validation (Web + React Native)' + description: '📋 用于表单验证的反应挂钩 (Web + React Native)' diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 0a3f340e0f..bafe52a212 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -61,6 +61,7 @@ prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub 应用程序' prodname_github_apps: 'GitHub 应用程序' prodname_oauth_app: 'OAuth 应用程序' +prodname_oauth_apps: 'OAuth 应用程序' #API and developer docs prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs' prodname_support_forum_with_url: '[GitHub API 开发和支持论坛](https://github.community/c/github-api-development-and-support/37)'