From 51d8e22040ae6f7eae7e7117159f614b438aef5c Mon Sep 17 00:00:00 2001 From: Feanil Patel Date: Fri, 10 Dec 2021 10:30:41 -0500 Subject: [PATCH 01/29] Update small grammer error in understanding-github-actions.md --- .../learn-github-actions/understanding-github-actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/learn-github-actions/understanding-github-actions.md b/content/actions/learn-github-actions/understanding-github-actions.md index 61b4d91686..6e69efdfbc 100644 --- a/content/actions/learn-github-actions/understanding-github-actions.md +++ b/content/actions/learn-github-actions/understanding-github-actions.md @@ -30,7 +30,7 @@ topics: ## The components of {% data variables.product.prodname_actions %} -You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created. Your workflow contains one or more _jobs_ which can run in sequential order or in parallel. Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify in your workflow. +You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created. Your workflow contains one or more _jobs_ which can run in sequential order or in parallel. Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow. ![Workflow overview](/assets/images/help/images/overview-actions-simple.png) From 926a392bfa7114afe44209780b4cac98238300fb Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Fri, 10 Dec 2021 18:04:34 +0000 Subject: [PATCH 02/29] update search indexes --- lib/search/indexes/github-docs-3.0-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 70 files changed, 140 insertions(+), 140 deletions(-) diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br index 71d370293c..bc8ff7fa46 100644 --- a/lib/search/indexes/github-docs-3.0-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:523bb99ba64e015730c0ee4d44214e4749931d8fe993731ae9722cb4740bf2e9 -size 608275 +oid sha256:10d42428e30f1b25086cc219bc09a2fc2aed07eaaee1f07ad43df2887b98bb71 +size 608337 diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br index 01a32ab24d..3b18cc6f13 100644 --- a/lib/search/indexes/github-docs-3.0-cn.json.br +++ b/lib/search/indexes/github-docs-3.0-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:88fed378fc9b60c3758870df22a5fe20e8ea961e805029609b0e0e3496f642d0 -size 1478849 +oid sha256:a4cab87e3465b3eae5fe86c2ecbd5cc022b314d1e2086f6bbd7c917c3b42e81f +size 1478625 diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br index 17c85c812c..4521fbd186 100644 --- a/lib/search/indexes/github-docs-3.0-en-records.json.br +++ b/lib/search/indexes/github-docs-3.0-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:27ffc5a8732d08fdfb2bb090ebf578aac11e66e0e4485b3245f96db63ec55203 -size 946850 +oid sha256:fa180a5683105483e9c5a56dcd9bd7e21aeed4f39ec18f5d26de7c9d367f3a91 +size 946338 diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br index cdae963ffe..2e305cc6d1 100644 --- a/lib/search/indexes/github-docs-3.0-en.json.br +++ b/lib/search/indexes/github-docs-3.0-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8b1fe317148c888d3ad4ca215f9733d272d6822d8b472184a3e284ab92a9785e -size 3863014 +oid sha256:7d1b3ee1d33f9b5f33e2b03c8ce684497fe88512794c6bcc4388ac9384e22230 +size 3862419 diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br index 1303a74bfd..886b353088 100644 --- a/lib/search/indexes/github-docs-3.0-es-records.json.br +++ b/lib/search/indexes/github-docs-3.0-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:65de77524464cf13dc99c5c9e65b3b53de3c5c190518bee6d83345fbc902b78e -size 591456 +oid sha256:0cfcbeef8fc9de0a752dcac7d3568d4b00132bad8fb7e7734a518f40b28d5412 +size 591263 diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br index be04668fe8..b7edf891c2 100644 --- a/lib/search/indexes/github-docs-3.0-es.json.br +++ b/lib/search/indexes/github-docs-3.0-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1bbaf848598f219a59f9ba90be3cb2a78686f499eea5fe0bf6af08f8ec54b755 -size 2604796 +oid sha256:1964fd62d244e813753db4e5dc4254dcd317cad131632757d777118e2f67d0e7 +size 2605072 diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br index 2f98b6c673..03bd684477 100644 --- a/lib/search/indexes/github-docs-3.0-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:846b70cffae751f8847b76a370287951543303e1966450deb43fd8a8f9972cba -size 620976 +oid sha256:5848be2856d21f5f8b2d77ac9e221e64fdac5609edb5d6b0276e7e74e5ece600 +size 620885 diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br index c8cda38568..d47f78747d 100644 --- a/lib/search/indexes/github-docs-3.0-ja.json.br +++ b/lib/search/indexes/github-docs-3.0-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bc2079c62fb9844681f0982fbd710ffea32ea7aa4a48d207c78c59e7759e8593 -size 3369009 +oid sha256:c8fc2c5896ed7d481afb0bf65f515e1286d1b139e29118f13ebc7ef65e6403e0 +size 3368854 diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br index 2017f8a94a..3edba01310 100644 --- a/lib/search/indexes/github-docs-3.0-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:71d476c5a357652a3f88b3b8097a806fccecfcabf33c8c75e1a4decc434126de -size 588635 +oid sha256:dcdcd992c2ee1f8344621bc3ac1f29fcf0e0a37936e00a8fe266b83af94428bc +size 588528 diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br index 3e7ead79f9..33d9db19f0 100644 --- a/lib/search/indexes/github-docs-3.0-pt.json.br +++ b/lib/search/indexes/github-docs-3.0-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2b0388c7061fd4dc924884811bab0a1fed2e2d5301fd04961461ff8ac1375a8f -size 2594409 +oid sha256:c21068488f16dacc7be98e91b7057168c6da68840b31b8cbbebdb840d40d71cc +size 2594756 diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index f3ca3f201e..2dce7599ab 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:69996421dd64542950f8b40c9afb08685ee77d19da0df01c9d1e4d8847a35ce4 -size 621541 +oid sha256:2de4a84e60a053d403933b0b8301544634044847b2921611078e89183947c1e7 +size 621660 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index 1d741bee74..c60ef585cd 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:01ae123b0cc5aa5425391ebcae80a3c7a0fd1fd0a4cc97a4afd3511785f4ea68 -size 1520139 +oid sha256:9d24a8264da02c7546641124a4b226d41218aa8762962daaefbaa48183989251 +size 1520173 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index 7a46ab4cb3..9084c6ecf3 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:77e84fce427b1238fad33cff26a549000368eb0bdcf356e50e0eea1d86c9c0c7 -size 970802 +oid sha256:0647b4a8c953cbae9be64a7ea104683007a11a79a652f066e3089f262ee9213d +size 971055 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index a599d0dc06..803aee2d9b 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fa542ffc5b33b46c0ce2614b6c0dabcf7d2d8290d6de74b46c6dbe38f6929395 -size 3953015 +oid sha256:837da80b9b5fe1b4fc8e8254109323993df4aae8ef0092d1aa04bd0cc3af90ed +size 3952493 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index 4108e02e0d..59048a4e5b 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b38dcdfd1002f69d83dcf51a07b79f2853e6157fd80e07af6fdbe772c68a4534 -size 603629 +oid sha256:cd348934a86fbded70471ad6ec99b21ac8429476acae442d0177e800ab66a121 +size 603468 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index 1cd3e898ca..f5907249a4 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8daa2310c92a6b3064682fb08bf7666fc0a3bcf28c6b7a069a5cc761e5f267d3 -size 2666436 +oid sha256:2e3d5a1bd0342aa0a0cd7ed32832530b05b9720d5610e77c68c4f8cf930da6a1 +size 2666744 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index 7e0e83b9d5..cef15b6df6 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9f73d5aef9bae3ce2e6bf45d93b685787d283932390f95c8ac6e71a15b5cf22f -size 634481 +oid sha256:f159da93099bbf0fa665d012750682f8e2eab7d067cc5fc99b7526c1988410e5 +size 634374 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index a40858bcc2..7a11d4a68f 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0cf49eb6d289795385731fc6d4f698291ed8392ac0d33eff6a5ae1245e2d448a -size 3447979 +oid sha256:f3689d933e1add60769a5d77aab9d5b62c94862a6a1749dc9bb2f6b82d68a970 +size 3448302 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index 650604cda1..cb51f3fbf5 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:015cdea005ee0165b3d54df68ab3d174084a68b7e0a590892ad5fd2b01c994f4 -size 600940 +oid sha256:9e243eb8a2b3c68ed2a6f482ee6c145347aa781e4452ca38e903c1bf99a8744e +size 600967 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 2996721455..17a91eb79c 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:957d2b1107c40d573de029ffc2a97cd90d374ba4f0c379fa987897e41e7ffc3d -size 2658993 +oid sha256:af01e9094eb7e360a806d5211120be7df69b78019fc17e05dedfcc74fa873c01 +size 2659050 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index b370f82560..12cc3dde11 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c7c425f6f1699da9e2ab6082abaa77b40a5ccc2b17fa9360505d3ab81c247f4f -size 632919 +oid sha256:1663bb3f498bb4563858b3d5331eef7fa25332a6e2ef517372afed9c1d8d9cc7 +size 632771 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 6fbad3c910..e60bebc445 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d1c363904c62c61a8a3f26eb30c0afb6ac07395bbcfbcbe2b74d83f619527824 -size 1546547 +oid sha256:721354ca43c816289c59aa563f71f70e99f72c8b9daa295a1efa6f1be5fbbf88 +size 1546681 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 91ca2c5e7a..97b9a6ee44 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2e419e8f7c058ba882c3d95cbf28ae6fdd634cae80b527b9c84d01d54b7cbfa6 -size 1002516 +oid sha256:ea092577ef879ad7f3b8d2adb238b15e78aa7dfef1e0b2a4316563dd52150743 +size 1002125 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index dbc01c596a..5e2e031770 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:60bd067bbdf29acc5a674e5b524d4a9dd94001eed0f6662514a9d4a17df68cc7 -size 4075260 +oid sha256:8f96155360a81ae2a351c9b556512e4bd542496d74636424152a08b14d13c45d +size 4075114 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 68d7aea981..395c3ed0f8 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:079b4e97bfb6e6654036da7fb6337ce37caf994c32ffb0d1b61aa9bb0db8588c -size 614574 +oid sha256:83b158296c576bbf23742cd544f617cc8ad82c1d5ecca8a9c4a9d7e16054eb34 +size 614409 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index af25f83b4a..8d11d54714 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4b91c7314f5f411546f13902509b17acbaa9240b4b473d64a50de5b426f774fe -size 2720764 +oid sha256:ca37b5599a30e40e29bbbc4e84aea29e4d1a279cf350dd379cf4ff58fc0d3816 +size 2721680 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index 2065f9fde8..6e7a3b6968 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5b14f804c63fbf718473d93a1e6b45c775b9586bec0fde2c342362ea1aeb3740 -size 645751 +oid sha256:db3d012e816e97a6d780bb5a97d8bdd617436fa77fd9b470b97c7934d68c967b +size 645691 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index c762385f85..55199c0ee6 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0134c564d6ce464641ba46dc6ae37fb54461e410bd974198047b420ce20e2d4f -size 3515056 +oid sha256:65347277b4ef444c6387760a5385222aec5d73487574c7e0fe12896b4fe060cf +size 3515134 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 0d65aa74bf..88f980b5eb 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e190411ed5bc1c2c1db2b343a668e78e902e3442eb5e42d084a5e50c03a26dac -size 611931 +oid sha256:9439d944e23303362e3741cf9edd011545ad1c5f08d4ab839d0a25de01741f17 +size 611843 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index 538f2d33a8..d67cfb440f 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a47a5e47d67d282e8d4b44f550b8b1ea8e9cce958d1a9672d44140d0c487246b -size 2707665 +oid sha256:66eafeca115a3bd8c34c05ebeaa2a4b60197fa6ed61873bd98dc0e5450dac727 +size 2707392 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 6b7852dac8..a8c1f0086a 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bbccdbb2bf668d625a4a80c7286934ae87a694572aa6cf2716ca623bd58803cf -size 653497 +oid sha256:8eeccf5d6c87a8d32b4f5b1f8d5366b3e50777d87efcb2c7a15a6b55422d90c0 +size 653685 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index de8d1bc182..3d276f8700 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fef2e292b11a3654a722e5c4b62bace00684c654f3eeac08e6836259cd66d2b9 -size 1605101 +oid sha256:feff0af3a6a2c4d7b8776071b45ba0da28999ae281a769f241485398a9ef0bc0 +size 1604806 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 1e5bfa5711..5b28ad762b 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a24c950c15a60739782bce9fb4b30b1fddd5aa70c05e9b00b79056d50def2cb4 -size 1036723 +oid sha256:02e1e9d31080ef0507cdaa21d0c0b7d7b12830e6a4f6c1437e156631b300f57d +size 1035714 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 64602ef2a0..bdf94d2dd0 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5176eeed4001a108e267bb2aea150535d5f2fd27c470801981a611d433ec47a3 -size 4176412 +oid sha256:ec4b4f7a4f117bf3860964ce3564106a6dbfef966ddf3e804862f0b6c6497115 +size 4176290 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 5f15326565..81c6257ded 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b2ba152932f9cd723b3629939f1dfa7492801cab82ec7eb38066bdfd95d4f01e -size 632844 +oid sha256:a7b68f1e97f3082b63fae2bd1c412fb48e534bc0065f786091556a4f5ef15a78 +size 632701 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 505fb9d06b..665e139d86 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8922da7fa37ac326a22afeb97a13e527f0c65c35ff9b1fbfcab2b4009ffff3a2 -size 2818873 +oid sha256:1400361ed61c2f51abc2606cf3b53f1b06d6e42dcafc3f482f600a1be8b5f219 +size 2818705 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index e0a5642ba1..40df4a48c3 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ed3d591d2550219dc4ff5992dbf84dba27506ca5f7df873b95d60b655aae0128 -size 667508 +oid sha256:18b5147177e1f59e4687c1a242ba4616c52a6155f0c7d7a2b5a6ff8eae138781 +size 667445 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index bd20d38fee..fed5843fec 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b368fe1989e89293927c82640edfef2a2aa24cb169a5d8c1b81b66e2355d820e -size 3635089 +oid sha256:f39fe7b1601b48c44204c843a011802b4f7e2a6a38a1d44d5872ca99185b10ec +size 3635235 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index ac0012113b..ab63de5b57 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7dcb79e4be1dba81ad1607d0471e164bb31848ee80047b8388883ee27e165baa -size 631179 +oid sha256:0801d82cae9d7ed80791600d94f1a90eee7acc9f7afd307fe4c3d50431decf0c +size 631280 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index 66c2bc251c..b1978e8ae9 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:03746bf3f0e855ac791fb53b50a4a01c0ff6562d0ea9234adb50cad5b1df26f6 -size 2794872 +oid sha256:a2627d77d945003237a04df15972a4cd9d3972b4d8b676f911935b9a2daaa2c3 +size 2795203 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 33382c9b9c..a514381a74 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cac56c407d88dca3a7fc016ca6305a9e96e55a6e9e0b9f128337bd28fa1cdd45 -size 862142 +oid sha256:a08664a1b1406babeafcad007ddf6263bced5f7c64670a1fdc152ca6c8724d91 +size 862394 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 003b55c846..669efd37ee 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a3a30d271c1bf32dd956ac7f7b67714fcca46008e113656c436f80fbf83d25a5 -size 1793272 +oid sha256:0547ccf68570caa493c2038772325dda3a0c8cc9e299873dc51164a3b986e29c +size 1793546 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 5b0460fd69..b9eddf9eeb 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:80503629c2b253a7f491fd9eb629d721bd6d8d93e5bdaca92d6cdd6c305019b3 -size 1326914 +oid sha256:b4caf8125361a4d17e8614a578211853a02e04402fc2efa7aa7f59eab3e68cab +size 1326399 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 75b3b7f335..34fa973b24 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e8e2598724c0f37e2795cc3130e7c24cffb7804cf996e1d7179c1c80743d880c -size 5055157 +oid sha256:88982a1afe93d3604513e5e74ba2fe58563134d34efb5496a8e7217cbaad3060 +size 5052992 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index 23797a7dcc..3cbe2bbaab 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d747594189c90de48a8835f9bd2af6634eca82fc3d067f346719f593b90e254a -size 809121 +oid sha256:89a7f069d1d16d584fb2a16c9b33f266046a5c6b403cdb15893831cfe8b650c3 +size 809085 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 11e12222af..d3a5edfda3 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:96d61d1518d93f885286d886ef56059f70067eaf23fed4dfeb9f16c8a96fbbe8 -size 3425879 +oid sha256:6c22bc683230177b4242cafbd98e132db1c3a25180869f838a2a82feec6f7420 +size 3426303 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index 4c4efecd7e..e9ea151377 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0ce5cd056a7f7d352b82a5a6c4436c7ccf83c00b128d51ba35c1e12b04bcc915 -size 876304 +oid sha256:405352756feb4a26ccd4525067375cd9141a64c560059ea54a6d8e8d5ed89d4e +size 876446 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 90e7a2d803..69f2a395b2 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c533b4c4c41077ef2a3ffc4c720ead521da5aaeb70bd27f82cebc508fff8c314 -size 4535436 +oid sha256:0c35ec2ff0cd0c5ad3a3dc7e6939066a4dfce866899b800e3e3b60909d170da4 +size 4535569 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index 9446afa90e..194072c94b 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:beb30df032a6b97ebaf8014aa5186c20cff58b471db2007cb2c53ecb7ebd9369 -size 810502 +oid sha256:d198f935f9eac0f1ef58abda9a2eaa81b0abbe0568e55cdc4ae7fce825dabfb4 +size 810403 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 763ff7cfad..07953bed60 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0f1b2e8705e8483d1b8c84ccd9f5d6788aee5663c4742ec0f60fe4232cdd4df4 -size 3395292 +oid sha256:eccf7c3764a8d080c6d5da7211231b2ec4d9fd28005a2458bb749411673f076e +size 3395458 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index d2bcdb75b4..e84a6f9b81 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0cfd8c1ecc6b0acd83022a9ca8361bc138d0dfa20ff1e901a55c18d9f3a52afb -size 506675 +oid sha256:85780d14eb238aa40ff4d453c97f4289b28fb31fb05343e74b40352021f5ad0f +size 506837 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 9ca9e09ac3..8be56718c0 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3c6b82b8214346eeb7dddc0a544b5fc4503b69d709d334942b48f0be639a1eb2 -size 1214798 +oid sha256:0dc01f2322662f054514422e35e5e6d445e88a784c742e43b45cfd77cb8eb176 +size 1214846 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index 49211f57fd..1204c3f47a 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ae4e788a873f5fa4e98152303a576da6d3bc88ed9ac525042eb4443d1599147e -size 825954 +oid sha256:74c2a6016c10a99f548125464ae6203313f1d41b92d63c00509e814126f67c3e +size 826019 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index f071673ec1..1c60cc870c 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:08638a0acfe4cdc5ac70554501127a7188ad3bffd7f28a130e63a5a6f717e0ea -size 3298689 +oid sha256:fac6d5f8c2e0f67071d3c36618d8905bff69105b73d9161d7187eff2021e2085 +size 3298210 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index a5e3c29275..1b511c14af 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ea9d0eaae25799c980481317f6fc5457860c71502a64013234d87d147dbb519d -size 476819 +oid sha256:92de45896a216dad74205b470b01b130c616fc6388c39175f20cf258badc5408 +size 476843 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index c5ce84d268..7012ee3e15 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:49d22feb8ee421185f3c3f518ba94560b58670eca2f11b2c12bcdc29f178de44 -size 2027083 +oid sha256:125b921ec57a559234af30a0e4de23be8cbdc807fc8332a56fe7da277c73c272 +size 2027598 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index 420ad61315..3e6b830d40 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:727bbe72c5aef0eb58ed977f0d5e762fda6c575fde1196ad6561e0ab8f0e8d11 -size 516840 +oid sha256:53bbc50bf02d6bdae98614fe4837d7e087c3e08a89a25835ccd7a896473f5cb4 +size 516938 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index e1ae1b26cb..1e6f64fae9 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ca1f2d0b1977c0aaf80de42b7a06db6c1febd6d03a7f9a3c4ff36f59cc9712a7 -size 2707593 +oid sha256:649c50ba8c591f251e2ebc9c390f493df419ea54ab721dc9514b74dc73942186 +size 2708110 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index f73c9852c8..06337d448d 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7171df35c1fae8463bed08973a8f5c733c42bca8f32ec0f82dd756e9147e2f5b -size 492216 +oid sha256:c1579250c17b80d9bbc30839343baf8ecf65337f4a0d1f3c032fcdd70e5cf9c0 +size 492277 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index ed706df792..8c9f1a7ca4 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cb203ab0b8a0f5223650b96f0afaf6be260736556cdcce4b85e79137c65df80a -size 2114282 +oid sha256:c6ca6b0ace7455c329fa8dc2f7a3c5e560784166980675242a7f7aebf4267ad2 +size 2114003 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 6ef9f6a5ec..42b748c4b6 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:72d1e15cb2b884150162866373f859b59d08ab67935819a02473d066cde11d54 -size 768538 +oid sha256:bffd18bbb794d4ef39162387425ab2e2e3cec65e32281a73615cdcd21c8527a0 +size 768189 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 794e3e081c..fe166f8c7e 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:67dffac8a514edbc9e4345283f0b03605e88417e1db38a9be92c5d841dc97dd8 -size 1797664 +oid sha256:b62bba8680f47c974ca97053f283e894725de1c7bfe08682ac44da81721ac474 +size 1795939 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index eb10029a4f..61dd8c856d 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cef8e6963bb3cb21a60e621468ce41a34959296cb52b502d08b804d13e0ea0a1 -size 1178996 +oid sha256:12f6e6efd60bc1d002bee852dc9c39dfe971cf2ba53b9870cce2936475baa272 +size 1178706 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index 05700ee3f0..8609d6d620 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8702f4dd50deaefe9775785bc999aaee8cd21a5bb0432a4b42301de9d9fd9d1d -size 4738835 +oid sha256:d94dfb634aa8af87e41fd66118cbc5fc37299657a82cd331871f906c51826a95 +size 4740691 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index ea533d9eb0..425821b9dd 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:699f7d96aaf576239848f0b17ad1e6eee7fbd577e66faea508379bab47752ca4 -size 745766 +oid sha256:d3b32582c66574349c281413c315dbe244e3778657e960b3c4e50c6b6d9f8b44 +size 745549 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index fe23126f79..7ae800afad 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1069dd6fc6599af6a11a3a1839faafed95dcf868a2613e5fefb24fdcc97e275f -size 3329522 +oid sha256:e4bbb37f572c65c6344145f20e813ef31672f45f395e6b936659a44eb7c903a5 +size 3329151 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 68a2a0ae97..79f4c516b3 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:08356f4e959c7f8bf9d3014ab835f5076384e7c6245487f2e1aa0da2017c2980 -size 786316 +oid sha256:edf8785e7bd94359e8d60e8d51088bf0e2c9c090417a469cddc65e0bf649bc96 +size 786301 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 763e51feed..34bc70be26 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0295a9f58405554b48939fc1522ddb48754fa6568b94cc54a90aaff4163b90ec -size 4284313 +oid sha256:53b0b199a3f4892ed76e8c62a94517b5ca9d1dbb81896b257a65b1795cc08d7e +size 4284403 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index 2c10461ef3..90453a8b62 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b6777b1160e9d8882737030decf2cc315a21886348e363a1e342ed79b5c55d5a -size 747757 +oid sha256:07eac4f5c636db43f11bef501a3e048dfb698303be99f6869a1234c857d45a94 +size 747740 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 9fc4350216..088d0547ee 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5aa75c7b99af993a62cb7d05b21e815a77106571e047e40ca5bfe00079c0bed6 -size 3287266 +oid sha256:2361fc4c672e92b6c7b974d4df6ec773875d6b4c26685733603b9146d90c0f2e +size 3287987 From 9571ea21bb3fe4e454fc4d71012d0eba1750950c Mon Sep 17 00:00:00 2001 From: Cadu Ribeiro Date: Fri, 10 Dec 2021 20:22:27 -0300 Subject: [PATCH 03/29] Change Enterprise Cloud docs to reflect the new 30 days trial (#23503) --- .../onboarding/getting-started-with-github-enterprise-cloud.md | 2 +- .../setting-up-a-trial-of-github-enterprise-cloud.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 336444f7a6..d8227e1740 100644 --- a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -49,7 +49,7 @@ To use an organization account with {% data variables.product.prodname_ghe_cloud Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." #### 3. Setting up and managing billing -When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." +When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." diff --git a/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md index ba8a064edd..8c44c1a59a 100644 --- a/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -29,7 +29,7 @@ You can use organizations for free with {% data variables.product.prodname_free_ ## About trials of {% data variables.product.prodname_ghe_cloud %} -You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "About billing for {% data variables.product.prodname_marketplace %}." +You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "About billing for {% data variables.product.prodname_marketplace %}." Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats. From 72a7eddd9bf5630737e9ab2420905b661ac44f22 Mon Sep 17 00:00:00 2001 From: bonsohi <31749534+bonsohi@users.noreply.github.com> Date: Fri, 10 Dec 2021 15:29:15 -0800 Subject: [PATCH 04/29] actions workaround alert for 3.3.0 (#23591) * actions workaround alert * Update known issue Co-authored-by: Ethan P <56270045+ethanpalm@users.noreply.github.com> --- data/release-notes/enterprise-server/3-3/0.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/data/release-notes/enterprise-server/3-3/0.yml b/data/release-notes/enterprise-server/3-3/0.yml index 7641f7af58..9dec376333 100644 --- a/data/release-notes/enterprise-server/3-3/0.yml +++ b/data/release-notes/enterprise-server/3-3/0.yml @@ -1,5 +1,5 @@ date: '2021-12-07' -intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." +intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."

**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command. sections: features: - heading: Security Manager role @@ -240,6 +240,7 @@ sections: # - PLACEHOLDER known_issues: + - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command. - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - Custom firewall rules are removed during the upgrade process. - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. From 9e0d7de8484090e92fcf0f4c9ab62d9e799a2808 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 10 Dec 2021 15:51:04 -0800 Subject: [PATCH 05/29] Fix redirect orphans (#23555) * Remove self referential redirects * remove redirect that should be visible * Delete outdated article * Readd redirect for deleted article * Remove deleted article from index * remove translations --- ...-from-azure-pipelines-to-github-actions.md | 1 - ...grating-from-circleci-to-github-actions.md | 1 - ...igrating-from-jenkins-to-github-actions.md | 1 - ...rating-from-travis-ci-to-github-actions.md | 1 - content/github/index.md | 1 - ...setting-up-and-managing-your-enterprise.md | 25 ------------------- ...setting-up-and-managing-your-enterprise.md | 25 ------------------- ...setting-up-and-managing-your-enterprise.md | 25 ------------------- ...setting-up-and-managing-your-enterprise.md | 25 ------------------- ...setting-up-and-managing-your-enterprise.md | 25 ------------------- 10 files changed, 130 deletions(-) delete mode 100644 content/github/setting-up-and-managing-your-enterprise.md delete mode 100644 translations/es-ES/content/github/setting-up-and-managing-your-enterprise.md delete mode 100644 translations/ja-JP/content/github/setting-up-and-managing-your-enterprise.md delete mode 100644 translations/pt-BR/content/github/setting-up-and-managing-your-enterprise.md delete mode 100644 translations/zh-CN/content/github/setting-up-and-managing-your-enterprise.md diff --git a/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 0d4690ad1e..1821812d34 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -2,7 +2,6 @@ title: Migrating from Azure Pipelines to GitHub Actions intro: '{% data variables.product.prodname_actions %} and Azure Pipelines share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.' redirect_from: - - /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions versions: fpt: '*' diff --git a/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 9c7290205c..aa34d59cd5 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -2,7 +2,6 @@ title: Migrating from CircleCI to GitHub Actions intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.' redirect_from: - - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions - /actions/learn-github-actions/migrating-from-circleci-to-github-actions versions: fpt: '*' diff --git a/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 91f7db33cf..dba3e38286 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -2,7 +2,6 @@ title: Migrating from Jenkins to GitHub Actions intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.' redirect_from: - - /actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions versions: fpt: '*' diff --git a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 1c4995ed9d..2cf18968d5 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -2,7 +2,6 @@ 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 %}.' redirect_from: - - /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions versions: fpt: '*' diff --git a/content/github/index.md b/content/github/index.md index a526e281f2..b8c5e0a166 100644 --- a/content/github/index.md +++ b/content/github/index.md @@ -20,5 +20,4 @@ children: - /understanding-how-github-uses-and-protects-your-data - /site-policy - /site-policy-deprecated - - /setting-up-and-managing-your-enterprise --- diff --git a/content/github/setting-up-and-managing-your-enterprise.md b/content/github/setting-up-and-managing-your-enterprise.md deleted file mode 100644 index 6ca74b1940..0000000000 --- a/content/github/setting-up-and-managing-your-enterprise.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Setting up and managing your enterprise -shortTitle: Enterprise management -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account - - /categories/setting-up-and-managing-your-enterprise-account -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Policies ---- - -## This documentation has moved - -{% ifversion fpt or ghec %} -Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can now find documentation about enterprise management in the new {% data variables.product.prodname_ghe_cloud %} version of "[Enterprise administrators]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin#all-docs)." - -For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-github-enterprise-cloud-version-for-github-docs/). -{% else %} -Enterprise owners on {% data variables.product.product_name %} can now find documentation about enterprise management in "[Enterprise administrators](/admin#all-docs)." -{% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise.md deleted file mode 100644 index 8a966c88f7..0000000000 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Configurar y administrar tu empresa -shortTitle: Enterprise management -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account - - /categories/setting-up-and-managing-your-enterprise-account -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Policies ---- - -## This documentation has moved - -{% ifversion fpt or ghec %} -Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can now find documentation about enterprise management in the new {% data variables.product.prodname_ghe_cloud %} version of "[Enterprise administrators]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin#all-docs)." - -For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-github-enterprise-cloud-version-for-github-docs/). -{% else %} -Enterprise owners on {% data variables.product.product_name %} can now find documentation about enterprise management in "[Enterprise administrators](/admin#all-docs)." -{% endif %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise.md deleted file mode 100644 index e098a6c974..0000000000 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Enterprise の設定と管理 -shortTitle: Enterprise management -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account - - /categories/setting-up-and-managing-your-enterprise-account -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Policies ---- - -## This documentation has moved - -{% ifversion fpt or ghec %} -Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can now find documentation about enterprise management in the new {% data variables.product.prodname_ghe_cloud %} version of "[Enterprise administrators]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin#all-docs)." - -For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-github-enterprise-cloud-version-for-github-docs/). -{% else %} -Enterprise owners on {% data variables.product.product_name %} can now find documentation about enterprise management in "[Enterprise administrators](/admin#all-docs)." -{% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise.md deleted file mode 100644 index eb008aaa9c..0000000000 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Configurar e gerenciar sua empresa -shortTitle: Enterprise management -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account - - /categories/setting-up-and-managing-your-enterprise-account -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Policies ---- - -## This documentation has moved - -{% ifversion fpt or ghec %} -Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can now find documentation about enterprise management in the new {% data variables.product.prodname_ghe_cloud %} version of "[Enterprise administrators]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin#all-docs)." - -For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-github-enterprise-cloud-version-for-github-docs/). -{% else %} -Enterprise owners on {% data variables.product.product_name %} can now find documentation about enterprise management in "[Enterprise administrators](/admin#all-docs)." -{% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise.md deleted file mode 100644 index f651580274..0000000000 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: 设置和管理企业 -shortTitle: Enterprise management -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account - - /categories/setting-up-and-managing-your-enterprise-account -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Policies ---- - -## This documentation has moved - -{% ifversion fpt or ghec %} -Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can now find documentation about enterprise management in the new {% data variables.product.prodname_ghe_cloud %} version of "[Enterprise administrators]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin#all-docs)." - -For more information about the {% data variables.product.prodname_ghe_cloud %} version of GitHub Docs, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-10-15-github-enterprise-cloud-version-for-github-docs/). -{% else %} -Enterprise owners on {% data variables.product.product_name %} can now find documentation about enterprise management in "[Enterprise administrators](/admin#all-docs)." -{% endif %} From daa16775d88aa461eb3bee1f43e39fdfdbb8ead5 Mon Sep 17 00:00:00 2001 From: Marcelo Jacobus Date: Fri, 10 Dec 2021 22:48:22 -0300 Subject: [PATCH 06/29] Fix label for translation batches (#23577) --- .github/workflows/create-translation-batch-pr.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/workflows/create-translation-batch-pr.yml b/.github/workflows/create-translation-batch-pr.yml index af1059a162..6b7edffb10 100644 --- a/.github/workflows/create-translation-batch-pr.yml +++ b/.github/workflows/create-translation-batch-pr.yml @@ -169,8 +169,9 @@ jobs: gh pr create --title "New translation batch for ${{ matrix.language }}" \ --base=main \ --head=${{ steps.set-branch.outputs.BRANCH_NAME }} \ - --body-file /tmp/pr-body.txt || git push origin :${{ steps.set-branch.outputs.BRANCH_NAME }} \ - --label "translation-batch" + --label "translation-batch-${{ matrix.language }}" \ + --label "translation-batch" \ + --body-file /tmp/pr-body.txt || git push origin :${{ steps.set-branch.outputs.BRANCH_NAME }} - name: Approve PR if: github.ref_name == 'main' From 04c8ed5726931a730c795310cff14a9df3ed335b Mon Sep 17 00:00:00 2001 From: Francis <15894826+francisfuzz@users.noreply.github.com> Date: Fri, 10 Dec 2021 18:08:00 -0800 Subject: [PATCH 07/29] fix: verify Crowdin CLI download before installing (#23515) This change uses the suggested steps in https://support.crowdin.com/cli-tool/#debian, with a slight modification in creating the `crowdin.list` file in the `/etc/apt/sources.list.d` directory. This approach creates a new file for `crowdin.list`, then pipes the content to `tee -a`. Credits go to [this Ask Ubuntu thread reply](https://askubuntu.com/questions/185268/permission-denied-etc-apt-sources-list/185270#185270). --- .github/workflows/create-translation-batch-pr.yml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/.github/workflows/create-translation-batch-pr.yml b/.github/workflows/create-translation-batch-pr.yml index 6b7edffb10..791999bf03 100644 --- a/.github/workflows/create-translation-batch-pr.yml +++ b/.github/workflows/create-translation-batch-pr.yml @@ -62,10 +62,15 @@ jobs: - name: Remove unwanted git hooks run: rm .git/hooks/post-checkout - - name: Install Crowdin CLI + # https://support.crowdin.com/cli-tool/#debian + - name: Download and install the public signing key + run: wget -qO - https://artifacts.crowdin.com/repo/GPG-KEY-crowdin | sudo apt-key add - + - name: Create the crowdin.list file in the /etc/apt/sources.list.d directory run: | - wget https://artifacts.crowdin.com/repo/deb/crowdin3.deb -O /tmp/crowdin.deb - sudo dpkg -i /tmp/crowdin.deb + sudo touch /etc/apt/sources.list.d/crowdin.list + echo "deb https://artifacts.crowdin.com/repo/deb/ /" | sudo tee -a /etc/apt/sources.list.d/crowdin.list + - name: Install the Crowdin CLI Debian Package + run: sudo apt-get update && sudo apt-get install crowdin3 # Delete empty source files that would be rejected by Crowdin breaking the workflow - name: Remove empty source files From 49f737356accb00f00d42e512645a1931ac8502d Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Sat, 11 Dec 2021 02:40:20 +0000 Subject: [PATCH 08/29] update search indexes --- lib/search/indexes/github-docs-3.0-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 70 files changed, 140 insertions(+), 140 deletions(-) diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br index bc8ff7fa46..7ac80e35ea 100644 --- a/lib/search/indexes/github-docs-3.0-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:10d42428e30f1b25086cc219bc09a2fc2aed07eaaee1f07ad43df2887b98bb71 -size 608337 +oid sha256:552c7175e712699b70f8b13180b136a2e28ff10e4bfbc80d26ae222615cc3b05 +size 608035 diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br index 3b18cc6f13..d7224954ca 100644 --- a/lib/search/indexes/github-docs-3.0-cn.json.br +++ b/lib/search/indexes/github-docs-3.0-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a4cab87e3465b3eae5fe86c2ecbd5cc022b314d1e2086f6bbd7c917c3b42e81f -size 1478625 +oid sha256:e011822f1e310cc584f151419fe968277a86ef21ed4c4ba8ff65a6b7078c57a9 +size 1477732 diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br index 4521fbd186..9c5be40741 100644 --- a/lib/search/indexes/github-docs-3.0-en-records.json.br +++ b/lib/search/indexes/github-docs-3.0-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fa180a5683105483e9c5a56dcd9bd7e21aeed4f39ec18f5d26de7c9d367f3a91 -size 946338 +oid sha256:00ec22354e7759fffcfb13abe9a4e5939e9011f393abcc07ee111aa880b2e7ca +size 946287 diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br index 2e305cc6d1..a33264cfc6 100644 --- a/lib/search/indexes/github-docs-3.0-en.json.br +++ b/lib/search/indexes/github-docs-3.0-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7d1b3ee1d33f9b5f33e2b03c8ce684497fe88512794c6bcc4388ac9384e22230 -size 3862419 +oid sha256:94946394bc356ac947acc6304779a86ddaa6ce2b18149c28ce6edd95c52dc996 +size 3862441 diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br index 886b353088..83b85ccc62 100644 --- a/lib/search/indexes/github-docs-3.0-es-records.json.br +++ b/lib/search/indexes/github-docs-3.0-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0cfcbeef8fc9de0a752dcac7d3568d4b00132bad8fb7e7734a518f40b28d5412 -size 591263 +oid sha256:50fade472d04fc7dd9b8f97826ddb5d583df37cc7de41ea125b10066516bb63c +size 591063 diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br index b7edf891c2..1fedf99253 100644 --- a/lib/search/indexes/github-docs-3.0-es.json.br +++ b/lib/search/indexes/github-docs-3.0-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1964fd62d244e813753db4e5dc4254dcd317cad131632757d777118e2f67d0e7 -size 2605072 +oid sha256:00f5762bb0ff797121d48faa448e7b65c5bf415cfb4f71abfcbc0d1615d92514 +size 2604237 diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br index 03bd684477..ec560bdbcd 100644 --- a/lib/search/indexes/github-docs-3.0-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5848be2856d21f5f8b2d77ac9e221e64fdac5609edb5d6b0276e7e74e5ece600 -size 620885 +oid sha256:434aaf71b2076721b917c9e01dd30d507c965b204a4833837bd116036230e946 +size 620609 diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br index d47f78747d..6e4b3399e3 100644 --- a/lib/search/indexes/github-docs-3.0-ja.json.br +++ b/lib/search/indexes/github-docs-3.0-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c8fc2c5896ed7d481afb0bf65f515e1286d1b139e29118f13ebc7ef65e6403e0 -size 3368854 +oid sha256:3cd01d934e42243d3387232cd878ede26242a115756e78b8e94f1571982245a6 +size 3367405 diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br index 3edba01310..90a45f53d6 100644 --- a/lib/search/indexes/github-docs-3.0-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dcdcd992c2ee1f8344621bc3ac1f29fcf0e0a37936e00a8fe266b83af94428bc -size 588528 +oid sha256:fdd9b47794419908d06bbf4a9a4adb4369154c17aabfbb5cc624f32a10c70bcb +size 588505 diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br index 33d9db19f0..df364491b5 100644 --- a/lib/search/indexes/github-docs-3.0-pt.json.br +++ b/lib/search/indexes/github-docs-3.0-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c21068488f16dacc7be98e91b7057168c6da68840b31b8cbbebdb840d40d71cc -size 2594756 +oid sha256:92ab91ad2d1dcaf0af0b0fea77d1b04851346691f6ea3a109c37c4955a703ee7 +size 2594494 diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index 2dce7599ab..37d5915f2b 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2de4a84e60a053d403933b0b8301544634044847b2921611078e89183947c1e7 -size 621660 +oid sha256:605f66d01b27c4207ddb09850b0281737119791453fd618b37073b3833bfe874 +size 621578 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index c60ef585cd..c767630c5b 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9d24a8264da02c7546641124a4b226d41218aa8762962daaefbaa48183989251 -size 1520173 +oid sha256:82018927e2796c033b8cfc575ac858a5286e19df2675ad84f1467f26c537611c +size 1519710 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index 9084c6ecf3..3abf683115 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0647b4a8c953cbae9be64a7ea104683007a11a79a652f066e3089f262ee9213d -size 971055 +oid sha256:4a3100b5c5bbb7d42c623b85a95caa4a79f5a5409c8206055b7cd052f356bc79 +size 970431 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index 803aee2d9b..bab5fa9147 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:837da80b9b5fe1b4fc8e8254109323993df4aae8ef0092d1aa04bd0cc3af90ed -size 3952493 +oid sha256:333289a0ec51cb1eb0f7a0c328867ff05980a86bd386751ee4653bd0ed245222 +size 3951320 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index 59048a4e5b..19ca687a45 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cd348934a86fbded70471ad6ec99b21ac8429476acae442d0177e800ab66a121 -size 603468 +oid sha256:5c5c40ed0743b7c0a61b836e1b9088d9a49df2da33b75b4b8d66c7763f4f4be4 +size 603532 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index f5907249a4..1855827954 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2e3d5a1bd0342aa0a0cd7ed32832530b05b9720d5610e77c68c4f8cf930da6a1 -size 2666744 +oid sha256:abfa36ec9df300d92508284cf98e733cf6538423941c0321c17af77005a3ced3 +size 2665632 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index cef15b6df6..d232ce0678 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f159da93099bbf0fa665d012750682f8e2eab7d067cc5fc99b7526c1988410e5 -size 634374 +oid sha256:de710ef522f0671272d78873ef91d3e2704b237933b14c7c172886637322be37 +size 634149 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index 7a11d4a68f..e26c775606 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f3689d933e1add60769a5d77aab9d5b62c94862a6a1749dc9bb2f6b82d68a970 -size 3448302 +oid sha256:de9f8368a2b5962954f31f6c1ee3cf34640f0eb388f2f103c17755d5afef2ce9 +size 3446849 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index cb51f3fbf5..8c152d31cf 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9e243eb8a2b3c68ed2a6f482ee6c145347aa781e4452ca38e903c1bf99a8744e -size 600967 +oid sha256:0846dac4fb80b927d19d45f3f93ebdd5b8f5593da5c86d47aedf0cfe308c2ebd +size 600847 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 17a91eb79c..f7231eda19 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:af01e9094eb7e360a806d5211120be7df69b78019fc17e05dedfcc74fa873c01 -size 2659050 +oid sha256:ea8a456b2b783c2c1c756bab1c0b0c01d7aabd825298702bb4f7e16543002afc +size 2658103 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 12cc3dde11..c9e1cbade2 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1663bb3f498bb4563858b3d5331eef7fa25332a6e2ef517372afed9c1d8d9cc7 -size 632771 +oid sha256:0f0c930d6f6c1384474a1b0ba948c4a919d66430551ae6bdfe5c033dada3508d +size 632698 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index e60bebc445..e015920c83 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:721354ca43c816289c59aa563f71f70e99f72c8b9daa295a1efa6f1be5fbbf88 -size 1546681 +oid sha256:9155e8571ec820fda00a0020fb96e5b74d6e81fbe448dd3b6c15938bde05eb1a +size 1545993 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 97b9a6ee44..9779837d27 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ea092577ef879ad7f3b8d2adb238b15e78aa7dfef1e0b2a4316563dd52150743 -size 1002125 +oid sha256:791e7afc25a506016ca0088e1968898ab66debc16e097f2951caf62505fcf2d8 +size 1001576 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 5e2e031770..f5b1f5fb5c 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8f96155360a81ae2a351c9b556512e4bd542496d74636424152a08b14d13c45d -size 4075114 +oid sha256:51949006a19e2662bffb95f51bf02a9617652576978cdfed0e998ebf81544618 +size 4074051 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 395c3ed0f8..2383b6335d 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:83b158296c576bbf23742cd544f617cc8ad82c1d5ecca8a9c4a9d7e16054eb34 -size 614409 +oid sha256:9fd3a183df4d8869ba6b0d43cccae2bff10fce35a69aa6b3d691fc7b4dc79651 +size 614290 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index 8d11d54714..755fe38726 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ca37b5599a30e40e29bbbc4e84aea29e4d1a279cf350dd379cf4ff58fc0d3816 -size 2721680 +oid sha256:24f780d8120e21488064dad011348c7fe9d5ac4786f21d19652675a5e0cf4ef6 +size 2721226 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index 6e7a3b6968..68c5aace44 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:db3d012e816e97a6d780bb5a97d8bdd617436fa77fd9b470b97c7934d68c967b -size 645691 +oid sha256:baf83e0e99ac6383d28cc4e89923e723ea47bc37cbc78ed235e885fe240407bc +size 645546 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 55199c0ee6..e87103c359 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:65347277b4ef444c6387760a5385222aec5d73487574c7e0fe12896b4fe060cf -size 3515134 +oid sha256:efbbdabf63982759a4b073a51c1d32de1e03da3780284f472dd07de6c7bbd9b7 +size 3515316 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 88f980b5eb..adff0e5286 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9439d944e23303362e3741cf9edd011545ad1c5f08d4ab839d0a25de01741f17 -size 611843 +oid sha256:4e6249af1f8acad27346194b33a892481737ea9982081fdd222a869a9ff99c14 +size 611860 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index d67cfb440f..0a2af0db34 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:66eafeca115a3bd8c34c05ebeaa2a4b60197fa6ed61873bd98dc0e5450dac727 -size 2707392 +oid sha256:14bcc87cf6994d4e83cad357d1a5be19a0a501b82a0d02e54a4f00d50740dd7b +size 2706997 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index a8c1f0086a..fc95b1f6d2 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8eeccf5d6c87a8d32b4f5b1f8d5366b3e50777d87efcb2c7a15a6b55422d90c0 -size 653685 +oid sha256:bd1d2cb849692c8929e2a624cee9d2cc58c98b08d6e00791b8fb1aeec8e80d61 +size 653462 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 3d276f8700..6924a5964c 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:feff0af3a6a2c4d7b8776071b45ba0da28999ae281a769f241485398a9ef0bc0 -size 1604806 +oid sha256:3a964608c7d96b660d1712762b36a641b835712eff1d8214dd446cab023916c3 +size 1605591 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 5b28ad762b..6cb8df86a7 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:02e1e9d31080ef0507cdaa21d0c0b7d7b12830e6a4f6c1437e156631b300f57d -size 1035714 +oid sha256:245442df10e46d746d846dbfcaa1f2b0bffe883f46e50050bf9c5ac1f9cb6b59 +size 1035661 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index bdf94d2dd0..3617b93ceb 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ec4b4f7a4f117bf3860964ce3564106a6dbfef966ddf3e804862f0b6c6497115 -size 4176290 +oid sha256:965df7bf6ddddb96c37652cd7016c63449e7291fddeb42e5a47d55aa599bfc2b +size 4174936 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 81c6257ded..fad9a55a2a 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a7b68f1e97f3082b63fae2bd1c412fb48e534bc0065f786091556a4f5ef15a78 -size 632701 +oid sha256:d15d8ed72e7049c2c0a3f4c863ca0629828564e7cb1c36a90d32a9b7875f39a6 +size 632536 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 665e139d86..cdee59ad13 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1400361ed61c2f51abc2606cf3b53f1b06d6e42dcafc3f482f600a1be8b5f219 -size 2818705 +oid sha256:2665e0df638f698dbcf9670b34bfc544c99287c5c11e38d31a2abb0a167fdcb5 +size 2818802 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 40df4a48c3..ce9e19be9c 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:18b5147177e1f59e4687c1a242ba4616c52a6155f0c7d7a2b5a6ff8eae138781 -size 667445 +oid sha256:6c300386221a5e1f8053d0bc5e8f8c494abba18be68798b4ef9d93a7a39892e3 +size 667153 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index fed5843fec..a5986bea48 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f39fe7b1601b48c44204c843a011802b4f7e2a6a38a1d44d5872ca99185b10ec -size 3635235 +oid sha256:8056d5fb6098dacbf25ad0fe6543a26e0a5421f6ac0522baec820cf34fbd300a +size 3634903 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index ab63de5b57..047112629d 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0801d82cae9d7ed80791600d94f1a90eee7acc9f7afd307fe4c3d50431decf0c -size 631280 +oid sha256:15f990165d5e0896aa817a637c0903a55dd37b1655d4be23df69963fdbad8c2f +size 631123 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index b1978e8ae9..6469f95e65 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a2627d77d945003237a04df15972a4cd9d3972b4d8b676f911935b9a2daaa2c3 -size 2795203 +oid sha256:86dfd97621150905e96e59502dae1c5c5fcdd98feafe8435e4614123b6a44e9a +size 2794785 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index a514381a74..737cc210b5 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a08664a1b1406babeafcad007ddf6263bced5f7c64670a1fdc152ca6c8724d91 -size 862394 +oid sha256:b314ae5df4427a223d22efa496ba21dd012ff2008222e6667a54ddd9f7f7cbed +size 862119 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 669efd37ee..21c5a0a97d 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0547ccf68570caa493c2038772325dda3a0c8cc9e299873dc51164a3b986e29c -size 1793546 +oid sha256:3386a734b68bd02f6dfb04c42a0090b59aeef96b073b151922c479eeb33fd8ae +size 1793303 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index b9eddf9eeb..a6d6eae6c6 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b4caf8125361a4d17e8614a578211853a02e04402fc2efa7aa7f59eab3e68cab -size 1326399 +oid sha256:15a56453032ae56fb126dc14e91353f80a0f820875cedb224e09323e2f317132 +size 1326155 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 34fa973b24..0b852f2ef4 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:88982a1afe93d3604513e5e74ba2fe58563134d34efb5496a8e7217cbaad3060 -size 5052992 +oid sha256:645890f69f3c30e09397adcc3f5a68defc9485b03ca301143e3325e13a4f9503 +size 5052506 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index 3cbe2bbaab..ade29640df 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:89a7f069d1d16d584fb2a16c9b33f266046a5c6b403cdb15893831cfe8b650c3 -size 809085 +oid sha256:10a645885f4d289d57921e701b8b6d19562e125511104f1d7048a1bdd5bc750e +size 808768 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index d3a5edfda3..7402924a4f 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6c22bc683230177b4242cafbd98e132db1c3a25180869f838a2a82feec6f7420 -size 3426303 +oid sha256:a43c3349b8b1edf2dbd614a7cdb720a8c356c3da2302579f697488125efb2543 +size 3424407 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index e9ea151377..7635add2a2 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:405352756feb4a26ccd4525067375cd9141a64c560059ea54a6d8e8d5ed89d4e -size 876446 +oid sha256:736f8aa4eb0a9dfc4be54589eabdffc7b2a69c95c9814045a58bb3142a8c845f +size 876139 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 69f2a395b2..efab9b6cb2 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0c35ec2ff0cd0c5ad3a3dc7e6939066a4dfce866899b800e3e3b60909d170da4 -size 4535569 +oid sha256:e07f786bf6e70b29156e43a8b54142ecba2cd3e23dabc6483b83178989849ac8 +size 4534121 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index 194072c94b..7c5a99af83 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d198f935f9eac0f1ef58abda9a2eaa81b0abbe0568e55cdc4ae7fce825dabfb4 -size 810403 +oid sha256:da08c9b916f2614d08fd8428cce21541a5eca83f2b23ff68f2d61c834a4b95b2 +size 810197 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 07953bed60..fc6f1b00bd 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eccf7c3764a8d080c6d5da7211231b2ec4d9fd28005a2458bb749411673f076e -size 3395458 +oid sha256:0ebe0aed8ec6331771b059080c2d7df4d06542f7d9f75a3f09177fbc2862098f +size 3394105 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index e84a6f9b81..035ac43699 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:85780d14eb238aa40ff4d453c97f4289b28fb31fb05343e74b40352021f5ad0f -size 506837 +oid sha256:168a45b79d3993a2059abf9bfc784d7afc691201d89c0b091ff86e072d6ff973 +size 506706 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 8be56718c0..a2194fd64d 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0dc01f2322662f054514422e35e5e6d445e88a784c742e43b45cfd77cb8eb176 -size 1214846 +oid sha256:05e835e10b02baf7af831f970cf44e97f7decd46c1e24dcc67affab96703b877 +size 1214467 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index 1204c3f47a..0e57f625da 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:74c2a6016c10a99f548125464ae6203313f1d41b92d63c00509e814126f67c3e -size 826019 +oid sha256:dddbbfa4a856842fb6889b74e00a83cc5c13f64dc95a4149507030f8ae4b00ec +size 825749 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 1c60cc870c..aeb175b8eb 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fac6d5f8c2e0f67071d3c36618d8905bff69105b73d9161d7187eff2021e2085 -size 3298210 +oid sha256:2851078f5994b9215f12b2add1efb403c2189cf43305d7dd32b73ee7b432aace +size 3297201 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 1b511c14af..cefb1c2024 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:92de45896a216dad74205b470b01b130c616fc6388c39175f20cf258badc5408 -size 476843 +oid sha256:48a62b309e344bb27db08a168139e58654e693c65678ee477cd2fe50c30e62bc +size 476659 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 7012ee3e15..b463c8ee84 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:125b921ec57a559234af30a0e4de23be8cbdc807fc8332a56fe7da277c73c272 -size 2027598 +oid sha256:11cb30da4051913761a23228d860144fcc7677568b96c60fb398d91d1750c533 +size 2026726 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index 3e6b830d40..b5516bb82c 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:53bbc50bf02d6bdae98614fe4837d7e087c3e08a89a25835ccd7a896473f5cb4 -size 516938 +oid sha256:81e7dacfed580c03cb36969768482bf08c9d7bc77754297dfcff51e3c8200909 +size 516815 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 1e6f64fae9..c56f47b985 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:649c50ba8c591f251e2ebc9c390f493df419ea54ab721dc9514b74dc73942186 -size 2708110 +oid sha256:4aa4ae08ab29f4dec73a316d2c4167df311127707de8212e9c419745b1d891c0 +size 2707312 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 06337d448d..0550343dfb 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c1579250c17b80d9bbc30839343baf8ecf65337f4a0d1f3c032fcdd70e5cf9c0 -size 492277 +oid sha256:f1349362ed3a2e43ba5d4b2a1558367637fcc51ad69a1693135a35e83493415b +size 492093 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 8c9f1a7ca4..dd021b0241 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c6ca6b0ace7455c329fa8dc2f7a3c5e560784166980675242a7f7aebf4267ad2 -size 2114003 +oid sha256:ee274b8a06419bd08e6ddf7b2b75c14cf296ebb7ca16faac6564de9aa2d5f629 +size 2113638 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 42b748c4b6..9ce4a275d1 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bffd18bbb794d4ef39162387425ab2e2e3cec65e32281a73615cdcd21c8527a0 -size 768189 +oid sha256:983b8179612310f9cc1bb18b9e67e3181bc295dcd70c469541b2b551477f3e62 +size 768128 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index fe166f8c7e..46d82d35b7 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b62bba8680f47c974ca97053f283e894725de1c7bfe08682ac44da81721ac474 -size 1795939 +oid sha256:08210ca5c4648aa6f1821514defda508cba45f652ba98b73619987456fe3f66f +size 1796417 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index 61dd8c856d..63a7b0238f 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:12f6e6efd60bc1d002bee852dc9c39dfe971cf2ba53b9870cce2936475baa272 -size 1178706 +oid sha256:07a0fdeb9d269a5681c77601702f0df115f9d8e360ab05f6f39322e4adf6f143 +size 1177971 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index 8609d6d620..6ad738af56 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d94dfb634aa8af87e41fd66118cbc5fc37299657a82cd331871f906c51826a95 -size 4740691 +oid sha256:3c68cf260c4b2f87dc936108c2b6341c2d3a261e9a972c5998e76c0691f75951 +size 4740180 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index 425821b9dd..c69f048596 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d3b32582c66574349c281413c315dbe244e3778657e960b3c4e50c6b6d9f8b44 -size 745549 +oid sha256:77cf2bd8c323c8c1e38f8ec602bbcc5e62f3814f54cc5a2987272a6d0b3873a3 +size 745465 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index 7ae800afad..04629d606e 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e4bbb37f572c65c6344145f20e813ef31672f45f395e6b936659a44eb7c903a5 -size 3329151 +oid sha256:73d29e0800bd9eb32a07ccf06fb9840389256a47c80603d7c9ef118e8608b2e2 +size 3328790 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 79f4c516b3..a3d37b19cd 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:edf8785e7bd94359e8d60e8d51088bf0e2c9c090417a469cddc65e0bf649bc96 -size 786301 +oid sha256:b2aac5f28e6f1be2bc3eb97f08e50d9b8d963225ed2c9195e90b302cd93f0667 +size 785931 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 34bc70be26..82204eead9 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:53b0b199a3f4892ed76e8c62a94517b5ca9d1dbb81896b257a65b1795cc08d7e -size 4284403 +oid sha256:1908b4eaaa409bc31558c905d13bf199020ae5d1ec9683e3316864a272713100 +size 4284093 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index 90453a8b62..4715ba0a1c 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:07eac4f5c636db43f11bef501a3e048dfb698303be99f6869a1234c857d45a94 -size 747740 +oid sha256:ce8440f86d28e718c9d6d61fd0c3e7d1bc6182028c3a3efb34fc63e29c731db6 +size 747664 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 088d0547ee..5441002ec4 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2361fc4c672e92b6c7b974d4df6ec773875d6b4c26685733603b9146d90c0f2e -size 3287987 +oid sha256:2cb5fd5325b2d81a3941d1490fafa81e5bae745bcf0a48cdf99af72c9f50e1fa +size 3286548 From f697835881ba9217ce096900d399addcd1107b96 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Fri, 10 Dec 2021 22:10:36 -0500 Subject: [PATCH 09/29] cleaning up trailing slash redirects (part 3) (#23570) --- .../index.md | 4 ++-- .../viewing-your-subscriptions.md | 10 +++++----- .../about-notifications.md | 2 +- .../configuring-notifications.md | 14 ++++++------- .../index.md | 2 +- .../about-your-profile.md | 4 ++-- .../personalizing-your-profile.md | 10 +++++----- .../pinning-items-to-your-profile.md | 2 +- ...contributions-to-your-githubcom-profile.md | 2 +- .../viewing-contributions-on-your-profile.md | 4 ++-- .../index.md | 4 ++-- ...-collaborators-to-a-personal-repository.md | 4 ++-- ...collaborator-from-a-personal-repository.md | 10 +++++----- ...ourself-from-a-collaborators-repository.md | 6 +++--- .../managing-email-preferences/index.md | 2 +- ...membering-your-github-username-or-email.md | 4 ++-- .../setting-your-commit-email-address.md | 14 ++++++------- .../about-your-personal-dashboard.md | 4 ++-- .../changing-your-github-username.md | 8 ++++---- .../converting-a-user-into-an-organization.md | 4 ++-- .../deleting-your-user-account.md | 2 +- .../managing-user-account-settings/index.md | 4 ++-- ...ss-to-your-user-accounts-project-boards.md | 2 +- .../merging-multiple-user-accounts.md | 4 ++-- .../accessing-an-organization.md | 6 +++--- ...izing-or-hiding-organization-membership.md | 2 +- .../removing-yourself-from-an-organization.md | 2 +- ...ng-organization-approval-for-oauth-apps.md | 4 ++-- content/authentication/index.md | 20 +++++++++---------- .../about-anonymized-urls.md | 2 +- .../about-githubs-ip-addresses.md | 8 ++++---- .../creating-a-personal-access-token.md | 4 ++-- .../creating-a-strong-password.md | 2 +- .../githubs-ssh-key-fingerprints.md | 2 +- .../index.md | 2 +- ...moving-sensitive-data-from-a-repository.md | 6 +++--- .../reviewing-your-ssh-keys.md | 4 ++-- ...updating-your-github-access-credentials.md | 4 ++-- ...-github-using-two-factor-authentication.md | 6 +++--- ...delivery-methods-for-your-mobile-device.md | 2 +- ...-factor-authentication-recovery-methods.md | 10 +++++----- .../configuring-two-factor-authentication.md | 6 +++--- .../index.md | 6 +++--- ...ccount-if-you-lose-your-2fa-credentials.md | 4 ++-- .../get-started/using-git/about-git-rebase.md | 2 +- .../using-git/about-git-subtree-merges.md | 4 ++-- ...etting-changes-from-a-remote-repository.md | 2 +- .../pushing-commits-to-a-remote-repository.md | 2 +- ...g-a-subfolder-out-into-a-new-repository.md | 2 +- .../using-git-rebase-on-the-command-line.md | 2 +- 50 files changed, 121 insertions(+), 121 deletions(-) diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md index c1d9b7f7df..9e22e31814 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md @@ -2,8 +2,8 @@ title: Managing subscriptions and notifications on GitHub intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.' redirect_from: - - /categories/76/articles/ - - /categories/notifications/ + - /categories/76/articles + - /categories/notifications - /categories/receiving-notifications-about-activity-on-github - /github/managing-subscriptions-and-notifications-on-github versions: diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index 4cf761d448..9d440d9c75 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -2,16 +2,16 @@ title: Viewing your subscriptions intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.' redirect_from: - - /articles/subscribing-to-conversations/ - - /articles/unsubscribing-from-conversations/ + - /articles/subscribing-to-conversations + - /articles/unsubscribing-from-conversations - /articles/subscribing-to-and-unsubscribing-from-notifications - /articles/listing-the-issues-and-pull-requests-youre-subscribed-to - - /articles/watching-repositories/ - - /articles/unwatching-repositories/ + - /articles/watching-repositories + - /articles/unwatching-repositories - /articles/watching-and-unwatching-repositories - /articles/watching-and-unwatching-releases-for-a-repository - /articles/watching-and-unwatching-team-discussions - - /articles/listing-watched-repositories/ + - /articles/listing-watched-repositories - /articles/listing-the-repositories-you-re-watching - /articles/listing-the-repositories-youre-watching - /github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index 53af16a5f5..24263811ac 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -2,7 +2,7 @@ title: About notifications intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.' redirect_from: - - /articles/notifications/ + - /articles/notifications - /articles/about-notifications - /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta - /github/managing-subscriptions-and-notifications-on-github/about-notifications diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index f6ed77fe33..4b11d385d7 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -3,16 +3,16 @@ title: Configuring notifications intro: 'Choose the type of activity on {% data variables.product.prodname_dotcom %} that you want to receive notifications for and how you want these updates delivered.' redirect_from: - /articles/about-web-notifications - - /format-of-notification-emails/ - - /articles/configuring-notification-emails/ - - /articles/about-notification-emails/ + - /format-of-notification-emails + - /articles/configuring-notification-emails + - /articles/about-notification-emails - /articles/about-email-notifications - /articles/accessing-your-notifications - - /articles/configuring-notification-delivery-methods/ - - /articles/managing-notification-delivery-methods/ - - /articles/managing-notification-emails-for-organizations/ + - /articles/configuring-notification-delivery-methods + - /articles/managing-notification-delivery-methods + - /articles/managing-notification-emails-for-organizations - /articles/choosing-the-delivery-method-for-your-notifications - - /articles/choosing-the-types-of-notifications-you-receive/ + - /articles/choosing-the-types-of-notifications-you-receive - /github/managing-subscriptions-and-notifications-on-github/configuring-notifications - /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications versions: diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md index 9a980a9489..66a0b98a87 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md @@ -2,7 +2,7 @@ title: Viewing and triaging notifications intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.' redirect_from: - - /articles/managing-notifications/ + - /articles/managing-notifications - /articles/managing-your-notifications - /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications versions: diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md index e711f972ef..7a6c7d46c8 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md @@ -2,8 +2,8 @@ title: About your profile intro: 'Your profile page tells people the story of your work through the repositories you''re interested in, the contributions you''ve made, and the conversations you''ve had.' redirect_from: - - /articles/viewing-your-feeds/ - - /articles/profile-pages/ + - /articles/viewing-your-feeds + - /articles/profile-pages - /articles/about-your-profile - /github/setting-up-and-managing-your-github-profile/about-your-profile - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 060afa3657..ad0820dc72 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -2,11 +2,11 @@ title: Personalizing your profile intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.' redirect_from: - - /articles/adding-a-bio-to-your-profile/ - - /articles/setting-your-profile-picture/ - - /articles/how-do-i-set-up-my-profile-picture/ - - /articles/gravatar-problems/ - - /articles/how-do-i-set-up-my-avatar/ + - /articles/adding-a-bio-to-your-profile + - /articles/setting-your-profile-picture + - /articles/how-do-i-set-up-my-profile-picture + - /articles/gravatar-problems + - /articles/how-do-i-set-up-my-avatar - /articles/personalizing-your-profile - /github/setting-up-and-managing-your-github-profile/personalizing-your-profile - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md index b6a0fa6432..236984b315 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md @@ -2,7 +2,7 @@ title: Pinning items to your profile intro: You can pin gists and repositories to your profile so other people can quickly see your best work. redirect_from: - - /articles/pinning-repositories-to-your-profile/ + - /articles/pinning-repositories-to-your-profile - /articles/pinning-items-to-your-profile - /github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md index c42ded9b20..9084cb9a07 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md @@ -2,7 +2,7 @@ title: Sending enterprise contributions to your GitHub.com profile intro: 'You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.' redirect_from: - - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index a183d24021..390e4d81e0 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -2,8 +2,8 @@ title: Viewing contributions on your profile intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.' redirect_from: - - /articles/viewing-contributions/ - - /articles/viewing-contributions-on-your-profile-page/ + - /articles/viewing-contributions + - /articles/viewing-contributions-on-your-profile-page - /articles/viewing-contributions-on-your-profile - /github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md index 32822ee3b9..26c50a8387 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md @@ -2,8 +2,8 @@ title: Managing access to your personal repositories intro: You can give people collaborator access to repositories owned by your personal account. redirect_from: - - /categories/101/articles/ - - /categories/managing-repository-collaborators/ + - /categories/101/articles + - /categories/managing-repository-collaborators - /articles/managing-access-to-your-personal-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 2e97a97343..caa381f9fe 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -2,8 +2,8 @@ title: Inviting collaborators to a personal repository intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.' redirect_from: - - /articles/how-do-i-add-a-collaborator/ - - /articles/adding-collaborators-to-a-personal-repository/ + - /articles/how-do-i-add-a-collaborator + - /articles/adding-collaborators-to-a-personal-repository - /articles/inviting-collaborators-to-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md index 3cfc5b62dd..627316136c 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md @@ -2,11 +2,11 @@ title: Removing a collaborator from a personal repository intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.' redirect_from: - - /articles/how-do-i-remove-a-collaborator/ - - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository/ - - /articles/removing-a-collaborator-from-a-private-repository/ - - /articles/deleting-a-private-fork-of-a-private-user-repository/ - - /articles/how-do-i-delete-a-fork-of-my-private-repository/ + - /articles/how-do-i-remove-a-collaborator + - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository + - /articles/removing-a-collaborator-from-a-private-repository + - /articles/deleting-a-private-fork-of-a-private-user-repository + - /articles/how-do-i-delete-a-fork-of-my-private-repository - /articles/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index 2c61cec169..0546453704 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -2,9 +2,9 @@ title: Removing yourself from a collaborator's repository intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.' redirect_from: - - /leave-a-collaborative-repo/ - - /leave-a-repo/ - - /articles/removing-yourself-from-a-collaborator-s-repo/ + - /leave-a-collaborative-repo + - /leave-a-repo + - /articles/removing-yourself-from-a-collaborator-s-repo - /articles/removing-yourself-from-a-collaborator-s-repository - /articles/removing-yourself-from-a-collaborators-repository - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md index 5db5961c8b..6f5986b82c 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md @@ -2,7 +2,7 @@ title: Managing email preferences intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.' redirect_from: - - /categories/managing-email-preferences/ + - /categories/managing-email-preferences - /articles/managing-email-preferences - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences versions: diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md index b7c3eaa701..e3a1cec0b9 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md @@ -2,8 +2,8 @@ title: Remembering your GitHub username or email intro: 'Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can''t remember your {% data variables.product.product_name %} user account name, you can try these methods for remembering it.' redirect_from: - - /articles/oh-noes-i-ve-forgotten-my-username-email/ - - /articles/oh-noes-i-ve-forgotten-my-username-or-email/ + - /articles/oh-noes-i-ve-forgotten-my-username-email + - /articles/oh-noes-i-ve-forgotten-my-username-or-email - /articles/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md index 27cd59c38b..338493bf2e 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md @@ -2,13 +2,13 @@ title: Setting your commit email address intro: 'You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.' redirect_from: - - /articles/keeping-your-email-address-private/ - - /articles/setting-your-commit-email-address-on-github/ - - /articles/about-commit-email-addresses/ - - /articles/git-email-settings/ - - /articles/setting-your-email-in-git/ - - /articles/set-your-user-name-email-and-github-token/ - - /articles/setting-your-commit-email-address-in-git/ + - /articles/keeping-your-email-address-private + - /articles/setting-your-commit-email-address-on-github + - /articles/about-commit-email-addresses + - /articles/git-email-settings + - /articles/setting-your-email-in-git + - /articles/set-your-user-name-email-and-github-token + - /articles/setting-your-commit-email-address-in-git - /articles/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md index 0eb7cae0e9..8ed0bcd91e 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md @@ -1,8 +1,8 @@ --- title: About your personal dashboard redirect_from: - - /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github/ - - /articles/opting-into-the-public-beta-for-a-new-dashboard/ + - /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github + - /articles/opting-into-the-public-beta-for-a-new-dashboard - /articles/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index 2567837344..f03142d93f 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -2,10 +2,10 @@ title: Changing your GitHub username intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.' redirect_from: - - /articles/how-to-change-your-username/ - - /articles/changing-your-github-user-name/ - - /articles/renaming-a-user/ - - /articles/what-happens-when-i-change-my-username/ + - /articles/how-to-change-your-username + - /articles/changing-your-github-user-name + - /articles/renaming-a-user + - /articles/what-happens-when-i-change-my-username - /articles/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md index da87d38dc8..7fececc39d 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md @@ -1,8 +1,8 @@ --- title: Converting a user into an organization redirect_from: - - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization/ - - /articles/explaining-the-account-transformation-warning/ + - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization + - /articles/explaining-the-account-transformation-warning - /articles/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md index fc6276d612..d75e89ba91 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md @@ -2,7 +2,7 @@ title: Deleting your user account intro: 'You can delete your {% data variables.product.product_name %} user account at any time.' redirect_from: - - /articles/deleting-a-user-account/ + - /articles/deleting-a-user-account - /articles/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index 6ba64d8d33..5869a719ec 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -2,8 +2,8 @@ title: Managing user account settings intro: 'You can change several settings for your personal account, including changing your username and deleting your account.' redirect_from: - - /categories/29/articles/ - - /categories/user-accounts/ + - /categories/29/articles + - /categories/user-accounts - /articles/managing-user-account-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings versions: diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md index 68438aea89..e41dec9831 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md @@ -2,7 +2,7 @@ title: Managing access to your user account's project boards intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.' redirect_from: - - /articles/managing-project-boards-in-your-repository-or-organization/ + - /articles/managing-project-boards-in-your-repository-or-organization - /articles/managing-access-to-your-user-account-s-project-boards - /articles/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md index 0e1db56667..57084beb98 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md @@ -2,8 +2,8 @@ title: Merging multiple user accounts intro: 'If you have separate accounts for work and personal use, you can merge the accounts.' redirect_from: - - /articles/can-i-merge-two-accounts/ - - /articles/keeping-work-and-personal-repositories-separate/ + - /articles/can-i-merge-two-accounts + - /articles/keeping-work-and-personal-repositories-separate - /articles/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md index a16f6c3bd0..06aab78e62 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md @@ -2,9 +2,9 @@ title: Accessing an organization intro: 'To access an organization that you''re a member of, you must sign in to your personal user account.' redirect_from: - - /articles/error-cannot-log-in-that-account-is-an-organization/ - - /articles/cannot-log-in-that-account-is-an-organization/ - - /articles/how-do-i-access-my-organization-account/ + - /articles/error-cannot-log-in-that-account-is-an-organization + - /articles/cannot-log-in-that-account-is-an-organization + - /articles/how-do-i-access-my-organization-account - /articles/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md index 1362c7db2e..0f06761832 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md @@ -2,7 +2,7 @@ title: Publicizing or hiding organization membership intro: 'If you''d like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.' redirect_from: - - /articles/publicizing-or-concealing-organization-membership/ + - /articles/publicizing-or-concealing-organization-membership - /articles/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md index 34c58d9443..c2db6f82ee 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md @@ -2,7 +2,7 @@ title: Removing yourself from an organization intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.' redirect_from: - - /articles/how-do-i-remove-myself-from-an-organization/ + - /articles/how-do-i-remove-myself-from-an-organization - /articles/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md index b84c363887..9571f2179e 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md @@ -2,8 +2,8 @@ title: Requesting organization approval for OAuth Apps intro: 'Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.' redirect_from: - - /articles/requesting-organization-approval-for-third-party-applications/ - - /articles/requesting-organization-approval-for-your-authorized-applications/ + - /articles/requesting-organization-approval-for-third-party-applications + - /articles/requesting-organization-approval-for-your-authorized-applications - /articles/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps diff --git a/content/authentication/index.md b/content/authentication/index.md index f2c78884e9..4e209b3382 100644 --- a/content/authentication/index.md +++ b/content/authentication/index.md @@ -2,17 +2,17 @@ title: Authentication intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.' redirect_from: - - /categories/56/articles/ - - /categories/ssh/ - - /mac-verify-ssh/ - - /ssh-issues/ - - /verify-ssh-redirect/ - - /win-verify-ssh/ - - /categories/92/articles/ - - /categories/gpg/ - - /categories/security/ + - /categories/56/articles + - /categories/ssh + - /mac-verify-ssh + - /ssh-issues + - /verify-ssh-redirect + - /win-verify-ssh + - /categories/92/articles + - /categories/gpg + - /categories/security - /categories/authenticating-to-github - - /github/authenticating-to-github/ + - /github/authenticating-to-github versions: fpt: '*' ghes: '*' diff --git a/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md b/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md index 7252e596e2..23e2375a3b 100644 --- a/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md +++ b/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md @@ -2,7 +2,7 @@ title: About anonymized URLs intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.' redirect_from: - - /articles/why-do-my-images-have-strange-urls/ + - /articles/why-do-my-images-have-strange-urls - /articles/about-anonymized-image-urls - /authenticating-to-github/about-anonymized-image-urls - /github/authenticating-to-github/about-anonymized-urls diff --git a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md index c23c0e6cc6..480901f678 100644 --- a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md +++ b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md @@ -2,10 +2,10 @@ title: About GitHub's IP addresses intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.' redirect_from: - - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist/ - - /categories/73/articles/ - - /categories/administration/ - - /articles/github-s-ip-addresses/ + - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist + - /categories/73/articles + - /categories/administration + - /articles/github-s-ip-addresses - /articles/about-github-s-ip-addresses - /articles/about-githubs-ip-addresses - /github/authenticating-to-github/about-githubs-ip-addresses diff --git a/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 021bb83cc6..ccb0b169ea 100644 --- a/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -2,8 +2,8 @@ title: Creating a personal access token intro: You should create a personal access token to use in place of a password with the command line or with the API. redirect_from: - - /articles/creating-an-oauth-token-for-command-line-use/ - - /articles/creating-an-access-token-for-command-line-use/ + - /articles/creating-an-oauth-token-for-command-line-use + - /articles/creating-an-access-token-for-command-line-use - /articles/creating-a-personal-access-token-for-the-command-line - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line - /github/authenticating-to-github/creating-a-personal-access-token diff --git a/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md index f76bfeb214..85eebfa495 100644 --- a/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md +++ b/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md @@ -2,7 +2,7 @@ title: Creating a strong password intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.' redirect_from: - - /articles/what-is-a-strong-password/ + - /articles/what-is-a-strong-password - /articles/creating-a-strong-password - /github/authenticating-to-github/creating-a-strong-password - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password diff --git a/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index cb442e4d69..035d69c803 100644 --- a/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -2,7 +2,7 @@ title: GitHub's SSH key fingerprints intro: Public key fingerprints can be used to validate a connection to a remote server. redirect_from: - - /articles/what-are-github-s-ssh-key-fingerprints/ + - /articles/what-are-github-s-ssh-key-fingerprints - /articles/github-s-ssh-key-fingerprints - /articles/githubs-ssh-key-fingerprints - /github/authenticating-to-github/githubs-ssh-key-fingerprints diff --git a/content/authentication/keeping-your-account-and-data-secure/index.md b/content/authentication/keeping-your-account-and-data-secure/index.md index 750844b4cf..9d1b48210b 100644 --- a/content/authentication/keeping-your-account-and-data-secure/index.md +++ b/content/authentication/keeping-your-account-and-data-secure/index.md @@ -3,7 +3,7 @@ title: Keeping your account and data secure intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.' redirect_from: - /articles/keeping-your-account-and-data-secure - - /github/authenticating-to-github/keeping-your-account-and-data-secure/ + - /github/authenticating-to-github/keeping-your-account-and-data-secure versions: fpt: '*' ghes: '*' diff --git a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 9056bc0961..385e8c165a 100644 --- a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -2,9 +2,9 @@ title: Removing sensitive data from a repository intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.' redirect_from: - - /remove-sensitive-data/ - - /removing-sensitive-data/ - - /articles/remove-sensitive-data/ + - /remove-sensitive-data + - /removing-sensitive-data + - /articles/remove-sensitive-data - /articles/removing-sensitive-data-from-a-repository - /github/authenticating-to-github/removing-sensitive-data-from-a-repository - /github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md index e19bb80294..4d40bff504 100644 --- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md +++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md @@ -2,8 +2,8 @@ title: Reviewing your SSH keys intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' redirect_from: - - /articles/keeping-your-application-access-tokens-safe/ - - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/ + - /articles/keeping-your-application-access-tokens-safe + - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe - /articles/reviewing-your-ssh-keys - /github/authenticating-to-github/reviewing-your-ssh-keys - /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys diff --git a/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index e1b972b591..8ca974ea4b 100644 --- a/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -2,8 +2,8 @@ title: Updating your GitHub access credentials intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.' redirect_from: - - /articles/rolling-your-credentials/ - - /articles/how-can-i-reset-my-password/ + - /articles/rolling-your-credentials + - /articles/how-can-i-reset-my-password - /articles/updating-your-github-access-credentials - /github/authenticating-to-github/updating-your-github-access-credentials - /github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md index 02b84cbdc0..a58a2a56b1 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md +++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md @@ -2,9 +2,9 @@ title: Accessing GitHub using two-factor authentication intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.' redirect_from: - - /articles/providing-your-2fa-security-code/ - - /articles/providing-your-2fa-authentication-code/ - - /articles/authenticating-to-github-using-fido-u2f-via-nfc/ + - /articles/providing-your-2fa-security-code + - /articles/providing-your-2fa-authentication-code + - /articles/authenticating-to-github-using-fido-u2f-via-nfc - /articles/accessing-github-using-two-factor-authentication - /github/authenticating-to-github/accessing-github-using-two-factor-authentication - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md index 8b8e9e7073..025b05a7ce 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -2,7 +2,7 @@ title: Changing two-factor authentication delivery methods for your mobile device intro: You can switch between receiving authentication codes through a text message or a mobile application. redirect_from: - - /articles/changing-two-factor-authentication-delivery-methods/ + - /articles/changing-two-factor-authentication-delivery-methods - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device - /github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index 74cb493413..d8d0f02c3a 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -2,11 +2,11 @@ title: Configuring two-factor authentication recovery methods intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials. redirect_from: - - /articles/downloading-your-two-factor-authentication-recovery-codes/ - - /articles/setting-a-fallback-authentication-number/ - - /articles/about-recover-accounts-elsewhere/ - - /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere/ - - /articles/generating-and-storing-an-account-recovery-token/ + - /articles/downloading-your-two-factor-authentication-recovery-codes + - /articles/setting-a-fallback-authentication-number + - /articles/about-recover-accounts-elsewhere + - /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere + - /articles/generating-and-storing-an-account-recovery-token - /articles/configuring-two-factor-authentication-recovery-methods - /github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 19166815e5..b1b364e782 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -2,9 +2,9 @@ title: Configuring two-factor authentication intro: You can choose among multiple options to add a second source of authentication to your account. redirect_from: - - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app/ - - /articles/configuring-two-factor-authentication-via-text-message/ - - /articles/configuring-two-factor-authentication-via-fido-u2f/ + - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app + - /articles/configuring-two-factor-authentication-via-text-message + - /articles/configuring-two-factor-authentication-via-fido-u2f - /articles/configuring-two-factor-authentication - /github/authenticating-to-github/configuring-two-factor-authentication - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md index 92b4805d9b..84d2bd82bf 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md +++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md @@ -2,10 +2,10 @@ title: Securing your account with two-factor authentication (2FA) intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.' redirect_from: - - /categories/84/articles/ - - /categories/two-factor-authentication-2fa/ + - /categories/84/articles + - /categories/two-factor-authentication-2fa - /articles/securing-your-account-with-two-factor-authentication-2fa - - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/ + - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa versions: fpt: '*' ghes: '*' diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 8956f5abd8..b734154e2b 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -2,8 +2,8 @@ title: Recovering your account if you lose your 2FA credentials intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.' redirect_from: - - /articles/recovering-your-account-if-you-lost-your-2fa-credentials/ - - /articles/authenticating-with-an-account-recovery-token/ + - /articles/recovering-your-account-if-you-lost-your-2fa-credentials + - /articles/authenticating-with-an-account-recovery-token - /articles/recovering-your-account-if-you-lose-your-2fa-credentials - /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials diff --git a/content/get-started/using-git/about-git-rebase.md b/content/get-started/using-git/about-git-rebase.md index 0fe4205bad..e6fc3b9603 100644 --- a/content/get-started/using-git/about-git-rebase.md +++ b/content/get-started/using-git/about-git-rebase.md @@ -1,7 +1,7 @@ --- title: About Git rebase redirect_from: - - /rebase/ + - /rebase - articles/interactive-rebase/ - /articles/about-git-rebase - /github/using-git/about-git-rebase diff --git a/content/get-started/using-git/about-git-subtree-merges.md b/content/get-started/using-git/about-git-subtree-merges.md index 1e415bca6c..d807a05e15 100644 --- a/content/get-started/using-git/about-git-subtree-merges.md +++ b/content/get-started/using-git/about-git-subtree-merges.md @@ -1,8 +1,8 @@ --- title: About Git subtree merges redirect_from: - - /articles/working-with-subtree-merge/ - - /subtree-merge/ + - /articles/working-with-subtree-merge + - /subtree-merge - /articles/about-git-subtree-merges - /github/using-git/about-git-subtree-merges - /github/getting-started-with-github/about-git-subtree-merges diff --git a/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/content/get-started/using-git/getting-changes-from-a-remote-repository.md index 209c0beb0e..63fa47a4cd 100644 --- a/content/get-started/using-git/getting-changes-from-a-remote-repository.md +++ b/content/get-started/using-git/getting-changes-from-a-remote-repository.md @@ -2,7 +2,7 @@ title: Getting changes from a remote repository intro: You can use common Git commands to access remote repositories. redirect_from: - - /articles/fetching-a-remote/ + - /articles/fetching-a-remote - /articles/getting-changes-from-a-remote-repository - /github/using-git/getting-changes-from-a-remote-repository - /github/getting-started-with-github/getting-changes-from-a-remote-repository diff --git a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md index 8303fb27d5..b5c8c33262 100644 --- a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md +++ b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md @@ -2,7 +2,7 @@ title: Pushing commits to a remote repository intro: Use `git push` to push commits made on your local branch to a remote repository. redirect_from: - - /articles/pushing-to-a-remote/ + - /articles/pushing-to-a-remote - /articles/pushing-commits-to-a-remote-repository - /github/using-git/pushing-commits-to-a-remote-repository - /github/getting-started-with-github/pushing-commits-to-a-remote-repository diff --git a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index f070c323c5..49eef30c38 100644 --- a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -1,7 +1,7 @@ --- title: Splitting a subfolder out into a new repository redirect_from: - - /articles/splitting-a-subpath-out-into-a-new-repository/ + - /articles/splitting-a-subpath-out-into-a-new-repository - /articles/splitting-a-subfolder-out-into-a-new-repository - /github/using-git/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository diff --git a/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/content/get-started/using-git/using-git-rebase-on-the-command-line.md index 793e4eaa92..95a87525e4 100644 --- a/content/get-started/using-git/using-git-rebase-on-the-command-line.md +++ b/content/get-started/using-git/using-git-rebase-on-the-command-line.md @@ -1,7 +1,7 @@ --- title: Using Git rebase on the command line redirect_from: - - /articles/using-git-rebase/ + - /articles/using-git-rebase - /articles/using-git-rebase-on-the-command-line - /github/using-git/using-git-rebase-on-the-command-line - /github/getting-started-with-github/using-git-rebase-on-the-command-line From 9d59f7dc8b2c241a10d180da188848e088194d61 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Fri, 10 Dec 2021 22:32:45 -0500 Subject: [PATCH 10/29] Lack of unique React keys (#23573) --- components/guides/ArticleCard.tsx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/components/guides/ArticleCard.tsx b/components/guides/ArticleCard.tsx index 7207f762c6..332953ba3a 100644 --- a/components/guides/ArticleCard.tsx +++ b/components/guides/ArticleCard.tsx @@ -19,9 +19,8 @@ export const ArticleCard = ({ card, typeLabel }: Props) => {
    {card.topics.map((topic) => { return ( -
  • +
    • -5 -Selecciona tu código de país y escribe el número de teléfono móvil, incluido el número de área. Cuando la información es correcta, haz clic en **Set fallback** (Establecer reserva). ![Establecer número de SMS de reserva](/assets/images/help/2fa/2fa-fallback-number.png) +3. Next to "Fallback SMS number", click **Add**. +![Add fallback SMS number button](/assets/images/help/2fa/add-fallback-sms-number-button.png) +4. Under "Fallback SMS number", click **Add fallback SMS number**. +![Add fallback SMS number text](/assets/images/help/2fa/add_fallback_sms_number_text.png) +5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**. + ![Set fallback SMS number](/assets/images/help/2fa/2fa-fallback-number.png) -Después de la configuración, el dispositivo de copia de seguridad recibirá un SMS de confirmación. +After setup, the backup device will receive a confirmation SMS. {% endif %} -## Leer más +## Further reading -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" -- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +- "[About two-factor authentication](/articles/about-two-factor-authentication)" +- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" +- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)" +- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index b81ee94e31..b1b364e782 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -1,10 +1,10 @@ --- -title: Configurar la autenticación de dos factores -intro: Puedes elegir entre varias opciones para añadir una segunda fuente de autenticación a tu cuenta. +title: Configuring two-factor authentication +intro: You can choose among multiple options to add a second source of authentication to your account. redirect_from: - - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app/ - - /articles/configuring-two-factor-authentication-via-text-message/ - - /articles/configuring-two-factor-authentication-via-fido-u2f/ + - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app + - /articles/configuring-two-factor-authentication-via-text-message + - /articles/configuring-two-factor-authentication-via-fido-u2f - /articles/configuring-two-factor-authentication - /github/authenticating-to-github/configuring-two-factor-authentication - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication @@ -14,119 +14,128 @@ versions: ghec: '*' topics: - 2FA -shortTitle: Configurar la 2FA +shortTitle: Configure 2FA --- +You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key. -Puedes configurar la autenticación de dos factores usando una app móvil {% ifversion fpt or ghec %} o mediante un mensaje de texto{% endif %}. También puedes agregar una clave de seguridad. - -Recomendamos encarecidamente el uso de una contraseña única basada en el tiempo (TOTP) para configurar 2FA.{% ifversion fpt or ghec %}Las aplicaciones TOTP son más confiables que los SMS, especialmente para las ubicaciones fuera de los EE. UU.{% endif %}Las apps TOTP respaldan las copias de seguridad de los códigos de autenticación en la nube y pueden restaurarse si pierdes acceso a tu dispositivo. +We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device. {% warning %} -**Advertencia:** -- Si eres un miembro{% ifversion fpt or ghec %}, gerente de facturación{% endif %} o colaborador externo de un repositorio privado de una organización que requiere autenticación de dos factores, debes salir de la organización antes de que puedas inhabilitar 2FA en {% data variables.product.product_location %}. -- Si inhabilitas 2FA, automáticamente perderás acceso a la organización y a cualquier bifurcación privada que tengas de los repositorios privados de la organización. Para volver a obtener acceso a la organización y a tus bifurcaciones, habilita nuevamente la autenticación de dos factores y comunícate con un propietario de la organización. +**Warning:** +- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}. +- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner. {% endwarning %} {% ifversion fpt or ghec %} -Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, no podrás configurar la 2FA para tu cuenta de {% data variables.product.prodname_managed_user %}. La 2FA debe configurarse mediante tu proveedor de identidad. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. {% endif %} -## Configurar la autenticación de dos factores mediante una app móvil TOTP +## Configuring two-factor authentication using a TOTP mobile app -Una aplicación de contraseña única basada en el tiempo (TOTP) genera automáticamente un código de autenticación que cambia después de un cierto período de tiempo. Recomendamos usar apps TOTP basadas en la nube como: +A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as: - [1Password](https://support.1password.com/one-time-passwords/) - [Authy](https://authy.com/guides/github/) - [LastPass Authenticator](https://lastpass.com/auth/) -- [Autenticador de Microsoft](https://www.microsoft.com/en-us/account/authenticator/) +- [Microsoft Authenticator](https://www.microsoft.com/en-us/account/authenticator/) {% tip %} -**Sugerencia**: Para configurar la autenticación mediante TOTP en múltiples dispositivos, durante la configuración, escanea el código QR usando todos los dispositivos al mismo tiempo. Si 2FA ya está habilitado y deseas agregar otro dispositivo, debes volver a configurar 2FA desde tus parámetros de seguridad. +**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings. {% endtip %} -1. Descargar una app TOTP. +1. Download a TOTP app. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} {%- ifversion fpt or ghes > 3.1 %} -5. Debajo de "Autenticación bifactorial", selecciona **Configurar utilizando una app** y haz clic en **Continuar**. -6. Debajo de "Verificación de autenticación", realiza alguan de las siguientes acciones: - - Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}. - - Si no puedes escanear el código QR, haz clic en **ingresa este código de texto** para ver un código que puedas ingresar manualmente en tu app de TOTP en su lugar. ![Haz clic para ingresar este código](/assets/images/help/2fa/2fa_wizard_app_click_code.png) -7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. En {% data variables.product.product_name %}, teclea el código en el campo debajo de "Ingresa el código de seis dígitos de la aplicación". Si tus códigos de recuperación no se muestran automáticamente, haz clic en **Continuar**. ![Campo para ingresar código de TOTP](/assets/images/help/2fa/2fa_wizard_app_enter_code.png) +5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**. +6. Under "Authentication verification", do one of the following: + - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}. + - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead. + ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png) +7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**. +![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png) {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} {%- else %} -5. En la página de autenticación de dos factores, haz clic en **Set up using an app** (Configurar mediante una app). -6. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso. - - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar). - - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir). - - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) -7. Después de guardar tu código de recuperación de dos factores, haz clic en **Next** (Siguiente). -8. En la página de autenticación de dos factores, realiza una de las siguientes opciones: - - Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}. - - Si no puedes escanear el código QR, haz clic en **enter this text code** (escribir este código de texto) para ver un código que puedas copiar e ingresar manualmente en {% data variables.product.product_name %}. ![Haz clic para ingresar este código](/assets/images/help/2fa/totp-click-enter-code.png) -9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. En {% data variables.product.product_name %}, en la página 2FA, escribe el código y haz clic en **Enable** (Habilitar). ![Campo TOTP Enable (Habilitar TOTP)](/assets/images/help/2fa/totp-enter-code.png) +5. On the Two-factor authentication page, click **Set up using an app**. +6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access. + - To save your recovery codes on your device, click **Download**. + - To save a hard copy of your recovery codes, click **Print**. + - To copy your recovery codes for storage in a password manager, click **Copy**. + ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) +7. After saving your two-factor recovery codes, click **Next**. +8. On the Two-factor authentication page, do one of the following: + - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}. + - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead. + ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png) +9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**. + ![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png) {%- endif %} {% data reusables.two_fa.test_2fa_immediately %} {% ifversion fpt or ghec %} -## Configurar la autenticación de dos factores mediante mensajes de texto +## Configuring two-factor authentication using text messages -Si no puedes habilitar la autenticación mediante una app móvil TOTP, puedes autenticar mediante mensajes SMS. También puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta. +If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account. -Antes de usar este método, asegúrate de que puedes recibir mensajes de texto. Es posible que se apliquen tarifas de protador. +Before using this method, be sure that you can receive text messages. Carrier rates may apply. {% warning %} -**Advertencia:** **Recomendamos enérgicamente** el uso de una aplicación TOTP para la autenticación de dos factores en lugar de SMS. {% data variables.product.product_name %} no admite el envío de mensajes SMS a teléfonos en todos los países. Antes de configurar la autenticación a través de mensaje de texto, revisa la lista de países donde {% data variables.product.product_name %} respalda la autenticación mediante SMS. Para obtener más información, consulta "[Países donde es compatible la autenticación SMS](/articles/countries-where-sms-authentication-is-supported)". +**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)". {% endwarning %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} -4. Debajo de la "Autenticación bifactorial", selecciona **Configurar utilizando SMS** y haz clic en **Continuar**. -5. Debajo de "Verificación de autenticación", selecciona el código de tu país y teclea tu número de teléfono móvil, incluyendo el código de área. Cuando la información es correcta, haz clic en **Send authentication code** (Enviar código de autenticación). +4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**. +5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**. - ![Pantalla 2FA SMS](/assets/images/help/2fa/2fa_wizard_sms_send.png) + ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png) -6. Recibirás un mensaje de texto con un código de seguridad. En {% data variables.product.product_name %}, teclea el código en el campo debajo de "Ingresa el código de seis dígitos que se envió a tu teléfono" y haz clic en **Continuar**. +6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**. - ![Campo 2FA SMS continue (Continuación de 2FA SMS)](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png) + ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png) {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} {% data reusables.two_fa.test_2fa_immediately %} {% endif %} -## Configurar la autenticación de dos factores mediante una clave de seguridad +## Configuring two-factor authentication using a security key {% data reusables.two_fa.after-2fa-add-security-key %} -En muchos dispositivos y buscadores, puedes utilizar una llave de seguridad física por USB o NFC. Algunos buscadores utilizan un lector de huella digital, reconocimiento facial o contraseña/NIP en tu dispositivo a modo de llave de seguridad. +On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key. -La autenticación con una clave de seguridad es *secundaria* para la autenticación con una aplicación TOTP{% ifversion fpt or ghec %} o un mensaje de texto{% endif %}. Si pierdes tu llave de seguridad, aún podrás utilizar tu código de teléfono para ingresar. +Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in. -1. Ya debes tener configurado 2FA mediante una app móvil TOTP{% ifversion fpt or ghec %} o mediante SMS{% endif %}. -2. Asegúrate de que tengas una llave de seguridad compatible con WebAuthn insertada en tu computadora. +1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}. +2. Ensure that you have a WebAuthn compatible security key inserted into your computer. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} -5. Al lado de "Security keys" (Claves de seguridad), haz clic en **Add** (Agregar). ![Agrega la opción de las claves de seguridad](/assets/images/help/2fa/add-security-keys-option.png) -6. En "Security keys" (Claves de seguridad), haz clic en **Register new security key** (Registrar clave de seguridad nueva). ![Registrar una nueva clave de seguridad](/assets/images/help/2fa/security-key-register.png) -7. Escribe un sobrenombre para la clave de seguridad, luego haz clic en **Add** (Agregar). ![Porporcionar un sobrenombre para una clave de seguridad](/assets/images/help/2fa/security-key-nickname.png) -8. Activa tu clave de seguridad, seguida por la documentación de tu clave de seguridad.![Solicitar una clave de seguridad](/assets/images/help/2fa/security-key-prompt.png) -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) +5. Next to "Security keys", click **Add**. + ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png) +6. Under "Security keys", click **Register new security key**. + ![Registering a new security key](/assets/images/help/2fa/security-key-register.png) +7. Type a nickname for the security key, then click **Add**. + ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png) +8. Activate your security key, following your security key's documentation. + ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png) +9. Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." + ![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png) {% data reusables.two_fa.test_2fa_immediately %} -## Leer más +## Further reading -- "[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)" -- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" -- "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" -- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" +- "[About two-factor authentication](/articles/about-two-factor-authentication)" +- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)" +- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md index c0a692fc04..84d2bd82bf 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md @@ -1,11 +1,11 @@ --- -title: Asegurar tu cuenta con autenticación de dos factores (2FA) +title: Securing your account with two-factor authentication (2FA) intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.' redirect_from: - - /categories/84/articles/ - - /categories/two-factor-authentication-2fa/ + - /categories/84/articles + - /categories/two-factor-authentication-2fa - /articles/securing-your-account-with-two-factor-authentication-2fa - - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/ + - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa versions: fpt: '*' ghes: '*' @@ -21,6 +21,6 @@ children: - /changing-two-factor-authentication-delivery-methods-for-your-mobile-device - /countries-where-sms-authentication-is-supported - /disabling-two-factor-authentication-for-your-personal-account -shortTitle: Asegurar tu cuenta con 2FA +shortTitle: Secure your account with 2FA --- diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 8956f5abd8..b734154e2b 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -2,8 +2,8 @@ title: Recovering your account if you lose your 2FA credentials intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.' redirect_from: - - /articles/recovering-your-account-if-you-lost-your-2fa-credentials/ - - /articles/authenticating-with-an-account-recovery-token/ + - /articles/recovering-your-account-if-you-lost-your-2fa-credentials + - /articles/authenticating-with-an-account-recovery-token - /articles/recovering-your-account-if-you-lose-your-2fa-credentials - /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md index f69f6033c9..9041475e84 100644 --- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md +++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md @@ -1,10 +1,10 @@ --- title: 'Error: Unknown key type' -intro: Este error significa que el tipo de llave SSH que utilizaste no se reconoció o no es compatible con tu cliente SSH. +intro: 'This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client. ' versions: fpt: '*' ghes: '>=3.2' - ghae: next + ghae: '*' ghec: '*' topics: - SSH @@ -12,28 +12,27 @@ redirect_from: - /github/authenticating-to-github/error-unknown-key-type - /github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type --- +## About the `unknown key type` error -## Acerca del error `unknown key type` +When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client. -Cuando generas una llave SSH nueva, podrías recibir un error de `unknown key type` si tu cliente SSH no es compatible con el tipo de llave que especificaste.{% mac %}Para resolver este problema en macOS, puedes actualizar tu cliente SSH o instalar un cliente SSH nuevo. +## Prerequisites -## Prerrequisitos +You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation. -Debes tener Homebrew instalado. Para obtener más información, consulta la [guía de instalación](https://docs.brew.sh/Installation) en la documentación de Homebrew. - -## Resolver el problema +## Solving the issue {% warning %} -**Advertencia:** Si instalas OpenSSH, tu computadora no podrá recuperar contraseñas que se almacenen en la keychain de Apple. Necesitarás ingresar tu contraseña o interactuar con tu llave de seguridad de hardware cada vez que te autentiques con SSH en {% data variables.product.prodname_dotcom %} u otro servicio web. +**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service. -Si eliminas a OpenSSh, las paráfrasis que se almacenan en tu keychain se podrán recuperar nuevamente. Puedes eliminar a OpenSSH si ingresas el comando `brew uninstall openssh` en la terminal. +If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal. {% endwarning %} -1. Abre Terminal. -2. Ingresa el comando `brew install openssh`. -3. Sal y vuelve a abrir la terminal. -4. Intenta llevar a cabo el procedimiento para generar una llave SSH nuevamente. Para obtener más información, consulta "[Generar una nueva llave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." +1. Open Terminal. +2. Enter the command `brew install openssh`. +3. Quit and relaunch Terminal. +4. Try the procedure for generating a new SSH key again. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." -{% endmac %}{% linux %}Para resolver este problema en Linux, utiliza el administrador de paquetes para tu distribución de Linux para instalar una versión nueva de OpenSSH o compila una versión nueva desde el orígen. Si instalas una versión diferente de OpenSSH, la capacidad de otras aplicaciones para autenticarse por SSH puede verse afectada. Para obtener más información, revisa los documentos para tu distribución.{% endlinux %} +{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md index 58d20b070d..6a8a95fbad 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md @@ -73,6 +73,12 @@ The following example timeline demonstrates how active committer count for {% da | August 15 | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | _49 + 10_
    **59** | | August 16 | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | _49 - 29_
    **20** | +{% note %} + +**Note:** A user will be flagged as active when their commits are pushed to any branch of a repository, even if the commits were authored more than 90 days ago. + +{% endnote %} + ## Getting the most out of {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.getting-the-most-from-your-license %} diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index fddb22eb95..6d51a952ce 100644 --- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -41,27 +41,27 @@ To set up {% data variables.product.prodname_vss_ghe %}, members of your team mu One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)." -1. An [enterprise owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) must create at least one organization in your enterprise on {% data variables.product.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." +1. An enterprise owner must create at least one organization in your enterprise on {% data variables.product.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -1. The [subscription admin](#roles-for-visual-studio-subscriptions-with-github-enterprise) must assign a license for {% data variables.product.prodname_vs %} to a [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs. +1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs. -1. Optionally, if the [subscription admin](#roles-for-visual-studio-subscriptions-with-github-enterprise) assigned licenses to [subscribers](#roles-for-visual-studio-subscriptions-with-github-enterprise) in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the [subscription admin](#roles-for-visual-studio-subscriptions-with-github-enterprise) can move the [subscribers](#roles-for-visual-studio-subscriptions-with-github-enterprise) to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs. +1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs. -1. If the [subscription admin](#roles-for-visual-studio-subscriptions-with-github-enterprise) has not disabled email notifications, the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs. +1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs. -1. An [organization owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) must invite the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) to the organization on {% data variables.product.product_location %} from step 1. The [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) joins the organization, the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) becomes an [enterprise member](#roles-for-visual-studio-subscriptions-with-github-enterprise). For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." +1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." {% tip %} **Tips**: - - While not required, we recommend that the [organization owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) sends an invitation to the same email address used for the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise)'s User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise)'s UPN, you can ensure that another [enterprise member](#roles-for-visual-studio-subscriptions-with-github-enterprise) does not claim the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise)'s license. - - If the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the [subscriber](#roles-for-visual-studio-subscriptions-with-github-enterprise) add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)." - - If the [organization owner](#roles-for-visual-studio-subscriptions-with-github-enterprise) must invite a large number of [subscribers](#roles-for-visual-studio-subscriptions-with-github-enterprise), a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. + - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. + - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)." + - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. {% endtip %} -After {% data variables.product.prodname_vss_ghe %} is set up for [subscribers](#roles-for-visual-studio-subscriptions-with-github-enterprise) on your team, [enterprise owners](#roles-for-visual-studio-subscriptions-with-github-enterprise) can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." +After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." ## Further reading diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md index be3d1c507d..fb05626d65 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md @@ -27,7 +27,7 @@ topics: There are two main ways to use {% data variables.product.prodname_codeql %} analysis for {% data variables.product.prodname_code_scanning %}: - Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)." -- Run the {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}CLI directly {% elsif ghes = 3.0 %}CLI or runner {% else %}runner {% endif %} in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." +- Run the {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %}CLI directly {% elsif ghes = 3.0 %}CLI or runner {% else %}runner {% endif %} in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." ## About {% data variables.product.prodname_codeql %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index c51ed6834e..88ca60761c 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -32,7 +32,7 @@ shortTitle: Configure code scanning ## About {% data variables.product.prodname_code_scanning %} configuration You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." {%- else %} "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." @@ -86,16 +86,16 @@ If you scan pull requests, then the results appear as alerts in a pull request c Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Defining the severities causing pull request check failure -By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)." +By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1 or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1 or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 1. Under "Code scanning", to the right of "Check Failure", use the drop-down menu to select the level of severity you would like to cause a pull request check failure. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Check failure setting](/assets/images/help/repository/code-scanning-check-failure-setting.png) {% else %} ![Check failure setting](/assets/images/help/repository/code-scanning-check-failure-setting-ghae.png) @@ -176,7 +176,7 @@ jobs: {% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Specifying the location for {% data variables.product.prodname_codeql %} databases In general, you do not need to worry about where the {% data variables.product.prodname_codeql_workflow %} places {% data variables.product.prodname_codeql %} databases since later steps will automatically find databases created by previous steps. However, if you are writing a custom workflow step that requires the {% data variables.product.prodname_codeql %} database to be in a specific disk location, for example to upload the database as a workflow artifact, you can specify that location using the `db-location` parameter under the `init` action. @@ -238,7 +238,7 @@ Alternatively, you can install Python dependencies manually on any operating sys ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: security-events: write actions: read{% endif %} @@ -269,7 +269,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Configuring a category for the analysis Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file. diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md index a54f0f60be..42c5f3df55 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md @@ -48,7 +48,8 @@ If your workflow uses a `language` matrix, `autobuild` attempts to build each of {% note %} -{% ifversion ghae %}**Note**: For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." +{% ifversion ghae %} +**Note**: {% data reusables.actions.self-hosted-runners-software %} {% else %} **Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 2b8052ebfc..3d209f2f24 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -37,7 +37,7 @@ By default, {% data variables.product.prodname_code_scanning %} analyzes your co ## 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{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem. +Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem. ![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) @@ -49,9 +49,9 @@ When {% data variables.product.prodname_code_scanning %} reports data-flow alert Alert severity levels may be `Error`, `Warning`, or `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### About security severity levels {% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. @@ -90,11 +90,11 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} {% data reusables.code-scanning.explore-alert %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -104,7 +104,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% note %} **Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. @@ -186,11 +186,11 @@ Anyone with write permission for a repository can fix an alert by committing a c If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed. -You can use{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. +You can use{% ifversion fpt or ghes > 3.1 or ghae or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -226,9 +226,9 @@ To dismiss or delete alerts: ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png) - Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. + Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -236,7 +236,7 @@ To dismiss or delete alerts: 1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index dac30adc85..a5315a96bc 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -1,7 +1,7 @@ --- -title: Ejecutarel escaneo de código de CodeQL en un contenedor -shortTitle: '{% data variables.product.prodname_code_scanning_capc %} en un contenedor' -intro: 'Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en un contenedor si garantizas que todos los procesos se ejecutan en el mismo contenedor.' +title: Running CodeQL code scanning in a container +shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container' +intro: 'You can run {% data variables.product.prodname_code_scanning %} in a container by ensuring that all processes run in the same container.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container @@ -22,33 +22,32 @@ topics: - Containers - Java --- - {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.deprecation-codeql-runner %} -## Acerca del {% data variables.product.prodname_code_scanning %} con una compilación en contenedor +## About {% data variables.product.prodname_code_scanning %} with a containerized build -Si estás configurando el {% data variables.product.prodname_code_scanning %} para un lenguaje compilado, y estás compilando el código en un ambiente contenido, el análisis podría fallar con el mensaje de error "No source code was seen during the build". Esto indica que {% data variables.product.prodname_codeql %} no fue capaz de monitorear tu código mientras se compilaba. +If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled. -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que compilaste tu código. Esto aplica tanto si estás utilizando el {% data variables.product.prodname_codeql_cli %}, el {% data variables.product.prodname_codeql_runner %} o las {% data variables.product.prodname_actions %}. Para obtener más información sobre el {% data variables.product.prodname_codeql_cli %} o el {% data variables.product.prodname_codeql_runner %}, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)" o la sección "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)". Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)". +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)." {% else %} -Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que compilaste tu código. Esto aplica ya sea que estés utilizando el {% data variables.product.prodname_codeql_runner %} o {% data variables.product.prodname_actions %}. Para encontrar más información sobre el {% data variables.product.prodname_codeql_runner %}, consulta la sección "[ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)". Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)". +You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)." {% endif %} -## Dependencias +## Dependencies -Es posible que tengas alguna dificultad para ejecutar el {% data variables.product.prodname_code_scanning %} si el contenedor que estás utilizando carece de ciertas dependencias (Por ejemplo, Git debe instalarse y agregarse a la variable PATH). Si te encuentras con algún problema en las dependencias, revisa la lista de software que habitualmente se incluye en los ambientes virtuales de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta los archivos `readme` específicos de la versión en estas ubicaciones: +You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux * macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win -## Ejemplo de flujo de trabajo +## Example workflow -Este flujo de trabajo de muestra utiliza {% data variables.product.prodname_actions %} para ejecutar un análisis de {% data variables.product.prodname_codeql %} en un ambiente contenido. El valor de `container.image` identifica el contenedor que se debe utilizar. En este ejemplo, se le llama a la imagen `codeql-container`, con una etiqueta de `f0f91db`. 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#jobsjob_idcontainer)". +This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)." ``` yaml name: "{% data variables.product.prodname_codeql %}" @@ -64,7 +63,7 @@ on: jobs: analyze: name: Analyze - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: security-events: write actions: read{% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 93999b69a9..49df6f9929 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -47,7 +47,7 @@ Enterprise owners, organization and repository administrators can add self-hoste {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} +1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository. @@ -93,7 +93,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) @@ -135,7 +135,7 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md index 9a11aa8815..c1ea916c94 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md @@ -1,13 +1,13 @@ --- title: Tracking code scanning alerts in issues using task lists shortTitle: Track alerts in issues -intro: 'You can add code scanning alerts to issues using task lists. This makes it easy to create a plan for development work that includes fixing alerts.' +intro: You can add code scanning alerts to issues using task lists. This makes it easy to create a plan for development work that includes fixing alerts. product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.' versions: fpt: '*' ghes: '> 3.3' - ghae: "issue-5036" + ghae: issue-5036 type: how_to topics: - Advanced Security @@ -62,7 +62,7 @@ The status of the tracked alert won't change if you change the checkbox state of {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes or ghae-next %} +{% ifversion fpt or ghes or ghae %} {% data reusables.code-scanning.explore-alert %} 1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." {% endif %} @@ -79,4 +79,4 @@ The status of the tracked alert won't change if you change the checkbox state of {% endwarning %} ![New tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-new-tracking-issue.png) -3. Click **Submit new issue**. \ No newline at end of file +3. Click **Submit new issue**. diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index c185d25ea2..8b4a6464af 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -49,11 +49,11 @@ For all configurations of {% data variables.product.prodname_code_scanning %}, t ### {% data variables.product.prodname_code_scanning_capc %} results check failures -If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, `critical`, or `high`,{% endif %} the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds. +If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, `critical`, or `high`,{% endif %} the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds. ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". +{% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1 or ghae or ghec %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". {% endif %} ### Other {% data variables.product.prodname_code_scanning %} checks diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 96dec45cdf..bf886eac2f 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -65,7 +65,7 @@ If an automatic build of code for a compiled language within your project fails, ```yaml jobs: - analyze:{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + analyze:{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: security-events: write actions: read{% endif %} @@ -123,7 +123,7 @@ If your workflow fails with an error `No source code was seen during the build` For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Lines of code scanned are lower than expected For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons: diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 0d0b534415..0f67facbfb 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -1,6 +1,6 @@ --- -title: Visualizar las bitácoras del escaneo de código -intro: 'Puedes ver la salida que se generó durante el análisis del {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_location %}.' +title: Viewing code scanning logs +intro: 'You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.product.product_location %}.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository.' miniTocMaxHeadingLevel: 4 @@ -13,70 +13,70 @@ versions: ghec: '*' topics: - Security -shortTitle: Visualizar las bitácoras del escaneo de código +shortTitle: View code scanning logs --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -## Acerca de tu configuración del {% data variables.product.prodname_code_scanning %} +## About your {% data variables.product.prodname_code_scanning %} setup -Puedes utilizar diversas herramientas para configurar el {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)". +You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)." -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -La bitácora y la información diagnóstica que tengas disponible dependerá del método que utilices para el {% data variables.product.prodname_code_scanning %} en tu repositorio. Puedes verificar el tipo de {% data variables.product.prodname_code_scanning %} que estás utilizando en la pestaña de **Seguridad** de tu repositorio si utilizas el menú desplegable de **Herramienta** en la lista de alertas. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -## Acerca del análisis y la información de diagnóstico +## About analysis and diagnostic information -Puedes ver la información de análisis y diagnóstico para la jecución del {% data variables.product.prodname_code_scanning %} utilizando el análisis de {% data variables.product.prodname_codeql %} en {% data variables.product.prodname_dotcom %}. +You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}. -La información de **Análisis** se muestra para los análisis más recientes en un encabezado en la parte superior de la lista de alertas. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +**Analysis** information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -Se muestra información de **Diagnóstico** en las bitácoras del flujo de trabajo de la acción, la cual consiste en un resumen de métricas y diagnóstico de extractor. Para obtener más información sobre cómo acceder a las bitácoras del {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_dotcom %}, consulta la sección "[Visualizar la salida de registros del {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" a continuación. +**Diagnostic** information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "[Viewing the logging output from {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" below. -Si estás utilizando el {% data variables.product.prodname_codeql_cli %} fuera de {% data variables.product.prodname_dotcom %}, verás la información de diagnóstico en la salida que se generó durante el análisis de la base de datos. Esta información también se incluye en el archivo de resultados SARIF que cargaste en {% data variables.product.prodname_dotcom %} con los resultados del {% data variables.product.prodname_code_scanning %}. +If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results. -Para obtener más información sobre el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)". +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." -### Acerca de las métricas de resumen +### About summary metrics {% data reusables.code-scanning.summary-metrics %} -### Acerca del diagnóstico de extración del código fuente de {% data variables.product.prodname_codeql %} +### About {% data variables.product.prodname_codeql %} source code extraction diagnostics {% data reusables.code-scanning.extractor-diagnostics %} {% endif %} -## Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} +## Viewing the logging output from {% data variables.product.prodname_code_scanning %} -Esta sección aplica a la ejecución del {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_actions %}(de {% data variables.product.prodname_codeql %} o de terceros). +This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party). -Después de configurar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones mientras se ejecutan. +After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. {% data reusables.repositories.actions-tab %} - Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. El texto de la entrada es el título que le diste a tu mensaje de confirmación. + You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. - ![Lista de acciones que muestran el flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) -1. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. +1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. -2. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**. +2. Click the job name on the left. For example, **Analyze (LANGUAGE)**. - ![Registro de salida del flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) -1. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan. +1. Review the logging output from the actions in this workflow as they run. -1. Una vez que todos los jobs se completen, puedes ver los detalles de cualquier alerta del {% data variables.product.prodname_code_scanning %} que se hayan identificado. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." {% note %} -**Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}. +**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. {% ifversion fpt or ghes > 3.1 or ghae or ghec %} - ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} - ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endif %} {% endnote %} diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index dd455f1b35..7d5a652b49 100644 --- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -34,10 +34,10 @@ To upload a SARIF file from a third-party static code analysis engine, you'll ne If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below. {% endif %} @@ -101,7 +101,7 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `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`. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +| `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`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %} | `properties.problem.severity` | **Recommended.** A string that indicates the level of severity of any alerts generated by a non-security query. This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `problem.severity`, and highest `precision` are shown first. Can be one of: `error`, `warning`, or `recommendation`. | `properties.security-severity` | **Recommended.** A score that indicates the level of severity, between 0.0 and 10.0, for security queries (`@tags` includes `security`). This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `security-severity`, and highest `precision` are shown first. {% data variables.product.prodname_code_scanning_capc %} translates numerical scores as follows: over 9.0 is `critical`, 7.0 to 8.9 is `high`, 4.0 to 6.9 is `medium` and 3.9 or less is `low`. {% endif %} @@ -141,7 +141,7 @@ A location within a programming artifact, such as a file in the repository or a | `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. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### `runAutomationDetails` object The `runAutomationDetails` object contains information that specifies the identity of a run. @@ -245,7 +245,7 @@ This SARIF output file has example values to show the minimum required propertie This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md index 96fc77dae0..f9dbd860e6 100644 --- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md +++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md @@ -36,10 +36,10 @@ topics: You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)." -You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use: +You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use: - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis. -- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). {% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). {% ifversion fpt or ghes > 3.0 or ghae or ghec %} - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% endif %} - The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"). - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"). @@ -80,7 +80,7 @@ on: jobs: build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: security-events: write{% endif %} steps: @@ -114,7 +114,7 @@ on: jobs: build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: security-events: write{% endif %} steps: @@ -135,7 +135,7 @@ jobs: ## Further reading - "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" -- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- ifversion fpt or ghes > 3.0 or ghae-next %} +- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- ifversion fpt or ghes > 3.0 or ghae %} - "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %} - "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %} - "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)" diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 6e861522f8..c8ad424e59 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -32,7 +32,7 @@ redirect_from: {% data reusables.code-scanning.codeql-context-for-actions-and-third-party-tools %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% data reusables.code-scanning.codeql-cli-context-for-third-party-tools %} diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 8d71a5fd2e..fba109bb62 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.1' - ghae: next + ghae: '*' ghec: '*' type: how_to topics: @@ -277,7 +277,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ ``` {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Example CI configuration for {% data variables.product.prodname_codeql %} analysis @@ -331,7 +331,7 @@ If you want to upload more than one set of results to the {% data variables.prod ### Alternative if your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} -{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} If your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} autobuild and you cannot specify a command line for the build, you can use indirect build tracing to create {% data variables.product.prodname_codeql %} databases for compiled languages. For more information, see [Using indirect build tracing](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) in the documentation for the {% data variables.product.prodname_codeql_cli %}. diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md index 6c8749f755..1099495b71 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md @@ -7,7 +7,7 @@ miniTocMaxHeadingLevel: 3 versions: fpt: '*' ghes: '>=3.1' - ghae: next + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index ae05187d14..f6f88a8066 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -1,12 +1,12 @@ --- -title: Migrarse del ejecutor de CodeQL al CLI de CodeQL -shortTitle: Migrarse desde el ejecutor de CodeQL -intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para completar las mismas tareas que hacías con el {% data variables.product.prodname_codeql_runner %}.' +title: Migrating from the CodeQL runner to CodeQL CLI +shortTitle: Migrating from the CodeQL runner +intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to complete the same tasks as with the {% data variables.product.prodname_codeql_runner %}.' product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' ghes: '>=3.1' - ghae: next + ghae: '*' ghec: '*' topics: - Advanced Security @@ -14,45 +14,46 @@ topics: - CodeQL --- -# Migrarse del {% data variables.product.prodname_codeql_runner %} al {% data variables.product.prodname_codeql_cli %} +# Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %} -El {% data variables.product.prodname_codeql_runner %} se va a obsoletizar. Puedes utilizar la versión 2.6.2 del {% data variables.product.prodname_codeql_cli %} y superiores. Este documento describe cómo migrar flujos de trabajo comunes desde el {% data variables.product.prodname_codeql_runner %} hacia el {% data variables.product.prodname_codeql_cli %}. +The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead. +This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}. -## Instalación +## Installation -Descarga el **paquete de {% data variables.product.prodname_codeql %}** del [repositorio `github/codeql-action`](https://github.com/github/codeql-action/releases). Este paquete contiene al {% data variables.product.prodname_codeql_cli %} y las consultas estándar y librerías de {% data variables.product.prodname_codeql %}. +Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries. -Para obtener más información sobre cómo configurar el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)". +For more information on setting up the {% data variables.product.prodname_codeql_cli %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." -## Resumen de los cambios en los flujos de trabajo +## Overview of workflow changes -Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_runner %} para analizar una base de código tiene los siguientes pasos. -- `codeql-runner- init` para comenzar a crear las bases de datos de {% data variables.product.prodname_codeql %} y leer la configuración. -- Para los lenguajes compilados: configura las variables de ambiente que produce el paso `init`. -- Para los lenguajes compilados: ejecuta la autocompilación o los pasos de compilación manual. -- `codeql-runner- analyze` para terminar de crear las bases de datos de {% data variables.product.prodname_codeql %}, ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %}, resumir los resultados en un archivo SARIF, y cargar los resultados a {% data variables.product.prodname_dotcom %}. +A typical workflow that uses the {% data variables.product.prodname_codeql_runner %} to analyze a codebase has the following steps. +- `codeql-runner- init` to start creating {% data variables.product.prodname_codeql %} databases and read the configuration. +- For compiled languages: set environment variables produced by the `init` step. +- For compiled languages: run autobuild or manual build steps. +- `codeql-runner- analyze` to finish creating {% data variables.product.prodname_codeql %} databases, run queries to analyze each {% data variables.product.prodname_codeql %} database, summarize the results in a SARIF file, and upload the results to {% data variables.product.prodname_dotcom %}. -Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_cli %} para analizar una base de código tiene los siguientes pasos. -- `codeql database create` para crear bases de datos de {% data variables.product.prodname_codeql %}. - - Para los lenguajes compilados: Proporciona un comando de compilación opcionalmente. -- `codeql database analyze` para ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %} y resumir los resultados en un archivo SARIF. Este comando debe ejecutarse una vez para cada lenguaje o base de datos. -- `codeql github upload-results` para cargar los archivos SARIF resultantes a {% data variables.product.prodname_dotcom %}, para que se muestre como alertas del escaneo de código. Este comando debe ejecutarse una vez para cada archivo SARIF o lenguaje. +A typical workflow that uses the {% data variables.product.prodname_codeql_cli %} to analyze a codebase has the following steps. +- `codeql database create` to create {% data variables.product.prodname_codeql %} databases. + - For compiled languages: Optionally provide a build command. +- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database. +- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file. -Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)". +For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)." -## Ejemplos de usos comunes para el {% data variables.product.prodname_codeql_cli %} +## Examples of common uses for the {% data variables.product.prodname_codeql_cli %} -### Acerca de los ejemplos +### About the examples -Estos ejemplos asumen que el código fuente se verificó en el directorio de trabajo actual. Si utilizas un directorio diferente, cambia el argumento `--source-root` y compila los pasos como sea correcto. +These examples assume that the source code has been checked out to the current working directory. If you use a different directory, change the `--source-root` argument and the build steps accordingly. -Estos ejemplos también asumen que el {% data variables.product.prodname_codeql_cli %} se coloca en la RUTA correcta. +These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH. -En estos ejemplos, un token de{% data variables.product.prodname_dotcom %} con alcance suficiente se almacena en la variable de ambiente `$TOKEN` y se pasa por los comandos de ejemplo a través de stdin o se almacena en la variable de ambiente `$GITHUB_TOKEN`. +In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable. -El nombre de ref y el SHA de confirmación que se verifican y analizan en estos ejemplos se conocen durante el flujo de trabajo. En el caso de las ramas, utiliza `refs/heads/BRANCH-NAME` como el ref. En el caso de la confirmación de encabezado de una solicitud de cambios, utiliza `refs/pulls/NUMBER/head`. En el caso de una confirmación de fusión generada por {% data variables.product.prodname_dotcom %} para una solicitud de cambios, utiliza `refs/pulls/NUMBER/merge`. Todos los siguientes ejemplos utilizan `refs/heads/main`. Si utilizas un nombre de rama diferente, debes modificar el código de muestra. +The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. -### Lenguaje sencillo no compilado (JavaScript) +### Single non-compiled language (JavaScript) Runner: ```bash @@ -79,9 +80,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Lenguaje sencillo no compilado (JavaScript) utilizando una suite de consultas (security-and-quality) +### Single non-compiled language (JavaScript) using a different query suite (security-and-quality) -Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples. +A similar approach can be taken for compiled languages, or multiple languages. Runner: ```bash @@ -109,9 +110,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Lenguaje sencillo no compilado (JavaScript) utilizando un archivo de configuración personalizado +### Single non-compiled language (JavaScript) using a custom configuration file -Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples. +A similar approach can be taken for compiled languages, or multiple languages. Runner: ```bash @@ -140,7 +141,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Lenguaje sencillo no compilado utilizando compilación automática (Java) +### Single compiled language using autobuild (Java) Runner: ```bash @@ -174,7 +175,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-java.sarif --github-auth-stdin ``` -### Lenguaje sencillo no copilado utilizando un comando de compilación personalizado (Java) +### Single compiled language using a custom build command (Java) Runner: ```bash @@ -207,9 +208,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-java.sarif --github-auth-stdin ``` -### Lenguaje sencillo no compilado utilizando rastreo de compilación indirecto (C# sobre Windows dentro de Azure DevOps) +### Single compiled language using indirect build tracing (C# on Windows within Azure DevOps) -El rastreo de compilación indirecta para los lenguajes compilados habilita al {% data variables.product.prodname_codeql %} para que detecte los pasos de compilación entre los pasos de `init` y `analyze`, cuando el código no puede compilarse utilizando la compilación automática o una línea de comandos compilada explícita. Esto es útil cuando se utilizan pasos de compilación preconfigurados desde tu sistema de IC, tales como las tareas de `VSBuild` y `MSBuild` en Azure DevOps. +Indirect build tracing for a compiled language enables {% data variables.product.prodname_codeql %} to detect all build steps between the `init` and `analyze` steps, when the code cannot be built using the autobuilder or an explicit build command line. This is useful when using preconfigured build steps from your CI system, such as the `VSBuild` and `MSBuild` tasks in Azure DevOps. Runner: ```yaml @@ -329,9 +330,10 @@ CLI: ``` -### Lenguajes múltiples utilizando compilación automática (C++, Python) +### Multiple languages using autobuild (C++, Python) -Este ejemplo no es estrictamente posible dentro del {% data variables.product.prodname_codeql_runner %}. Solo se analizará un lenguaje (el lenguaje compilado que tenga la mayoría de los archivos). +This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}. +Only one language (the compiled language with the most files) will be analyzed. Runner: ```bash @@ -371,7 +373,7 @@ for language in cpp python; do done ``` -### Lenguajes múltiples utilizando un comando de compilación personalizado (C++, Python) +### Multiple languages using a custom build command (C++, Python) Runner: ```bash diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index 14ce3be757..441e52b87a 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -36,7 +36,7 @@ topics: The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. {% endif %} diff --git a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md index 03f2bdc45b..ff470708a7 100644 --- a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md @@ -1,6 +1,6 @@ --- -title: Agregar una política de seguridad a tu repositorio -intro: Puedes dar instrucciones de cómo reportar una vulnerabilidad de seguridad en tu proyecto si agregas una política de seguridad a tu repositorio. +title: Adding a security policy to your repository +intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository. redirect_from: - /articles/adding-a-security-policy-to-your-repository - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.1' - ghae: next + ghae: '*' ghec: '*' type: how_to topics: @@ -16,48 +16,50 @@ topics: - Vulnerabilities - Repositories - Health -shortTitle: Agregar una política de seguridad +shortTitle: Add a security policy --- -## Acerca de las políticas de seguridad +## About security policies -Para otorgar instrucciones a las personas sobre cómo reportar las vulnerabilidades de seguridad en tu proyecto,{% ifversion fpt or ghes > 3.0 or ghec %} puedes agregar un archivo de _SECURITY.md_ a carpeta `docs`, `.github` o raíz de tu repositorio.{% else %} puedes agregar un archivo de _SECURITY.md_ a la carpeta `docs` o raíz de tu repositorio.{% endif %} Cuando alguien crea una propuesta en tu repositorio, verán un enlace en la política de seguridad de tu proyecto. +To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes > 3.0 or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy. {% ifversion not ghae %} -Puedes crear una política de seguridad predeterminada para tu cuenta de usuario o de organización. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." +You can create a default security policy for your organization or user account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} {% tip %} -**Sugerencia:** Para que las demás personas puedan encontrar tu política de seguridad, puedes vincular tu archivo _SECURITY.md_ desde otros lugares en tu repositorio, como un archivo README. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". +**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)." {% endtip %} {% ifversion fpt or ghec %} -Después de que alguien reporte una vulnerabilidad de seguridad en tu proyecto, puedes utilizar {% data variables.product.prodname_security_advisories %} para divulgar, arreglar y publicar información acerca de la misma. Para obtener más información sobre el proceso de reportar y divulgar vulnerabilidades en {% data variables.product.prodname_dotcom %}, consulta la sección "[Acerca de la divulgación coordinada de las vulnerabilidades de seguridad](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para obtener más información acerca de las {% data variables.product.prodname_security_advisories %}, consulta la sección "[Acerca del {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". +After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about {% data variables.product.prodname_security_advisories %}, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." {% data reusables.repositories.github-security-lab %} {% endif %} -{% ifversion ghes > 3.0 or ghae-next %} +{% ifversion ghes > 3.0 or ghae %} -Cuando pones las instrucciones de reporte de seguridad claramente disponibles, facilitas a tus usurios el reportar cualquier vulnerabilidad de seguridad que encuentren en tu repositorio utilizando tu canal de comunicación preferido. +By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel. {% endif %} -## Agregar una política de seguridad a tu repositorio +## Adding a security policy to your repository {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. En la barra lateral iziquierda, haz clic en **Política de seguridad**. ![Pestaña de política de seguridad](/assets/images/help/security/security-policy-tab.png) -4. Haz clic en **Start setup** (Iniciar configuración). ![Botón Start setup (Iniciar configuración)](/assets/images/help/security/start-setup-security-policy-button.png) -5. En el archivo _SECURITY.md_ nuevo, agrega información sobre las versiones compatibles de tu proyecto y cómo informar una vulnerabilidad. +3. In the left sidebar, click **Security policy**. + ![Security policy tab](/assets/images/help/security/security-policy-tab.png) +4. Click **Start setup**. + ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png) +5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability. {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} -## Leer más +## Further reading -- "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %} -- "[Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %} +- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %} +- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %} - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %} diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md index f6811cfb39..174275d178 100644 --- a/translations/es-ES/content/code-security/getting-started/github-security-features.md +++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md @@ -23,7 +23,7 @@ The {% data variables.product.prodname_advisory_database %} contains a curated l {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} ## Available for all repositories {% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} ### Security policy Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md index 8b7f466b77..7cbdb8a96f 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md @@ -35,7 +35,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The - To change who can view your repository, click **Change visibility**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %} - To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)."{% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} ## Setting a security policy 1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**. diff --git a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md index 870dca2229..445c0f3fab 100644 --- a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md @@ -54,19 +54,19 @@ When {% data variables.product.prodname_secret_scanning %} detects a set of cred If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% ifversion fpt or ghec %} private{% endif %} repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."{% endif %} When you push commits to a{% ifversion fpt or ghec %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets. When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% ifversion fpt or ghec %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} generates an alert. - {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners. -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} - {% data variables.product.prodname_dotcom %} sends an email alert to the contributor who committed the secret to the repository, with a link to the related {% data variables.product.prodname_secret_scanning %} alert. The commit author can then view the alert in the repository, and resolve the alert. {% endif %} - {% data variables.product.prodname_dotcom %} displays an alert in the repository.{% ifversion ghes = 3.0 %} For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} For more information about viewing and resolving {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %} Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." diff --git a/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md index 1e72900bcd..3ae19dfdbe 100644 --- a/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md +++ b/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md @@ -1,6 +1,6 @@ --- -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.' +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.' redirect_from: - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories @@ -17,7 +17,7 @@ topics: - Secret scanning - Advanced Security - Repositories -shortTitle: Configurar escaneos de secretos +shortTitle: Configure secret scans --- {% data reusables.secret-scanning.beta %} @@ -26,61 +26,66 @@ shortTitle: Configurar escaneos de secretos {% ifversion fpt or ghec %} {% note %} -**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. +**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. {% endnote %} {% endif %} -## Habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% ifversion fpt or ghec %}privados {% endif %} +## Enabling {% data variables.product.prodname_secret_scanning %} for {% ifversion fpt or ghec %}private {% endif %}repositories -{% ifversion ghes or ghae-next %} -Puedes habilitar el {% data variables.product.prodname_secret_scanning %} para cualquier repositorio que pertenezca a una organización. -{% endif %} Una vez habilitado, {% data reusables.secret-scanning.secret-scanning-process %} +{% ifversion ghes or ghae %} +You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization. +{% endif %} Once enabled, {% data reusables.secret-scanning.secret-scanning-process %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} -4. Si aún no se ha habilitado la {% data variables.product.prodname_advanced_security %} para el repositorio, haz clic en **Habilitar** a la derecha de "{% data variables.product.prodname_GH_advanced_security %}". - {% ifversion fpt or ghec %}![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-dotcom.png) - {% elsif ghes > 3.0 or ghae-next %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %} -5. Revisa el impacto de habilitar la {% data variables.product.prodname_advanced_security %} y luego haz clic en **Habilitar la {% data variables.product.prodname_GH_advanced_security %} para este repositorio**. -6. Cuando habilitas la {% data variables.product.prodname_advanced_security %}, puede que el {% data variables.product.prodname_secret_scanning %} se habilite en el repositorio debido a 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) +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. + {% ifversion fpt or ghec %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) + {% elsif ghes > 3.0 or ghae %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %} +5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**. +6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. 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) {% elsif ghes = 3.0 %} -7. 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) +7. 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) {% endif %} {% ifversion ghae %} -1. Antes de que puedas habilitar el {% data variables.product.prodname_secret_scanning %}, necesitas habilitar primero 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/enterprise/github-ae/repository/enable-ghas-ghae.png) -2. 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/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png) -3. 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/enterprise/github-ae/repository/enable-secret-scanning-ghae.png) +1. Before you can enable {% data variables.product.prodname_secret_scanning %}, 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/enterprise/github-ae/repository/enable-ghas-ghae.png) +2. 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/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png) +3. 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/enterprise/github-ae/repository/enable-secret-scanning-ghae.png) {% endif %} -## Excluir alertas del {% data variables.product.prodname_secret_scanning %} en los repositorios {% ifversion fpt or ghec %}privados {% endif %} +## Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% ifversion fpt or ghec %}private {% endif %}repositories -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. +You can use a *secret_scanning.yml* file to exclude directories from {% data variables.product.prodname_secret_scanning %}. For example, you can exclude directories that contain tests or randomly generated content. {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. En el campo de nombre del archivo, teclea *.github/secret_scanning.yml*. -4. Debajo de **Editar nuevo archivo**, teclea `paths-ignore:` seguido por las rutas que quieras excluir de {% data variables.product.prodname_secret_scanning %}. +3. In the file name field, type *.github/secret_scanning.yml*. +4. Under **Edit new file**, type `paths-ignore:` followed by the paths you want to exclude from {% data variables.product.prodname_secret_scanning %}. ``` yaml paths-ignore: - "foo/bar/*.js" ``` - - Puedes utilizar caracteres especiales, tales como `*` para filtrar las rutas. Para obtener más información acerca de filtrar las rutas, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)". + + You can use special characters, such as `*` to filter paths. For more information about filter patterns, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)." {% note %} - - **Notas:** - - Si hay más de 1,000 entradas en `paths-ignore`, {% data variables.product.prodname_secret_scanning %} solo excluirá de los escaneos a los primeros 1,000 directorios. - - Si *secret_scanning.yml* es mayor a 1 MB, {% data variables.product.prodname_secret_scanning %} ignorará todo el archivo. - + + **Notes:** + - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans. + - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file. + {% endnote %} -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-secret-scanning-alerts)". +You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)." -## Leer más +## Further reading -- "[Administrar la seguridad y la configuración de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}- "[Definir patrones personalizados para el {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"{% endif %} +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" +{% ifversion fpt or ghes > 3.1 or ghae or ghec %}- "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"{% endif %} diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index ed23e51702..7ef55ec4a7 100644 --- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.2' - ghae: next + ghae: '*' ghec: '*' topics: - Repositories diff --git a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md index 15013c110e..16d8b25dda 100644 --- a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md @@ -25,7 +25,7 @@ shortTitle: About security overview You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." -The security overview indicates whether {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae-next %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} +The security overview indicates whether {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)." diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md b/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md new file mode 100644 index 0000000000..8c37404960 --- /dev/null +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md @@ -0,0 +1,45 @@ +--- +title: Connecting to a private network +intro: 'You can connect {% data variables.product.prodname_codespaces %} to resources on a private network, including package registries, license servers, and on-premises databases.' +product: '{% data reusables.gated-features.codespaces %}' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Fundamentals + - Developer +--- + +## About codespace networking + +By default, your codespaces have access to all resources on the public internet, including package managers, license servers, databases, and cloud platform APIs, but they have no access to resources on private networks. + +## Connecting to resources on a private network + +The currently supported method of accessing resources on a private network is to use a VPN. It is currently not recommended to allowlist codespaces IPs as this would allow all codespaces (both yours and those of other customers) access to the network protected resources. + +### Using a VPN to access resources behind a private network + +The easiest way to access resources behind a private network is to VPN into that network from within your codespace. + +We recommend VPN tools like [OpenVPN](https://openvpn.net/) to access resources on a private network. For more information, see "[Using the OpenVPN client from GitHub Codespaces](https://github.com/codespaces-contrib/codespaces-openvpn)." + +There are also a number of third party solutions that, while not explicitly endorsed by {% data variables.product.prodname_dotcom %}, have provided examples of how to integrate with {% data variables.product.prodname_codespaces %}. + +These third party solutions include: + +- [Tailscale](https://tailscale.com/kb/1160/github-codespaces/) + +### Allowlisting private resources for codespaces + +While {% data variables.product.prodname_dotcom %} publishes IP ranges for several products on its Meta API, codespaces IPs are dynamically assigned, meaning your codespace is not guaranteed to have the same IP address day to day. We highly discourage users from allowlisting an entire IP range, as this would give overly broad access to all codespaces (including users not affiliated with your codespaces). + +For more information about the Meta API, see "[Meta](/rest/reference/meta)." + +## Restricting access to the public internet + +At present, there is no way to restrict codespaces from accessing the public internet, or to restrict appropriately authenticated users from accessing a forwarded port. + +For more information on how to secure your codespaces, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces)." diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md index d6e1e5d12f..0558dd88ff 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,7 @@ children: - /using-codespaces-for-pull-requests - /deleting-a-codespace - /forwarding-ports-in-your-codespace + - /connecting-to-a-private-network - /using-codespaces-in-visual-studio-code - /using-codespaces-with-github-cli --- diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md index d5a2cc2400..8f0f7625e6 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md @@ -1,6 +1,6 @@ --- -title: Sintaxis para el modelado de formato de GitHub -intro: 'Puedes utilizar el modelado de formato de {% data variables.product.company_short %} para configurar los formatos para las características compatibles.' +title: Syntax for GitHub's form schema +intro: 'You can use {% data variables.product.company_short %}''s form schema to configure forms for supported features.' versions: fpt: '*' ghec: '*' @@ -11,17 +11,17 @@ topics: {% note %} -**Nota:** El modelado de formatos de {% data variables.product.company_short %} se encuentra actualmente en beta y está sujeto a cambios. +**Note:** {% data variables.product.company_short %}'s form schema is currently in beta and subject to change. {% endnote %} -## Acerca del modelado de formatos de {% data variables.product.company_short %} +## About {% data variables.product.company_short %}'s form schema -Puedes utilizar el modelado de formato de {% data variables.product.company_short %} para configurar los formatos para las características compatibles. Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)". +You can use {% data variables.product.company_short %}'s form schema to configure forms for supported features. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)." -Un formato es un conjunto de elemotos para solicitar la aportación de un usuario. Puedes configurar un formato si creas una definición de formato YAML, la cual es un arreglo de elementos de formato. Cada elemento de formato es un conjunto de pares de valor-llave que determinan el tipo y las propiedades del elemento y las restricciones que quieres aplicarle. Para algunas claves, el valor es otro conjunto de pares de clave-valor. +A form is a set of elements for requesting user input. You can configure a form by creating a YAML form definition, which is an array of form elements. Each form element is a set of key-value pairs that determine the type of the element, the properties of the element, and the constraints you want to apply to the element. For some keys, the value is another set of key-value pairs. -Por ejemplo, la siguente definición de formato incluye cuatro elementos de formato: un área de texto para proporcionar el sistema operativo del usuario, un menú desplegable para elegir la versión de software que está ejecutando el usuario, una casilla de verificación para reconocer que se leyó y aceptó el código de conducta y el lenguaje de marcado que agradece al usuario por haber completado el formato. +For example, the following form definition includes four form elements: a text area for providing the user's operating system, a dropdown menu for choosing the software version the user is running, a checkbox to acknowledge the Code of Conduct, and Markdown that thanks the user for completing the form. ```yaml{:copy} - type: textarea @@ -55,48 +55,48 @@ Por ejemplo, la siguente definición de formato incluye cuatro elementos de form value: "Thanks for completing our form!" ``` -## Claves +## Keys -Para cada elemento de formato, puedes configurar las siguientes claves. +For each form element, you can set the following keys. -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | -| `type` | El tipo de elemento que quieres definir. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | -| `id` | El identificador del elemento, excepto cuando el `type` se configura como `markdown`. {% data reusables.form-schema.id-must-be-unique %} Si se proporcionó, la `id` es el identificador canónico para el campo en los pre-llenados de parámetro de la consulta de URL. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `attributes` | Un conjunto de pares clave-valor que definen las propiedades del elemento. | Requerido | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `validations` | Un conjunto de pares de clave-valor que configuran las restricciones en el elemento. | Opcional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +| `type` | The type of element that you want to define. | Required | String | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | +| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} If provided, the `id` is the canonical identifier for the field in URL query parameter prefills. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `attributes` | A set of key-value pairs that define the properties of the element. | Required | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `validations` | A set of key-value pairs that set constraints on the element. | Optional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -Puedes elegir desde los siguientes tipos de elementos de formato. Cada tipo tiene atributos y validaciones únicos. +You can choose from the following types of form elements. Each type has unique attributes and validations. -| Type | Descripción | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| [`markdown`](#markdown) | El texto de lenguaje de marcado se muestra en el formato para proporcionar contexto adicional al usuario, pero **no se ha enviado**. | -| [`textarea`](#textarea) | Un campo de texto de línea múltiple. | -| [`input`](#input) | Un campo de texto de línea sencilla. | -| [`desplegable`](#dropdown) | Un menú desplegable. | -| [`checkboxes`](#checkboxes) | Un conjunto de casillas de verificación. | +| Type | Description | +| ---- | ----------- | +| [`markdown`](#markdown) | Markdown text that is displayed in the form to provide extra context to the user, but is **not submitted**. | +| [`textarea`](#textarea) | A multi-line text field. | +| [`input`](#input) | A single-line text field. | +| [`dropdown`](#dropdown) | A dropdown menu. | +| [`checkboxes`](#checkboxes) | A set of checkboxes. | ### `markdown` -Puedes utilizar un elemento de `markdown` para mostrar el lenguaje de marcado en tu formato que proporcione contexto adicional al usuario, pero que no se haya emitido. +You can use a `markdown` element to display Markdown in your form that provides extra context to the user, but is not submitted. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------- | ------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | -| `value` | El texto se interpreta. El formateo en lenguaje de marcado es compatible. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +| `value` | The text that is rendered. Markdown formatting is supported. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | {% tip %} -**Tips:** El procesamiento de YAML tratará el símbolo de hash como un comentario. Para insertar encabezados con lenguaje de marcado, pon tu texto entre comillas. +**Tips:** YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes. -Para el texto de línea múltiple, puedes utilizar el operador de pipa. +For multi-line text, you can use the pipe operator. {% endtip %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -110,30 +110,29 @@ body: ### `textarea` -Puedes utilizar un elemento de `textarea` para agregar un texto de línea múltiple a tu formato. Los contribuyentes también pueden adjuntar archivos en los campos de `textarea`. +You can use a `textarea` element to add a multi-line text field to your form. Contributors can also attach files in `textarea` fields. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `etiqueta` | Una descripción breve de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descripción` | Una descripción del área de texto para proporcionar contexto u orientación, la cual se muestra en el formato. | Opcional | Secuencia | Secuencia vacía | {% octicon "dash" aria-label="The dash icon" %} -| `placeholder` | Un marcador de posición que interpreta en el área de texto cuando está vacía. | Opcional | Secuencia | Secuencia vacía | {% octicon "dash" aria-label="The dash icon" %} -| `value` | El texto se pre-llena en el área de texto. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `render` | Si se proporciona un valor, el texto emitido se formatea en un bloque de código. Cuando se proporciona esta llave, el áera de texto no se expandirá para los adjuntos de archivo o la edición de lenguaje de marcado. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | Los lenguajes que conoce {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta [el archivo YAML de lenguajes](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the text area to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `placeholder` | A semi-opaque placeholder that renders in the text area when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Text that is pre-filled in the text area. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `render` | If a value is provided, submitted text will be formatted into a codeblock. When this key is provided, the text area will not expand for file attachments or Markdown editing. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Languages known to {% data variables.product.prodname_dotcom %}. For more information, see [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). | -#### Validaciones +#### Validations {% data reusables.form-schema.validations-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ----- | ----------- | --------- | ---- | -------------- | --------------- | -| | | | | | | +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -154,29 +153,28 @@ body: ### `input` -Puedes utilizar un elemento de `input` para agregar un campo de texto de línea sencilla a tu formato. +You can use an `input` element to add a single-line text field to your form. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------------- | -------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | -| `etiqueta` | Una descripción breve de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descripción` | Una descripción del campo para proporcionar contexto u orientación, la cual se muestra en el formato. | Opcional | Secuencia | Secuencia vacía | {% octicon "dash" aria-label="The dash icon" %} -| `placeholder` | Un marcador de posición semi-transparente que interpreta en el campo cuando está vacío. | Opcional | Secuencia | Secuencia vacía | {% octicon "dash" aria-label="The dash icon" %} -| `value` | El texto se pre-llenó en el campo. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the field to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `placeholder` | A semi-transparent placeholder that renders in the field when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `value` | Text that is pre-filled in the field. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -#### Validaciones +#### Validations {% data reusables.form-schema.validations-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ----- | ----------- | --------- | ---- | -------------- | --------------- | -| | | | | | | +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -190,31 +188,30 @@ body: required: true ``` -### `desplegable` +### `dropdown` -Puedes utilizar un elemento de `dropdown` para agregar un menú desplegable en tu formato. +You can use a `dropdown` element to add a dropdown menu in your form. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------------- | -------------------------------------------------------------------------------------------------------------------------- | --------- | --------------------- | ----------------------------------------------- | ----------------------------------------------- | -| `etiqueta` | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descripción` | Una descripción del menú desplegable para proporcionar contexto adicional u orientación, la cual se muestra en el formato. | Opcional | Secuencia | Secuencia vacía | {% octicon "dash" aria-label="The dash icon" %} -| `multiple` | Determina si el usuario puede seleccionar más de una opción. | Opcional | Booleano | false | {% octicon "dash" aria-label="The dash icon" %} -| `options` | Un arreglo de opciones que puede elegir el usuario. No puede estar vacío y todas las elecciones deben ser distintas. | Requerido | Arreglo de secuencias | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the dropdown to provide extra context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `multiple` | Determines if the user can select more than one option. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} | +| `options` | An array of options the user can choose from. Cannot be empty and all choices must be distinct. | Required | String array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | -#### Validaciones +#### Validations {% data reusables.form-schema.validations-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ----- | ----------- | --------- | ---- | -------------- | --------------- | -| | | | | | | +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -233,22 +230,22 @@ body: ### `checkboxes` -Puedes utilizar el elemento de `checkboxes` para agregar un conjunto de casillas de verificación a tu formato. +You can use the `checkboxes` element to add a set of checkboxes to your form. -#### Atributos +#### Attributes {% data reusables.form-schema.attributes-intro %} -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | -| `etiqueta` | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `descripción` | Una descripción del conjunto de casillas de verificación, la cual se muestra en el formato. Es compatible con el formateo de lenguaje de marcado. | Opcional | Secuencia | Secuencia vacía | {% octicon "dash" aria-label="The dash icon" %} -| `options` | Un arreglo de casillas de verificación que puede seleccionar el usuario. Para conocer la sintaxis, consulta a continuación. | Requerido | Arreglo | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Key | Description | Required | Type | Default | Valid values | +| --- | ----------- | -------- | ---- | ------- | ------- | +| `label` | A brief description of the expected user input, which is displayed in the form. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | +| `description` | A description of the set of checkboxes, which is displayed in the form. Supports Markdown formatting. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} | +| `options` | An array of checkboxes that the user can select. For syntax, see below. | Required | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | {% data reusables.form-schema.options-syntax %} {% data reusables.form-schema.required-key %} -#### Ejemplo +#### Example ```YAML{:copy} body: @@ -263,6 +260,6 @@ body: - label: Linux ``` -## Leer más +## Further reading - [YAML](https://yaml.org) diff --git a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md index 591a162bb2..e561cf3c93 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md @@ -1,6 +1,6 @@ --- -title: Crear una GitHub App a partir de un manifiesto -intro: 'Un Manifiesto de una GitHub App es una GitHub App preconfigurada que puedes compartir con cualquiera que desée utilizar tu app en sus repositorios personales. El flujo del manifiesto les permite a los usuarios crear, instalar y comenzar a extender una GitHub App rápidamente sin necesidad de registrarla o de conectar el registro al código hospedado de la app.' +title: Creating a GitHub App from a manifest +intro: 'A GitHub App Manifest is a preconfigured GitHub App you can share with anyone who wants to use your app in their personal repositories. The manifest flow allows someone to quickly create, install, and start extending a GitHub App without needing to register the app or connect the registration to the hosted app code.' redirect_from: - /apps/building-github-apps/creating-github-apps-from-a-manifest - /developers/apps/creating-a-github-app-from-a-manifest @@ -11,80 +11,79 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Flujo de manifiesto para la creación de Apps +shortTitle: App creation manifest flow --- +## About GitHub App Manifests -## Acerca de los Manifiestos de las GitHub Apps +When someone creates a GitHub App from a manifest, they only need to follow a URL and name the app. The manifest includes the permissions, events, and webhook URL needed to automatically register the app. The manifest flow creates the GitHub App registration and retrieves the app's webhook secret, private key (PEM file), and GitHub App ID. The person who creates the app from the manifest will own the app and can choose to [edit the app's configuration settings](/apps/managing-github-apps/modifying-a-github-app/), delete it, or transfer it to another person on GitHub. -Cuando alguien crea una GitHub App desde un manifiesto, únicamente necesitan seguir una URL y nombrar a la app. El manifiesto incluye los permisos, eventos, y URL de los webhooks que se necesiten para registrar la app automáticamente. El flujo del manifiesto crea el registro de la GitHub App y recupera el secreto del webhook, llave privada (archivo PEM), e ID de la GitHub App. Quien sea que cree la app desde el manifiesto será el propietario de la misma y podrá elegir [editar los ajustes de la configuración de seguridad de la app](/apps/managing-github-apps/modifying-a-github-app/), eliminarlos, o transferirlos a otra persona en GitHub. +You can use [Probot](https://probot.github.io/) to get started with GitHub App Manifests or see an example implementation. See "[Using Probot to implement the GitHub App Manifest flow](#using-probot-to-implement-the-github-app-manifest-flow)" to learn more. -Puedes utilizar al [Probot](https://probot.github.io/) para comenzar a utilizar los Manifiestos de las GitHub Apps o ver un ejemplo de implementación. Consulta la sección "[Utilizar al Probot para implementar el flujo del Manifiesto de las GitHub Apps](#using-probot-to-implement-the-github-app-manifest-flow)" para obtener más información. +Here are some scenarios where you might use GitHub App Manifests to create preconfigured apps: -Aquí te mostramos algunos escenarios en donde podrías utilizar los Manifiestos de las GitHub Apps para crear apps preconfiguradas: +* Help new team members come up-to-speed quickly when developing GitHub Apps. +* Allow others to extend a GitHub App using the GitHub APIs without requiring them to configure an app. +* Create GitHub App reference designs to share with the GitHub community. +* Ensure you deploy GitHub Apps to development and production environments using the same configuration. +* Track revisions to a GitHub App configuration. -* Para ayudar a los miembros nuevos del equipo a que se familiaricen rápidamente con el desarrollo de las GitHub Apps. -* Para permitir que otros extiendan una GitHub App utilizando las API de GitHub sin que necesiten configurar dicha app. -* Para crear diseños de referencia de GitHub Apps y compartirlos con la comunidad de GitHub. -* Para garantizar que despliegas GitHub Apps en los ambientes de desarrollo y de producción utilizando la misma configuración. -* Para rastrear las revisiones hechas en la configuración de una GitHub App. +## Implementing the GitHub App Manifest flow -## Implementar el flujo del Manifiesto de una GitHub App - -El flujo del Manifiesto de una GitHub App utiliza un proceso de intercambio similar al del [flujo de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). El flujo utiliza un manifiesto para [registrar una GitHub App](/apps/building-github-apps/creating-a-github-app/) y recibe un `code` temporal que se utiliza para recuperar la llave privada, webhoo, secreto, e ID de la misma. +The GitHub App Manifest flow uses a handshaking process similar to the [OAuth flow](/apps/building-oauth-apps/authorizing-oauth-apps/). The flow uses a manifest to [register a GitHub App](/apps/building-github-apps/creating-a-github-app/) and receives a temporary `code` used to retrieve the app's private key, webhook secret, and ID. {% note %} -**Nota:** Tienes solo una hora para completar los tres pasos del flujo del Manifiesto de la GitHub App. +**Note:** You must complete all three steps in the GitHub App Manifest flow within one hour. {% endnote %} -Sigue estos pasos par aimplementar el flujo del Manifiesto de la GitHub App: +Follow these steps to implement the GitHub App Manifest flow: -1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva. -1. GitHub redirige a las personas de vuelta a tu sitio. -1. Intercambias el código temporal para recuperar la configuración de la app. +1. You redirect people to GitHub to create a new GitHub App. +1. GitHub redirects people back to your site. +1. You exchange the temporary code to retrieve the app configuration. -### 1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva +### 1. You redirect people to GitHub to create a new GitHub App -Para redireccionar a las personas a crear una GitHub App nueva, [proporciona un enlace](#examples) para que ellos den clic y envíen una solicitud de `POST` a `https://github.com/settings/apps/new` para una cuenta de usuario o a `https://github.com/organizations/ORGANIZATION/settings/apps/new` para una cuenta de organización, reemplazando `ORGANIZATION` con el nombre de la cuenta de organización en donde se creará la app. +To redirect people to create a new GitHub App, [provide a link](#examples) for them to click that sends a `POST` request to `https://github.com/settings/apps/new` for a user account or `https://github.com/organizations/ORGANIZATION/settings/apps/new` for an organization account, replacing `ORGANIZATION` with the name of the organization account where the app will be created. -Debes incluir los [Parámetros del Manifiesto de la GitHub App](#github-app-manifest-parameters) como una secuencia cifrada con JSON en un parámetro que se llame `manifest`. También puedes incluir un [parámetro](#parameters) de `state` para agregar seguridad adicional. +You must include the [GitHub App Manifest parameters](#github-app-manifest-parameters) as a JSON-encoded string in a parameter called `manifest`. You can also include a `state` [parameter](#parameters) for additional security. -Se redirigirá al creador de la app a una página de GitHub en donde encontrará un campo de entrada y ahí podrá editar el nombre de la app que incluiste en el parámetro de `manifest`. Si no incluyes un `name` en el `manifest`, podrán configurar un nombre de su elección para la app en este campo. +The person creating the app will be redirected to a GitHub page with an input field where they can edit the name of the app you included in the `manifest` parameter. If you do not include a `name` in the `manifest`, they can set their own name for the app in this field. -![Crear un Manifiesto de una GitHub App](/assets/images/github-apps/create-github-app-manifest.png) +![Create a GitHub App Manifest](/assets/images/github-apps/create-github-app-manifest.png) -#### Parámetros del Manifiesto de la GitHub App +#### GitHub App Manifest parameters - | Nombre | Type | Descripción | - | --------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name (nombre)` | `secuencia` | El nombre dela GitHub App. | - | `url` | `secuencia` | **Requerido.** La página principal de tu GitHub App. | - | `hook_attributes` | `objeto` | La configuración del webhook de la GitHub App. | - | `redirect_url` | `secuencia` | La URL completa a la cual redirigir después de que el usuario incia la creación de una GitHub App desde un manifiesto.{% ifversion fpt or ghae-next or ghes > 3.0 or ghec %} - | `callback_urls` | `conjunto de secuencias` | Una URL completa a la cual redirigir cuando alguien autorice una instalación. Puedes proporcionar hasta 10 URL de rellamado.{% else %} - | `callback_url` | `secuencia` | Una URL completa a la cual redirigir cuando alguien autoriza una instalación.{% endif %} - | `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` | `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`). | + Name | Type | Description +-----|------|------------- +`name` | `string` | The name of the GitHub App. +`url` | `string` | **Required.** The homepage of your GitHub App. +`hook_attributes` | `object` | The configuration of the GitHub App's webhook. +`redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% ifversion fpt or ghae or ghes > 3.0 or ghec %} +`callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} +`callback_url` | `string` | A full URL to redirect to after someone authorizes an installation.{% endif %} +`description` | `string` | A description of the GitHub App. +`public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. +`default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. +`default_permissions` | `object` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). -El objeto `hook_attributes` tiene la siguiente clave: +The `hook_attributes` object has the following key: -| Nombre | Type | Descripción | -| -------- | ----------- | --------------------------------------------------------------------------------------------- | -| `url` | `secuencia` | **Requerido.** La URL del servidor que recibirá las solicitudes de `POST` del webhook. | -| `active` | `boolean` | Entrega detalles del evento cuando se activa este gancho y su valor predeterminado es "true". | +Name | Type | Description +-----|------|------------- +`url` | `string` | **Required.** The URL of the server that will receive the webhook `POST` requests. +`active` | `boolean` | Deliver event details when this hook is triggered, defaults to true. -#### Parámetros +#### Parameters - | Nombre | Type | Descripción | - | ------- | ----------- | ------------------------------------------- | - | `state` | `secuencia` | {% data reusables.apps.state_description %} + Name | Type | Description +-----|------|------------- +`state`| `string` | {% data reusables.apps.state_description %} -#### Ejemplos +#### Examples -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: +This example uses a form on a web page with a button that triggers the `POST` request for a user account: ```html
    @@ -101,7 +100,7 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s "url": "https://example.com/github/events", }, "redirect_url": "https://example.com/redirect", - {% ifversion fpt or ghae-next or ghes > 3.0 or ghec %}"callback_urls": [ + {% ifversion fpt or ghae or ghes > 3.0 or ghec %}"callback_urls": [ "https://example.com/callback" ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, @@ -119,7 +118,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. +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 @@ -136,7 +135,7 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s "url": "https://example.com/github/events", }, "redirect_url": "https://example.com/redirect", - {% ifversion fpt or ghae-next or ghes > 3.0 or ghec %}"callback_urls": [ + {% ifversion fpt or ghae or ghes > 3.0 or ghec %}"callback_urls": [ "https://example.com/callback" ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, @@ -154,49 +153,49 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s ``` -### 2. GitHub redirige a las personas de vuelta a tu sitio +### 2. GitHub redirects people back to your site -Cuando la persona dé clic en **Crear GitHub App**, Github lo redirigirá a la `redirect_url` con un `code` temporal en un parámetro de código. Por ejemplo: +When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. For example: https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 -Si proporcionaste un parámetro de `state`, también verás este parámetro en la `redirect_url`. Por ejemplo: +If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. For example: https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 -### 3. Intercambias el código temporal para recuperar la configuración de la app +### 3. You exchange the temporary code to retrieve the app configuration -Para completar el intercambio, envía el `code` temporal en una solicitud de tipo `POST` a la terminal [Crear una Github App a partir de un manifiesto](/rest/reference/apps#create-a-github-app-from-a-manifest). La respuesta incluirá la `id` (GitHub App ID), la `pem` (llave privada), y el `webhook_secret`. GitHub crea un secreto de webhook para la app de forma automática. Puedes almacenar estos valores en variables de ambiente dentro del servidor de la app. Por ejemplo, si tu app utiliza [dotenv](https://github.com/bkeepers/dotenv) para almacenar las variables de ambiente, almacenarías las variables en el archivo `.env` de tu app. +To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file. -Tienes solo una hora para completar este paso en el flujo del Manifiesto de la GitHub App. +You must complete this step of the GitHub App Manifest flow within one hour. {% note %} -**Nota:** Esta terminal tiene un límite de tasa. Consulta la sección [Límites de tasa](/rest/reference/rate-limit) para aprender cómo obtener tu estado actual de límite de tasa. +**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status. {% endnote %} POST /app-manifests/{code}/conversions -Para obtener más información acerca de la respuesta de la terminal, consulta la sección [Crear una GitHub App desde un manifiesto](/rest/reference/apps#create-a-github-app-from-a-manifest). +For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest). -Cuando se complete el último paso del flujo del manifiesto, la persona que cree la app desde el flujo será el propietario de una GitHub App registrada que podrá instalar en cualquiera de sus repositorios personales. En cualquier momento podrán elegir extender la app utilizando las API de GitHub, transferir la propiedad a alguien más, o borrarla. +When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time. -## Utilizar el Probot par aimplementar el flujo del Manifiesto de la GitHub App +## Using Probot to implement the GitHub App Manifest flow -El [Probot](https://probot.github.io/) es un marco de trabajo que se creó con [Node.js](https://nodejs.org/) y que realiza muchas de las tareas que todas las GitHub Apps requieren, como el validar webhooks y llevar a cabo la autenticación. El Probot implementa el [flujo del manifiesto de las GitHub Apps](#implementing-the-github-app-manifest-flow), lo cual facilita el crear y compartir los diseños de referencia de las GitHub Apps con la comunidad de GtiHub. +[Probot](https://probot.github.io/) is a framework built with [Node.js](https://nodejs.org/) that performs many of the tasks needed by all GitHub Apps, like validating webhooks and performing authentication. Probot implements the [GitHub App manifest flow](#implementing-the-github-app-manifest-flow), making it easy to create and share GitHub App reference designs with the GitHub community. -Para crear una App de Probot que puedas compartir, sigue estos pasos: +To create a Probot App that you can share, follow these steps: -1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app). -1. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. El Probot utiliza la configuración en `app.yml` como los [parámetros del manifiesto dela GitHub App](#github-app-manifest-parameters). -1. Agrega el código personalizado de tu aplicación. -1. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally) u [hospédala en donde quieras](#hosting-your-app-with-glitch). Cuando navegues a la URL de la app hospedada, encontrarás una página web con un botón de **Registrar GitHub App** en el que as personas podrán dar clic para crear una app preconfigurada. La siguiente página web es la implementación del Probot para el [paso 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) en el flujo del Manifiesto de la GitHub App: +1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app). +1. Open the project you created, and customize the settings in the `app.yml` file. Probot uses the settings in `app.yml` as the [GitHub App Manifest parameters](#github-app-manifest-parameters). +1. Add your application's custom code. +1. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally) or [host it anywhere you'd like](#hosting-your-app-with-glitch). When you navigate to the hosted app's URL, you'll find a web page with a **Register GitHub App** button that people can click to create a preconfigured app. The web page below is Probot's implementation of [step 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) in the GitHub App Manifest flow: -![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png) +![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png) -Al utilizar [dotenv](https://github.com/bkeepers/dotenv), el Probot crea un archivo de tipo `.env` y configura las variables de ambiente para la `APP_ID`, `PRIVATE_KEY`, y el `WEBHOOK_SECRET` con los valores que [recupera de la configuración de la app](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). +Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file and sets the `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET` environment variables with the values [retrieved from the app configuration](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). -### Hospedar tu app con Glitch +### Hosting your app with Glitch -Puedes ver un ejemplo de una [App de Probot de muestra](https://glitch.com/~auspicious-aardwolf) que utiliza [Glitch](https://glitch.com/) para hospedar y compartir la app. El ejemplo utiliza la [API de verificaciones](/rest/reference/checks) y selecciona los eventos necesarios de la misma y los permisos en el archivo `app.yml`. Glitch es una herramienta que te permite "Remezclar tus propias apps". El remezclar una app crea una copia de la app que Glitch hospeda y despliega. Consulta la sección "[Acerca de Glitch](https://glitch.com/about/)" para aprender sobre cómo remezclar las apps de Glitch. +You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps. diff --git a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 9a34f94af7..4c41f66d9e 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -22,13 +22,13 @@ You can add query parameters to these URLs to preselect the configuration of a { The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app. -{% ifversion ghes > 3.1 or fpt or ghae-next or ghec %} +{% ifversion ghes > 3.1 or fpt or ghae or ghec %} For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)." {% endif %} The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: -{% ifversion fpt or ghae-next or ghes > 3.0 or ghec %} +{% ifversion fpt or ghae or ghes > 3.0 or ghec %} ```text {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite @@ -50,7 +50,7 @@ The complete list of available query parameters, permissions, and events is list -----|------|------------- `name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. `description` | `string` | A description of the {% data variables.product.prodname_github_app %}. -`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae-next or ghes > 3.0 or ghec %} +`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae or ghes > 3.0 or ghec %} `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} `callback_url` | `string` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} `request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. diff --git a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index f7fea30a12..cc15507cf3 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -98,9 +98,9 @@ By default, the response takes the following form. The response parameters `expi ```json { - "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "access_token": "{% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", + "refresh_token": "{% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -924,7 +924,7 @@ While most of your API interaction should occur using your server-to-server inst * [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Further reading diff --git a/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md index e62b3e056f..7acf2cb64a 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md @@ -1,6 +1,6 @@ --- -title: Actualizar los tokens de acceso de usuario a servidor -intro: 'Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad.' +title: Refreshing user-to-server access tokens +intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.' redirect_from: - /apps/building-github-apps/refreshing-user-to-server-access-tokens - /developers/apps/refreshing-user-to-server-access-tokens @@ -11,75 +11,75 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Actualizar el acceso de usuario a servidor +shortTitle: Refresh user-to-server access --- - {% data reusables.pre-release-program.expiring-user-access-tokens %} -## Acerca de los tokens de acceso de usuario con caducidad +## About expiring user access tokens -Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad. Para obtener más información sobre cómo crear solicitudes de usuario a servidor, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -La caducidad de los tokens se alcanza después de 8 horas. Cuando recibes un token nuevo para el acceso de usuario a servidor, la respuesta también contendrá un token de actualización, el cual se puede intercambiar por un token de usuario nuevo y un token de actualización. Los tokens de actualización son válidos por 6 meses. +Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. -## Renovar un token de usuario con un token de actualización +## Renewing a user token with a refresh token -Para renovar un token de acceso de usuario a servidor que esté por caducar, puedes intercambiar el `refresh_token` por un token de acceso nuevo y un `refresh_token`. +To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`. `POST https://github.com/login/oauth/access_token` -Esta solicitud de rellamada te enviará un token de acceso y un token de actualización nuevos. Esta solicitud de rellamada es similar a la solicitud de OAuth que utilizarías para intercambiar un `code` temporal para un token de acceso. Para obtener más información, consulta las secciones "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" y "[Información básica sobre la autenticación](/rest/guides/basics-of-authentication#providing-a-callback)". +This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." -### Parámetros +### Parameters -| Nombre | Type | Descripción | -| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `refresh_token` | `secuencia` | **Requerido.** El token que se genera cuando el dueño de la {% data variables.product.prodname_github_app %} habilita los tokens con caducidad y emite un token de acceso de usuario nuevo. | -| `grant_type` | `secuencia` | **Requerido.** El valor debe ser `refresh_token` (se requiere en la especificación de OAuth). | -| `client_id` | `secuencia` | **Requerido.** La ID de cliente para tu {% data variables.product.prodname_github_app %}. | -| `client_secret` | `secuencia` | **Requerido.** El secreto del cliente para tu {% data variables.product.prodname_github_app %}. | +Name | Type | Description +-----|------|------------ +`refresh_token` | `string` | **Required.** The token generated when the {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token. +`grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification). +`client_id` | `string` | **Required.** The client ID for your {% data variables.product.prodname_github_app %}. +`client_secret` | `string` | **Required.** The client secret for your {% data variables.product.prodname_github_app %}. -### Respuesta +### Response ```json { - "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "access_token": "{% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", + "refresh_token": "{% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" } ``` -## Configurar los tokens de usuario con caducidad para una GitHub App existente +## Configuring expiring user tokens for an existing GitHub App -Puedes habilitar o inhabilitar los tokens de autorización de usuario a servidor desde los ajustes de tu {% data variables.product.prodname_github_app %}. +You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Da clic en la opción**Editar** junto a la {% data variables.product.prodname_github_app %} que escogiste. ![Configuración para editar una GitHub App](/assets/images/github-apps/edit-test-app.png) -5. En la barra lateral izquierda, haz clic en **{% ifversion ghes < 3.1 %} Características Beta {% else %} Características Opcionales {% endif %}**. +4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}. + ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png) +5. In the left sidebar, click **{% ifversion ghes < 3.1 %} Beta {% else %} Optional {% endif %} Features**. {% ifversion ghes < 3.1 %} ![Beta features tab](/assets/images/github-apps/beta-features-option.png) {% else %} ![Optional features tab](/assets/images/github-apps/optional-features-option.png) {% endif %} -6. Junto a "caducidad de token de usuario a servidor", da clic en **Unirse** o en **No unirse**. Esta característica podría tardar un par de segundos para su aplicación. +6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply. -## Decidir no unirse a los tokens con caducidad para las GitHub Apps nuevas +## Opting out of expiring tokens for new GitHub Apps -Cuando creas una {% data variables.product.prodname_github_app %}, ésta utilizará predeterminadamente los tokens de acceso de usuario a servidor con caducidad. +When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens. -Si quieres que tu app utlice tokens de acceso de usuario a servidor sin caducidad, puedes deseleccionar la opción "Poner caducidad en los tokens de autorización de usuario" en la página de ajustes de la app. +If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page. -![Opción para unirse a los tokens de usuario con caducidad durante la configuración de las GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png) +![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png) -Las {% data variables.product.prodname_github_apps %} existentes que utilicen tokens de autorización de usuario a servidor solo se verán afectadas por este flujo nuevo cuando el propietario de la app habilite la caducidad de los tokens para la app en cuestión. +Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. -Habilitar los tokens de usuario con caducidad para las {% data variables.product.prodname_github_apps %} existentes requiere que se envíen los usuarios a través del flujo de OAuth para re-emitir tokens de usuario nuevos que caducarán en 8 horas y que harán una solicitud con el token de actualización para obtener un token de acceso y un token de actualización nuevos. Para obtener más información, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -## Leer más +## Further reading -- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" {% endif %} diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index f4291e06cb..fc5641bce7 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Autorizar aplicaciones OAuth +title: Authorizing OAuth Apps intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps/ @@ -17,70 +17,69 @@ versions: topics: - OAuth Apps --- +{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser. -La implementación de OAuth de {% data variables.product.product_name %} es compatible con el [tipo de otorgamientos de código de autorización](https://tools.ietf.org/html/rfc6749#section-4.1) estándar y con el [Otorgamiento de Autorización de Dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0 para las apps que no tengan acceso a un buscador web. +If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). -Si quieres saltar el proceso de autorización de tu app en el modo estándar, tal como sucede cuando la estás probando, puedes utilizar el [flujo no web para aplicaciones](#non-web-application-flow). +To authorize your OAuth app, consider which authorization flow best fits your app. -Para autorizar tu app de OAuth, considera qué flujo de autorizaciones queda mejor con ella. +- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.){% ifversion fpt or ghae or ghes > 3.0 or ghec %} +- [device flow](#device-flow): Used for headless apps, such as CLI tools.{% endif %} -- [flujo web de aplicaciones](#web-application-flow): Se utiliza para autorizar a los usuarios para las aplicaciones de OAuth que se ejecutan en el buscador. (El [tipo de otorgamiento implícito](https://tools.ietf.org/html/rfc6749#section-4.2) no es compatible.){% ifversion fpt or ghae or ghes > 3.0 or ghec %} -- [flujo de dispositivos](#device-flow): Se utiliza para las aplicaciones sin encabezado, tales como las herramientas de CLI.{% endif %} - -## Flujo de aplicaciones Web +## Web application flow {% note %} -**Nota:** Si estás creando una GitHub App, aún puedes utilizar el flujo de aplicaciones web de OAuth, pero la configuración tiene diferencias importantes. Consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obtener más información. +**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endnote %} -El flujo web de aplicaciones para autorizar a los usuarios en tu app es: +The web application flow to authorize users for your app is: -1. Se redirecciona a los usuarios para solicitar su identidad de GitHub -2. GitHub redirecciona a los usuarios de vuelta a tu sitio -3. Tu aplicación accede a la API con el token de acceso del usuario +1. Users are redirected to request their GitHub identity +2. Users are redirected back to your site by GitHub +3. Your app accesses the API with the user's access token -### 1. Solicita la identidad de un usuario de GitHub +### 1. Request a user's GitHub identity GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -Cuando tu GitHub App especifica un parámetro de `login`, solicita a los usuarios con una cuenta específica que pueden utilizar para registrarse y autorizar tu app. +When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. -#### Parámetros +#### Parameters -| Nombre | Type | Descripción | -| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `client_id` | `secuencia` | **Requerido**. La ID de cliente que recibiste de GitHub cuando te {% ifversion fpt or ghec %}[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). | -| `login` | `secuencia` | Sugiere una cuenta específica para utilizar para registrarse y autorizar la app. | -| `alcance` | `secuencia` | Una lista de [alcances](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada en espacio. De no proporcionarse, el `scope` será, predeterminadamente, una lista vacía para los usuarios que no han autorizado ningún alcance para la aplicación. Para los usuarios que han autorizado alcances para la aplicación, el usuario no se mostrará en la página de autorización de OAuth con la lista de alcances. En vez de esto, este paso del flujo se completara automáticamente con el conjunto de alcances que el usuario haya autorizado para la aplicación. Por ejemplo, si un usuario ya realizó el flujo web dos veces y autorizó un token con alcance de `user` y otro con alcance de `repo`, un tercer flujo web que no proporcione un `scope` recibirá un token con los alcances `user` y `repo`. | -| `state` | `secuencia` | {% data reusables.apps.state_description %} -| `allow_signup` | `secuencia` | Ya sea que se ofrezca o no una opción para registrarse en GitHub a los usuarios sin autenticar durante el flujo de OAuth, la opción predeterminada es `true`. Utiliza `false` cuando una política prohíba los registros. | +Name | Type | Description +-----|------|-------------- +`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. +`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls). +`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. +`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope. +`state` | `string` | {% data reusables.apps.state_description %} +`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. -### 2. GitHub redirecciona a los usuarios de vuelta a tu sitio +### 2. Users are redirected back to your site by GitHub -Si el usuario acepta tu solicitud, {% data variables.product.product_name %} lo redirecciona a tu sitio con un `code` temporal en un parámetro de código así como el estado que proporcionaste en el paso previo en un parámetro de `state`. El código temporal caducará después de 10 minutos. Si los estados no empatan, entonces un tercero creó la solicitud, y debes abandonar el proceso. +If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process. -Intercambia este `code` por un token de acceso: +Exchange this `code` for an access token: POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -#### Parámetros +#### Parameters -| Nombre | Type | 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 %}. | -| `código` | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1. | -| `redirect_uri` | `secuencia` | La URL en tu aplicación, hacia la cual se envía a los usuarios después de su autorización. | +Name | Type | Description +-----|------|-------------- +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`code` | `string` | **Required.** The code you received as a response to Step 1. +`redirect_uri` | `string` | The URL in your application where users are sent after authorization. -#### Respuesta +#### Response -Predeterminadamente, la respuesta toma la siguiente forma: +By default, the response takes the following form: ``` -access_token={% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer ``` {% data reusables.apps.oauth-auth-vary-response %} @@ -88,7 +87,7 @@ access_token={% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F2 ```json Accept: application/json { - "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer" } @@ -99,18 +98,18 @@ Accept: application/xml bearer repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} ``` -### 3. Utiliza el token de acceso para acceder a la API +### 3. Use the access token to access the API -El token de acceso te permite hacer solicitudes a la API a nombre de un usuario. +The access token allows you to make requests to the API on a behalf of a user. Authorization: token OAUTH-TOKEN GET {% data variables.product.api_url_code %}/user -Por ejemplo, en curl, puedes configurar el encabezado de autorización de la siguiente manera: +For example, in curl you can set the Authorization header like this: ```shell curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user @@ -118,38 +117,38 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre {% ifversion fpt or ghae or ghes > 3.0 or ghec %} -## Flujo de dispositivos +## Device flow {% note %} -**Nota:** El flujo de dispositivos se encuentra en un beta público y está sujeto a cambios. +**Note:** The device flow is in public beta and subject to change. {% endnote %} -Este flujo de dispositivos te permite autorizar usuarios para una app sin encabezado, tal como una herramienta de CLI o un administrador de credenciales de Git. +The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. -### Resumen del flujo de dispositivos +### Overview of the device flow -1. Tu app solicita el dispositivo y los códigos de verificación de usuario y obtiene una URL de autoización en donde el usuario ignresará su código de verificación de usuario. -2. La app pide al usuario ingresar un código de verificación de usuario en {% data variables.product.device_authorization_url %}. -3. La app sondea el estado de autenticación del usuario. Una vez que el usuario haya autorizado el dispositivo, la app podrá hacer llamadas a la API con un token de acceso nuevo. +1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. +2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. +3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. -### Paso 1: La app solicita los códigos de dispositivo y de usuario a GitHub +### Step 1: App requests the device and user verification codes from GitHub POST {% data variables.product.oauth_host_code %}/login/device/code -Tu app debe solicitar un código de verificación de usuario y una URL de verificación que la app utilizará para indicar al usuario que se autentique en el siguiente paso. Esta solicitud también devuelve un código de verificación de dispositivo que debe utilizar la app para recibir un token de acceso y verificar así el estado de la autenticación del usuario. +Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. -#### Parámetros de entrada +#### Input Parameters -| Nombre | Type | Descripción | -| ----------- | ----------- | ------------------------------------------------------------------------------------------------------- | -| `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu app. | -| `alcance` | `secuencia` | El alcance al cual está solicitando acceso tu app. | +Name | Type | Description +-----|------|-------------- +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. +`scope` | `string` | The scope that your app is requesting access to. -#### Respuesta +#### Response -Predeterminadamente, la respuesta toma la siguiente forma: +By default, the response takes the following form: ``` device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice @@ -179,46 +178,46 @@ Accept: application/xml ``` -#### Parámetros de respuesta +#### Response parameters -| Nombre | Type | 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. | -| `verification_uri` | `secuencia` | La URL de verificación en donde los usuarios necesitan ingresar el `user_code`: {% data variables.product.device_authorization_url %}. | -| `expires_in` | `número` | La cantidad de segundos antes de que caduquen tanto el `device_code` como el `user_code`. La cantidad predeterminada es de 900 segundos o 15 minutos. | -| `interval` | `número` | La cantidad mínima de segundos que deben transcurrir antes de que puedas hacer una soliciud de token de acceso nueva (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) para completar la autorización del dispositivo. Por ejemplo, si el intervalo es 5, entonces no puedes hacer una solicitud nueva hasta que hayan transcurrido 5 segudos. Si haces más de una solicitud en estos 5 segundos, entonces lelgarás al límite de tasa y recibirás un error de `slow_down`. | +Name | Type | Description +-----|------|-------------- +`device_code` | `string` | The device verification code is 40 characters and used to verify the device. +`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. +`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. +`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. +`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. -### Paso 2: Indicar al usuario ingresar el código de usuario en un buscador +### Step 2: Prompt the user to enter the user code in a browser -Tu dispositivo mostrará el código de verificación de usuario y pedirá al usuario ingresar el código en la {% data variables.product.device_authorization_url %}. +Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. - ![Campo para ingresar el código de verificación de usuario nuevo en tu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png) + ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) -### Paso 3: La app sondea GitHub para verificar si el usuario autorizó el dispositivo +### Step 3: App polls GitHub to check if the user authorized the device POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -Tu app hará solicitudes de autorización de dispositivo que sondean a `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, hasta que los códigos de dispositivo y de usuario caduquen o hasta que el usuario haya autorizado la app con éxito con un código de usuario válido. La app debe usar el `interval` de sondeo mínimo que se ha recuperado en el paso 1 para evitar los errores de límite de tasa. Para obtener más información, consulta la sección "[Límites de tasa para el flujo del dispositivo](#rate-limits-for-the-device-flow)". +Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." -El usuario debe ingresar un código válido dentro de los 15 minutos (o 900 segundos) siguientes. Después de transcurridos estos 15 minutos, necesitarás solicitar un código de autorización de dispositivo nuevo con `POST {% data variables.product.oauth_host_code %}/login/device/code`. +The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. -Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se puede utilizar para hacer solicitudes a la API en nombre de un usuario. +Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. -#### Parámetros de entrada +#### Input parameters -| Nombre | Type | 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`. | -| `grant_type` | `secuencia` | **Requerido.** El tipo de otorgamiento debe ser `urn:ietf:params:oauth:grant-type:device_code`. | +Name | Type | Description +-----|------|-------------- +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. +`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. -#### Respuesta +#### Response -Predeterminadamente, la respuesta toma la siguiente forma: +By default, the response takes the following form: ``` -access_token={% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist ``` {% data reusables.apps.oauth-auth-vary-response %} @@ -226,7 +225,7 @@ access_token={% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F2 ```json Accept: application/json { - "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "access_token": "{% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "repo,gist" } @@ -235,52 +234,58 @@ Accept: application/json ```xml Accept: application/xml - {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} bearer gist,repo ``` -### Límites de tasa para el flujo del dispositivo +### Rate limits for the device flow -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. +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. -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). +If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). -### Códigos de error para el flujo del dispositivo +### Error codes for the device flow -| Código de error | Descripción | -| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `authorization_pending` | Este error ocurre cuando la solicitud de autorización se encuentra pendiente y el usuario no ha ingresado el código de usuario aún. Se espera que la app siga sondeando la solicitud de `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` sin exceder el [`interval`](#response-parameters), lo cual requiere una cantidad mínima de segundos entre cada solicitud. | -| `slow_down` | Cuando recibes el error de `slow_down`, se agregan 5 segundos extra al `interval` mínimo o al marco de tiempo requerido entre tus solicitudes utilizando `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. Por ejemplo, si el intervalo de inicio requirió por lo menos 5 segundos entre solicitudes y obtienes una respuesta de error de `slow_down`, ahora necesitarás esperar por lo menos 10 segundos antes de que hagas una solicitud nueva para un token de acceso de OAuth. La respuesta de error incluye el nuevo `interval` que debes utilizar. | -| `expired_token` | Si el código de dispositivo expiró, entonces verás el error `token_expired`. Debes hacer una nueva solicitud para un código de dispositivo. | -| `unsupported_grant_type` | El tipo de otorgamiento debe ser `urn:ietf:params:oauth:grant-type:device_code` y se debe incluir como un parámetro de entrada cuando sondeas la solicitud de token de OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. | -| `incorrect_client_credentials` | Para el flujo de dispositivos, debes pasar la ID de cliente de tu app, la cual puedes encontrar en la página de configuración de la misma. No se necesita el `client_secret` para el flujo del dispositivo. | -| `incorrect_device_code` | El device_code que se proporcionó es inválido. | -| `access_denied` | Cuando un usuario da clic en cancelar durante el proceso de autorización, recibirás un error de `access_denied` y el usuario no podrá utilizar el código de verificación nuevamente. | +| Error code | Description | +|----|----| +| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | +| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. +| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. +| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. +| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. +| `incorrect_device_code` | The device_code provided is not valid. +| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again. -Para obtener más información, consulta la sección "[Otorgamiento de Autorización de Dispositivo de OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)". +For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." {% endif %} -## Flujo de aplicaciónes no web +## Non-Web application flow -La autenticación no web está disponible para situaciones limitadas, como las pruebas. Si lo necesitas, puedes utilizar la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) para crear un token de acceso personal utilizando tu [página de configuración de los tokens de acceso personal](/articles/creating-an-access-token-for-command-line-use). Esta técnica le permite al usuario revocar el acceso en cualquier momento. +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. {% ifversion fpt or ghes or ghec %} {% note %} -**Nota:** CUando utilices el flujo de aplicaciones no web para crear un token OAuth2, asegúrate de entender cómo [trabajar con autenticaciones de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) si tú o tus usuarios han habilitado dicho tipo de autenticación. +**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with +two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if +you or your users have two-factor authentication enabled. {% endnote %} {% endif %} -## URLs de Redirección +## Redirect URLs -El parámetro `redirect_uri` es opcional. Si se deja fuera, GitHub redireccionará a los usuarios a la URL de rellamado configurada en la aplicación de OAuth. De proporcionarse, el puerto y host de las URL de rellamado deberán empatar exactamente con la URL de rellamado. La ruta de las URL de redireccionamiento deberán referenciar un subdirectorio de la URL de rellamado. +The `redirect_uri` parameter is optional. If left out, GitHub will +redirect users to the callback URL configured in the OAuth Application +settings. If provided, the redirect URL's host and port must exactly +match the callback URL. The redirect URL's path must reference a +subdirectory of the callback URL. CALLBACK: http://example.com/path - + GOOD: http://example.com/path GOOD: http://example.com/path/subdir/other BAD: http://example.com/bar @@ -289,31 +294,31 @@ El parámetro `redirect_uri` es opcional. Si se deja fuera, GitHub redireccionar BAD: http://oauth.example.com:8080/path BAD: http://example.org -### URLs de redirección de Localhost +### Localhost redirect urls -El parámetro opcional `redirect_uri` también puede utilizarse para las URL de localhost. Si la aplicación especifica una URL y puerto de localhost, entonces, después de autorizar la aplicación, los usuarios se redireccionarán al puerto y URL proporcionados. La `redirect_uri` no necesita empatar con el puerto especificado en la url de rellamado para la app. +The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app. -Para la URL de rellamado de `http://localhost/path`, puedes utilizar esta `redirect_uri`: +For the `http://localhost/path` callback URL, you can use this `redirect_uri`: ``` http://localhost:1234/path ``` -## Crear tokens múltiples para Apps de OAuth +## Creating multiple tokens for OAuth Apps -Puedes crear tokens múltiples para una combinación de usuario/aplicación/alcance para crear tokens para casos de uso específicos. +You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases. -Esto es útil si tu Aplicación de OAuth es compatible con un flujo de trabajo que utilice GitHub para registrarse y requiera solo información básica del usuario. Otro flujo de trabajo podría requerir acceso a los repositorios privados del usuario. Al utilizar tokens múltiples, tu App de OAuth podrá llevar a cabo el flujo web para cada caso de uso, solicitando únicamente los alcances que necesite. Si un usuario utiliza tu aplicación únicamente para registrarse, nunca se les solicitará otorgar acceso a tu App de OAuth para sus repositorios privados. +This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories. {% data reusables.apps.oauth-token-limit %} {% data reusables.apps.deletes_ssh_keys %} -## Dirigir a los usuarios para revisar su acceso +## Directing users to review their access -Puedes vincular a la información de autorización para una App de OAuth para que los usuarios puedan revisar y revocar sus autorizaciones de la aplicación. +You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations. -Para crear este vínculo, necesitarás el `client_id` de tus Apps de Oauth, el cual recibiste de GitHub cuando registraste la aplicación. +To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application. ``` {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id @@ -321,17 +326,17 @@ Para crear este vínculo, necesitarás el `client_id` de tus Apps de Oauth, el c {% tip %} -**Tip:** Para aprender más acerca de los recursos a los cuales puede acceder tu App de OAuth para un usuario, consulta la sección "[Descubrir recursos para un usuario](/rest/guides/discovering-resources-for-a-user)". +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} -## Solución de problemas +## Troubleshooting -* "[Solución de problemas para errores de solicitud de autorización](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" -* "[Solución de problemas para errores de solicitud de tokens de acceso para Apps de OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -{% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Errores de flujo de dispositivo](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} -* "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" +* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" +{% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} -## Leer más +## Further reading -- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index eafc29f6ab..c8409c004a 100644 --- a/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -1,5 +1,5 @@ --- -title: Hacer pública o privada a una GitHub App +title: Making a GitHub App public or private intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps/ @@ -15,27 +15,29 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Administrar la visbilidad de las apps +shortTitle: Manage app visibility --- +For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)." -Para obtener información sobre la autenticación, consulta la sección "[Autenticarse con las GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". +## Public installation flow -## Flujo de instalación pública +Public installation flows have a landing page to enable other people besides the app owner to install the app in their repositories. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)." -Los flujos de las instalaciones públicas tienen una página de llegada para habilitar a otras personas además del propietario de la app para que la instalen en sus repositorios. Este enlace se proprociona en el campo "enlace público" cuando configuras tu GitHub App. Para obtener más información, consulta la sección "[Instalar las GitHub Apps](/apps/installing-github-apps/)". +## Private installation flow -## Flujo de instalación privada +Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner. -Los flujos de instalación privada permiten que solo el propietario de la GitHub App pueda instalarla. Aún así, existirá información limitada sobre la GitHub App en una página pública, pero el botón de **Instalar** solo estará disponible para los administradores de la organización o para la cuenta de usuario si dicha GitHub App le pertenece a una cuenta individual. Las GitHub Apps {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}privadas {% else %}privadas (también conocidas como internas){% endif %} solo pueden instalarse en la cuenta de usuario u organización del propietario. +## Changing who can install your GitHub App -## Cambiar el quién puede instalar tu GitHub App - -Para cambiar quién puede instalar una GitHub App: +To change who can install the GitHub App: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -3. Selecciona la GitHub App cuya opción de instalación quieras cambiar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) +3. Select the GitHub App whose installation option you want to change. +![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Hacer pública** o **Hacer{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}privada{% else %}interna{% endif %}**. ![Botón para cambiar la opción de instalación para tu GitHub App](/assets/images/github-apps/github_apps_make_public.png) -6. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Sí, hacer esta GitHub App pública** o **Sí, hacer esta GitHub App {% ifversion fpt or ghes < 3.2 or ghec %}interna{% else %}privada{% endif %}**. ![Botón para confirmar el cambio de tu opción de instalación](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 or ghae or ghec %}private{% else %}internal{% endif %}**. +![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) +6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 or ghec %}internal{% else %}private{% endif %}**. +![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 97db301474..1905ce8446 100644 --- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -1,6 +1,6 @@ --- -title: Escribir la descripción de un listado para tu app -intro: 'Para [Listar tu app](/marketplace/listing-on-github-marketplace/) en {% data variables.product.prodname_marketplace %}, necesitarás escribir una descripción de ésta y proporcionar imágenes que se apeguen a los lineamientos de GitHub.' +title: Writing a listing description for your app +intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.' redirect_from: - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/ - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/ @@ -16,183 +16,181 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Escribir listas de descripciones +shortTitle: Write listing descriptions --- +Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing. -Aquí te mostramos los lineamientos de los campos que necesitas llenar en la sección **Listar descripción** del borrador de tu listado. +## Naming and links -## Nomencltura y enlaces +### Listing name -### Nombre del listado +Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing account on {% data variables.product.product_location %}, unless the name is your own user or organization name. -El nombre de tu listado aparecerá en la [página inicial de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). El nombre se limita a 255 caracteres y puede ser diferente que aquél de tu app. Your listing cannot have the same name as an existing account on {% data variables.product.product_location %}, unless the name is your own user or organization name. +### Very short description -### Descripción muy corta +The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). -La comunidad verá la descripción "muy corta" debajo del nombre de tu app en la [página principal de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png) -![Descripción corta de la app en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png) +#### Length -#### Longitud +We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly. -Te remcomendamos mantener un largo de 40 a 80 caracteres para las descripciones cortas. Aunque se te permite utilizar más caracteres, las descripciones concisas son más fáciles de leer y más rápidas de entender para los clientes. +#### Content -#### Contenido +- Describe the app’s functionality. Don't use this space for a call to action. For example: -- Describe la funcionalidad de la app. No utilices este espaccio para un llamado a la acción. Por ejemplo: + **DO:** Lightweight project management for GitHub issues - **RECOMENDADO:** Una administración de proyectos ligera para los informes de problemas de GitHub + **DON'T:** Manage your projects and issues on GitHub - **NO RECOMENDADO:** Administración de proyectos e informes de problemas en GitHub + **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_ - **Tip:** Pon los verbos en tercera persona del singular en las llamadas a la acción para convertirlas en una descripción aceptable: _Administra tus proyectos e informes de problemas en GitHub_ +- Don’t repeat the app’s name in the description. -- No repitas el nombre de la app en la descripción. + **DO:** A container-native continuous integration tool - **RECOMENDADO:** Una herramienta de integración contínua nativa para el contenedor + **DON'T:** Skycap is a container-native continuous integration tool - **NO RECOMENDADO:** Skycap es una herramienta de integración contínua nativa para el contenedor +#### Formatting -#### Formato +- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns. -- Apégate siempre al uso de mayúsculas correcto en las oraciones. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios. +- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence. -- No uses puntuación al final de tu descripción corta. Las descripciones cortas no deben incluir oraciones completas, y en definitiva, no deben incluir más de una oración. +- Only capitalize proper nouns. For example: -- Usa mayúscula inicial únicamente en nombres propios. Por ejemplo: + **DO:** One-click delivery automation for web developers - **RECOMENDADO:** Automatización de entrega en un solo click para desarrolladores web + **DON'T:** One-click delivery automation for Web Developers - **NO RECOMENDADO:** Automatización de entrega en un solo click para Desarrolladores Web +- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- Utiliza siempre una [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas. +- Avoid referring to the GitHub community as "users." -- Evita referirte a la comunidad de GitHub como "usuarios". + **DO:** Create issues automatically for people in your organization - **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización + **DON'T:** Create issues automatically for an organization's users - **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización +- Avoid acronyms unless they’re well established (such as API). For example: -- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). Por ejemplo: + **DO:** Agile task boards, estimates, and reports without leaving GitHub - **RECOMENDADO:** Tableros de tareas ágiles, estimados y reportes sin salir de GitHub + **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI - **NO RECOMENDADO:** Tableros de tareas ágiles, estimados, y reportes sin dejar la IU de GitHub +### Categories -### Categorías +Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app. -Las apps en {% data variables.product.prodname_marketplace %} se pueden mostrar por categoría. Selecciona la categoría que describa mejor la funcionalidad principal de tu app en el menú desplegable de **Categoría principal** y, opcionalmente, selecciona una **Categoría secundaria** si es que describe mejor a tu app. +### Supported languages -### Lenguajes compatibles +If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional. -Si tu app funciona únicamente con lenguajes específicos, selecciona hasta 10 lenguajes de programación que sean compatibles con ella. Estos lenguajes se muestran en la página del listado de {% data variables.product.prodname_marketplace %} de tu app. Este campo es opcional. +### Listing URLs -### Listar las URL +**Required URLs** +* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries. +* **Privacy policy URL:** The web page that displays your app's privacy policy. +* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App. -**URL Requeridas** -* **URL de servicio al cliente:** La URL de una página web a la que llegarán tus clientes cuando tienen preguntas de la cuenta, producto o soporte técnico. -* **URL de la política de privacidad:** La página web que muestra la política de privacidad de tu app. -* **URL de la instalación:** Este campo se muestra únicamente para las apps de OAuth. (Las GitHub Apps no utilizan esta URL porque utilizan la URL de configuración opcional de la página de su página de configuración). Cuando un cliente compra tu App de OAuth, GitHub redireccionará a los clientes a la URL de la instalación después de que la instalen. Necesitarás redirigir a los clientes a `https://github.com/login/oauth/authorize` para comenzar el flujo de autorizaciones de OAuth. Consulta la sección "[Compras nuevas de Apps de OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para recibir más detalles al respecto. Omite este campo si estás listando una GitHub App. +**Optional URLs** +* **Company URL:** A link to your company's website. +* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance. +* **Documentation URL:** A link to documentation that teaches customers how to use your app. -**URL opcionales** -* **URL de la empresa:** Un enlace al sitio web de tu empresa. -* **URL de estado:** Un enlace a la página web que muestra el estado de tu app. Las páginas de estado incluyen reportes de incidentes actuales y en forma de historial, el estado de tiempo activo de la aplicación web, y los periodos programados de mantenimiento. -* **URL de Documentación:** Un enlace a la documentación que muestra a los clientes cómo utilizar tu app. +## Logo and feature card -## Logo y tarjeta de características +{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps. -{% data variables.product.prodname_marketplace %} muestra todos los listados con un logo de imagen cuadrada dentro de una insignia circular para distinguir a las apps visualmente. +![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png) -![Imágenes de logo e insignia en GitHub marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png) +A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card. -Una tarjeta de características consiste en el logo, nombre e imagen personalizada de fondo para tu app, la cual captura la personalidad de ésta. {% data variables.product.prodname_marketplace %} muestra esta tarjeta si tu app es una de las cuatro apps que se presentan aleatoriamente en la parte superior de la [página principal](https://github.com/marketplace). Cada descripción muy corta de las apps se muestra debajo de su tarjeta de características. +![Feature card](/assets/images/marketplace/marketplace_feature_card.png) -![Tarjeta de características](/assets/images/marketplace/marketplace_feature_card.png) +As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card. -En medidad que subas imágenes y selecciones los colores, tu borrador de listado de {% data variables.product.prodname_marketplace %} mostrará una vista previa de tu logo y de tu tarjeta de características. +#### Guidelines for logos -#### Lineamientos para los logos +You must upload a custom image for the logo. For the badge, choose a background color. -Debes cargar una imagen personalizada para el logo. Para el caso de la insignia, elige un color de fondo. +- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published. +- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center. +- For best results, upload a logo image with a transparent background. +- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image. +- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens. -- Carga una imagen de logo que tenga por lo menos 200 pixeles por 200 pixeles para que éste no tenga que escalarse ascendentemente cuando se publique tu listado. -- Los logos se cortarán en forma de cuadrado. Te recomendamos cargar un archivo de imagen cuadrado con tu logo en el centro. -- Para obtener los mejores resultados, carga una imagen de logo con un fondo transparente. -- Para darle la apariencia contínua a la insignia, elige un color de fondo que empate con el color (o con la transparencia) de tu imagen de logo. -- Evita utilizar las imágenes de logo que tienen texto o palabras. Los logos con texto no se escalan bien en pantallas pequeñas. +#### Guidelines for feature cards -#### Lineamientos para las tarjetas de características +You must upload a custom background image for the feature card. For the app's name, choose a text color. -Debes cargar una imagen personalizada de fondo para la tarjeta de características. Elige el color del texto para el nombre de la app. +- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality. +- Background image measures 965 pixels x 482 pixels (width x height). +- Choose a text color for your app's name that shows up clearly over the background image. -- Utiliza un patrón o textura en la imagen de fondo para dar a tu tarjeta una identidad visual específica y ayudar a que resalten contra el fondo oscuro de la página de inicio de {% data variables.product.prodname_marketplace %}. Las tarjetas de caracetrísticas capturan la personalidad de la marca de tu app. -- La imagen de fondo mide 065 pixeles x 482 pixeles (ancho x alto). -- Elige un color de texto para el nombre de tu app, el cual se muestre claramente sobre la imagen de fondo. +## Listing details -## Detalles del listado +To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description." -Para obtener la página de llegada de tu app, da clic en su nombre desde la página principal de {% data variables.product.prodname_marketplace %} o desde su página de categoría. La página de llegada muestra una descripción más larga de tu app, la cual incluye dos partes: una "Descripción de introducción" y una "Descripción detallada". +Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page. -Tu "Descripción de introducción" se muestra en la parte superior de la página de llegada de {% data variables.product.prodname_marketplace %} para tu app. +![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png) -![Descripción de introducción en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png) +Clicking **Read more...**, displays the "Detailed description." -El dar clic en **Leer más...** mostrará la "Descripción detallada". +![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png) -![Descripción detallada en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png) +Follow these guidelines for writing these descriptions. -Sigue estos lineamientos para escribir estas descripciones. +### Length -### Longitud +We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly. -Te recomendamos escribir un resumen de alto nivel que se componga de una o dos oraciones de entre 150 y 250 caracteres en el campo "Descripción de introducción" cuando [listes tu aplicación](/marketplace/listing-on-github-marketplace/). Aunque se te permite utilizar más caracteres, los resúmenes concisos son más fáciles de leer y más rápidas de entender para los clientes. +You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description. -Puedes agregar más información en el campo opcional "Descripción detallada". Encuentras esta descripción al dar clic en **Leer más...** debajo de la descripción de introducción en la página de llegada de tu app. Una descripción detallada consiste en 3-5 [propuestas de valor](https://en.wikipedia.org/wiki/Value_proposition) con 1-2 oraciones que se describen una a la otra. Puedes utilizar hasta 1,000 caracteres para esta descripción. +### Content -### Contenido +- Always begin introductory descriptions with your app's name. -- Inicia siempre con el nombre de tu aplicación en las descripciones de introducción. +- Always write descriptions and value propositions using the active voice. -- Escribe siempre las descripciones y propuestas de valor utilizando la voz activa. +### Formatting -### Formato +- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns. -- Utiliza siempre las mayúsculas adecuadamente en las oraciones de los títulos para las propuestas de valor. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios. +- Use periods in your descriptions. Avoid exclamation marks. -- Utiliza puntos en tus descripciones. Evita los signos de admiración. +- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence. -- No utilices signos de puntuación al final de tus títulos para las propuestas de valor. Los títulos de propuestas de valor no deben incluir oraciones completas ni más de una oración. +- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example: -- Para cada propuesta de valor, incluye un título seguido de un párrafo de descripción. Da formato al título como un [encabezado nivel tres](/articles/basic-writing-and-formatting-syntax/#headings) utilizando lenguaje de marcado (Markdown). Por ejemplo: + ### Learn the skills you need + GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. - ### Adquiere las habilidades que necesitas +- Only capitalize proper nouns. - GitHub Learning Lab te puede ayudar a aprender cómo utilizar GitHub, a comunicarte de forma más efectiva con el lenguaje de Markdown, a gestionar conflictos de fusión, y más. +- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- Usa mayúscula inicial únicamente en nombres propios. +- Avoid referring to the GitHub community as "users." -- Utiliza siempre la [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas. + **DO:** Create issues automatically for people in your organization -- Evita referirte a la comunidad de GitHub como "usuarios". + **DON'T:** Create issues automatically for an organization's users - **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización +- Avoid acronyms unless they’re well established (such as API). - **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización +## Product screenshots -- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). +You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page. -## Impresiones de pantalla de los productos +### Guidelines for screenshots -Puedes cargar hasta cinco impresiones de pantalla para tu app para que se muestren en su página de llegada. Agrega una captura opcional a cada impresión de pantalla para proporcionar contexto. Después de cargar tus impresiones de pantalla, puedes arrastrarlas para que tomen el órden en el que quieras que se muestren dentro de la página de llegada. +- Images must be of high resolution (at least 1200px wide). +- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next. +- Show as much of the user interface as possible so people can see what your app does. +- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes. +- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots. +- Captions are most effective when they are short and snappy. -### Lineamientos para las impresiones de pantalla - -- Las imágenes deben tener resolución alta (por lo menos 1200px de ancho). -- Todas las imágenes deben tener la misma altura y ancho (proporción de aspecto) para evitar los saltos de página cuando las personas den clic de una imagen a otra. -- Muestra tanto de la interface de usuario como sea posible para que las personas pueden ver lo que hace tu app. -- Cuando tomes una impresión de pantalla de tu app en un buscador, incluye solamente el contenido en la ventana a mostrar. Evita incluir la barra de dirección, la barra de título o los iconos de la barra de herramientas, ya que estos no se escalan bien cuando se miran desde pantallas más pequeñas. -- GitHub muestra las impresiones de pantalla que cargues en una caja dentro de la página de llegada de tu app, así que no necesitas agregar cajas o márgenes al rededor de tus impresiones de pantalla. -- Las capturas son más efectivas cuando son cortas y concisas. - -![Imagen de impresión de pantalla en GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png) +![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md index d3339f1770..999f345c3d 100644 --- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -1,6 +1,6 @@ --- -title: Planes de precios para las apps de GitHub Marketplace -intro: 'Los planes de precios te permiten darle a tu app diferentes recursos o niveles de servicio. Puedes ofrecer hasta 10 planes de precios en tu listado de {% data variables.product.prodname_marketplace %}.' +title: Pricing plans for GitHub Marketplace apps +intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.' redirect_from: - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/ - /marketplace/selling-your-app/github-marketplace-pricing-plans @@ -10,51 +10,50 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Planes de precios para las apps +shortTitle: Pricing plans for apps --- +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to apps published by verified publishers. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -Los planes de precios de {% data variables.product.prodname_marketplace %} pueden ser gratuitos, de tasa fija, o por unidad. Los precios se configuran, muestran y procesan en dólares estadounidenses. Los planes de pago se restringen para las apps que publican los publicadores verificados. Para obtener más información acerca de cómo convertirse en un publicador verificado, consulta la sección "[Solicitar una verificación de publicador para tu organización](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. 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)." -Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. No tienes que escribir código para realizar las transacciones de facturación, pero tendrás que administrar los eventos desde la API de {% data variables.product.prodname_marketplace %}. 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)". +If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. -Si la app que estás listando en {% data variables.product.prodname_marketplace %} tiene opciones de plan múltiples, puedes configurar los planes de precios correspondientes. Por ejemplo, si tu app tiene dos opciones de plan, u plan de código abierto y un plan profesional, puedes configurar un plan de precios gratuito para tu plan de código abierto y un plan de tasa fija para tu plan profesional. Cada listado de {% data variables.product.prodname_marketplace %} debe tener un precio mensual y anual para cada plan que se liste. - -Para obtener más información sobre cómo crear un plan de precios, consulta la sección "[Configurar un plan de precios del listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". +For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." {% data reusables.marketplace.free-plan-note %} -## Tipos de planes de precios +## Types of pricing plans -### Planes gratuitos +### Free pricing plans {% data reusables.marketplace.free-apps-encouraged %} -Los planes gratuitos no tienen costo alguno para los usuarios. Si configuras un plan de precios gratuito, no puedes cobrar a los usuarios que elijan dicho plan por utilizar tu app. Puedes crear planes tanto de pago como gratuitos para tu listado. +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -Todas las apps necesitan administrar los eventos de las compras nuevas y de las cancelaciones. Aquellas apps que solo tengan planes gratuitos no necesitan administrar los eventos de las pruebas gratuitas, mejoras y retrocesos. 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)". +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. 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)." -Si agregas un plan de pago a una app que ya esté listada en {% data variables.product.prodname_marketplace %} como un servicio gratuito, necesitarás solicitar una verificación para dicha app y pasar por un proceso de integración financiera. +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. -### Planes de pago +### Paid pricing plans -Hay dos tipos de planes de pago: +There are two types of paid pricing plan: -- Los planes de pago de tasa fija cobran una cantidad fija mensual o anualmente. +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. -- Los planes de pago por unidad cobran una cantidad fija ya sea mensual o anual por el tipo de unidad que especifiques. Una "unidad" puede ser lo que tu escojas (por ejemplo, un usuario, una plaza, una persona). +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). -Puede que también quieras ofrecer pruebas gratuitas. Estas proporcionan periodos de prueba gratuitos de 14 días en aplicaciones de GitHub y de OAuth. Cuandoconfiguras un plan de precios en Marketplace, puedes seleccionar la opción de proporcionar un plan gratuito para los planes de tasa fija o o de costo por unidad. +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. -## Periodos de prueba gratuitos +## Free trials -Los clientes pueden iniciar un periodo de prueba gratuto para cualquier plan de pago en una lista de Marketplace que incluya pruebas gratuitas. Sin embargo, los clientes no pueden crear más de una prueba gratuita por producto de marketplace. +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. -Los periodos de prueba gratuitos tienen una longitud fija de 14 días. Se les notifica a los clientes 4 días antes del fin de su periodo de pruebas gratuito (en el día 11 del este periodo) sobre la mejora que se hará a su plan. Al final del periodo de pruebas gratuito, los clientes se matricularán automáticamente en el plan desde el cual estaban generando el periodo gratuito en caso de que no lo cancelen. +Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -Para obtener más información, consulta la sección "[Administrar las compras nuevas y las pruebas gratuitas](/developers/github-marketplace/handling-new-purchases-and-free-trials/)". +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)." {% note %} -**Nota:** GitHub espera que borres cualquier dato privado del cliente dentro de los primeros 30 días después de que se cancela una prueba, iniciando con la recepción del evento de cancelación. +**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event. {% endnote %} diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md index aff45966e6..09d39b815f 100644 --- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md +++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- -title: Eventos de webhook para la API de GitHub Marketplace -intro: 'Una app de {% data variables.product.prodname_marketplace %} recibe información acerca de los cambios en el plan de un usuario desde el webhook del evento de compra en Marketplace. Un evento de compra de marketplace se activa cuando un usuario compra, cancela o cambia su plan de pago.' +title: Webhook events for the GitHub Marketplace API +intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ @@ -11,66 +11,65 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Eventos de webhook +shortTitle: Webhook events --- +## {% data variables.product.prodname_marketplace %} purchase webhook payload -## Carga útil del webhook de compras en {% data variables.product.prodname_marketplace %} +Webhooks `POST` requests have special headers. See "[Webhook delivery headers](/webhooks/event-payloads/#delivery-headers)" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub. -Las solicitudes de `POST` de los webhooks tienen encabezados especiales. Consulta la sección "[Encabezados de entrega de Webhooks](/webhooks/event-payloads/#delivery-headers)" para encontrar más detalles. GitHub no reenvía los intentos fallidos de entrega. Asegúrate de que tu app pueda recibir toda la carga útil del webhook que envíe GitHub. - -Las cancelaciones y disminuciones de categoría toman efecto el primer día del siguiente ciclo de facturación. Los eventos para las cancelaciones y disminuciones de categoría se envían cuando el nuevo plan entre en vigor al inicio del siguiente ciclo de facturación. Los eventos para las nuevas compras y mejoras de categoría comienzan inmediatamente. Utiliza `effective_date` en la carga útil del webhook para determinar cuándo comenzará un cambio. +Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the `effective_date` in the webhook payload to determine when a change will begin. {% data reusables.marketplace.marketplace-malicious-behavior %} -Cada carga útil de webhook de una `marketplace_purchase` tendrá la siguiente información: +Each `marketplace_purchase` webhook payload will have the following information: -| Clave | Type | Descripción | -| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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` | `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 %}. | +Key | Type | Description +----|------|------------- +`action` | `string` | The action performed to generate the webhook. Can be `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, or `changed`. For more information, see the example webhook payloads below. **Note:** The `pending_change` and `pending_change_cancelled` payloads contain the same keys as shown in the [`changed` payload example](#example-webhook-payload-for-a-changed-event). +`effective_date` | `string` | The date the `action` becomes effective. +`sender` | `object` | The person who took the `action` that triggered the webhook. +`marketplace_purchase` | `object` | The {% data variables.product.prodname_marketplace %} purchase information. -El objeto `marketplace_purchase` tiene las siguientes claves: +The `marketplace_purchase` object has the following keys: -| Clave | Type | Descripción | -| -------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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` | `objeto` | El plan que compra el `user` u `organization`. | +Key | Type | Description +----|------|------------- +`account` | `object` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint. +`billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. +`unit_count` | `integer` | Number of units purchased. +`on_free_trial` | `boolean` | `true` when the `account` is on a free trial. +`free_trial_ends_on` | `string` | The date the free trial will expire. +`next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. +`plan` | `object` | The plan purchased by the `user` or `organization`. -El objeto `plan` tiene las siguientes claves: +The `plan` object has the following keys: -| Clave | Type | Descripción | -| ------------------------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `número` | El identificador único para este plan. | -| `name (nombre)` | `secuencia` | El nombre del 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`. | -| `has_free_trial` | `boolean` | es `true` cuando este listado ofrece un periodo de prueba gratuito. | -| `unit_name` | `secuencia` | El nombre de la unidad. Si el modelo de precios no es `per-unit`, éste será `nil`. | -| `bullet` | `conjunto de secuencias` | Los nombres de los puntos configurados en el plan de precios. | +Key | Type | Description +----|------|------------- +`id` | `integer` | The unique identifier for this plan. +`name` | `string` | The plan's name. +`description` | `string` | This plan's description. +`monthly_price_in_cents` | `integer` | The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents. +`yearly_price_in_cents` | `integer` | The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 10000 cents. +`price_model` | `string` | The pricing model for this listing. Can be one of `flat-rate`, `per-unit`, or `free`. +`has_free_trial` | `boolean` | `true` when this listing offers a free trial. +`unit_name` | `string` | The name of the unit. If the pricing model is not `per-unit` this will be `nil`. +`bullet` | `array of strings` | The names of the bullets set in the pricing plan.
    -### Ejemplo de la carga útil de un webhook para un evento de `purchased` -Este ejemplo proporciona la carga útil del evento `purchased`. +### Example webhook payload for a `purchased` event +This example provides the `purchased` event payload. {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} -### Ejemplo de la carga útil de un webhook para un evento de `changed` +### Example webhook payload for a `changed` event -Los cambios en un plan incluyen mejoras y degradaciones. Este ejemplo representa las cargas útiles de los eventos `changed`,`pending_change`, y `pending_change_cancelled`. La acción identifica cuál de estos tres eventos ha ocurrido. +Changes in a plan include upgrades and downgrades. This example represents the `changed`,`pending_change`, and `pending_change_cancelled` event payloads. The action identifies which of these three events has occurred. {{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }} -### Ejemplo de carga útil del webhook para un evento de `cancelled` +### Example webhook payload for a `cancelled` event {{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }} diff --git a/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md index 4087a4efda..9fc83a14a9 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md +++ b/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md @@ -1,6 +1,6 @@ --- -title: Tipos de evento de GitHub -intro: 'Para la API de Eventos de {% data variables.product.prodname_dotcom %}, aprende acerca de cada tipo de evento, la acción que los desencadena en {% data variables.product.prodname_dotcom %}, y las propiedades exclusivas de cada evento.' +title: GitHub event types +intro: 'For the {% data variables.product.prodname_dotcom %} Events API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /v3/activity/event_types @@ -13,37 +13,36 @@ versions: topics: - Events --- - -La API de eventos puede devolver diferentes tipos de ventos que se activan de acuerdo a la actividad en GitHub. Cada respuesta de evento contiene propiedades compartidas, pero tiene un objeto único de `payload` que se determina por su tipo de evento. Las [propiedades comunes del objeto de los eventos](#event-object-common-properties) describen aquellas propiedades que comparten todos los eventos, y cada tipo de evento describe las propiedades de la `payload` que son exclusivas para éste. +The Events API can return different types of events triggered by activity on GitHub. Each event response contains shared properties, but has a unique `payload` object determined by its event type. The [Event object common properties](#event-object-common-properties) describes the properties shared by all events, and each event type describes the `payload` properties that are unique to the specific event. {% ifversion fpt or ghec %} {% endif %} -## Propiedades comunes del objeto de los eventos +## Event object common properties -Los objetos de los eventos que se devuelven de las terminales de la API de Eventos tienen la misma estructura. +The event objects returned from the Events API endpoints have the same structure. -| Nombre del atributo de la API del Evento | Descripción | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | Identificador único para el evento. | -| `type` | El tipo de evento. Los eventos utilizan PascalCase para el nombre. | -| `actor (actor)` | El usuario que activó el evento. | -| `actor.id` | El identificador único para el actor. | -| `actor.login` | El nombre de usuario para el actor. | -| `actor.display_login` | El formato de visualización específico para el nombre de usuario. | -| `actor.gravatar_id` | El identificador único del perfil de Gravatar para el actor. | -| `actor.url` | La URL de la API de REST que se utiliza para recuperar el objeto del usuario, el cual incluye información adicional del usuario. | -| `actor.avatar_url` | La URL de la imagen de perfil del actor. | -| `repo` | El objeto del repositorio en donde ocurrió el evento. | -| `repo.id` | El identificador único del repositorio. | -| `repo.name` | El nombre del repositorio, el cual incluye también al nombre del propietario. Por ejemplo, el nombre del repositorio `hello-world`, cuyo propietario es la cuenta de usuario `octocat`, es `octocat/hello-world`. | -| `repo.url` | La URL de la API de REST que se utiliza para recuperar el objeto del repositorio, el cual incluye información adicional sobre dicho repositorio. | -| `payload` | El objeto de la carga útil del evento que es exclusivo para el tipo de evento. En el siguiente ejemplo puedes ver el tipo de evento para el objeto de `payload` de la API de eventos. | +| Event API attribute name | Description | +|--------------------------|-------------| +| `id` | Unique identifier for the event. | +| `type` | The type of event. Events uses PascalCase for the name. | +| `actor` | The user that triggered the event. | +| `actor.id` | The unique identifier for the actor. | +| `actor.login` | The username of the actor. | +| `actor.display_login` | The specific display format of the username. | +| `actor.gravatar_id` | The unique identifier of the Gravatar profile for the actor. | +| `actor.url` | The REST API URL used to retrieve the user object, which includes additional user information. | +| `actor.avatar_url` | The URL of the actor's profile image. | +| `repo` | The repository object where the event occurred. | +| `repo.id` | The unique identifier of the repository. | +| `repo.name` | The name of the repository, which includes the owner and repository name. For example, `octocat/hello-world` is the name of the `hello-world` repository owned by the `octocat` user account. | +| `repo.url` | The REST API URL used to retrieve the repository object, which includes additional repository information. | +| `payload` | The event payload object is unique to the event type. See the event type below for the event API `payload` object. | -### Ejemplo con el objeto de evento WatchEvent +### Example WatchEvent event object -Este ejemplo te muestra el formato de la respuesta de [WatchEvent](#watchevent) cuando utilizas la [API de Eventos](/rest/reference/activity#events). +This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). ``` HTTP/2 200 @@ -88,7 +87,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.commit_comment_properties %} @@ -98,7 +97,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.create_properties %} @@ -108,7 +107,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.delete_properties %} @@ -118,7 +117,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.fork_properties %} @@ -128,7 +127,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.gollum_properties %} @@ -138,7 +137,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.issue_comment_webhook_properties %} {% data reusables.webhooks.issue_comment_properties %} @@ -149,7 +148,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.issue_event_api_properties %} {% data reusables.webhooks.issue_properties %} @@ -160,7 +159,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.member_event_api_properties %} {% data reusables.webhooks.member_properties %} @@ -169,9 +168,9 @@ Link: ; rel="next", ## PublicEvent {% data reusables.webhooks.public_short_desc %} -### Objeto de `payload` del evento +### Event `payload` object -Este evento devuelve un objeto de `payload` vacío. +This event returns an empty `payload` object. {% endif %} ## PullRequestEvent @@ -179,7 +178,7 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} @@ -190,13 +189,13 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object -| Clave | Type | Descripción | -| ---------------------- | ----------- | -------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`. | -| `solicitud_extracción` | `objeto` | La solicitud de cambios a la cual pertenece la revisión. | -| `revisar` | `objeto` | La revisión que se afectó. | +Key | Type | Description +----|------|------------- +`action` | `string` | The action that was performed. Can be `created`. +`pull_request` | `object` | The pull request the review pertains to. +`review` | `object` | The review that was affected. ## PullRequestReviewCommentEvent @@ -204,7 +203,7 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.pull_request_review_comment_event_api_properties %} {% data reusables.webhooks.pull_request_review_comment_properties %} @@ -215,24 +214,24 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object -| Clave | Type | Descripción | -| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `push_id` | `número` | Identificador único para la carga. | -| `tamaño` | `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`. | -| `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]` | `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. | -| `commits[][distinct]` | `boolean` | Si la confirmación es distinta de cualquier otra que se haya subido antes. | +Key | Type | Description +----|------|------------- +`push_id` | `integer` | Unique identifier for the push. +`size`|`integer` | The number of commits in the push. +`distinct_size`|`integer` | The number of distinct commits in the push. +`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. +`head`|`string` | The SHA of the most recent commit on `ref` after the push. +`before`|`string` | The SHA of the most recent commit on `ref` before the push. +`commits`|`array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) +`commits[][sha]`|`string` | The SHA of the commit. +`commits[][message]`|`string` | The commit message. +`commits[][author]`|`object` | The git author of the commit. +`commits[][author][name]`|`string` | The git author's name. +`commits[][author][email]`|`string` | The git author's email address. +`commits[][url]`|`url` | URL that points to the commit API resource. +`commits[][distinct]`|`boolean` | Whether this commit is distinct from any that have been pushed before. ## ReleaseEvent @@ -240,7 +239,7 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.release_event_api_properties %} {% data reusables.webhooks.release_properties %} @@ -250,7 +249,7 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.sponsorship_short_desc %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.sponsorship_event_api_properties %} {% data reusables.webhooks.sponsorship_properties %} @@ -262,6 +261,6 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} -### Objeto de `payload` del evento +### Event `payload` object {% data reusables.webhooks.watch_properties %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 94ac6cf87b..d02f24f4a3 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -100,7 +100,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. > } ``` -{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## branch_protection_rule Activity related to a branch protection rule. For more information, see "[About branch protection rules](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)." @@ -190,7 +190,7 @@ Key | Type | Description {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`sender` | `object` | If the `action` is `reopened_by_user` or `closed_by_user`, the `sender` object will be the user that triggered the event. The `sender` object is {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}empty{% endif %} for all other actions. +`sender` | `object` | If the `action` is `reopened_by_user` or `closed_by_user`, the `sender` object will be the user that triggered the event. The `sender` object is {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae %}`github-enterprise`{% else %}empty{% endif %} for all other actions. ### Webhook payload example diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index 412aba4134..3d9668f167 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -1,42 +1,42 @@ --- -title: Integrar a GitHub Classroom con un IDE -shortTitle: Integrar con un IDE -intro: 'Puedes preconfigurar un ambiente de desarrollo integrado (IDE) compatible para las tareas que crees en {% data variables.product.prodname_classroom %}.' +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' +permissions: Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %} redirect_from: - /education/manage-coursework-with-github-classroom/online-ide-integrations - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide --- +## About integration with an IDE -## Acerca de la integración con un IDE +{% data reusables.classroom.about-online-ides %} -{% data reusables.classroom.about-online-ides %} +After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. -Después de que un alumno acepta una tarea con un IDE, el archivo README en su repositorio de tareas contendrá un botón para abrir dicha tarea en el IDE. El alumno puede comenzar a trabajar de inmediato y no se requiere alguna configuración adicional. +## Supported IDEs -## IDE compatibles +{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE. -{% data variables.product.prodname_classroom %} es compatible con los siguientes IDE. Puedes aprender más sobre la experiencia del alumno para cada IDE. +| IDE | More information | +| :- | :- | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | -| IDE | Más información | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Microsoft MakeCode Arcade | "[Acerca de utilizar MakeCode Arcade con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | -| Visual Studio Code | La [extensión de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) en el Mercado de Visual Studio | +We know cloud IDE integrations are important to your classroom and are working to bring more options. -Sabemos que las integraciones con IDE en la nube son importantes para tu aula y estamos trabajando para traerte más opciones. +## Configuring an IDE for an assignment -## Configurar un IDE para una tarea +You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." -Puedes elegir el IDE que te gustaría utilizar para una tarea cuando la crees. Para aprender cómo crear una tarea nueva que utilice un IDE, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". +## Authorizing the OAuth app for an IDE -## Autorizar la App de OAuth para un IDE +The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization. -La primera vez que configuras una tarea con un IDE, deberás autorizar la App de OAuth para este en tu organización. +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." -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)" +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md index 100143c690..472a3fbbda 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -3,6 +3,7 @@ title: Connect a learning management system to GitHub Classroom intro: 'You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom.' versions: fpt: '*' +permissions: Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %} redirect_from: - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom - /education/manage-coursework-with-github-classroom/connect-to-lms diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index dd48d29d63..7654c97ba3 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -3,6 +3,7 @@ title: Create a group assignment intro: You can create a collaborative assignment for teams of students who participate in your course. versions: fpt: '*' +permissions: Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %} redirect_from: - /education/manage-coursework-with-github-classroom/create-group-assignments - /education/manage-coursework-with-github-classroom/create-a-group-assignment diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md index 579d598fd7..6e386bbbed 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -1,19 +1,19 @@ --- -title: Crear una tarea desde un repositorio de plantilla -intro: 'Puedes crear una tarea desde un repositorio de plantilla para proporcionar a tus alumnos código inicial, documentación y otros recursos.' +title: Create an assignment from a template repository +intro: 'You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students.' +permissions: Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %} versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments - /education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository -shortTitle: Repositorio de plantilla +shortTitle: Template repository --- +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." -Puedes utilizar un repositorio de plantilla en {% data variables.product.product_name %} como el código inicial de una tarea en {% data variables.product.prodname_classroom %}. Tu repositorio de plantilla puede contener código modelo, documentación y otros recursos para tus alumnos. Para obtener más información, consulta "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)". +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. -Para utilizar el repositorio de plantilla para tu tarea, éste debe pertenecer a tu organización, o su visibilidad debe ser pública. +## 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)" +- "[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)" diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md index a76f6beeba..085d2558c4 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md @@ -3,6 +3,7 @@ title: Create an individual assignment intro: You can create an assignment for students in your course to complete individually. versions: fpt: '*' +permissions: Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %} redirect_from: - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment - /education/manage-coursework-with-github-classroom/create-an-individual-assignment diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md index e08cd628d3..9d01bfbd28 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md @@ -1,7 +1,7 @@ --- title: Manage classrooms intro: 'You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}.' -permissions: Organization owners can manage a classroom for an organization. +permissions: Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %} versions: fpt: '*' redirect_from: diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md index 685fd98c1a..31eee9a49a 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md @@ -1,91 +1,101 @@ --- -title: Utiliza las calificaciones automáticas -intro: Puedes proporcionar retroalimentación automáticamente en las emisiones de código de tus alumnos si configuras las pruebas para que se ejecuten en el repositorio de tareas. +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. miniTocMaxHeadingLevel: 3 versions: fpt: '*' +permissions: Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %} redirect_from: - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers - /education/manage-coursework-with-github-classroom/use-autograding --- - -## Acerca de las calificaciones automáticas +## About autograding {% data reusables.classroom.about-autograding %} -Después de que un alumno acepte una tarea, en cada subida al repositorio de la misma, {% data variables.product.prodname_actions %} ejecuta comandos para tu prueba de calificaciones automáticas en un ambiente Linux que contiene el código más nuevo del alumno. {% data variables.product.prodname_classroom %} crea los flujos de trabajo necesarios para {% data variables.product.prodname_actions %}. No necesitas tener experiencia con las {% data variables.product.prodname_actions %} para utilizar las calificaciones automáticas. +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. -Puedes utiizar un marco de trabajo de prueba, ejecutar un comando personalizado, escribir pruebas de entrada/salida, o combinar varios métodos de pruebas. El ambiente de Linux para las calificaciones automáticas contienen muchas herramientas de software populares. Para obtener más información, consulta los detalles de la última versión de Ubuntu en "[Especificaciones para los ejecutores hospedados en {% data variables.product.company_short %}](/actions/reference/specifications-for-github-hosted-runners#supported-software)". +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." -Puedes ver un resumen de qué estudiantes están pasando las pruebas con calificación automática si navegas a la tarea en {% data variables.product.prodname_classroom %}. Una marca verde significa que el alumno está pasando todas las pruebas, la X roja significa que el alumno falló en algunas o todas las pruebas. Si otorgas puntos para una o más pruebas, entonces una burbuja mostrará la puntuación de éstas con base en la puntuación máxima posible para la tarea. +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. -![Resumen de una tarea con resultados de calificación automática](/assets/images/help/classroom/autograding-hero.png) +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) -## Métodos para calificar +## Grading methods -Hay dos métodos para calificar: pruebas de entrada/salida y pruebas de ejecución de comandos. +There are two grading methods: input/output tests and run command tests. -### Prueba de entrada/salida +### Input/output test -Una prueba de entrada/salida ejecuta un comando de configuración opcionalmente y proporciona una entrada estándar de un comando de prueba. {% data variables.product.prodname_classroom %} evalúa la salida del comando de prueba contra un resultado esperado. +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. -| Parámetro | Descripción | -|:---------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- | -| **Nombre de la prueba** | El nombre de la prueba para identificarla en las bitácoras | -| **Comando de configuración** | _Opcional_. Un comando a ejecutar antes de las pruebas, tal como una compilación o instalación | -| **Comando de ejecución** | El comando para ejecutar la prueba y generar una salida estándar para su evaluación | -| **Inputs** | Entrada estándar para el comando de ejecución | -| **Salida esperada** | La salida que quieres ver como estándar para el comando de ejecución | -| **Comparación** | El tipo de comparación entre el la salida del comando de ejecución y la salida esperada

    • **Included**: Pasa cuando la salida esperada aparece
      en cualquier parte dentro de la salida estándar del comando de ejecución
    • **Exact**: Pasa cuando la salida esperada es completamente idéntica
      a la salida estándar del comando de ejecución
    • **Regex**: Pasa si la expresión regular en la salida
      esperada coincide con la salida estándar del comando de ejecución
    | -| **Tiempo excedido** | En minutos, lo que tarda una prueba en ejecutarse antes de que resulte en un fallo | -| **Puntos** | _Opcional_. La cantidad de puntos que vale la prueba contra una puntuación total | +| Setting | Description | +| :- | :- | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

    • **Included**: Passes when the expected output appears
      anywhere in the standard output from the run command
    • **Exact**: Passes when the expected output is completely identical
      to the standard output from the run command
    • **Regex**: Passes if the regular expression in expected
      output matches against the standard output from the run command
    | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | -### Prueba de comando de ejecución +### Run command test -Una prueba de comando de ejecución ejecuta un comando de configuración y luego un comando de prueba. {% data variables.product.prodname_classroom %} verifica el estado de salida del comando de prueba. Un código de salida de `0` resultará en éxito y cualquier otro código de salida resultara en un fallo. +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. -{% data variables.product.prodname_classroom %} proporciona preajustes para un las pruebas de comandos de ejecución específicas de lenguaje para varios lenguajes de programación. Por ejemplo, la prueba de **ejecutar nodo** llena previamente el comando de configuración con `npm install` y el comando de prueba con `npm test`. +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. -| Parámetro | Descripción | -|:---------------------------- |:---------------------------------------------------------------------------------------------- | -| **Nombre de la prueba** | El nombre de la prueba para identificarla en las bitácoras | -| **Comando de configuración** | _Opcional_. Un comando a ejecutar antes de las pruebas, tal como una compilación o instalación | -| **Comando de ejecución** | El comando para ejecutar la prueba y generar un código de salida para evaluación | -| **Tiempo excedido** | En minutos, lo que tarda una prueba en ejecutarse antes de que resulte en un fallo | -| **Puntos** | _Opcional_. La cantidad de puntos que vale la prueba contra una puntuación total | +| Setting | Description | +| :- | :- | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | -## Configurar las pruebas de calificación automática para una tarea +## Configuring autograding tests for an assignment -Puedes agregar pruebas de calificación automática durante la creación de una tarea nueva. {% data reusables.classroom.for-more-information-about-assignment-creation %} +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} -Puedes agregar, editar o borrar las pruebas de calificación automática para una tarea existente. Si cambias las pruebas de calificación automática para una tarea existente, los repositorios de tareas existentes no se verán afectados. Un alumno o equipo debe aceptar la tarea y crear un repositorio de tareas nuevo para utilizar las pruebas nuevas. +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.assignments-click-pencil %} -1. En la barra lateral, da clic en **Calificaciones y retroalimentación**. !["Calificaciones y retroalimentación" a la izquierda de los puntos básicos de la tarea](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) -1. Agrega, edita o borra una prueba de calificación automática. - - Para agregar una prueba, debajo de "Agregar pruebas de calificación automática", selecciona el menú desplegable **Agregar prueba** y luego da clic en el método de calificación que quieras utilizar. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configura la prueba y luego da clic en **Guardar caso de prueba**. ![Botón de "Guardar caso de prueba" para una prueba de calificación automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png) - - Para editar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configura la prueba y luego da clic en **Guardar caso de prueba**. ![Botón de "Guardar caso de prueba" para una prueba de calificación automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png) - - Para borrar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Icono de cesta de basura para borrar una prueba de calificación automática](/assets/images/help/classroom/autograding-click-trash.png) -1. En la parte inferior de la página, da clic en **Actualizar tarea**. ![Botón de "Actualizar tarea" en la parte inferior de la página](/assets/images/help/classroom/assignments-click-update-assignment.png) +1. In the left sidebar, click **Grading and feedback**. + !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. + ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) + Configure the test, then click **Save test case**. + !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. + ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) + Configure the test, then click **Save test case**. + !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. + ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. + !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) -## Ver y descargar los resultados de las pruebas de autoevaluación +## Viewing and downloading results from autograding tests -### Descargar los resultados de autoevaluación +### Download autograding results -También puedes descargar un CSV de las puntuaciones de autoevaluación de tus alumnos a través del botón "Descargar". Esto generará un CSV de descarga que contiene un enlace al repositorio del alumno, a su manejador de {% data variables.product.prodname_dotcom %}, identificador de lista, marca de tiempo de emisión y puntuación de autoevaluación. +You can also download a CSV of your students' autograding scores via the "Download" button. This will generate and download a CSV containing a link to the student's repository, their {% data variables.product.prodname_dotcom %} handle, roster identifier, submission timestamp, and autograding score. -![Botón de "Descargar" seleccionado mostrando "Descargar las calificaciones resaltadas" y una opción adicional para "Descargar repositorios"](/assets/images/help/classroom/download-grades.png) +!["Download" button selected showing "Download grades highlighted" and an additional option to "Download repositories"](/assets/images/help/classroom/download-grades.png) -### Ver bitácoras individuales +### View individual logs {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-assignment-in-list %} -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)". +1. To the right of a submission, click **View test**. + !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." -## Leer más +## Further reading -- [Documentación de {% data variables.product.prodname_actions %}](/actions) +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index 4ebe5860b3..4d3f0a3309 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -1,96 +1,104 @@ --- -title: Utiliza la tarea inicial de Git y GitHub -intro: 'Puedes utilizar la tarea de inicio de Git & {% data variables.product.company_short %} para proporcionar a los alumnos un resumen de lo básic de Git y de {% data variables.product.company_short %}.' +title: Use the Git and GitHub starter assignment +intro: 'You can use the Git & {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.company_short %} fundamentals.' versions: fpt: '*' +permissions: Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %} redirect_from: - /education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment -shortTitle: Tarea de inicio +shortTitle: Starter assignment --- -La tarea inicial de Git & {% data variables.product.company_short %} es un curso prehecho que resume los puntos básicos de Git y de {% data variables.product.company_short %} y enlaza a los alumnos con recursos para aprender más sobre temas específicos. +The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics. -## Prerrequisitos +## Prerequisites {% data reusables.classroom.assignments-classroom-prerequisite %} -## Crear la tarea inicial +## Creating the starter assignment -### Si no hay tareas existentes en el aula +### If there are no existing assignments in the classroom -1. Inicia sesión en {% data variables.product.prodname_classroom_with_url %}. -2. Navegar a un aula. -3. En la pestaña de {% octicon "repo" aria-label="The repo icon" %} **Tareas**, haz clic en **Utilizar tarea de inicio**. +1. Sign into {% data variables.product.prodname_classroom_with_url %}. +2. Navigate to a classroom. +3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **Use starter assignment**.
    - Crear tu primera tarea + Creating your first assignment
    -### Si ya existen tareas en el aula +### If there already are existing assignments in the classroom -1. Inicia sesión en {% data variables.product.prodname_classroom_with_url %}. -2. Navegar a un aula. -3. En la pestaña de {% octicon "repo" aria-label="The repo icon" %}**Tareas**, haz clic en el enlace sobre el letrero azul. +1. Sign into {% data variables.product.prodname_classroom_with_url %}. +2. Navigate to a classroom. +3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link on the blue banner.
    - En el botón de 'Tarea nueva' + The 'New assignment' button
    -## Configurar lo básico para una tarea +## Setting up the basics for an assignment -Importa el curso de inicio en tu organización, nombra tu tarea, decide si quieres asignar una fecha límite y elige la visibilidad de los repositorios de la tarea. +Import the starter course into your organization, name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. -- [Importar la tarea](#importing-the-assignment) -- [Nombrar una tarea](#naming-an-assignment) -- [Asignar una fecha límita para una tarea](#assigning-a-deadline-for-an-assignment) -- [Elegir un tipo de tarea](#choosing-an-assignment-type) -- [Elegir un tipo de visibilidad para los repositorios de la tarea](#choosing-a-visibility-for-assignment-repositories) +- [Prerequisites](#prerequisites) +- [Creating the starter assignment](#creating-the-starter-assignment) + - [If there are no existing assignments in the classroom](#if-there-are-no-existing-assignments-in-the-classroom) + - [If there already are existing assignments in the classroom](#if-there-already-are-existing-assignments-in-the-classroom) +- [Setting up the basics for an assignment](#setting-up-the-basics-for-an-assignment) + - [Importing the assignment](#importing-the-assignment) + - [Naming the assignment](#naming-the-assignment) + - [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) + - [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) +- [Inviting students to an assignment](#inviting-students-to-an-assignment) +- [Next steps](#next-steps) +- [Further reading](#further-reading) -### Importar la tarea +### Importing the assignment -Primero necesitas improtar la tarea inicial de Git & {% data variables.product.product_name %} en tu organización. +You first need to import the Git & {% data variables.product.product_name %} starter assignment into your organization.
    - El botón de `importar la tarea` + The `Import the assignment` button
    -### Nombrar la tarea +### Naming the assignment -Para una tarea individual, {% data variables.product.prodname_classroom %} nombra los repositorios de acuerdo con su prefijo y con el nombre de usuario de {% data variables.product.product_name %} del alumno. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si nombras a una tarea "assingment-1" y el nombre de usuario del alumno en {% data variables.product.product_name %} es @octocat, entonces el nombre del repositorio de la tarea para @octocat será `assignment-1-octocat`. +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. {% data reusables.classroom.assignments-type-a-title %} -### Asignar una fecha límita para una tarea +### Assigning a deadline for an assignment {% data reusables.classroom.assignments-guide-assign-a-deadline %} -### Elegir un tipo de visibilidad para los repositorios de la tarea +### Choosing a visibility for assignment repositories -Los repositorios de una tarea pueden ser públicos o privados. Si utilizas repositorios privados, solo el alumno puede ver la retroalimentación que proporciones. Debajo de "Visibilidad del repositorio", selecciona una visibilidad. +The repositories for an assignment can be public or private. If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility. -Cuando termines, haz clic en **Continuar**. {% data variables.product.prodname_classroom %} creará la tarea y te llevará a la su página. +When you're done, click **Continue**. {% data variables.product.prodname_classroom %} will create the assignment and bring you to the assignment page.
    - Botón 'Continuar' + 'Continue' button
    -## Invitar a los alumnos a una tarea +## Inviting students to an assignment {% data reusables.classroom.assignments-guide-invite-students-to-assignment %} -Puedes ver si un alumno se unió al aula y aceptó o emitió una tarea en la pestaña de **Todos los alumnos** de la misma. {% data reusables.classroom.assignments-to-prevent-submission %} +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
    - Tarea individual + Individual assignment
    -La tarea inicial de Git & {% data variables.product.company_short %} solo se encuentra disponible para alumnos individuales y no para grupos. Una vez que creas la tarea, los alumnos pueden comenzar a trabajar en ella. +The Git & {% data variables.product.company_short %} starter assignment is only available for individual students, not for groups. Once you create the assignment, students can start work on the assignment. -## Pasos siguientes +## Next steps -- Haz tareas adicionales personalizadas para tu curso. Para obtener más información, consulta las secciones "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" y "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". +- Make additional assignments customized to your course. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" and "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." -## Leer más +## Further reading -- "[Utiliza {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" -- "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index e847237555..671697cc51 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,12 +1,12 @@ --- -title: Encontrar maneras para colaborar con el código abierto en GitHub -intro: 'Puedes encontrar maneras de contribuir a los proyectos de código abierto en {% data variables.product.product_location %} que te parezcan relevantes.' +title: Finding ways to contribute to open source on GitHub +intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.' permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - - /articles/where-can-i-find-open-source-projects-to-work-on/ - - /articles/finding-interesting-projects-on-github/ - - /articles/about-official-github-mirrors/ - - /articles/about-github-mirrors/ + - /articles/where-can-i-find-open-source-projects-to-work-on + - /articles/finding-interesting-projects-on-github + - /articles/about-official-github-mirrors + - /articles/about-github-mirrors - /articles/finding-open-source-projects-on-github - /github/getting-started-with-github/finding-open-source-projects-on-github - /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github @@ -16,42 +16,41 @@ versions: ghec: '*' topics: - Open Source -shortTitle: Contribuir al código abierto +shortTitle: Contribute to open source --- +## Discovering relevant projects -## Descubrir proyectos relevantes +If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." -Si hay un tema en particular que te interese, visita `github.com/topics/`. Por ejemplo, si te interesa el aprendizaje automático, puedes encontrar proyectos relevantes e informes de problemas iniciales si visitas https://github.com/topics/machine-learning. Puedes buscar temas populares si visitas [Temas](https://github.com/topics). También puedes buscar repositorios que empaten con algún tema que te interese. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." +If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe). -Si has tenido actividad en {% data variables.product.product_location %} recientemente, puedes encontrar recomendaciones personalizadas para proyectos e informes de problemas iniciales que se basen en tus contribuciones, estrellas y otras actividades previas en [Explore](https://github.com/explore). También puedes registrarte para el boletín Explore para recibir correos electrónicos sobre las oportunidades disponibles para colaborar con {% data variables.product.product_name %} de acuerdo a tus intereses. Para registrarte, consulta [Boletín Explore por correo](https://github.com/explore/subscribe). - -Mantente al tanto de las actividades recientes de los repositorios y personas que sigues en la sección "Toda la actividad" de tu tablero personal. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". +Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." {% data reusables.support.ask-and-answer-forum %} -## Encontrar informes de problemas iniciales +## Finding good first issues -Si ya sabes en qué proyecto quieres trabajar, puedes encontrar informes de problemas aptos para principiantes en ese repositorio si visitas `github.com///contribute`. Como ejemplo, puedes encontrar cómo realizar tu primera contribución a `electron/electron` en https://github.com/electron/electron/contribute. +If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com///contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute. -## Abrir una propuesta +## Opening an issue -Si encuentras un error en un proyecto de código abierto, verifica si ya se reportó. Si aún no se ha reportado el error, peudes abrir una propuesta para reportarlo de acuerdo con los lineamientos de contribución del proyecto. +If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines. -## Validar una propuesta o solicitud de cambios +## Validating an issue or pull request -Hay varias formas en las que puedes contribuir con los proyectos de código abierto. +There are a variety of ways that you can contribute to open source projects. -### Reproducir un error que se haya reportado -Puedes contribuir con un proyecto de código abierto si validas la propuesta o si agregas contexto adicional a una propuesta existente. +### Reproducing a reported bug +You can contribute to an open source project by validating an issue or adding additional context to an existing issue. -### Probar una solicitud de cambios -Puedes contribuir a un proyecto de código abierto si fusionas una solicitud de cambios en tu copia local del proyecto y pruebas los cambios. Agrega el resultado de tus pruebas en un comentario de la solicitud de cambios. +### Testing a pull request +You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request. -### Actualizar las propuestas -Puedes contribuir con un proyecto de código abierto si agregas información adicional a las propuestas existentes. +### Updating issues +You can contribute to an open source project by adding additional information to existing issues. -## Leer más +## Further reading -- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" -- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" +- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)" +- "[About your organization dashboard](/articles/about-your-organization-dashboard)" diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/index.md b/translations/es-ES/content/get-started/exploring-projects-on-github/index.md index e41c873e4e..35476b39db 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/index.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/index.md @@ -1,12 +1,12 @@ --- -title: Explorar proyectos en GitHub -intro: 'Descubre proyectos interesantes en {% data variables.product.product_name %} y contribuye con el código abierto colaborando con otras personas.' +title: Exploring projects on GitHub +intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.' redirect_from: - - /categories/stars/ - - /categories/87/articles/ - - /categories/exploring-projects-on-github/ + - /categories/stars + - /categories/87/articles + - /categories/exploring-projects-on-github - /articles/exploring-projects-on-github - - /github/getting-started-with-github/exploring-projects-on-github/ + - /github/getting-started-with-github/exploring-projects-on-github versions: fpt: '*' ghes: '*' @@ -18,6 +18,6 @@ children: - /finding-ways-to-contribute-to-open-source-on-github - /saving-repositories-with-stars - /following-people -shortTitle: Explorar proyectos +shortTitle: Explore projects --- diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md index 1c33362094..6f823e3ea2 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md @@ -1,11 +1,11 @@ --- -title: Guardar repositorios con estrellas -intro: 'Puedes marcar los repositorios y temas como favoritos para llevar el seguimiento de los proyectos que te parezcan interesantes{% ifversion fpt or ghec %} y descubrir el contenido relacionado en tu sección de noticias{% endif %}.' +title: Saving repositories with stars +intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.' redirect_from: - - /articles/stars/ - - /articles/about-stars/ - - /articles/browsing-friends-stars/ - - /articles/managing-your-stars/ + - /articles/stars + - /articles/about-stars + - /articles/browsing-friends-stars + - /articles/managing-your-stars - /articles/saving-repositories-with-stars - /github/getting-started-with-github/saving-repositories-with-stars - /github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars @@ -16,47 +16,114 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Guardar repositorios marcados como favoritos +shortTitle: Save repos with stars --- +You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}. -Puedes buscar, clasificar y filtrar tus repositorios y temas marcados con estrella en tu {% data variables.explore.your_stars_page %}. +## About stars -## Acerca de las estrellas - -Marcar con estrellas tus repositorios y temas favoritos te facilitará encontrarlos posteriormente. Puedes ver todos los repositorios y temas que has marcado con estrellas visitando tu {% data variables.explore.your_stars_page %}. +Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}. {% ifversion fpt or ghec %} -Puedes seleccionar los repositorios y temas como favoritos para descubrir proyectos similares en {% data variables.product.product_name %}. Cuando marcas repositorios o temas con estrellas, {% data variables.product.product_name %} puede recomendar contenido relacionado en la vista de tus noticias. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)". +You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)". {% endif %} -Marcar un repositorio con estrella también muestra reconocimiento al mantenedor del repositorio por su trabajo. Muchas de las clasificaciones de los repositorios de {% data variables.product.prodname_dotcom %} dependen de la cantidad de estrellas que tiene un repositorio. Además, [Explore](https://github.com/explore) muestra repositorios populares en base a la cantidad de estrellas que tienen. +Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have. -## Marcar un repositorio como favorito +## Starring a repository -Marcar un repositorio como favorito es un proceso simple de dos pasos. +Starring a repository is a simple two-step process. {% data reusables.repositories.navigate-to-repo %} -1. En la esquina superior derecha de la página, haz clic en **Favorito**. ![Marcar un repositorio como favorito](/assets/images/help/stars/starring-a-repository.png) -1. Opcionalmente, para dejar de marcar un repositorio como favorito, haz clic en **Desmarcar como favorito**. ![Dejar de marcar a un repositorio como favorito](/assets/images/help/stars/unstarring-a-repository.png) +1. In the top-right corner of the page, click **Star**. +![Starring a repository](/assets/images/help/stars/starring-a-repository.png) +1. Optionally, to unstar a previously starred repository, click **Unstar**. +![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png) -## Buscar estrellas +{% ifversion fpt or ghec %} +## Organizing starred repositories with lists -Puedes utilizar la barra de búsqueda en tu {% data variables.explore.your_stars_page %} para encontrar rápidamente los repositorios y temas que marcaste como favoritos. +{% note %} -1. Dirígete a tu {% data variables.explore.your_stars_page %}. -1. Utiliza la barra de búsqueda para encontrar tus repositorios marcados como favoritos o temas por su nombre. ![Buscar a través de las estrellas](/assets/images/help/stars/stars_search_bar.png) +**Note:** Lists are currently in public beta and subject to change. -La barra de búsqueda únicamente busca en los nombres de los temas y repositorios, y no en cualquier otro calificador (tal como el tamaño del repositorio o la fecha en la que se actualizó la última vez). +{% endnote %} -## Clasificar y filtrar estrellas +Curate repositories that you've starred with public lists. You can create public lists that appear on your stars page at `https://github.com/USERNAME?tab=stars`. -Puedes utilizar la clasificación o el filtrado para personalizar como ves los repositorios marcados como favoritos y los temas en tu página de favoritos. +If you add a private repository to a list, then the private repository will only appear in your list for people with `read` access to the repository. -1. Dirígete a tu {% data variables.explore.your_stars_page %}. -1. Para clasificar las estrellas, selecciona el menú desplegable de **Clasificar** y luego **Marcados recientemente como favoritos**, **Recientemente activos** o **Con más estrellas**. ![Clasificar estrellas](/assets/images/help/stars/stars_sort_menu.png) -1. Para filtrar tu lista de favoritos con base en su lenguaje de programación, haz clic en el que quieras bajo **Filtrar por lenguaje**. ![Filtrar estrellas por lenguaje](/assets/images/help/stars/stars_filter_language.png) -1. Para filtrar tu lista de favoritos según el repositorio o tema, haz clic en la opción deseada. ![Filtrar favoritos por tema](/assets/images/help/stars/stars_filter_topic.png) +![Screenshot of lists on stars page](/assets/images/help/stars/lists-overview-on-stars-page.png) -## Leer más +You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories. -- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" +![Screenshot of "Star" dropdown menu with list options featured from the repository page](/assets/images/help/stars/stars-dropdown-on-repo.png) + +![Screenshot of "Starred" dropdown menu with list options featured from a starred repository list](/assets/images/help/stars/add-repo-to-list.png) + +### Creating a list + +{% data reusables.stars.stars-page-navigation %} +2. Next to "Lists", click **Create list**. + ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png) +3. Enter a name and description for your list and click **Create**. + ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png) + +### Adding a repository to a list + +{% data reusables.stars.stars-page-navigation %} +2. Find the repository you want to add to your list. + ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png) +3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list. + ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png) + +### Removing a repository from your list + +{% data reusables.stars.stars-page-navigation %} +2. Select your list. +3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list. + ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png) + +### Editing a list name or description + +{% data reusables.stars.stars-page-navigation %} +1. Select the list you want to edit. +2. Click **Edit list**. +3. Update the name or description and click **Save list**. + ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png) + +### Deleting a list + +{% data reusables.stars.stars-page-navigation %} +2. Select the list you want to delete. +3. Click **Delete list**. + ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png) +4. To confirm, click **Delete**. + +{% endif %} + +## Searching starred repositories and topics + +You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred. + +1. Go to your {% data variables.explore.your_stars_page %}. +1. Use the search bar to find your starred repositories or topics by their name. +![Searching through stars](/assets/images/help/stars/stars_search_bar.png) + +The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated). + +## Sorting and filtering stars on your stars page + +You can use sorting or filtering to customize how you see starred repositories and topics on your stars page. + +1. Go to your {% data variables.explore.your_stars_page %}. +1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**. +![Sorting stars](/assets/images/help/stars/stars_sort_menu.png) +1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**. +![Filter stars by language](/assets/images/help/stars/stars_filter_language.png) +1. To filter your list of stars based on repository or topic, click on the desired option. +![Filter stars by topic](/assets/images/help/stars/stars_filter_topic.png) + +## Further reading + +- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md index 823ea0d672..6448f9759d 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -1,98 +1,98 @@ --- -title: Acerca de los repositorios remotos +title: About remote repositories redirect_from: - - /articles/working-when-github-goes-down/ - - /articles/sharing-repositories-without-github/ + - /articles/working-when-github-goes-down + - /articles/sharing-repositories-without-github - /articles/about-remote-repositories - - /articles/which-url-should-i-use/ + - /articles/which-url-should-i-use - /articles/which-remote-url-should-i-use - /github/using-git/which-remote-url-should-i-use - /github/using-git/about-remote-repositories - /github/getting-started-with-github/about-remote-repositories - /github/getting-started-with-github/getting-started-with-git/about-remote-repositories -intro: 'El acercamiento colaborativo de GitHub al desarrollo depende de publicar confirmaciones desde tu repositorio local hacia {% data variables.product.product_name %} para que el resto de las personas las vean, recuperen y actualicen.' +intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +## About remote repositories -## Acerca de los repositorios remotos +A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server. -Una URL remota es la manera de Git de decir "el lugar donde se almacena tu código". Esa URL podría ser tu repositorio en GitHub o la bifurcación de otro usuario o incluso en un servidor completamente diferente. +You can only push to two types of URL addresses: -Solo puedes subir a dos tipos de direcciones URL: +* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git` +* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git` -* Una URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git` -* Una URL SSH como `git@{% data variables.command_line.backticks %}:user/repo.git` +Git associates a remote URL with a name, and your default remote is usually called `origin`. -Git asocia una URL remota con un nombre y tu remoto predeterminado generalmente se llama `origen`. +## Creating remote repositories -## Crear repositorios remotos - -Puedes usar el comando `git remote add` para hacer coincidir una URL remota con un nombre. Por ejemplo, escribirás lo siguiente en la línea de comandos: +You can use the `git remote add` command to match a remote URL with a name. +For example, you'd type the following in the command line: ```shell git remote add origin <REMOTE_URL> ``` -Esto asocia el nombre `origin` con `REMOTE_URL`. +This associates the name `origin` with the `REMOTE_URL`. -Puedes usar el comando `git remote set-url` para [cambiar la URL de un remoto](/github/getting-started-with-github/managing-remote-repositories). +You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories). -## Elegir una URL para tu repositorio remoto +## Choosing a URL for your remote repository -Existen varias formas de clonar los repositorios disponibles en {% data variables.product.product_location %}. +There are several ways to clone repositories available on {% data variables.product.product_location %}. -Cuando ves un repositorio mientras estás registrado en tu cuenta, las URL que puedes utilizar para clonar el proyecto en tu computadora están disponibles debajo de los detalles del repositorio. +When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details. -Para obtener más información sobre cómo configurar o cambiar tu URL remota, consulta la sección "[Administrar los repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)". +For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Clonar con las URL con HTTPS +## Cloning with HTTPS URLs -Las URL clon `https://` se encuentran disponibles en todos los repositorios, sin importar su visibilidad. Las URL clon `https://` funcionan aún si estás detrás de un cortafuegos o de un proxy. +The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy. -Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio mendiante URL con HTTPS en la línea de comando, Git te pedirá tu nombre de usuario y contraseña de {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %} +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %} {% data reusables.command_line.provide-an-access-token %} {% tip %} **Tips**: -- Puedes utilizar un asistente de credenciales para que Git recuerde tus credenciales de {% data variables.product.prodname_dotcom %} cada que habla con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[ Almacenar tus credencialesde {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)". -- Para clonar un repositorio sin autenticarse en {% data variables.product.product_name %} desde la línea de comando, puedes utilizar {% data variables.product.prodname_desktop %} como alternativa. Para obtener más información, consulta la sección "[Clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". +- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." +- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." {% endtip %} - {% ifversion fpt or ghec %}Si prefieres utilizar SSH pero no puedes conectarte por el puerto 22, podrías utilizar SSH a través del puerto HTTPS. Para obtener más información, consulta la sección "[Utilizar SSH a través del puerto HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %} + {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %} -## Clonar con URL de SSH +## Cloning with SSH URLs -Las URL de SSH brindan acceso a un repositorio de Git por medio de SSH, un protocolo seguro. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta la sección "[Conectarse a {% data variables.product.prodname_dotcom %} con SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)". +SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)." -Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio remoto utilizando URL de SSH, se te solicitará una contraseña y deberás ingresar tu frase de acceso con llave de SSH. Para obtener más información, consulta la sección "[Trabajar con frases de acceso con llave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)". +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)." -{% ifversion fpt or ghec %}Si estás intentando acceder a una organización que utiliza el inicio de sesión único (SSO) de SAML, debes autorizar tu llave de SSH para acceder a la organización antes de que te autentiques. Para obtener más información, consulta la sección "[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)" y "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)". {% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} {% tip %} -**Tip**: Puedes utilizar una URL con SSH para clonar un repositorio a tu computador, o como una forma segura de desplegar tu código en servidores productivos. También puedes utilizar el envío a un agente de SSH con tu script de despliegue para evitar administrar llaves en el servidor. Para obtener más información, consulta la sección "[Utilizar el Reenvío de Agente de SSH](/developers/overview/using-ssh-agent-forwarding)". +**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} {% ifversion fpt or ghes or ghae or ghec %} -## Clonar con {% data variables.product.prodname_cli %} +## Cloning with {% data variables.product.prodname_cli %} -También puedes instalar {% data variables.product.prodname_cli %} para utilizar flujos de trabajo de {% data variables.product.product_name %} en tu terminal. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% endif %} {% ifversion not ghae %} -## Clonar con Subversion +## Cloning with Subversion -También puedes utilizar un cliente de [Subversion](https://subversion.apache.org/) para acceder a cualquier repositorio en {% data variables.product.prodname_dotcom %}. Subversion ofrece características diferentes a Git. Para obtener más información, consulta la sección "[¿Cuáles son las diferencias entre Subversion y Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" +You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" -También puedes acceder a los repositorios de {% data variables.product.prodname_dotcom %} desde 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)". +You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)." {% endif %} diff --git a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index 0585c48a70..8abbe4ef24 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -1,10 +1,10 @@ --- -title: Asociar editores de texto con Git -intro: Usar un editor de texto para abrir y editar tus archivos con Git. +title: Associating text editors with Git +intro: Use a text editor to open and edit your files with Git. redirect_from: - - /textmate/ - - /articles/using-textmate-as-your-default-editor/ - - /articles/using-sublime-text-2-as-your-default-editor/ + - /textmate + - /articles/using-textmate-as-your-default-editor + - /articles/using-sublime-text-2-as-your-default-editor - /articles/associating-text-editors-with-git - /github/using-git/associating-text-editors-with-git - /github/getting-started-with-github/associating-text-editors-with-git @@ -14,44 +14,43 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Editores de texto asociados +shortTitle: Associate text editors --- - {% mac %} -## Usar Atom como editor +## Using Atom as your editor -1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "atom --wait" ``` -## Utilizar Visual Studio Code como tu editor +## Using Visual Studio Code as your editor -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "code --wait" ``` -## Usar Sublime Text como tu editor +## Using Sublime Text as your editor -1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. +1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "subl -n -w" ``` -## Usar TextMate como editor +## Using TextMate as your editor -1. Instala [TextMate](https://macromates.com/). -2. Instala la utilidad de shell `mate` de TextMate. Para obtener más información, consulta "[mate y rmate](https://macromates.com/blog/2011/mate-and-rmate/)" en la documentación de TextMate. +1. Install [TextMate](https://macromates.com/). +2. Install TextMate's `mate` shell utility. For more information, see "[mate and rmate](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -4. Escribe este comando: +4. Type this command: ```shell $ git config --global core.editor "mate -w" ``` @@ -59,38 +58,38 @@ shortTitle: Editores de texto asociados {% windows %} -## Usar Atom como editor +## Using Atom as your editor -1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "atom --wait" ``` -## Utilizar Visual Studio Code como tu editor +## Using Visual Studio Code as your editor -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "code --wait" ``` -## Usar Sublime Text como tu editor +## Using Sublime Text as your editor -1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. +1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w" ``` -## Usar Notepad++ como editor +## Using Notepad++ as your editor -1. Instala Notepad++ desde https://notepad-plus-plus.org/. Para obtener más información, consulta la sección "[Comenzar](https://npp-user-manual.org/docs/getting-started/)" en la documentación de Notepad++. +1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin" ``` @@ -98,29 +97,29 @@ shortTitle: Editores de texto asociados {% linux %} -## Usar Atom como editor +## Using Atom as your editor -1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "atom --wait" ``` -## Utilizar Visual Studio Code como tu editor +## Using Visual Studio Code as your editor -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "code --wait" ``` -## Usar Sublime Text como tu editor +## Using Sublime Text as your editor -1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. +1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation. {% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: +3. Type this command: ```shell $ git config --global core.editor "subl -n -w" ``` diff --git a/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md index 8524ac5fbc..5c74e8cf31 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md @@ -1,7 +1,7 @@ --- title: Caching your GitHub credentials in Git redirect_from: - - /firewalls-and-proxies/ + - /firewalls-and-proxies - /articles/caching-your-github-password-in-git - /github/using-git/caching-your-github-password-in-git - /github/using-git/caching-your-github-credentials-in-git diff --git a/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md index 9dc5442342..676651b64c 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md @@ -1,10 +1,10 @@ --- -title: Configurar Git para manejar finales de línea -intro: 'Para evitar problemas en tus diferencias, puedes configurar Git para manejar correctamente los finales de línea.' +title: Configuring Git to handle line endings +intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.' redirect_from: - - /dealing-with-lineendings/ - - /line-endings/ - - /articles/dealing-with-line-endings/ + - /dealing-with-lineendings + - /line-endings + - /articles/dealing-with-line-endings - /articles/configuring-git-to-handle-line-endings - /github/using-git/configuring-git-to-handle-line-endings - /github/getting-started-with-github/configuring-git-to-handle-line-endings @@ -14,23 +14,22 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Manejar los extremos de línea +shortTitle: Handle line endings --- +## About line endings +Every time you press return on your keyboard you insert an invisible character called a line ending. Different operating systems handle line endings differently. -## Acerca de los finales de línea -Cada vez que presionas Enter en tu teclado, insertas un caracter invisible denominado fin de línea. Esto se maneja de forma diferente en los diferentes sistemas operativos. +When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS. -Cuando colaboras en proyectos con Git y {% data variables.product.product_name %}, Git podría producir resultados inesperados si, por ejemplo, estás trabajando en una máquina Windows y tu colaborador hizo cambios en macOS. +You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems. -Puedes configurar Git para que maneje los fines de línea automáticamente y así puedas colaborar eficazmente con las personas que utilizan otros sistemas operativos. +## Global settings for line endings -## Parámetros globales para finales de línea - -El comando `git config core.autocrlf` se usa para cambiar el modo en que Git maneja los finales de línea. Toma un solo argumento. +The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument. {% mac %} -En macOS, simplemente pasas `input` a la configuración. Por ejemplo: +On macOS, you simply pass `input` to the configuration. For example: ```shell $ git config --global core.autocrlf input @@ -41,7 +40,7 @@ $ git config --global core.autocrlf input {% windows %} -En Windows, simplemente escribes `true` en la configuración. Por ejemplo: +On Windows, you simply pass `true` to the configuration. For example: ```shell $ git config --global core.autocrlf true @@ -53,7 +52,7 @@ $ git config --global core.autocrlf true {% linux %} -En Linux, simplemente escribes `input` en la configuración. Por ejemplo: +On Linux, you simply pass `input` to the configuration. For example: ```shell $ git config --global core.autocrlf input @@ -62,75 +61,75 @@ $ git config --global core.autocrlf input {% endlinux %} -## Parámetros por repositorio +## Per-repository settings -Como ocpión, puedes configurar un archivo de tipo *.gitattributes* para administrar cómo Git lee los fines de línea en un repositorio específico. Cuando confirmas este archivo en un repositorio, éste invalida la configuración de `core.autocrlf` para todos los colaboradores del mismo. Esto garantiza un comportamiento consistente para todos los usuarios, sin importar su configuración y ambiente de Git. +Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment. -El archivo *.gitattributes* debe crearse en la raíz del repositorio y confirmarse como cualquier otro archivo. +The *.gitattributes* file must be created in the root of the repository and committed like any other file. -Un archivo *.gitattributes* se asemeja a una tabla con dos columnas: +A *.gitattributes* file looks like a table with two columns: -* A la izquierda está el nombre del archivo que coincide con Git. -* A la derecha está la configuración de fin de línea que Git debería usar para esos archivos. +* On the left is the file name for Git to match. +* On the right is the line ending configuration that Git should use for those files. -### Ejemplo +### Example -Aquí hay un ejemplo de archivo *.gitattributes*. Puedes usarlo como plantilla para tus repositorios: +Here's an example *.gitattributes* file. You can use it as a template for your repositories: ``` -# Esteblece el comportamiento predeterminado, en caso de que las personas no tengan configurado core.autocrlf. +# Set the default behavior, in case people don't have core.autocrlf set. * text=auto -# Declara explícitamente los archivos de texto que siempre quieres que estén normalizados y convertidos -# a finales de línea nativos en el control. +# Explicitly declare text files you want to always be normalized and converted +# to native line endings on checkout. *.c text *.h text -# Declara los archivos que siempre tendrán los finales de línea CRLF en el control. +# Declare files that will always have CRLF line endings on checkout. *.sln text eol=crlf -# Denota todos los archivos que son absolutamente binarios y no deberían modificarse. +# Denote all files that are truly binary and should not be modified. *.png binary *.jpg binary ``` -Notarás que los archivos coinciden—`*.c`, `*.sln`, `*.png`—, separados con un espacio, y luego se les dará una configuración —`text`, `text eol=crlf`, `binary`. Revisaremos algunas configuraciones posibles a continuación. +You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below. -- `text=auto` Git manejará los archivos en cualquier manera que crea sea mejor. Esta es una buena opción predeterminada. +- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option. -- `text eol=crlf` Git siempre convertirá los fines de línea en `CRLF` a la salida. Deberías usar esto para los archivos que deben conservar los finales `CRLF`, incluso en OSX o Linux. +- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux. -- `text eol=lf` Git siempre convertirá los finales de línea en `LF` a la salida. Deberías usar esto para los archivos que deben conservar los finales LF, incluso en Windows. +- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows. -- `binary` Git entenderá que los archivos especificados no son de texto, y no deberá intentar cambiarlos. El parámetro `binario` también es un alias para `text -diff`. +- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`. -## Actualizar un repositorio después de los finales de línea +## Refreshing a repository after changing line endings -Cuando configuras la opción `core.autocrlf` o confirmas un archivo de tipo *.gitattributes* podrías encontrar que Git reporta cambios a archivos que no has modificado. Git ha cambiado los fines de línea para que concuerden con tu nueva configuración. +When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration. -Para garantizar que todos los fines de línea en tu repositorio concuerdan con tu nueva configuración, respalda tus archivos con Git, borra los archivos en tu repositorio (con excepción de el directorio `.git`), y luego restablece todos los archivos al mismo tiempo. +To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once. -1. Guarda los archivos actuales en Git, de manera que nada de tu trabajo se pierda. +1. Save your current files in Git, so that none of your work is lost. ```shell $ git add . -u $ git commit -m "Saving files before refreshing line endings" ``` -2. Agrega todos los archivos cambiados nuevamente y normaliza los finales de línea. +2. Add all your changed files back and normalize the line endings. ```shell $ git add --renormalize . ``` -3. Muestra los archivos reescritos, normalizados. +3. Show the rewritten, normalized files. ```shell $ git status ``` -4. Confirma los cambios en tu repositorio. +4. Commit the changes to your repository. ```shell $ git commit -m "Normalize all the line endings" ``` -## Leer más +## Further reading -- [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 -- [Comenzar -Configuración Inicial](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) en el libro de Pro Git -- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) por [Tim Clem](https://github.com/tclem) +- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book +- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git +- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book +- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem) diff --git a/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md b/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md index cfea0ad64a..426fd8dbb8 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md @@ -1,8 +1,8 @@ --- -title: Flujos de trabajo de Git -intro: 'El flujo de {% data variables.product.prodname_dotcom %} es un flujo de trabajo ligero basado en ramas que soporta equipos y proyectos que despliegan frecuentemente.' +title: Git workflows +intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.' redirect_from: - - /articles/what-is-a-good-git-workflow/ + - /articles/what-is-a-good-git-workflow - /articles/git-workflows - /github/using-git/git-workflows - /github/getting-started-with-github/git-workflows @@ -13,5 +13,4 @@ versions: ghae: '*' ghec: '*' --- - -Puedes adoptar el método de flujo de {% data variables.product.prodname_dotcom %} para estandarizar como funciona tu equipo y como colabora con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[flujo de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-flow)". +You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)." diff --git a/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md b/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md index fcbe715cfc..72d4b8d668 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md @@ -1,66 +1,66 @@ --- -title: Ignorar archivos +title: Ignoring files redirect_from: - - /git-ignore/ - - /ignore-files/ + - /git-ignore + - /ignore-files - /articles/ignoring-files - /github/using-git/ignoring-files - /github/getting-started-with-github/ignoring-files - /github/getting-started-with-github/getting-started-with-git/ignoring-files -intro: 'Puedes configurar Git para que ignore archivos que no quieres ingresar en {% data variables.product.product_name %}.' +intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +## Configuring ignored files for a single repository -## Configurar archivos ignorados para solo un repositorio +You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit. +To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository. -Puedes crear un archivo de tipo *.gitignore* en el directorio raíz de tu repositorio para indicarle a Git qué archivos y directorios ignorar cuando haces una confirmación. Para compartir las reglas para ignorar con otros usuarios que clonan el repositorio, confirma el archivo de tipo *.gitignore* en tu repositorio. - -GitHub mantiene una lista oficial de archivos recomendados de tipo *.gitignore* para varios sistemas operativos, ambientes y lenguajes de programación populares en el repositorio público `github/gitignore`. También puedes usar gitignore.io para crear un archivo *.gitignore* para tu sistema operativo, lenguaje de programación o IDE. Para obtener más información, consulta la sección "[github/gitignore](https://github.com/github/gitignore)" y el sitio "[gitignore.io](https://www.gitignore.io/)". +GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Navega a la ubicación de tu repositorio de Git. -3. Crea un archivo de tipo *.gitignore* para tu repositorio. +2. Navigate to the location of your Git repository. +3. Create a *.gitignore* file for your repository. ```shell $ touch .gitignore ``` If the command succeeds, there will be no output. + +For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository. -Para ver un archivo de tipo *.gitignore* de ejemplo, consulta la sección "[Algunas configuraciones comunes de .gitignore](https://gist.github.com/octocat/9257657)" en el repositorio de Octocat. - -Si quieres ignorar un archivo que ya se haya ingresado, deberás dejar de rastrearlo antes de que agregues una regla para ignorarlo. Desde tu terminal, deja de rastrear el archivo. +If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file. ```shell $ git rm --cached FILENAME ``` -## Configurar archivos ignorados para todos los repositorios en tu computador +## Configuring ignored files for all repositories on your computer -También puedes crear un archivo global de tipo *.gitignore* para definir una lista de reglas para ignorar archivos en cada repositorio de Git en tu computador. Por ejemplo, puedes crear el archivo en *~/.gitignore_global* y agregarle algunas normas. +You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Configura Git para que utilice el archivo de exclusión *~/.gitignore_global* en todos los repositorios de Git. +2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories. ```shell $ git config --global core.excludesfile ~/.gitignore_global ``` -## Excluir archivos locales sin crear un archivo de tipo *.gitignore* +## Excluding local files without creating a *.gitignore* file -Si no quieres crear un archivo *.gitignore* para compartir con otros, puedes crear normas que no estén confirmadas con el repositorio. Puedes utilizar esta técnica para los archivos generados de forma local que no esperas que otros usuarios generen, tales como los archivos creados por tu editor. +If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor. -Utiliza tu editor de texto favorito para abrir el archivo llamado *.git/info/exclude* dentro de la raíz de tu repositorio de Git. Cualquier norma que agregues aquí no se registrará y solo ignorará archivos de tu repositorio local. +Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Navega a la ubicación de tu repositorio de Git. -3. Utilizando tu editor de texto favorito, abre el archivo *.git/info/exclude*. +2. Navigate to the location of your Git repository. +3. Using your favorite text editor, open the file *.git/info/exclude*. -## Leer más +## Further Reading -* [Ignorar archivos](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) en el libro de Pro Git -* [.gitignore](https://git-scm.com/docs/gitignore) en las páginas de man de Git -* [Una colección de plantillas útiles de *.gitignore* ](https://github.com/github/gitignore) en el repositorio github/gitignore -* Sitio de [gitignore.io](https://www.gitignore.io/) +* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book +* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git +* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository +* [gitignore.io](https://www.gitignore.io/) site diff --git a/translations/es-ES/content/get-started/getting-started-with-git/index.md b/translations/es-ES/content/get-started/getting-started-with-git/index.md index d35f373851..35a583d510 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/index.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/index.md @@ -1,12 +1,12 @@ --- -title: Comenzar con Git -intro: 'Configura Git, un sistema de control de versiones distribuido, para administrar tus repositorios de {% data variables.product.product_name %} desde tu computadora.' +title: Getting started with Git +intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.product_name %} repositories from your computer.' redirect_from: - /articles/getting-started-with-git-and-github - /github/using-git/getting-started-with-git-and-github - /github/using-git/learning-about-git - /articles/learning-about-git - - /github/getting-started-with-github/getting-started-with-git/ + - /github/getting-started-with-github/getting-started-with-git versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md index 3ffdb947b4..0914d2a7ea 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -2,9 +2,9 @@ title: Managing remote repositories intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.' redirect_from: - - /categories/18/articles/ - - /remotes/ - - /categories/managing-remotes/ + - /categories/18/articles + - /remotes + - /categories/managing-remotes - /articles/managing-remote-repositories - /articles/adding-a-remote - /github/using-git/adding-a-remote diff --git a/translations/es-ES/content/get-started/index.md b/translations/es-ES/content/get-started/index.md index c1da31cefa..8917ef270e 100644 --- a/translations/es-ES/content/get-started/index.md +++ b/translations/es-ES/content/get-started/index.md @@ -1,21 +1,21 @@ --- -title: Comenzar con GitHub -shortTitle: Empezar -intro: 'Aprende cómo comenzar a crear, enviar y mantener software con {% data variables.product.prodname_dotcom %}. Explora nuestros productos, regístrate para una cuenta y conéctate con la comunidad de desarrollo más grande del mundo.' +title: Getting started with GitHub +shortTitle: Get started +intro: 'Learn how to start building, shipping, and maintaining software with {% data variables.product.prodname_dotcom %}. Explore our products, sign up for an account, and connect with the world''s largest development community.' redirect_from: - - /categories/54/articles/ - - /categories/bootcamp/ - - /categories/32/articles/ - - /categories/2/articles/ - - /categories/organizations/ - - /categories/about-github/ - - /categories/53/articles/ - - /categories/setup/ + - /categories/54/articles + - /categories/bootcamp + - /categories/32/articles + - /categories/2/articles + - /categories/organizations + - /categories/about-github + - /categories/53/articles + - /categories/setup - /categories/getting-started-with-github - - /categories/19/articles/ + - /categories/19/articles - /categories/using-git - /github/using-git - - /github/getting-started-with-github/ + - /github/getting-started-with-github versions: fpt: '*' ghes: '*' @@ -60,4 +60,3 @@ children: - /getting-started-with-git - /using-git --- - diff --git a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md index d5330b1689..d99e76f16a 100644 --- a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md @@ -69,7 +69,7 @@ If you have an enterprise account, license use for the entire enterprise is show {% endif %} -{% ifversion ghec or ghes > 3.0 or ghae-next %} +{% ifversion ghec or ghes > 3.0 or ghae %} ## Further reading diff --git a/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md index e12f41cae3..9d725ebcf0 100644 --- a/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md @@ -1,9 +1,9 @@ --- title: Access permissions on GitHub redirect_from: - - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do/ - - /articles/what-are-the-different-types-of-team-permissions/ - - /articles/what-are-the-different-access-permissions/ + - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do + - /articles/what-are-the-different-types-of-team-permissions + - /articles/what-are-the-different-access-permissions - /articles/access-permissions-on-github - /github/getting-started-with-github/access-permissions-on-github - /github/getting-started-with-github/learning-about-github/access-permissions-on-github diff --git a/translations/es-ES/content/get-started/learning-about-github/index.md b/translations/es-ES/content/get-started/learning-about-github/index.md index 43514a903a..32d67d6de5 100644 --- a/translations/es-ES/content/get-started/learning-about-github/index.md +++ b/translations/es-ES/content/get-started/learning-about-github/index.md @@ -1,9 +1,9 @@ --- -title: Obtener información sobre GitHub -intro: 'Aprende cómo puedes utilizar los productos de {% data variables.product.company_short %} para mejorar tu proceso de administración de software y colaborar con otras personas.' +title: Learning about GitHub +intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.' redirect_from: - /articles/learning-about-github - - /github/getting-started-with-github/learning-about-github/ + - /github/getting-started-with-github/learning-about-github versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md index 242358a9c1..4981f1858c 100644 --- a/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md @@ -2,10 +2,10 @@ title: Types of GitHub accounts intro: 'Your user account is your identity on {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}' redirect_from: - - /manage-multiple-clients/ - - /managing-clients/ - - /articles/what-s-the-difference-between-user-and-organization-accounts/ - - /articles/differences-between-user-and-organization-accounts/ + - /manage-multiple-clients + - /managing-clients + - /articles/what-s-the-difference-between-user-and-organization-accounts + - /articles/differences-between-user-and-organization-accounts - /articles/types-of-github-accounts - /github/getting-started-with-github/types-of-github-accounts - /github/getting-started-with-github/learning-about-github/types-of-github-accounts diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 336444f7a6..d8227e1740 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -49,7 +49,7 @@ To use an organization account with {% data variables.product.prodname_ghe_cloud Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." #### 3. Setting up and managing billing -When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." +When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." diff --git a/translations/es-ES/content/get-started/quickstart/be-social.md b/translations/es-ES/content/get-started/quickstart/be-social.md index a301f20548..e59c630dd1 100644 --- a/translations/es-ES/content/get-started/quickstart/be-social.md +++ b/translations/es-ES/content/get-started/quickstart/be-social.md @@ -1,7 +1,7 @@ --- title: Be social redirect_from: - - /be-social/ + - /be-social - /articles/be-social - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social diff --git a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md index 7f7bfa62a8..3f155a9a7e 100644 --- a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md +++ b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md @@ -1,10 +1,10 @@ --- -title: Comunicarse en GitHub -intro: 'Puedes debatir cambios y proyectos específicos, así como metas de equipo o ideas más amplias, usando tipos diferentes de debates en {% data variables.product.product_name %}.' +title: Communicating on GitHub +intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.' miniTocMaxHeadingLevel: 3 redirect_from: - /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github - - /articles/about-discussions-in-issues-and-pull-requests/ + - /articles/about-discussions-in-issues-and-pull-requests - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github - /github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github - /github/getting-started-with-github/quickstart/communicating-on-github @@ -19,139 +19,138 @@ topics: - Discussions - Fundamentals --- +## Introduction -## Introducción - -{% data variables.product.product_name %} proporciona herramientas de comunicación colaborativas que te permiten interactuar de cerca con tu comunidad. Esta guía de inicio rápido te mostrará cómo escoger la herramienta correcta para tus necesidades. +{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs. {% ifversion fpt or ghec %} -Puedes crear y participar en propuestas, solicitudes de cambios, {% data variables.product.prodname_discussions %} y debates de equipo, dependiendo del tipo de conversación que te gustaría tener. +You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have. {% endif %} {% ifversion ghes or ghae %} -Puedes crear y participar de propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener. +You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have. {% endif %} ### {% data variables.product.prodname_github_issues %} -- son útiles para debatir los detalles específicos de un proyecto, tales como los reportes de errores, mejoras planeadas y retroalimentación. -- son específicas de un repositorio y, habitualmente, es claro quién es el propietario. -- a menudo se refiere a ellas como el sistema de rastreo de errores de {% data variables.product.prodname_dotcom %}. - -### Solicitudes de cambios -- te permiten proponer cambios específicos. -- te permiten comentar directamente en los cambios propuestos que otros sugieren. -- son específicos para un repositorio. - +- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback. +- are specific to a repository, and usually have a clear owner. +- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system. + +### Pull requests +- allow you to propose specific changes. +- allow you to comment directly on proposed changes suggested by others. +- are specific to a repository. + {% ifversion fpt or ghec %} ### {% data variables.product.prodname_discussions %} -- son como un foro y son muy útiles para ideas y debates abiertos en donde es importante la colaboración. -- pueden abarcar muchos repositorios. -- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas y la creación de una base de conocimiento comunitario. -- a menudo no se sabe quién es el propietario. -- a menudo no dan como resultado una tarea sobre la cual se pueda actuar. +- are like a forum, and are best used for open-form ideas and discussions where collaboration is important. +- may span many repositories. +- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base. +- often don’t have a clear owner. +- often do not result in an actionable task. {% endif %} -### Debates de equipo -- pueden iniciarse en la página de tu equipo para tener conversaciones que abarquen varios proyectos y no pertenecen solo a una propuesta o solicitud de cambios específicas. En vez de abrir un informe de problemas en un repositorio para debatir sobre una idea, puedes incluir a todo el equipo si tienes una conversación en un debate de equipo. -- te permiten mantener debates con tu equipo sobre planeación, análisis, diseño, investigación de usuarios y toma de decisiones generales de un proyecto, todo en un solo lugar.{% ifversion ghes or ghae %} -- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas. -- a menudo no se sabe quién es el propietario. -- a menudo no dan como resultad una tarea sobre la cual se pueda actuar.{% endif %} +### Team discussions +- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion. +- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes or ghae %} +- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas. +- often don’t have a clear owner. +- often do not result in an actionable task.{% endif %} -## ¿Qué debate debo utilizar? +## Which discussion tool should I use? -### Casos de las propuestas +### Scenarios for issues -- Quiero dar seguimiento a las tareas, ampliaciones y errores. -- Quiero emitir un reporte de errores. -- Quiero compartir retroalimentación sobre una característica específica. -- Quiero hacer una pregunta sobre los archivos del repositorio. +- I want to keep track of tasks, enhancements and bugs. +- I want to file a bug report. +- I want to share feedback about a specific feature. +- I want to ask a question about files in the repository. -#### Ejemplo de propuesta +#### Issue example -Este ejemplo demuestra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una propuesta en nuestro repositorio de documentación de código abierto para concientizarnos de un error y debatir sobre cómo arreglarlo. +This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix. -![Ejemplo de propuesta](/assets/images/help/issues/issue-example.png) +![Example of issue](/assets/images/help/issues/issue-example.png) -- Un usuario notó que el color azul del letrero en la parte superior de la página de la versión china de los documentos de {% data variables.product.prodname_dotcom %} hace que el texto contenido sea ilegible. -- El usurio creó una propuesta en el repositorio, la cual declaraba el problema y sugería un arreglo (el cual es utilizar un color de fondo diferente para el letrero). -- Se produce un debate y, periódicamente, se llega a un consenso sobre qué solución aplicar. -- Entonces, un colaborador puede crear una solicitud de cambios con la solución. +- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable. +- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner). +- A discussion ensues, and eventually, a consensus will be reached about the fix to apply. +- A contributor can then create a pull request with the fix. -### Escenarios para solicitudes de cambios +### Scenarios for pull requests -- Quiero arreglar un error tipográcifo en un repositorio. -- Quiero hacer cambios en un repositorio. -- Quiero hacer cambios para corregir un error. -- Quiero comentar en los cambios que otros sugieren. +- I want to fix a typo in a repository. +- I want to make changes to a repository. +- I want to make changes to fix an issue. +- I want to comment on changes suggested by others. -#### Ejemplo de solicitud de cambios +#### Pull request example -Este ejemplo ilustra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una solicitud de cambios en el repositorio de código abierto de nuestra documentación para arreglar un error tipográfico. +This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo. -En la pestaña de **Conversación** de la solicitud de cambios, el autor explica por qué crearon la solicitud de cambios. +In the **Conversation** tab of the pull request, the author explains why they created the pull request. -![Ejemplo de solicitud de cambios - Pestaña de conversación](/assets/images/help/pull_requests/pr-conversation-example.png) +![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png) -La pestaña **Archivos que cambiaron** de la solicitud de cambios muestra la solución implementada. +The **Files changed** tab of the pull request shows the implemented fix. -![Ejemplo de solicitud de cambios - Pestaña de archivos que cambiaron](/assets/images/help/pull_requests/pr-files-changed-example.png) +![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png) -- Este contribuyente nota un error tipográfico en el repositorio. -- El usuario crea una solicitud de cambios con la solución. -- Un mantenedor de repositorio revisa la solicitud de cambios, la comenta y la fusiona. +- This contributor notices a typo in the repository. +- The user creates a pull request with the fix. +- A repository maintainer reviews the pull request, comments on it, and merges it. {% ifversion fpt or ghec %} -### Casos para los {% data variables.product.prodname_discussions %} +### Scenarios for {% data variables.product.prodname_discussions %} -- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio. -- Quiero compartir las noticias con mis colaboradores o con mi equipo. -- Quiero comenzar o participar en una conversación abierta. -- Quiero hacer un anuncio a mi comunidad. +- I have a question that's not necessarily related to specific files in the repository. +- I want to share news with my collaborators, or my team. +- I want to start or participate in an open-ended conversation. +- I want to make an announcement to my community. -#### Ejemplo de {% data variables.product.prodname_discussions %} +#### {% data variables.product.prodname_discussions %} example -Este ejemplo muestra la publicación de bienvenida de {% data variables.product.prodname_discussions %} para el repositorio de código abierto de los documentos de {% data variables.product.prodname_dotcom %} e ilustra cómo el equipo quiere colaborar con su comunidad. +This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community. -![Ejemplo de un {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png) +![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png) -El mantenedor de la comunidad inició un debate para recibir a la comunidad y para pedir a los miembros que se presentaran a sí mismos. Esta publicación fomenta un ambiente acogedor para los visitantes y contribuyentes. Esta publicación también aclara que al equipo le complace ayudar a los contribuyentes del repositorio. +This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository. {% endif %} {% ifversion fpt or ghes or ghae or ghec %} -### Casos de debates de equipo +### Scenarios for team discussions -- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio. -- Quiero compartir las noticias con mis colaboradores o con mi equipo. -- Quiero comenzar o participar en una conversación abierta. -- Quiero anunciar algo a mi equipo. +- I have a question that's not necessarily related to specific files in the repository. +- I want to share news with my collaborators, or my team. +- I want to start or participate in an open-ended conversation. +- I want to make an announcement to my team. {% ifversion fpt or ghec %} -Como puedes ver, los debates de equipo son muy similares a los {% data variables.product.prodname_discussions %}. Para {% data variables.product.prodname_dotcom_the_website %}, te recomendamos utilizar los {% data variables.product.prodname_discussions %} como inicio de conversaciones. Puedes utilizar los {% data variables.product.prodname_discussions %} para colaborar con cualquier comunidad en {% data variables.product.prodname_dotcom %}. Si eres parte de una organización y te gustaría iniciar conversaciones dentro de tu organización o del equipo que está dentro de ella, debes utilizar los debates de equipo. +As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions. {% endif %} -#### Ejemplo de debates de equipo +#### Team discussion example -Este ejemplo muestra una publicación de equipo para el equipo `octo-team`. +This example shows a team post for the `octo-team` team. -![Ejemplo de debate de equipo](/assets/images/help/projects/team-discussions-example.png) +![Example of team discussion](/assets/images/help/projects/team-discussions-example.png) -Un miembro del equipo `octocat` publicó un debate de equipo que les informaba sobre varias cosas: -- Un miembro del equipo llamado Mona inició eventos de juego remotos. -- Hay una publicación del blog que describe cómo los equipos utilizan {% data variables.product.prodname_actions %} para producir sus documentos. -- Los materiales sobre el "All Hands" de abril está ahora disponible para que lo vean todos los miembros del equipo. +The `octocat` team member posted a team discussion, informing the team of various things: +- A team member called Mona started remote game events. +- There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs. +- Material about the April All Hands is now available for all team members to view. {% endif %} -## Pasos siguientes +## Next steps -Estos ejemplos te muestran cómo decidir cuál es la mejor herramienta para tus conversaciones en {% data variables.product.product_name %}. Pero esto es solo el inicio; puedes hacer mucho más para confeccionar estas herramientas de acuerdo con tus necesidades. +These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. -Para las propuestas, por ejemplo, puedes etiquetarlas con etiquetas para buscarlas más rápidamente y crear plantillas de propuesta para ayudar a los contribuyentes a abrir propuestas significativas. Para obtener más información, consulta la sección "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues#working-with-issues)" y "[Acerca de las plantillas de propuestas y solicitudes de cambio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)". +For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)." -Para las solicitudes de cambio, puedes crear borradores de estas si los cambios que propones aún están en curso. Los borradores de solicitudes de cambios no pueden fusionarse hasta que se marquen como listos para revisión. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." +For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." {% ifversion fpt or ghec %} -Para el caso de los {% data variables.product.prodname_discussions %}, puedes configurar un código de conducta y fijar los debates que contengan información importante de tu comunidad. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." {% endif %} -Para el caso de los debates de equipo, puedes editarlos o borrarlos en la página del equipo y puedes configurar las notificaciones para estos. Para obtener más información, consulta [Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)". +For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." diff --git a/translations/es-ES/content/get-started/quickstart/create-a-repo.md b/translations/es-ES/content/get-started/quickstart/create-a-repo.md index 56c2e95fd0..d3b24b7e93 100644 --- a/translations/es-ES/content/get-started/quickstart/create-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/create-a-repo.md @@ -1,7 +1,7 @@ --- title: Create a repo redirect_from: - - /create-a-repo/ + - /create-a-repo - /articles/create-a-repo - /github/getting-started-with-github/create-a-repo - /github/getting-started-with-github/quickstart/create-a-repo diff --git a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md index f40be52431..c9fa67d1cb 100644 --- a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md @@ -1,8 +1,8 @@ --- title: Fork a repo redirect_from: - - /fork-a-repo/ - - /forking/ + - /fork-a-repo + - /forking - /articles/fork-a-repo - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo diff --git a/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md index 5ce711cfb5..c7023667de 100644 --- a/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md +++ b/translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md @@ -1,8 +1,8 @@ --- title: Git and GitHub learning resources redirect_from: - - /articles/good-resources-for-learning-git-and-github/ - - /articles/what-are-other-good-resources-for-learning-git-and-github/ + - /articles/good-resources-for-learning-git-and-github + - /articles/what-are-other-good-resources-for-learning-git-and-github - /articles/git-and-github-learning-resources - /github/getting-started-with-github/git-and-github-learning-resources - /github/getting-started-with-github/quickstart/git-and-github-learning-resources diff --git a/translations/es-ES/content/get-started/quickstart/github-flow.md b/translations/es-ES/content/get-started/quickstart/github-flow.md index 0db3281778..0ae27c4179 100644 --- a/translations/es-ES/content/get-started/quickstart/github-flow.md +++ b/translations/es-ES/content/get-started/quickstart/github-flow.md @@ -2,8 +2,8 @@ title: GitHub flow intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.' redirect_from: - - /articles/creating-and-editing-files-in-your-repository/ - - /articles/github-flow-in-the-browser/ + - /articles/creating-and-editing-files-in-your-repository + - /articles/github-flow-in-the-browser - /articles/github-flow - /github/collaborating-with-issues-and-pull-requests/github-flow - /github/getting-started-with-github/github-flow diff --git a/translations/es-ES/content/get-started/quickstart/index.md b/translations/es-ES/content/get-started/quickstart/index.md index 42b3ee9dc4..cfc4b9e48c 100644 --- a/translations/es-ES/content/get-started/quickstart/index.md +++ b/translations/es-ES/content/get-started/quickstart/index.md @@ -1,6 +1,6 @@ --- -title: Inicio Rápido -intro: 'Comenzar a usar {% data variables.product.product_name %} para administrar los repositorios de Git y colaborar con otros.' +title: Quickstart +intro: 'Get started using {% data variables.product.product_name %} to manage Git repositories and collaborate with others.' versions: fpt: '*' ghes: '*' @@ -24,6 +24,6 @@ children: - /git-cheatsheet - /git-and-github-learning-resources redirect_from: - - /github/getting-started-with-github/quickstart/ + - /github/getting-started-with-github/quickstart --- diff --git a/translations/es-ES/content/get-started/quickstart/set-up-git.md b/translations/es-ES/content/get-started/quickstart/set-up-git.md index e55b465c7e..2b916a6abb 100644 --- a/translations/es-ES/content/get-started/quickstart/set-up-git.md +++ b/translations/es-ES/content/get-started/quickstart/set-up-git.md @@ -1,18 +1,18 @@ --- -title: Configurar Git +title: Set up Git redirect_from: - - /git-installation-redirect/ - - /linux-git-installation/ - - /linux-set-up-git/ - - /mac-git-installation/ - - /mac-set-up-git/ - - /set-up-git-redirect/ - - /win-git-installation/ - - /win-set-up-git/ + - /git-installation-redirect + - /linux-git-installation + - /linux-set-up-git + - /mac-git-installation + - /mac-set-up-git + - /set-up-git-redirect + - /win-git-installation + - /win-set-up-git - /articles/set-up-git - /github/getting-started-with-github/set-up-git - /github/getting-started-with-github/quickstart/set-up-git -intro: 'En el centro de {% data variables.product.prodname_dotcom %} hay un sistema de control de versión de código abierto (VCS) llamado Git. Git es responsable de todo lo relacionado con {% data variables.product.prodname_dotcom %} que suceda de forma local en tu computadora.' +intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.' versions: fpt: '*' ghes: '*' @@ -24,50 +24,49 @@ topics: - Notifications - Accounts --- +## Using Git -## Utilizar GitHub +To use Git on the command line, you'll need to download, install, and configure Git on your computer. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. También puedes instalar el {% data variables.product.prodname_cli %} para utilizar {% data variables.product.prodname_dotcom %} desde la línea de comandos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +If you want to work with Git locally, but don't want to use the command line, you can instead download and install the [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) client. For more information, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)." -Si deseas trabajar con Git de forma local, pero no deseas utilizar la línea de comando, puedes descargar e instalar en su lugar el cliente [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obtener más información, consulta la sección "[Instalar y configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". +If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including: -Si no deseas trabajar con archivos de forma local, {% data variables.product.product_name %} te permite realizar muchas acciones relacionadas con Git de forma directa en el navegador, lo que incluye: +- [Creating a repository](/articles/create-a-repo) +- [Forking a repository](/articles/fork-a-repo) +- [Managing files](/repositories/working-with-files/managing-files) +- [Being social](/articles/be-social) -- [Crear un repositorio](/articles/create-a-repo) -- [Bifurcar un repositorio](/articles/fork-a-repo) -- [Administrar archivos](/repositories/working-with-files/managing-files) -- [Socializar](/articles/be-social) +## Setting up Git -## Configurar Git +1. [Download and install the latest version of Git](https://git-scm.com/downloads). +2. [Set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). +3. [Set your commit email address in Git](/articles/setting-your-commit-email-address). -1. [Descarga e instala la última versión de Git](https://git-scm.com/downloads). -2. [Configura tu nombre de usuario en Git](/github/getting-started-with-github/setting-your-username-in-git). -3. [Configura tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address). +## Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git -## Pasos siguientes: Autenticación con {% data variables.product.prodname_dotcom %} desde Git - -Cuando te conectas a un repositorio {% data variables.product.prodname_dotcom %} desde Git, deberás autenticarte con {% data variables.product.product_name %} utilizando HTTPS o SSH. +When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. {% note %} -**Nota:** Puedes autenticarte en {% data variables.product.product_name %} utilizando el {% data variables.product.prodname_cli %} ya sea para HTTP o SSH. Para obtener más información, consulta [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). {% endnote %} -### Conectar por HTTPS (recomendado) +### Connecting over HTTPS (recommended) -Si [clonas con HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), puedes [almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) utilizando un asistente de credenciales. +If you [clone with HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), you can [cache your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) using a credential helper. -### Conectar por SSH +### Connecting over SSH -Si clonas [con SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), debes [generar las claves de SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) en cada computadora que utilices para subir o extraer desde {% data variables.product.product_name %}. +If you [clone with SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), you must [generate SSH keys](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on each computer you use to push or pull from {% data variables.product.product_name %}. -## Celebrar +## Celebrate -¡Felicitaciones, ahora tienes configurado todo Git y {% data variables.product.prodname_dotcom %}! Ahora puedes elegir crear un repositorio en donde puedas poner tus proyectos. Esta es una forma excelente de respaldar tu código y facilita compartirlo en todo el mundo. Para obtener más información, consulta "[Crear un repositorio](/articles/create-a-repo)". +Congratulations, you now have Git and {% data variables.product.prodname_dotcom %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)". -Puedes crear una copia de un repositorio si la bifurcas y propones los cambios que quieres ver si afectar al repositorio de nivel superior. Para obtener más información, consulta "[Bifurcar un repositorio](/articles/fork-a-repo)." +You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "[Fork a repository](/articles/fork-a-repo)." -Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. Puedes interactuar con las personas, repositorios y organizaciones conectándote y siguiéndolos en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Sé sociable ](/articles/be-social)". +Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)." {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-ES/content/get-started/signing-up-for-github/index.md b/translations/es-ES/content/get-started/signing-up-for-github/index.md index acb0eb8d18..5b9a0d3fcd 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/index.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/index.md @@ -1,9 +1,9 @@ --- -title: Registrarse en GitHub -intro: 'Comienza a utilizar {% data variables.product.prodname_dotcom %} para ti mismo o para tu equipo.' +title: Signing up for GitHub +intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.' redirect_from: - /articles/signing-up-for-github - - /github/getting-started-with-github/signing-up-for-github/ + - /github/getting-started-with-github/signing-up-for-github versions: fpt: '*' ghes: '*' @@ -16,5 +16,6 @@ children: - /verifying-your-email-address - /setting-up-a-trial-of-github-enterprise-cloud - /setting-up-a-trial-of-github-enterprise-server + - /setting-up-a-trial-of-github-ae --- diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md new file mode 100644 index 0000000000..895f30fd9d --- /dev/null +++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md @@ -0,0 +1,69 @@ +--- +title: Setting up a trial of GitHub AE +intro: 'You can try {% data variables.product.prodname_ghe_managed %} for free.' +versions: + ghae: '*' +topics: + - Accounts +shortTitle: GitHub AE trial +--- + +## About the {% data variables.product.prodname_ghe_managed %} trial + +You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region. + +- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance. +- **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at https://portal.azure.com. This is used to deploy the {% data variables.product.prodname_ghe_managed %} account. + +## Setting up your trial of {% data variables.product.prodname_ghe_managed %} + + +Before you can start your trial of {% data variables.product.prodname_ghe_managed %}, you must request access by contacting your {% data variables.product.prodname_dotcom %} account team. {% data variables.product.prodname_dotcom %} will enable the {% data variables.product.prodname_ghe_managed %} trial for your Azure subscription. + +Contact {% data variables.contact.contact_enterprise_sales %} to check your eligibility for a {% data variables.product.prodname_ghe_managed %} trial. + +## Deploying {% data variables.product.prodname_ghe_managed %} with the {% data variables.actions.azure_portal %} + +The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.prodname_ghe_managed %} account in your Azure resource group. + +1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}. + ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png) +1. To begin the process of adding a new {% data variables.product.prodname_ghe_managed %} account, click **Create GitHub AE account**. +1. Complete the "Project details" and "Instance details" fields. + ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png) + - **Account name:** The hostname for your enterprise + - **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.prodname_ghe_managed %} + - **Administrator email:** The email address that will receive the login information +1. To review a summary of the proposed changes, click **Review + create**. +1. After the validation process has completed, click **Create**. + +The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." + +{% note %} + +**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} instance are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." + +{% endnote %} + +## Navigating to your enterprise + +You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region. + +1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**. +1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: + ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png) + +## Next steps + +Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)." + +## Finishing your trial + +You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted. + +If you need more time to evaluate {% data variables.product.prodname_ghe_managed %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension. + +## Further reading + +- "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)" +- "[{% data variables.product.prodname_ghe_managed %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)" diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md index ba8a064edd..8c44c1a59a 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -29,7 +29,7 @@ You can use organizations for free with {% data variables.product.prodname_free_ ## About trials of {% data variables.product.prodname_ghe_cloud %} -You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "About billing for {% data variables.product.prodname_marketplace %}." +You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "About billing for {% data variables.product.prodname_marketplace %}." Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats. diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 2f786d49a4..6b47866c00 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -2,7 +2,7 @@ title: Setting up a trial of GitHub Enterprise Server intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.' redirect_from: - - /articles/requesting-a-trial-of-github-enterprise/ + - /articles/requesting-a-trial-of-github-enterprise - /articles/setting-up-a-trial-of-github-enterprise-server - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server - /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server diff --git a/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md index 9fb9cf1999..ec5d6be37c 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md @@ -1,9 +1,9 @@ --- -title: Verificar tu dirección de correo electrónico -intro: 'Verificar tu dirección principal de correo electrónico garantiza mayor seguridad, permite que el personal {% data variables.product.prodname_dotcom %} te ayude mejor si olvidas tu contraseña y te brinda acceso a más funciones en {% data variables.product.prodname_dotcom %}.' +title: Verifying your email address +intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.' redirect_from: - - /articles/troubleshooting-email-verification/ - - /articles/setting-up-email-verification/ + - /articles/troubleshooting-email-verification + - /articles/setting-up-email-verification - /articles/verifying-your-email-address - /github/getting-started-with-github/verifying-your-email-address - /github/getting-started-with-github/signing-up-for-github/verifying-your-email-address @@ -12,59 +12,60 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Verificar tu dirección de correo electrónico +shortTitle: Verify your email address --- +## About email verification -## Acerca de la verificación del correo electrónico +You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified. -Puedes verificar tu dirección de correo electrónico después de registrarte con una cuenta nueva o cuando agregas una dirección de correo electrónico nueva. Si una dirección de correo electrónico no es válida para el envío o devuelve correos, quedará como no verificada. - -Si no verificas tu dirección de correo electrónico, no podrás hacer lo siguiente: - - Crear o bifurcar repositorios - - Crear propuestas o solicitudes de extracción - - Comentar sobre las propuestas, solicitudes de extracción o confirmaciones - - Autorizar aplicaciones de {% data variables.product.prodname_oauth_app %} - - Generar tokens de acceso personal - - Recibir notificaciones por correo electrónico - - Poner estrellas en repositorios - - Crear o actualizar tableros de proyecto, incluido agregar tarjetas - - Crear o actualizar gists - - Crear o utilizar {% data variables.product.prodname_actions %} - - Patrocinar desarrolladores con {% data variables.product.prodname_sponsors %} +If you do not verify your email address, you will not be able to: + - Create or fork repositories + - Create issues or pull requests + - Comment on issues, pull requests, or commits + - Authorize {% data variables.product.prodname_oauth_app %} applications + - Generate personal access tokens + - Receive email notifications + - Star repositories + - Create or update project boards, including adding cards + - Create or update gists + - Create or use {% data variables.product.prodname_actions %} + - Sponsor developers with {% data variables.product.prodname_sponsors %} {% warning %} -**Advertencias**: +**Warnings**: - {% data reusables.user_settings.no-verification-disposable-emails %} - {% data reusables.user_settings.verify-org-approved-email-domain %} {% endwarning %} -## Verificar tu dirección de correo electrónico +## Verifying your email address {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.emails %} -1. Debajo de tu dirección de correo electrónico, da clic en **Reenviar correo de verificación**. ![Reenviar enlace de verificación por correo electrónico](/assets/images/help/settings/email-verify-button.png) -4. {% data variables.product.prodname_dotcom %} te enviará un correo electrónico con un enlace. Después de hacer clic en el enlace, se te llevará a tu tablero {% data variables.product.prodname_dotcom %} y verás un mensaje emergente de confirmación. ![Mensaje emergente que confirma que se verificó tu correo electrónico](/assets/images/help/settings/email-verification-confirmation-banner.png) +1. Under your email address, click **Resend verification email**. + ![Resend verification email link](/assets/images/help/settings/email-verify-button.png) +4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner. + ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png) -## Solución de problemas de verificación de correo electrónico +## Troubleshooting email verification -### No se pudo enviar el correo electrónico de verificación +### Unable to send verification email {% data reusables.user_settings.no-verification-disposable-emails %} -### Página de error después de hacer clic en el enlace de verificación +### Error page after clicking verification link -El enlace de verificación vence después de 24 horas. Si no verificas tu correo electrónico dentro de las 24 horas, puedes solicitar otro enlace de verificación de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". +The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)." If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}. 1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}. -2. Sal y vuelve a iniciar tu navegador. +2. Quit and restart your browser. 3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}. -4. Haz clic en el enlace de verificación del correo electrónico que te enviamos. +4. Click on the verification link in the email we sent you. -## Leer más +## Further reading -- "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)" +- "[Changing your primary email address](/articles/changing-your-primary-email-address)" diff --git a/translations/es-ES/content/get-started/using-git/about-git-rebase.md b/translations/es-ES/content/get-started/using-git/about-git-rebase.md index 0fe4205bad..e6fc3b9603 100644 --- a/translations/es-ES/content/get-started/using-git/about-git-rebase.md +++ b/translations/es-ES/content/get-started/using-git/about-git-rebase.md @@ -1,7 +1,7 @@ --- title: About Git rebase redirect_from: - - /rebase/ + - /rebase - articles/interactive-rebase/ - /articles/about-git-rebase - /github/using-git/about-git-rebase diff --git a/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md b/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md index 9c66795346..d807a05e15 100644 --- a/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md +++ b/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md @@ -1,45 +1,44 @@ --- -title: Acerca de las fusiones de subárbol de Git +title: About Git subtree merges redirect_from: - - /articles/working-with-subtree-merge/ - - /subtree-merge/ + - /articles/working-with-subtree-merge + - /subtree-merge - /articles/about-git-subtree-merges - /github/using-git/about-git-subtree-merges - /github/getting-started-with-github/about-git-subtree-merges - /github/getting-started-with-github/using-git/about-git-subtree-merges -intro: 'Si necesitas gestionar múltiples proyectos dentro de un solo repositorio, puedes usar una "fusión de subárbol" para manejar todas las referencias.' +intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +## About subtree merges -## Acerca de las fusiones de subárboles +Typically, a subtree merge is used to contain a repository within a repository. The "subrepository" is stored in a folder of the main repository. -Habitualmente, una fusión de subárbol se usa para contener un repositorio dentro de otro repositorio. El "subrepositorio" se almacena en una carpeta del repositorio principal. +The best way to explain subtree merges is to show by example. We will: -La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Haremos lo siguiente: +- Make an empty repository called `test` that represents our project +- Merge another repository into it as a subtree called `Spoon-Knife`. +- The `test` project will use that subproject as if it were part of the same repository. +- Fetch updates from `Spoon-Knife` into our `test` project. -- Crear un repositorio vacío llamado `test` que represente nuestro proyecto. -- Fusionar otro repositorio en él como un subárbol llamado `Spoon-Knife`. -- El proyecto `test` usará ese subproyecto como si fuera parte del mismo repositorio. -- Recuperar actualizaciones desde `Spoon-Knife` hacia el proyecto `test`. - -## Configurar el repositorio vacío para una fusión de subárbol +## Setting up the empty repository for a subtree merge {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crear un directorio nuevo y navegar a él. +2. Create a new directory and navigate to it. ```shell $ mkdir test $ cd test ``` -3. Inicializar un repositorio de Git nuevo. +3. Initialize a new Git repository. ```shell $ git init > Initialized empty Git repository in /Users/octocat/tmp/test/.git/ ``` -4. Crear y confirmar un archivo nuevo. +4. Create and commit a new file. ```shell $ touch .gitignore $ git add .gitignore @@ -49,9 +48,9 @@ La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Ha > create mode 100644 .gitignore ``` -## Agregar un nuevo repositorio como subárbol +## Adding a new repository as a subtree -1. Agregar una URL remota nueva que apunte a un proyecto por separado en el que estemos interesados. +1. Add a new remote URL pointing to the separate project that we're interested in. ```shell $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git > Updating spoon-knife @@ -64,52 +63,52 @@ La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Ha > From git://github.com/octocat/Spoon-Knife > * [new branch] main -> Spoon-Knife/main ``` -2. Fusionar el proyecto `Spoon-Knife` en el proyecto de Git local. Esto no modifica ninguno de tus archivos localmente, pero prepara Git para el siguiente paso. +2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step. - Si estás usando Git 2.9 o superior: + If you're using Git 2.9 or above: ```shell $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main > Automatic merge went well; stopped before committing as requested ``` - Si estás usando Git 2.8 o inferior: + If you're using Git 2.8 or below: ```shell $ git merge -s ours --no-commit spoon-knife/main > Automatic merge went well; stopped before committing as requested ``` -3. Crear un nuevo directorio denominado **spoon-knife**, y copiar el historial de Git del proyecto `Spoon-Knife` en él. +3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it. ```shell $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main ``` -4. Confirmar los cambios para mantenerlos seguros. +4. Commit the changes to keep them safe. ```shell $ git commit -m "Subtree merged in spoon-knife" > [main fe0ca25] Subtree merged in spoon-knife ``` -Aunque solo hemos agregado un subproyecto, se puede incorporar cualquier número de subproyectos en un repositorio de Git. +Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository. {% tip %} -**Sugerencia**: Si creas un clon nuevo del repositorio en el futuro, no se crearán los remotos que agregaste. Deberás volver a agregarlos mediante [el comando `git remote add`](/github/getting-started-with-github/managing-remote-repositories). +**Tip**: If you create a fresh clone of the repository in the future, the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories). {% endtip %} -## Sincronizando con actualizaciones y cambios +## Synchronizing with updates and changes -Cuando se agrega un subproyecto, no se mantiene sincronizado automáticamente con los cambios ascendentes. Necesitarás actualizar el subproyecto con el siguiente comando: +When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command: ```shell $ git pull -s subtree remotename branchname ``` -Para el ejemplo de más arriba, esto sería: +For the example above, this would be: ```shell $ git pull -s subtree spoon-knife main ``` -## Leer más +## Further reading -- [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)" +- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) +- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)" diff --git a/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md index 209c0beb0e..63fa47a4cd 100644 --- a/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md +++ b/translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md @@ -2,7 +2,7 @@ title: Getting changes from a remote repository intro: You can use common Git commands to access remote repositories. redirect_from: - - /articles/fetching-a-remote/ + - /articles/fetching-a-remote - /articles/getting-changes-from-a-remote-repository - /github/using-git/getting-changes-from-a-remote-repository - /github/getting-started-with-github/getting-changes-from-a-remote-repository diff --git a/translations/es-ES/content/get-started/using-git/index.md b/translations/es-ES/content/get-started/using-git/index.md index 077d3fd73a..d0382733d1 100644 --- a/translations/es-ES/content/get-started/using-git/index.md +++ b/translations/es-ES/content/get-started/using-git/index.md @@ -1,15 +1,15 @@ --- -title: Utilizar GitHub -intro: 'Utiliza Git para administrar tus repositorios de {% data variables.product.product_name %} desde tu computadora.' +title: Using Git +intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.' redirect_from: - /articles/using-common-git-commands - /github/using-git/using-common-git-commands - /github/using-git/using-advanced-git-commands - - /categories/52/articles/ - - /categories/advanced-git/ + - /categories/52/articles + - /categories/advanced-git - /articles/using-advanced-git-commands - /github/using-git/changing-author-info - - /github/getting-started-with-github/using-git/ + - /github/getting-started-with-github/using-git versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md index 8303fb27d5..b5c8c33262 100644 --- a/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md @@ -2,7 +2,7 @@ title: Pushing commits to a remote repository intro: Use `git push` to push commits made on your local branch to a remote repository. redirect_from: - - /articles/pushing-to-a-remote/ + - /articles/pushing-to-a-remote - /articles/pushing-commits-to-a-remote-repository - /github/using-git/pushing-commits-to-a-remote-repository - /github/getting-started-with-github/pushing-commits-to-a-remote-repository diff --git a/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index f070c323c5..49eef30c38 100644 --- a/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -1,7 +1,7 @@ --- title: Splitting a subfolder out into a new repository redirect_from: - - /articles/splitting-a-subpath-out-into-a-new-repository/ + - /articles/splitting-a-subpath-out-into-a-new-repository - /articles/splitting-a-subfolder-out-into-a-new-repository - /github/using-git/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository diff --git a/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md index 099782a075..95a87525e4 100644 --- a/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md +++ b/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md @@ -1,25 +1,24 @@ --- -title: Utilizar la rebase de Git en la línea de comando +title: Using Git rebase on the command line redirect_from: - - /articles/using-git-rebase/ + - /articles/using-git-rebase - /articles/using-git-rebase-on-the-command-line - /github/using-git/using-git-rebase-on-the-command-line - /github/getting-started-with-github/using-git-rebase-on-the-command-line - /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line -intro: Aquí hay un breve tutorial acerca de usar `git rebase` en la línea de comando. +intro: Here's a short tutorial on using `git rebase` on the command line. versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -shortTitle: Rebase de Git +shortTitle: Git rebase --- +## Using Git rebase -## Utilizar el rebase de Git +In this example, we will cover all of the `git rebase` commands available, except for `exec`. -En este ejemplo, abordaremos todos los comandos disponibles de `git rebase`, excepto `exec`. - -Comenzaremos nuestra rebase ingresando `git rebase --interactive HEAD~7` en el terminal. Nuestro editor de texto preferido mostrará las siguientes líneas: +We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines: ``` pick 1fc6c95 Patch A @@ -31,17 +30,17 @@ pick 4ca2acc i cant' typ goods pick 7b36971 something to move before patch B ``` -En este ejemplo, haremos lo siguiente: +In this example, we're going to: -* Combinar la quinta confirmación (`fa39187`) con la confirmación `"Patch A"` (`1fc6c95`), utilizando `squash` (combinar). -* Mover la última confirmación (`7b36971`) hacia arriba antes de la confirmación `"Patch B"` (`6b2481b`) y la conservarla como `pick`. -* Fusionar la confirmación `"A fix for Patch B"` (`c619268`) con la confirmación `"Patch B"` (`6b2481b`) y omitir el mensaje de confirmación utilizando `fixup`. -* Separar la tercera confirmación (`dd1475d`) en dos confirmaciones más pequeñas utilizando `edit` (editar). -* Corregir el mensaje de confirmación de la confirmación mal escrita (`4ca2acc`), utilizando `reword` (otro texto). +* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`. +* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`. +* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`. +* Split the third commit (`dd1475d`) into two smaller commits, using `edit`. +* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`. -¡Uf! Parece mucho trabajo, pero haciendo cada paso por vez, podemos concretar esos cambios fácilmente. +Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes. -Para comenzar, tendremos que modificar los comandos en el archivo para que luzca como sigue: +To start, we'll need to modify the commands in the file to look like this: ``` pick 1fc6c95 Patch A @@ -53,35 +52,35 @@ edit dd1475d something I want to split reword 4ca2acc i cant' typ goods ``` -Hemos cambiado cada comando de la línea desde `pick` al comando que nos interesa. +We've changed each line's command from `pick` to the command we're interested in. -Ahora, guarda y cierra el editor; esto comenzará la rebase interactiva. +Now, save and close the editor; this will start the interactive rebase. -Git saltea el primer comando de rebase, `pick 1fc6c95`, ya que no necesita hacer nada. Va al siguiente comando, `squash fa39187`. Como esta operación requiere tu entrada, Git vuelve a abrir tu editor de texto. El archivo que abre luce parecido a lo siguiente: +Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this: ``` -# Es una combinación de dos confirmaciones. -# El mensaje de la primera confirmación es: +# This is a combination of two commits. +# The first commit's message is: Patch A -# Este es el mensaje de la 2.a confirmación: +# This is the 2nd commit message: something to add to patch A -# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con -# con '#' se ignoran, y un mensaje vacío anula la confirmación. -# Actualmente no se encuentra en una rama. -# Cambios por confirmar: -# (usa "git reset HEAD ..." para deshacer) +# Please enter the commit message for your changes. Lines starting +# with '#' will be ignored, and an empty message aborts the commit. +# Not currently on any branch. +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) # -# modificado: a +# modified: a # ``` -Este archivo es la manera de Git de decir, "Oye, esto es lo que estoy a punto de hacer con esta `squash` (combinación)". Detalla el primer mensaje de confirmación (`"Patch A"`) y el segundo mensaje de confirmación (`"something to add to patch A"`). Si estás satisfecho con estos mensajes de confirmación, puedes guardar el archivo y cerrar el editor. De lo contrario, tienes la opción de cambiar el mensaje de confirmación, simplemente, cambiando el texto. +This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text. -Cuando el editor esté cerrado, la rebase continúa: +When the editor is closed, the rebase continues: ``` pick 1fc6c95 Patch A @@ -93,42 +92,42 @@ edit dd1475d something I want to split reword 4ca2acc i cant' typ goods ``` -Git procesa los dos comandos `pick` (para `pick 7b36971` y `pick 6b2481b`). *También* procesa el comando `fixup` (`fixup c619268`), ya que este no necesita ninguna interacción. `fixup` fusiona los cambios de `c619268` en la confirmación que tiene ante sí, `6b2481b`. Ambos cambios tendrán el mismo mensaje de confirmación: `"Patch B"`. +Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`. -Git llega a la operación `edit dd1475d`, se detiene e imprime el siguiente mensaje para el terminal: +Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal: ```shell -Puedes modificar la confirmación ahora con +You can amend the commit now, with git commit --amend -Una vez que estés satisfecho con tus cambios, ejecuta +Once you are satisfied with your changes, run git rebase --continue ``` -En este punto, puedes editar cualquiera de los archivos de tu proyecto para hacer más cambios. Para cada cambio que hagas, tendrás que realizar una confirmación nueva. Lo puedes hacer ingresando el comando `git commit --amend`. Cuando termines de hacer todos tus cambios, puedes ejecutar `git rebase --continue`. +At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`. -Luego Git llega al comando `reword 4ca2acc`. Este abre tu editor de texto una vez más y presenta la siguiente información: +Git then gets to the `reword 4ca2acc` command. It opens up your text editor one more time, and presents the following information: ``` i cant' typ goods -# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con -# con '#' se ignoran, y un mensaje vacío anula la confirmación. -# Actualmente no se encuentra en una rama. -# Cambios por confirmar: +# Please enter the commit message for your changes. Lines starting +# with '#' will be ignored, and an empty message aborts the commit. +# Not currently on any branch. +# Changes to be committed: # (use "git reset HEAD^1 ..." to unstage) # -# modificado: a +# modified: a # ``` -Como antes, Git muestra el mensaje de confirmación para que lo edites. Puedes cambiar el texto (`"i cant' typ goods"`), guardar el archivo y cerrar el editor. Git terminará la rebase y te devolverá al terminal. +As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal. -## Subir código de rebase a GitHub +## Pushing rebased code to GitHub -Como has modificado el historial de Git, el `git push origin` común **no** funcionará. Tendrás que modificar el comando realizando un "empuje forzado" de tus últimos cambios: +Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes: ```shell # Don't override changes @@ -140,10 +139,10 @@ $ git push origin main --force {% warning %} -El cargar forzadamente tiene implicaciones serias ya que cambia la secuencia del historial de confirmaciones para la rama. Utilízalo con cuidado, especialmente si muchas personas acceden a tu repositorio. +Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people. {% endwarning %} -## Leer más +## Further reading -* "[Resolver conflictos de fusión después de una rebase de Git](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)" +* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)" diff --git a/translations/es-ES/content/get-started/using-github/github-mobile.md b/translations/es-ES/content/get-started/using-github/github-mobile.md new file mode 100644 index 0000000000..76e50e0dd8 --- /dev/null +++ b/translations/es-ES/content/get-started/using-github/github-mobile.md @@ -0,0 +1,91 @@ +--- +title: GitHub Mobile +intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' +versions: + fpt: '*' + ghes: '*' + ghec: '*' +topics: + - Mobile +redirect_from: + - /get-started/using-github/github-for-mobile + - /github/getting-started-with-github/github-for-mobile + - /github/getting-started-with-github/using-github/github-for-mobile +--- +{% data reusables.mobile.ghes-release-phase %} + +## About {% data variables.product.prodname_mobile %} + +{% data reusables.mobile.about-mobile %} + +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. + +With {% data variables.product.prodname_mobile %} you can: +- Manage, triage, and clear notifications +- Read, review, and collaborate on issues and pull requests +- Search for, browse, and interact with users, repositories, and organizations +- Receive a push notification when someone mentions your username + +For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." + +## Installing {% data variables.product.prodname_mobile %} + +To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% 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 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. + +### Prerequisites + +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 %}. + +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} + +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 %}. + +### Adding, switching, or signing out of accounts + +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. + +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. + +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**. + +## Supported languages for {% data variables.product.prodname_mobile %} + +{% data variables.product.prodname_mobile %} is available in the following languages. + +- English +- Japanese +- Brazilian Portuguese +- Simplified Chinese +- Spanish + +If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. + +## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS + +{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site. + +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. + +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. + +## Sharing feedback + +If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at mobilefeedback@github.com. + +You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). + +## Opting out of beta releases for iOS + +If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time. + +1. On your iOS device, open the TestFlight app. +2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**. +3. At the bottom of the page, tap **Stop Testing**. diff --git a/translations/es-ES/content/get-started/using-github/index.md b/translations/es-ES/content/get-started/using-github/index.md index c02c7f63b9..d0e1e4d2f2 100644 --- a/translations/es-ES/content/get-started/using-github/index.md +++ b/translations/es-ES/content/get-started/using-github/index.md @@ -1,9 +1,9 @@ --- -title: Utilizar GitHub -intro: 'Explorar los productos de {% data variables.product.company_short %} desde plataformas y dispositivos diversos.' +title: Using GitHub +intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.' redirect_from: - /articles/using-github - - /github/getting-started-with-github/using-github/ + - /github/getting-started-with-github/using-github versions: fpt: '*' ghes: '*' @@ -14,9 +14,8 @@ children: - /supported-browsers - /github-cli - /github-desktop - - /github-for-mobile + - /github-mobile - /keyboard-shortcuts - /github-command-palette - /troubleshooting-connectivity-problems --- - diff --git a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md index bc0dfabdb6..2265ca6c86 100644 --- a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md @@ -2,9 +2,9 @@ title: Keyboard shortcuts intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.' redirect_from: - - /articles/using-keyboard-shortcuts/ - - /categories/75/articles/ - - /categories/keyboard-shortcuts/ + - /articles/using-keyboard-shortcuts + - /categories/75/articles + - /categories/keyboard-shortcuts - /articles/keyboard-shortcuts - /github/getting-started-with-github/keyboard-shortcuts - /github/getting-started-with-github/using-github/keyboard-shortcuts @@ -53,7 +53,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a |.| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %} | control b or command b | Inserts Markdown formatting for bolding text | control i or command i | Inserts Markdown formatting for italicizing text -| control k or command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %} +| control k or command k | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %} | control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list | control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %} @@ -88,14 +88,14 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ | control b or command b | Inserts Markdown formatting for bolding text -| control i or command i | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} +| control i or command i | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %} | control e or command e | Inserts Markdown formatting for code or a command within a line{% endif %} | control k or command k | Inserts Markdown formatting for creating a link -| control shift p or command shift p| Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} +| control shift p or command shift p| Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %} | control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} | control enter | Submits a comment -| control . and then control [saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae-next or ghes > 3.2 or ghec %} +| control . and then control [saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %} | control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} |control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} | r | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | diff --git a/translations/es-ES/content/get-started/using-github/supported-browsers.md b/translations/es-ES/content/get-started/using-github/supported-browsers.md index dd9faeb2f6..610b6584c6 100644 --- a/translations/es-ES/content/get-started/using-github/supported-browsers.md +++ b/translations/es-ES/content/get-started/using-github/supported-browsers.md @@ -1,23 +1,22 @@ --- -title: Navegadores compatibles +title: Supported browsers redirect_from: - - /articles/why-doesn-t-graphs-work-with-ie-8/ - - /articles/why-don-t-graphs-work-with-ie8/ + - /articles/why-doesn-t-graphs-work-with-ie-8 + - /articles/why-don-t-graphs-work-with-ie8 - /articles/supported-browsers - /github/getting-started-with-github/supported-browsers - /github/getting-started-with-github/using-github/supported-browsers -intro: 'Diseñamos {% data variables.product.product_name %} para admitir las últimas versiones de los navegadores web. Admitimos las versiones actuales de [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), y [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).' +intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' --- +## Firefox Extended Support Release -## Lanzamiento de soporte extendido de Firefox +We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox. -Nos esforzamos para admitir el más reciente [Lanzamiento de soporte extendido](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) de Firefox. Las versiones anteriores de Firefox pueden inhabilitar algunas funciones en {% data variables.product.product_name %} y necesitan la última versión de Firefox. +## Beta and developer builds -## Construcciones de programador y beta - -Puedes encontrar errores inesperados en beta y en construcciones de programador de nuestros navegadores compatibles. Si encuentras un error en {% data variables.product.product_name %} en uno de estas construcciones no lanzadas, verifica que también exista en la versión estable del mismo navegador. Si el error solo existe en la versión inestable, considera informar el error al programador del navegador. +You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer. diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 5798f99a5f..ceaaf6c438 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -1,6 +1,6 @@ --- -title: Extensiones e integraciones de GitHub -intro: 'Utiliza las extensiones {% data variables.product.product_name %} para trabajar sin inconvenientes en los repositorios {% data variables.product.product_name %} dentro de las aplicaciones de terceros.' +title: GitHub extensions and integrations +intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.' redirect_from: - /articles/about-github-extensions-for-third-party-applications/ - /articles/github-extensions-and-integrations @@ -8,45 +8,44 @@ redirect_from: versions: fpt: '*' ghec: '*' -shortTitle: Extensiones & integraciones +shortTitle: Extensions & integrations --- +## Editor tools -## Herramientas del editor +You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio. -Puedes conectarte a los repositorios de {% data variables.product.product_name %} dentro de las herramientas de edición de terceros tales como Atom, Unity y Visual Studio. +### {% data variables.product.product_name %} for Atom -### {% data variables.product.product_name %} para Atom +With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/). -Con el {% data variables.product.product_name %} para la extensión de Atom, puedes confirmar, subir, extraer, resolver conflictos de fusión y mucho más desde el editor de Atom. Para obtener más información, consulta el [{% data variables.product.product_name %} oficial para el sitio de Atom](https://github.atom.io/). +### {% data variables.product.product_name %} for Unity -### {% data variables.product.product_name %} para Unity +With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs). -Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs). +### {% data variables.product.product_name %} for Visual Studio -### {% data variables.product.product_name %} para Visual Studio +With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). -Con el {% data variables.product.product_name %} para la extensión de Visual Studio, puedes trabajar en los repositorios {% data variables.product.product_name %} sin salir de Visual Studio. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de Visual Studio o la [documentación](https://github.com/github/VisualStudio/tree/master/docs). +### {% data variables.product.prodname_dotcom %} for Visual Studio Code -### {% data variables.product.prodname_dotcom %} para Visual Studio Code +With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). -Con el {% data variables.product.prodname_dotcom %} para la extensión de Visual Studio Code, puedes revisar y administrar solicitudes de extracción {% data variables.product.product_name %} en Visual Studio Code. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de Visual Studio Code o la [documentación](https://github.com/Microsoft/vscode-pull-request-github). - -## Herramientas de gestión de proyectos +## Project management tools You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira. -### Integración de Jira Cloud y {% data variables.product.product_name %}.com +### Jira Cloud and {% data variables.product.product_name %}.com integration -Puedes integrar Jira Cloud con tu cuenta personal o de organización para escanear confirmaciones y solicitudes de extracción, y crear los metadatos e hipervínculos correspondientes en cualquiera de las propuestas de Jira mencionadas. Para obtener más información, visita la [App de integración de Jira](https://github.com/marketplace/jira-software-github) en marketplace. +You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace. -## Herramientas de comunicación para equipos +## Team communication tools You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams. -### Integración con Slack y con {% data variables.product.product_name %} +### Slack and {% data variables.product.product_name %} integration -Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, confirmaciones, lanzamientos, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Slack. Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace. -### Microsoft Teams y su integración con {% data variables.product.product_name %} +### Microsoft Teams and {% data variables.product.product_name %} integration -Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambios, confirmaciones, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas, comentar en tus propuestas o solicitudes de cambios y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource. +You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource. diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md index a526e281f2..b8c5e0a166 100644 --- a/translations/es-ES/content/github/index.md +++ b/translations/es-ES/content/github/index.md @@ -20,5 +20,4 @@ children: - /understanding-how-github-uses-and-protects-your-data - /site-policy - /site-policy-deprecated - - /setting-up-and-managing-your-enterprise --- diff --git a/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md index 3fe119cf44..02ffbb9d03 100644 --- a/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -20,7 +20,7 @@ By using the Additional Products and Features, you also agree to the applicable - **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images. -- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages. +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages. ## Actions GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. @@ -68,7 +68,7 @@ Codespaces allows you to load extensions from the Microsoft Visual Studio Market The generally available version of Codespaces is not currently available for U.S. government customers. U.S. government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews). ## Connect -With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% ifversion ghae-next %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% ifversion ghae-next %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). +With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% ifversion ghae %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% ifversion ghae %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). ## GitHub Enterprise Importer Importer is a framework for exporting data from other sources to be imported to the GitHub platform. Importer is provided “AS-IS”. 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 18bd27176c..a52889b4c1 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 @@ -1,5 +1,5 @@ --- -title: Términos de servicio de GitHub +title: GitHub Terms of Service redirect_from: - /tos/ - /terms/ @@ -13,303 +13,303 @@ topics: - Legal --- -¡Gracias por usar GitHub! Estamos felices de que estés aquí. Por favor, lee cuidadosamente estos Términos de Servicio antes de ingresar o usar GitHub. Ya que se trata de un contrato tan importante entre nosotros y nuestros usuarios, intentamos ser muy claros. Para tu comodidad, presentamos estos términos en un breve resumen no vinculante seguido de los términos legales completos. +Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms. -## Resumen +## Summary -| Sección | ¿Qué puedes encontrar allí? | -| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [A. Definiciones](#a-definitions) | Algunos términos básicos, definidos de forma que te ayude a entender este acuerdo. Consulta la copia de seguridad de esta sección para obtener una aclaración. | -| [B. Términos de la cuenta](#b-account-terms) | Estos son los requisitos básicos para tener una cuenta en GitHub. | -| [C. Uso aceptable](#c-acceptable-use) | Estas son las reglas básicas que debes seguir cuando uses tu cuenta de GitHub. | -| [D. Contenido generado por el usuario](#d-user-generated-content) | Eres responsable del contenido que publicas en GitHub. Sin embargo, tienes ciertas responsabilidades al respecto y te pedimos que nos otorgues algunos derechos de manera que podamos proporcionarte los servicios. | -| [E. Repositorios privados](#e-private-repositories) | Esta sección expone cómo tratará GitHub el contenido que publiques en los repositorios privados. | -| [F. Copyright & Política DMCA](#f-copyright-infringement-and-dmca-policy) | Esta sección explica la forma en la que GitHub responderá si crees que alguien está infringiendo tus derechos de autor en GitHub. | -| [G. Notificación de propiedad intelectual](#g-intellectual-property-notice) | Describe los derechos de GitHub en el sitio web y el servicio. | -| [H. Términos de la API](#h-api-terms) | Estas son las reglas para usar las API de GitHub, ya sea que estés usando la API para el desarrollo o la recopilación de datos. | -| [I. Términos de producto adicionales](#i-github-additional-product-terms) | Tenemos algunas reglas específicas para las características y productos de GitHub. | -| [J. Vista previa Beta](#j-beta-previews) | Estos son algunos de los términos adicionales que se aplican a las características de GitHub que continúan en desarrollo. | -| [K. Pago](#k-payment) | Eres responsable del pago. Somos responsables de facturarte con exactitud. | -| [L. Cancelación y terminación](#l-cancellation-and-termination) | Puedes cancelar este acuerdo y cerrar tu cuenta en cualquier momento. | -| [M. Comunicaciones con GitHub](#m-communications-with-github) | Sólo utilizamos el correo electrónico y otros medios electrónicos para estar en contacto con nuestros usuarios. No ofrecemos soporte telefónico. | -| [N. Exención de garantías](#n-disclaimer-of-warranties) | Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. **Lee esta sección cuidadosamente; deberías entender qué esperar.** | -| [O. Limitación de responsabilidad](#o-limitation-of-liability) | No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. **Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.** | -| [P. Liberación e indemnización](#p-release-and-indemnification) | Eres completamente responsable de tu uso del servicio. | -| [Q. Cambios a estos Términos de Servicio](#q-changes-to-these-terms) | Podemos modificar este acuerdo, pero te avisaremos con 30 días de antelación de cambios materiales. | -| [R. Varios](#r-miscellaneous) | Consulta esta sección para obtener detalles legales, incluyendo nuestra elección de la ley. | +| Section | What can you find there? | +| --- | --- | +| [A. Definitions](#a-definitions) | Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification. | +| [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub. | +| [C. Acceptable Use](#c-acceptable-use)| These are the basic rules you must follow when using your GitHub Account. | +| [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you. | +| [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. | +| [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. | +| [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. | +| [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs, whether you are using the API for development or data collection. | +| [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. | +| [J. Beta Previews](#j-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. | +| [K. Payment](#k-payment) | You are responsible for payment. We are responsible for billing you accurately. | +| [L. Cancellation and Termination](#l-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. | +| [M. Communications with GitHub](#m-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. | +| [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | +| [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | +| [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. | +| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. | +| [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. | -## Términos de servicio de GitHub -Fecha de entrada en vigencia: 16 de noviembre de 2020 +## The GitHub Terms of Service +Effective date: November 16, 2020 -## A. Definiciones -**Versión resumida:** *Utilizamos estos términos básicos a lo largo del acuerdo y tienen significados específicos. Es necesario que comprendas el significado de cada uno de nuestros términos. No habrá una evaluación sobre ello, pero es información útil.* +## A. Definitions +**Short version:** *We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.* -1. Una "Cuenta" representa tu relación legal con GitHub. Una "Cuenta de Usuario" representa la autorización individual del Usuario para iniciar sesión y utilizar el Servicio y sirve como identidad del Usuario en GitHub. “Organización” se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Una Cuenta de Usuario puede ser miembro de cualquier número de organizaciones. -2. El "Acuerdo" se refiere, colectivamente, a todos los términos, condiciones, avisos contenidos o a los que se hace referencia en el presente documento (los "Términos de Servicio" o los "Términos") y todas las demás reglas de funcionamiento, políticas (incluyendo la Declaración de Privacidad de GitHub, disponible en [github.com/site/privacy](https://github.com/site/privacy)) y procedimientos que podemos publicar de vez en cuando en el Sitio Web. La mayoría de nuestras políticas de sitio están disponibles en [docs.github.com/categories/site-policy](/categories/site-policy). -3. "Vistas Previas Beta" se refiere al software, los servicios o las características identificadas como alfa, beta, vista previa, acceso temprano o evaluación o a las palabras o frases con significados similares. -4. "Contenido" se refiere al contenido presentado o mostrado a través del sitio web, incluyendo, sin limitación al código, texto, datos, artículos, imágenes, fotografías, gráficos, software, aplicaciones, paquetes, diseños, características y otros materiales disponibles en el Sitio Web o disponibles de otra forma a través del Servicio. "Contenido" también incluye Servicios. “Contenido generado por el usuario” es Contenido, escrito o no, creado o cargado por nuestros Usuarios. "Tu Contenido" es Contenido que creas o posees. -5. “GitHub” y “Nosotros” se refieren a GitHub, Inc., así como a nuestros afiliados, directores, subsidiarios, contratistas, licenciadores, oficiales, agentes y empleados. -6. El “Servicio” se refiere a las aplicaciones, software, productos y servicios proporcionados por GitHub, incluyendo cualquier Vista Previa Beta. -7. “El Usuario”, “Tú” y “tu” se refieren a la persona, empresa u organización que ha visitado o está utilizando el Sitio Web o Servicio; que ingresa o utiliza cualquier parte de la Cuenta; o que dirije el uso de la Cuenta en el desempeño de sus funciones. Un usuario debe tener al menos 13 años de edad. Las condiciones especiales pueden aplicarse para cuentas empresariales o gubernamentales (véase [Section B(5): Términos Adicionales](#5-additional-terms)). -8. El "Sitio Web" se refiere al sitio web de GitHub ubicado en [github. om](https://github.com/) y todos los contenidos, servicios y productos proporcionados por GitHub en o a través del sitio web. También se refiere a subdominios propiedad de GitHub de github.com, tales como [education.github.com](https://education.github.com/) y [pages.github.com](https://pages.github.com/). Estos Términos también rigen los sitios web de la conferencia de GitHub, como [githubuniverse.com](https://githubuniverse.com/) y sitios web de productos, como [atom.io](https://atom.io/). Ocasionalmente, los sitios web propiedad de GitHub pueden proporcionar condiciones de servicio diferentes o adicionales. Si estos términos adicionales entran en conflicto con este Contrato, los términos más específicos se aplican a la página o servicio correspondiente. +1. An "Account" represents your legal relationship with GitHub. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations. +2. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/categories/site-policy). +3. "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings. +4. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own. +5. “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees. +6. The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews. +7. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See [Section B(5): Additional Terms](#5-additional-terms)). +8. The “Website” refers to GitHub’s website located at [github.com](https://github.com/), and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites, such as [githubuniverse.com](https://githubuniverse.com/), and product websites, such as [atom.io](https://atom.io/). Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service. -## B. Términos de la cuenta -**Versión resumida:** *Las Cuentas de Usuario y las Organizaciones tienen diferentes controles administrativos; una persona debe crear tu cuenta; debes tener 13 años o más; debes proporcionar una dirección de correo electrónico válida; y no es posible tener más de una cuenta gratuita. Eres el único responsable de tu Cuenta y de todo lo que ocurra mientras estas conectado o usando tu Cuenta. Eres responsable de mantener tu cuenta segura.* +## B. Account Terms +**Short version:** *User Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.* -### 1. Controles de la cuenta -- Usuarios. Sujeto a estos términos, conserva el control administrativo definitivo sobre tu cuenta de usuario y el Contenido dentro de ella. +### 1. Account Controls +- Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it. -- Organizaciones. El "propietario" de una Organización que fue creada bajo estos Términos tiene el control administrativo final sobre esa Organización y el Contenido dentro de ella. Dentro del Servicio, un propietario puede administrar el acceso del Usuario a los datos y proyectos de la Organización. Una Organización puede tener múltiples propietarios, pero debe haber al menos una Cuenta de Usuario designada como propietario de una Organización. Si eres el propietario de una Organización bajo estos términos, te consideramos responsable de las acciones que se llevan a cabo en o a través de dicha Organización. +- Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization. -### 2. Información requerida -Debes proporcionar una dirección de correo electrónico válida para completar el proceso de registro. Cualquier otra información solicitada, como tu nombre real, es opcional, a menos que aceptes estos términos en nombre de una entidad legal (en cuyo caso necesitamos más información sobre la entidad legal) o si optas por una [Cuenta de pago](#k-payment), en cuyo caso será necesaria información adicional para fines de facturación. +### 2. Required Information +You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a [paid Account](#k-payment), in which case additional information will be necessary for billing purposes. -### 3. Requisitos de la cuenta -Tenemos unas cuantas reglas simples para cuentas de usuario en el servicio de GitHub. -- Debes ser una persona para crear una cuenta. No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados. Permitimos cuentas de máquina: -- Una cuenta de máquina se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. No puedes mantener más de una cuenta de máquina gratuita además de tu cuenta de usuario gratuita. -- 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 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). +### 3. Account Requirements +We have a few simple rules for User Accounts on GitHub's Service. +- You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts: +- A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free User Account. +- One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine). +- You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will [terminate that User’s Account immediately](#l-cancellation-and-termination). If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws. +- Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many User Accounts as your subscription allows. +- You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information, please see our [Export Controls policy](/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. -- Eres responsable de todo el contenido publicado y la actividad que se produzca bajo tu Cuenta (incluso cuando el contenido sea publicado por otros que tienen Cuentas bajo tu Cuenta). -- Eres responsable de mantener la seguridad de tu cuenta y contraseña. GitHub no será responsable de ninguna pérdida o daño que surja del incumplimiento de esta obligación de seguridad. -- Debes notificar inmediatamente [a GitHub](https://support.github.com/contact?tags=docs-policy) si tienes conocimiento de cualquier uso no autorizado o acceso a nuestro servicio a través de tu cuenta, incluyendo cualquier uso no autorizado de tu contraseña o cuenta. +### 4. User Account Security +You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you. +- You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account). +- You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. +- You will promptly [notify GitHub](https://support.github.com/contact?tags=docs-policy) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account. -### 5. Términos adicionales -En algunas situaciones, pueden aplicarse términos de terceros a tu uso de GitHub. Por ejemplo, puedes ser miembro de una Organización en GitHub con tus propios términos o acuerdos de licencia; puedes descargar una aplicación que se integre con GitHub; o puedes usar el Servicio para autenticarte a otro servicio. Ten en cuenta que aunque estos Términos son nuestro acuerdo total contigo, los términos de otras partes rigen sus relaciones contigo. +### 5. Additional Terms +In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you. -Si eres un usuario del gobierno o de otro modo accedes o utilizas cualquier servicio de GitHub en una capacidad gubernamental, esta [Enmienda del Gobierno a los Términos de Servicio de GitHub](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) aplican para ti y debes aceptar sus disposiciones. +If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this [Government Amendment to GitHub Terms of Service](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) applies to you, and you agree to its provisions. -Si te registraste en la nube GitHub Enterprise, la [ Apéndice Enterprise Cloud ](/articles/github-enterprise-cloud-addendum/) aplica para ti y debes aceptar sus disposiciones. +If you have signed up for GitHub Enterprise Cloud, the [Enterprise Cloud Addendum](/articles/github-enterprise-cloud-addendum/) applies to you, and you agree to its provisions. -## C. Uso aceptable -**Versión simplificada:** *GitHub presenta una amplia variedad de proyectos en equipo en todo el mundo y dicha cooperación solamente funciona cuando nuestros usuarios pueden trabajar juntos con buenas intenciones. Mientras usas el Servicio, debes cumplir con los términos de esta sección, que incluyen algunas restricciones sobre el contenido que puedes publicar, que realizar en el servicio y otras limitaciones. En síntesis, la idea es que sean geniales entre sí.* +## C. Acceptable Use +**Short version:** *GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.* -Tu uso del sitio web y del servicio no debe violar ninguna ley aplicable, incluyendo leyes de derechos de autor o de marcas, leyes de control de exportación o sanciones, u otras leyes de su jurisdicción. Eres responsable de asegurarte que tu uso del Servicio cumpla con las leyes y cualquier normativa aplicable. +Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations. -Aceptas que en ningún caso violarás nuestras [Políticas de uso aceptable](/articles/github-acceptable-use-policies) o [Directrices de la comunidad](/articles/github-community-guidelines). +You agree that you will not under any circumstances violate our [Acceptable Use Policies](/articles/github-acceptable-use-policies) or [Community Guidelines](/articles/github-community-guidelines). -## D. Contenido generado por el usuario -/**Versión resumida+*:** *Eres propietario del contenido que creas, pero nos permitirás ciertos derechos para que podamos mostrar y compartir el contenido que publiques. Continúas teniendo el control sobre tu contenido y responsabilidad por el mismo y los derechos que nos concedes están limitados a aquellos que necesitamos para proporcionar el servicio. Tenemos derecho a eliminar el contenido o cerrar cuentas si lo necesitamos.* +## D. User-Generated Content +**Short version:** *You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.* -### 1. Responsabilidad para el Contenido generado por el usuario -Puedes crear o cargar Contenido generado por el Usuario mientras usas el Servicio. Eres el único responsable del contenido y por cualquier daño que resulte de cualquier Contenido generado por el Usuario que publiques, cargues, enlaces o que de otra forma esté disponible a través del Servicio, independientemente de la forma de dicho Contenido. No eres responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. +### 1. Responsibility for User-Generated Content +You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content. -### 2. GitHub puede eliminar contenido -Tenemos el derecho de rechazar o eliminar cualquier contenido generado por el usuario que, a nuestro exclusivo criterio, viole alguna ley o [términos o políticas de GitHub](/github/site-policy). El contenido generado por el usuario que se muestra en GitHub para móvil puede estar sujeto a los términos adicionales de las tiendas de aplicaciones móviles. +### 2. GitHub May Remove Content +We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms. -### 3. Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia -Conservas la propiedad y la responsabilidad de tu contenido. Si estás publicando algo que no hayas creado tu mismo o de lo cual no posees los derechos, aceptas que eres responsable de cualquier Contenido que publiques; que sólo enviarás contenido que tengas derecho a publicar; y que cumplirás plenamente con cualquier licencia de terceros relacionada con el Contenido que publiques. +### 3. Ownership of Content, Right to Post, and License Grants +You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post. -Ya que conservas la propiedad y la responsabilidad de tu contenido, necesitamos que nos concedas — y a otros usuarios de GitHub — ciertos permisos legales, listados en las Secciones D. — D.7. Estas licencias se aplican a Tu Contenido. Si cargas Contenido que ya viene con una licencia que le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. Debes comprender que no recibirás ningún pago por ninguno de los derechos otorgados en las Secciones D.4 — D.7. Las licencias que nos concedes terminarán cuando retires Tu Contenido de nuestros servidores, a menos que otros Usuarios lo hayan bifurcado. +Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it. -### 4. Licencia otorgada -Necesitamos el derecho legal de hacer cosas como alojar Tu Contenido, publicarlo y compartirlo. Nos otorgas a nosotros y a nuestros sucesores legales el derecho a almacenar, archivar, analizar y mostrar tu contenido, y hacer copias incidentales, según sea necesario para proporcionar el servicio, incluyendo la mejora del servicio con el paso del tiempo. Esta licencia incluye el derecho a hacer cosas como copiarlo en nuestra base de datos y hacer copias de seguridad; mostrártelo y a otros usuarios; analizarlo en un índice de búsqueda o analizarlo de cualquier otra manera en nuestros servidores; compartirlo con otros usuarios; y reproducirlo, en caso de que tu contenido sea algo así como música o video. +### 4. License Grant to Us +We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. -Esta licencia no le otorga a GitHub el derecho a vender tu contenido. Tampoco le otorga a GitHub el derecho a distribuir o usar tu contenido fuera de nuestra prestación del servicio, excepto que como parte del derecho a archivar tu contenido, GitHub pueda permitir que nuestros socios almacenen y archiven tu contenido en repositorios públicos en conexión con el [GitHub Arctic Code Vault y el programa de archivado de GitHub](https://archiveprogram.github.com/). +This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/). -### 5. Otorgamiento de la licencia a otros Usuarios -Cualquier contenido generado por el usuario que postees públicamente, incluyendo temas, comentarios y contribuciones a los repositorios de otros usuarios, puede ser visto por otros. Al configurar tus repositorios para ser vistos públicamente, aceptas permitir a otros ver y "bifurcar" tus repositorios (esto significa que otros pueden hacer sus propias copias de Contenido de tus repositorios en los repositorios que controlan). +### 5. License Grant to Other Users +Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). -Si configuras tus páginas y repositorios para ser vistos públicamente, estás otorgando a cada usuario de GitHub una licencia no exclusiva a nivel mundial para usar, mostrar, y reproducir Tu Contenido a través del Servicio de GitHub y para reproducir Tu Contenido únicamente en GitHub según lo permitido a través de la funcionalidad de GitHub (por ejemplo, a través de bifurcación). Puedes otorgar derechos adicionales si [adoptas una licencia](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Si estás cargando Contenido que no creaste ni posees, eres responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos. +If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users. -### 6. Contribuciones conforme a la Licencia del repositorio -Cada vez que agregas contenido a un repositorio que contiene un aviso de una licencia, tienes la licencia de ese contenido bajo los mismos términos, y aceptas que tienes el derecho de licenciar dicho contenido conforme a esos términos. Si tienes un acuerdo por separado para licenciar dicho contenido bajo diferentes términos, como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá. +### 6. Contributions Under Repository License +Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. -¿No es así justo como funciona ahora? Sí. Esto se acepta ampliamente como la norma en la comunidad de código abierto; se conoce comúnmente por el abreviado "inbound=outbound". Lo estamos haciendo explícito. +Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit. -### 7. Derechos morales -Conservas todos los derechos morales sobre Tu Contenido que cargas, publicas o envías a cualquier parte del Servicio, incluyendo los derechos de integridad y atribución. Sin embargo, renuncias a estos derechos y aceptas no ejercerlos contra nosotros para ejercer razonablemente los derechos otorgados en la Sección D.4, pero no de otra manera. +### 7. Moral Rights +You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise. -En la medida en que este acuerdo no sea exigible por la legislación aplicable, concedes a GitHub los derechos que necesitamos para usar Tu Contenido sin atribución y para hacer adaptaciones razonables de Tu Contenido según sea necesario para prestar el Sitio Web y el Servicio. +To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service. -## E. Repositorios privados -**Resumen:** *Tratamos el contenido de los repositorios privados como confidencial y sólo accedemos a este tal y como se describe en nuestra Declaración de Privacidad—con fines de seguridad—para ayudar al propietario del repositorio con un asunto de soporte, para mantener la integridad del servicio, cumplir con nuestras obligaciones legales, si tenemos motivos para creer que el contenido viola la ley o con tu consentimiento.* +## E. Private Repositories +**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.* -### 1. Control de repositorios privados -Algunas cuentas pueden tener repositorios privados, que permiten al Usuario controlar el acceso al Contenido. +### 1. Control of Private Repositories +Some Accounts may have private repositories, which allow the User to control access to Content. -### 2. Control de repositorios privados -GitHub considera que el contenido de los repositorios privados es confidencial para ti. GitHub protegerá el contenido de los repositorios privados del uso no autorizado, el acceso, o divulgación de la misma manera que utilizaríamos para proteger nuestra propia información confidencial de naturaleza similar y, en ningún caso, con un grado de atención más razonable. +### 2. Confidentiality of Private Repositories +GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care. -### 3. Acceso -El personal de GitHub solo puede ingresar al contenido de tus repositorios privados en las situaciones descritas en nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement#repository-contents). +### 3. Access +GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents). -Puedes decidir habilitar acceso adicional a tus repositorios privados. Por ejemplo: -- Puedes habilitar diversos servicios o funciones de GitHub que requieren derechos adicionales sobre Tu Contenido en los repositorios privados. Estos derechos pueden variar dependiendo del servicio o función, pero GitHub continuará tratando su contenido de repositorio privado como confidencial. Si estos servicios o características requieren derechos además de aquellos que necesitamos para proporcionar el servicio de GitHub, le daremos una explicación sobre esos derechos. +You may choose to enable additional access to your private repositories. For example: +- You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights. -Además, podemos estar [obligados por ley](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar el contenido de tus repositorios privados. +Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. -GitHub proporcionará un aviso con respecto a nuestro acceso al contenido del repositorio privado, a excepción de [ divulgación legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumplir con nuestras obligaciones legales o cuando se limite a los requisitos de la ley, para el escaneo automatizado o en respuesta a una amenaza de seguridad u otro riesgo para la seguridad. +GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. -## F. Violación de la propiedad intelectual y la política de DMCA -Si crees que el contenido de nuestro sitio web viola tus derechos de autor, por favor contáctanos de acuerdo con nuestra [Política sobre la Ley de Derechos de Autor Digital del Milenio](/articles/dmca-takedown-policy/). Si eres propietario de derechos de autor y consideras que el contenido en GitHub viola tus derechos, por favor contáctanos a través de [nuestro sencillo formulario DMCA](https://github.com/contact/dmca) o enviando un correo electrónico a copyright@github.com. Puede haber consecuencias legales por enviar un aviso de sumisión falso o poco serio. Antes de enviar una solicitud de sumisión, debes considerar usos legales tales como uso justo y usos autorizados. +## F. Copyright Infringement and DMCA Policy +If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses. -Cancelaremos las Cuentas de [infractores insistentes](/articles/dmca-takedown-policy/#e-repeated-infringement) de esta política. +We will terminate the Accounts of [repeat infringers](/articles/dmca-takedown-policy/#e-repeated-infringement) of this policy. -## G. Notificación de propiedad intelectual -**Versión resumida:** *Somos dueños del servicio y de todo nuestro contenido. Para que puedas utilizar nuestro contenido, te damos ciertos derechos, pero sólo puedes utilizar nuestro contenido de la forma que lo hemos permitido.* +## G. Intellectual Property Notice +**Short version:** *We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.* -### 1. Derechos de GitHub sobre el Contenido -GitHub y nuestros licenciatarios, vendedores, agentes y/o nuestros proveedores de contenidos conservan la propiedad de todos los derechos de propiedad intelectual de cualquier tipo relacionados con el Sitio Web y el Servicio. Nos reservamos todos los derechos que no se le conceden expresamente en virtud de este Acuerdo o por ley. La apariencia del Sitio Web y el Servicio es propiedad intelectual de GitHub, Inc. Todos los derechos reservados. No puedes duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. +### 1. GitHub's Rights to Content +GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from GitHub. -### 2. Nombres comerciales y logos de GitHub -Si deseas usar las marcas registradas de GitHub, debes seguir todas nuestras directrices de marca registrada, incluyendo las que aparecen en nuestra página de logos: https://github.com/logos. +### 2. GitHub Trademarks and Logos +If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos. -### 3. Licencia a políticas de GitHub -La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). +### 3. License to GitHub Policies +This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license). -## H. Términos de la API -**Versión resumida:** *Aceptas estos términos de servicio, además de esta sección H, al usar cualquiera de las API de GitHub (Interfaz del Proveedor de la Aplicación), incluyendo el uso de la API a través de un producto de terceros que ingresa a GitHub.* +## H. API Terms +**Short version:** *You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.* -Las solicitudes abusivas o excesivamente frecuentes a GitHub a través de la API pueden resultar en la suspensión temporal o permanente del acceso de tu Cuenta a la API. GitHub, a nuestra sola discreción, determinará el abuso o el uso excesivo de la API. Intentaremos avisarte por correo electrónico antes de la suspensión. +Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension. -No puedes compartir tokens API para exceder las limitaciones de velocidad de GitHub. +You may not share API tokens to exceed GitHub's rate limitations. -No puedes utilizar la API para descargar datos o Contenido de GitHub con fines de spamming, incluyendo el propósito de vender la información personal de los usuarios de GitHub, tales como reclutadores, cazatalentos y bolsas de trabajo. +You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards. -Todo uso de la API de GitHub está sujeto a estos términos de servicio y a la [Declaración de privacidad de GitHub](https://github.com/site/privacy). +All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy). -GitHub puede ofrecer acceso basado en suscripción a nuestra API para aquellos usuarios que requieren acceso de alto rendimiento o acceso que resultaría en reventa del servicio de GitHub. +GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service. -## I. Términos adicionales de los productos de GitHub -**Versión resumida:** *Debes seguir ciertos términos y condiciones específicos para las diversas características y productos de GitHub y aceptas los Términos y Condiciones Suplementarios cuando estés de acuerdo con este Contrato.* +## I. GitHub Additional Product Terms +**Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.* -Algunas características del servicio pueden estar sujetas a términos adicionales específicos de esa característica o producto según lo establecido en los términos adicionales del producto de GitHub. Al ingresar o utilizar los Servicios, también aceptas los [Términos de adicionales del producto de GitHub](/github/site-policy/github-additional-product-terms). +Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms). -## J. Vista previa Beta -**Versión corta:** *Las vistas previas beta podrían no ser compatibles o cambiar en cualquier momento. Podrías recibir información confidencial a través de estos programas, la cual debe mantenerse confidencial mientras el programa sea privado. Nos encantaría recibir tus comentarios para mejorar nuestras vistas previas beta.* +## J. Beta Previews +**Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.* -### 1. Sujeto a cambio +### 1. Subject to Change -Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Además, las Vistas Previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que se encuentra sujeto el Servicio. **Al hacer uso de una Vista Previa beta, la estás utilizando bajo tu propio riesgo.** +Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview, you use it at your own risk.** -### 2. Confidencialidad +### 2. Confidentiality -Como usuario de las Vistas Previas Beta, puedes tener acceso a información especial que no está disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. +As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret. -**Obligaciones de confidencialidad.** Aceptas que cualquier información no pública de Vista Previa Beta que te proporcionamos, como información sobre una vista previa privada Beta, se considerará información confidencial de GitHub (colectivamente, “Información Confidencial”), independientemente de si está marcada o identificada como tal. Aceptas usar dicha Información Confidencial únicamente para el propósito expreso de probar y evaluar la Vista Previa Beta (el “Propósito”) y para ningún otro propósito. Debes tener el mismo cuidado que con tu propia información confidencial pero no menos de las precauciones razonables para prevenir cualquier uso no autorizado, revelación, publicación o divulgación de nuestra Información Confidencial. Te comprometes a no revelar, publicar o divulgar ninguna Información Confidencial a terceros a menos que no prohibamos o restrinjamos dicha divulgación (por ejemplo, puede ser parte de una discusión de grupo organizada por GitHub acerca de una característica de la Vista Previa Beta). +**Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature). -**Excepciones.** La Información Confidencial no incluirá información que: (a) sea o esté disponible públicamente sin violación de este Contrato a través de ningún acto o inacción por su parte (como cuando una Vista Previa Beta privada se convierte en una Vista Previa Beta pública); (b) conozcas antes de que lo divulguemos; (c) esté desarrollada independientemente por ti sin violación de ninguna obligación de confidencialidad con nosotros o con terceros; o (d) sea revelada con permiso de GitHub. No violarás los términos de este Acuerdo si se te pide revelar Información Confidencial de acuerdo con el funcionamiento de la ley, siempre y cuando GitHub haya recibido un aviso por escrito razonable para objetar, a menos que la ley lo prohíba. +**Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law. -### 3. Comentarios +### 3. Feedback -Siempre estamos tratando de mejorar los productos y servicios y tus comentarios como usuario de las Vistas Previas Beta nos ayudarán a hacerlo. Si decides darnos cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios (colectivamente, "Comentarios"), reconoces y aceptas que GitHub tendrá una licencia sin cargo de regalías completamente pagada, mundial, transferible, irrevocable para implementar, usar, modificar, explotar comercialmente y/o incorporar los Comentarios en nuestros productos, servicios y documentación. +We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation. -## K. Pago -**Versión resumida:** *Eres responsable de cualquier cargo asociado con tu uso de GitHub. Somos responsables de comunicarte esos cobros con claridad y precisión y de hacerte saber con mucha antelación si esos precios cambian.* +## K. Payment +**Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change.* -### 1. Precios -Nuestros precios y términos de pago están disponibles en [github.com/pricing](https://github.com/pricing). Si aceptas un precio de suscripción, ese seguirá siendo tu precio durante la duración del plazo de pago; sin embargo, los precios están sujetos a cambios al final de un plazo de pago. +### 1. Pricing +Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term. -### 2. Mejoras, descensos y cambios -- Te cobraremos inmediatamente cuando pase del plan gratuito a cualquier plan de pago. -- Si cambias de un plan de facturación mensual a un plan de facturación anual, GitHub te cobrará por un año completo en la próxima fecha de facturación mensual. -- Si mejoras a un mayor nivel de servicio, te cobraremos el plan actualizado inmediatamente. -- Puedes cambiar tu nivel de servicio en cualquier momento [eligiendo una opción de plan](https://github.com/pricing) o entrando a tu [configuración de facturación](https://github.com/settings/billing). Si decides bajar la categoría de tu Cuenta, puedes perder el acceso al Contenido, características o capacidad de tu Cuenta. Consulta nuestra sección sobre [Cancelación](#l-cancellation-and-termination) para obtener información sobre cómo obtener una copia de ese contenido. +### 2. Upgrades, Downgrades, and Changes +- We will immediately bill you when you upgrade from the free plan to any paying plan. +- If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date. +- If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately. +- You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on [Cancellation](#l-cancellation-and-termination) for information on getting a copy of that Content. -### 3. Programación de facturación; no reembolsos -**Pago basado en el plan** para planes de pago mensuales o anuales, el Servicio se cobra con antelación de forma mensual o anual respectiva y no es reembolsable. No habrá reembolsos o créditos Para meses parciales de servicio, reembolsos o reembolsos durante meses sin usar con una cuenta abierta; sin embargo, el servicio permanecerá activo durante el período de facturación pagado. Para tratar a todos por igual, no se harán excepciones. +### 3. Billing Schedule; No Refunds +**Payment Based on Plan** For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made. -**Pago basado en el uso** Algunas funciones de servicio se facturan según su uso. Una cantidad limitada de estas características del Servicio puede incluirse en su plan por un período limitado sin cargo adicional. Si decides comprar características de Servicio pagadas más allá de la cantidad incluida en tu plan, pagarás por estas funciones del Servicio con base en tu uso real en el mes anterior. El pago mensual de estas compras se cobrará de forma periódica en mora. Consulte los [Términos adicionales del producto de GitHub para conocer más detalles](/github/site-policy/github-additional-product-terms). +**Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/github/site-policy/github-additional-product-terms). -**Facturación** Para usuarios facturados, el usuario acepta pagar los cobros en su totalidad, por adelantado sin deducción ni saldar cuentas de ningún tipo, en dólares americanos. estadounidenses. El usuario debe pagar las cuotas dentro de treinta (30) días a partir de la fecha de facturación de GitHub. Los importes pagaderos en virtud de este Acuerdo no son reembolsables, excepto que se estipule de otro modo en este Acuerdo. Si el usuario no paga las cuotas a tiempo, GitHub se reserva el derecho, además de tomar cualquier otra acción conforme a derecho o equidad, a (i) cobrar intereses sobre importes vencidos en 1.0% al mes o el tipo de interés más alto permitido por la ley, el que sea menor y a cobrar todos los gastos de recuperación y (ii) cancelar el formulario de pedido aplicable. El usuario es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en relación con el presente Acuerdo. +**Invoicing** For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. -### 4. Autorización -Al aceptar estos términos, nos das permiso para hacer un cargo a tu tarjeta de crédito en el archivo Cuenta de PayPal, u otros métodos de pago aprobados para los cobros que autorizas para GitHub. +### 4. Authorization +By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub. -### 5. Responsabilidad de pago -Eres responsable de todas las cuotas, incluyendo los impuestos, asociados con tu uso del Servicio. Al utilizar el Servicio, aceptas pagar a GitHub cualquier cobro incurrido en relación con tu uso del Servicio. Si impugnas el asunto, ponte en contacto con [el Soporte de GitHub](https://support.github.com/contact?tags=docs-policy). Eres responsable de proporcionarnos un medio de pago válido para las pagar las Cuentas. Las cuentas gratuitas no están obligadas a proporcionar información de pago. +### 5. Responsibility for Payment +You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information. -## L. Cancelación y terminación -**Versión resumida:** *Puedes cerrar tu Cuenta en cualquier momento. Si lo haces, trataremos tu información de forma responsable.* +## L. Cancellation and Termination +**Short version:** *You may close your Account at any time. If you do, we'll treat your information responsibly.* -### 1. Cancelación de la cuenta -Es tu responsabilidad cancelar correctamente tu cuenta con GitHub. Puedes [cancelar tu cuenta en cualquier momento](/articles/how-do-i-cancel-my-account/) entrando a tu Configuración en la barra de navegación global en la parte superior de la pantalla. La pantalla de la Cuenta proporciona un enlace simple y sin preguntas de cancelación. No podemos cancelar Cuentas en respuesta a una solicitud de correo electrónico o teléfono. +### 1. Account Cancellation +It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/articles/how-do-i-cancel-my-account/) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. -### 2. Tras la cancelación -Conservaremos y usaremos tu información cuando sea necesario para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero sin requerimientos legales, borraremos tu perfil completo y el Contenido de tus repositorios dentro de los 90 días posteriores a la cancelación o terminación (aunque es posible que permanezca alguna información en las copias de seguridad cifradas). Esta información no se puede recuperar una vez que su cuenta sea cancelada. +### 2. Upon Cancellation +We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is cancelled. -No eliminaremos el contenido con el que hayas contribuido a los repositorios de otros usuarios o que otros usuarios hayan bifurcado. +We will not delete Content that you have contributed to other Users' repositories or that other Users have forked. -Si se solicita, haremos un esfuerzo razonable para proporcionar al propietario de una cuenta una copia de los contenidos legales, no infringido de la Cuenta después de la cancelación, terminación o descenso de categoría. Debes hacer esta solicitud dentro de los 90 días siguientes a la cancelación, terminación o descenso de categoría. +Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade. -### 3. GitHub pueder rescindir -GitHub tiene derecho a suspender o rescindir tu acceso a todas o a cualquier parte del sitio web en cualquier momento con o sin causa, con o sin previo aviso, efectivo inmediatamente. GitHub se reserva el derecho de denegar el servicio a cualquier persona por cualquier motivo en cualquier momento. +### 3. GitHub May Terminate +GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time. -### 4. Continuidad -Todas las disposiciones de este Acuerdo que, por su naturaleza, deben sobrevivir a la terminación *sobrevivirán* la terminación — incluyendo, sin limitación: Disposiciones de propiedad, exenciones de garantía, indemnización y limitaciones de responsabilidad. +### 4. Survival +All provisions of this Agreement which, by their nature, should survive termination *will* survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability. -## M. Comunicaciones con GitHub -**Versión resumida:** *Utilizamos correo electrónico y otros medios electrónicos para mantenernos en contacto con nuestros usuarios.* +## M. Communications with GitHub +**Short version:** *We use email and other electronic means to stay in touch with our users.* -### 1. Comunicación electrónica requerida -Para propósitos contractuales, (1) otorgarás tu consentimiento para recibir nuestras comunicaciones en forma electrónica a través de la dirección de correo electrónico que ingresaste o a través del Servicio; y (2) aceptarás que todos los Términos de Servicio, acuerdos, avisos, revelaciones, y otras comunicaciones que le proporcionamos electrónicamente satisfacen cualquier requisito legal que dichas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta tus derechos no renunciables. +### 1. Electronic Communication Required +For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights. -### 2. El aviso legal para GitHub debe ser por escrito -Las comunicaciones realizadas a través del correo electrónico o el sistema de mensajería de soporte de GitHub no constituirán un aviso legal a GitHub ni a ninguno de sus oficiales, empleados, agentes o representantes en cualquier situación en la que el aviso a GitHub se requiera por contrato o cualquier ley o reglamento. El aviso legal a GitHub debe ser por escrito y [presentado al agente legal de GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests). +### 2. Legal Notice to GitHub Must Be in Writing +Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests). -### 3. Sin soporte telefónico -GitHub sólo ofrece soporte por correo electrónico, comunicaciones en el servicio y mensajes electrónicos. No ofrecemos soporte telefónico. +### 3. No Phone Support +GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support. -## N. Exención de garantías -**Versión resumida:** *Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. Lee esta sección cuidadosamente; deberías entender qué esperar.* +## N. Disclaimer of Warranties +**Short version:** *We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.* -GitHub proporciona el sitio web y el servicio “tal cual” y “según disponibilidad”, sin garantía de ningún tipo. Sin perjuicio de esto, renunciamos expresamente a todas las garantías, ya sean explícitas, implícitas o reglamentarias, respecto al Servicio Web y el Servicio incluyendo entre otras cualquier garantía implícita de comercialización, idoneidad para un propósito en particular, título, seguridad, precisión y de no incumplimiento. +GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement. -GitHub no garantiza que los Servicios cumplan con tus requisitos; que el Servicio no se interrumpa y sea oportuno, seguro o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. Asumes toda la responsabilidad y el riesgo de pérdida resultante de su descarga y/o uso de archivos, información, contenido u otro material obtenido del Servicio. +GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service. -## O. Limitación de responsabilidad -**Versión resumida:** *No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.* +## O. Limitation of Liability +**Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.* -Comprendes y aceptas que no seremos responsables ante ti o ante ningún tercero por ninguna pérdida de ganancias, uso, buena voluntad, o datos, o para cualquier daño accidental, indirecto, especial, consecuencial o exemplatorio, que surjan sin embargo de +You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from -- el uso, divulgación o visualización de tu contenido generado por el usuario; -- tu uso o incapacidad para usar el Servicio; -- cualquier modificación, cambio de precios, suspensión o interrupción del Servicio; -- el Servicio generalmente o el software o sistemas que hacen el Servicio disponible; -- acceso no autorizado a o alteraciones de tus transmisiones o datos; -- declaración o conducta de cualquier tercero en el Servicio; -- cualquier otra interacción de usuario que introduzca o reciba a través del uso del Servicio; o -- cualquier otro asunto relacionado con el Servicio. +- the use, disclosure, or display of your User-Generated Content; +- your use or inability to use the Service; +- any modification, price change, suspension or discontinuance of the Service; +- the Service generally or the software or systems that make the Service available; +- unauthorized access to or alterations of your transmissions or data; +- statements or conduct of any third party on the Service; +- any other user interactions that you input or receive through your use of the Service; or +- any other matter relating to the Service. -Nuestra responsabilidad es limitada, ya sea que hayamos sido informados o no de la posibilidad de tales daños, e incluso si se descubre que un remedio establecido en este Acuerdo no ha cumplido su propósito esencial. No nos responsabilizaremos por ningún fallo o retraso debido a asuntos que escapen a nuestro control razonable. +Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control. -## P. Liberación e indemnización -**Versión resumida:** *Eres responsable de tu uso del servicio. Si dañas a otra persona o entras en una disputa con otra persona, no estaremos implicados.* +## P. Release and Indemnification +**Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved.* -Si tienes una disputa con uno o más usuarios, aceptas liberar a GitHub de todos y cada uno de los reclamos, demandas y daños (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o de cualquier forma relacionados con tales disputas. +If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes. -Aceptas indemnizarnos, defendernos y liberarnos de toda responsabilidad contra cualquier reclamación, responsabilidad y gastos, incluyendo los honorarios de abogados, derivados del uso del Sitio Web y del Servicio, incluyendo sin limitación a tu violación de este Acuerdo, considerando que GitHub (1) te dé un aviso por escrito de la reclamación, demanda, juicio o procedimiento; (2) te da control exclusivo de la defensa y resolución de reclamaciones, demanda, juicio o diligencia (siempre y cuando no pueda solucionar ninguna reclamación, demanda, juicio o diligencia, a menos que el acuerdo libere incondicionalmente a GitHub de toda responsabilidad); y (3) te proporcione toda la asistencia razonable, a su cargo. +You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense. -## Q. Modificaciones a estos términos -**Versión resumida:** *Desamos que nuestros usuarios estén informados sobre los cambios importantes en nuestros términos, pero algunos cambios no son tan importantes — no queremos molestarte cada vez que arreglamos un error tipográfico. Por ello, si bien es posible que modifiquemos el presente acuerdo en cualquier momento, notificaremos a los usuarios sobre cualquier cambio material y te daremos tiempo para ajustarlos.* +## Q. Changes to These Terms +**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.* -Nos reservamos el derecho, a nuestro exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizaremos este Acuerdo en el caso en que ocurran dichas modificaciones. Notificaremos a nuestros usuarios de los cambios materiales en el presente acuerdo, como aumentos de precios, al menos 30 días antes de que el cambio entre en vigencia al publicar un aviso en nuestro sitio web o al enviar un correo electrónico a la dirección principal de correo electrónico especificada en tu cuenta de GitHub. El uso continuo del Servicio por parte del cliente después de dichos 30 días constituye el acuerdo a las revisiones del presente Acuerdo. Para cualquier otra modificación, tu uso continuo del sitio web constituye un acuerdo con nuestras revisiones de estos términos de servicio. Puedes visualizar todas las modificaciones a estos Términos en nuestro repositorio [Site Policy](https://github.com/github/site-policy)-. +We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. -Nos reservamos el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, temporal o permanentemente, el Sitio Web (o cualquier parte de este) con o sin notificación. +We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice. -## R. Varios +## R. Miscellaneous -### 1. Legislación aplicable -Excepto en la medida en que la ley aplicable establezca lo contrario, este Acuerdo entre tu persona y GitHub y cualquier acceso o uso del Sitio Web o del Servicio se rige por las leyes federales de los Estados Unidos de América y las leyes del Estado de California, sin tener en cuenta el conflicto de disposiciones legales. Tú y GitHub acuerdan someterse a la jurisdicción exclusiva y sede de los tribunales ubicados en la Ciudad y el Condado de San Francisco, California. +### 1. Governing Law +Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California. -### 2. Intransferible -GitHub puede asignar o delegar estos Términos de Servicio y/o la [Declaración de privacidad de GitHub](https://github.com/site/privacy), en su totalidad o en parte, a cualquier persona o entidad en cualquier momento con o sin tu consentimiento, incluyendo la concesión de licencia en la Sección D.4. No puedes asignar ni delegar ningún derecho u obligación bajo los Términos de Servicio o Declaración de Privacidad sin nuestro previo consentimiento por escrito y ninguna asignación no autorizada y delegación por ti es nula. +### 2. Non-Assignability +GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy), in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void. -### 3. Encabezados y resúmenes de sección -A lo largo de este Acuerdo, cada sección incluye títulos y breves resúmenes de los siguientes términos y condiciones. Estos títulos de sección y breves resúmenes no son legalmente vinculantes. +### 3. Section Headings and Summaries +Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding. -### 4. Divisibilidad, sin exención y supervivencia -Si alguna parte de este Acuerdo es considerada inválida o no aplicable, esa parte del Acuerdo será interpretada para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. Cualquier incumplimiento por parte de GitHub para hacer cumplir cualquier disposición de este Acuerdo no será considerado una renuncia a nuestro derecho a hacer cumplir dicha disposición. Nuestros derechos en virtud de este Acuerdo sobrevivirán a cualquier rescisión de este Acuerdo. +### 4. Severability, No Waiver, and Survival +If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement. -### 5. Enmiendas, acuerdo completo -Este Acuerdo sólo puede modificarse por una enmienda por escrito firmada por un representante autorizado de GitHub o por la publicación de GitHub de una versión revisada de acuerdo con la sección [Q. Cambios a estos términos](#q-changes-to-these-terms). Estos Términos de Servicio, junto con la Declaración de Privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tu persona y nosotros. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito, y cualquier otra comunicación entre tu persona y GitHub relacionada con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. +### 5. Amendments; Complete Agreement +This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with [Section Q. Changes to These Terms](#q-changes-to-these-terms). These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements. -### 6. Preguntas -¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://support.github.com/contact?tags=docs-policy). +### 6. Questions +Questions about the Terms of Service? [Contact us](https://support.github.com/contact?tags=docs-policy). diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index f1b441fcdc..5753951e64 100644 --- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -55,7 +55,7 @@ Text that is not a quote ## Quoting code -You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %} +You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %} ```markdown Use `git status` to list all new or modified files that haven't yet been committed. @@ -80,7 +80,7 @@ For more information, see "[Creating and highlighting code blocks](/articles/cre ## Links -You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %} +You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %} `This site was built using [GitHub Pages](https://pages.github.com/).` diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index f7db09b277..2464279e9e 100644 --- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -1,6 +1,6 @@ --- -title: Adjuntar archivos -intro: Puedes transmitir información si adjuntas varios tipos de archivo a tus propuestas y solicitudes de cambio. +title: Attaching files +intro: You can convey information by attaching a variety of file types to your issues and pull requests. redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests - /articles/issue-attachments/ @@ -17,44 +17,44 @@ topics: {% warning %} -**Advertencia:** Si agregas una imagen {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} o video {% endif %} a un comentario de alguna propuesta o solicitud de cambios, cualquiera podrá ver la URL anonimizada sin autenticación, aún si la solicitud de cambios está en un repositorio privado{% ifversion ghes %}, o si se habilita el modo privado{% endif %}. Para mantener privados archivos de medios sensibles, estos se deben servir desde una red o servidor privados que requieran autenticación. {% ifversion fpt or ghec %}Para obtener más información sobre las URL anonimizadas, consulta la sección "[Acerca de las URL anonimizadas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae or ghec %} or video{% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} -Para adjuntar un archivo a una propuesta o una conversación de una solicitud de extracción, arrástralo y suéltalo en el cuadro de comentarios. Como alternativa, puedes dar clic en la barra al final del recuadro de comentarios para buscar, seleccionar y agregar un archivo desde tu ordenador. +To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer. -![Seleccionar adjuntos desde el ordenador](/assets/images/help/pull_requests/select-bar.png) +![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png) {% tip %} -**Tip:** En varios buscadores, puedes copiar y pegar las imágenes directamente en el campo. +**Tip:** In many browsers, you can copy-and-paste images directly into the box. {% endtip %} -El tamaño máximo de archivo es: -- 10MB de imágenes y gifs{% ifversion fpt or ghec %} -- 10MB para videos que se suban a un repositorio que pertenezca a un usuario u organización en un plan gratuito de GitHub -- 100MB para videos que se suban a los repositorios que pertenezcan a un usuario u organización de un plan de pago de GitHub{% elsif fpt or ghes > 3.1 or ghae-next %} -- 100MB para videos{% endif %} -- 25MB para el resto de los archivos +The maximum file size is: +- 10MB for images and gifs{% ifversion fpt or ghec %} +- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan +- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif fpt or ghes > 3.1 or ghae %} +- 100MB for videos{% endif %} +- 25MB for all other files -Archivos compatibles: +We support these files: * PNG (*.png*) * GIF (*.gif*) * JPEG (*.jpg*) -* Archivos de registro (*.log*) -* Documentos de Microsoft Word (*.docx*), Powerpoint (*.pptx*) y Excel (*.xlsx*) -* Archivos de texto (*.txt*) -* PDF (*.pdf*) -* ZIP (*.zip*, *.gz*){% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +* Log files (*.log*) +* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents +* Text files (*.txt*) +* PDFs (*.pdf*) +* ZIP (*.zip*, *.gz*){% ifversion fpt or ghes > 3.1 or ghae or ghec %} * Video (*.mp4*, *.mov*) {% note %} -**Nota:** La compatibilidad con los codecs de video es específica del buscador y es posible que un video que cargues en uno de los buscadores no se pueda ver en otro de ellos. Por el momento, recomendamos utilizar h.264 para una mejor compatibilidad. +**Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility. {% endnote %} {% endif %} -![GIF animados adjuntos](/assets/images/help/pull_requests/dragging_images.gif) +![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif) 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 21b98ef538..c14b543958 100644 --- a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md @@ -1,6 +1,6 @@ --- -title: Administrar cuentas empresariales -intro: Puedes administrar tu cuenta empresarial y las organizaciones que le pertenecen con la API de GraphQL. +title: Managing enterprise accounts +intro: You can manage your enterprise account and the organizations it owns with the GraphQL API. redirect_from: - /v4/guides/managing-enterprise-accounts versions: @@ -9,114 +9,126 @@ versions: ghae: '*' topics: - API -shortTitle: Administrar cuentas empresariales +shortTitle: Manage enterprise accounts --- -## Acerca de administrar cuentas empresariales con GraphQL +## About managing enterprise accounts with GraphQL -Para ayudarte a monitorear y hacer cambios en tu organización y mantener el cumplimiento, puedes utilizar la API de Cuentas Empresariales y la API de Bitácoras de Auditoría, las cuales se encuentran disponibles únicamente como API de GraphQL. +To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs. -Las terminales de cuenta empresarial funcionan tanto para GitHub Enterprise Cloud y GitHub Enterprise Server. +The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server. -GraphQL te permite solicitar y recuperar únicamente los datos que especificas. Por ejemplo, puedes crear una consulta de GraphQL, o hacer una solicitud de información, para ver todos los nuevos miembros que se agregaron a tu organización. O puedes hacer una mutación, o cambio, para invitar a un administrador a tu cuenta empresarial. +GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account. -Con la API de Bitácoras de Auditoria, puedes monitorear cuando alguien: -- Accede a tu configuración de organización o de repositorio. -- Cambia los permisos. -- Agrega o elimina usuarios en una organización, repositorio, o equipo. -- Promueve algún usuario a administrador. -- Cambia los permisos de GitHub App. +With the Audit Log API, you can monitor when someone: +- Accesses your organization or repository settings. +- Changes permissions. +- Adds or removes users in an organization, repository, or team. +- Promotes users to admin. +- Changes permissions of a GitHub App. -La API de Bitácoras de Auditoría te permite mantener las copias de tus datos de bitácoras de auditoria. Para las consultas realizadas con la API de Bitácoras de Auditoria, la respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. Para encontrar una lista de los campos disponibles con la API de Bitácoras de Auditoria, consulta la "[interface AuditEntry](/graphql/reference/interfaces#auditentry/)". +The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)." -Con la API de Cuentas Empresariales puedes: -- Listar y revisar todas las organizaciones y repositorios que pertenecen a tu cuenta empresarial. -- Cambiar la configuración de la cuenta empresarial. -- Configurar políticas para la configuración en tu cuenta empresarial y sus organizaciones. -- Invitar administradores a tu cuenta empresarial. -- Crear nuevas organizaciones en tu cuenta empresarial. +With the Enterprise Accounts API, you can: +- List and review all of the organizations and repositories that belong to your enterprise account. +- Change Enterprise account settings. +- Configure policies for settings on your enterprise account and its organizations. +- Invite administrators to your enterprise account. +- Create new organizations in your enterprise account. -Para encontrar una lista de los campos disponibles con la API de Cuentas Empresariales, consulta "[Campos y tipos de GraphQL para la API de cuenta empresarial](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)". +For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)." -## Comenzar a utilizar GraphQL para cuentas empresariales +## Getting started using GraphQL for enterprise accounts -Sigue estos pasos para comenzar a utilizar GraphQL para administrar tus cuentas empresariales: - - Autenticarte con un token de acceso personal - - Elegir un cliente de GraphQL o utilizar el Explorador de GraphQL - - Configurar Insomnia para utilizar la API de GraphQL +Follow these steps to get started using GraphQL to manage your enterprise accounts: + - Authenticating with a personal access token + - Choosing a GraphQL client or using the GraphQL Explorer + - Setting up Insomnia to use the GraphQL API -Para encontrar algunas consultas de ejemplo, visita la sección "[Una consulta de ejemplo utilizando la API de Cuentas Empresariales](#an-example-query-using-the-enterprise-accounts-api)". +For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)." -### 1. Autenticarte con tu token de acceso personal +### 1. Authenticate with your personal access token -1. Para autenticarte con GraphQL, necesitas generar un token de acceso personal (PAT) desde la configuración de desarrollador. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +1. To authenticate with GraphQL, you need to generate a personal access token (PAT) from developer settings. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -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: +2. Grant admin and full control permissions to your personal access token for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your personal access token: - `repo` - `admin:org` - - `usuario` + - `user` - `admin:enterprise` - Los alcances específicos para la cuenta empresarial son: - - `admin:enterprise`: Proporciona control total de las empresas (incluye a {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` y `read:enterprise`) - - `manage_billing:enterprise`: Lee y escribe datos de facturación empresarial.{% ifversion ghes > 3.2 or ghae %} - - `manage_runners:enterprise`: Acceso para administrar los ejecutores y grupos de ejecutores empresariales de GitHub Actions.{% endif %} - - `read:enterprise`: Lee datos del perfil empresarial. + The enterprise account specific scopes are: + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} + - `read:enterprise`: Read enterprise profile data. -3. Copia tu token de acceso personal y mantenlo en un lugar seguro hasta que lo agregues a tu cliente de GraphQL. +3. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client. -### 2. Elige un cliente de GraphQL +### 2. Choose a GraphQL client -Te recomendamos utilizar GraphiQL u otro cliente independiente de GraphQL que te permita configurar la URL base. +We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL. -También podrás considerar utilizar estos clientes de GraphQL: +You may also consider using these GraphQL clients: - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries) - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/) -Los siguientes pasos utilizarán Insomnia. +The next steps will use Insomnia. -### 3. Configurar Insomnia para utilizar la API de GraphQL de GitHub con cuentas empresariales +### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts -1. Agrega la url base y el método `POST` a tu cliente de GraphQL. Cuando utilices GraphQL para solicitar información (consultas), cambiar información (mutaciones), o transferir datos utilizando la API de GitHub, el método HTTP predeterminado es `POST` y la url base sigue esta sintaxis: - - Para tu instancia empresarial: `https:///api/graphql` - - Para GitHub Enterprise Cloud: `https://api.github.com/graphql` +1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax: + - For your enterprise instance: `https:///api/graphql` + - For GitHub Enterprise Cloud: `https://api.github.com/graphql` -2. Para autenticarte, abre el menú de opciones de autenticación y selecciona **Token titular**. A continuación, agrega tu token de acceso personal, el cual habías copiado. +2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your personal access token that you copied earlier. - ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) + ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) - ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-bearer-token-option.png) + ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-bearer-token-option.png) -3. Incluye la información del encabezado. - - Agrega `Content-Type` como el encabezado y `application/json` como el valor. ![Encabezado estándar](/assets/images/developer/graphql/json-content-type-header.png) ![Encabezado con valor de vista previa para la API de Bitácoras de Auditoría](/assets/images/developer/graphql/preview-header-for-2.18.png) +3. Include header information. + - Add `Content-Type` as the header and `application/json` as the value. + ![Standard header](/assets/images/developer/graphql/json-content-type-header.png) + ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png) -Ahora estás listo para comenzar a hacer consultas. +Now you are ready to start making queries. -## Un ejemplo de consulta utilizando la API de Cuentas Empresariales +## An example query using the Enterprise Accounts API -Esta consulta de GraphQL solicita la cantidad total de {% ifversion not ghae %} repositorios `public`{% else %} repositorios`private`{% endif %} en cada una de las organizaciones de tu aplicativo que utilizan la API de cuentas empresariales. Para personalizar esta consulta, reemplaza `` con el slug de tu instancia empresarial. +This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `` with `octo-enterprise`. {% ifversion not ghae %} ```graphql -query publicRepositoriesByOrganization { - organizationOneAlias: organization(login: "") { - # How to use a fragment - ...repositories +query publicRepositoriesByOrganization($slug: String!) { + enterprise(slug: $slug) { + ...enterpriseFragment } - organizationTwoAlias: organization(login: "") { - ...repositories - } - # organizationThreeAlias ... and so on up-to lets say 100 } -# How to define a fragment -fragment repositories on Organization { - name - repositories(privacy: PUBLIC){ - totalCount + +fragment enterpriseFragment on Enterprise { + ... on Enterprise{ + name + organizations(first: 100){ + nodes{ + name + ... on Organization{ + name + repositories(privacy: PUBLIC){ + totalCount + } + } + } + } } } + +# Passing our Enterprise Account as a variable +variables { + "slug": "" +} ``` {% else %} @@ -152,7 +164,7 @@ variables { ``` {% endif %} -El siguiente ejemplo de consulta de GraphQL muestra lo retador que es el recuperar la cantidad de repositorios {% ifversion not ghae %}`public`{% else %}`private`{% endif %} en cada organización sin utilizar la API de Cuenta Empresarial. Nota que la API de Cuentas Empresariales de GraphQL ha hecho esta tarea más simple para las empresas, ya que solo necesitas personalizar una sola variable. Para personalizar esta consulta, reemplaza `` y ``, etc. con los nombres de organización en tu instancia. +The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API. Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `` and ``, etc. with the organization names on your instance. {% ifversion not ghae %} ```graphql @@ -200,7 +212,7 @@ fragment repositories on Organization { ``` {% endif %} -## Consulta a cada organización por separado +## Query each organization separately {% ifversion not ghae %} @@ -248,7 +260,7 @@ fragment repositories on Organization { {% endif %} -Esta consulta de GraphQL solicita las últimas 5 entradas de bitácora para una organización empresarial. Para personalizar este query, reemplaza `` y ``. +This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `` and ``. ```graphql { @@ -274,12 +286,13 @@ Esta consulta de GraphQL solicita las últimas 5 entradas de bitácora para una } ``` -Para obtener más información acerca de cómo comenzar con GraphQL, consulta las secciónes "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)" y "[Formar Llamados con GraphQL](/graphql/guides/forming-calls-with-graphql)". +For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." -## Campos y tipos de GraphQL para la API de Cuentas Empresariales +## GraphQL fields and types for the Enterprise Accounts API -Aquí tienes un resumen de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales. +Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API. -Para obtener más detalles acerca de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales, observa la barra lateral con las definiciones detalladas de GraphQL desde cualquier [página de referencia de GraphQL](/graphql). +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -Puedes acceder a los documentos de referencia desde dentro del explorador de GraphQL en GitHub. Para obtener más información, consulta la sección "[Utilizar el explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)". Para obtener otro tipo de información, tal como los detalles de autenticación y el límite de tasas, revisa las [guías](/graphql/guides). +You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)." +For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). diff --git a/translations/es-ES/content/graphql/index.md b/translations/es-ES/content/graphql/index.md index e1b26e37df..61e400a8c7 100644 --- a/translations/es-ES/content/graphql/index.md +++ b/translations/es-ES/content/graphql/index.md @@ -1,7 +1,26 @@ --- -title: API de GraphQL de GitHub -intro: 'Puedes utilizar la API de GraphQL de {% data variables.product.prodname_dotcom %} para crear consultas precisas y flexibles para los datos que necesitas integrar con {% data variables.product.prodname_dotcom %}.' -shortTitle: API de GraphQL +title: GitHub GraphQL API +intro: 'To create integrations, retrieve data, and automate your workflows, use the {% data variables.product.prodname_dotcom %} GraphQL API. The {% data variables.product.prodname_dotcom %} GraphQL API offers more precise and flexible queries than the {% data variables.product.prodname_dotcom %} REST API.' +shortTitle: GraphQL API +introLinks: + overview: /graphql/overview/about-the-graphql-api +featuredLinks: + guides: + - /graphql/guides/forming-calls-with-graphql + - /graphql/guides/introduction-to-graphql + - /graphql/guides/using-the-explorer + popular: + - /graphql/overview/explorer + - /graphql/overview/public-schema + - /graphql/overview/schema-previews + - /graphql/guides/using-the-graphql-api-for-discussions + guideCards: + - /graphql/guides/migrating-from-rest-to-graphql + - /graphql/guides/managing-enterprise-accounts + - /graphql/guides/using-global-node-ids +changelog: + label: 'api, apis' +layout: product-landing redirect_from: - /v4 versions: diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index 40398276a0..6f847a5927 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -170,7 +170,7 @@ With issue and pull request search terms, you can: - Filter issues and pull requests by label: `state:open type:issue label:"bug"` - Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` -{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} {% tip %} **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND. diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md index bb538e6131..4fc8425724 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -83,12 +83,4 @@ For more information about how to create an allow list for a {% data variables.p ## Using {% data variables.product.prodname_actions %} with an IP allow list -{% ifversion ghae %} - -{% data reusables.github-actions.ip-allow-list-hosted-runners %} - -{% else %} - {% data reusables.github-actions.ip-allow-list-self-hosted-runners %} - -{% endif %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index 0d23b4dbc8..f222e7b6c4 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -77,7 +77,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% ifversion fpt or ghec %} | [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} | [`team`](#team-category-actions) | Contains all activities related to teams in your organization. -| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} | [`workflows`](#workflows-category-actions) | Contains activities related to {% data variables.product.prodname_actions %} workflows.{% endif %} You can search for specific sets of actions using these terms. For example: @@ -307,6 +307,20 @@ An overview of some of the most common actions that are recorded as events in th | `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." {% endif %} +{% ifversion ghae %} +### `external_group` category actions + +{% data reusables.saml.external-group-audit-events %} + +{% endif %} + +{% ifversion ghae %} +### `external_identity` category actions + +{% data reusables.saml.external-identity-audit-events %} + +{% endif %} + {% ifversion fpt or ghec %} ### `git` category actions @@ -402,7 +416,7 @@ For more information, see "[Managing the publication of {% data variables.produc | Action | Description |------------------|------------------- -| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae or ghec %} | `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %} | `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. @@ -434,7 +448,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." -| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %} | `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} | `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} @@ -546,7 +560,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### `pull_request` category actions @@ -587,7 +601,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae or ghec %} | `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." | `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".{% endif %} | `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %} @@ -605,7 +619,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." | `remove_topic` | Triggered when a repository admin removes a topic from a repository. -| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae or ghec %} | `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} | `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} @@ -744,7 +758,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." | `enable` | Triggered when an organization owner enables team discussions for an organization. -{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghec or ghes > 3.1 or ghae %} ### `workflows` category actions {% data reusables.actions.actions-audit-events-workflow %} @@ -752,4 +766,4 @@ For more information, see "[Managing the publication of {% data variables.produc ## Further reading - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %} -- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %} \ No newline at end of file +- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %} diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 22b6b0342e..87dda915f4 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -121,7 +121,7 @@ Some of the features listed below are limited to organizations using {% data var | Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | | Change a repository's settings | | | | | **X** | | Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %} | Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | | Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** |{% endif %} | Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %} @@ -165,7 +165,7 @@ In this section, you can find the access required for security features, such as | [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} | [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} [1] Repository writers and maintainers can only see alert information for their own commits. {% endif %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index 4b2252d181..753c2e3f39 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -87,7 +87,7 @@ You can configure this behavior for an organization using the procedure below. M {% data reusables.github-actions.private-repository-forks-configure %} {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Setting the permissions of the `GITHUB_TOKEN` for your organization {% data reusables.github-actions.workflow-permissions-intro %} diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 5e52b05048..03a6516b82 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -87,9 +87,9 @@ You can only choose an additional permission if it's not already included in the ### Security -- **Read {% data variables.product.prodname_code_scanning %} results**: Provide users with read permissions for {% data variables.product.prodname_code_scanning %} alerts. -- **Write {% data variables.product.prodname_code_scanning %} results**: Provide users with write permissions for {% data variables.product.prodname_code_scanning %} alerts. -- **Delete {% data variables.product.prodname_code_scanning %} results**: Provide users with delete permissions for {% data variables.product.prodname_code_scanning %} alerts. +- **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts. +- **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts. +- **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts. ## Precedence for different levels of access diff --git a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index aded45e897..f33c0fa3a5 100644 --- a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -16,7 +16,6 @@ shortTitle: Publish & install with Actions {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} ## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} @@ -33,7 +32,7 @@ You can extend the CI and CD capabilities of your repository by publishing or in ### Authenticating to package registries on {% data variables.product.prodname_dotcom %} -{% ifversion fpt or ghec %}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_location %}, 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. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." +{% ifversion fpt or ghec %}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_location %}, 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/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)." @@ -139,7 +138,7 @@ jobs: build-and-push-image: runs-on: ubuntu-latest - needs: run-npm-test {% ifversion ghes > 3.1 or ghae-next %} + needs: run-npm-test {% ifversion ghes > 3.1 or ghae %} permissions: contents: read packages: write {% endif %} @@ -289,7 +288,7 @@ build-and-push-image: {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% raw %} @@ -533,7 +532,7 @@ jobs: # Push image to GitHub Packages. # See also https://docs.docker.com/docker-hub/builds/ push: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: packages: write contents: read{% endif %} diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md index 2118fbff99..7896aa0be5 100644 --- a/translations/es-ES/content/packages/quickstart.md +++ b/translations/es-ES/content/packages/quickstart.md @@ -1,37 +1,36 @@ --- -title: Guía de inciio rápido para GitHub Packages -intro: 'Publica en el {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %}.' +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.' allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -shortTitle: Inicio Rápido +shortTitle: Quickstart --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## Introducción +## Introduction -En esta guía, crearás un flujo de trabajo de {% data variables.product.prodname_actions %} para probar tu código y luego lo publicarás en el {% 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 %}. -## Publicar tu paquete +## Publishing your package -1. Crea un repositorio nuevo en {% data variables.product.prodname_dotcom %}, agregando el `.gitignore` para Node. {% ifversion ghes < 3.1 %} Crea un repositorio privado si te gustaría borrar este paquete más adelante, los paquetes públicos no pueden borrarse.{% endif %} Para obtener más información, consulta la sección "[Crear un repositorio nuevo ](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". -2. Clona el repositorio en tu máquina local. +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. {% ifversion ghes < 3.1 %} Create a private repository if you’d like to delete this package later, public packages cannot be deleted.{% endif %} For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. ```shell $ git clone https://{% ifversion ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git $ cd YOUR-REPOSITORY ``` -3. Crea un archivo `index.js` y agrega una alerta básica que diga "Hello world!" +3. Create an `index.js` file and add a basic alert to say "Hello world!" {% raw %} ```javascript{:copy} alert("Hello, World!"); ``` {% endraw %} -4. Inicializa un paquete de npm con `npm init`. En el asistente de inicialización de paquetes, ingresa tu paquete con el nombre: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, y configura el script de pruebas en `exit 0`. Esto generará un archivo `package.json` con información sobre tu paquete. +4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package. {% raw %} ```shell $ npm init @@ -42,15 +41,15 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam ... ``` {% endraw %} -5. Ejecuta `npm install` para generar el archivo `package-lock.json` y luego confirma y sube tus cambios a {% data variables.product.prodname_dotcom %}. +5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}. ```shell $ npm install $ git add index.js package.json package-lock.json $ git commit -m "initialize npm package" $ git push ``` -6. Crea un directorio de `.github/workflows`. En este directorio, crea un archivo que se llame `release-package.yml`. -7. Copia el siguiente contenido de YAML en el archivo `release-package.yml`{% ifversion ghae %}, reemplazando a `YOUR-HOSTNAME` con el nombre de tu empresa{% endif %}. +6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`. +7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}. ```yaml{:copy} name: Node.js Package @@ -71,7 +70,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam publish-gpr: needs: build - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: packages: write contents: read{% endif %} @@ -86,14 +85,14 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam env: NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %} ``` -8. Dile a NPM en qué alcance y registro publicar paquetes para utilizar uno de los siguientes métodos: - - Agrega un archivo de configuración NPM para el repositorio creando un archivo `.npmrc` en el directorio raíz con el siguiente contenido: +8. Tell NPM which scope and registry to publish packages to using one of the following methods: + - Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents: {% raw %} ```shell @YOUR-USERNAME:registry=https://npm.pkg.github.com ``` {% endraw %} - - Edita el archivo `package.json` y especifica la clave `publishConfig`: + - Edit the `package.json` file and specify the `publishConfig` key: {% raw %} ```shell "publishConfig": { @@ -101,7 +100,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam } ``` {% endraw %} -9. Confirma y sube tus cambios a {% data variables.product.prodname_dotcom %}. +9. Commit and push your changes to {% data variables.product.prodname_dotcom %}. ```shell $ git add .github/workflows/release-package.yml # Also add the file you created or edited in the previous step. @@ -109,29 +108,29 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam $ git commit -m "workflow to publish package" $ git push ``` -10. El flujo de trabajo que creaste se ejecutará cuando sea que se cree un lanzamiento nuevo en tu repositorio. Si las pruebas pasan, entonces el paquete se publicará en {% data variables.product.prodname_registry %}. +10. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. + + To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." - Para probar esto, navega a la pestaña de **Código** en tu repositorio y crea un lanzamiento nuevo. Para obtener más información, consulta la sección "[Gestionar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)". +## Viewing your published package -## Visualizar tu paquete publicado - -Puedes ver todos los paquetes que has publicado. +You can view all of the packages you have published. {% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %} -## Instalar un paquete publicado +## Installing a published package -Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. Para obtener más información, consulta la sección "[Trabajar con el registro de npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)". +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)." -## Pasos siguientes +## Next steps -El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. Pero esto es solo el inicio de lo que puedes hacer con el {% data variables.product.prodname_registry %}. Puedes publicar tu paquete en varios registros con un solo flujo de trabajo, activar el flujo de trabajo para que se ejecute en eventos diferentes tales como una solicitud de cambios fusionada, administrar contenedores, y más. +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. -El combinar el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu proceso de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí hay algunos recursos útiles para llevar a cabo los siguientes pasos con el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %}: +Combining {% data variables.product.prodname_registry %} and {% 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_registry %} and {% data variables.product.prodname_actions %}: -- "[Aprende sobre el {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para un tutorial más a fondo de GitHub Packages -- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para un tutorial más a fondo de GitHub Actions -- "[Trabajar con un registro de {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" para casos de uso y ejemplos específicos +- "[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 +- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md index 0a76534207..36d4f570c7 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md @@ -13,14 +13,13 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request - /github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request - shortTitle: Merge PR automatically --- ## 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)."{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} +Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %} After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index a9effb3ad9..6dc332b6d9 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -72,7 +72,7 @@ Only the user who created the pull request can give you permission to push commi {% tip %} - **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)." + **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)." {% endtip %} 8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like. diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 8a89ae3bb8..8babad4362 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -30,7 +30,7 @@ You can review changes in a pull request one file at a time. While reviewing the {% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-next %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} You can change the format of the diff view in this tab by clicking {% octicon "gear" aria-label="The Settings gear" %} and choosing the unified or split view. The choice you make will apply when you view the diff for other pull requests. diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index 8d9cfd5548..586100d514 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -15,7 +15,7 @@ topics: - Pull requests --- -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Syncing a fork from the web UI diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md index 371252c242..1b863c2771 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -17,7 +17,7 @@ shortTitle: Manage auto merge --- ## About auto-merge -If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% ifversion fpt or ghae-next or ghes > 3.1 or ghec %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." ## Managing auto-merge diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md index 9d1c5e6711..6f1a34c11c 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md @@ -16,8 +16,32 @@ shortTitle: Use merge queue ## About pull request merge queue {% data reusables.pull_requests.merge-queue-overview %} -{% data reusables.pull_requests.merge-queue-reject %} +The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`. + +For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`. + +``` +on: + push: + branches: + - gh/readonly/queue/main/** +``` + +{% data reusables.pull_requests.merge-queue-merging-method %} + +For information about merge methods, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." For information about the "Require linear history" branch protection setting, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)." + +{% note %} + +**Note:** During the beta, there are some limitations when using the merge queue: + +* The merge queue cannot be enabled on branch protection rules using wildcards (`*`) in the name. +* There is no support for squash merge commits. (Only merge commits and "rebase and merge" commits are supported.) + +{% endnote %} + +{% data reusables.pull_requests.merge-queue-reject %} ## Managing pull request merge queue Repository administrators can configure merge queues for pull requests targeting selected branches of a repository. The requirement to use a merge queue is a branch protection setting called "Require merge queue" that can be enabled in branch protection rules. diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index c4be3a9f2a..2d760fe6f2 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -42,7 +42,7 @@ By default, the restrictions of a branch protection rule don't apply to people w For each branch protection rule, you can choose to enable or disable the following settings. - [Require pull request reviews before merging](#require-pull-request-reviews-before-merging) - [Require status checks before merging](#require-status-checks-before-merging) -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} - [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %} - [Require signed commits](#require-signed-commits) - [Require linear history](#require-linear-history) @@ -99,7 +99,7 @@ You can set up required status checks to either be "loose" or "strict." The type For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Require conversation resolution before merging Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge. @@ -138,6 +138,8 @@ Before you can require a linear commit history, your repository must allow squas {% data reusables.pull_requests.merge-queue-beta %} {% data reusables.pull_requests.merge-queue-overview %} + +{% data reusables.pull_requests.merge-queue-merging-method %} {% data reusables.pull_requests.merge-queue-references %} {% endif %} diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 1ac3ee3211..fe9eb1dd68 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -80,7 +80,7 @@ When you create a branch rule, the branch you specify doesn't have to exist yet ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png) - Search for status checks, selecting the checks you want to require. ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png) -{%- ifversion fpt or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghes > 3.1 or ghae %} 1. Optionally, select **Require conversation resolution before merging**. ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png) {%- endif %} diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index b6d8c53a63..d82c43712f 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -1,6 +1,6 @@ --- -title: Cambiar la rama predeterminada -intro: 'Si tienes màs de una rama en tu repositorio, puedes configurar cualquiera de ellas como la predeterminada.' +title: Changing the default branch +intro: 'If you have more than one branch in your repository, you can configure any branch as the default branch.' permissions: People with admin permissions to a repository can change the default branch for the repository. versions: fpt: '*' @@ -14,40 +14,43 @@ redirect_from: - /github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch topics: - Repositories -shortTitle: Cambia la rama predeterminada +shortTitle: Change the default branch --- +## About changing the default branch -## Acerca de cambiar la rama predeterminada - -Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base para las solicitudes de cambios y confirmaciones de còdigo. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". +You can choose the default branch for a repository. The default branch is the base branch for pull requests and code commits. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." {% ifversion not ghae %} {% note %} -**Nota**: Si utilizas el puente de Git-Subversion, el cambiar la rama predeterminada afectarà al contenido de tu rama `trunk` y al `HEAD` que ves cuando listas las referencias para el repositorio remoto. Para obtener màs informaciòn, consulta la secciòn "[Soporte para los clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)" y a [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) en la documentaciòn de Git. +**Note**: If you use the Git-Subversion bridge, changing the default branch will affect your `trunk` branch contents and the `HEAD` you see when you list references for the remote repository. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)" and [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) in the Git documentation. {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -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)". +You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." {% endif %} {% data reusables.branches.set-default-branch %} -## Prerrequisitos +## Prerequisites -Para cambiar la rama predeterminada, tu repositorio debe tener màs de una rama. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)". +To change the default branch, your repository must have more than one branch. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)." -## Cambiar la rama predeterminada +## Changing the default branch {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} -1. Debajo de "Rama predeterminada", a la derecha del nombre de rama predeterminado, da clic en el {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Cambiar el icono con dos flechas hacia la derecha del nombre de la rama predeterminada actual](/assets/images/help/repository/repository-options-defaultbranch-change.png) -1. Utiliza el menù desplegable y luego da clic en el nombre de una rama. ![Menù desplegable para elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png) -1. Da clic en **Actualizar**. ![Botòn de "Update" despuès de elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-update.png) -1. Lee la advertencia y luego da clic en **Entiendo, actualizar la rama predeterminada.** ![Botón de "Entiendo, actualizar la rama predeterminada." para realizar la actualización](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) +1. Under "Default branch", to the right of the default branch name, click {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. + ![Switch icon with two arrows to the right of current default branch name](/assets/images/help/repository/repository-options-defaultbranch-change.png) +1. Use the drop-down, then click a branch name. + ![Drop-down to choose new default branch](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png) +1. Click **Update**. + !["Update" button after choosing a new default branch](/assets/images/help/repository/repository-options-defaultbranch-update.png) +1. Read the warning, then click **I understand, update the default branch.** + !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index e5683513b9..820352f6af 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,7 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' - ghae: next + ghae: '*' ghec: '*' topics: - Repositories diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index 970ef6ff72..a6ad2effcd 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -40,7 +40,7 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu ![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png) -{% ifversion fpt or ghae-next or ghes > 3.1 or ghec %} +{% ifversion fpt or ghae or ghes > 3.1 or ghec %} ## Auto-generated table of contents for README files diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index cb0ef50a07..90bd18f498 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -90,7 +90,7 @@ You can configure this behavior for a repository using the procedure below. Modi {% data reusables.repositories.settings-sidebar-actions %} {% data reusables.github-actions.private-repository-forks-configure %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Setting the permissions of the `GITHUB_TOKEN` for your repository {% data reusables.github-actions.workflow-permissions-intro %} diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md index 7e4246ba15..d0f6114565 100644 --- a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md +++ b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md @@ -15,16 +15,34 @@ topics: ## About navigating code on {% data variables.product.prodname_dotcom %} -Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). The following languages are supported: -- C# -- CodeQL -- Go -- Java -- JavaScript -- PHP -- Python -- Ruby -- TypeScript +Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition. + +![Code navigation display](/assets/images/help/repository/code-navigation-popover.png) + +Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported: + +| Language | search-based code navigation | precise code navigation | +|:----------:|:----------------------------:|:-----------------------:| +| C# | ✅ | | +| CodeQL | ✅ | | +| Go | ✅ | | +| Java | ✅ | | +| JavaScript | ✅ | | +| PHP | ✅ | | +| Python | ✅ | ✅ | +| Ruby | ✅ | | +| TypeScript | ✅ | | + + +You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both. + +{% data variables.product.prodname_dotcom %} has developed two code navigation approaches based on the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) and [`stack-graphs`](https://github.com/github/stack-graphs) library: + - search-based - searches all definitions and references across a repository to find entities with a given name + - precise - resolves definitions and references based on the set of classes, functions, and imported definitions at a given point in your code + +To learn more about these approaches, see "[Precise and search-based navigation](#precise-and-search-based-navigation)." + +Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results. ## Jumping to the definition of a function or method @@ -38,11 +56,21 @@ You can find all references for a function or method within the same repository ![Find all references tab](/assets/images/help/repository/find-all-references-tab.png) +## Precise and search-based navigation + +Certain languages supported by {% data variables.product.prodname_dotcom %} have access to *precise code navigation*, which uses an algorithm (based on the open source [`stack-graphs`](https://github.com/github/stack-graphs) library) that resolves definitions and references based on the set of classes, functions, and imported definitions that are visible at any given point in your code. Other languages use *search-based code navigation*, which searches all definitions and references across a repository to find entities with a given name. Both strategies are effective at finding results and both make sure to avoid inappropriate results such as comments, but precise code navigation can give more accurate results, especially when a repository contains multiple methods or functions with the same name. + +If you don't see the results you expect from a precise code navigation query, you can click on the "search-based" link in the displayed popover to perform search-based navigation. + +![Search-based code navigation link](/assets/images/help/repository/search-based-code-navigation-link.png) + +If your precise results appear inaccurate, you can file a support request. + ## Troubleshooting code navigation If code navigation is enabled for you but you don't see links to the definitions of functions and methods: - Code navigation only works for active branches. Push to the branch and try again. -- Code navigation only works for repositories with less than 100,000 files. +- Code navigation only works for repositories with fewer than 100,000 files. ## Further reading - "[Searching code](/github/searching-for-information-on-github/searching-code)" diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md index 74ab5b1968..86d5220126 100644 --- a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md @@ -230,7 +230,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap In the same way, we can [view repositories for the authenticated user][user repos api]: ```shell -$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ +$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -274,7 +274,7 @@ Fetching information for existing repositories is a common use case, but the we need to `POST` some JSON containing the details and configuration options. ```shell -$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ +$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -320,7 +320,7 @@ Just like github.com, the API provides a few methods to view issues for the authenticated user. To [see all your issues][get issues api], call `GET /issues`: ```shell -$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ +$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -328,7 +328,7 @@ To get only the [issues under one of your {% data variables.product.product_name /orgs//issues`: ```shell -$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ +$ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -370,7 +370,7 @@ body to the `/issues` path underneath the repository in which we want to create the issue: ```shell -$ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ +$ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/es-ES/content/rest/guides/traversing-with-pagination.md b/translations/es-ES/content/rest/guides/traversing-with-pagination.md index bbf5c4c404..91595eb798 100644 --- a/translations/es-ES/content/rest/guides/traversing-with-pagination.md +++ b/translations/es-ES/content/rest/guides/traversing-with-pagination.md @@ -16,7 +16,7 @@ shortTitle: Traverse with pagination The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. Most of the time, you might even find that you're asking for _too much_ information, -and in order to keep our servers happy, the API will automatically [paginate the requested items][pagination]. +and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination). In this guide, we'll make some calls to the Search API, and iterate over the results using pagination. You can find the complete source code for this project diff --git a/translations/es-ES/content/rest/index.md b/translations/es-ES/content/rest/index.md index 22b8cc2c19..789e0c3023 100644 --- a/translations/es-ES/content/rest/index.md +++ b/translations/es-ES/content/rest/index.md @@ -1,7 +1,27 @@ --- -title: API de REST de GitHub -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.' +title: GitHub REST API +shortTitle: REST API +intro: 'To create integrations, retrieve data, and automate your workflows, build with the {% data variables.product.prodname_dotcom %} REST API.' +introLinks: + quickstart: /rest/guides/getting-started-with-the-rest-api +featuredLinks: + guides: + - /rest/guides/getting-started-with-the-rest-api + - /rest/guides/basics-of-authentication + - /rest/guides/best-practices-for-integrators + popular: + - /rest/overview/resources-in-the-rest-api + - /rest/overview/other-authentication-methods + - /rest/overview/troubleshooting + - /rest/overview/endpoints-available-for-github-apps + - /rest/overview/openapi-description + guideCards: + - /rest/guides/delivering-deployments + - /rest/guides/getting-started-with-the-checks-api + - /rest/guides/traversing-with-pagination +changelog: + label: 'api, apis' +layout: product-landing redirect_from: - /v3 versions: diff --git a/translations/es-ES/content/rest/reference/actions.md b/translations/es-ES/content/rest/reference/actions.md index d18e1d43d1..f00f66a23b 100644 --- a/translations/es-ES/content/rest/reference/actions.md +++ b/translations/es-ES/content/rest/reference/actions.md @@ -13,7 +13,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)." @@ -34,7 +33,7 @@ The Artifacts API allows you to download, delete, and retrieve information about {% ifversion fpt or ghes > 2.22 or ghae or ghec %} ## Permissions -The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)." +The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %} You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md index d8512c1e8d..fbe657c8eb 100644 --- a/translations/es-ES/content/rest/reference/enterprise-admin.md +++ b/translations/es-ES/content/rest/reference/enterprise-admin.md @@ -34,6 +34,10 @@ REST API endpoints{% ifversion ghes %}—except [Management Console](#management {% data variables.product.api_url_pre %} ``` +{% ifversion fpt or ghec %} +When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`. +{% endif %} + {% ifversion ghes %} [Management Console](#management-console) API endpoints are only prefixed with a hostname: @@ -85,7 +89,6 @@ You can also read the current version by calling the [meta endpoint](/rest/refer ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/packages.md b/translations/es-ES/content/rest/reference/packages.md index 9c4a6e924b..72b91cab3b 100644 --- a/translations/es-ES/content/rest/reference/packages.md +++ b/translations/es-ES/content/rest/reference/packages.md @@ -1,6 +1,6 @@ --- -title: Paquetes -intro: 'Con la API del {% data variables.product.prodname_registry %}, puedes administrar paquetes para tus repositorios y organizaciones de {% data variables.product.prodname_dotcom %}.' +title: Packages +intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.' product: '{% data reusables.gated-features.packages %}' versions: fpt: '*' @@ -10,16 +10,16 @@ topics: miniTocMaxHeadingLevel: 3 --- -La API de {% data variables.product.prodname_registry %} te permite administrar paquetes utilizando la API de REST. Para aprender más sobre cómo restablecer o borrar paquetes, consulta la sección "[Restablecer y borrar paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package)". +The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)." -Para utilizar esta API, primero tienes que autenticarte utilizando un token de acceso personal. - - Para acceder a los metadatos del paquete, tu token debe incluir el alcance `read:packages`. - - Para borrar los paquetes y las versiones de paquetes, tu token debe incluir los alcances `read:packages` y `delete:packages`. - - Para restablecer los paquetes y sus versiones, tu token debe incluir los alcances de `read:packages` y `write:packages`. +To use this API, you must authenticate using a personal access token. + - To access package metadata, your token must include the `read:packages` scope. + - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes. + - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes. -Si tu `package_type` es `npm`, `maven`, `rubygems`, o `nuget`, entonces tu token también debe incluir el alcance `repo`, ya que este hereda los permisos de un repositorio de {% data variables.product.prodname_dotcom %}. Si tu paquete está en el {% data variables.product.prodname_container_registry %}, entonces tu `package_type` es `container` y tu token no necesita el alcance de `repo` para acceder o administrar este `package_type`. Los paquetes de `container` ofrecen permisos granulares separados de un repositorio. Para obtener más información, consulta la sección "[Acerca de los permisos para el {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)". +If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." -Si quieres utilizar la API del {% data variables.product.prodname_registry %} para acceder a los recursos de una organización con el SSO habilitado, entonces debes habilitar el SSO para tu token de acceso personal. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizar con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)". +If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md index ca85509c37..b740a1207d 100644 --- a/translations/es-ES/content/rest/reference/repos.md +++ b/translations/es-ES/content/rest/reference/repos.md @@ -170,7 +170,7 @@ You can communicate that a transient environment no longer exists by setting its {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %} {% endfor %} -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Environments The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." diff --git a/translations/es-ES/content/rest/reference/secret-scanning.md b/translations/es-ES/content/rest/reference/secret-scanning.md index d3fd555101..2cb0e7cdf5 100644 --- a/translations/es-ES/content/rest/reference/secret-scanning.md +++ b/translations/es-ES/content/rest/reference/secret-scanning.md @@ -11,7 +11,7 @@ miniTocMaxHeadingLevel: 3 {% data reusables.secret-scanning.api-beta %} -The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}: +The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}: - Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. - Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below. diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md index cc87ced91a..f6f7e88e11 100644 --- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -61,18 +61,18 @@ The {% data variables.search.advanced_url %} provides a visual interface for con ![Advanced Search](/assets/images/help/search/advanced_search_demo.gif) -{% ifversion fpt or ghes or ghae-next or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment -If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. +If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. {% ifversion fpt or ghes or ghec %} -- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} -- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation -{% endif %} -{% ifversion ghes or ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation + +{% ifversion ghes or ghae %} To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md index 1ad80e1954..cf410536e1 100644 --- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -1,7 +1,7 @@ --- -title: Habilitar la búsqueda en repositorios de GitHub.com desde tu ambiente empresarial privado -shortTitle: Buscar en GitHub.com desde una empresa -intro: 'Puedes conectar tus cuentas personales de {% data variables.product.prodname_dotcom_the_website %} y tu ambiente privado de {% data variables.product.prodname_enterprise %} para buscar contenido en repositorios específicos de {% data variables.product.prodname_dotcom_the_website %}{% ifversion fpt or ghec %} desde tu ambiente privado{% else %} desde {% data variables.product.product_name %}{% endif %}.' +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' redirect_from: - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ @@ -12,42 +12,41 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: next + ghae: '*' ghec: '*' topics: - GitHub search --- -## Acerca de cómo buscar repositorios de {% data variables.product.prodname_dotcom_the_website %} desde {% ifversion fpt or ghec %}tu ambiente empresarial privado{% else %}{% data variables.product.product_name %}{% endif %} +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt or ghec %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} -Puedes buscar repositorios privados designados en {% data variables.product.prodname_ghe_cloud %} desde {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_location %}{% ifversion ghae %} en {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}Por ejemplo, si utilizas {% data variables.product.prodname_ghe_server %}, puedes buscar repositorios privados desde tu empresa en {% data variables.product.prodname_ghe_cloud %} en la interfaz web de {% data variables.product.prodname_ghe_server %}.{% endif %} +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} -## Prerrequisitos +## Prerequisites -- Un propietario de empresa de {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} debe habilitar {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %}. Para obtener más información, consulta lo siguiente.{% ifversion fpt or ghes or ghec %} - - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} - - "[Habilitar {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_managed %} documentation +- An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %} {% endif %} -- Ya debes tener acceso a los repositorios privados y conectar tu cuenta {% ifversion fpt or ghec %}en tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %} en {% data variables.product.product_name %}{% endif %} con tu cuenta en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre los repositorios en los que puedes buscar, consulta la sección "[Acerca de cómo buscar en GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)". +- You must already have access to the private repositories and connect your account {% ifversion fpt or ghec %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." -## Habilitar la búsqueda de repositorios de GitHub.com desde {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} +## Enabling GitHub.com repository search from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} {% ifversion fpt or ghec %} -Para obtener más información, consulta lo siguiente. +For more information, see the following. -| Tue ambiente empresarial | Más información | -|:--------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% data variables.product.prodname_ghe_server %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} -| -| {% data variables.product.prodname_ghe_managed %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" -{% endif %} +| Your enterprise environment | More information | +| :- | :- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" | +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" | {% elsif ghes or ghae %} -1. Inicia sesión en {% data variables.product.product_name %} y en {% data variables.product.prodname_dotcom_the_website %}. -1. En {% data variables.product.product_name %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. +![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %} {% data reusables.github-connect.connect-dotcom-and-enterprise %} diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 53bb4c70c6..87b2785ed3 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -155,7 +155,7 @@ You can narrow your results by labels, using the `label` qualifier. Since issues | ------------- | ------------- | label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." -| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next or ghec %} +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} ## Search by milestone diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml index 852e08b17e..5b8ada1c94 100644 --- a/translations/es-ES/data/glossaries/external.yml +++ b/translations/es-ES/data/glossaries/external.yml @@ -177,13 +177,13 @@ - term: rama predeterminada description: >- - The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch. + La rama base para todas las solicitudes de cambio y confirmaciones de código en un repositorio. Cada repositorio tiene por lo menos una rama, la cual crea Git cuando lo inicializas. La rama principal a menudo se llama {% ifversion ghes < 3.2 %} 'master'{% else %}'main'{% endif %}, y habitualmente es la rama predeterminada. - - term: dependents graph + term: gráfica de dependientes description: >- Un gráfico del repositorio que muestra los paquetes, los proyectos y los repositorios que dependen de un repositorio público. - - term: dependency graph + term: gráfica de dependencias description: >- Un gráfico del repositorio que muestra los paquetes y los proyectos de los que depende el respositorio. - @@ -248,7 +248,7 @@ - term: gist description: >- - A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}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 {% ifversion ghae %}interno{% else %}público{% endif %} o secreto, aunque los gists secretos estarán disponibles para {% ifversion ghae %}cualquier miembro de la empresa{% else %}cualquiera{% endif %} que tenga la URL. - term: Git description: >- @@ -373,7 +373,7 @@ 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,7 +392,7 @@ 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 creará una rama denominada 'master'. Hoy en día, muchas herramientas utilizan un nombre alterno para la rama predeterminada.{% ifversion fpt or ghes > 3.1 or ghae %} Por ejemplo, cuando creas un repositorio nuevo en GitHub, la rama predeterminada se llama 'main'.{% endif %} - - term: members graph + term: gráfica de miembros description: Un gráfico del repositorio que muestra todas las bifurcaciones de un repositorio. - term: mención @@ -418,7 +418,7 @@ description: >- Un equipo hijo de un equipo padre. Puedes tener varios equipos hijo (o anidados). - - term: network graph + term: gráfica 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. - @@ -539,10 +539,10 @@ 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áfica 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áfica 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. - diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml new file mode 100644 index 0000000000..b2e5ff7237 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml @@ -0,0 +1,20 @@ +date: '2021-12-07' +sections: + security_fixes: + - 'Support bundles could include sensitive files if they met a specific set of conditions.' + bugs: + - 'Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.' + - 'A misconfiguration in the Management Console caused scheduling errors.' + - 'Docker would hold log files open after a log rotation.' + - 'GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments.' + changes: + - 'Clarifies explanation of Actions path-style in documentation.' + - 'Updates support contact URLs to use the current support site, support.github.com.' + known_issues: + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml index 6f3bbb15f3..8ad038ea19 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml @@ -25,7 +25,7 @@ sections: - "Puedes personalizar los tipos de notificaciones que quieres recibir de repositorios individuales. Para obtener más información, consulta la sección \"[Configurar las notificaciones](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)\".\n" - heading: 'Filtrado de GitHub Mobile' notes: - - "El filtrado con [{% data variables.product.prodname_mobile %}](https://github.com/mobile) te permite buscar y encontrar propuestas, solicitudes de cambio y debates desde tu dispositivo. Los metadatos nuevos para los elementos de lista de las propuestas y solicitudes de cambio te permiten filtrar por asignados, estado de verificación, estados de revisión y conteo de comentarios.\n\n{% data variables.product.prodname_mobile %} beta está disponible para {% data variables.product.prodname_ghe_server %}. Inicia sesión con nuestras apps para [Android](https://play.google.com/store/apps/details?id=com.github.android) y [iOS](https://apps.apple.com/app/github/id1477376905) para clasificar las notificaciones y administrar las propuestas y solicitudes de cambio al momento. Los administradores pueden inhabilitar la compatibilidad móvil para sus empresas utilizando la consola de administración o ejecutando `ghe-config app.mobile.enabled false`. Para obtener más información, consulta la sección \"[GitHub para dispositivos móviles](/github/getting-started-with-github/using-github/github-for-mobile).\"\n" + - "El filtrado con [{% data variables.product.prodname_mobile %}](https://github.com/mobile) te permite buscar y encontrar propuestas, solicitudes de cambio y debates desde tu dispositivo. Los metadatos nuevos para los elementos de lista de las propuestas y solicitudes de cambio te permiten filtrar por asignados, estado de verificación, estados de revisión y conteo de comentarios.\n\n{% data variables.product.prodname_mobile %} beta está disponible para {% data variables.product.prodname_ghe_server %}. Inicia sesión con nuestras apps para [Android](https://play.google.com/store/apps/details?id=com.github.android) y [iOS](https://apps.apple.com/app/github/id1477376905) para clasificar las notificaciones y administrar las propuestas y solicitudes de cambio al momento. Los administradores pueden inhabilitar la compatibilidad móvil para sus empresas utilizando la consola de administración o ejecutando `ghe-config app.mobile.enabled false`. Para obtener más información, consulta la sección \"[GitHub móvil](/github/getting-started-with-github/using-github/github-mobile)\".\n" changes: - heading: 'Cambios en la administración' notes: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml new file mode 100644 index 0000000000..cec6929d55 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml @@ -0,0 +1,21 @@ +date: '2021-12-07' +sections: + security_fixes: + - 'Support bundles could include sensitive files if they met a specific set of conditions.' + bugs: + - 'Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.' + - 'A misconfiguration in the Management Console caused scheduling errors.' + - 'Docker would hold log files open after a log rotation.' + - 'GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments.' + changes: + - 'Clarifies explanation of Actions path-style in documentation.' + - 'Updates support contact URLs to use the current support site, support.github.com.' + known_issues: + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml index 747617a9bb..62d2d7a5ae 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,127 +1,309 @@ date: '2021-09-09' release_candidate: true deprecated: true -intro: 'Si {% data variables.product.product_location %} está ejecutando una compilación candidata a lanzamiento, no puedes mejorarla con un hotpatch. Te recomendamos que solo ejecutes candidatos a lanzamiento en ambientes de prueba.' +intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. sections: features: - - heading: 'Patrones personalizados para el escaneo de secretos' + - heading: Custom patterns for secret scanning notes: - - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden especificar los patrones para el escaneo de secretos. Cuando se especifica un patrón nuevo, el escaneo de secretos busca dicho patrón en todo el historial de Git del repositorio, así como cualquier confirmación nueva.\n\nLos patrones definidos por los usuarios se encuentran en beta para {% data variables.product.prodname_ghe_server %} 3.2. Se pueden definir a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección \"[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)\".\n" - - heading: 'Resumen de seguridad para la Seguridad Avanzada (beta)' + # https://github.com/github/releases/issues/1426 + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + + - heading: Security overview for Advanced Security (beta) notes: - - "Los clientes de la {% data variables.product.prodname_GH_advanced_security %} ahora tienen una vista de nivel de organización apra los riegos de seguridad de las aplicaciones que detecte el {% data variables.product.prodname_code_scanning %}, el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_secret_scanning %}. El resumen de seguridad muestra la habilitación de estado de las características de seguridad en cada repositorio, así como la cantidad de alertas que se detectan.\n\nAdicionalmente, el resumen de seguridad lista todas las alertas del {% data variables.product.prodname_secret_scanning %} a nivel organizacional. Tendremos vistas similares para el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_code_scanning %} en los lanzamientos futuros cercanos. Para obtener más información, consulta la sección \"[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)\".\n\n![Captura de pantalla del resumen de seguridad](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png)\n" - - heading: 'Revisión de dependencias (beta)' + # https://github.com/github/releases/issues/1381 + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + + - heading: Dependency review (beta) notes: - - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden ver un diff enriquecido de las dependencias que cambiaron en una solicitud de cambios. La revisión de dependencias proporciona una vista fácil de entender de los cambios a las dependencias y de su impacto de seguridad en la pestaña de \"Archivos que cambiaron\" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron junto con la información de vulnerabilidades de estas dependencias. Para obtener más información, consulta la sección \"[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)\".\n" - - heading: 'Ambientes de GitHub Actions' + # https://github.com/github/releases/issues/1364 + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information for these dependencies. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + + - heading: GitHub Actions environments notes: - - "Los ambientes, las reglas de protección de ambiente y los secretos de ambiente ahora están disponibles en general para las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}. Para obtener más información, consulta la sección \"[Environments](/actions/reference/environments)\".\n" - - heading: 'Autenticación por SSH con llaves seguras' + # https://github.com/github/releases/issues/1308 + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + + - heading: SSH authentication with security keys notes: - - "Ahora es compatible la autenticación por SSH utilizando una llave de seguridad FIDO2 cuando agregas una llave SSH de tipo `sk-ecdsa-sha2-nistp256@openssh.com` o `sk-ssh-ed25519@openssh.com` a tu cuenta. Las llaves de seguridad SSH almacenan material de llaves secretas en un dispositivo de hardware por separado, el cual requiere de verificación, tal como un tap, para operar. Para obtener más información, consulta la sección \"[Generar una clave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)\".\n" - - heading: 'Temas oscuro y oscuro atenuado' + # https://github.com/github/releases/issues/1276 + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + + - heading: 'Dark and dark dimmed themes' notes: - - "Ahora hay temas oscuro y opaco oscuro disponibles para la IU web. {% data variables.product.product_name %} empatará las preferencias de tu sistema si no has configurado las preferencias de tema en {% data variables.product.product_name %}. También puedes elegir qué temas estarán activos durante el día y la noche. Para obtener más información, consulta la sección \"[Administrar la configuración de tu tema](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n\n![Temas oscuro y opaco oscuro](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif)\n" - - heading: 'Aprobar dominios no verificados para las notificaciones de correo electrónico' + # https://github.com/github/releases/issues/1260 + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + + - heading: 'Approving unverified domains for email notifications' notes: - - 'Los dominios que no se pueden verificar ahora pueden aprobarse para el enrutamiento de notificaciones por correo electrónico. Los propietarios de empresas y organizaciones podrán aprobar dominios y aumentar su política de restricción de notificaciones por correo electrónico automáticamente, lo cual permitirá que las notificaciones se envíen a los colaboradores, consultores, adquisiciones o a otros socios. para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" y "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' - - heading: 'Soporte para el almacenamiento de credenciales seguro del Administrador de Credenciales de Git (GCM) y autenticación multifactorial' + # https://github.com/github/releases/issues/1244 + - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." + + - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' notes: - - "Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}.\n\nGCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository.\n" + # https://github.com/github/releases/issues/1406 + - | + Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. + changes: - - heading: 'Cambios en la administración' + - heading: Administration Changes notes: - - 'Se agregó un ajuste de "Política de Referente de Agente Usuario" a la configuración empresarial. Esto permite que un administrador configure una "Política de referente" más estricta para ocultar el nombre de host de una instalación de {% data variables.product.prodname_ghe_server %} de sitios externos. Este ajuste se encuentra inhabilitado predeterminadamente y los eventos de bitácoras de auditoría lo rastrean para los propietarios empresariales y el personal de las empresas cuando se habilita o inhabilita. Para obtener más información, consulta la sección "[Configurar la Política de Referente en tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".' - - 'La revisión de salud de MySQL se cambió al uso de `mysqladmin ping` en vez de las verificaciones de TCP, lo cual elimina algo del ruido innecesario en la bitácora de errores de MySQL, las verificaciones de recuperación de fallos del orquestador se mejoraron para prevenir las recuperaciones de fallos de MySQL innecesarias al aplicar cambios de configuración del clúster.' - - 'El servicio Resque, el cual da la compatibilidad con procesamiento de jobs en segundo plano, se reemplazó con Aqueduct Lite. este cambio hace que el sistema de jobs se pueda administrar más fácilmente y no debería afectar la experiencia del usuario. Para la administración y comandos de depuración nuevas de Aqueduct, consulta la sección "[Utilidades de la línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)".' - - heading: 'Cambios de Token' + # https://github.com/github/releases/issues/1309 + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + + # https://github.com/github/releases/issues/1515 + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + + # https://github.com/github/releases/issues/1287 + - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." + + - heading: Token Changes notes: - - "El formato de tokens de autenticación para {% data variables.product.product_name %} ha cambiado,. Dicho cambio afecta el formato de los tokens de acceso personal y de los tokens de acceso para las {% data variables.product.prodname_oauth_apps %}, así como de los tokens de usuario a servidor, de servidor a servidor y de actualización para {% data variables.product.prodname_github_apps %}.\n\nLos diferentes tipos de token ahora tienen prefijos identificables únicos, los cuales permiten que el escaneo de secretos detecten los tokens para que puedas mitigar el impacto de que alguien confirme un token accidentalmente en un repositorio. {% data variables.product.company_short %} recomienda actualizar los tokens existentes tan pronto como te sea posible. Para obtener más información, consulta las secciones \"[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)\" y \"[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)\".\n" - - heading: 'Cambios de repositorios' + # https://github.com/github/releases/issues/1235 + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + + - heading: 'Repositories changes' notes: - - 'Los repositorios en los perfiles de usuario y en los perfiles de organización ahora son compatibles con la clasificación por conteo de estrellas.' - - 'Cuando veas el historial de confirmación de un archivo único, ahora puedes hacer clic en {% octicon "file-code" aria-label="The code icon" %} para ver dicho archivo en algún punto selecto del historial.' - - 'Cuando un submódulo se define con una ruta relativa en {% data variables.product.product_location %}, el submódulo ahora se puede hacer clic en la interfaz web. Al hacer clic en el submódulo de la interfaz web le llevará al repositorio enlazado. Anteriormente, sólo los submódulos con URLs absolutas podían hacer clic. Esto es soportado para rutas relativas para los repositorios con el mismo propietario que siguen el patrón ..REPOSITORY o rutas relativas de repositorios con un propietario diferente que siga el patrón ../OWNER/REPOSITORY. Para obtener más información sobre cómo trabajar con submódulos, consulta la sección [Trabajar con submódulos](https://github.blog/2016-02-01-working-with-submodules/) en {% data variables.product.prodname_blog %}.' - - 'La IU web ahora puede utilizarse para sincronizar una rama desactualizada de una bifurcación con la rama ascendente de dicha bifurcación. Si no hay conflictos de fusión entre las ramas, la rama se actualizará ya sea mediante un envío rápido o mediante la fusión desde la parte ascendente. Si hay conflictos, se te pedirá crear una solicitud de cambios para resolverlos. Para obtener más información, consulta la sección "[Sincronizar una bifurcación](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)".' - - heading: 'Cambios en el Lenguaje de Marcado' + # https://github.com/github/releases/issues/1295 + - Repositories on user profiles and organization profiles now support sorting by star count. + + # https://github.com/github/releases/issues/1327 + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + + # https://github.com/github/releases/issues/1254 + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + + # https://github.com/github/releases/issues/1250 + - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." + + - heading: 'Markdown changes' notes: - - 'El editor de lenguaje de marcado que se utiliza al crear o editar un lanzamiento en un repositorio ahora tiene una barra de herramientas para edición de texto. Para obtener más información, consulta la sección "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)".' - - '{% data variables.product.product_name %} ahora tiene compatibilidad para cargar archivos de video en donde sea que utilices lenguaje de marcado. Comparte demostraciones, pasos de reproducción y más en los comentarios de tus propuestas y solicitudes de cambio, así como en los archivos de lenguaje de marcado dentro de los repositorios, tales como los README. Para obtener más información, consulta la sección "[Adjuntar archivos](/github/writing-on-github/working-with-advanced-formatting/attaching-files)".' - - 'Los archivos de lenguaje de marcado ahora generarán una tabla de contenido automáticamente en el encabezado cuando haya 2 o más encabezados. La tabla de contenido es interactiva y enlaza a la sección seleccionada. Los 6 niveles de encabezado del lenguaje de marcado son compatibles.' - - 'Hay un atajo de teclado nuevo, `cmd+e` en macOS o `ctrl+e` en Windows, para insertar bloques de código en los archivos, propuestas, solicitudes de cambio y comentarios de Lenguaje de Marcado.' - - 'El agregar `?plain=1` a la URL en cualquier archivo de lenguaje de marcado ahora mostrará al archivo sin procesar y con números de línea. La vista simple puede utilizarse para enlazar a otros usuarios a líneas específicas. Por ejemplo, el agregar `?plain=1#L52` resaltará la línea 52 del archivo de marcado en texto simple. Para obtener más información, consulta la sección "[Crear un enlace permanente a un fragmento de código](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)".' - - heading: 'Cambios en propuestas y sollicitudes de cambio' + # https://github.com/github/releases/issues/1477 + - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + + # https://github.com/github/releases/issues/1169 + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + + # https://github.com/github/releases/issues/1269 + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + + # https://github.com/github/releases/issues/1294 + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + + # https://github.com/github/releases/issues/1474 + - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)." + + - heading: 'Issues and pull requests changes' notes: - - 'Con la [versión más reciente de Octicons](https://github.com/primer/octicons/releases), los estados de las propuestas y solicitudes de cambios ahora son más fáciles de distinguir visualmente para que puedas escanear los estados de forma más sencilla. Para obtener más información consulta la sección [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).' - - 'Ahora tenemos disponible una regla de protección de rama de "Requerir la resolución de la conversación antes de fusionar" y un menú de "Conversaciones". Descubre fácilmente tus comentarios de solicitudes de cambios desde la pestaña de "Archivos que cambiaron" y requiere qeu todas tus conversaciones en solicitudes de cambio se resuelvan antes de fusionarse. Para obtener más información, consulta las secciones "[Acerca de las revisiones de solicitudes de cambio](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)".' - - 'Para prevenir la fusión de cambios inesperados después de habilitar la fusión automática para una solicitud de cambios, ahora se inhabilitó esta opción automáticamente cuando un usuario sin acceso de escritura al repositorio sube estos cambios. Los usuarios que no tengan permisos de escritura aún pueden actualizar la solicitud de cambios con aquellos de la rama base cuando se habilita la fusión automática. Para prevenir que un usuario malintencionado utilice un conflicto de fusión para introducir cambios inesperados a la solicitud de cambios, la fusión automática para la solicitud de cambios se encuentra inhabilitada si dicha actualización causa un conflicto de fusión. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".' - - 'Las personas con permisos de mantenimiento ahora pueden administrar el ajuste de "Permitir la fusión automática" a nivel de repositorio. Este ajuste, el cual a menudo se encuentra inhabilitado, controla si la fusión automática está disponible para las solicitudes de cambios en el repositorio., Anteriormente, solo las personas con permisos administrativos podían administrar este ajuste. Adicionalmente, este ajuste ahora puede controlarse utilizando las API de REST para "[Crear repositorio](/rest/reference/repos#create-an-organization-repository)" y "[Actualizar repositorio](/rest/reference/repos#update-a-repository)". Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio]](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)".' - - 'La selección de propuestas y solicitudes de cambio de los asignados ahora es compatible con la búsqueda de escritura anticipada, así que puedes encontrar usuarios en tu organización más rápidamente. Adicionalmente, las clasificaciones de resultados de búsqueda se actualizaron para preferir las coincidencias al inicio del nombre de usuario de una persona o nombre de perfil.' - - 'Cuando se solicita una revisión de un equipo de más de 100 personas, los desarrolladores ahora muestran una caja de diálogo de confirmación para poder prevenir las notificaciones innecesarias para los equipos grandes.' - - 'Ahora hay compatibilidad con tener `code blocks` con comilla inversa en los títulos de las propuestas y en cualquier lugar en el que se referencien propuestas y solicitudes de cambios en {% data variables.product.prodname_ghe_server %}.' - - 'Los eventos para las solicitudes de cambios y revisiones de solicitudes de cambios ahora se incluyen en la bitácora de auditoría tanto para [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) como para [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). estos eventos ayudan a que los administradores monitoreen mejor la actividad de las solicitudes de cambios y ayuden a garantizar que se cumplan los requisitos de seguridad y cumplimiento. Los eventos pueden verse desde la IU web, exportarse como CSV o JSON o acceder a ellos a través de la API de REST. También puedes buscar la bitácora de auditoría para los eventos de solicitudes de cambio específicos. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)".' - - heading: 'Cambios a las ramas' + # https://github.com/github/releases/issues/1413 + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + + # https://github.com/github/releases/issues/1419 + - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." + + # https://github.com/github/releases/issues/1279 + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + + # https://github.com/github/releases/issues/1550 + - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)." + + # https://github.com/github/releases/issues/1201 + - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name. + + # https://github.com/github/releases/issues/1430 + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + + # https://github.com/github/releases/issues/1293 + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + + # https://github.com/github/releases/issues/1300 + - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)." + + - heading: 'Branches changes' notes: - - "El nombre de rama predeterminado para los repositorios nuevos ahora es `main`. Los repositorios existentes no se verán impactados por este cambio. Si los usuarios, propietarios de organizaciones o propietarios de empresas ya especificaron una rama predeterminada para repositorios nuevos anteriormente, tampoco se les impactará.\n\nSi quieres configurar un nombre de rama predeterminada diferente, puedes hacerlo en los ajustes de [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), o [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).\n" - - "Las ramas, incluyendo a la predeterminada, ahora pueden volver a nombrarse utilizando la IU web de {% data variables.product.product_name %}. Cuando una rama se vuelve a nombrar, cualquier solicitud de cambios abierta y lanzamiento de borrador que apunten a la rama que se volvió a nombrar se redirigirá automáticamente y las reglas de protección de rama que referencien explícitamente a la rama que se volvió a nombrar se actualizarán.\n\nSe requieren permisos administrativos para volver a nombrar la rama predeterminada, pero es suficiente contar con permisos de escritura para volver a nombrar otras ramas.\n\nPara ayudar a hacer el cambio con tanta continuidad como sea posible para los usuarios:\n\n* Se muestra un aviso a los contribuyentes, mantenedores y administradores de la página de inicio del repositorio, el cual contiene instrucciones para actualizar su repositorio local.\n*Las solicitudes web para la rama antigua se redireccionarán.\n* Se devolverá una respuesta HTTP de \"se movió permanentemente\" a todo llamado de la API de REST.\n* Se mostrará un mensaje informativo para los usuarios de la línea de comandos de Git que suban información a la rama antigua.\n\nPara obtener más información, consulta la sección \"[Volver a nombrar una rama](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)\".\n" - - heading: 'Cambioas a las GitHub Actions' + # https://github.com/github/releases/issues/885 + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + + # https://github.com/github/releases/issues/981 + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + + - heading: 'GitHub Actions changes' notes: - - 'Las {% data variables.product.prodname_actions %} ahora te permiten controlar los permisos que se otorgan al secreto del `GITHUB_TOKEN`. El `GITHUB_TOKEN` es un secreto que se genera automáticamente y te permite hacer llamados autenticados a la API de {% data variables.product.product_name %} en tus ejecuciones de flujo de trabajo. Las {% data variables.product.prodname_actions %} generan un token nuevo para cada job y hacen que el token venza cuando se completa el job. El token a menudo tiene permisos de `escritura` para varias [Terminales de la API](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), con excepción de los casos de las solicitudes de cambios de las bifurcaciones, los cuales siempre se marcan como de `lectura`. Estos ajustes nuevos te permiten seguir el principio de los menores privilegios necesarios en tus flujos de trabajo,. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".' - - 'El {% data variables.product.prodname_cli %} 1.9 y posterior te permiten trabajar con las {% data variables.product.prodname_actions %} en tu terminal. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' - - 'La bitácora de auditoría ahora incluye eventos asociados con las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}. Estos datos proporcionan un conjunto de datos ampliamente expandidos para los administradores, así como auditorías de cumplimiento. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)".' - - 'Se hicieron mejoras de rendimiento a {% data variables.product.prodname_actions %}, lo cual podría dar como resultado una capacidad de procesamiento de jobs máxima más alta. Para obtener más información sobre la capacidad de procesamiento de los jobs con configuraciones de CPU y memoria probadas internamente, consulta la sección "[Iniciar con {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".' - - heading: 'Cambios a los GitHub packages' + # https://github.com/github/releases/issues/1227 + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + + # https://github.com/github/releases/issues/1280 + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + + # https://github.com/github/releases/issues/1157 + - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)." + + # https://github.com/github/releases/issues/1587 + - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job throughput. For more information on job throughput with internally-tested CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." + + - heading: 'GitHub Packages changes' notes: - - 'Cualquier paquete o versión de paquete del {% data variables.product.prodname_registry %} ahora se puede borrar de la IU web de {% data variables.product.product_name %}. También puedes deshacer el borrado de cualquier paquete o versión de paquete dentro de los primeros 30 días. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".' - - heading: 'Cambios al Dependabot y a la gráfica de Dependencias' + # https://github.com/github/releases/issues/1088 + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + + - heading: 'Dependabot and Dependency graph changes' notes: - - 'La gráfica de dependencias ahora puede habilitarse utilizando la Consola de Administración en vez de necesitar la ejecución de un comando en el shell administrativo. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".' - - 'Ahora, las notificaciones para {% data variables.product.prodname_dependabot_alerts %} múltiples se agrupan si se descubren al mismo tiempo. Esto reduce significativamente el volumen de notificaciones de alertas del {% data variables.product.prodname_dependabot %} que reciben los usuarios. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).' - - 'Las gráficas de dependencias y {% data variables.product.prodname_dependabot_alerts %} ahora son compatibles con los módulos de Go. {% data variables.product.prodname_ghe_server %} analiza los archivos de `go.mod` de un repositorio para entender las dependencias del mismo. En conjunto con las asesorías de seguridad, la gráfica de dependencias proporciona la información necesaria para alertar a los desarrolladores sobre las dependencias vulnerables. Para obtener más información sobre cómo habilitar la gráfica de dependencias en los repositorios privados, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)".' - - 'Los ajustes de notificación predeterminados para las alertas de seguridad han cambiado. Anteriormente, si tenías permiso para ver las alertas de seguridad en un repositorio, hubieras recibido las notificaciones de dicho repositorio mientras tu configuración permitiera las notificaciones de alertas de seguridad. Ahora debes decidir unirte a las notificaciones de alertas de seguridad observando el repositorio. Se te notificará si seleccionas `Toda la actividad` o si configuras `Personalizado` para incluir las `Alertas de seguridad`. Todos los repositorios existentes se migrarán automáticamente a estos ajustes nuevos y seguirás recibiendo notificaciones; sin embargo, cualquier repositorio nuevo requerirá que decidas unirte observando el repositorio. Para obtener más información, consulta las secciones "[Configurar notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" y "[Administrar las alertas del escaneo de secretos](/code-security/secret-security/managing-alerts-from-secret-scanning)".' - - heading: 'Cambios al escaneo de código y de secretos' + # https://github.com/github/releases/issues/1537 + - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." + + # https://github.com/github/releases/issues/1153 + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + + # https://github.com/github/releases/issues/1371 + - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)." + + # https://github.com/github/releases/issues/1538 + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + + - heading: 'Code scanning and secret scanning changes' notes: - - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql %} ahora genera información diagnóstica para todos los lenguajes compatibles. Esto ayuda a mantener el estado de la base de datos creada para entender el estado y calidad del análisis que se realizó. La información diagnóstica se encuentra disponible desde la [versión 2.5.6](https://github.com/github/codeql-cli-binaries/releases) del {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). Puedes ver esta información diagnóstica detallada en las bitácoras para {% data variables.product.prodname_codeql %} de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras de escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".' - - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql_cli %} ahora es compatible con el análisis de diversos lenguajes durante una compilación sencilla. Esto facilita el ejecutar análisis de código para utilizar sistemas de IC/DC diferentes a los de las {% data variables.product.prodname_actions %}. El modo nuevo del comando `codeql database create` se encuentra disponible desde la [versión 2.5.6] (https://github.com/github/codeql-cli-binaries/releases) del [{% data variables.product.prodname_codeql_cli %}] (https://codeql.github.com/docs/codeql-cli/). Para obtener más información sobre cómo configurar esto, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)".' - - 'Las alertas de {% data variables.product.prodname_code_scanning_capc %} de todas las herramientas habilitadas ahora se muestran en una lista consolidada para que puedas priorizar fácilmente entre todas ellas. Puedes ver las alertas desde una herramienta específica utilizando le filtro de "Herramienta" y los de "Regla" y "Etiqueta" se actualizarán dinámicamente con base en tu selección de "Herramientas".' - - 'El {% data variables.product.prodname_code_scanning_capc %} cib {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar código de C++20. Esto solo está disponible cuando creas bases de código con GCC en Linux. Los módulos de C++20 aún no son compatibles.' - - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró al agregar compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) y al incrementar la cobertura de nuestros modelos de marcos de trabajo y librerías para varios lenguajes ({C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), y [Java](https://github.com/github/codeql/tree/main/java)). Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuarios no confiables, revisar los pasos a través de los cuales fluyen los datos e identificar hundimientos potencialmente peligrosos en los cuales podrían terminar estos datos,. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección de [registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).' - - "El {% data variables.product.prodname_code_scanning_capc %} ahora muestra niveles de `gravedad de seguridad` para las alertas del Code QL. Puedes configurar qué niveles de `gravedad de seguridad` ocasionarán un fallo de verificación para una solicitud de cambios. El nivel de gravedad de las alertas de seguridad puede ser `crítico`, `alto, `medio` o `bajo`. Predeterminadamente, cualquier alerta del {% data variables.product.prodname_code_scanning %} con un `nivel de gravedad` que sea `crítico` o `alto` ocasionará que una solicitud de cambios falle.\n\nAdicionalmetnte, ahora también puedes configurar qué niveles de gravedad ocasionarán que la verificación de solicitudes de cambio falle para las alertas que no sean de seguridad. Puedes configurar este comportamiento a nivel de repositorio y definir si las alertas con gravedad de `error`, `advertencia` o `nota` ocasionarán que una verificación de solicitud de cambio falle. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} que no sean de seguridad y tengan un nivel de gravedad de `error` ocasionarán que la verificación de una solicitud de cambios falle.\n\nPara obtener más información, consulta la sección \"[Definir qué alertas de niveles de gravedad ocasionan que falle la verificación de las solicitudes de cambio]](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)\".\n\n![Lista de alertas de escaneo de código con niveles de seguridad](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png)\n" - - "Las mejoras al filtro de rama para las alertas del {% data variables.product.prodname_code_scanning %} dejan más claro qué alertas del {% data variables.product.prodname_code_scanning %} se están mostrando en la página de alertas. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} se filtran para mostrar únicamente las alertas de la rama predeterminada del repositorio. Puedes utilizar el filtro de rama para mostrar las alertas en cualquiera de las ramas no predeterminadas. Cualquier filtro de rama que se haya aplicado se mostrará en la barra de búsqueda.\n\nLa sintaxis de búsqueda también se simplificó como `branch:`. Esta sintaxis se puede utilizar varias veces en la barra de búsqueda para filtrar en ramas múltiples. La sintaxis previa `ref:refs/heads/`, aún es compatible, así que cualquier URL que se haya guardado seguirá funcionando.\n" - - "Ahora está disponible la búsqueda de texto libre para las alertas de escaneo de código. Puedes buscar resultados del escaneo de código para encontrar alertas específicas rápidamente sin tener que conocer los términos de búsqueda exactos. La búsqueda se aplica a lo large del nombre, descripción y texto de ayuda de la alerta. La sintaxis es:\n\n- Una palabra única devuelve todas las coincidencias.\n- Las palabras de búsqueda múltiples devuelven coincidencias para cualquiera de las palabras.\n- Las palabras entre comillas dobles devuelven coincidencias exactas.\n- La palabra clave 'AND' devuelve coincidencias de palabras múltiples.\n" - - '{% data variables.product.prodname_secret_scanning_caps %} agregó patrones para 23 proveedores de servicio nuevos. Para encontrar la lista actualizada de secretos compatibles, consulta la sección "[Acerca del escaneo de secretos](/code-security/secret-scanning/about-secret-scanning)".' - - heading: 'Cambios a la API' + # https://github.com/github/releases/issues/1352 + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + + # https://github.com/github/releases/issues/1360 + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + + # https://github.com/github/releases/issues/1160 + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + + # https://github.com/github/releases/issues/1454 + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + + # https://github.com/github/releases/issues/1375 + - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + + # https://github.com/github/releases/issues/1335 + # https://github.com/github/releases/issues/1314 + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + + # https://github.com/github/releases/issues/1324 + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + + # https://github.com/github/releases/issues/1313 + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + + - heading: API Changes notes: - - 'La compatibilidad con paginación se agregó a la terminar de "comparar dos confirmaciones" de la API de REST, la cual devuelve una lista de confirmaciones que se pueden alcanzar desde una confirmación o rama, pero no desde alguna otra. La API ahora también puede devolver los resultados para comparaciones de más de 250 confirmaciones. Para obtener más información, consulta la sección de "[Repositories](/rest/reference/repos#compare-two-commits)" de la API de REST y la sección de "[Navegar con paginación](/rest/guides/traversing-with-pagination)".' - - 'La API de REST ahora puede utilizarse para reenviar mediante programación o verificar el estado de los webhooks. Para obtener más información, consulta las secciones "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," y "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' - - "Se han realizado mejoras al escaneo de código y a las API de la {% data variables.product.prodname_GH_advanced_security %}:\n\n- La API de escaneo de código ahora devuelve la versión de consulta de COdeQL que se utiliza para un análisis. Esto puede utilizarse para reproducir los resultados o confirmar un análisis que se utiliza como la consulta más reciente. Para obtener información, consulta la sección \"[Escaneo de código](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)\" en la documentación de la API de REST.\n-Los usuarios administrativos ahora pueden utilizar la API de REST para habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para repositorios utilizando el objeto `security_and_analysis` en `repos/{org}/{repo}`. Adicionalmente, los usuarios administrativos pueden verificar si la {% data variables.product.prodname_advanced_security %} se encuentra habilitada actualmente para un repositorio utilizando una solicitud de tipo `GET /repos/{owner}/{repo}`. Estos cambios de ayudan a administrar el acceso a los repositorios de {% data variables.product.prodname_advanced_security %} en escala. Para obtener más información, consulta la sección de \"[Repositories](/rest/reference/repos#update-a-repository)\" en la documentación de la API de REST.\n" + # https://github.com/github/releases/issues/1253 + - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)." + + # https://github.com/github/releases/issues/969 + - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation. + + # https://github.com/github/releases/issues/1349 + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + + # No security/bug fixes for the RC release + # security_fixes: + # - PLACEHOLDER + + # bugs: + # - PLACEHOLDER + known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + deprecations: - - heading: 'Obsoletización de GitHub Enterprise Server 2.21' + - heading: Deprecation of GitHub Enterprise Server 2.21 notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 se descontinuó el 6 de junio de 2021**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - - heading: 'Obsoletización de GitHub Enterprise Server 2.22' + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. 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 %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - heading: Deprecation of GitHub Enterprise Server 2.22 notes: - - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuará el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - - heading: 'Obsoletización del soporte para XenServer Hypervisor' + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. 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 %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - heading: Deprecation of XenServer Hypervisor support notes: - - 'Desde la versión 3.1 de {% data variables.product.prodname_ghe_server %}, comenzaremos a descontinuar la compatibilidad con Xen Hypervisor. La obsoletización completa está programada para la versión 3.3 de {% data variables.product.prodname_ghe_server %}, siguiendo la ventana de obsoletización estándar de un año. Por favor, contacta al [Soporte de Github](https://support.github.com/contact) so tienes dudas o preguntas.' - - heading: 'Eliminación de los servicios tradicionales de GitHub' + # https://github.com/github/docs-content/issues/4439 + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://support.github.com/contact) with questions or concerns. + - heading: Removal of Legacy GitHub Services notes: - - '{% data variables.product.prodname_ghe_server %} 3.2 elimina los registros de base de datos de GitHub Service sin utilizar. Hay más información disponible en la [publicación del anuncio de obsoletización](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' - - heading: 'Obsoletización de las terminales de la API de Aplicaciones OAuth y autenticación de la API a través de parámetros de consulta' + # https://github.com/github/releases/issues/1506 + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters notes: - - "Para prevenir el inicio de sesión o exposición accidental de los `access_tokens`, desalentamos el uso de las terminales de la API de las Aplicaciones OAuth y el uso de auth de API a través de parámetros de consultas. Visita las siguientes publicaciones para ver los reemplazos propuestos:\n\n*[Reemplazo para las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Reemplazo de auth a través de encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nSe pretende que estas terminales y rutas de auth se eliminen del {% data variables.product.prodname_ghe_server %} en la versión 3.4 de {% data variables.product.prodname_ghe_server %}.\n" - - heading: 'Eliminación de los eventos de webhook y terminales tradicionales de las GitHub Apps' + # https://github.com/github/releases/issues/1316 + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - heading: Removal of legacy GitHub App webhook events and endpoints notes: - - "Se eliminaron dos eventos de webhook relacionados con las GitHub Apps tradicionales: `integration_installation` y `integration_installation_repositories`. En su lugar, deberías estar escuchando a los eventos de `installation` y `installation_repositories`.\n" - - "La siguiente terminal de la API de REST se eliminó: `POST /installations/{installation_id}/access_tokens`. En su lugar, deberías etar utilizando aquella con designador de nombre: `POST /app/installations/{installation_id}/access_tokens`.\n" + # https://github.com/github/releases/issues/965 + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: - - '{% data variables.product.prodname_ghe_server %} 3.2 requiere de por lo menos contar con [Las Utilidades de Respaldo 3.2.0 de GitHub Enterprise](https://github.com/github/backup-utils) para [Los Respaldos y Recuperación de Desastres](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml index 3ffe8ffef8..b5f39207ee 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml @@ -1,126 +1,311 @@ date: '2021-09-28' -intro: 'Para encontrar las instrucciones de mejora, consulta la sección "[Mejorar a {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".' +intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." sections: features: - - heading: 'Patrones personalizados para el escaneo de secretos' + - heading: Custom patterns for secret scanning notes: - - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden especificar los patrones para el escaneo de secretos. Cuando se especifica un patrón nuevo, el escaneo de secretos busca dicho patrón en todo el historial de Git del repositorio, así como cualquier confirmación nueva.\n\nLos patrones definidos por los usuarios se encuentran en beta para {% data variables.product.prodname_ghe_server %} 3.2. Se pueden definir a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección \"[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)\".\n" - - heading: 'Resumen de seguridad para la Seguridad Avanzada (beta)' + # https://github.com/github/releases/issues/1426 + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + + - heading: Security overview for Advanced Security (beta) notes: - - "Los clientes de la {% data variables.product.prodname_GH_advanced_security %} ahora tienen una vista de nivel de organización apra los riegos de seguridad de las aplicaciones que detecte el {% data variables.product.prodname_code_scanning %}, el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_secret_scanning %}. El resumen de seguridad muestra la habilitación de estado de las características de seguridad en cada repositorio, así como la cantidad de alertas que se detectan.\n\nAdicionalmente, el resumen de seguridad lista todas las alertas del {% data variables.product.prodname_secret_scanning %} a nivel organizacional. Tendremos vistas similares para el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_code_scanning %} en los lanzamientos futuros cercanos. Para obtener más información, consulta la sección \"[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)\".\n\n![Captura de pantalla del resumen de seguridad](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png)\n" - - heading: 'Revisión de dependencias (beta)' + # https://github.com/github/releases/issues/1381 + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + + - heading: Dependency review (beta) notes: - - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden ver un diff enriquecido de las dependencias que cambiaron en una solicitud de cambios. La revisión de dependencias proporciona una vista fácil de entender de los cambios a las dependencias y de su impacto de seguridad en la pestaña de \"Archivos que cambiaron\" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron junto con la información de vulnerabilidades de estas dependencias. Para obtener más información, consulta la sección \"[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)\".\n" - - heading: 'Ambientes de GitHub Actions' + # https://github.com/github/releases/issues/1364 + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information for these dependencies. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + + - heading: GitHub Actions environments notes: - - "Los ambientes, las reglas de protección de ambiente y los secretos de ambiente ahora están disponibles en general para las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}. Para obtener más información, consulta la sección \"[Environments](/actions/reference/environments)\".\n" - - heading: 'Autenticación por SSH con llaves seguras' + # https://github.com/github/releases/issues/1308 + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + + - heading: SSH authentication with security keys notes: - - "Ahora es compatible la autenticación por SSH utilizando una llave de seguridad FIDO2 cuando agregas una llave SSH de tipo `sk-ecdsa-sha2-nistp256@openssh.com` o `sk-ssh-ed25519@openssh.com` a tu cuenta. Las llaves de seguridad SSH almacenan material de llaves secretas en un dispositivo de hardware por separado, el cual requiere de verificación, tal como un tap, para operar. Para obtener más información, consulta la sección \"[Generar una clave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)\".\n" - - heading: 'Temas oscuro y oscuro atenuado' + # https://github.com/github/releases/issues/1276 + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + + - heading: 'Dark and dark dimmed themes' notes: - - "Ahora hay temas oscuro y opaco oscuro disponibles para la IU web. {% data variables.product.product_name %} empatará las preferencias de tu sistema si no has configurado las preferencias de tema en {% data variables.product.product_name %}. También puedes elegir qué temas estarán activos durante el día y la noche. Para obtener más información, consulta la sección \"[Administrar la configuración de tu tema](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n\n![Temas oscuro y opaco oscuro](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif)\n" - - heading: 'Aprobar dominios no verificados para las notificaciones de correo electrónico' + # https://github.com/github/releases/issues/1260 + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + + - heading: 'Approving unverified domains for email notifications' notes: - - 'Los dominios que no se pueden verificar ahora pueden aprobarse para el enrutamiento de notificaciones por correo electrónico. Los propietarios de empresas y organizaciones podrán aprobar dominios y aumentar su política de restricción de notificaciones por correo electrónico automáticamente, lo cual permitirá que las notificaciones se envíen a los colaboradores, consultores, adquisiciones o a otros socios. para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" y "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' - - heading: 'Soporte para el almacenamiento de credenciales seguro del Administrador de Credenciales de Git (GCM) y autenticación multifactorial' + # https://github.com/github/releases/issues/1244 + - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." + + - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' notes: - - "Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}.\n\nGCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository.\n" + # https://github.com/github/releases/issues/1406 + - | + Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. + changes: - - heading: 'Cambios en la administración' + - heading: Administration Changes notes: - - 'Se agregó un ajuste de "Política de Referente de Agente Usuario" a la configuración empresarial. Esto permite que un administrador configure una "Política de referente" más estricta para ocultar el nombre de host de una instalación de {% data variables.product.prodname_ghe_server %} de sitios externos. Este ajuste se encuentra inhabilitado predeterminadamente y los eventos de bitácoras de auditoría lo rastrean para los propietarios empresariales y el personal de las empresas cuando se habilita o inhabilita. Para obtener más información, consulta la sección "[Configurar la Política de Referente en tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".' - - 'La revisión de salud de MySQL se cambió al uso de `mysqladmin ping` en vez de las verificaciones de TCP, lo cual elimina algo del ruido innecesario en la bitácora de errores de MySQL, las verificaciones de recuperación de fallos del orquestador se mejoraron para prevenir las recuperaciones de fallos de MySQL innecesarias al aplicar cambios de configuración del clúster.' - - 'El servicio Resque, el cual da la compatibilidad con procesamiento de jobs en segundo plano, se reemplazó con Aqueduct Lite. este cambio hace que el sistema de jobs se pueda administrar más fácilmente y no debería afectar la experiencia del usuario. Para la administración y comandos de depuración nuevas de Aqueduct, consulta la sección "[Utilidades de la línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)".' - - heading: 'Cambios de Token' + # https://github.com/github/releases/issues/1309 + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + + # https://github.com/github/releases/issues/1515 + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + + # https://github.com/github/releases/issues/1287 + - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." + + - heading: Token Changes notes: - - "El formato de tokens de autenticación para {% data variables.product.product_name %} ha cambiado,. Dicho cambio afecta el formato de los tokens de acceso personal y de los tokens de acceso para las {% data variables.product.prodname_oauth_apps %}, así como de los tokens de usuario a servidor, de servidor a servidor y de actualización para {% data variables.product.prodname_github_apps %}.\n\nLos diferentes tipos de token ahora tienen prefijos identificables únicos, los cuales permiten que el escaneo de secretos detecten los tokens para que puedas mitigar el impacto de que alguien confirme un token accidentalmente en un repositorio. {% data variables.product.company_short %} recomienda actualizar los tokens existentes tan pronto como te sea posible. Para obtener más información, consulta las secciones \"[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)\" y \"[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)\".\n" - - heading: 'Cambios de repositorios' + # https://github.com/github/releases/issues/1235 + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + + - heading: 'Repositories changes' notes: - - 'Los repositorios en los perfiles de usuario y en los perfiles de organización ahora son compatibles con la clasificación por conteo de estrellas.' - - 'Cuando veas el historial de confirmación de un archivo único, ahora puedes hacer clic en {% octicon "file-code" aria-label="The code icon" %} para ver dicho archivo en algún punto selecto del historial.' - - 'Cuando un submódulo se define con una ruta relativa en {% data variables.product.product_location %}, el submódulo ahora se puede hacer clic en la interfaz web. Al hacer clic en el submódulo de la interfaz web le llevará al repositorio enlazado. Anteriormente, sólo los submódulos con URLs absolutas podían hacer clic. Esto es soportado para rutas relativas para los repositorios con el mismo propietario que siguen el patrón ..REPOSITORY o rutas relativas de repositorios con un propietario diferente que siga el patrón ../OWNER/REPOSITORY. Para obtener más información sobre cómo trabajar con submódulos, consulta la sección [Trabajar con submódulos](https://github.blog/2016-02-01-working-with-submodules/) en {% data variables.product.prodname_blog %}.' - - 'La IU web ahora puede utilizarse para sincronizar una rama desactualizada de una bifurcación con la rama ascendente de dicha bifurcación. Si no hay conflictos de fusión entre las ramas, la rama se actualizará ya sea mediante un envío rápido o mediante la fusión desde la parte ascendente. Si hay conflictos, se te pedirá crear una solicitud de cambios para resolverlos. Para obtener más información, consulta la sección "[Sincronizar una bifurcación](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)".' - - heading: 'Cambios en el Lenguaje de Marcado' + # https://github.com/github/releases/issues/1295 + - Repositories on user profiles and organization profiles now support sorting by star count. + + # https://github.com/github/releases/issues/1327 + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + + # https://github.com/github/releases/issues/1254 + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + + # https://github.com/github/releases/issues/1250 + - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." + + - heading: 'Markdown changes' notes: - - 'El editor de lenguaje de marcado que se utiliza al crear o editar un lanzamiento en un repositorio ahora tiene una barra de herramientas para edición de texto. Para obtener más información, consulta la sección "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)".' - - '{% data variables.product.product_name %} ahora tiene compatibilidad para cargar archivos de video en donde sea que utilices lenguaje de marcado. Comparte demostraciones, pasos de reproducción y más en los comentarios de tus propuestas y solicitudes de cambio, así como en los archivos de lenguaje de marcado dentro de los repositorios, tales como los README. Para obtener más información, consulta la sección "[Adjuntar archivos](/github/writing-on-github/working-with-advanced-formatting/attaching-files)".' - - 'Los archivos de lenguaje de marcado ahora generarán una tabla de contenido automáticamente en el encabezado cuando haya 2 o más encabezados. La tabla de contenido es interactiva y enlaza a la sección seleccionada. Los 6 niveles de encabezado del lenguaje de marcado son compatibles.' - - 'Hay un atajo de teclado nuevo, `cmd+e` en macOS o `ctrl+e` en Windows, para insertar bloques de código en los archivos, propuestas, solicitudes de cambio y comentarios de Lenguaje de Marcado.' - - 'El agregar `?plain=1` a la URL en cualquier archivo de lenguaje de marcado ahora mostrará al archivo sin procesar y con números de línea. La vista simple puede utilizarse para enlazar a otros usuarios a líneas específicas. Por ejemplo, el agregar `?plain=1#L52` resaltará la línea 52 del archivo de marcado en texto simple. Para obtener más información, consulta la sección "[Crear un enlace permanente a un fragmento de código](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)".' - - heading: 'Cambios en propuestas y sollicitudes de cambio' + # https://github.com/github/releases/issues/1477 + - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + + # https://github.com/github/releases/issues/1169 + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + + # https://github.com/github/releases/issues/1269 + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + + # https://github.com/github/releases/issues/1294 + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + + # https://github.com/github/releases/issues/1474 + - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)." + + - heading: 'Issues and pull requests changes' notes: - - 'Con la [versión más reciente de Octicons](https://github.com/primer/octicons/releases), los estados de las propuestas y solicitudes de cambios ahora son más fáciles de distinguir visualmente para que puedas escanear los estados de forma más sencilla. Para obtener más información consulta la sección [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).' - - 'Ahora tenemos disponible una regla de protección de rama de "Requerir la resolución de la conversación antes de fusionar" y un menú de "Conversaciones". Descubre fácilmente tus comentarios de solicitudes de cambios desde la pestaña de "Archivos que cambiaron" y requiere qeu todas tus conversaciones en solicitudes de cambio se resuelvan antes de fusionarse. Para obtener más información, consulta las secciones "[Acerca de las revisiones de solicitudes de cambio](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)".' - - 'Para prevenir la fusión de cambios inesperados después de habilitar la fusión automática para una solicitud de cambios, ahora se inhabilitó esta opción automáticamente cuando un usuario sin acceso de escritura al repositorio sube estos cambios. Los usuarios que no tengan permisos de escritura aún pueden actualizar la solicitud de cambios con aquellos de la rama base cuando se habilita la fusión automática. Para prevenir que un usuario malintencionado utilice un conflicto de fusión para introducir cambios inesperados a la solicitud de cambios, la fusión automática para la solicitud de cambios se encuentra inhabilitada si dicha actualización causa un conflicto de fusión. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".' - - 'Las personas con permisos de mantenimiento ahora pueden administrar el ajuste de "Permitir la fusión automática" a nivel de repositorio. Este ajuste, el cual a menudo se encuentra inhabilitado, controla si la fusión automática está disponible para las solicitudes de cambios en el repositorio., Anteriormente, solo las personas con permisos administrativos podían administrar este ajuste. Adicionalmente, este ajuste ahora puede controlarse utilizando las API de REST para "[Crear repositorio](/rest/reference/repos#create-an-organization-repository)" y "[Actualizar repositorio](/rest/reference/repos#update-a-repository)". Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio]](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)".' - - 'La selección de propuestas y solicitudes de cambio de los asignados ahora es compatible con la búsqueda de escritura anticipada, así que puedes encontrar usuarios en tu organización más rápidamente. Adicionalmente, las clasificaciones de resultados de búsqueda se actualizaron para preferir las coincidencias al inicio del nombre de usuario de una persona o nombre de perfil.' - - 'Cuando se solicita una revisión de un equipo de más de 100 personas, los desarrolladores ahora muestran una caja de diálogo de confirmación para poder prevenir las notificaciones innecesarias para los equipos grandes.' - - 'Ahora hay compatibilidad con tener `code blocks` con comilla inversa en los títulos de las propuestas y en cualquier lugar en el que se referencien propuestas y solicitudes de cambios en {% data variables.product.prodname_ghe_server %}.' - - 'Los eventos para las solicitudes de cambios y revisiones de solicitudes de cambios ahora se incluyen en la bitácora de auditoría tanto para [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) como para [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). estos eventos ayudan a que los administradores monitoreen mejor la actividad de las solicitudes de cambios y ayuden a garantizar que se cumplan los requisitos de seguridad y cumplimiento. Los eventos pueden verse desde la IU web, exportarse como CSV o JSON o acceder a ellos a través de la API de REST. También puedes buscar la bitácora de auditoría para los eventos de solicitudes de cambio específicos. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)".' - - heading: 'Cambios a las ramas' + # https://github.com/github/releases/issues/1413 + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + + # https://github.com/github/releases/issues/1419 + - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." + + # https://github.com/github/releases/issues/1279 + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + + # https://github.com/github/releases/issues/1550 + - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)." + + # https://github.com/github/releases/issues/1201 + - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name. + + # https://github.com/github/releases/issues/1430 + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + + # https://github.com/github/releases/issues/1293 + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + + # https://github.com/github/releases/issues/1300 + - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)." + + - heading: 'Branches changes' notes: - - "El nombre de rama predeterminado para los repositorios nuevos ahora es `main`. Los repositorios existentes no se verán impactados por este cambio. Si los usuarios, propietarios de organizaciones o propietarios de empresas ya especificaron una rama predeterminada para repositorios nuevos anteriormente, tampoco se les impactará.\n\nSi quieres configurar un nombre de rama predeterminada diferente, puedes hacerlo en los ajustes de [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), o [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).\n" - - "Las ramas, incluyendo a la predeterminada, ahora pueden volver a nombrarse utilizando la IU web de {% data variables.product.product_name %}. Cuando una rama se vuelve a nombrar, cualquier solicitud de cambios abierta y lanzamiento de borrador que apunten a la rama que se volvió a nombrar se redirigirá automáticamente y las reglas de protección de rama que referencien explícitamente a la rama que se volvió a nombrar se actualizarán.\n\nSe requieren permisos administrativos para volver a nombrar la rama predeterminada, pero es suficiente contar con permisos de escritura para volver a nombrar otras ramas.\n\nPara ayudar a hacer el cambio con tanta continuidad como sea posible para los usuarios:\n\n* Se muestra un aviso a los contribuyentes, mantenedores y administradores de la página de inicio del repositorio, el cual contiene instrucciones para actualizar su repositorio local.\n*Las solicitudes web para la rama antigua se redireccionarán.\n* Se devolverá una respuesta HTTP de \"se movió permanentemente\" a todo llamado de la API de REST.\n* Se mostrará un mensaje informativo para los usuarios de la línea de comandos de Git que suban información a la rama antigua.\n\nPara obtener más información, consulta la sección \"[Volver a nombrar una rama](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)\".\n" - - heading: 'Cambioas a las GitHub Actions' + # https://github.com/github/releases/issues/885 + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + + # https://github.com/github/releases/issues/981 + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + + - heading: 'GitHub Actions changes' notes: - - 'Las {% data variables.product.prodname_actions %} ahora te permiten controlar los permisos que se otorgan al secreto del `GITHUB_TOKEN`. El `GITHUB_TOKEN` es un secreto que se genera automáticamente y te permite hacer llamados autenticados a la API de {% data variables.product.product_name %} en tus ejecuciones de flujo de trabajo. Las {% data variables.product.prodname_actions %} generan un token nuevo para cada job y hacen que el token venza cuando se completa el job. El token a menudo tiene permisos de `escritura` para varias [Terminales de la API](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), con excepción de los casos de las solicitudes de cambios de las bifurcaciones, los cuales siempre se marcan como de `lectura`. Estos ajustes nuevos te permiten seguir el principio de los menores privilegios necesarios en tus flujos de trabajo,. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".' - - 'El {% data variables.product.prodname_cli %} 1.9 y posterior te permiten trabajar con las {% data variables.product.prodname_actions %} en tu terminal. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' - - 'La bitácora de auditoría ahora incluye eventos asociados con las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}. Estos datos proporcionan un conjunto de datos ampliamente expandidos para los administradores, así como auditorías de cumplimiento. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)".' - - '{% data variables.product.prodname_ghe_server %} 3.2 contiene mejoras de rendimiento para la concurrencia de los jobs con {% data variables.product.prodname_actions %}. Para obtener más información sobre las metas de rendimiento nuevas de acuerdo con los rangos de configuraciones de CPU y memoria, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".' - - 'The [{% data variables.product.prodname_actions %} Runner](https://github.com/actions/runner) application in {% data variables.product.prodname_ghe_server %} 3.2 has been updated to [v2.279.0](https://github.com/actions/runner/releases/tag/v2.279.0).' - - heading: 'Cambios a los GitHub packages' + # https://github.com/github/releases/issues/1227 + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + + # https://github.com/github/releases/issues/1280 + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + + # https://github.com/github/releases/issues/1157 + - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)." + + # https://github.com/github/releases/issues/1587 + - | + {% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." + * The "Maximum Concurrency" values were modified to reflect our most up to date performance testing. [Updated: 2021-12-07] + + - The [{% data variables.product.prodname_actions %} Runner](https://github.com/actions/runner) application in {% data variables.product.prodname_ghe_server %} 3.2 has been updated to [v2.279.0](https://github.com/actions/runner/releases/tag/v2.279.0). + + - heading: 'GitHub Packages changes' notes: - - 'Cualquier paquete o versión de paquete del {% data variables.product.prodname_registry %} ahora se puede borrar de la IU web de {% data variables.product.product_name %}. También puedes deshacer el borrado de cualquier paquete o versión de paquete dentro de los primeros 30 días. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".' - - heading: 'Cambios al Dependabot y a la gráfica de Dependencias' + # https://github.com/github/releases/issues/1088 + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + + - heading: 'Dependabot and Dependency graph changes' notes: - - 'La gráfica de dependencias ahora puede habilitarse utilizando la Consola de Administración en vez de necesitar la ejecución de un comando en el shell administrativo. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".' - - 'Ahora, las notificaciones para {% data variables.product.prodname_dependabot_alerts %} múltiples se agrupan si se descubren al mismo tiempo. Esto reduce significativamente el volumen de notificaciones de alertas del {% data variables.product.prodname_dependabot %} que reciben los usuarios. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).' - - 'Las gráficas de dependencias y {% data variables.product.prodname_dependabot_alerts %} ahora son compatibles con los módulos de Go. {% data variables.product.prodname_ghe_server %} analiza los archivos de `go.mod` de un repositorio para entender las dependencias del mismo. En conjunto con las asesorías de seguridad, la gráfica de dependencias proporciona la información necesaria para alertar a los desarrolladores sobre las dependencias vulnerables. Para obtener más información sobre cómo habilitar la gráfica de dependencias en los repositorios privados, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)".' - - 'Los ajustes de notificación predeterminados para las alertas de seguridad han cambiado. Anteriormente, si tenías permiso para ver las alertas de seguridad en un repositorio, hubieras recibido las notificaciones de dicho repositorio mientras tu configuración permitiera las notificaciones de alertas de seguridad. Ahora debes decidir unirte a las notificaciones de alertas de seguridad observando el repositorio. Se te notificará si seleccionas `Toda la actividad` o si configuras `Personalizado` para incluir las `Alertas de seguridad`. Todos los repositorios existentes se migrarán automáticamente a estos ajustes nuevos y seguirás recibiendo notificaciones; sin embargo, cualquier repositorio nuevo requerirá que decidas unirte observando el repositorio. Para obtener más información, consulta las secciones "[Configurar notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" y "[Administrar las alertas del escaneo de secretos](/code-security/secret-security/managing-alerts-from-secret-scanning)".' - - heading: 'Cambios al escaneo de código y de secretos' + # https://github.com/github/releases/issues/1537 + - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." + + # https://github.com/github/releases/issues/1153 + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + + # https://github.com/github/releases/issues/1371 + - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)." + + # https://github.com/github/releases/issues/1538 + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + + - heading: 'Code scanning and secret scanning changes' notes: - - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql %} ahora genera información diagnóstica para todos los lenguajes compatibles. Esto ayuda a mantener el estado de la base de datos creada para entender el estado y calidad del análisis que se realizó. La información diagnóstica se encuentra disponible desde la [versión 2.5.6](https://github.com/github/codeql-cli-binaries/releases) del {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). Puedes ver esta información diagnóstica detallada en las bitácoras para {% data variables.product.prodname_codeql %} de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras de escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".' - - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql_cli %} ahora es compatible con el análisis de diversos lenguajes durante una compilación sencilla. Esto facilita el ejecutar análisis de código para utilizar sistemas de IC/DC diferentes a los de las {% data variables.product.prodname_actions %}. El modo nuevo del comando `codeql database create` se encuentra disponible desde la [versión 2.5.6] (https://github.com/github/codeql-cli-binaries/releases) del [{% data variables.product.prodname_codeql_cli %}] (https://codeql.github.com/docs/codeql-cli/). Para obtener más información sobre cómo configurar esto, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)".' - - 'Las alertas de {% data variables.product.prodname_code_scanning_capc %} de todas las herramientas habilitadas ahora se muestran en una lista consolidada para que puedas priorizar fácilmente entre todas ellas. Puedes ver las alertas desde una herramienta específica utilizando le filtro de "Herramienta" y los de "Regla" y "Etiqueta" se actualizarán dinámicamente con base en tu selección de "Herramientas".' - - 'El {% data variables.product.prodname_code_scanning_capc %} cib {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar código de C++20. Esto solo está disponible cuando creas bases de código con GCC en Linux. Los módulos de C++20 aún no son compatibles.' - - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró al agregar compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) y al incrementar la cobertura de nuestros modelos de marcos de trabajo y librerías para varios lenguajes ({C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), y [Java](https://github.com/github/codeql/tree/main/java)). Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuarios no confiables, revisar los pasos a través de los cuales fluyen los datos e identificar hundimientos potencialmente peligrosos en los cuales podrían terminar estos datos,. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección de [registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).' - - "El {% data variables.product.prodname_code_scanning_capc %} ahora muestra niveles de `gravedad de seguridad` para las alertas del Code QL. Puedes configurar qué niveles de `gravedad de seguridad` ocasionarán un fallo de verificación para una solicitud de cambios. El nivel de gravedad de las alertas de seguridad puede ser `crítico`, `alto, `medio` o `bajo`. Predeterminadamente, cualquier alerta del {% data variables.product.prodname_code_scanning %} con un `nivel de gravedad` que sea `crítico` o `alto` ocasionará que una solicitud de cambios falle.\n\nAdicionalmetnte, ahora también puedes configurar qué niveles de gravedad ocasionarán que la verificación de solicitudes de cambio falle para las alertas que no sean de seguridad. Puedes configurar este comportamiento a nivel de repositorio y definir si las alertas con gravedad de `error`, `advertencia` o `nota` ocasionarán que una verificación de solicitud de cambio falle. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} que no sean de seguridad y tengan un nivel de gravedad de `error` ocasionarán que la verificación de una solicitud de cambios falle.\n\nPara obtener más información, consulta la sección \"[Definir qué alertas de niveles de gravedad ocasionan que falle la verificación de las solicitudes de cambio]](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)\".\n\n![Lista de alertas de escaneo de código con niveles de seguridad](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png)\n" - - "Las mejoras al filtro de rama para las alertas del {% data variables.product.prodname_code_scanning %} dejan más claro qué alertas del {% data variables.product.prodname_code_scanning %} se están mostrando en la página de alertas. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} se filtran para mostrar únicamente las alertas de la rama predeterminada del repositorio. Puedes utilizar el filtro de rama para mostrar las alertas en cualquiera de las ramas no predeterminadas. Cualquier filtro de rama que se haya aplicado se mostrará en la barra de búsqueda.\n\nLa sintaxis de búsqueda también se simplificó como `branch:`. Esta sintaxis se puede utilizar varias veces en la barra de búsqueda para filtrar en ramas múltiples. La sintaxis previa `ref:refs/heads/`, aún es compatible, así que cualquier URL que se haya guardado seguirá funcionando.\n" - - "Ahora está disponible la búsqueda de texto libre para las alertas de escaneo de código. Puedes buscar resultados del escaneo de código para encontrar alertas específicas rápidamente sin tener que conocer los términos de búsqueda exactos. La búsqueda se aplica a lo large del nombre, descripción y texto de ayuda de la alerta. La sintaxis es:\n\n- Una palabra única devuelve todas las coincidencias.\n- Las palabras de búsqueda múltiples devuelven coincidencias para cualquiera de las palabras.\n- Las palabras entre comillas dobles devuelven coincidencias exactas.\n- La palabra clave 'AND' devuelve coincidencias de palabras múltiples.\n" - - '{% data variables.product.prodname_secret_scanning_caps %} agregó patrones para 23 proveedores de servicio nuevos. Para encontrar la lista actualizada de secretos compatibles, consulta la sección "[Acerca del escaneo de secretos](/code-security/secret-scanning/about-secret-scanning)".' - - heading: 'Cambios a la API' + # https://github.com/github/releases/issues/1352 + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + + # https://github.com/github/releases/issues/1360 + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + + # https://github.com/github/releases/issues/1160 + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + + # https://github.com/github/releases/issues/1454 + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + + # https://github.com/github/releases/issues/1375 + - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + + # https://github.com/github/releases/issues/1335 + # https://github.com/github/releases/issues/1314 + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + + # https://github.com/github/releases/issues/1324 + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + + # https://github.com/github/releases/issues/1313 + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + + - heading: API Changes notes: - - 'La compatibilidad con paginación se agregó a la terminar de "comparar dos confirmaciones" de la API de REST, la cual devuelve una lista de confirmaciones que se pueden alcanzar desde una confirmación o rama, pero no desde alguna otra. La API ahora también puede devolver los resultados para comparaciones de más de 250 confirmaciones. Para obtener más información, consulta la sección de "[Repositories](/rest/reference/repos#compare-two-commits)" de la API de REST y la sección de "[Navegar con paginación](/rest/guides/traversing-with-pagination)".' - - 'La API de REST ahora puede utilizarse para reenviar mediante programación o verificar el estado de los webhooks. Para obtener más información, consulta las secciones "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," y "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' - - "Se han realizado mejoras al escaneo de código y a las API de la {% data variables.product.prodname_GH_advanced_security %}:\n\n- La API de escaneo de código ahora devuelve la versión de consulta de COdeQL que se utiliza para un análisis. Esto puede utilizarse para reproducir los resultados o confirmar un análisis que se utiliza como la consulta más reciente. Para obtener información, consulta la sección \"[Escaneo de código](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)\" en la documentación de la API de REST.\n-Los usuarios administrativos ahora pueden utilizar la API de REST para habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para repositorios utilizando el objeto `security_and_analysis` en `repos/{org}/{repo}`. Adicionalmente, los usuarios administrativos pueden verificar si la {% data variables.product.prodname_advanced_security %} se encuentra habilitada actualmente para un repositorio utilizando una solicitud de tipo `GET /repos/{owner}/{repo}`. Estos cambios de ayudan a administrar el acceso a los repositorios de {% data variables.product.prodname_advanced_security %} en escala. Para obtener más información, consulta la sección de \"[Repositories](/rest/reference/repos#update-a-repository)\" en la documentación de la API de REST.\n" + # https://github.com/github/releases/issues/1253 + - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)." + + # https://github.com/github/releases/issues/969 + - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation. + + # https://github.com/github/releases/issues/1349 + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + + # No security/bug fixes for the RC release + # security_fixes: + # - PLACEHOLDER + + # bugs: + # - PLACEHOLDER + known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + deprecations: - - heading: 'Obsoletización de GitHub Enterprise Server 2.21' + - heading: Deprecation of GitHub Enterprise Server 2.21 notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 se descontinuó el 6 de junio de 2021**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - - heading: 'Obsoletización de GitHub Enterprise Server 2.22' + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. 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 %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - heading: Deprecation of GitHub Enterprise Server 2.22 notes: - - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuará el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - - heading: 'Obsoletización del soporte para XenServer Hypervisor' + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. 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 %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - heading: Deprecation of XenServer Hypervisor support notes: - - 'Desde la versión 3.1 de {% data variables.product.prodname_ghe_server %}, comenzaremos a descontinuar la compatibilidad con Xen Hypervisor. La obsoletización completa está programada para la versión 3.3 de {% data variables.product.prodname_ghe_server %}, siguiendo la ventana de obsoletización estándar de un año. Por favor, contacta al [Soporte de Github](https://support.github.com/contact) so tienes dudas o preguntas.' - - heading: 'Eliminación de los servicios tradicionales de GitHub' + # https://github.com/github/docs-content/issues/4439 + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://support.github.com/contact) with questions or concerns. + - heading: Removal of Legacy GitHub Services notes: - - '{% data variables.product.prodname_ghe_server %} 3.2 elimina los registros de base de datos de GitHub Service sin utilizar. Hay más información disponible en la [publicación del anuncio de obsoletización](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' - - heading: 'Obsoletización de las terminales de la API de Aplicaciones OAuth y autenticación de la API a través de parámetros de consulta' + # https://github.com/github/releases/issues/1506 + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters notes: - - "Para prevenir el inicio de sesión o exposición accidental de los `access_tokens`, desalentamos el uso de las terminales de la API de las Aplicaciones OAuth y el uso de auth de API a través de parámetros de consultas. Visita las siguientes publicaciones para ver los reemplazos propuestos:\n\n*[Reemplazo para las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Reemplazo de auth a través de encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nSe pretende que estas terminales y rutas de auth se eliminen del {% data variables.product.prodname_ghe_server %} en la versión 3.4 de {% data variables.product.prodname_ghe_server %}.\n" - - heading: 'Eliminación de los eventos de webhook y terminales tradicionales de las GitHub Apps' + # https://github.com/github/releases/issues/1316 + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - heading: Removal of legacy GitHub App webhook events and endpoints notes: - - "Se eliminaron dos eventos de webhook relacionados con las GitHub Apps tradicionales: `integration_installation` y `integration_installation_repositories`. En su lugar, deberías estar escuchando a los eventos de `installation` y `installation_repositories`.\n" - - "La siguiente terminal de la API de REST se eliminó: `POST /installations/{installation_id}/access_tokens`. En su lugar, deberías etar utilizando aquella con designador de nombre: `POST /app/installations/{installation_id}/access_tokens`.\n" + # https://github.com/github/releases/issues/965 + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: - - '{% data variables.product.prodname_ghe_server %} 3.2 requiere de por lo menos contar con [Las Utilidades de Respaldo 3.2.0 de GitHub Enterprise](https://github.com/github/backup-utils) para [Los Respaldos y Recuperación de Desastres](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml new file mode 100644 index 0000000000..2d761493fc --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml @@ -0,0 +1,25 @@ +date: '2021-12-07' +sections: + security_fixes: + - 'Support bundles could include sensitive files if they met a specific set of conditions.' + bugs: + - 'In some cases when Actions was not enabled, `ghe-support-bundle` reported an unexpected message `Unable to find MS SQL container.`' + - 'Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.' + - 'A misconfiguration in the Management Console caused scheduling errors.' + - 'Docker would hold log files open after a log rotation.' + - 'Migrations could get stuck due to incorrect handling of `blob_path` values that are not UTF-8 compatible.' + - 'GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments.' + - 'Pagination links on org audit logs would not persist query parameters.' + - 'During a hotpatch, it was possible for duplicate hashes if a transition ran more than once.' + changes: + - 'Clarifies explanation of Actions path-style in documentation.' + - 'Updates support contact URLs to use the current support site, support.github.com.' + - 'Additional troubleshooting provided when running `ghe-mssql-diagnostic`.' + known_issues: + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml index ab3c6a4e98..cf185c5c31 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -1,6 +1,6 @@ date: '2021-11-09' release_candidate: true -deprecated: false +deprecated: true intro: "{% note %}\n\n**Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.\n\n{% endnote %}\n\nFor upgrade instructions, see \"[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server).\"\n" sections: features: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml new file mode 100644 index 0000000000..99bf26343c --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml @@ -0,0 +1,114 @@ +date: '2021-12-07' +intro: 'For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."

    **Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.' +sections: + features: + - heading: 'Security Manager role' + notes: + - "Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The \"security manager\" role can be applied to any team and grants the team's members the following access:\n\n- Read access on all repositories in the organization.\n- Write access on all security alerts in the organization.\n- Access to the organization-level security tab.\n- Write access on security settings at the organization level.\n- Write access on security settings at the repository level.\n\nFor more information, see \"[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"\n" + - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' + notes: + - "{% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.\n\nEphemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management.\n\nYou can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.\n\nFor more information, see \"[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)\" and \"[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job).\"\n" + - heading: 'Dark high contrast theme' + notes: + - "A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.\n\n![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)\n\nFor more information about changing your theme, see \"[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings).\"\n" + changes: + - heading: 'Cambios en la administración' + notes: + - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.' + - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."' + - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."' + - 'A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.' + - heading: 'Cambios de Token' + notes: + - "An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.\n\nWhen using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see \"[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).\"\n" + - heading: 'Notifications changes' + notes: + - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.' + - heading: 'Cambios de repositorios' + notes: + - 'Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code.' + - 'If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list.' + - 'When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.' + - 'You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers.' + - 'When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."' + - 'A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).' + - 'You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."' + - heading: 'Cambios en el Lenguaje de Marcado' + notes: + - "You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments.\n\n* To add quotes, use cmd shift . on Mac, or ctrl shift . on Windows and Linux.\n* To add an ordered list, use cmd shift 7 on Mac, or ctrl shift 7 on Windows and Linux.\n* To add an unordered list, use cmd shift 8 on Mac, or ctrl shift 8 on Windows and Linux.\n\nSee \"[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)\" for a full list of available shortcuts.\n" + - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."' + - 'When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.' + - 'You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."' + - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.' + - 'When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.' + - heading: 'Cambios en propuestas y sollicitudes de cambio' + notes: + - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."' + - "Improvements have been made to help teams manage code review assignments. You can now:\n\n- Limit assignment to only direct members of the team.\n- Continue with automatic assignment even if one or more members of the team are already requested.\n- Keep a team assigned to review even if one or more members is newly assigned.\n\nThe timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.\n\nFor more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).\n" + - 'You can now filter pull request searches to only include pull requests you are directly requested to review.' + - 'Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."' + - heading: 'Cambioas a las GitHub Actions' + notes: + - 'You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."' + - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.' + - "The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:\n\n* A self-hosted runner is registered or removed.\n* A self-hosted runner is added to a runner group, or removed from a runner group.\n* A runner group is created or removed.\n* A workflow run is created or completed.\n* A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.\n\nFor more information, see \"[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events).\"\n" + - '{% data variables.product.prodname_ghe_server %} 3.3 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."' + - 'To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}.' + - heading: 'Cambios a los GitHub packages' + notes: + - 'When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.' + - heading: 'Cambios al Dependabot y a la gráfica de Dependencias' + notes: + - 'Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."' + - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.' + - heading: 'Cambios al escaneo de código y de secretos' + notes: + - 'The depth of {% data variables.product.prodname_codeql %}''s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.' + - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).' + - "Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request.\n\nSome other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).\n" + - 'You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).' + - 'User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository''s entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."' + - heading: 'API and webhook changes' + notes: + - 'Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)."' + - 'You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."' + - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Repositories](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.' + - 'Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."' + - 'You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.' + - 'GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository''s issues and pull requests, and to access a public repository''s comments and content.' + - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.' + - "A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.\n\nCommits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n" + - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.' + - heading: 'Performance Changes' + notes: + - 'Page loads and jobs are now significantly faster for repositories with many Git refs.' + known_issues: + - 'After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.' + - 'On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' + deprecations: + - heading: 'Obsoletización de GitHub Enterprise Server 2.22' + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuó el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' + - heading: 'Deprecation of GitHub Enterprise Server 3.0' + notes: + - '**{% data variables.product.prodname_ghe_server %} 3.0 se descontinuará el 16 de febrero de 2022**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' + - heading: 'Obsoletización del soporte para XenServer Hypervisor' + notes: + - 'Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.' + - heading: 'Deprecation of OAuth Application API endpoints and API authentication using query parameters' + notes: + - "To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements:\n\n* [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nThese endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.\n" + - heading: 'Deprecation of the CodeQL runner' + notes: + - 'The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).' + - heading: 'Deprecation of custom bit-cache extensions' + notes: + - "Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3.\n\nAny repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.\n\nRepositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.\n\nTo start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the **Schedule** button.\n" + backups: + - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml b/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml index 62827a6cf5..0931904dc8 100644 --- a/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml +++ b/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml @@ -9,11 +9,9 @@ sections: heading: 'GitHub Actions beta' notes: - | - [Las {% data variables.product.prodname_actions %}](https://github.com/features/actions)son una solución poderosa y flexible de IC/DC y automatización de flujos de trabajo. Para obtener más información, consulta la sección "[Introducción a las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)." + [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)." - Las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %} utilizan un [{% data variables.actions.hosted_runner %}] nuevo (/actions/using-github-hosted-runners/about-ae-hosted-runners), el cual solo se encuentra disponible para {% data variables.product.product_name %} y que te permite personalizar el tamaño, imágenes y configuración de red de los ejecutores. Estos ejecutores son un ambiente de cómputo de IC con servicios finalizados y que cuentan con auto-escalamiento y administración y que {% data variables.product.company_short %} administra en su totalidad. Durante el beta, usar los {% data variables.actions.hosted_runner %}s es gratuito. Para obtener más información, consulta la sección "[Agregar {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)." - - Por favor, toma en cuenta que cuando se habiliten las {% data variables.product.prodname_actions %} durante esta mejora, se mostrarán dos organizaciones llamadas "GitHub Actions" (@**actions** y @**github**) en {% data variables.product.product_location %}. {% data variables.product.prodname_actions %} requiere estas organizaciones. los usuarios de nombre @**ghost** y @**actions** aparecerán como los actores para la creación de estas organizaciones en la bitácora de auditoría. + Please note that when {% data variables.product.prodname_actions %} is enabled during this upgrade, two organizations named "GitHub Actions" (@**actions** and @**github**) will appear in {% data variables.product.product_location %}. These organizations are required by {% data variables.product.prodname_actions %}. Users named @**ghost** and @**actions** appear as the actors for creation of these organizations in the audit log. - heading: 'GitHub Packages beta' notes: diff --git a/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml new file mode 100644 index 0000000000..1b0a3fcaa6 --- /dev/null +++ b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -0,0 +1,136 @@ +date: '2021-12-06' +friendlyDate: 'December 6, 2021' +title: 'December 6, 2021' +currentWeek: true +sections: + features: + - heading: 'Administration' + notes: + - | + Customers with active or trial subscriptions for {% data variables.product.product_name %} can now provision {% data variables.product.product_name %} resources from the [Azure Portal](https://portal.azure.com/signin/index/). Your Azure subscription must be feature-flagged to access {% data variables.product.product_name %} resources in the portal. Contact your account manager or {% data variables.contact.contact_enterprise_sales %} to validate your Azure subscription's eligibility. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_managed %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae#deploying-github-ae-with-the-azure-portal)." + - heading: 'GitHub Actions' + notes: + - | + [GitHub Actions](https://github.com/features/actions) is now generally available for {% data variables.product.product_name %}. GitHub Actions is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)." + - | + Self-hosted runners are the default type of runner system on {% data variables.product.product_name %}, and are now generally available for GitHub Actions. With self-hosted runners, you can manage your own machines or containers for the execution of GitHub Actions jobs. For more information, see "[About self-hosted runners](https://docs.github.com/en/github-ae@latest/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." + - | + Environments, environment protection rules, and environment secrets are now generally available for GitHub Actions on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + - | + GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can achieve the following. + + - View and understand complex workflows. + - Track progress of workflows in real-time. + - Troubleshoot runs quickly by easily accessing logs and jobs metadata. + - Monitor progress of deployment jobs and easily access deployment targets. + + For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)." + - | + GitHub Actions now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. GitHub Actions generates a new token for each job and expires the token when a job completes. The token has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)." + - | + GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message. + - | + GitHub CLI 1.9 and later allows you to work with GitHub Actions in your terminal. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/). + + - heading: 'Code scanning' + notes: + - | + Code scanning is now in beta for {% data variables.product.product_name %}. For more information, see "[About code scanning](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)." + - heading: 'Secret scanning' + notes: + - | + You can now specify your own patterns for secret scanning with the beta of custom patterns on {% data variables.product.product_name %}. You can specify patterns for repositories, organizations, and your entire enterprise. When you specify a new pattern, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - heading: 'GitHub Connect' + notes: + - | + GitHub Connect is now available in beta for {% data variables.product.product_name %}. GitHub Connect brings the power of the world's largest open source community to {% data variables.product.product_location %}. You can allow users to view search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_name %}, show contribution counts from {% data variables.product.product_name %} on {% data variables.product.prodname_dotcom_the_website %}, and use GitHub Actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + - heading: 'GitHub Packages' + notes: + - | + You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI or REST API. You can also undo the deletion of any package or package version within 30 days. + - | + The npm registry for GitHub Packages and {% data variables.product.prodname_dotcom_the_website %} no longer returns a time value in metadata responses, providing substantial performance improvements. {% data variables.product.company_short %} will continue returning the time value in the future. + - heading: 'Audit logging' + notes: + - | + Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help administrators better monitor pull request activity and ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. + - | + Additional events for GitHub Actions are now included in the audit log for both [enterprises](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). + + - A workflow is deleted or re-run. + - A self-hosted runner's version is updated. + - heading: 'Authentication' + notes: + - | + GitHub AE now officially supports Okta for SAML single sign-on (SSO) and user provisioning with SCIM. You can also map groups in Okta to teams on GitHub AE. For more information, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" and "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for OAuth Apps, as well as user-to-server, server-to-server, and refresh tokens for GitHub Apps. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible to improve security and allow secret scanning to detect the tokens. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About secret scanning](/code-security/secret-security/about-secret-scanning)." + - | + You can now authenticate SSH connections to {% data variables.product.product_name %} using a FIDO2 security key by adding an `sk-ecdsa-sha2-nistp256@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. Storing the key on separate hardware and requiring physical interaction for your SSH key offers additional security. Since the key is stored on hardware and is non-extractable, the key can't be read or stolen by software running on the computer. The physical interaction prevents unauthorized use of the key since the security key will not operate until you physically interact with it. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + - | + Git Credential Manager (GCM) Core versions 2.0.452 and later now provide secure credential storage and multi-factor authentication support for {% data variables.product.product_name %}. GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + - heading: 'Notifications' + notes: + - | + You can now configure which events you would like to be notified about on {% data variables.product.product_name %}. From any repository, select the {% octicon "file-code" aria-label="The code icon" %} **Watch** drop-down, then click **Custom**. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)." + - heading: 'Issues and pull requests' + notes: + - | + With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - | + You can now see all pull request review comments in the **Files** tab for a pull request by selecting the **Conversations** drop-down. You can also require that all pull request review comments are resolved before anyone merges the pull request. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." For more information about management of branch protection settings with the API, see "[Repositories](/rest/reference/repos#get-branch-protection)" in the REST API documentation and "[Mutations](/graphql/reference/mutations#createbranchprotectionrule)" in the GraphQL API documentation. + - | + You can now upload video files everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, show reproduction steps, and more in issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - | + {% data variables.product.product_name %} now shows a confirmation dialog when you request a review from a team with more than 100 members, allowing you to prevent unnecessary notifications for large teams. + - | + When an issue or pull request has fewer than 30 possible assignees, the assignees control will list all potential users rather than a limited set of suggestions. This behavior helps people in small organizations to quickly find the right user. For more information about assigning users to issues and pull requests, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users#assigning-an-individual-issue-or-pull-request)." + - | + You can now include multiple words after the `#` in a comment for an issue or pull request to further narrow your search. To dismiss the suggestions, press Esc. + - | + To prevent the merge of unexpected changes after you enable auto-merge for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, {% data variables.product.product_name %} will disable auto-merge for the pull request if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - | + People with maintain access can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin access could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)." + - | + The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name. + + - heading: 'Repositories' + notes: + - | + When viewing the commit history for a file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view the file at the specified time in the repository's history. + - | + You can now use the web UI to synchronize an out-of-date branch for a fork with the fork's upstream branch. If there are no merge conflicts between the branches, {% data variables.product.product_name %} updates your branch either by fast-forwarding or by merging from upstream. If there are conflicts, {% data variables.product.product_name %} will prompt you to open pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." + - | + You can now sort the repositories on a user or organization profile by star count. + - | + The Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another, now supports pagination. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)." + - | + When you define a submodule in {% data variables.product.product_location %} with a relative path, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. Relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY are supported. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - | + By precomputing checksums, the amount of time a repository is under lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance. + - heading: 'Releases' + notes: + - | + You can now react with emoji to all releases on {% data variables.product.product_name %}. For more information, see "[About releases](/github/administering-a-repository/releasing-projects-on-github/about-releases)." + - heading: 'Themes' + notes: + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also customize the themes that are active during day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + - heading: 'Markdown' + notes: + - | + Markdown files in your repositories now automatically generate a table of contents in the header the file has two or more headings. The table of contents is interactive and links to the corresponding section. All six Markdown heading levels are supported. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes#auto-generated-table-of-contents-for-readme-files)." + - | + `code` markup is now supported in titles for issues and pull requests. Text within backticks (`` ` ``) will appear rendered in a fixed-width font anywhere the issue or pull request title appears in the web UI for {% data variables.product.product_name %}. + - | + While editing Markdown in files, issues, pull requests, or comments, you can now use a keyboard shortcut to insert a code block. The keyboard shortcut is command + E on a Mac or Ctrl + E on other devices. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code)." + - | + You can append `?plain=1` to the URL for any Markdown file to display the file without rendering and with line numbers. You can use the plain view to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)." + - heading: 'GitHub Apps' + notes: + - | + API requests to create an installation access token now respect IP allow lists for an enterprise or organization. Any API requests made with an installation access token for a GitHub App installed on your organization already respect IP allow lists. This feature does not currently consider any Azure network security group (NSG) rules that {% data variables.product.company_short %} Support has configured for {% data variables.product.product_location %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise#about-ip-allow-lists)," "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)," and "[Apps](https://docs.github.com/en/rest/reference/apps#create-an-installation-access-token-for-an-app)" in the REST API documentation. + - heading: 'Webhooks' + notes: + - | + You can now programmatically resend or check the status of webhooks through the REST API. For more information, see "[Repositories](https://docs.github.com/en/rest/reference/repos#webhooks)," "[Organizations](https://docs.github.com/en/rest/reference/orgs#webhooks)," and "[Apps](https://docs.github.com/en/rest/reference/apps#webhooks)" in the REST API documentation. diff --git a/translations/es-ES/data/reusables/actions/about-secrets.md b/translations/es-ES/data/reusables/actions/about-secrets.md index c2b646d0ae..6a1f925a0c 100644 --- a/translations/es-ES/data/reusables/actions/about-secrets.md +++ b/translations/es-ES/data/reusables/actions/about-secrets.md @@ -1 +1 @@ -Los secretos cifrados te permiten almacenar información sensible, tal como tokens de acceso, en tu repositorio{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, ambientes de repositorio,{% endif %} u organización. +Los secretos cifrados te permiten almacenar información sensible, tal como tokens de acceso, en tu repositorio{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, ambientes de repositorio,{% endif %} u organización. diff --git a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md index a6086c3289..2006e4fe69 100644 --- a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md @@ -1,12 +1,12 @@ -| Acción | Descripción | -| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -| `cancel_workflow_run` | Se activa cuando se cancela una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Cancelar un flujo de trabajo](/actions/managing-workflow-runs/canceling-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} -| `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} -| `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -| `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". | -| `disable_workflow` | Se activa cuando se inhabilita un flujo de trabajo. | -| `enable_workflow` | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente. | -| `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} -| `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. Para obtener más información, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} -| `approve_workflow_job` | Se activa cuando se aprueba el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". | -| `reject_workflow_job` | Se activa cuando se rechaza el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)".{% endif %} +| Acción | Descripción | +| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `cancel_workflow_run` | Se activa cuando se cancela una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Cancelar un flujo de trabajo](/actions/managing-workflow-runs/canceling-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} +| `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} +| `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". | +| `disable_workflow` | Se activa cuando se inhabilita un flujo de trabajo. | +| `enable_workflow` | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente. | +| `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)".{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} +| `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. Para obtener más información, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `approve_workflow_job` | Se activa cuando se aprueba el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". | +| `reject_workflow_job` | Se activa cuando se rechaza el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)".{% endif %} diff --git a/translations/es-ES/data/reusables/actions/ae-beta.md b/translations/es-ES/data/reusables/actions/ae-beta.md deleted file mode 100644 index 2bb67af1aa..0000000000 --- a/translations/es-ES/data/reusables/actions/ae-beta.md +++ /dev/null @@ -1,13 +0,0 @@ -{% ifversion ghae-next %} - - - -{% elsif ghae %} - -{% note %} - -**Nota:** El {% data variables.product.prodname_actions %} se encuentra actualmente en beta para {% data variables.product.prodname_ghe_managed %}. - -{% endnote %} - -{% endif %} diff --git a/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md b/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md deleted file mode 100644 index 3abe4cf00b..0000000000 --- a/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md +++ /dev/null @@ -1,7 +0,0 @@ -{% ifversion ghae %} -{% note %} - -**Nota:** Los {% data variables.actions.hosted_runner %} se encuentran actualmente en beta y están sujetos a cambios. - -{% endnote %} -{% endif %} diff --git a/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md index ee2da8757a..09b656c396 100644 --- a/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -2,17 +2,7 @@ {% warning %} -{% ifversion ghae-next %} - -**Advertencia:** Los ejecutores auto-hospedados se hablitan predeterminadamente para {% data variables.product.prodname_ghe_managed %}. Los ejecutores auto-hospedados son de larga duración y cualquier riesgo que sufra la máquina hospedadora podría filtrar secretos o credenciales, o habilitar otros ataques. Si te gustaría inhabilitar los ejecutores auto-hospedados en tu empresa, puedes contactar al soporte de {% data variables.product.prodname_dotcom %}. Para obtener más información sobre los riesgos de utilizar ejecutores auto-hospedados, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)". - -{% elsif ghae %} - -**Advertencia:** Los ejecutores auto-hospedados actualmente están inhabilitados para {% data variables.product.prodname_ghe_managed %}. Esto es porque {% data variables.product.prodname_ghe_managed %} ofrece garantías para los límites de seguridad, las cuales son incompatibles con la forma en que trabajan los ejecutores auto-hospedados. Sin embargo, en caso de que sí necesites utilizar ejecutores auto-hospedados con {% data variables.product.prodname_ghe_managed %} y entender las implicaciones de seguridad, puedes contactar al soporte de {% data variables.product.prodname_dotcom %} para que hagan una exepción de seguridad que los habilitará. - -Si no necesitas ejecutores auto-hospedados, entonces puedes utilizar {% data variables.actions.hosted_runner %} para que ejecuten tus flujos de trabajo. Para obtener más información, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)". - -{% endif %} +**Warning:** Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. Para obtener más información sobre los riesgos de utilizar ejecutores auto-hospedados, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)". For more information about the management of access to {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}, see "[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)." {% endwarning %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md b/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md index 4cc9f1d2eb..77cf1f0458 100644 --- a/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md +++ b/translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md @@ -2,7 +2,7 @@ {% note %} -**Nota:** Las {% data variables.product.prodname_actions %} en {% data variables.product.product_location %} podrían tener acceso limitado a las acciones en {% data variables.product.prodname_dotcom_the_website %} o en {% data variables.product.prodname_marketplace %}. 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)." +**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 %}. 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. {% endnote %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md index 9e5c719981..d7fd554d79 100644 --- a/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md +++ b/translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md @@ -1 +1 @@ -Las {% data variables.product.prodname_actions %} utilizan almacenamiento externo para almacenar artefactos de flujo de trabajo y bitácoras. Estos datos se almacenan en tu proveedor de almacenamiento externo, tal como Azure Blob Storage, Amazon S3 o MinIO. Como resultado, los respaldos de {% data variables.product.prodname_ghe_server %} y sus configuraciones de disponibilidad alta no proporcionan protección para los datos que se almacenan en este servicio externo y, en vez de esto, dependen de la protección de datos y replicación que proporciona el proveedor de almacenamiento externo, tal como Azure o AWS. +{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. diff --git a/translations/es-ES/data/reusables/actions/self-hosted-runners-software.md b/translations/es-ES/data/reusables/actions/self-hosted-runners-software.md new file mode 100644 index 0000000000..03bcfb0728 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/self-hosted-runners-software.md @@ -0,0 +1 @@ +You must install the required software on your self-hosted runners. For more information about self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)." diff --git a/translations/es-ES/data/reusables/advanced-security/license-overview.md b/translations/es-ES/data/reusables/advanced-security/license-overview.md index 3e5a8c9db2..2812d4cc53 100644 --- a/translations/es-ES/data/reusables/advanced-security/license-overview.md +++ b/translations/es-ES/data/reusables/advanced-security/license-overview.md @@ -1 +1,12 @@ -Cada licencia de {% data variables.product.prodname_GH_advanced_security %} especifica una cantidad máxima de cuentas o de plazas que pueden utilizar estas características. Cada confirmante activo en por lo menos un repositorio con la característica habilitada utilizará una plaza. Un confirmante activo es alguien que crea por lo menos una confirmación que se haya subido al repositorio en los últimos 90 días. +Cada licencia de {% data variables.product.prodname_GH_advanced_security %} especifica una cantidad máxima de cuentas o de plazas que pueden utilizar estas características. Cada confirmante activo en por lo menos un repositorio con la característica habilitada utilizará una plaza. A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored. + +{% note %} + +**Note:** Active committers are calculated using both the commit author information and the timestamp for when the code was pushed to {% data variables.product.product_name %}. + +- When a user pushes code to {% data variables.product.prodname_dotcom %}, every user who authored code in that push counts towards {% data variables.product.prodname_GH_advanced_security %} seats, even if the code is not new to {% data variables.product.prodname_dotcom %}. + +- Users should always create branches from a recent base, or rebase them before pushing. This will ensure that users who have not committed in the last 90 days do not take up {% data variables.product.prodname_GH_advanced_security %} seats. + +{% endnote %} + diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md index e4dd8be529..8669a6386e 100644 --- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md @@ -4,4 +4,4 @@ 1. Proporciona una secuencia de pruebas de muestra para asegurarte de que tu configuración empate con los patrones que esperas. ![Crear un formato de patrón personalizado del {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/secret-scanning-create-custom-pattern.png) -1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}. +1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}. diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md index 7859cac121..07bf614a03 100644 --- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md @@ -1 +1 @@ -1. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", debajo de "Patrones personalizados", haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next or ghec %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}. +1. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", debajo de "Patrones personalizados", haz clic en {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}. diff --git a/translations/es-ES/data/reusables/classroom/classroom-admins-link.md b/translations/es-ES/data/reusables/classroom/classroom-admins-link.md new file mode 100644 index 0000000000..238033da6d --- /dev/null +++ b/translations/es-ES/data/reusables/classroom/classroom-admins-link.md @@ -0,0 +1 @@ +For more information on classroom admins, see "[About management of classrooms](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms#about-management-of-classrooms)." \ No newline at end of file diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md b/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md index 091f3e931e..8ee0fc92dc 100644 --- a/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md +++ b/translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md @@ -1 +1 @@ -Puedes ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} dentro de {% data variables.product.product_name %} utilizando {% data variables.product.prodname_actions %}. Como alternativa, si utilizas un sistema de integración o despliegue/entrega contínua (IC/ID) de terceros, puedes ejecutar un análisis de {% data variables.product.prodname_codeql %} en tu sistema existente y cargar los resultados a {% data variables.product.product_location %}. +You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using {% data variables.product.prodname_actions %}. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}. diff --git a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md index 16b6594082..98bd06f5cb 100644 --- a/translations/es-ES/data/reusables/code-scanning/edit-workflow.md +++ b/translations/es-ES/data/reusables/code-scanning/edit-workflow.md @@ -1 +1 @@ -Habitualmente, no necesitas editar el flujo de trabajo predeterminado para {% data variables.product.prodname_code_scanning %}. Sin embargo, si lo requieres, puedes editar el flujo de trabajo para personalizar algunos de los ajustes. Por ejemplo, puedes editar el {% data variables.product.prodname_codeql_workflow %} de {% data variables.product.prodname_dotcom %} para especificar la frecuencia de los escaneos, los idiomas o los directorios a escanear, y qué debe buscar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} en tu código. También podrías necesitar editar el {% data variables.product.prodname_codeql_workflow %} si utilizas un conjunto de comandos específicos para compilar tu código. +Typically, you don't need to edit the default workflow for {% data variables.product.prodname_code_scanning %}. However, if required, you can edit the workflow to customize some of the settings. For example, you can edit {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql_workflow %} to specify the frequency of scans, the languages or directories to scan, and what {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} looks for in your code. You might also need to edit the {% data variables.product.prodname_codeql_workflow %} if you use a specific set of commands to compile your code. diff --git a/translations/es-ES/data/reusables/code-scanning/enabling-options.md b/translations/es-ES/data/reusables/code-scanning/enabling-options.md index 9fee080bae..ad4eded9d1 100644 --- a/translations/es-ES/data/reusables/code-scanning/enabling-options.md +++ b/translations/es-ES/data/reusables/code-scanning/enabling-options.md @@ -1,28 +1,8 @@ - - - - - - - - - - - - -
    - Tipo de análisis - - Opciones para generar alertas -
    - -
    -{%- ifversion fpt or ghes > 3.0 or ghae-next %} -| -{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)"). +| Type of analysis | Options for generating alerts | +|------------------|-------------------------------| +{%- ifversion fpt or ghes > 3.0 or ghae %} +| {% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)"). {%- else %} -| -{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)"). +| {% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)"). {%- endif %} -| Terceros | Utilizando -{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)").| +| Third‑party | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)").| diff --git a/translations/es-ES/data/reusables/code-scanning/licensing-note.md b/translations/es-ES/data/reusables/code-scanning/licensing-note.md index 4be164fb79..22e63b326f 100644 --- a/translations/es-ES/data/reusables/code-scanning/licensing-note.md +++ b/translations/es-ES/data/reusables/code-scanning/licensing-note.md @@ -1,7 +1,7 @@ {% note %} -**Nota:** {% ifversion fpt or ghec %} -El {% data variables.product.prodname_codeql_cli %} se puede usar gratuitamente en los repositorios públicos que se mantienen en {% data variables.product.prodname_dotcom_the_website %} y está disponible para utilizarse en los repositorios privados que pertenezcan a los clientes con una licencia de la {% 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 %}El {% data variables.product.prodname_codeql_cli %} se encuentra disponible para los clientes con una licencia de la {% data variables.product.prodname_advanced_security %}. +**Note:** {% ifversion fpt or ghec %} +The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. {% endif %} {% endnote %} diff --git a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md index 5b4083e896..e74bb3a820 100644 --- a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md +++ b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md @@ -1,20 +1,18 @@ -Cuando utilizas {% data variables.product.prodname_codeql %} para escanear código, el motor de análisis de {% data variables.product.prodname_codeql %} genera una base de datos desde el código y ejecuta consultas en éste. El {% data variables.product.prodname_codeql %} utiliza un conjunto predeterminado de consultas, pero puedes especificar más consultas para que se ejecuten, adicionalmente a las predeterminadas. +When you use {% data variables.product.prodname_codeql %} to scan code, the {% data variables.product.prodname_codeql %} analysis engine generates a database from the code and runs queries on it. {% data variables.product.prodname_codeql %} analysis uses a default set of queries, but you can specify more queries to run, in addition to the default queries. {% if codeql-packs %} -Puedes ejecutar consultas adicionales si son parte de un -paquete de {% data variables.product.prodname_codeql %} (beta) publicado en el {% data variables.product.prodname_container_registry %} de {% data variables.product.company_short %} o de un paquete de {% data variables.product.prodname_ql %} en un repositorio. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)". +You can run extra queries if they are part of a {% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." -Las opciones disponibles para especificar las consultas adicionales que quieres ejecutar son: +The options available to specify the additional queries you want to run are: -- `packs` para instalar uno o más paquetes de consulta de {% data variables.product.prodname_codeql %} (beta) y ejecutar la suite de consultas predeterminada para estos paquetes. -- `queries` para especificar un archivo sencilo de _.ql_, un directorio que contenga varios archivos de _.ql_, un archivo de definición de suite de consultas _.qls_ o cualquier combinación de estos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)". +- `packs` to install one or more {% data variables.product.prodname_codeql %} query packs (beta) and run the default query suite or queries for those packs. +- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)." -Puedes utilizar tanto `packs` como `queries` en el mismo flujo de trabajo. +You can use both `packs` and `queries` in the same workflow. {% else %} -Cualquier consulta adicional que quieras ejecutar debe pertenecer a un -paquete de {% data variables.product.prodname_ql %} en un repositorio. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)". +Any additional queries you want to run must belong to a {% data variables.product.prodname_ql %} pack in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." -Puedes especificar un solo archivo _.ql_, un directorio que contenga varios archivos _.ql_, un archivo de definición de suite de consulta _.qls_, o cualquier combinación de éstos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)". +You can specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)." {% endif %} -{% ifversion fpt or ghec %}No te recomendamos referenciar las suites de consultas directamente desde el repositorio de `github/codeql`, como por ejemplo `github/codeql/cpp/ql/src@main`. Puede que dichas consultas no se compilen con la misma versión de {% data variables.product.prodname_codeql %} que se utiliza para tus otras consultas, lo cual puede llevar a que se cometan errores durante el análisis.{% endif %} +{% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, like `github/codeql/cpp/ql/src@main`. Such queries may not be compiled with the same version of {% data variables.product.prodname_codeql %} as used for your other queries, which could lead to errors during analysis.{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md index a65b4e97ab..7b5e1aabf8 100644 --- a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,7 +1,7 @@ {% note %} **Notas:** -- La carga de SARIF es compatible con un máximo de {% ifversion ghae-next or fpt or ghes > 3.0 or ghec %}5000{% else %}1000{% endif %} resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes. +- La carga de SARIF es compatible con un máximo de {% ifversion ghae or fpt or ghes > 3.0 or ghec %}5000{% else %}1000{% endif %} resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes. - Para cada carga, la carga de SARIF es compatible con un tamaño máximo de 10 MB para el archivo comprimido de `gzip`. Cualquier carga que esté sobre este límite, se rechazará. Si tu archivo SARIF es demasiado grande porque contiene demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes. diff --git a/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md b/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md index 74f1e7755b..aaf643f0db 100644 --- a/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md +++ b/translations/es-ES/data/reusables/code-scanning/use-codeql-runner-not-cli.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} Si no es adecuado que utilices el {% data variables.product.prodname_codeql_cli %} para tu sistema de IC, como alternativa, está disponible el {% data variables.product.prodname_codeql_runner %}. Típicamente, esto se necesita si el sistema de IC necesitaría orquestrar invocaciones del compilador así como ejecutar un análisis de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system)". {% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md index 139214e8f0..d1c977333f 100644 --- a/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md +++ b/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md @@ -1,3 +1,3 @@ -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} El {% data variables.product.prodname_codeql_cli %} es un producto independiente que puedes utilizar para analizar código. Su propósito principal es generar una representación de base de datos de una base de código, una base de datos de {% data variables.product.prodname_codeql %}. Una vez que esté lista la base de datos, puedes consultarla interactivamente o ejecutar una suite de consultas para generar un conjunto de resultados en formato SARIF y cargarlos a {% data variables.product.product_location %}. {% endif %} diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-tos.md b/translations/es-ES/data/reusables/dependabot/dependabot-tos.md index a358938079..c22b0988af 100644 --- a/translations/es-ES/data/reusables/dependabot/dependabot-tos.md +++ b/translations/es-ES/data/reusables/dependabot/dependabot-tos.md @@ -1,5 +1,5 @@ {% ifversion fpt %} -En las [Condiciones de Servicio de {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-terms-of-service) se incluyen al {% data variables.product.prodname_dependabot %} y a todas sus características relacionadas. +{% data variables.product.prodname_dependabot %} and all related features are covered by [{% data variables.product.prodname_dotcom %}'s Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service). {% elsif ghec %} -Tu acuerdo de licencia cubre al {% data variables.product.prodname_dependabot %} y a todas las características relacionadas. Para obtener más información, consulta la sección "[Términos para clientes de {% data variables.product.company_short %} Enterprise](https://github.com/enterprise-legal)". +{% data variables.product.prodname_dependabot %} and all related features are covered by your license agreement. For more information, see "[{% data variables.product.company_short %} Enterprise Customer Terms](https://github.com/enterprise-legal)." {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md index 36e8e9c64a..8d633a04a6 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. Haz clic en la pestaña de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}**Ejecutores**{% else %}**Ejecutores auto-hospedados**{% endif %}. +1. Haz clic en la pestaña de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}**Ejecutores**{% else %}**Ejecutores auto-hospedados**{% endif %}. diff --git a/translations/es-ES/data/reusables/enterprise/navigate-to-log-streaming-tab.md b/translations/es-ES/data/reusables/enterprise/navigate-to-log-streaming-tab.md new file mode 100644 index 0000000000..b4d6f85f4e --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise/navigate-to-log-streaming-tab.md @@ -0,0 +1,4 @@ +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Haz clic en la pestaña de **Transmisión de bitácoras**. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md b/translations/es-ES/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md new file mode 100644 index 0000000000..37b1ab5120 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md @@ -0,0 +1 @@ +1. Verify the endpoint, then click **Save**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md b/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md index 51c91b94b1..c06f308925 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md +++ b/translations/es-ES/data/reusables/enterprise_installation/download-appliance.md @@ -1 +1 @@ -1. Haz clic en **Get the latest release of {% data variables.product.prodname_ghe_server %}** (Obtener el último lanzamiento del {% data variables.product.prodname_ghe_server %}). +1. Click **Get the latest release of {% data variables.product.prodname_ghe_server %}**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md b/translations/es-ES/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md new file mode 100644 index 0000000000..690abb634f --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_ghe_server %} supports PROXY Protocol V1, which is incompatible with AWS Network Load Balancers. If you use AWS Network Load Balancers with {% data variables.product.prodname_ghe_server %}, do not enable PROXY support. + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md b/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md index 7ea6837515..0c74592a2b 100644 --- a/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md +++ b/translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md @@ -1 +1 @@ -Un equipo que se encuentra [sincronizado a un grupo LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) se indica con una insignia de LDAP especial. La lista de miembros para un equipo de LDAP sincronizado únicamente se puede administrar desde el grupo LDAP al que está mapeado. +A team that's [synced to an LDAP group](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) is indicated with a special LDAP badge. The member list for an LDAP synced team can only be managed from the LDAP group it's mapped to. diff --git a/translations/es-ES/data/reusables/form-schema/options-syntax.md b/translations/es-ES/data/reusables/form-schema/options-syntax.md index e87310212b..0837b76ba1 100644 --- a/translations/es-ES/data/reusables/form-schema/options-syntax.md +++ b/translations/es-ES/data/reusables/form-schema/options-syntax.md @@ -1,5 +1,5 @@ Para cada valor en el arreglo de `options`, puedes configurar las siguientes claves. -| Clave | Descripción | Requerido | Type | Predeterminado | Opciones | +| Clave | Descripción | Requerido | Tipo | Predeterminado | Opciones | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | | `etiqueta` | El identificador para la opción, el cual se muestra en el formato. Hay compatibilidad con lenguaje de marcado para formateo de texto en itálicas o negritas y para los hipervínculos. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | diff --git a/translations/es-ES/data/reusables/gated-features/ghas.md b/translations/es-ES/data/reusables/gated-features/ghas.md index 0f74920694..060b70911a 100644 --- a/translations/es-ES/data/reusables/gated-features/ghas.md +++ b/translations/es-ES/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} +La {% data variables.product.prodname_GH_advanced_security %} se encuentra disponible para las cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %} 3.0 o superior.{% ifversion fpt or ghec %} La {% data variables.product.prodname_GH_advanced_security %} también se incluye en todos los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)".{% else %} Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" y refiérete al [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/packages.md b/translations/es-ES/data/reusables/gated-features/packages.md index 797b9cc52e..be454eea75 100644 --- a/translations/es-ES/data/reusables/gated-features/packages.md +++ b/translations/es-ES/data/reusables/gated-features/packages.md @@ -1,4 +1,4 @@ -{% data variables.product.prodname_registry %} 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 %} 3.0 or higher, and {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} +El {% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 3.0 o superior y {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)" y refiérete al [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.{% endif %} {% ifversion fpt or ghec %}
    {% data variables.product.prodname_registry %} no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. Las cuentas que utilicen los planes tradicionales por repositorio tampoco podrán acceder al {% data variables.product.prodname_container_registry %} ya que estas cuentas se facturan por repositorio. {% data reusables.gated-features.more-info %} diff --git a/translations/es-ES/data/reusables/gated-features/secret-scanning.md b/translations/es-ES/data/reusables/gated-features/secret-scanning.md index 3a91933dfb..f910931949 100644 --- a/translations/es-ES/data/reusables/gated-features/secret-scanning.md +++ b/translations/es-ES/data/reusables/gated-features/secret-scanning.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec %}El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible para todos los repositorios públicos y para los privados que pertenecen a organizaciones en donde se habilitó la {% data variables.product.prodname_GH_advanced_security %}. -{%- elsif ghes > 3.0 or ghae-next %}Las {% data variables.product.prodname_secret_scanning_caps %} están disponibles para los repositorios que pertenezcan a organizaciones en donde esté habilitada la {% data variables.product.prodname_GH_advanced_security %}. +{%- elsif ghes > 3.0 or ghae %}Las {% data variables.product.prodname_secret_scanning_caps %} están disponibles para los repositorios que pertenezcan a organizaciones en donde esté habilitada la {% data variables.product.prodname_GH_advanced_security %}. {%- elsif ghae %} El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible como parte de la {% data variables.product.prodname_GH_advanced_security %}, la cual es gratuita durante el lanzamiento beta. {%- else %} diff --git a/translations/es-ES/data/reusables/getting-started/marketplace.md b/translations/es-ES/data/reusables/getting-started/marketplace.md index 5283cdf6a7..31b86d2397 100644 --- a/translations/es-ES/data/reusables/getting-started/marketplace.md +++ b/translations/es-ES/data/reusables/getting-started/marketplace.md @@ -1 +1 @@ -{% data variables.product.prodname_marketplace %} contiene integraciones que agregan funcionalidad y mejoran tu flujo de trabajo. En [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), puedes descubrir, buscar e instalar herramientas gratuitas y de pago, incluyendo {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, y {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace)". +{% data variables.product.prodname_marketplace %} contains integrations that add functionality and improve your workflow. You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). For more information, see "[About {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace)." diff --git a/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md b/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md index 320cd7d9fd..816927b973 100644 --- a/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md +++ b/translations/es-ES/data/reusables/github-actions/artifact-log-retention-statement.md @@ -1 +1 @@ -Predeterminadamente, {% data variables.product.product_name %} almacena bitácoras de compilación y artefactos durante 90 días y este periodo de retención puede personalizarse. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)". +By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and this retention period can be customized.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/contacting-support.md b/translations/es-ES/data/reusables/github-actions/contacting-support.md index 9ba6a3389e..d4bcb7c776 100644 --- a/translations/es-ES/data/reusables/github-actions/contacting-support.md +++ b/translations/es-ES/data/reusables/github-actions/contacting-support.md @@ -1,9 +1,9 @@ -Si necesitas ayuda con lo que sea relacionado con la configuración de flujo de trabajo, tal como la sintaxis, los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, o la creación de acciones, busca un tema existente o inicia uno nuevo en la [categoría de {% data variables.product.prodname_actions %} de {% data variables.product.prodname_gcf %}](https://github.community/c/code-to-cloud/github-actions/41). +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). -Si tienes algún tipo de retroalimentación o solicitudes de características para {% data variables.product.prodname_actions %}, compártelas en el {% data variables.contact.contact_feedback_actions %}. +If you have feedback or feature requests for {% data variables.product.prodname_actions %}, share those in the {% data variables.contact.contact_feedback_actions %}. -Contacta a {% data variables.contact.contact_support %} para cualquiera de los siguientes, que tu tipo de uso o el tipo de uso que pretendes tener caiga en las siguientes categorías de limitación: +Contact {% data variables.contact.contact_support %} for any of the following, whether your use or intended use falls into the usage limit categories: -* Si crees que tu cuenta se ha restringido de manera incorrecta -* Si llegas un error inesperado cuando ejecutas una de tus acciones, por ejemplo: una ID única -* Si llegas a una situación en donde el comportamiento existente contradice a aquél que se espera, pero no siempre se documenta +* If you believe your account has been incorrectly restricted +* If you encounter an unexpected error when executing one of your Actions, for example: a unique ID +* If you encounter a situation where existing behavior contradicts expected, but not always documented, behavior diff --git a/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md b/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md index 3f5092e9ca..c5e42afc4f 100644 --- a/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md +++ b/translations/es-ES/data/reusables/github-actions/enabled-actions-description.md @@ -1 +1 @@ -When you enable {% data variables.product.prodname_actions %}, workflows are able to run actions located within your repository and any other{% ifversion fpt %} public{% elsif ghec or ghes %} public or internal{% elsif ghae %} internal{% endif %} repository. +Cuando habilitas las {% data variables.product.prodname_actions %}, los flujos de trabajo pueden ejecutar acciones que se ubiquen dentro de tu repositorio y en cualquier otro repositorio{% ifversion fpt %} público{% elsif ghec or ghes %} público o interno{% elsif ghae %} interno{% endif %}. diff --git a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md index 101a1a3d0e..8c23fd1fdb 100644 --- a/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md +++ b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md @@ -10,6 +10,7 @@ permissions: issues: read|write|none discussions: read|write|none packages: read|write|none + pages: read|write|none pull-requests: read|write|none repository-projects: read|write|none security-events: read|write|none diff --git a/translations/es-ES/data/reusables/github-actions/github-token-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-permissions.md index 5ffe1cbb78..a65beaf53a 100644 --- a/translations/es-ES/data/reusables/github-actions/github-token-permissions.md +++ b/translations/es-ES/data/reusables/github-actions/github-token-permissions.md @@ -1 +1 @@ -El secreto de `GITHUB_TOKEN` se configuro para un token de acceso para el repositorio cada vez que comienza un job en un flujo de trabajo. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}Debes configurar los permisos para este token de acceso en el archivo del flujo de trabajo para otorgar acceso de lectura para el alcance `contents` y acceso de escritura para el de `packages`. {% else %}Tiene permisos de lectura y escritura para los paquetes del repositorio en donde se ejecuta el flujo de trabajo. {% endif %}Para obtener más información, consulta la sección "[Autenticarte con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". +El secreto de `GITHUB_TOKEN` se configuro para un token de acceso para el repositorio cada vez que comienza un job en un flujo de trabajo. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Debes configurar los permisos para este token de acceso en el archivo del flujo de trabajo para otorgar acceso de lectura para el alcance `contents` y acceso de escritura para el de `packages`. {% else %}Tiene permisos de lectura y escritura para los paquetes del repositorio en donde se ejecuta el flujo de trabajo. {% endif %}Para obtener más información, consulta la sección "[Autenticarte con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". diff --git a/translations/es-ES/data/reusables/github-actions/hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/hosted-runner-navigate-to-repo-org-enterprise.md deleted file mode 100644 index c52cf043db..0000000000 --- a/translations/es-ES/data/reusables/github-actions/hosted-runner-navigate-to-repo-org-enterprise.md +++ /dev/null @@ -1,15 +0,0 @@ -1. Navega a donde está registrado tu {% data variables.actions.hosted_runner %}: - * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. - * **Si utilizas un ejecutor a nivel de empresa**: - - 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**. - 1. En la barra lateral de la cuenta de empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Policies** (Políticas). -1. Navega a los ajustes de {% data variables.product.prodname_actions %}: - * **En un repositorio de organización**: Haz clic en **Acciones** en la barra lateral izquierda. - - ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) - * **Si utilizas un ejecutor a nivel de empresa**: Debajo de "Políticas {% octicon "law" aria-label="The law icon" %}", haz clic en **Acciones**. - - ![Configuración de acciones](/assets/images/help/settings/actions-enterprise-policies.png) - diff --git a/translations/es-ES/data/reusables/github-actions/ip-allow-list-hosted-runners.md b/translations/es-ES/data/reusables/github-actions/ip-allow-list-hosted-runners.md deleted file mode 100644 index 48f22d58a8..0000000000 --- a/translations/es-ES/data/reusables/github-actions/ip-allow-list-hosted-runners.md +++ /dev/null @@ -1,3 +0,0 @@ -Para permitir que tus {% data variables.actions.hosted_runner %} se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus {% data variables.actions.hosted_runner %} a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)". - -Para obtener más información sobre los {% data variables.actions.hosted_runner %}, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/github-ae@latest/actions/using-github-hosted-runners/about-ae-hosted-runners)". diff --git a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md index 753300c299..ed15a5ea59 100644 --- a/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md +++ b/translations/es-ES/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md @@ -1,6 +1,6 @@ {% ifversion ghae %} -Para permitir que tus -{% data variables.actions.hosted_runner %} se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus {% data variables.actions.hosted_runner %} a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)". +Para permitir que tus ejecutores auto-hospedados se comuniquen con +{% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)". {% else %} {% warning %} diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md index 4ccf0b2a66..a3630e59cb 100644 --- a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md +++ b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md @@ -1,4 +1,4 @@ -Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories.{% ifversion ghec or ghes or ghae %} For enterprises, the policies are applied to all repositories in all organizations.{% endif %} +Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Disponible únicamente para los repositorios privados {% ifversion ghec or ghes or ghae %}e internos{% endif %}, puedes configurar estos ajustes de política para {% ifversion ghec %}empresas, {% elsif ghes or ghae %}tu empresa, {% endif %}organizaciones, o repositorios.{% ifversion ghec or ghes or ghae %}Para empresas, las políticas se aplcan a todos los repositorios en todas las organizaciones.{% endif %} - **Ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones** - permite a los usuarios ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones utilizando un `GITHUB_TOKEN` con permisos de solo lectura y sin acceso a los secretos. - **Enviar tokens de escritura a los flujos de trabajo desde las solicitudes de extracción** - Permite a las solicitudes de extracción de las bifuraciones utilizar un `GITHUB_TOKEN` con permiso de escritura. diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md index 83faa1f3f9..c5cc918fbe 100644 --- a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}La clave de `permissions` especifica el acceso otorgado al `GITHUB_TOKEN`.{% endif %} +Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso otorgado al `GITHUB_TOKEN`.{% endif %} 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 d2d8dbe1ee..78fd73c235 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 @@ -1,4 +1,4 @@ -1. En la sección de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"ejecutores"{% else %}"ejecutores auto-hospedados"{% endif %} de la página de ajustes, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecutores que te gustaría configurar y luego en **Editar el nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. En la sección de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"ejecutores"{% else %}"ejecutores auto-hospedados"{% endif %} de la página de ajustes, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecutores que te gustaría configurar y luego en **Editar el nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modifica tus opciones de política o cambia el nombre del grupo ejecutor. {% ifversion not ghae %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index 2a714dd952..085ae92c05 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -6,7 +6,7 @@ {% elsif ghec or ghes or ghae %} 1. Navega a donde se ubiquen tus grupos de ejecutores auto-hospedados: * **In an organization**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.{% ifversion ghec %} - * **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 ghes or ghae %} + * **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %} * **Si utilizas un ejecutor a nivel de empresa**: 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. 2. En la barra lateral izquierda, da clic en **Resumen empresarial**. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md index d948b07bb5..24de0e04b3 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md @@ -1,5 +1,5 @@ Para especificar un ejecutor auto-hospedado para tu trabajo, configura `runs-on` en tu archivo de flujo de trabajo con las etiquetas de dicho ejecutor. -Todos los ejecutores auto-hospedados tienen la etiqueta `self-hosted`. El utilizar únicamente esta etiqueta seleccionará cualquier ejecutor auto-hospedado. To select runners that meet certain criteria, such as operating system or architecture, we recommend providing an array of labels that begins with `self-hosted` (this must be listed first) and then includes additional labels as needed. When you specify an array of labels, jobs will be queued on runners that have all the labels that you specify. +Todos los ejecutores auto-hospedados tienen la etiqueta `self-hosted`. El utilizar únicamente esta etiqueta seleccionará cualquier ejecutor auto-hospedado. Para seleccionar los ejecutores que cumplen con ciertos criterios, tales como el sistema operativo o arquitectura, te recomendamos proporcionar un arreglo de etiquetas que comience con `self-hosted` (este se debe listar primero) y que luego incluya etiquetas adicionales conforme lo requieras. Cuando especifiques un arreglo de etiquetas, los jobs se pondrán en cola cuando se trate de ejecutores que tengan todas las etiquetas que especificas. -Although the `self-hosted` label is not required, we strongly recommend specifying it when using self-hosted runners to ensure that your job does not unintentionally specify any current or future {% data variables.product.prodname_dotcom %}-hosted runners. +Aunque la etiqueta de `self-hosted` no se requiere, te recomendamos ampliamente especificarla cuando utilices ejecutores auto-hospedados para garantizar que tu trabajo no especifique algún ejecutor hospedado en {% data variables.product.prodname_dotcom %} futuro o actual por accidente. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md index 7372ea0240..fbf869e5fd 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. Ubica la lista de ejecutores debajo de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}. + 1. Ubica la lista de ejecutores debajo de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md index d8348476c5..65ded479f7 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md @@ -6,12 +6,12 @@ {% elsif ghec or ghes or ghae %} 1. Navega a donde está registrado tu ejecutor auto-hospedado: * **En una organización**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. - * {% ifversion ghec %}**Si se utiliza una cuenta empresarial**: navega a tu cuenta visitando `https://github.com/enterprises/ENTERPRISE-NAME`, remplazando la parte de `ENTERPRISE-NAME` con tu nombre de cuenta empresarial.{% elsif ghes or ghae %}**Si utilizas un ejecutor a nivel empresarial**: + * {% ifversion ghec %}**If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}**If using an enterprise-level runner**: 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**. 1. In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 1. Navega a los ajustes de {% data variables.product.prodname_actions %}: - * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %} y luego en **Ejecutores**{% endif %}. - * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt or ghec or ghes > 3.1 or ghae-next %}, y luego en la pestaña de **Ejecutores** {% endif %}. + * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec or ghes > 3.1 or ghae %} y luego en **Ejecutores**{% endif %}. + * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt or ghec or ghes > 3.1 or ghae %}, y luego en la pestaña de **Ejecutores** {% endif %}. {% endif %} 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 35412e38f8..c8f28605ee 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 @@ -6,12 +6,12 @@ {% elsif ghec or ghes or ghae %} 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**. {% ifversion ghec %} - * **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 ghes or ghae %} + * **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %} * **Si utilizas un ejecutor a nivel de empresa**: 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. 2. En la barra lateral izquierda, da clic en **Resumen empresarial**. 3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 2. Navega a los ajustes de {% data variables.product.prodname_actions %}: - * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}, then click **Runners**{% endif %}.{% ifversion ghec or ghae or ghes %} - * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghes > 3.1 or ghae-next or ghec %}, then click the **Runners** tab{% endif %}.{% endif %} + * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, then click **Runners**{% endif %}.{% ifversion ghec or ghae or ghes %} + * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghes > 3.1 or ghae or ghec %}, then click the **Runners** tab{% endif %}.{% endif %} {% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index fe7dc99744..794a26ad6b 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Debajo de {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista. +1. Debajo de {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista. 1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al ejecutor que quieres eliminar, y luego da clic en **Eliminar**. ![Eliminar una configuración de ejecutor autoalojado](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 54a6af6358..8591d0ffe6 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. En la barra lateral izquierda, haz clic en **Acciones**.{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} +1. En la barra lateral izquierda, haz clic en **Acciones**.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 1. En la barra lateral izquierda, debajo de "Acciones"; haz clic en **Grupos ejecutores**.{% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md index dcc2e80609..4abb0ab1cf 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. En la barra lateral izquierda, haz clic en **Acciones**{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} y luego haz clic en **Ejecutores**{% endif %}. +1. En la barra lateral izquierda, haz clic en **Acciones**{% ifversion fpt or ghes > 3.1 or ghae or ghec %} y luego haz clic en **Ejecutores**{% endif %}. diff --git a/translations/es-ES/data/reusables/github-ae/saml-idp-table.md b/translations/es-ES/data/reusables/github-ae/saml-idp-table.md new file mode 100644 index 0000000000..db04f96ef7 --- /dev/null +++ b/translations/es-ES/data/reusables/github-ae/saml-idp-table.md @@ -0,0 +1,4 @@ +| IdP | SAML | Aprovisionamiento de usuarios | Team mapping | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} +| [Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label= "The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) | \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-connect/beta.md b/translations/es-ES/data/reusables/github-connect/beta.md index 38de9506c0..7abe1798db 100644 --- a/translations/es-ES/data/reusables/github-connect/beta.md +++ b/translations/es-ES/data/reusables/github-connect/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-next %} +{% ifversion ghae %} {% note %} **Nota:** {% data variables.product.prodname_github_connect %} para {% data variables.product.product_name %} se encuentra actualmente en beta y está sujeto a cambios. diff --git a/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md index 18a044ccbb..4dd41c844b 100644 --- a/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md +++ b/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -1 +1,2 @@ -1. Debajo de "Contributions" (Contribuciones), selecciona **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}** (Enviar mi recuento de contribuciones a {% data variables.product.prodname_dotcom_the_website %}), luego haz clic en **Update contributions** (Actualizar contribuciones). ![Casilla para enviar contribuciones y botón para actualizar contribuciones](/assets/images/help/settings/send-and-update-contributions.png) +1. Under "Contributions", select **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**, then click **Update contributions.** + ![Send contributions checkbox and update contributions button](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/es-ES/data/reusables/github-connect/sync-frequency.md b/translations/es-ES/data/reusables/github-connect/sync-frequency.md index 0057d0fdb2..0905f58853 100644 --- a/translations/es-ES/data/reusables/github-connect/sync-frequency.md +++ b/translations/es-ES/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.product_name %} envía actualizaciones cada hora. +{% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% elsif ghes or ghae %}{% data variables.product.product_name %}{% endif %} sends updates hourly. 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 18a4258c7a..2b6cb58ca4 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 @@ -1,4 +1,4 @@ -| Nombre | Type | Descripción | +| Nombre | Tipo | Descripción | | ------------------------ | ----------- | ----------------------------------------------------------------------------------------------------------------------------- | | `id` | `número` | El identificador único del evento. | | `node_id` | `secuencia` | La [ID de Nodo Global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) del evento. | 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 db56805fb3..da5e9656ae 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 @@ -5,7 +5,7 @@ - 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. Se enviará una notificación web cuando se habilite el {% data variables.product.prodname_dependabot %} en un repositorio cada que se confirme un archivo de manifiesto nuevo en dicho repositorio y cuando se encuentre una vulnerabilidad nueva con severidad crítica o alta (opción **Web**).{% ifversion not ghae %} -- en {% data variables.product.prodname_mobile %}, como notificaciones web. Para obtener más información, consulta la sección [Habilitar las notificaciones de subida con GitHub para dispositivos móviles](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)".{% endif %} +- en {% data variables.product.prodname_mobile %}, como notificaciones web. For more information, see "[Enabling push notifications with GitHub Mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %} {% note %} diff --git a/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md b/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md index 2921877ac6..e6a87294c4 100644 --- a/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md +++ b/translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md @@ -1,5 +1,5 @@ {% note %} -**Nota:** Cuando eliminas un usuario de la organización, sus datos de membresía se guardan durante tres meses. Si en el transcurso de ese tiempo invitas al usuario a que se vuelva a unir a la organización, puedes restaurar sus datos o cualquier bifurcación privada de tus repositorios de la organización que le haya pertenecido. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)". +**Note:** When you remove a user from your organization, their membership data is saved for three months. You can restore their data, or any private forks they owned of your organization's repositories, if you invite the user to rejoin the organization within that time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)." {% endnote %} diff --git a/translations/es-ES/data/reusables/organizations/organizations_include.md b/translations/es-ES/data/reusables/organizations/organizations_include.md index 728f14f7d4..a2fd3eb92b 100644 --- a/translations/es-ES/data/reusables/organizations/organizations_include.md +++ b/translations/es-ES/data/reusables/organizations/organizations_include.md @@ -3,7 +3,8 @@ Las organizaciones incluyen: - La capacidad de otorgarles a los miembros [un rango de permisos de acceso a los repositorios de la organización](/articles/repository-permission-levels-for-an-organization) - [Los elementos anidados que reflejan la estructura de tu grupo o compañía](/articles/about-teams) con permisos de acceso y menciones en cascada{% ifversion not ghae %} - La posibilidad de que los propietarios de la organización vean el [estado de autenticación de dos factores(2FA)](/articles/about-two-factor-authentication) de los miembros -- La opción de [requerir que todos los miembros de la organización utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +- The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}{% ifversion fpt%} +- The ability to [create and administer classrooms with GitHub Classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms){% endif %} {% ifversion fpt or ghec %} Puedes utilizar las organizaciones de forma gratuita con diff --git a/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md b/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md index 3d980144e1..c40d3a47ca 100644 --- a/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md +++ b/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md @@ -1,5 +1,5 @@ {%- ifversion ghae %} -1. In the `plugins` element of the *pom.xml* file, add the [checksum-maven-plugin](https://search.maven.org/artifact/net.nicoulaj.maven.plugins/checksum-maven-plugin) plugin, and configure the plugin to send at least SHA-256 checksums. +1. En el elemento `plugins` del archivo *pom.xml*, agrega el plugin [checksum-maven-plugin](https://search.maven.org/artifact/net.nicoulaj.maven.plugins/checksum-maven-plugin) y configúralo para enviar por lo menos comprobaciones SHA-256. ```xml diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md new file mode 100644 index 0000000000..9c09c5248f --- /dev/null +++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md @@ -0,0 +1,2 @@ +Once CI checks pass, {% data variables.product.product_name %} merges the pull request by fast-forwarding the default branch. The merge queue will use merge commits if the "Require linear history" branch protection setting is turned off, and the "Rebase and merge" method otherwise. + \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md index 9363401492..6e2a7cdd0f 100644 --- a/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md +++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md @@ -1,3 +1,5 @@ Merge queues for pull requests can increase the rate at which pull requests are merged into a busy default branch, whilst ensuring that CI checks pass. -Once a pull request has passed any required checks and approvals, a contributor can add the pull request to the merge queue. The queue then creates a temporary branch with that pull request and any pull requests ahead of it in the queue, and triggers any required continuous integration (CI) checks. Once CI checks pass, {% data variables.product.product_name %} merges the pull request by fast-forwarding the default branch. +Merge queues use {% data variables.product.prodname_actions %}. For more information about actions, see "[{% data variables.product.prodname_actions %}](/actions/)." + +Once a pull request has passed any required checks and approvals, a contributor with write access can add the pull request to the merge queue. The queue then creates a temporary branch with that pull request and any pull requests ahead of it in the queue, and triggers any required continuous integration (CI) checks. diff --git a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index 4ca6162bed..43fe7d3734 100644 --- a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -1,11 +1,11 @@ {% warning %} -**Advertencia:** +**Warning:** -- Si eliminas el acceso de una persona a un repositorio privado, todas sus bifurcaciones de ese repositorio privado se eliminarán. Los clones locales del repositorio privado se conservarán. Si se revoca el acceso de un equipo a un repositorio privado o se elimina un equipo con acceso a un repositorio privado, y los miembros del equipo no tienen acceso al repositorio a través de otro equipo, las bifurcaciones privadas del repositorio se eliminarán.{% ifversion ghes %} -- Cuando [LDAP Sync esté habilitado](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), si eliminas a una persona de un repositorio, perderá acceso, pero sus bifurcaciones no se eliminarán. Si la persona se agrega a un equipo con acceso al repositorio original de la organización dentro de los tres meses, su acceso a las bifurcaciones se restaurarán de manera automática la próxima vez que ocurra una sincronización.{% endif %} -- Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. +- If you remove a person’s access to a private repository, any of their forks of that private repository are deleted. Local clones of the private repository are retained. If a team's access to a private repository is revoked or a team with access to a private repository is deleted, and team members do not have access to the repository through another team, private forks of the repository will be deleted.{% ifversion ghes %} +- When [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync), if you remove a person from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.{% endif %} +- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- Las personas con permisos administrativos en un repositorio privado{% ifversion ghes or ghae or ghec %} o interno{% endif %} pueden dejar de permitir la bifurcación del mismo, y los propietarios de la organización pueden dejar de permitir la bifurcación de cualquier repositorio privado {% ifversion ghes or ghae or ghec %} o interno {% endif %} en una organización. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" y "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". +- People with admin permissions to a private{% ifversion ghes or ghae or ghec %} or internal{% endif %} repository can disallow forking of that repository, and organization owners can disallow forking of any private{% ifversion ghes or ghae or ghec %} or internal{% endif %} repository in an organization. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/es-ES/data/reusables/repositories/security-guidelines.md b/translations/es-ES/data/reusables/repositories/security-guidelines.md index 36c886960a..7aac715200 100644 --- a/translations/es-ES/data/reusables/repositories/security-guidelines.md +++ b/translations/es-ES/data/reusables/repositories/security-guidelines.md @@ -1,3 +1,3 @@ -{% ifversion fpt or ghes > 3.0 or ghae-next or ghec %} +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} Puedes crear una política de seguridad para dar instrucciones a las personas para reportar las vulnerabilidades de seguridad en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)". {% endif %} diff --git a/translations/es-ES/data/reusables/repositories/sidebar-issues.md b/translations/es-ES/data/reusables/repositories/sidebar-issues.md index 71e63b75b1..e17726b150 100644 --- a/translations/es-ES/data/reusables/repositories/sidebar-issues.md +++ b/translations/es-ES/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. Debajo del nombre de tu repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %} **Propuestas**. - {% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} + {% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Pestaña de informe de problemas](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/es-ES/data/reusables/repositories/sidebar-pr.md b/translations/es-ES/data/reusables/repositories/sidebar-pr.md index bb96953c5c..ec55c20498 100644 --- a/translations/es-ES/data/reusables/repositories/sidebar-pr.md +++ b/translations/es-ES/data/reusables/repositories/sidebar-pr.md @@ -2,6 +2,6 @@ {% octicon "git-pull-request" aria-label="The pull request icon" %} **Solicitudes de cambios**. {% ifversion fpt or ghec %} ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-tabs-pull-requests.png) - {% elsif ghes > 3.1 or ghae-next %} + {% elsif ghes > 3.1 or ghae %} ![Selección de pestañas en una solicitud de cambios](/assets/images/enterprise/3.3/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/es-ES/data/reusables/saml/external-group-audit-events.md b/translations/es-ES/data/reusables/saml/external-group-audit-events.md new file mode 100644 index 0000000000..0d8ec42f8d --- /dev/null +++ b/translations/es-ES/data/reusables/saml/external-group-audit-events.md @@ -0,0 +1,7 @@ +| Acción | Descripción | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `external_group.delete` | Triggered when your Okta group is deleted. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.link` | Triggered when your Okta group is mapped to your {% data variables.product.prodname_ghe_managed %} team. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.provision` | Triggered when an Okta group is mapped to your team on {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.unlink` | Triggered when your Okta group is unmapped from your {% data variables.product.prodname_ghe_managed %} team. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.update` | Triggered when your Okta group's settings are updated. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | \ No newline at end of file diff --git a/translations/es-ES/data/reusables/saml/external-identity-audit-events.md b/translations/es-ES/data/reusables/saml/external-identity-audit-events.md new file mode 100644 index 0000000000..74a3811926 --- /dev/null +++ b/translations/es-ES/data/reusables/saml/external-identity-audit-events.md @@ -0,0 +1,5 @@ +| Acción | Descripción | +| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `external_identity.deprovision` | Triggered when a user is removed from your Okta group and is subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_identity.provision` | Triggered when an Okta user is added to your Okta group and is subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_identity.update` | Triggered when an Okta user's settings are updated. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | \ No newline at end of file diff --git a/translations/es-ES/data/reusables/saml/okta-ae-applications-menu.md b/translations/es-ES/data/reusables/saml/okta-ae-applications-menu.md new file mode 100644 index 0000000000..e20691a67e --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-ae-applications-menu.md @@ -0,0 +1,3 @@ +1. In the Okta Dashboard, expand the **Applications** menu, then click **Applications**. + + !["Applications" menu navigation](/assets/images/help/saml/okta-ae-add-application.png) diff --git a/translations/es-ES/data/reusables/saml/okta-ae-configure-app.md b/translations/es-ES/data/reusables/saml/okta-ae-configure-app.md new file mode 100644 index 0000000000..ba304314fb --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-ae-configure-app.md @@ -0,0 +1,3 @@ +1. Click on the {% data variables.product.prodname_ghe_managed %} app. + + ![Configure app](/assets/images/help/saml/okta-ae-configure-app.png) diff --git a/translations/es-ES/data/reusables/saml/okta-ae-provisioning-tab.md b/translations/es-ES/data/reusables/saml/okta-ae-provisioning-tab.md new file mode 100644 index 0000000000..2a9267415a --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-ae-provisioning-tab.md @@ -0,0 +1,3 @@ +1. Da clic en **Aprovisionamiento**. + + ![Configure app](/assets/images/help/saml/okta-ae-provisioning-tab.png) diff --git a/translations/es-ES/data/reusables/saml/okta-ae-sso-beta.md b/translations/es-ES/data/reusables/saml/okta-ae-sso-beta.md new file mode 100644 index 0000000000..599020093b --- /dev/null +++ b/translations/es-ES/data/reusables/saml/okta-ae-sso-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_ghe_managed %} single sign-on (SSO) support for Okta is currently in beta. + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/saml/saml-supported-idps.md b/translations/es-ES/data/reusables/saml/saml-supported-idps.md index 26402d8793..6263ae9071 100644 --- a/translations/es-ES/data/reusables/saml/saml-supported-idps.md +++ b/translations/es-ES/data/reusables/saml/saml-supported-idps.md @@ -11,4 +11,5 @@ - Shibboleth {% elsif ghae %} - Azure Active Directory (Azure AD) +- Okta (beta) {% endif %} diff --git a/translations/es-ES/data/reusables/scim/supported-idps.md b/translations/es-ES/data/reusables/scim/supported-idps.md index 0d38f43b12..87ae59bdf0 100644 --- a/translations/es-ES/data/reusables/scim/supported-idps.md +++ b/translations/es-ES/data/reusables/scim/supported-idps.md @@ -2,4 +2,5 @@ Los siguientes IdP pueden aprovisionar o desaprovisionar las cuentas de usuario {% ifversion ghae %} - Azure AD +- Okta (currently in beta) {% endif %} diff --git a/translations/es-ES/data/reusables/secret-scanning/api-beta.md b/translations/es-ES/data/reusables/secret-scanning/api-beta.md index 5d810c67a5..5da9aeb454 100644 --- a/translations/es-ES/data/reusables/secret-scanning/api-beta.md +++ b/translations/es-ES/data/reusables/secret-scanning/api-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghes > 3.0 or ghae-next %} +{% ifversion ghes > 3.0 or ghae %} {% note %} 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 2302ab0642..bee4e10bce 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,31 +1,31 @@ | Proveedor | Secreto compatible | Slug de la API | | ----------- | ----------------------- | ----------------- | | Adafruit IO | Clave de IO de Adafruit | adafruit_io_key | -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Adobe | Token de Dispositivo de Adobe | adobe_device_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Adobe | Token de Servicio de Adobe | adobe_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Adobe | Token de Acceso de Duración Corta de Adobe | adobe_short_lived_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Adobe | Token Web JSON de Adobe | adobe_jwt{% endif %} Alibaba Cloud | ID de Llave de Acceso a Alibaba Cloud | alibaba_cloud_access_key_id Alibaba Cloud | Llave Secreta de Acceso a Alibaba Cloud | alibaba_cloud_access_key_secret Amazon Web Services (AWS) | ID de Llave de Acceso de Amazon AWS | aws_access_key_id Amazon Web Services (AWS) | Llave de Acceso Secreta de Amazon AWS | aws_secret_access_key {%- ifversion fpt or ghec or ghes > 3.2 %} Amazon Web Services (AWS) | Token de Sesión de Amazon AWS | aws_session_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS | aws_temporary_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Token de Acceso Personal de Asana | asana_personal_access_token{% endif %} Atlassian | Token de la API de Atlassian | atlassian_api_token Atlassian | Token Web JSON de Atlassian | atlassian_jwt -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Atlassian | Token de Acceso Personal al Servidor de Bitbucket | bitbucket_server_personal_access_token{% endif %} Azure | Token de Acceso Personal a Azure DevOps | azure_devops_personal_access_token Azure | Token SAS de Azure | azure_sas_token Azure | Certificado de Administración de Servicios de Azure | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Secuencia de Conexión SQL de Azure | azure_sql_connection_string{% endif %} Azure | Llave de Cuenta de Almacenamiento de Azure | azure_storage_account_key {%- ifversion fpt or ghec or ghes > 3.2 %} Beamer | Llave de la API de Beamer | beamer_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Llave de Secreto de Producción de Checkout.com | checkout_production_secret_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Llave Secreta de Pruebas de Checkout.com | checkout_test_secret_key{% endif %} Clojars | Token de Despliegue de Clojars | clojars_deploy_token -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | Credencial de CodeShip de CloudBees | codeship_credential{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} Contentful | Token de Acceso Personal a Contentful | contentful_personal_access_token{% endif %} Databricks | Token de Acceso a Databricks | databricks_access_token Discord | Token de Bot de Discord | discord_bot_token @@ -37,33 +37,33 @@ Doppler | Token de Servicio de Doppler | doppler_service_token{% endif %} Doppler | Token del CLI de Doppler | doppler_cli_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.0 or ghae %} Doppler | Token de SCIM de Doppler | doppler_scim_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Doppler | Token de Auditoría de Doppler | doppler_audit_token{% endif %} Dropbox | Token de Acceso a Dropbox | dropbox_access_token Dropbox | Token de Acceso de Vida Corta a Dropbox | dropbox_short_lived_access_token -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Duffel | Token de Acceso en Vivo de Duffel | duffel_live_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Duffel | Token de Acceso de Prueba de Duffel | duffel_test_access_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.0 or ghae %} Dynatrace | Token de Acceso a Dynatrace | dynatrace_access_token{% endif %} Dynatrace | Token Interno de Dynatrace | dynatrace_internal_token -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} EasyPost | Llave de la API de Producción de EasyPost | easypost_production_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} EasyPost | Llave de la API de Pruebas de EasyPost | easypost_test_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Fastly | Token de la API de Fastly | fastly_api_token{% endif %} Finicity | Llave de la App de Finicity | finicity_app_key -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Llave de Secreto de la API en Vivo de Flutterwave | flutterwave_live_api_secret_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Ññave Secreta de la API de Pruebas de Flutterwave | flutterwave_test_api_secret_key{% endif %} Frame.io | Token Web JSON de Frame.io | frameio_jwt Frame.io| Token de Desarrollador de Frame.io | frameio_developer_token {%- ifversion fpt or ghec or ghes > 3.2 %} FullStory | Llave de la API de FullStory | fullstory_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | Token de Acceso Personal de GitHub | github_personal_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | Token de Acceso de OAuth de GitHub | github_oauth_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | Token de Actualización de GitHub | github_refresh_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key {%- ifversion fpt or ghec or ghes > 3.3 %} GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token @@ -83,31 +83,31 @@ Google | ID de Cliente OAuth de Google | google_oauth_client_id{% endif %} Google | Secreto de Cliente OAuth de Google | google_oauth_client_secret{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 %} Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Grafana | Llave de la API de Grafana | grafana_api_key{% endif %} Hashicorp Terraform | API del Token de Terraform Cloud / Enterprise | terraform_api_token Hubspot | Llave de la API de Hubspot | hubspot_api_key -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Intercom | Token de Acceso a Intercom | intercom_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Ionic | Token de Acceso Personal de Ionic | ionic_personal_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Ionic | Token de Actualización de Ionic | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Llave de la API de Linear | linear_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Token de Acceso Oauth de Linear | linear_oauth_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Lob | Llave de la API en Vivo de Lob | lob_live_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Lob | Llave de la API de Pruebas de Lob | lob_test_api_key{% endif %} Mailchimp | Llave de la API de Mailchimp | mailchimp_api_key Mailgun | Llave de la API de Mailgun | mailgun_api_key {%- ifversion fpt or ghec or ghes > 3.3 %} Mapbox | Token de Acceso Secreto a Mapbox | mapbox_secret_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} MessageBird | Llave de la API de MessageBird | messagebird_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Meta | Token de Acceso a Facebook | facebook_access_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} New Relic | Llave Personal de la API de New Relic | new_relic_personal_api_key{% endif %} @@ -121,11 +121,11 @@ New Relic | Llave de Licencia de New Relic | new_relic_license_key{% endif %} Notion | Notion Integration Token | notion_integration_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 %} Notion | Notion OAuth Client Secret | notion_oauth_client_secret{% endif %} npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Onfido | Token de la API de Onfido Live | onfido_live_api_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Onfido | Token de la API de Onfido Sandbox | onfido_sandbox_api_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | Llave de la API de OpenAI | openai_api_key{% endif %} Palantir | Token Web JSON de Palantir | palantir_jwt {%- ifversion fpt or ghec or ghes > 3.2 %} PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password{% endif %} @@ -137,19 +137,19 @@ PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token{% end Plivo | ID de Auth de Plivo | plivo_auth_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} Plivo | Token de Autenticación a Plivo | plivo_auth_token{% endif %} Postman | Llave de la API de Postman | postman_api_key Proctorio | Llave de Consumidor de Proctorio | proctorio_consumer_key Proctorio | Llave de Vinculación de Proctorio | proctorio_linkage_key Proctorio | Llave de Registro de Proctorio | proctorio_registration_key Proctorio | Llave de Secreto de Proctorio | proctorio_secret_key Pulumi | Toekn de Acceso a Pulumi | pulumi_access_token -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | Token de la API de PyPI | pypi_api_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} RubyGems | Llave de la API de RubyGems | rubygems_api_key{% endif %} Samsara | Token de la API de Samsara | samsara_api_token Samsara | Token de Acceso OAuth a Samsara | samsara_oauth_access_token -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} SendGrid | Llave de la API de SendGrid | sendgrid_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} Sendinblue | Llave de la API de Sendinblue | sendinblue_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} Sendinblue | Llave de SMTP de Sendinblue | sendinblue_smtp_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Token de la API de Shippo Live | shippo_live_api_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Token de la API de Pruebas de Shippo | shippo_test_api_token{% endif %} Shopify | Secreto Compartido de la App de Shopify | shopify_app_shared_secret Shopify | Token de Acceso a Shopify | shopify_access_token Shopify | Token de Acceso a 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 del Webhook Entrante de Slack | slack_incoming_webhook_url Slack | URL del Webhook del Flujo de Trabajo de Slack | slack_workflow_webhook_url {%- ifversion fpt or ghec or ghes > 3.3 %} Square | Square Access Token | square_access_token{% endif %} @@ -165,12 +165,12 @@ Stripe | Llave Secreta de la API de Prueba de Stripe | stripe_test_secret_key{% Stripe | Llave Restringida de la API en Vivo de Stripe | stripe_live_restricted_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.0 or ghae %} Stripe | Llave Restringida de la API de Prueba de Stripe | stripe_test_restricted_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Stripe | Secreto de Firmado de Webhook de Stripe | stripe_webhook_signing_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} {%- ifversion fpt or ghec or ghes > 3.3 %} Supabase | Supabase Service Key | supabase_service_key{% endif %} Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.1 or ghae-next %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Telegram | Token del Bot de Telegram | telegram_bot_token{% endif %} Tencent Cloud | ID Secreta de Tencent Cloud | tencent_cloud_secret_id {%- ifversion fpt or ghec or ghes > 3.3 %} Twilio | Token de Acceso a Twilio | twilio_access_token{% endif %} Twilio | Identificador de Secuencia de Cuenta de Twilio | twilio_account_sid Twilio | Llave de la API de Twilio | twilio_api_key diff --git a/translations/es-ES/data/reusables/stars/stars-page-navigation.md b/translations/es-ES/data/reusables/stars/stars-page-navigation.md new file mode 100644 index 0000000000..ce25909848 --- /dev/null +++ b/translations/es-ES/data/reusables/stars/stars-page-navigation.md @@ -0,0 +1 @@ +1. In the upper-right corner of any page, click your profile photo, then click ** Your stars**. ![Screenshot of stars option in a dropdown menu](/assets/images/help/stars/navigate-to-stars-page.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md index f0a72851b4..78729722f4 100644 --- a/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md +++ b/translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md @@ -1,5 +1,5 @@ -{% data variables.contact.enterprise_support %} podría considerar a un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, {% ifversion ghae %}o {% endif %} instrucciones de solución alternativa{% ifversion ghes %}, o recomendándote un lanzamiento disponible que trate el problema{% endif %}. +{% data variables.contact.enterprise_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, {% ifversion ghae %}or {% endif %} workaround instructions{% ifversion ghes %}, or by advising you of an available release that addresses the issue{% endif %}. -Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.enterprise_support %} puede pedirte que elimines complementos, módulos o códigos no compatibles al intentar resolver el problema. Si el problema se arregla cuando el plug-in, módulo, o código personalizado no compatibles se eliminan, {% data variables.contact.enterprise_support %} podría considerar el ticket como resuelto. +If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.enterprise_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.enterprise_support %} may consider the ticket solved. -{% data variables.contact.enterprise_support %} podría cerrar un ticket si éste está fuera de su alcance o si han habido varios intentos para contactarte sin éxito. Si {% data variables.contact.enterprise_support %} cierra un ticket por falta de respuesta, puedes solicitar que lo vuelva a abrir. +{% data variables.contact.enterprise_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.enterprise_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.enterprise_support %} reopen the ticket. diff --git a/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md index bda2be6cf1..01055b4e78 100644 --- a/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md +++ b/translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md @@ -1,5 +1,5 @@ -{% data variables.contact.premium_support %} podría considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, instrucciones de solución alternativa, o recomendándote un lanzamiento disponible que trata el problema. +{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available release that addresses the issue. -Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.premium_support %} puede pedirte que elimines el complemento, el módulo o el código no compatible mientras intentas resolver el problema. {% data variables.contact.premium_support %} puede considerar el ticket como resuelto si el problema se soluciona cuando se elimina el plug-in, módulo, o código personalizado no compatible. +If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.premium_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.premium_support %} may consider the ticket solved. -{% data variables.contact.premium_support %} podría cerrar un ticket si éste está fuera de su alcance o si han habido varios intentos para contactarte sin éxito. Si {% data variables.contact.premium_support %} cierra un ticket por no haber recibido respuesta, puedes solicitar que lo reabra. +{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.premium_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.premium_support %} reopen the ticket. diff --git a/translations/es-ES/data/reusables/supported-languages/python.md b/translations/es-ES/data/reusables/supported-languages/python.md index 1427723cc8..2bf98383ae 100644 --- a/translations/es-ES/data/reusables/supported-languages/python.md +++ b/translations/es-ES/data/reusables/supported-languages/python.md @@ -1 +1 @@ -| Python |{% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
    pip | {% octicon "check" aria-label="The check icon" %}
    pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
    pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
    pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} +| Python |{% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %}
    precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
    pip | {% octicon "check" aria-label="The check icon" %}
    pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
    pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
    pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 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 71988ac64e..12015b12b4 100644 --- a/translations/es-ES/data/reusables/webhooks/check_run_properties.md +++ b/translations/es-ES/data/reusables/webhooks/check_run_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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` | `objeto` | La [check_run](/rest/reference/checks#get-a-check-run). | 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 300c2d99e0..7224ad2b90 100644 --- a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md +++ b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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` | `objeto` | La [check_suite](/rest/reference/checks#suites). | 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 1e3bdf23c5..e39bbc74d2 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,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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`. | | `alerta` | `objeto` | La alerta de escaneo de código involucrada en el evento. | 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 5a09adfbf2..9fb6e5f95a 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 | +| Clave | Tipo | 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 e64b3ca05e..f0c5ada8a5 100644 --- a/translations/es-ES/data/reusables/webhooks/create_properties.md +++ b/translations/es-ES/data/reusables/webhooks/create_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | --------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | `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`. | diff --git a/translations/es-ES/data/reusables/webhooks/delete_properties.md b/translations/es-ES/data/reusables/webhooks/delete_properties.md index 727ad32af7..6e92c7eed9 100644 --- a/translations/es-ES/data/reusables/webhooks/delete_properties.md +++ b/translations/es-ES/data/reusables/webhooks/delete_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | ---------- | ----------- | ---------------------------------------------------------------------------------------- | | `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 borró en el repositorio. Puede ser `branch` o `tag`. | 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 d1e29d86b4..01db75f554 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 | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`. | | `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 a00605b049..731ec88d0c 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 | +| Clave | Tipo | Descripción | | -------- | -------- | --------------------------------------------------------------------------------- | | `forkee` | `objeto` | El recurso de [`repository`](/rest/reference/repos#get-a-repository) que se creó. | diff --git a/translations/es-ES/data/reusables/webhooks/gollum_properties.md b/translations/es-ES/data/reusables/webhooks/gollum_properties.md index 98ca0e4bf3..39a7756aae 100644 --- a/translations/es-ES/data/reusables/webhooks/gollum_properties.md +++ b/translations/es-ES/data/reusables/webhooks/gollum_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------------------- | ----------- | ---------------------------------------------------------------------- | | `páginas` | `arreglo` | Las páginas que se actualizaron. | | `pages[][page_name]` | `secuencia` | El nombre de la página. | diff --git a/translations/es-ES/data/reusables/webhooks/installation_properties.md b/translations/es-ES/data/reusables/webhooks/installation_properties.md index 913f410ce2..2746802fde 100644 --- a/translations/es-ES/data/reusables/webhooks/installation_properties.md +++ b/translations/es-ES/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------------- | ----------- | ----------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `created` - Alguien instala una {% data variables.product.prodname_github_app %}.
    • `deleted` - Alguien desinstala una {% data variables.product.prodname_github_app %}
      • {% ifversion fpt or ghes or ghae or ghec %}
    • `suspend` - alguien suspende la instalación de una {% data variables.product.prodname_github_app %}.
    • `unsuspend` - Alguien deja de suspender una instalación de {% data variables.product.prodname_github_app %}.
      • {% endif %}
    • `new_permissions_accepted` - Alguien acepta permisos nuevos para una instalación de {% data variables.product.prodname_github_app %}. Cuando un propietario de una {% data variables.product.prodname_github_app %} solcita permisos nuevos, la persona que instaló dicha {% data variables.product.prodname_github_app %} debe aceptar la solicitud de estos permisos nuevos.
    | | `repositories` | `arreglo` | Un areglo de objetos de repositorio al que puede acceder la instalación. | diff --git a/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md b/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md index ecbe522cdb..7adfdfa19f 100644 --- a/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md +++ b/translations/es-ES/data/reusables/webhooks/installation_repositories_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser tanto `added` como `removed`. | | `repository_selection` | `secuencia` | La elección de repositorios en los cuales se encuentra la instalación. Puede ser tanto `selected` como `all`. | diff --git a/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md index 517915c39f..4f1f637743 100644 --- a/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/issue_comment_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | -------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. | diff --git a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md index 42e5ad095f..f912fa2c38 100644 --- a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md +++ b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, o `unlabeled`. | diff --git a/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md index 0b69e0fa29..0d42edcd07 100644 --- a/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/issue_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `deleted`, `pinned`, `unpinned`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, `unlabeled`, `locked`, `unlocked`, `transferred`, `milestoned`, o `demilestoned`. | diff --git a/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md index 46d749a875..90cbcc889b 100644 --- a/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md +++ b/translations/es-ES/data/reusables/webhooks/member_event_api_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ---------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `added` para indicar que un usuario aceptó una invitación al repositorio. | diff --git a/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md index ff479a4024..5936ddb985 100644 --- a/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/member_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ----------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `added` - Un usuario acepta una invitación a un repositorio.
    • `removed` - Se elimina a un usuario como colaborador de un repositorio.
    • `edited` - Han cambiado los permisos de colaborador de un usuario.
    | diff --git a/translations/es-ES/data/reusables/webhooks/membership_properties.md b/translations/es-ES/data/reusables/webhooks/membership_properties.md index eb5e6b565c..5284292644 100644 --- a/translations/es-ES/data/reusables/webhooks/membership_properties.md +++ b/translations/es-ES/data/reusables/webhooks/membership_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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`. | diff --git a/translations/es-ES/data/reusables/webhooks/milestone_properties.md b/translations/es-ES/data/reusables/webhooks/milestone_properties.md index e875f5bc69..292021c0ec 100644 --- a/translations/es-ES/data/reusables/webhooks/milestone_properties.md +++ b/translations/es-ES/data/reusables/webhooks/milestone_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | ---------------------------- | ----------- | ------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre: `created`, `closed`, `opened`, `edited`, o `deleted`. | | `hito` | `objeto` | El hito mismo. | diff --git a/translations/es-ES/data/reusables/webhooks/package_properties.md b/translations/es-ES/data/reusables/webhooks/package_properties.md index 0ed44ec297..3cd2722195 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 | +| Clave | Tipo | Descripción | | --------- | ----------- | ------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Puede ser `published` o `updated`. | | `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 d094490cdb..47dcc76361 100644 --- a/translations/es-ES/data/reusables/webhooks/project_card_properties.md +++ b/translations/es-ES/data/reusables/webhooks/project_card_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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` | `objeto` | Los cambios a la tarjeta del proyecto si la acción se puso como `edited` o `converted`. | 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 fba0041ffb..b21c652122 100644 --- a/translations/es-ES/data/reusables/webhooks/project_column_properties.md +++ b/translations/es-ES/data/reusables/webhooks/project_column_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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` | `objeto` | Los cambios a la columna del proyecto si la acción se puso como `edited`. | diff --git a/translations/es-ES/data/reusables/webhooks/project_properties.md b/translations/es-ES/data/reusables/webhooks/project_properties.md index 41f15ed400..d6132e30b3 100644 --- a/translations/es-ES/data/reusables/webhooks/project_properties.md +++ b/translations/es-ES/data/reusables/webhooks/project_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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` | `objeto` | Los cambios al proyecto si la acción se puso como `edited`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md index 03fe366d0b..21e7eb30eb 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, y `synchronize`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md index 108cda8365..193c77ca4a 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | --------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`. | diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md index 517915c39f..4f1f637743 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | -------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. | 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 8505fcdce2..bbd73c9214 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,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | 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` | `objeto` | La [solicitud de extracción](/rest/reference/pulls) a la cual pertenece la revisión. | 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 5a1ed8c18f..8d62c7db5b 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 | +| Clave | Tipo | Descripción | | -------- | ----------- | ----------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `assigned`
      • {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
    • `auto_merge_disabled`
    • `auto_merge_enabled`
      • {% endif %}
    • `closed`: Si la acción se muestra como `closed` y la clave `merged` está como `false`, la solicitud de cambios se cerró con confimraciones sin fusionar. Si la acción está `closed` y la clave que está como `merged` está en `true`, la solicitud de cambios se fusionó.
    • `converted_to_draft`
    • `edited`
    • `labeled`
    • `locked`
    • `opened`
    • `ready_for_review`
    • `reopened`
    • `review_request_removed`
    • `review_requested`
    • `synchronize`: Se activa cuando se actualiza la rama de encabezado de una solicitud de cambios. Por ejemplo, cuando se actualiza la rama de encabezado desde la rama base, cuando las confirmaciones nuevas se suben a la rama de encabezado o cuando se cambia la rama de encabezado.
    • `unassigned`
    • `unlabeled`
    • `unlocked`
    | diff --git a/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md index 32e6fa2985..9c534eafd7 100644 --- a/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md +++ b/translations/es-ES/data/reusables/webhooks/release_event_api_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | --------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `published`. | diff --git a/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md index fff2412103..a66281e74b 100644 --- a/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/release_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `published`: se publica un lanzamiento, pre-lanzamiento, o borrador de un lanzamiento
    • `unpublished`: se borra un lanzamiento o pre-lanzamiento
    • `created`: se guarda un borrador, o se publica un lanzamiento o pre-lanzamiento sin que se haya guardado previamente como un borrador
    • `edited`: se edita un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
    • `deleted`: se borra un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
    • `prereleased`: se crea un pre-lanzamiento
    • `released`: se publica un lanzamiento o borrador de un lanzamiento, o se cambia un prelanzamiento a lanzamiento
      • | 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 b695be300b..0eadefb117 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 | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------------------- | | `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 62f800c9ca..206f353fb0 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 | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Este puede ser alguno de entre: `create`, `dismiss`, o `resolve`. | | `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 8c9ab1fa16..f05b41ec01 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 | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción que se realizó. Esta puede ser ya sea `created`, `resolved`, o `reopened`. | | `alerta` | `objeto` | La alerta del escaneo de secretos involucrada en el evento. | diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md index 178dc2e34d..28458c3853 100644 --- a/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md +++ b/translations/es-ES/data/reusables/webhooks/sponsorship_event_api_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ---------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`. | diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md index 7b747286ea..cbdd521f07 100644 --- a/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/sponsorship_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de entre: `created`, `cancelled`, `edited`, `tier_changed`, `pending_cancellation`, o `pending_tier_change`. Nota: La acción `created` solo se activa después de que se procesa un pago. | diff --git a/translations/es-ES/data/reusables/webhooks/star_properties.md b/translations/es-ES/data/reusables/webhooks/star_properties.md index 634104251a..a80dd2a379 100644 --- a/translations/es-ES/data/reusables/webhooks/star_properties.md +++ b/translations/es-ES/data/reusables/webhooks/star_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | ------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción realizada. Puede ser `created` o `deleted`. | | `starred_at` | `secuencia` | La hora en la cual se creó un marcado con estrella. {% data reusables.shortdesc.iso_8601 %} Será `null` para las acciones que estén como `deleted`. | diff --git a/translations/es-ES/data/reusables/webhooks/watch_properties.md b/translations/es-ES/data/reusables/webhooks/watch_properties.md index 21b3643e64..b3930bbc65 100644 --- a/translations/es-ES/data/reusables/webhooks/watch_properties.md +++ b/translations/es-ES/data/reusables/webhooks/watch_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------- | ----------- | ---------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Acutalmente, solo puede ser `started`. | diff --git a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md index 1a54bff9f7..3d9ee845ac 100644 --- a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md +++ b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | --------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
      • `queued` - Se creó un job nuevo.
      • `in_progress` - El job se comenzó a procesar en el ejecutor.
      • `completed` - el `status` del job es `completed`.
      | | `workflow_job` | `objeto` | El job de flujo de trabajo. Muchas claves de `workflow_job`, tales como `head_sha`, `conclusion`, y `started_at` son las mismas que aquellas en un objeto [`check_run`](#check_run). | diff --git a/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md b/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md index 39bec3188e..52f531e154 100644 --- a/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md +++ b/translations/es-ES/data/reusables/webhooks/workflow_run_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | +| Clave | Tipo | Descripción | | -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `requested` o `completed`. | | `workflow_run` | `objeto` | La ejecución del flujo de trabajo. Muchas claves de `workflow_run`, tales como `head_branch`, `conclusion`, y `pull_requests` son las mismas que aquellas en un objeto [`check_suite`](#check_suite). | diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml index e33e7fe7f2..fdb24cf77b 100644 --- a/translations/es-ES/data/ui.yml +++ b/translations/es-ES/data/ui.yml @@ -14,8 +14,7 @@ header: ghes_release_notes_upgrade_release_only: '📣 Este no es el lanzamiento más reciente de Enterprise Server.' ghes_release_notes_upgrade_patch_and_release: '📣 Este no es el lanzamiento de parche más reciente de esta serie de lanzamientos, y no es elúltimo lanzamiento de Enterprise Server.' release_notes: - banner_text_current: Estos cam bios se implementarán en la siguiente semana. - banner_text_past: Estos cambios se implementarán en las empresas durante la semana de + banner_text: GitHub comenzó a implementar estos cambios en empresas en search: need_help: '¿Necesitas ayuda?' placeholder: Busca temas, productos... @@ -70,7 +69,7 @@ products: fields: Campos arguments: Argumentos name: Nombre - type: Type + type: Tipo description: Descripción input_fields: Campos de entrada return_fields: Campos de retorno @@ -161,7 +160,7 @@ product_guides: all_guides: 'Todas las guías de {{ productMap[currentProduct].name }}' filter_instructions: Filtra la lista de guías utilizando estos controles filters: - type: Type + type: Tipo topic: Tema all: Todas guides_found: diff --git a/translations/es-ES/data/variables/actions.yml b/translations/es-ES/data/variables/actions.yml index 86968e6229..4fa0661763 100644 --- a/translations/es-ES/data/variables/actions.yml +++ b/translations/es-ES/data/variables/actions.yml @@ -1,3 +1,2 @@ --- -hosted_runner: 'Ejecutor hospedado en AE' azure_portal: 'Portal de Azure' diff --git a/translations/es-ES/data/variables/enterprise.yml b/translations/es-ES/data/variables/enterprise.yml index 2757a36221..f48e897988 100644 --- a/translations/es-ES/data/variables/enterprise.yml +++ b/translations/es-ES/data/variables/enterprise.yml @@ -1,4 +1,4 @@ --- management_console: 'Consola de administración' #https://support.github.com/enterprise/server-upgrade -upgrade_assistant: 'Upgrade assistant' +upgrade_assistant: 'Asistente de mejora' diff --git a/translations/es-ES/data/variables/gists.yml b/translations/es-ES/data/variables/gists.yml index 2973c08309..ad196f4396 100644 --- a/translations/es-ES/data/variables/gists.yml +++ b/translations/es-ES/data/variables/gists.yml @@ -1,7 +1,7 @@ --- gist_homepage: >- - {% ifversion fpt or ghec %}[gist home page](https://gist.github.com/){% elsif ghae %}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 %} + {% ifversion fpt or ghec %}[página de inicio de gist](https://gist.github.com/){% elsif ghae %}página de inicio de gist, `http(s)://gist.[hostname]`{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` si se habilitaron los subdominios{% endif %} gist_search_url: >- - {% ifversion fpt or ghec %}[Gist Search](https://gist.github.com/search){% elsif ghae %}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 %} + {% ifversion fpt or ghec %}[Búsqueda de Gists](https://gist.github.com/search){% elsif ghae %}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: >- - {% ifversion fpt or ghec %}[Discover](https://gist.github.com/discover){% elsif ghae %}Discover, `http(s)://gist.[hostname]/discover`{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %} + {% ifversion fpt or ghec %}[Discover](https://gist.github.com/discover){% elsif ghae %}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 1749ca6ab8..8f5edae6a8 100644 --- a/translations/es-ES/data/variables/product.yml +++ b/translations/es-ES/data/variables/product.yml @@ -46,8 +46,8 @@ prodname_cli: 'CLI de GitHub' #GitHub Desktop prodname_desktop: 'GitHub Desktop' desktop_link: 'https://desktop.github.com/' -#GitHub for Mobile -prodname_mobile: 'GitHub para móviles' +#GitHub Mobile +prodname_mobile: 'GitHub Mobile' prodname_ios: 'GitHub para iOS' prodname_android: 'GitHub para Android' #GitHub Pages diff --git a/translations/es-ES/data/variables/release_candidate.yml b/translations/es-ES/data/variables/release_candidate.yml index 361ba6ba63..ec65ef6f94 100644 --- a/translations/es-ES/data/variables/release_candidate.yml +++ b/translations/es-ES/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.3 +version: '' diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv index dc53402601..c017a692dd 100644 --- a/translations/log/es-resets.csv +++ b/translations/log/es-resets.csv @@ -1,22 +1,37 @@ file,reason +translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error +translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error +translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error +translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error +translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,rendering error @@ -29,27 +44,54 @@ translations/es-ES/content/account-and-profile/setting-up-and-managing-your-gith translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error +translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error +translations/es-ES/content/actions/advanced-guides/index.md,rendering error translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,Listed in localization-support#489 translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error +translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md,rendering error translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,rendering error translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md,rendering error translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,Listed in localization-support#489 translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,rendering error translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,Listed in localization-support#489 translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md,rendering error +translations/es-ES/content/actions/automating-builds-and-tests/index.md,rendering error +translations/es-ES/content/actions/creating-actions/about-custom-actions.md,rendering error +translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md,rendering error translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,Listed in localization-support#489 translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md,rendering error +translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md,rendering error +translations/es-ES/content/actions/creating-actions/index.md,rendering error translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md,rendering error +translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md,rendering error translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error +translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error translations/es-ES/content/actions/deployment/about-deployments/index.md,Listed in localization-support#489 translations/es-ES/content/actions/deployment/about-deployments/index.md,rendering error +translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error +translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service.md,rendering error +translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md,Listed in localization-support#489 translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error +translations/es-ES/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error +translations/es-ES/content/actions/deployment/index.md,rendering error translations/es-ES/content/actions/deployment/managing-your-deployments/index.md,Listed in localization-support#489 translations/es-ES/content/actions/deployment/managing-your-deployments/index.md,rendering error +translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,Listed in localization-support#489 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,rendering error translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,Listed in localization-support#489 @@ -69,11 +111,15 @@ translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-r translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,Listed in localization-support#489 translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error +translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,rendering error +translations/es-ES/content/actions/hosting-your-own-runners/index.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489 translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error +translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error +translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error translations/es-ES/content/actions/index.md,Listed in localization-support#489 translations/es-ES/content/actions/index.md,rendering error translations/es-ES/content/actions/learn-github-actions/contexts.md,Listed in localization-support#489 @@ -81,38 +127,79 @@ translations/es-ES/content/actions/learn-github-actions/contexts.md,rendering er translations/es-ES/content/actions/learn-github-actions/creating-workflow-templates.md,rendering error translations/es-ES/content/actions/learn-github-actions/environment-variables.md,Listed in localization-support#489 translations/es-ES/content/actions/learn-github-actions/environment-variables.md,rendering error +translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md,rendering error translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md,Listed in localization-support#489 translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md,rendering error translations/es-ES/content/actions/learn-github-actions/expressions.md,rendering error translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error +translations/es-ES/content/actions/learn-github-actions/index.md,rendering error +translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md,rendering error translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md,rendering error +translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md,rendering error translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error +translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md,rendering error translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,Listed in localization-support#489 translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,rendering error translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,Listed in localization-support#489 translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md,rendering error +translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md,rendering error translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,rendering error +translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md,rendering error +translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md,rendering error +translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md,rendering error +translations/es-ES/content/actions/managing-workflow-runs/index.md,rendering error translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,Listed in localization-support#489 translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error +translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error +translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md,rendering error +translations/es-ES/content/actions/migrating-to-github-actions/index.md,rendering error +translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md,rendering error +translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md,rendering error +translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md,rendering error +translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md,rendering error +translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md,rendering error translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md,rendering error translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error +translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md,rendering error +translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error +translations/es-ES/content/actions/publishing-packages/index.md,rendering error translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md,rendering error translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md,rendering error +translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md,rendering error translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error translations/es-ES/content/actions/quickstart.md,Listed in localization-support#489 translations/es-ES/content/actions/quickstart.md,rendering error translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,Listed in localization-support#489 translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,rendering error +translations/es-ES/content/actions/security-guides/encrypted-secrets.md,rendering error +translations/es-ES/content/actions/security-guides/index.md,rendering error translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error -translations/es-ES/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md,rendering error +translations/es-ES/content/actions/using-containerized-services/about-service-containers.md,rendering error +translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md,rendering error +translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md,rendering error +translations/es-ES/content/actions/using-containerized-services/index.md,rendering error translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,Listed in localization-support#489 translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,Listed in localization-support#489 translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,rendering error +translations/es-ES/content/actions/using-github-hosted-runners/index.md,rendering error translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,rendering error translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md,Listed in localization-support#489 @@ -121,19 +208,29 @@ translations/es-ES/content/admin/advanced-security/enabling-github-advanced-secu translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,rendering error translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md,rendering error translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error +translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,Listed in localization-support#489 translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error +translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error +translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error +translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error translations/es-ES/content/admin/authentication/index.md,rendering error +translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md,rendering error +translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error +translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,rendering error translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error +translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md,rendering error +translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error +translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md,rendering error translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error @@ -141,12 +238,14 @@ translations/es-ES/content/admin/configuration/managing-connections-between-your translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,rendering error translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,rendering error +translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,rendering error translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,Listed in localization-support#489 translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,Listed in localization-support#489 translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,Listed in localization-support#489 translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,rendering error +translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md,rendering error translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md,rendering error translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,Listed in localization-support#489 @@ -159,6 +258,7 @@ translations/es-ES/content/admin/enterprise-management/configuring-high-availabi translations/es-ES/content/admin/enterprise-management/index.md,Listed in localization-support#489 translations/es-ES/content/admin/enterprise-management/index.md,rendering error translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error +translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,Listed in localization-support#489 translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error @@ -186,11 +286,14 @@ translations/es-ES/content/admin/github-actions/index.md,rendering error translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,Listed in localization-support#489 translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,rendering error +translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md,rendering error translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,Listed in localization-support#489 translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,rendering error +translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,rendering error translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,Listed in localization-support#489 translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md,rendering error +translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md,rendering error translations/es-ES/content/admin/guides.md,Listed in localization-support#489 translations/es-ES/content/admin/guides.md,rendering error translations/es-ES/content/admin/index.md,rendering error @@ -208,6 +311,7 @@ translations/es-ES/content/admin/overview/system-overview.md,rendering error translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,Listed in localization-support#489 translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,rendering error translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error +translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,rendering error translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,rendering error @@ -217,6 +321,10 @@ translations/es-ES/content/admin/user-management/managing-organizations-in-your- translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,Listed in localization-support#489 translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error +translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error +translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error +translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error +translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md,rendering error translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,Listed in localization-support#489 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error @@ -244,6 +352,7 @@ translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,Listed in localization-support#489 translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error +translations/es-ES/content/authentication/index.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,Listed in localization-support#489 translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,Listed in localization-support#489 @@ -252,6 +361,10 @@ translations/es-ES/content/authentication/keeping-your-account-and-data-secure/a translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error +translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error +translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error +translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error +translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error @@ -262,10 +375,15 @@ translations/es-ES/content/authentication/managing-commit-signature-verification translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error +translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error +translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error +translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error +translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md,Listed in localization-support#489 translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md,rendering error +translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error translations/es-ES/content/billing/index.md,rendering error translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,Listed in localization-support#489 translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error @@ -287,6 +405,7 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,Listed in localization-support#489 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error +translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,Listed in localization-support#489 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,Listed in localization-support#489 @@ -294,6 +413,7 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,Listed in localization-support#489 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error +translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md,rendering error translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,rendering error @@ -302,8 +422,10 @@ translations/es-ES/content/code-security/code-scanning/using-codeql-code-scannin translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error +translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,rendering error translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error +translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error translations/es-ES/content/code-security/getting-started/github-security-features.md,Listed in localization-support#489 translations/es-ES/content/code-security/getting-started/github-security-features.md,rendering error translations/es-ES/content/code-security/getting-started/securing-your-organization.md,Listed in localization-support#489 @@ -316,6 +438,7 @@ translations/es-ES/content/code-security/index.md,Listed in localization-support translations/es-ES/content/code-security/index.md,rendering error translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,Listed in localization-support#489 translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,rendering error +translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,Listed in localization-support#489 translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error @@ -378,6 +501,7 @@ translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-de translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,Listed in localization-support#489 translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error +translations/es-ES/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,rendering error translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,Listed in localization-support#489 translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,Listed in localization-support#489 @@ -420,13 +544,14 @@ translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md,renderi translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,Listed in localization-support#489 translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,rendering error translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,Listed in localization-support#489 -translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error +translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,parsing error translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md,rendering error translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md,Listed in localization-support#489 translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md,rendering error +translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,rendering error translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md,Listed in localization-support#489 translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md,rendering error translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md,Listed in localization-support#489 @@ -434,14 +559,22 @@ translations/es-ES/content/desktop/contributing-and-collaborating-using-github-d translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,Listed in localization-support#489 translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,rendering error translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error +translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error +translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error +translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error translations/es-ES/content/developers/apps/guides/using-content-attachments.md,rendering error +translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error +translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error +translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error +translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error translations/es-ES/content/developers/overview/managing-deploy-keys.md,rendering error +translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md,rendering error translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,Listed in localization-support#489 translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error @@ -454,20 +587,35 @@ translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learni translations/es-ES/content/education/guides.md,Listed in localization-support#489 translations/es-ES/content/education/guides.md,rendering error translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error +translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,Listed in localization-support#489 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,rendering error translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,Listed in localization-support#489 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error +translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,rendering error translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,Listed in localization-support#489 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,Listed in localization-support#489 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,rendering error translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error +translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error +translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error +translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error +translations/es-ES/content/get-started/exploring-projects-on-github/index.md,rendering error +translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error +translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error +translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error +translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error +translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md,rendering error +translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md,rendering error +translations/es-ES/content/get-started/getting-started-with-git/index.md,rendering error translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error +translations/es-ES/content/get-started/index.md,rendering error translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error +translations/es-ES/content/get-started/learning-about-github/index.md,rendering error translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,Listed in localization-support#489 @@ -477,6 +625,7 @@ translations/es-ES/content/get-started/onboarding/getting-started-with-github-te translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error translations/es-ES/content/get-started/quickstart/be-social.md,Listed in localization-support#489 translations/es-ES/content/get-started/quickstart/be-social.md,rendering error +translations/es-ES/content/get-started/quickstart/communicating-on-github.md,rendering error translations/es-ES/content/get-started/quickstart/create-a-repo.md,rendering error translations/es-ES/content/get-started/quickstart/fork-a-repo.md,Listed in localization-support#489 translations/es-ES/content/get-started/quickstart/fork-a-repo.md,rendering error @@ -484,23 +633,33 @@ translations/es-ES/content/get-started/quickstart/git-and-github-learning-resour translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error translations/es-ES/content/get-started/quickstart/github-flow.md,Listed in localization-support#489 translations/es-ES/content/get-started/quickstart/github-flow.md,rendering error +translations/es-ES/content/get-started/quickstart/index.md,rendering error +translations/es-ES/content/get-started/quickstart/set-up-git.md,rendering error +translations/es-ES/content/get-started/signing-up-for-github/index.md,rendering error +translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error +translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error translations/es-ES/content/get-started/using-git/about-git-rebase.md,Listed in localization-support#489 translations/es-ES/content/get-started/using-git/about-git-rebase.md,rendering error +translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md,rendering error translations/es-ES/content/get-started/using-git/about-git.md,rendering error translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md,Listed in localization-support#489 translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error +translations/es-ES/content/get-started/using-git/index.md,rendering error translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,Listed in localization-support#489 translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md,Listed in localization-support#489 translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md,rendering error translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error +translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error translations/es-ES/content/get-started/using-github/github-command-palette.md,Listed in localization-support#489 translations/es-ES/content/get-started/using-github/github-command-palette.md,rendering error -translations/es-ES/content/get-started/using-github/github-for-mobile.md,rendering error +translations/es-ES/content/get-started/using-github/github-mobile.md,rendering error +translations/es-ES/content/get-started/using-github/index.md,rendering error translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,Listed in localization-support#489 translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,rendering error +translations/es-ES/content/get-started/using-github/supported-browsers.md,rendering error translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,Listed in localization-support#489 translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,rendering error @@ -508,6 +667,7 @@ translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md,rend translations/es-ES/content/github/copilot/index.md,Listed in localization-support#489 translations/es-ES/content/github/copilot/index.md,rendering error translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error +translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error translations/es-ES/content/github/extending-github/about-webhooks.md,rendering error translations/es-ES/content/github/extending-github/getting-started-with-the-api.md,rendering error translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error @@ -521,6 +681,7 @@ translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-sa translations/es-ES/content/github/site-policy/github-data-protection-agreement.md,rendering error translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md,Listed in localization-support#489 translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error +translations/es-ES/content/github/site-policy/github-terms-of-service.md,rendering error translations/es-ES/content/github/site-policy/index.md,Listed in localization-support#489 translations/es-ES/content/github/site-policy/index.md,rendering error translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,rendering error @@ -533,10 +694,13 @@ translations/es-ES/content/github/working-with-github-support/submitting-a-ticke translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,Listed in localization-support#489 translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error +translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error translations/es-ES/content/graphql/guides/index.md,rendering error +translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md,rendering error translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md,rendering error +translations/es-ES/content/graphql/index.md,rendering error translations/es-ES/content/graphql/overview/breaking-changes.md,Listed in localization-support#489 translations/es-ES/content/graphql/overview/breaking-changes.md,rendering error translations/es-ES/content/index.md,Listed in localization-support#489 @@ -638,6 +802,7 @@ translations/es-ES/content/packages/learn-github-packages/installing-a-package.m translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md,rendering error translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error +translations/es-ES/content/packages/quickstart.md,rendering error translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,rendering error translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,rendering error @@ -805,6 +970,7 @@ translations/es-ES/content/repositories/configuring-branches-and-merges-in-your- translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md,rendering error +translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,Listed in localization-support#489 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error @@ -858,6 +1024,7 @@ translations/es-ES/content/rest/guides/index.md,rendering error translations/es-ES/content/rest/guides/rendering-data-as-graphs.md,rendering error translations/es-ES/content/rest/guides/traversing-with-pagination.md,rendering error translations/es-ES/content/rest/guides/working-with-comments.md,rendering error +translations/es-ES/content/rest/index.md,rendering error translations/es-ES/content/rest/overview/api-previews.md,rendering error translations/es-ES/content/rest/overview/libraries.md,rendering error translations/es-ES/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489 @@ -878,6 +1045,7 @@ translations/es-ES/content/rest/reference/enterprise-admin.md,rendering error translations/es-ES/content/rest/reference/gitignore.md,rendering error translations/es-ES/content/rest/reference/licenses.md,rendering error translations/es-ES/content/rest/reference/migrations.md,rendering error +translations/es-ES/content/rest/reference/packages.md,rendering error translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md,rendering error translations/es-ES/content/rest/reference/pulls.md,Listed in localization-support#489 translations/es-ES/content/rest/reference/pulls.md,rendering error @@ -888,6 +1056,7 @@ translations/es-ES/content/rest/reference/search.md,rendering error translations/es-ES/content/rest/reference/secret-scanning.md,rendering error translations/es-ES/content/rest/reference/teams.md,rendering error translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error +translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error translations/es-ES/content/search-github/searching-on-github/searching-code.md,Listed in localization-support#489 translations/es-ES/content/search-github/searching-on-github/searching-code.md,rendering error @@ -905,4 +1074,25 @@ translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponso translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,rendering error translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md,rendering error translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md,rendering error +translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags +translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags +translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags +translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags +translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/edit-workflow.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/enabling-options.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/licensing-note.md,broken liquid tags +translations/es-ES/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags +translations/es-ES/data/reusables/dependabot/dependabot-tos.md,broken liquid tags +translations/es-ES/data/reusables/enterprise_installation/download-appliance.md,broken liquid tags +translations/es-ES/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags +translations/es-ES/data/reusables/getting-started/marketplace.md,broken liquid tags +translations/es-ES/data/reusables/github-actions/contacting-support.md,broken liquid tags +translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md,broken liquid tags +translations/es-ES/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md,broken liquid tags translations/es-ES/data/reusables/package_registry/authenticate-packages.md,Listed in localization-support#489 +translations/es-ES/data/reusables/package_registry/authenticate-packages.md,broken liquid tags +translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags +translations/es-ES/data/reusables/support/enterprise-resolving-and-closing-tickets.md,broken liquid tags +translations/es-ES/data/reusables/support/premium-resolving-and-closing-tickets.md,broken liquid tags From 3cdc2097179fbff84526127b3061bbff611b5736 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Sun, 12 Dec 2021 21:40:41 -0600 Subject: [PATCH 25/29] New translation batch for cn (#23624) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check parsing * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js From 64216114c0a1493c57a87ee12cc79d0f8e4f45d5 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Mon, 13 Dec 2021 03:49:40 -0500 Subject: [PATCH 26/29] cleaning up trailing slash redirects (part 4) (#23601) --- ...s-token-for-use-with-saml-single-sign-on.md | 2 +- ...ssh-key-for-use-with-saml-single-sign-on.md | 2 +- .../index.md | 4 ++-- ...w-ssh-key-and-adding-it-to-the-ssh-agent.md | 4 ++-- .../connecting-to-github-with-ssh/index.md | 16 ++++++++-------- .../working-with-ssh-key-passphrases.md | 4 ++-- .../about-commit-signature-verification.md | 4 ++-- .../index.md | 6 +++--- .../signing-commits.md | 4 ++-- .../signing-tags.md | 2 +- .../telling-git-about-your-signing-key.md | 2 +- ...it-and-tag-signature-verification-status.md | 2 +- .../index.md | 4 ++-- .../error-agent-admitted-failure-to-sign.md | 2 +- .../troubleshooting-ssh/index.md | 2 +- .../recovering-your-ssh-key-passphrase.md | 4 ++-- content/github/index.md | 6 +++--- content/github/writing-on-github/index.md | 6 +++--- .../archiving-a-github-repository/index.md | 2 +- .../index.md | 2 +- ...and-restoring-branches-in-a-pull-request.md | 6 +++--- .../creating-a-new-repository.md | 6 +++--- .../creating-an-issues-only-repository.md | 4 ++-- .../deleting-a-repository.md | 4 ++-- .../duplicating-a-repository.md | 2 +- .../transferring-a-repository.md | 18 +++++++++--------- .../about-code-owners.md | 2 +- .../about-readmes.md | 4 ++-- .../about-repository-languages.md | 10 +++++----- .../classifying-your-repository-with-topics.md | 2 +- .../licensing-a-repository.md | 2 +- ...nd-analysis-settings-for-your-repository.md | 4 ++-- ...ifications-for-pushes-to-your-repository.md | 6 +++--- .../setting-repository-visibility.md | 6 +++--- .../about-releases.md | 4 ++-- .../releasing-projects-on-github/index.md | 4 ++-- .../managing-releases-in-a-repository.md | 2 +- ...ewing-your-repositorys-releases-and-tags.md | 2 +- .../about-repository-graphs.md | 2 +- .../viewing-a-projects-contributors.md | 4 ++-- .../repositories/working-with-files/index.md | 4 ++-- .../managing-files/editing-files.md | 2 +- .../about-git-large-file-storage.md | 2 +- .../about-large-files-on-github.md | 2 +- .../about-storage-and-bandwidth-usage.md | 4 ++-- ...ollaboration-with-git-large-file-storage.md | 2 +- .../configuring-git-large-file-storage.md | 2 +- .../installing-git-large-file-storage.md | 2 +- .../getting-permanent-links-to-files.md | 4 ++-- .../using-files/tracking-changes-in-a-file.md | 4 ++-- 50 files changed, 101 insertions(+), 101 deletions(-) diff --git a/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index 3957e660c3..4f9ee9ca67 100644 --- a/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -2,7 +2,7 @@ title: Authorizing a personal access token for use with SAML single sign-on intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.' redirect_from: - - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization/ + - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on diff --git a/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md index 4a9c0b3218..fab6fce6f0 100644 --- a/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md +++ b/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md @@ -2,7 +2,7 @@ title: Authorizing an SSH key for use with SAML single sign-on intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.' redirect_from: - - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization/ + - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on diff --git a/content/authentication/authenticating-with-saml-single-sign-on/index.md b/content/authentication/authenticating-with-saml-single-sign-on/index.md index 2eb03de42e..aaf8f6b2ba 100644 --- a/content/authentication/authenticating-with-saml-single-sign-on/index.md +++ b/content/authentication/authenticating-with-saml-single-sign-on/index.md @@ -3,9 +3,9 @@ title: Authenticating with SAML single sign-on intro: 'You can authenticate to {% ifversion fpt %}a {% data variables.product.product_name %} organization {% elsif ghae %}{% data variables.product.product_location %} {% endif %}with SAML single sign-on (SSO){% ifversion fpt %} and view your active sessions{% endif %}.' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ + - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on - /articles/authenticating-with-saml-single-sign-on - - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/ + - /github/authenticating-to-github/authenticating-with-saml-single-sign-on versions: fpt: '*' ghae: '*' diff --git a/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 17b3890a45..76ac207187 100644 --- a/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -2,8 +2,8 @@ title: Generating a new SSH key and adding it to the ssh-agent intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.' redirect_from: - - /articles/adding-a-new-ssh-key-to-the-ssh-agent/ - - /articles/generating-a-new-ssh-key/ + - /articles/adding-a-new-ssh-key-to-the-ssh-agent + - /articles/generating-a-new-ssh-key - /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent - /github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent - /github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent diff --git a/content/authentication/connecting-to-github-with-ssh/index.md b/content/authentication/connecting-to-github-with-ssh/index.md index d586fbb62b..f052a1f3f4 100644 --- a/content/authentication/connecting-to-github-with-ssh/index.md +++ b/content/authentication/connecting-to-github-with-ssh/index.md @@ -2,15 +2,15 @@ title: Connecting to GitHub with SSH intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.' redirect_from: - - /key-setup-redirect/ - - /linux-key-setup/ - - /mac-key-setup/ - - /msysgit-key-setup/ - - /articles/ssh-key-setup/ - - /articles/generating-ssh-keys/ - - /articles/generating-an-ssh-key/ + - /key-setup-redirect + - /linux-key-setup + - /mac-key-setup + - /msysgit-key-setup + - /articles/ssh-key-setup + - /articles/generating-ssh-keys + - /articles/generating-an-ssh-key - /articles/connecting-to-github-with-ssh - - /github/authenticating-to-github/connecting-to-github-with-ssh/ + - /github/authenticating-to-github/connecting-to-github-with-ssh versions: fpt: '*' ghes: '*' diff --git a/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md index 9e36321e37..f9dfd3f00c 100644 --- a/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md +++ b/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md @@ -2,8 +2,8 @@ title: Working with SSH key passphrases intro: You can secure your SSH keys and configure an authentication agent so that you won't have to reenter your passphrase every time you use your SSH keys. redirect_from: - - /ssh-key-passphrases/ - - /working-with-key-passphrases/ + - /ssh-key-passphrases + - /working-with-key-passphrases - /articles/working-with-ssh-key-passphrases - /github/authenticating-to-github/working-with-ssh-key-passphrases - /github/authenticating-to-github/connecting-to-github-with-ssh/working-with-ssh-key-passphrases diff --git a/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index 0a0564460c..e369530726 100644 --- a/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -2,8 +2,8 @@ title: About commit signature verification intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.' redirect_from: - - /articles/about-gpg-commit-and-tag-signatures/ - - /articles/about-gpg/ + - /articles/about-gpg-commit-and-tag-signatures + - /articles/about-gpg - /articles/about-commit-signature-verification - /github/authenticating-to-github/about-commit-signature-verification - /github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification diff --git a/content/authentication/managing-commit-signature-verification/index.md b/content/authentication/managing-commit-signature-verification/index.md index ee520e190f..8a3ba49810 100644 --- a/content/authentication/managing-commit-signature-verification/index.md +++ b/content/authentication/managing-commit-signature-verification/index.md @@ -2,10 +2,10 @@ title: Managing commit signature verification intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} will verify these signatures so other people will know that your commits come from a trusted source.{% ifversion fpt %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}' redirect_from: - - /articles/generating-a-gpg-key/ - - /articles/signing-commits-with-gpg/ + - /articles/generating-a-gpg-key + - /articles/signing-commits-with-gpg - /articles/managing-commit-signature-verification - - /github/authenticating-to-github/managing-commit-signature-verification/ + - /github/authenticating-to-github/managing-commit-signature-verification versions: fpt: '*' ghes: '*' diff --git a/content/authentication/managing-commit-signature-verification/signing-commits.md b/content/authentication/managing-commit-signature-verification/signing-commits.md index ad03fae2b2..a158f5199a 100644 --- a/content/authentication/managing-commit-signature-verification/signing-commits.md +++ b/content/authentication/managing-commit-signature-verification/signing-commits.md @@ -2,8 +2,8 @@ title: Signing commits intro: You can sign commits locally using GPG or S/MIME. redirect_from: - - /articles/signing-commits-and-tags-using-gpg/ - - /articles/signing-commits-using-gpg/ + - /articles/signing-commits-and-tags-using-gpg + - /articles/signing-commits-using-gpg - /articles/signing-commits - /github/authenticating-to-github/signing-commits - /github/authenticating-to-github/managing-commit-signature-verification/signing-commits diff --git a/content/authentication/managing-commit-signature-verification/signing-tags.md b/content/authentication/managing-commit-signature-verification/signing-tags.md index 4781a9c471..7d9a38a398 100644 --- a/content/authentication/managing-commit-signature-verification/signing-tags.md +++ b/content/authentication/managing-commit-signature-verification/signing-tags.md @@ -2,7 +2,7 @@ title: Signing tags intro: You can sign tags locally using GPG or S/MIME. redirect_from: - - /articles/signing-tags-using-gpg/ + - /articles/signing-tags-using-gpg - /articles/signing-tags - /github/authenticating-to-github/signing-tags - /github/authenticating-to-github/managing-commit-signature-verification/signing-tags diff --git a/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index d56867dcdc..25275ba5df 100644 --- a/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -2,7 +2,7 @@ title: Telling Git about your signing key intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.' redirect_from: - - /articles/telling-git-about-your-gpg-key/ + - /articles/telling-git-about-your-gpg-key - /articles/telling-git-about-your-signing-key - /github/authenticating-to-github/telling-git-about-your-signing-key - /github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key diff --git a/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md index e643302eb5..38e0b87865 100644 --- a/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md +++ b/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md @@ -2,7 +2,7 @@ title: Checking your commit and tag signature verification status intro: 'You can check the verification status of your commit and tag signatures on {% data variables.product.product_name %}.' redirect_from: - - /articles/checking-your-gpg-commit-and-tag-signature-verification-status/ + - /articles/checking-your-gpg-commit-and-tag-signature-verification-status - /articles/checking-your-commit-and-tag-signature-verification-status - /github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status - /github/authenticating-to-github/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status diff --git a/content/authentication/troubleshooting-commit-signature-verification/index.md b/content/authentication/troubleshooting-commit-signature-verification/index.md index 7d4c3126b8..46abaa90df 100644 --- a/content/authentication/troubleshooting-commit-signature-verification/index.md +++ b/content/authentication/troubleshooting-commit-signature-verification/index.md @@ -2,9 +2,9 @@ title: Troubleshooting commit signature verification intro: 'You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on {% data variables.product.product_name %}.' redirect_from: - - /articles/troubleshooting-gpg/ + - /articles/troubleshooting-gpg - /articles/troubleshooting-commit-signature-verification - - /github/authenticating-to-github/troubleshooting-commit-signature-verification/ + - /github/authenticating-to-github/troubleshooting-commit-signature-verification versions: fpt: '*' ghes: '*' diff --git a/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md index 812c79ca2d..1f852e1bcf 100644 --- a/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md +++ b/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md @@ -2,7 +2,7 @@ title: 'Error: Agent admitted failure to sign' intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.' redirect_from: - - /articles/error-agent-admitted-failure-to-sign-using-the-key/ + - /articles/error-agent-admitted-failure-to-sign-using-the-key - /articles/error-agent-admitted-failure-to-sign - /github/authenticating-to-github/error-agent-admitted-failure-to-sign - /github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign diff --git a/content/authentication/troubleshooting-ssh/index.md b/content/authentication/troubleshooting-ssh/index.md index 49ff2d76ab..b7b79529d9 100644 --- a/content/authentication/troubleshooting-ssh/index.md +++ b/content/authentication/troubleshooting-ssh/index.md @@ -3,7 +3,7 @@ title: Troubleshooting SSH intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.' redirect_from: - /articles/troubleshooting-ssh - - /github/authenticating-to-github/troubleshooting-ssh/ + - /github/authenticating-to-github/troubleshooting-ssh versions: fpt: '*' ghes: '*' diff --git a/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md index e9f54aa68b..e8e60da730 100644 --- a/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md +++ b/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md @@ -2,8 +2,8 @@ title: Recovering your SSH key passphrase intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.' redirect_from: - - /articles/how-do-i-recover-my-passphrase/ - - /articles/how-do-i-recover-my-ssh-key-passphrase/ + - /articles/how-do-i-recover-my-passphrase + - /articles/how-do-i-recover-my-ssh-key-passphrase - /articles/recovering-your-ssh-key-passphrase - /github/authenticating-to-github/recovering-your-ssh-key-passphrase - /github/authenticating-to-github/troubleshooting-ssh/recovering-your-ssh-key-passphrase diff --git a/content/github/index.md b/content/github/index.md index b8c5e0a166..25aee3d946 100644 --- a/content/github/index.md +++ b/content/github/index.md @@ -1,9 +1,9 @@ --- title: GitHub redirect_from: - - /articles/ - - /common-issues-and-questions/ - - /troubleshooting-common-issues/ + - /articles + - /common-issues-and-questions + - /troubleshooting-common-issues intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.' versions: fpt: '*' diff --git a/content/github/writing-on-github/index.md b/content/github/writing-on-github/index.md index bb6fca8401..e53ef2f32b 100644 --- a/content/github/writing-on-github/index.md +++ b/content/github/writing-on-github/index.md @@ -1,9 +1,9 @@ --- title: Writing on GitHub redirect_from: - - /categories/88/articles/ - - /articles/github-flavored-markdown/ - - /articles/writing-on-github/ + - /categories/88/articles + - /articles/github-flavored-markdown + - /articles/writing-on-github - /categories/writing-on-github intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.' versions: diff --git a/content/repositories/archiving-a-github-repository/index.md b/content/repositories/archiving-a-github-repository/index.md index d56b3073ee..753b40a4bf 100644 --- a/content/repositories/archiving-a-github-repository/index.md +++ b/content/repositories/archiving-a-github-repository/index.md @@ -2,7 +2,7 @@ title: Archiving a GitHub repository intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.' redirect_from: - - /articles/can-i-archive-a-repository/ + - /articles/can-i-archive-a-repository - /articles/archiving-a-github-repository - /enterprise/admin/user-management/archiving-and-unarchiving-repositories - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md index 9589970b76..fbef6893f4 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md @@ -2,7 +2,7 @@ title: Defining the mergeability of pull requests intro: 'You can require pull requests to pass a set of checks before they can be merged. For example, you can block pull requests that don''t pass status checks or require that pull requests have a specific number of approving reviews before they can be merged.' redirect_from: - - /articles/defining-the-mergeability-of-a-pull-request/ + - /articles/defining-the-mergeability-of-a-pull-request - /articles/defining-the-mergeability-of-pull-requests - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions - /github/administering-a-repository/defining-the-mergeability-of-pull-requests diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md index 6ee9ec66c3..807c0c5aa5 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md @@ -2,9 +2,9 @@ title: Deleting and restoring branches in a pull request intro: 'If you have write access in a repository, you can delete branches that are associated with closed or merged pull requests. You cannot delete branches that are associated with open pull requests.' redirect_from: - - /articles/tidying-up-pull-requests/ - - /articles/restoring-branches-in-a-pull-request/ - - /articles/deleting-unused-branches/ + - /articles/tidying-up-pull-requests + - /articles/restoring-branches-in-a-pull-request + - /articles/deleting-unused-branches - /articles/deleting-and-restoring-branches-in-a-pull-request - /github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request - /github/administering-a-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request diff --git a/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index c6e900e528..a8a463dce3 100644 --- a/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -2,9 +2,9 @@ title: Creating a new repository intro: You can create a new repository on your personal account or any organization where you have sufficient permissions. redirect_from: - - /creating-a-repo/ - - /articles/creating-a-repository-in-an-organization/ - - /articles/creating-a-new-organization-repository/ + - /creating-a-repo + - /articles/creating-a-repository-in-an-organization + - /articles/creating-a-new-organization-repository - /articles/creating-a-new-repository - /articles/creating-an-internal-repository - /github/setting-up-and-managing-your-enterprise-account/creating-an-internal-repository diff --git a/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md index 30ab449f76..e5428dc4c8 100644 --- a/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md +++ b/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md @@ -2,8 +2,8 @@ title: Creating an issues-only repository intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.' redirect_from: - - /articles/issues-only-access-permissions/ - - /articles/is-there-issues-only-access-to-organization-repositories/ + - /articles/issues-only-access-permissions + - /articles/is-there-issues-only-access-to-organization-repositories - /articles/creating-an-issues-only-repository - /github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository diff --git a/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/content/repositories/creating-and-managing-repositories/deleting-a-repository.md index 5fb2fd7aea..f9f2013c0c 100644 --- a/content/repositories/creating-and-managing-repositories/deleting-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/deleting-a-repository.md @@ -2,8 +2,8 @@ title: Deleting a repository intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository. redirect_from: - - /delete-a-repo/ - - /deleting-a-repo/ + - /delete-a-repo + - /deleting-a-repo - /articles/deleting-a-repository - /github/administering-a-repository/deleting-a-repository - /github/administering-a-repository/managing-repository-settings/deleting-a-repository diff --git a/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index fe81a4601c..0cbb49c85b 100644 --- a/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -2,7 +2,7 @@ title: Duplicating a repository intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.' redirect_from: - - /articles/duplicating-a-repo/ + - /articles/duplicating-a-repo - /articles/duplicating-a-repository - /github/creating-cloning-and-archiving-repositories/duplicating-a-repository - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/duplicating-a-repository diff --git a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index 651ec1b4dd..82edf7150d 100644 --- a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -2,15 +2,15 @@ title: Transferring a repository intro: You can transfer repositories to other users or organization accounts. redirect_from: - - /articles/about-repository-transfers/ - - /move-a-repo/ - - /moving-a-repo/ - - /articles/what-is-transferred-with-a-repository/ - - /articles/what-is-transferred-with-a-repo/ - - /articles/how-to-transfer-a-repo/ - - /articles/how-to-transfer-a-repository/ - - /articles/transferring-a-repository-owned-by-your-personal-account/ - - /articles/transferring-a-repository-owned-by-your-organization/ + - /articles/about-repository-transfers + - /move-a-repo + - /moving-a-repo + - /articles/what-is-transferred-with-a-repository + - /articles/what-is-transferred-with-a-repo + - /articles/how-to-transfer-a-repo + - /articles/how-to-transfer-a-repository + - /articles/transferring-a-repository-owned-by-your-personal-account + - /articles/transferring-a-repository-owned-by-your-organization - /articles/transferring-a-repository - /github/administering-a-repository/transferring-a-repository - /github/administering-a-repository/managing-repository-settings/transferring-a-repository diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 0371d81e62..d5d45325ef 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -2,7 +2,7 @@ title: About code owners intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository. redirect_from: - - /articles/about-codeowners/ + - /articles/about-codeowners - /articles/about-code-owners - /github/creating-cloning-and-archiving-repositories/about-code-owners - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index a6ad2effcd..bd1c73488f 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -2,8 +2,8 @@ title: About READMEs intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.' redirect_from: - - /articles/section-links-on-readmes-and-blob-pages/ - - /articles/relative-links-in-readmes/ + - /articles/section-links-on-readmes-and-blob-pages + - /articles/relative-links-in-readmes - /articles/about-readmes - /github/creating-cloning-and-archiving-repositories/about-readmes - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md index 2ab843e2d4..be5c459c90 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md @@ -2,11 +2,11 @@ title: About repository languages intro: The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository. redirect_from: - - /articles/my-repository-is-marked-as-the-wrong-language/ - - /articles/why-isn-t-my-favorite-language-recognized/ - - /articles/my-repo-is-marked-as-the-wrong-language/ - - /articles/why-isn-t-sql-recognized-as-a-language/ - - /articles/why-isn-t-my-favorite-language-recognized-by-github/ + - /articles/my-repository-is-marked-as-the-wrong-language + - /articles/why-isn-t-my-favorite-language-recognized + - /articles/my-repo-is-marked-as-the-wrong-language + - /articles/why-isn-t-sql-recognized-as-a-language + - /articles/why-isn-t-my-favorite-language-recognized-by-github - /articles/about-repository-languages - /github/creating-cloning-and-archiving-repositories/about-repository-languages - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-languages diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index 2aa2f07f4f..48c0c4d4bf 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -2,7 +2,7 @@ title: Classifying your repository with topics intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.' redirect_from: - - /articles/about-topics/ + - /articles/about-topics - /articles/classifying-your-repository-with-topics - /github/administering-a-repository/classifying-your-repository-with-topics - /github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index c719bbebe9..3ac3c54bdd 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -2,7 +2,7 @@ title: Licensing a repository intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.' redirect_from: - - /articles/open-source-licensing/ + - /articles/open-source-licensing - /articles/licensing-a-repository - /github/creating-cloning-and-archiving-repositories/licensing-a-repository - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md index b027483903..0181b7ae84 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -3,8 +3,8 @@ title: Managing security and analysis settings for your repository intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.' permissions: People with admin permissions to a repository can manage security and analysis settings for the repository. redirect_from: - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/ - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories/ + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories + - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization - /github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 9a40def4b8..67c8fece20 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -3,9 +3,9 @@ title: About email notifications for pushes to your repository intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository. permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository. redirect_from: - - /articles/managing-notifications-for-pushes-to-a-repository/ - - /articles/receiving-email-notifications-for-pushes-to-a-repository/ - - /articles/about-email-notifications-for-pushes-to-your-repository/ + - /articles/managing-notifications-for-pushes-to-a-repository + - /articles/receiving-email-notifications-for-pushes-to-a-repository + - /articles/about-email-notifications-for-pushes-to-your-repository - /github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository - /github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository - /github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 1841cf3ab9..60c27fc359 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -2,9 +2,9 @@ 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/ - - /articles/converting-a-public-repo-to-a-private-repo/ + - /articles/making-a-private-repository-public + - /articles/making-a-public-repository-private + - /articles/converting-a-public-repo-to-a-private-repo - /articles/setting-repository-visibility - /github/administering-a-repository/setting-repository-visibility - /github/administering-a-repository/managing-repository-settings/setting-repository-visibility diff --git a/content/repositories/releasing-projects-on-github/about-releases.md b/content/repositories/releasing-projects-on-github/about-releases.md index 883c2fc595..b4e5fce59b 100644 --- a/content/repositories/releasing-projects-on-github/about-releases.md +++ b/content/repositories/releasing-projects-on-github/about-releases.md @@ -2,8 +2,8 @@ title: About releases intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.' redirect_from: - - /articles/downloading-files-from-the-command-line/ - - /articles/downloading-files-with-curl/ + - /articles/downloading-files-from-the-command-line + - /articles/downloading-files-with-curl - /articles/about-releases - /articles/getting-the-download-count-for-your-releases - /github/administering-a-repository/getting-the-download-count-for-your-releases diff --git a/content/repositories/releasing-projects-on-github/index.md b/content/repositories/releasing-projects-on-github/index.md index f486698180..feb05945b2 100644 --- a/content/repositories/releasing-projects-on-github/index.md +++ b/content/repositories/releasing-projects-on-github/index.md @@ -2,8 +2,8 @@ title: Releasing projects on GitHub intro: 'You can create a release to package software, release notes, and binary files for other people to download.' redirect_from: - - /categories/85/articles/ - - /categories/releases/ + - /categories/85/articles + - /categories/releases - /github/administering-a-repository/releasing-projects-on-github versions: fpt: '*' diff --git a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index f03d82caf8..eff47a5b08 100644 --- a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -3,7 +3,7 @@ title: Managing releases in a repository intro: You can create releases to bundle and deliver iterations of a project to users. redirect_from: - /articles/creating-releases - - /articles/listing-and-editing-releases/ + - /articles/listing-and-editing-releases - /articles/editing-and-deleting-releases - /articles/managing-releases-in-a-repository - /github/administering-a-repository/creating-releases diff --git a/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index e8b67b47a9..393e6eb56c 100644 --- a/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -2,7 +2,7 @@ title: Viewing your repository's releases and tags intro: You can view the chronological history of your repository by release name or tag version number. redirect_from: - - /articles/working-with-tags/ + - /articles/working-with-tags - /articles/viewing-your-repositorys-tags - /github/administering-a-repository/viewing-your-repositorys-tags - /github/administering-a-repository/viewing-your-repositorys-releases-and-tags diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md index 63f175baf4..2a5f059245 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md @@ -2,7 +2,7 @@ title: About repository graphs intro: Repository graphs help you view and analyze data for your repository. redirect_from: - - /articles/using-graphs/ + - /articles/using-graphs - /articles/about-repository-graphs - /github/visualizing-repository-data-with-graphs/about-repository-graphs - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/about-repository-graphs diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md index 0035e6e331..02ea78541a 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md @@ -2,8 +2,8 @@ title: Viewing a project's contributors intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.' redirect_from: - - /articles/i-don-t-see-myself-in-the-contributions-graph/ - - /articles/viewing-contribution-activity-in-a-repository/ + - /articles/i-don-t-see-myself-in-the-contributions-graph + - /articles/viewing-contribution-activity-in-a-repository - /articles/viewing-a-projects-contributors - /github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-projects-contributors diff --git a/content/repositories/working-with-files/index.md b/content/repositories/working-with-files/index.md index 8a03d297e2..1e874875f7 100644 --- a/content/repositories/working-with-files/index.md +++ b/content/repositories/working-with-files/index.md @@ -2,8 +2,8 @@ title: Working with files intro: Learn how to manage and use files in repositories. redirect_from: - - /categories/81/articles/ - - /categories/manipulating-files/ + - /categories/81/articles + - /categories/manipulating-files - /categories/managing-files-in-a-repository - /github/managing-files-in-a-repository versions: diff --git a/content/repositories/working-with-files/managing-files/editing-files.md b/content/repositories/working-with-files/managing-files/editing-files.md index e17fdc3abf..b52562a21b 100644 --- a/content/repositories/working-with-files/managing-files/editing-files.md +++ b/content/repositories/working-with-files/managing-files/editing-files.md @@ -2,7 +2,7 @@ title: Editing files intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.' redirect_from: - - /articles/editing-files/ + - /articles/editing-files - /articles/editing-files-in-your-repository - /github/managing-files-in-a-repository/editing-files-in-your-repository - /articles/editing-files-in-another-user-s-repository diff --git a/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index ac1229f6fe..284c0fc933 100644 --- a/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -2,7 +2,7 @@ title: About Git Large File Storage intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' redirect_from: - - /articles/about-large-file-storage/ + - /articles/about-large-file-storage - /articles/about-git-large-file-storage - /github/managing-large-files/about-git-large-file-storage - /github/managing-large-files/versioning-large-files/about-git-large-file-storage diff --git a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 88569010b9..575108e57e 100644 --- a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -12,7 +12,7 @@ redirect_from: - /articles/conditions-for-large-files - /github/managing-large-files/conditions-for-large-files - /github/managing-large-files/working-with-large-files/conditions-for-large-files - - /articles/what-is-the-size-limit-for-a-repository/ + - /articles/what-is-the-size-limit-for-a-repository - /articles/what-is-my-disk-quota - /github/managing-large-files/what-is-my-disk-quota - /github/managing-large-files/working-with-large-files/what-is-my-disk-quota diff --git a/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md index c32b022fd9..d8b8b08de9 100644 --- a/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md @@ -2,8 +2,8 @@ title: About storage and bandwidth usage intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}' redirect_from: - - /articles/billing-plans-for-large-file-storage/ - - /articles/billing-plans-for-git-large-file-storage/ + - /articles/billing-plans-for-large-file-storage + - /articles/billing-plans-for-git-large-file-storage - /articles/about-storage-and-bandwidth-usage - /github/managing-large-files/about-storage-and-bandwidth-usage - /github/managing-large-files/versioning-large-files/about-storage-and-bandwidth-usage diff --git a/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md index 773630514c..f1cd37622a 100644 --- a/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md @@ -2,7 +2,7 @@ title: Collaboration with Git Large File Storage intro: 'With {% data variables.large_files.product_name_short %} enabled, you''ll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn''t have {% data variables.large_files.product_name_short %} will experience a different workflow.' redirect_from: - - /articles/collaboration-with-large-file-storage/ + - /articles/collaboration-with-large-file-storage - /articles/collaboration-with-git-large-file-storage - /github/managing-large-files/collaboration-with-git-large-file-storage - /github/managing-large-files/versioning-large-files/collaboration-with-git-large-file-storage diff --git a/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md index 6b94878a8b..6569c30f30 100644 --- a/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md @@ -2,7 +2,7 @@ title: Configuring Git Large File Storage intro: 'Once [{% data variables.large_files.product_name_short %} is installed](/articles/installing-git-large-file-storage/), you need to associate it with a large file in your repository.' redirect_from: - - /articles/configuring-large-file-storage/ + - /articles/configuring-large-file-storage - /articles/configuring-git-large-file-storage - /github/managing-large-files/configuring-git-large-file-storage - /github/managing-large-files/versioning-large-files/configuring-git-large-file-storage diff --git a/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md index c051cbb5a7..744ea932b5 100644 --- a/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md @@ -2,7 +2,7 @@ title: Installing Git Large File Storage intro: 'In order to use {% data variables.large_files.product_name_short %}, you''ll need to download and install a new program that''s separate from Git.' redirect_from: - - /articles/installing-large-file-storage/ + - /articles/installing-large-file-storage - /articles/installing-git-large-file-storage - /github/managing-large-files/installing-git-large-file-storage - /github/managing-large-files/versioning-large-files/installing-git-large-file-storage diff --git a/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md index cba6634af4..e634289eb4 100644 --- a/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md +++ b/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md @@ -2,8 +2,8 @@ title: Getting permanent links to files intro: 'When viewing a file on {% data variables.product.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.' redirect_from: - - /articles/getting-a-permanent-link-to-a-file/ - - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url/ + - /articles/getting-a-permanent-link-to-a-file + - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url - /articles/getting-permanent-links-to-files - /github/managing-files-in-a-repository/getting-permanent-links-to-files - /github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files diff --git a/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md b/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md index 9f93554c5f..2aa33de78a 100644 --- a/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md +++ b/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md @@ -2,8 +2,8 @@ title: Tracking changes in a file intro: You can trace changes to lines in a file and discover how parts of the file evolved over time. redirect_from: - - /articles/using-git-blame-to-trace-changes-in-a-file/ - - /articles/tracing-changes-in-a-file/ + - /articles/using-git-blame-to-trace-changes-in-a-file + - /articles/tracing-changes-in-a-file - /articles/tracking-changes-in-a-file - /github/managing-files-in-a-repository/tracking-changes-in-a-file - /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file From fe5a08ece6459300db814d05f1051b8c8cf93ae6 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Mon, 13 Dec 2021 03:57:00 -0500 Subject: [PATCH 27/29] content unit tests shouldn't depend on github.blog (#23578) --- tests/content/featured-links.js | 24 +- .../github-blog-feed-packages-2021.xml | 218 ++++++++++++++++++ 2 files changed, 240 insertions(+), 2 deletions(-) create mode 100644 tests/fixtures/github-blog-feed-packages-2021.xml diff --git a/tests/content/featured-links.js b/tests/content/featured-links.js index 38d829369a..d5af4508a9 100644 --- a/tests/content/featured-links.js +++ b/tests/content/featured-links.js @@ -1,12 +1,32 @@ +import fs from 'fs/promises' +import path from 'path' +import { fileURLToPath } from 'url' + +import { beforeAll, jest } from '@jest/globals' +import nock from 'nock' +import japaneseCharacters from 'japanese-characters' + import '../../lib/feature-flags.js' -import { jest } from '@jest/globals' import { getDOM, getJSON } from '../helpers/supertest.js' import enterpriseServerReleases from '../../lib/enterprise-server-releases.js' -import japaneseCharacters from 'japanese-characters' + +const __dirname = path.dirname(fileURLToPath(import.meta.url)) describe('featuredLinks', () => { jest.setTimeout(3 * 60 * 1000) + beforeAll(async () => { + const packagesFeedFixturePayload = await fs.readFile( + path.join(__dirname, '../fixtures/github-blog-feed-packages-2021.xml'), + 'utf-8' + ) + nock('https://github.blog') + .get('/changelog/label/packages/feed') + .reply(200, packagesFeedFixturePayload) + }) + + afterAll(() => nock.cleanAll()) + describe('rendering', () => { test('non-TOC pages do not have intro links', async () => { const $ = await getDOM('/en/get-started/quickstart/set-up-git') diff --git a/tests/fixtures/github-blog-feed-packages-2021.xml b/tests/fixtures/github-blog-feed-packages-2021.xml new file mode 100644 index 0000000000..b90b7383fb --- /dev/null +++ b/tests/fixtures/github-blog-feed-packages-2021.xml @@ -0,0 +1,218 @@ + + + + packages – The GitHub Blog + + https://github.blog + Updates, ideas, and inspiration from GitHub to help developers build and design software. + Mon, 21 Jun 2021 19:05:37 +0000 + en-US + + hourly + + 1 + https://wordpress.org/?v=5.7.4 + + + https://github.blog/wp-content/uploads/2019/01/cropped-github-favicon-512.png?fit=32%2C32 + packages – The GitHub Blog + https://github.blog + 32 + 32 + +153214340 + GitHub Packages Container registry is generally available! + https://github.blog/changelog/2021-06-21-github-packages-container-registry-is-generally-available + + + Mon, 21 Jun 2021 19:05:37 +0000 + https://github.blog/changelog/2021-06-21-github-packages-container-registry-is-generally-available + + + GitHub Packages Container registry, ghcr.io, is now generally available! Container registry provides the best developer experience for publishing, managing, and consuming containers on GitHub. For more information, check out the Container registry general availability blog post.

      +

      Learn more about GitHub Container registry

      +

      For questions, visit the GitHub Packages community

      +

      To see what's next for Packages, visit our public roadmap

      +]]>       + + + + 58760       + + Packages: ghcr.io maintenance mode on 2021-06-05 + https://github.blog/changelog/2021-06-02-packages-ghcr-io-maintenance-mode-on-2021-06-05 + + + Wed, 02 Jun 2021 20:26:25 +0000 + https://github.blog/changelog/2021-06-02-packages-ghcr-io-maintenance-mode-on-2021-06-05 + + + On June 5th, 2021 the GitHub Container Registry, ghcr.io, will be put into maintenance mode. The maintenance window will occur from 16:00 – 17:30 UTC. During this short time pushes to the service will be blocked, however pulls or downloads will remain available. For more detailed status information during maintenance, please refer to https://githubstatus.com

      +

      Learn more about GitHub Container Registry

      +

      For questions, visit the GitHub Packages community

      +

      To see what's next for Packages, visit our public roadmap

      +]]>       + + + + 58525       + + Packages: Container registry now supports GITHUB_TOKEN + https://github.blog/changelog/2021-03-24-packages-container-registry-now-supports-github_token + + + Wed, 24 Mar 2021 17:56:45 +0000 + https://github.blog/changelog/2021-03-24-packages-container-registry-now-supports-github_token + + + You can now use GITHUB_TOKEN to authenticate with the Packages Container registry in your Actions workflows. Say goodbye to all those PATs (delete them from your profile too!), and say hello to using the GITHUB_TOKEN in your workflows to read, create, update, and delete containers.

      +
            - name: Login to Packages Container registry
+        uses: docker/login-action@v1 
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+-          password: ${{ secrets.PAT }}
++          password: ${{ secrets.GITHUB_TOKEN }}
      +

      Write and read access of Actions to containers can be managed in the container settings.

      +

      manage actions access animation

      +

      Learn more about authenticating to Container registry with GitHub Actions

      +

      For questions, visit the GitHub Packages community

      +

      To see what's next for Packages, visit our public roadmap

      +]]>       + + + + 56993       + + Packages: internal visibility now available for Container registry + https://github.blog/changelog/2021-03-24-packages-internal-visibility-now-available-for-container-registry + + + Wed, 24 Mar 2021 17:55:30 +0000 + https://github.blog/changelog/2021-03-24-packages-internal-visibility-now-available-for-container-registry + + + The GitHub Packages Container registry can now create and use containers set with Internal visibility. Internal visibility allows all members of an organization and all organizations within an enterprise read access to the container to more easily share data with your teammates.

      +

      This feature is generally available today on GitHub Enterprise Cloud. Navigate to your organization's Packages settings and click the option for Internal visibility to enable.

      +

      image

      +

      Learn more about configuring visibility for container images

      +

      For questions, visit the GitHub Packages community

      +

      To see what's next for Packages, visit our public roadmap

      +]]>       + + + + 56992       + + Packages: time has been dropped from npm package metadata responses + https://github.blog/changelog/2021-03-05-packages-time-has-been-dropped-from-npm-package-metadata-responses + + + Fri, 05 Mar 2021 17:02:14 +0000 + https://github.blog/changelog/2021-03-05-packages-time-has-been-dropped-from-npm-package-metadata-responses + + + The Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.

      +

      Learn more about the Packages npm registry

      +

      For questions, visit the GitHub Packages community

      +

      To see what's next for Packages, visit our public roadmap

      +

      Note: This post originally inaccurately referred to time as not being returned in the “official npm specification”. While an “official npm specification” does not exist, time is referred to in the registry package-metadata documentation and used for some commands.

      +]]>       + + + + 56624       + + Packages: delete and restore for all packages + https://github.blog/changelog/2021-02-17-packages-delete-and-restore-for-all-packages + + + Thu, 18 Feb 2021 01:15:14 +0000 + https://github.blog/changelog/2021-02-17-packages-delete-and-restore-for-all-packages + + + You can now delete and restore any package type within GitHub Packages, even publicly visible packages. Any package or package version of yours can now be deleted through the github.com website or REST APIs. The ability to delete any package will help you manage the packages you want to keep in your account. Any package deleted within the last 30 days can also be restored to undo a delete and bring the package back to its original state.

      +

      Learn more about deleting and restoring packages and Packages REST APIs

      +

      For questions, visit the GitHub Packages community

      +

      To see what's next for Packages, visit our public roadmap

      +]]>       + + + + 56289       + + Packages: ghcr.io maintenance mode on 2021-01-09 + https://github.blog/changelog/2021-01-08-packages-ghcr-io-maintenance-mode-on-2021-01-09 + + + Fri, 08 Jan 2021 20:27:27 +0000 + https://github.blog/changelog/2021-01-08-packages58-ghcr-io-maintenance-mode-on-2021-01-09 + + + On January 9th 2021 the GitHub Container Registry, ghcr.io, will be put into maintenance mode. During this short time pushes to the service will be blocked, however pulls or downloads will remain available. For more detailed status information during maintenance, please refer to https://githubstatus.com

      +

      Learn more about GitHub Container Registry

      +]]>       + + + + 55793       + + Packages can filter for tagged and untagged containers + https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers + + + Mon, 14 Dec 2020 17:48:23 +0000 + https://github.blog/changelog/2020-12-14-packages-can-filter-for-tagged-and-untagged-containers + + + As more and more versions of containers are published it can become harder to find the tagged images in between a long list of untagged images which create a lot of noise. Now when you visit the version list page of a container, like the super-linter versions, you'll see options for listing tagged, untagged, and all images. We default to showing only the tagged images on the version list page to keep the list limited to the most important images.

      +

      This filtering is only available for GitHub Packages containers (beta).

      +]]>       + + + + 55332       + + Packages container support is an opt-in beta + https://github.blog/changelog/2020-11-17-packages-container-support-is-an-opt-in-beta + + + Tue, 17 Nov 2020 17:21:57 +0000 + https://github.blog/changelog/2020-11-17-packages-container-support-is-an-opt-in-beta + + + You can now more easily opt-in to the public beta of GitHub Packages' improved containers experience. New users and organizations can opt-in to the beta for their organization using either organization settings, or for their user account using user feature preview.

      +

      Current organizations and users of the Packages containers beta will be automatically opted-in for continued access to service.

      +

      See Enabling improved container support for more information.

      +]]>       + + + + 55125       + + Packages – Organization admins access to containers + https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers + + + Mon, 16 Nov 2020 23:54:34 +0000 + https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers + + + Organization admins now have admin privileges for all containers in their organization. Specifically, admins can read, write, manage access, and change the visibility of containers.

      +]]>       + + + + 55124       +       +       From 2f6995b86eac58130a00e72858a2355f77426ccb Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Mon, 13 Dec 2021 10:05:22 +0000 Subject: [PATCH 28/29] update search indexes --- lib/search/indexes/github-docs-3.0-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.0-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 70 files changed, 140 insertions(+), 140 deletions(-) diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br index 9cf62f4ba4..3e4d57b57c 100644 --- a/lib/search/indexes/github-docs-3.0-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06166a59091bf8673251180aa990a7f96fbf2960c445ef6b28818af3aa2d8471 -size 606208 +oid sha256:5b07a8e48fc921d0dbbfba5eccb4c7e11a839d1e20493a7ea369a30e9562567a +size 606407 diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br index fe2d9b2af4..26e6803b29 100644 --- a/lib/search/indexes/github-docs-3.0-cn.json.br +++ b/lib/search/indexes/github-docs-3.0-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4b2f4f3560668d5a46157fc81cda310b084a4d5085170f5ef69c18127811b0b7 -size 1519629 +oid sha256:6a0f80a844047da849c32e1879dfb46413599c962bde418bb32dee450a42f84a +size 1519551 diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br index 8116323f90..079231e20b 100644 --- a/lib/search/indexes/github-docs-3.0-en-records.json.br +++ b/lib/search/indexes/github-docs-3.0-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:117eb82ecaecaaa71feb479f4a19d6823d8b8ffd30d701f524addfd710b8e25f -size 946317 +oid sha256:e66729712c893e76869a47bd36a825f097af5b2f0e483bbe96bba1a607552ce7 +size 946758 diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br index 5baabb8eaf..c17cbad30c 100644 --- a/lib/search/indexes/github-docs-3.0-en.json.br +++ b/lib/search/indexes/github-docs-3.0-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1b4a0ba2672621b5b0dfe9ddb344e3c098c2a74ae5084f90a97c17207bde8a98 -size 3861327 +oid sha256:7397a575e3104b98d807cfa77cad9d738dbb236580035bffb851b52eb8bc3cbc +size 3862906 diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br index 4393df6eff..5da7c2f168 100644 --- a/lib/search/indexes/github-docs-3.0-es-records.json.br +++ b/lib/search/indexes/github-docs-3.0-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3dafe76ff8362c3263b1b517eef69a936f7cd619f4428c01706813ad7a6a476b -size 591089 +oid sha256:ddd597a5d3053787b6d91cc9b645c8d23cc284da8134c4ca7cefc295354a49d1 +size 586837 diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br index 8adb7d7477..0711d99038 100644 --- a/lib/search/indexes/github-docs-3.0-es.json.br +++ b/lib/search/indexes/github-docs-3.0-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e868497c31e11167d27754b95b8d7cebdce8ed9d353d0b99bda07190930bdf13 -size 2604430 +oid sha256:44fe6abd11a577732449a46a22a10e86fffa3f351e910e4fe7ddb61feb0c94d0 +size 2685942 diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br index f58e767eba..d879976d71 100644 --- a/lib/search/indexes/github-docs-3.0-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2700ee9ae3481d4008323f91f4d5087aa0b43cd5dec59fc0066997d42d5eb3a5 -size 620695 +oid sha256:152b607d48324f5e5d420fbe713ce9f161c8827a17eb00e0bd5b223df309dcfc +size 621190 diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br index 3d8a8d45c3..5f17480056 100644 --- a/lib/search/indexes/github-docs-3.0-ja.json.br +++ b/lib/search/indexes/github-docs-3.0-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:746457e4ca9957fe9cca734736a26ae12631a6e17c534bd745d2e36cdb64bf6f -size 3367851 +oid sha256:2740d30d5d085768c9390f38bb7f090fb213605a267d331f4e8a7f43ed6cf5b4 +size 3376085 diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br index 175c84710b..357db07db5 100644 --- a/lib/search/indexes/github-docs-3.0-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8ba0bfa0a356cdb420a86f012a5d08b22bbb3f47737c77e2f4e72cfc4655b8d4 -size 587443 +oid sha256:bf1ababcc5ceff2e97dcf6cadc1425b678e43ba90d5d5d44ff02dbc51f9d573e +size 587411 diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br index 11fd75d4b1..c46d7cbfb8 100644 --- a/lib/search/indexes/github-docs-3.0-pt.json.br +++ b/lib/search/indexes/github-docs-3.0-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:03c35cbd90981725c4b66ca1193f7199a1356124dd25f52bd97e942bb7e323d9 -size 2622011 +oid sha256:eff15e148f874556fda5a1be26e1bbac51a52137710152d35cd32209b780b595 +size 2622272 diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index b8ebdda67b..6f7c5892dc 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:29c235827b315446e63da2206ccee0aa98191a28dc1d6d8f39ce711804a30672 -size 619809 +oid sha256:e8a15ff1cd8ad36fd373e63f49e1fbe0723c7b2af58871af0c250815def9e515 +size 619752 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index 1eaf0b15bd..e89c844457 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b4be3e81b66d20277cd5e452f8806dcbdcadac5575ca54986c8b4e2dc4aa9657 -size 1560789 +oid sha256:4e25db76ee8a7bc9e1379470877d5789278a0a2b6bedb1187c7db875341adb21 +size 1560858 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index 1666aacafc..e5450e0560 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:79c5b3ea71f3837871c7b574226c1e13dfe6e84e217f75013f71014158456d87 -size 970661 +oid sha256:3f13cedba02f4d095fd0f2905c2ede17dfb98124f47ef275871dcc6712873696 +size 970881 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index cd868e77d6..4c00528875 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a951bf9d42e7cb7d0f25acc32f565215f214e71b9dda2a93ece5c1b0b006317d -size 3951733 +oid sha256:c545f1508bb1e1284218de88a3e1bc73393708ae66c6a12e715c259427d0a57f +size 3951381 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index e554b9d0e1..7f80157228 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e60bba0c842d0128bf4efbdb4836808c554de10bf4d416d195c257d0c61828e9 -size 603641 +oid sha256:e2a4affaa5ebffc3c12a5dfe9635518c8f620a34a6cab9edcbf1d85ac43f7613 +size 598714 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index 1ac8418996..0a9de1e2cd 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:89c49357a7e442e43d08ac4937c45b0b1eb5d540e4b95c6538bcf84cc9bd6e75 -size 2665999 +oid sha256:a0ae372ca7b58c9de8957fa7c4c7ffba49d8a4558bea343868e216df545a80f2 +size 2749212 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index 81bfb43a2f..3180bd6516 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:41a61c207dc3c85e12e29e8bff20a96bb78cbb4471f259864157fa2f90b76500 -size 634112 +oid sha256:f70661e069e4fd0a11dcac93c773f2b79b0aefb3570dfe900e8cc761de0043f4 +size 634478 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index 46d62f0a4d..0b3541b8c1 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7e8399ba053cfa6182a73dec91aec835a3c29c5bbecd5297a500bb804298bf87 -size 3447249 +oid sha256:4c5228e43c240d6a5bc31f0cb11c8761e5efcf5e8aed348155e50ad75a99f8cc +size 3456079 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index c40baaf815..cce971cbb6 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1f73e263b5a3d738fe151da665307378531d515a0e048d3d81d535cede265ef4 -size 599963 +oid sha256:46cc56d2c5fe2b5e314df5d9d968ac1fa6d1baa907ec8172addf5d3656a934c8 +size 600020 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 76b5e7f659..811a1aa06c 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:af802020e195ced710bdba996c7b203c674fc531af93bd5e156769a7de8dc549 -size 2686321 +oid sha256:a6ac94583cceabdc7cae27938418a40ec999a87b4344e3371b6a7c78e69c44f2 +size 2686325 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 30c451a2b6..4d5edb5fb6 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:130e915966452f90e9ef737534307a92c5cac71936b4829d31ff45219dbdcb99 -size 631001 +oid sha256:5c6adc5f919ebf10be2a0cf904fc08a36576a44accae97598ba6c8407ad1ef35 +size 631148 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index c95313020e..dc5ea4ed16 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:db42df7e5e54012ab0dd0c0e24efe08d49c71652c1486bc63029640381e780a1 -size 1587394 +oid sha256:55e7ec0ae4ebc3fd631148accd3f26d0b8db3f7822020a1ca89296429951565e +size 1587549 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index aaedf9becc..241515341b 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2def187d8d47cd0955bb9936a6d9d78e032b4eaf0be347fb13f725c6b0c7d948 -size 1001587 +oid sha256:f1f402bafd6c563c3cf9d405e1e952281b7afc566e28d6539155bfea2717d623 +size 1002164 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 7ce69a4e0b..17206a5350 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:81a1d8adc4570ad7b5a92dbb8076490a53997f2b1bdd5ad218aeeef4c50025aa -size 4074513 +oid sha256:7f3efdf77a878a6820477761b584dbeacb1496d55a918c1ff3e5cb039bb71901 +size 4076073 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 8bdd01aa83..8c2e5c2934 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:831a15e87c1d0adf2e49cf100133810a4975c4a81500950e469211a4b3cac8d8 -size 614369 +oid sha256:51eb94a3da6fe11db3f92ee761c1fc2e3483617ff8473a4eb7debca661c5b239 +size 609399 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index 5cfe5fca43..dc472345ef 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b05e3108742e98f44b231e97ab0f7ece8e5ddab4d517f08e6830dc4da2d9b58f -size 2721602 +oid sha256:6cd56bc93ba7651cf1e3a4ca819bc9695e4ea6e778a40e89a5f7cd3c20e96087 +size 2802864 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index 51798e465f..c205842c3b 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:176eb6470a0ae92434b4d3730c54781c903e64afaeced3bb1601ebb9527ad98b -size 645513 +oid sha256:5c0314577d8b60761cad773929db2e8707b93d35e73bcbf93c1671ff16d611a0 +size 645717 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 0d7738d2b7..59063a439a 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f1dd21d36d8768e0357ab7d05ae99b6ef2b4bedd7eff76f1fabb8e5403e4dbfe -size 3516476 +oid sha256:7c8cfeb99f5dc23d0b0ca27852d2acd102dff5e07e24b0c026b8a70aa5f3b6b8 +size 3522752 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 06bd2d4b24..35be032803 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f6564be3ed22d1162b21849111415e8e12cc159659da7e57b1315eead884753a -size 610713 +oid sha256:843bf3d53091fa172a38e8a6138a7bfabd50a507d5a5e876b9196a0fac3eb375 +size 610781 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index ab28dc28f4..3df61098e5 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7ec1b70c88324077c19ae2444d762288eca9984a58ee1853dc03cbd34b986bdd -size 2734109 +oid sha256:6ed130472a4de505b0cabb5aa5f17763743eac1a92eaccbb94adbcba136d0d86 +size 2734323 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 151ae84e34..731ec014c0 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1e6ce40cf39064670238967f56d0da92108814b9b45bcb1a07e428af6cf9081f -size 651847 +oid sha256:c06cd9fe6d7bc8ccad6068e065b1e760568ce4ae81768ebb426323ac107ff354 +size 651882 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 07eb0d3378..fdf8f898bc 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e1e957daba86e289061255efce357d224261f45aa4eba2bf8fb3798aa512005e -size 1645820 +oid sha256:2edf9c2caa33dc33d7b59c6fd59a4877d245016c45d607c849cb80051f3dad87 +size 1647015 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 3e49057a40..3c8d56c7bc 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:494bc5f104a767836503a3adf50f8d5821abd69eb61557a2db60a7831462c54f -size 1035782 +oid sha256:5b94b4b1d2020ec040cb11912f8542feaeda9462e914a67e7f41c481833a52be +size 1036503 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index d3004cceb7..66ee901816 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:91fa6ba27088e733132e8e18ec550d8459fd1383927b29c9aa85d14c2e456f2f -size 4175675 +oid sha256:779b58dd83d28f720f792a903a228616f7a3caec91297c2277a42d070dec1f9b +size 4177524 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 1e0cb470ff..049007489d 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f05d37e45140f405527efdcd3505999f0610d0cc006303c0960879e95b31bcd9 -size 632554 +oid sha256:9541323afda8337f8694a25245727b692af575a1e27687161fb230377a1c728d +size 627379 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index c731312702..74947e2c6a 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fdd243e2f775d48f5a36c06a194f49d4671d391638c6bad14b487a607573451f -size 2819135 +oid sha256:c45bc7816ab2d2ddb5225d077211056f87816f3233e485e9e3c703ad5aad46bc +size 2903635 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index a3b61e0567..270e060de2 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a49c6e3e6ccf70a8b6d47bd5bf5a84b08401c4be1219452a7445575422758aa4 -size 667330 +oid sha256:8ff90a419305aa230aec7da4c23a0a92ef11d6d0838877f2874017e0785ef0e2 +size 667517 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index 2487ae7fd0..239c420b9c 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f0d0c32d8b5a545e69c410e433b8ea54a5b7149decdfd8ce660d5a72ff646b00 -size 3634823 +oid sha256:3ad39fb49d8e78ad57c525d7134378a7a5a7bf13c2fe98ac0259a26414d7233f +size 3642080 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index acd6caafcc..3024f8469c 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bc16daeeb6455075b7520d3fab6f6625739122f4192fe026e6d5fb6b5abafaf8 -size 630137 +oid sha256:dfcb3b72910919a974f712855db0eee53cf490fed457f565b089686a761f59bb +size 630090 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index a940d3307f..a94a82646b 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ad4f746371326f2cf71b9b65da561ed113f174ec5f6791ce5140ca9f77c78a9a -size 2822587 +oid sha256:c81f6a44cd7596c74690ddaaae8bec57f934ac1a1754ea460a9f98412e499939 +size 2821977 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 84f7fb2e6a..de0d4110a1 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:24d60906f5140a023519f530c191df82bc52358f9f3674a32650e14dc6ca69b0 -size 859800 +oid sha256:d1067d80c9626fb23771cf612e117e1b168f6fe33b4c522c81d22ce9d382b34b +size 859699 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index d9f50e4de7..f2d22b266d 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2c83a7482228e6df29513f6274284991a9856a8e32628ec8bfcec9ad0ad527ae -size 1843604 +oid sha256:e4b87d325b0b9814d562674135a9068a105093ceddf2f92cde3d42154c7044ec +size 1843567 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 64b2bea527..15cecbc59b 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:59aebd704b5eb48fd4e64af50098feaafeaa0ef08176efd557ef6c0c22e7a70c -size 1325957 +oid sha256:7f201ae8402d3875732f7014fb75a7f058c188d4c5cc9cfe668414327e405649 +size 1326303 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index b86f89093b..bc441e5d7e 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:85daae5c7d96e19fc7b05e877178f3a2718908a72168225b7ec1542146e0e548 -size 5053508 +oid sha256:92d382649c62ae5359c5efe5b3fbf26da12e1241c6459d3c1ed7078f191cc805 +size 5053986 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index 262f595018..9fdf79a57a 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ac5593de1936996f1e7398dd4da02b7e09d86d1fa9991c39d50042ef556a9492 -size 808869 +oid sha256:be194fbab224f5cc623e8132c5c43dfdabd264e708d71ddf64459b449cbd4f13 +size 806835 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index a59cbf4ed8..8d1627d375 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:61c0590ba5f32d537171e76e246e933997f2ffb552c7cf3fca243fcf7ebd3a51 -size 3425535 +oid sha256:579eb39585de986b80a5ba8ae2405445e0db56a130bb5ddda53356fc1cd699f8 +size 3523939 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index c5b9b6ad4f..fc5fe0818c 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d34d5cb0608488c7908487bffc87b1a5fa37291e4c7d9650dcaf40aaaf13169a -size 876169 +oid sha256:c7e1c40040f9aa964c6a14c67d5b3356764d3affae72b25d82ee551eb701765a +size 877293 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 37ac13dcf6..8d50aa95d8 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b5ceb03d6fbb06a155ccb19a7daafc2f4c4af8a496d03e9e1668db436c896db3 -size 4534829 +oid sha256:c8fb2f8db56095a7a4d4fca3b090cea46bf393cb0e2c8d2a4b75df184f049e3f +size 4543692 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index e2484c3a7b..136c47d856 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:30c87e135fb36bec669372107c126ed9b493600cf4e28d2ee67ef8010161a12b -size 808949 +oid sha256:3b69072038568f97ae84ad0edfb68c182ea7d8f53d6ef5dfe116e5f68562130e +size 809229 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 32f8a6f8c1..fd6ecb6f36 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5c9651c3560671d2dab201c4fb79ba41b04926beb252ce60a15d6a81ec437ff3 -size 3425373 +oid sha256:b0bcf336af020a0afbf0b21af178a86579170f2c2736bc73e8bae87ffdc3ebe5 +size 3426541 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 9617425068..09c6940650 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:36064010019ab944944be4d88a76e5a3730e635980bcaf4801498ee061cafcb2 -size 505124 +oid sha256:56779f0f53b6263964713bed47d4cf433e15d2ccbdab60ae65c7b63a8f6bbbf9 +size 505081 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 4fefc986fc..b82a40e518 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8fdc79d3d12306595dfc67403c1b30840ba257bae32364308648c1af4e102057 -size 1238475 +oid sha256:46fa0065df1468b6510ac5f71a435a086a2e278acbcc9efe4df012e45ef1284f +size 1238624 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index ea206d373e..b26355b21b 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8e564f4a67741552d89fa32f2a0bc3adfec6a87430436830a14ababe000ef207 -size 825816 +oid sha256:5f51d324bbbdf9b2550f8290cc5bc3518914c21ec6bbee17a169a4b1afe1ec8c +size 825827 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index e2ba865bf0..7af2e84111 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fa76ab99415bc234edbfbd6a2c70c44a7e0177066f08101714dfa6ca2f168f95 -size 3298672 +oid sha256:ace8ccabf89124b2123f2a1375c9661874cde217b6923409c651eb8347b7af95 +size 3298573 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index b7177d7c25..a65f9da250 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d08c4f404cfa9ab77f34bdbe5cbda3d98aa691f7545afffe27e57b33e9ab7557 -size 476690 +oid sha256:6d8c8d7e1afd0bbc2174486c0dfec95af14c8a873e4d038d2e04027b612000f8 +size 490130 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 71239bb1d6..2dc77f7f9e 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0c34866c07520d403a343246305c8c3107168a1bc411b1ac21d1339b4ca48c5d -size 2026072 +oid sha256:0fcc8d8d4331367043772d63b53080d4174f70d560faf5c9889834816f234dd4 +size 2186507 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index c7346a33f9..8c95f3266f 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7520e6d691a32e52f0e56c96035ee7de5788ffce203afa13bd850bab9487ec46 -size 516977 +oid sha256:0ba783b891b4d37ff3f6c444882144ed954a49c7cf7005f061b502abcf550677 +size 515893 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index bc4feeab52..c535f9cbf3 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:56420ab043243b0bfa99ff9e90db72b884e3e671bf13ecab6838696950dc8389 -size 2707340 +oid sha256:77d7d311475dbc997dca3746eafa0559f6bf5edb4f2686b6506d1bb3bd0e7db8 +size 2705560 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index d59550c1a0..4901212f2f 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:febb82ca70257880ba51afe2a951c29140855cb908c78ff18757ca642090e2df -size 491590 +oid sha256:9ad872ec32066dae5441294534d67ded4a026dcc09519a25851073d7709f285e +size 491524 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index fc36fff84a..33e3c47408 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:40de7b4c32812b0ca5a77e4fe833f34a002ee27df095dbc1e3550f72b6594cf8 -size 2131424 +oid sha256:3c52330e286c3cc6515550094755fa7fc85ad3525674c4c61cce9147a9a1a878 +size 2131703 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 12e0bcab01..e02354ff6e 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d4fbd04917a109923bde0dfba922ae37ff8188a616b4c35efec391e53526955d -size 765676 +oid sha256:6e86f4bb5bd6dc39ae12a3acdcab47794d0f5741cc4c94f3e0385aa13d939d3e +size 765740 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 06494f598d..3891ee59f1 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:52b474d6c4e4988065ad3375510d6c030839ed2ca50954b0333bb92158432494 -size 1846185 +oid sha256:cd28ad2b93937579a927f99f08dbb39176f2fdfba3e157d549406c05958d1cd3 +size 1846668 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index b0f3e654ca..83d6bbc13b 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:db1c69bba6707200f0010244685a539b97292090e5b6c1ee5d12c4275d13ad2f -size 1178255 +oid sha256:0c54ea2b054b637181fef86ed521fcbbef9b41a2f3803adf8b97fa998219291d +size 1178269 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index cef5a58831..0ad283ade8 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06d1ccee40c9a9ac2475159cf33eea131711f471bf9c68efa0a0660b2177f8b9 -size 4741965 +oid sha256:709534f99020776a13533492a93c096a45f6ca56fca572e8085e6c3bd00ee00f +size 4742674 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index bbc358e04d..e8429a5ea6 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:988ed682654c234e42cafbd45d864258c6ad3b84bd2a02c1a0ae0fe3f2f90930 -size 745595 +oid sha256:d464b6e46cce390c9b8c93a3aff8758c212278659f64573e1669b93ab2ec2fdb +size 743463 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index 4555651f12..3cc71fc0d5 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4ff21ed49aac296edf77467a3dedefb53ccc12005faf0ad54bb621c7c44f5f09 -size 3328876 +oid sha256:f38dfb199c6108c57bd669b99e279fdb249c84cdad1b7bf7f4ff1a5ef50070e4 +size 3429611 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index c8e82ea848..faaa12e39e 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:40c94a07326261967d1c710181f5b016b84db7f5dc2abf8e09cdcef05c661164 -size 785732 +oid sha256:36f9334cb9a5d751d8d451946c8573b2a6f92eb332d7318418aac0ccecfc7a3d +size 787699 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 1b4d0ca6c6..11af44aa30 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8b1862d68a151d21b8b2814ddbb4ddb663f69b348f95dd1ddb0b986e7b71089e -size 4284269 +oid sha256:52ccf69021af95196f1a5e998d79801f242ddf4521a5615100e13ca13d7dd4bb +size 4294262 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index 250cc6ef8e..e106df8261 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e568254d4ad880ccbd2e4d9b29a4d4b964cad44e90c1d9d3707503956d748b8c -size 746540 +oid sha256:e06196b401cde0f938d06b5efed3c75649eb7760dcb63cd6200c7c756dbf81ac +size 746764 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 39774b4cd5..3ac5186507 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:239bc31215e84bbf5beb3b7b4de363e1828b6cee5e33119f11a44e6b3070ad3c -size 3319224 +oid sha256:200d99602ba26858878b9a1116d9345325e6ea9b5ab63b519691acd92491c55d +size 3320046 From 7df4dba54b194fcbcd040c5d25e7960f9e7dfd24 Mon Sep 17 00:00:00 2001 From: Pulkit Agarwal <36596168+pulkitaggarwl@users.noreply.github.com> Date: Mon, 13 Dec 2021 15:38:40 +0530 Subject: [PATCH 29/29] Update configuring-a-packages-access-control-and-visibility.md (#12242) * Update configuring-a-packages-access-control-and-visibility.md * Update content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md Co-authored-by: hubwriter --- .../configuring-a-packages-access-control-and-visibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index 8b051b2888..293248895a 100644 --- a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -152,7 +152,7 @@ You can choose the visibility of containers that organization members can publis 6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images. - To enable organization members to create public container images, click **Public**. - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. - - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, click **Internal**. + - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png) ## Configuring visibility of container images for an organization