Octomerger Bot
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:20d10592d319f192b54699b87b8cd8f68b0e58a71857923e5455d13552d4bf4e
|
||||
size 795156
|
||||
oid sha256:10305ffca722f9497da5dccfee5ca6554253de266f0ea719d177917ef0d96c60
|
||||
size 795177
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b0eb65f14c67b2e7949edd031d1f75e1da465aceb60afc7295210a9305b52650
|
||||
size 1645986
|
||||
oid sha256:542a252eadbb7f572ba5de5c7462e3665aa53735d63485a5b2a81e8fdce63877
|
||||
size 1645913
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4744dbdb476f2c37aeb209afa5b2752af8495c412f60a6943b16b2181b947f92
|
||||
size 1094576
|
||||
oid sha256:2dc5860c4574cf8577076e6529ef4783807d769dcb1b3480c5b0a00d994a91ed
|
||||
size 1095553
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:43bf17391e51dbf3bc3f3c0b86c5b02e19040b31f96d505874abb2dd85aa6950
|
||||
size 4442029
|
||||
oid sha256:5ea1535092ea321dbc573ae92bcd3c44bd717809d4d64abc0109c22812f8966c
|
||||
size 4443671
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ba377befffac71117131cbf5588d83e4010b271320f35a7f4b684c77b1c2f9ab
|
||||
size 734114
|
||||
oid sha256:8437af322a6cbf905106b8a88aa7c0b7eaa7eb482743ca75cedf081b573222e4
|
||||
size 734155
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e2af9387d6174b89722bed9e78ded931483533a686314bfa04f770b5980ee442
|
||||
size 3128125
|
||||
oid sha256:d459b7c5dae4fc6973f6e30285842ad21fddfbc07201fb4a09939a929b340d52
|
||||
size 3127165
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2466b933cb57eccfb5e804c5f158e9d924a79c594b33530ee463ef41ddad14cf
|
||||
size 810806
|
||||
oid sha256:fe395396f95396d5309a669f23c05657c70f2bdfa7cebffee9c9a15826a938c3
|
||||
size 810791
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1ee6a6dd91db8bc2fb4998f6871473ff50b071daea7549be6c0ac0097817b634
|
||||
size 4455419
|
||||
oid sha256:0d31b26697e8f10798a21e33d022d5e1269c0948c0eec62dc792fcf0e49598e6
|
||||
size 4455087
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:39fc635e83065615e9796e4c2c0b297546314fd0cb94b89bb5292304cc16697f
|
||||
size 722904
|
||||
oid sha256:0ad06cd7939816e3841ebdf682b3557fc64451766a5d1c09551da40c917c6f52
|
||||
size 722895
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:67311169d831dc89e41e06124e8e1d67b6751082e05fa29e13c5801ebe86593a
|
||||
size 3023222
|
||||
oid sha256:e17fd9906fb32c2941816c9ff7de2a1d0afe76f6045fe65ef63f3024b691bca9
|
||||
size 3022640
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:364ad68908f97deb4f6ca8cd63de16724057cfb6f2dc60d60d3bee89be4b5517
|
||||
size 820900
|
||||
oid sha256:fb5e185c567a0d7f0ba865ae64a78f2c27fea5761aee2559d37b40d70e0c2f22
|
||||
size 820956
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3cd42acd81bc8789c73b79c42d6d663aa6e5957bb713a967580179cbc9de7b9c
|
||||
size 1694326
|
||||
oid sha256:2eb4933dce2c39d0629008d97c32b9ee9d94464347e86ee2c7024863538a29f0
|
||||
size 1694012
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:63a19244826ea254053fa0bf6f609bc9ec110c32b8e868709562fdd3c1c143cc
|
||||
size 1130065
|
||||
oid sha256:460feb77d1819bba14164d32a73d6cd79142f9a11a0d1b558e119fffb3b67723
|
||||
size 1130620
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b509c6fa1bea0e18809847078f2807010756d58819af810c23afec303dd0e104
|
||||
size 4543574
|
||||
oid sha256:ef5430df67cd2624b43d559e4338e3bf2013019755db9e10db2fe81dd8c64048
|
||||
size 4547467
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:781d2ba1cfcaeffd537d0c31b072236b41e427290bcaea22cbffaf16838be9a4
|
||||
size 755316
|
||||
oid sha256:78df7a88264596072250995ab1a31e0534443c8d69d15816b3957c2b36cf9040
|
||||
size 755382
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4023fd20a0ba6764dd8ea9949b18fae13024fc4de1758e664ae4fa8d6de71d55
|
||||
size 3211385
|
||||
oid sha256:0e39815546c90a4c6fe67c48e30e00d9c139c82ca09a52bcfc5301c3ca00f997
|
||||
size 3211641
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:acae8605cabdfb0e1bde3e8e61ce2ab863ab5dde170f770ef540267b4e9c43b6
|
||||
size 836131
|
||||
oid sha256:41b1e1574494a8b6ecd8f01c977704bb59381691943dc350326460aa92189e25
|
||||
size 836435
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:024ce6dc8d53d8112883d4bd1e3efc52755a2ae7cfcb956c13501fa16a037a56
|
||||
size 4589191
|
||||
oid sha256:a4b310defec03261d115ac8fd0c6c60e4f96700118a78ca207d8fd9fd4440d6a
|
||||
size 4589843
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f640282e4aca179a0dbb9dbd2f7c9f6e0619a495317d5cd567a3f7b1fa3e6708
|
||||
size 744486
|
||||
oid sha256:b28b9222d48551aa0035be4b72a0645f510cea1e56c078af936310289abd01cb
|
||||
size 744570
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cd2ad6033068094672347686ef9e3a127f7b18edfe93f409825a40ac58231816
|
||||
size 3108669
|
||||
oid sha256:03023e85e34e7f3e30d2c554ff697f7fcab62ef45fa3a377980f03824bf5ae74
|
||||
size 3108809
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c8874cab046f0dcaf7769d89eb973682fb747abfd2b859229757ad75dee1736b
|
||||
size 823419
|
||||
oid sha256:0755a52c0668c8a112ffb31690d93a3a12f431c836d8a82f69f4be2325ad9641
|
||||
size 823418
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ee5fbb7f83e1b650d992a81ddaa8411b949ace62804882d61f6292ea617759e4
|
||||
size 1710234
|
||||
oid sha256:dc53f18b975cf32137b48b3a86f2e3c4e8f5122a152577c6bdacd3a5690f79e5
|
||||
size 1710373
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ac89486d0cf18699656491f21459ac54d4232f476e82355a8fbb3f33fe51f3e8
|
||||
size 1141711
|
||||
oid sha256:155b7c1a60d9a3a7b0721ab3df3de82833327c87ecdd7a83e1ed8dcd34593997
|
||||
size 1142432
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0d999f76499e18c850fbb2a65acc35d13d59edc39132becf8427e5e3bdd1a090
|
||||
size 4603388
|
||||
oid sha256:01f602b549b5f559a53490017ad8bbda9091e15295ba66d1701f4e88d2438aa5
|
||||
size 4606670
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3ca62bf3fd5e89f1fc1d9446a29a19f351feb10e5523d5b2a64c1a188a6ae3b5
|
||||
size 760126
|
||||
oid sha256:7d38164ad58959c6f5630da65fc6347a7ac21548396129d9e427eb56582df5fa
|
||||
size 760181
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e9e307babbda1f87e02c823993e1b6da8f504cd08dfa64050f4500748d812857
|
||||
size 3236208
|
||||
oid sha256:d575582ad6bdf4f7b926b0aeb82998f6ae4ce9ca85195eb0dd4bc131d826f330
|
||||
size 3236306
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cde0c5c4433d69b78edffb504c62c7c31543e6dc75806c76278d6309b78748a3
|
||||
size 839679
|
||||
oid sha256:0a091f2b28c44d5a0aeb7c197d011b86ec02dd193abbb91734c1f79177ceb575
|
||||
size 839778
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:75fb7e396b59444a30e695c50b3630e4e2223f6e289308cbaa5e70c59057810d
|
||||
size 4624275
|
||||
oid sha256:a3af0a7760f0b467ae5f2582a6f4d92cafc6db8e2c4d3194f3d7fa5e3e782de7
|
||||
size 4624728
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8efd5dcfd0802fb00802d6d72b78c45e643115a59d2b36114c5229b913e0180d
|
||||
size 748825
|
||||
oid sha256:447610bb5b208f2c73ee28fbfa3ae1806f871b40a638b3a5cb9d500fb7b506c8
|
||||
size 748971
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c80a1e766964b0a5348307c439f9127822bebd44d9ade692fca5d9a54958de41
|
||||
size 3133863
|
||||
oid sha256:3669e463e683f29c68616249df694e042077eb6a799ae8c4426fdea19a8841ec
|
||||
size 3133698
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:db951021fae9e36cb4363a7537f130a74f4470522303ea1a7ee363cc1f07178b
|
||||
size 854942
|
||||
oid sha256:fb45c4a72225c50b4a11465fedce1315a8f3f785d80cc09dcf4414634aa56382
|
||||
size 855000
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bb9179c70f210380143adb389968fd8543c479aa2f3adbc48274c8748db46479
|
||||
size 1779038
|
||||
oid sha256:a6b5266e6cdda57f7deaa26963a8fa8937875128897063ac473f10db5c13696d
|
||||
size 1779376
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2cb38625cb248fba81f489c7f076a405d3887ce8b9f2d200ea9ecb5a90f42f6b
|
||||
size 1182141
|
||||
oid sha256:58fdc2fcb056ff6338a43627cb9ebf176f0e0b8949874dfb1b2800548cc2ab1a
|
||||
size 1182749
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d38a8891be0da5d81c61f5fefaf02d7ffaa7f83ef626dbd75cca5181900859ee
|
||||
size 4769997
|
||||
oid sha256:5fbfff79f35d7674c48c878680c224ea98b9900731cf2524e37ac861204fd091
|
||||
size 4771789
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6322a3bc5ca2e687787d3cc16e33cacbafa70e8fa5936c97e6bee05c80e0354a
|
||||
size 784750
|
||||
oid sha256:36a22afc73a5ab1ab817183596f2222e7837f82e3daaf81220b6d798010dd01e
|
||||
size 784878
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7d3be0e15fc1106578d539e784ca8b3a25cc83e7b42e058e273753cfb35fc776
|
||||
size 3356161
|
||||
oid sha256:9788ad22b7d4808b3fb0ef447fc1574de46132ad4b101455c27b2a4336d5aef0
|
||||
size 3356277
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f9fad8d4ed79779707012c032d7537989e750b980f1cbe5a7ec50e6d939b5475
|
||||
size 868847
|
||||
oid sha256:b543758f2e6c9b779ec3b9a1856a414292fd393dc348e6ba3645ad3e5ab5c95a
|
||||
size 869001
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9c6e072a407b5187c84979cb2745aff3c50f5ba0cda50fb709f92f8fe9ec9723
|
||||
size 4801300
|
||||
oid sha256:8836ff3b83cf43d4d643b10d8a0a4daabc754f4a4eb946657618fe3fc0c17f37
|
||||
size 4801338
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:318ea713429dbbc043e3e0389a141d2b42719c7b8e6094100ace8434c365de1f
|
||||
size 773237
|
||||
oid sha256:5ed07dacadb8852b059682354b5255eb11b53907b10bf489bdfe922ae317850c
|
||||
size 773346
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f352101d02d81e5b3d0c80c9fb12b53568d05ab27f5065b812868278a72e6ac9
|
||||
size 3249101
|
||||
oid sha256:04d26e91a10a23d9ca25ee87235ab889b973428d02e331cdec1273fe39cdabe7
|
||||
size 3249281
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2a6f77338211e4e6dc437495d4f875ef0004319452cb99b54421cfa63fe9be87
|
||||
oid sha256:53b7e111a62214f27391cecf91ae384f4fb83b62bffe36c40e87c8744874dfdd
|
||||
size 876364
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d6b4b219f948e1e6dceaa5c51f0d14a9d71767c078d4ee5fb9878f56d96524eb
|
||||
size 1826455
|
||||
oid sha256:2d5f077c9756ad7f650f0ca99024b7d660ddbb667c3b32435a880ad1fff0a2ee
|
||||
size 1827124
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e4928d03fe0c4d2a189b220744ea6a0126656403efdeeedb4664f779b2b8a4bd
|
||||
size 1210230
|
||||
oid sha256:396095cf853c678dcaa6601868f43428c1e234892a2792212a7c5d69ef4a1c56
|
||||
size 1210789
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:453a92b00d870f36c9d5351ffdd2a7bd670a388266acb4aee0d24322c4c0e728
|
||||
size 4881893
|
||||
oid sha256:927f7cef9a139f99aab6f73b8695dcce9ecee9d68fc415aea012985797d35cfc
|
||||
size 4884021
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0566fc8b5db632bdc664627069d68822fc41dd9d0a3338c0219be5aa29f3a1dc
|
||||
size 804970
|
||||
oid sha256:f1dc907de8efeba3cd236c2b60c3d3d9601e264b4dcc8c2c59b262faef281a44
|
||||
size 804999
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ea2f79826d485b592c5a2f4cd2df1ed65d137033f17b4a0b9a2da3d188912a5c
|
||||
size 3447761
|
||||
oid sha256:596019a4d9dcba7567aa52b32788f1ecc067d3dbedc6ce1f797c52d979002a06
|
||||
size 3447782
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:65c37aa037c3b2bde7045efa673083c87e681833b813aab2d5b0436f5a6e1fea
|
||||
size 890664
|
||||
oid sha256:c7fe92822f26bb049d8d3f97b37f3f15089cb7beb769e2f4279f7954b6d507a8
|
||||
size 890905
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ac4ee862ba0848c1eece8399796d39460e069c256e626041d9174fabe07c1c07
|
||||
size 4927975
|
||||
oid sha256:aa6f104e81268e7055849d7f134df5fad8ccb4e390225cdc41ca3b69bf252643
|
||||
size 4928388
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7a2fc852f4b4e49c423f8fe3681a637520c07f01cf41ab1543b0b77aa0aa7548
|
||||
size 793381
|
||||
oid sha256:d9725a309e73e38d9955508e84a4784fa94baf0a9ef1991fa80387f604b4bc8c
|
||||
size 793485
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b1596325612041399f1a02d3d6a61a468261b8f31a32688aca6ead8dfa6e52f0
|
||||
size 3340526
|
||||
oid sha256:c8ff612fd7785ef832c65a3da9b2c8c1805f832612475a93e77682891597e86e
|
||||
size 3340717
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:85d53b78848ed9ebb59ecff439d15b5bc3304a6d5c233a32b79afa9026914796
|
||||
size 1039161
|
||||
oid sha256:515f3b95567c11d6483a083de32a0121f7a0127a4a55760d2d7db613c3c40b82
|
||||
size 1039194
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3b40b79fc0d6380b4a55334fd7be588b3d1ef81cd715206682242eb01498484a
|
||||
size 1887462
|
||||
oid sha256:efe390ac24d334acec84f25babbf5b07bb9ca67c2910495161b4d4040a9c70fb
|
||||
size 1887116
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c331b2febd2adc986cbc17dd5f181c99f59a6b4dc7114818d61ba3d408c185e8
|
||||
size 1459775
|
||||
oid sha256:1fb7bf9b6d084e8af49d4a4f99200d8d59dd0921d6290136895de849d969d3ad
|
||||
size 1456504
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ca3b0c4be73b0d83ef1279e4b79a573051f0132159897691c8c26caab6379de7
|
||||
size 5625835
|
||||
oid sha256:cab1ff5a70896b337427cf2f0bcf2f32d40eb1c437839915cb7d1e55742b1133
|
||||
size 5642431
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:26fe00bccbd6fde9bc77aede4e091199f4e1e6ec5ae9b396dfd93eca9a6824ea
|
||||
size 937531
|
||||
oid sha256:e3bbdf22f7d2d1637b0d4f310eb8a32396f378cde955919b70551dcc5da531b7
|
||||
size 937804
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:55efeb3e6cc2dc6109ce417f44de4ae37398874e7ed1504c8f396ef3e7f09b57
|
||||
size 3893245
|
||||
oid sha256:a69de89c81d96d683f2734455aa1c81f2f60940e83c586a936ea7bcade032b3d
|
||||
size 3893395
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:766f0f7ba38a23119211081b4cc0db79c6dde9b35dae046bf12c91c214595147
|
||||
size 1047545
|
||||
oid sha256:1d28cccaeb1938bd93dbf9f7069033f3af7989866292d6163382234ee764d6ca
|
||||
size 1047664
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2851d74d03ed335c386f1e703e9f9a67b8747869e240682fb5a3e1955d5aa89c
|
||||
size 5633645
|
||||
oid sha256:bcba3a18466768ca566d3588925c564803033d213f35ae79c4f8fbb0fd4373dc
|
||||
size 5633994
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1f739cf8031aa9eaa9372ffb0dcb5d4fbc656acf5b5714130b5fce33f12da02d
|
||||
size 926326
|
||||
oid sha256:4cb8d9b749f38a8b313b33b63ded9b5839f69fbb48152e38c9eecc9f44849d19
|
||||
size 926383
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:19e1aabc7ce7c640a5645c9299b7250558f8f69ed8b4634f442ba4f2438d29d5
|
||||
size 3791303
|
||||
oid sha256:639d925eae0c07439165faba0f9690edcb1bb8178b67c33e475be34bda791fe8
|
||||
size 3791974
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c087f05fdcccd94edcee8377dc5ad46bec01d0bb41fd9f82ba92022d40e59973
|
||||
size 660753
|
||||
oid sha256:7f10ca82a8cf4e861a475304476470db8b1d1506c98fd793ae2cd1378308fa0e
|
||||
size 660892
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:dbc8eee7254b0a7ff30ed479ec461bfd70c97f74294b92329cecd95c9577213d
|
||||
size 1322001
|
||||
oid sha256:1aaccb203149b14c5f8c2da8217aea48900d183218266671a05c8f9a11c7c1e1
|
||||
size 1322817
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b2c3e38e77a5505da63e47a5040e375c08c7a6eb6a2543494b4211b5767f374c
|
||||
size 943954
|
||||
oid sha256:56392e75bedd95e8ad23d0f2ce54d498b33a8486fdb0627d75f3721240dec30e
|
||||
size 939875
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:375fee43ca51db3b5965048893130885d3eef253d3fdf76cfa063c91918b8145
|
||||
size 3727962
|
||||
oid sha256:aa7829a8e1be18d67c9c4f40633b86b1eff4eb65d34688f7a93825f20793066e
|
||||
size 3730188
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:345f2e51f9ce8bd1d8f67ece73b49994fa9d76db950528937b39f3beb0106888
|
||||
size 614546
|
||||
oid sha256:a43530d9ebf23ea217cd39733b0687b3d6501db3fd883560e0c297d090b4ef75
|
||||
size 614591
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bcdcd34e591d520905dda060cacead8f95c2de9662a909aab08a8c3ceddde9fc
|
||||
size 2537124
|
||||
oid sha256:1e645c85ee2a9d4fbfd59ab45a4c065eef648b878ef35bc0f8548ab8a385e566
|
||||
size 2537165
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b3e07101ad83f4b0e5c86d9a55c68ca152b52d0733cbd3c8a6d815e434ecbd8e
|
||||
size 674209
|
||||
oid sha256:c307a8e3e2bd2f54cbec89d0508f02d8cf509e2f859b772049e6a022ccbea8b1
|
||||
size 674328
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2b4966c6766ef713bdd6eb82faa81aa338b64420191bab2f1be2f6acf3002bd9
|
||||
size 3609182
|
||||
oid sha256:d1f0a93a94cbe908add76fdb80942b3ae79e785d3eda63cb2c9ab60b3f93cc61
|
||||
size 3609650
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:16ad9bd59e235e162a14e7d02b5f068accfb901eab828eaa33a4e6e6dca0d8c5
|
||||
size 605835
|
||||
oid sha256:2cc054006199910d18e03bea293cde1b4da185c8f13b0782310f337654be22e4
|
||||
size 605882
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5ac397b64d84c29e1e6293052fb6ada8d1dc16aad480b5a2b90c89d69ff370ff
|
||||
size 2433893
|
||||
oid sha256:aeb67a3c30b32c83cfe24a3e33c0c2abf301f73fc213aa6ea56f09dfb86ee468
|
||||
size 2433828
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bab18dfe79bf316dee20e5b82c5eeecdfd246c95b51b1017b02511befb89c6ff
|
||||
size 1011465
|
||||
oid sha256:7facdd2ba7b1d50df5317124d8a5067eff0d02804a103e275d1ad0720f017b6f
|
||||
size 1011737
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:077f324f13c33d5e4f03aa9e4056d65d02055751eddb573080ba80cacfb8e80a
|
||||
size 2019736
|
||||
oid sha256:21f01134f563ffd276c638564b628a55fd77d83a78cc1569be7238565c46305a
|
||||
size 2020079
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:61ef3b3ee20f8eb97131e0404089a2a3c65a4f09f8bd6c7dcc8ad365afd45361
|
||||
size 1389613
|
||||
oid sha256:a59d08b4f31e0a75b8c1e743c6d4225f55a1462c52df002087963bc276c95270
|
||||
size 1394277
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:53e824fad28960890923e7d64bb87c69a2f60bca251e02f618e13668baf28f9b
|
||||
size 5646238
|
||||
oid sha256:f517950bc249fbc4fa5f231a4972695f1ab03ea04c4ee6983813bef6bfce2e5f
|
||||
size 5667701
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6bf9474ca946d02fbe721d20c154eea6fd94e46a6320a0563e22c4a12a3788b3
|
||||
size 935943
|
||||
oid sha256:949c59a87a342b15cf01cc730879897bfe05628840a25f7db4f236a656510245
|
||||
size 936161
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:88a7c0ac0fe56ab832a146abeec1aa97e8ac66e96a09a1e20267589a699e078f
|
||||
size 4034014
|
||||
oid sha256:fa08e5c341b0cf41ca7dc17427de19ec50a2094bbabbbe1756f0a6a037e3cb49
|
||||
size 4034442
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:62b728def6921fff5d0aeb4de45aa11fff12d975e4916bd0225964333a2eb631
|
||||
size 1026014
|
||||
oid sha256:525d5659b9e27040b6ed76e41b048fa9444c64004b43723a28e3abd0db65f6d1
|
||||
size 1026345
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c9b443c93d6500b9cb01ade1d2b190562e16d32e27ae2e209b6e6ca6f826b486
|
||||
size 5734709
|
||||
oid sha256:033edf091838b2212a99fd3a0b41484573603ad78682ef1da58d9a49de415e2b
|
||||
size 5734204
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c8eaa801baa1b20e76daa00b73f36dff3366b752f87bc1b0815d18d987c7d676
|
||||
size 923599
|
||||
oid sha256:3fb7ca6e225568be031ad599fadb489eeaa41d054c81a1685978247aaff43831
|
||||
size 923594
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8d79a91ece9749c15b922efd2a39f293ced33bd0b49c0b1e42048bb7bd96b014
|
||||
size 3922206
|
||||
oid sha256:6f98c9f2edebf7844e18bd58507d7b45f06912753661c1b4317204ab9cdb65e7
|
||||
size 3922109
|
||||
|
||||
@@ -25,6 +25,7 @@ children:
|
||||
- /managing-the-default-branch-name-for-your-repositories
|
||||
- /managing-security-and-analysis-settings-for-your-personal-account
|
||||
- /managing-access-to-your-personal-accounts-project-boards
|
||||
- /managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
|
||||
- /integrating-jira-with-your-personal-projects
|
||||
- /what-does-the-available-for-hire-checkbox-do
|
||||
shortTitle: Ajustes de cuenta personal
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Managing your cookie preferences for GitHub's enterprise marketing pages
|
||||
intro: 'You can control how {% data variables.product.company_short %} uses information from non-essential tracking cookies for enterprise marketing pages.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Manage cookie preferences
|
||||
---
|
||||
|
||||
## About cookie preferences on enterprise marketing pages
|
||||
|
||||
{% data variables.product.company_short %} may use non-essential cookies on some enterprise marketing pages. You can customize how these cookies behave. For more information about how {% data variables.product.company_short %} uses cookies, see "[{% data variables.product.company_short %} Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement)."
|
||||
|
||||
## Changing your cookie preferences
|
||||
|
||||
You can customize how non-essential cookies behave on any {% data variables.product.company_short %} enterprise marketing page.
|
||||
|
||||
1. Navigate to the {% data variables.product.company_short %} enterprise marketing page where you'd like to change your cookie preferences. For example, navigate to [{% data variables.product.company_short %} Resources](https://resources.github.com/).
|
||||
1. Scroll to the bottom of the page, then click **Manage Cookies**.
|
||||
|
||||
|
||||
|
||||
1. Under "Manage cookie preferences," to accept or reject each non-essential cookie, click **Accept** or **Reject**.
|
||||
|
||||
|
||||
|
||||
1. Haz clic en **Guardar cambios**.
|
||||
|
||||
|
||||
@@ -71,7 +71,7 @@ You can add self-hosted runners at the organization level, where they can be use
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runners %}
|
||||
1. Click **New runner**.
|
||||
{% ifversion actions-hosted-runners %}1. Click **New runner**, then click **New self-hosted runner**.{% else %}1. Click **New runner**.{% endif %}
|
||||
{% data reusables.actions.self-hosted-runner-configure %}
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
|
||||
@@ -23,7 +23,7 @@ shortTitle: Ejecutar la app del ejecutor al inicio
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)".
|
||||
**Nota:** Debes agregar un ejecutor a {% data variables.product.product_name %} antes de que puedas configurar la aplicación de ejecutor auto-hospedado como servicio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)".
|
||||
|
||||
{% endnote %}
|
||||
{% endcapture %}
|
||||
@@ -34,7 +34,7 @@ shortTitle: Ejecutar la app del ejecutor al inicio
|
||||
|
||||
{{ service_nonwindows_intro }}
|
||||
|
||||
For Linux systems that use `systemd`, you can use the `svc.sh` script that is created after successfully adding the runner to install and manage using the application as a service.
|
||||
Para los sistemas Linux que utilizan `systemd`, puedes utilizar el script de `svc.sh` que se creó después de agregar el ejecutor con éxito para instala y administrar utilizando la aplicación como servicio.
|
||||
|
||||
{{ service_non_windows_intro_shell }}
|
||||
|
||||
|
||||
@@ -9,215 +9,65 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
shortTitle: Administrar el acceso a los ejecutores
|
||||
shortTitle: Using runner groups
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Acerca de los grupos de ejecutores auto-hospedados
|
||||
## About runner groups
|
||||
|
||||
{% ifversion fpt %}
|
||||
{% note %}
|
||||
|
||||
**Nota:** Todas las organizaciones tienen un solo grupo de ejecutores auto-hospedados predeterminado. Solo las cuentas empresariales y las organizaciones que pretenezcan a estas pueden crear y administrar grupos de ejecutores auto-hospedados adicionales.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Los grupos de ejecutores auto-hospedados se utilizan para controlar el acceso a los ejecutores auto-hospedados. Los administradores de las organizaciones pueden configurar políticas de acceso que controlen qué repositorios en una organización tienen acceso al grupo de ejecutores.
|
||||
Si utilizas
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %}, puedes crear grupos de ejecutores adicionales; los administradores empresariales pueden configurar políticas de acceso que controlen qué organizaciones dentro de una empresa pueden acceder al grupo de ejecutores y los administradores organizacionales pueden asignar políticas de acceso granulares de repositorio para el grupo de ejecutores empresarial. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
|
||||
{% endif %}
|
||||
{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
Los grupos de ejecutores auto-hospedados se utilizan para controlar el acceso a los ejecutores auto-hospedados a nivel de empresas y organizaciones. Los propietarios de empresas pueden configurar políticas de acceso que controlan qué organizaciones
|
||||
{% ifversion restrict-groups-to-workflows %}y flujos de trabajo {% endif %}en una empresa tienen acceso al grupo de ejecutores. Los propietarios de las organizaciones pueden configurar las políticas de acceso que controlan qué repositorios{% ifversion restrict-groups-to-workflows %} y flujos de trabajo{% endif %} en una organización tienen aceso al grupo de ejecutores.
|
||||
|
||||
Cuando un propietario de empresa otorga un acceso organizacional a un grupo de ejecutores, los propietarios de organizaciones pueden verlo listado en los ajustes del ejecutor auto-hospedado de la organización. Los propietarios organizacionales pueden entonces asignar políticas de acceso adicionales y granulares para los repositorios{% ifversion restrict-groups-to-workflows %} y flujos de trabajo{% endif %} al grupo ejecutor de la empresa.
|
||||
|
||||
Cuando se crean nuevos ejecutores, se asignan automáticamente al grupo predeterminado. Los ejecutores solo pueden estar en un grupo a la vez. Puedes mover los ejecutores del grupo predeterminado a otro grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](#moving-a-self-hosted-runner-to-a-group)".
|
||||
|
||||
## Crear un grupo de ejecutores auto-hospedados para una organización
|
||||
|
||||
Todas las organizaciones tienen un solo grupo predeterminado de ejecutores auto-hospedados. Las organizaciones dentro de una cuenta empresarial pueden crear grupos auto-hospedados adicionales. Los administradores de la organización pueden permitir el acceso de los repositorios individuales a un grupo de ejecutores. Para obtener más información sobre cómo crear un grupo de ejecutores auto-hospedados con la API de REST, consulta la sección "[Grupos de ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runner-groups)".
|
||||
{%- ifversion ghec or ghes %}
|
||||
|
||||
Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser mimebros de un grupo a la vez. Puedes mover un ejecutor del grupo predeterminado a cualquier grupo que crees.
|
||||
{% data reusables.actions.self-hosted-runner-security-admonition %}
|
||||
|
||||
Cuando creas un grupo, debes elegir la política que define qué reositorios{% ifversion restrict-groups-to-workflows %} y flujos de trabajo{% endif %} tienen acceso al grupo ejecutor.
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
|
||||
1. En la sección de "Grupos de ejecutores", haz clic en **Grupo de ejecutores nuevo**.
|
||||
1. Ingresa un nombre para tu grupo ejecutor.
|
||||
{% data reusables.actions.runner-group-assign-policy-repo %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Advertencia**: {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
|
||||
|
||||
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
|
||||
|
||||
{% endwarning %}
|
||||
{% data reusables.actions.runner-group-assign-policy-workflow %}{%- ifversion restrict-groups-to-workflows %}Los grupos ejecutores que pertenecen a las organizaciones no pueden acceder a los flujos de trabajo de una organización diferente en la empresa. En vez de esto, debes crear un grupo de ejecutores que pertenezca a la empresa.{% endif %}
|
||||
{% data reusables.actions.self-hosted-runner-create-group %}
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
|
||||
1. Debajo de {% ifversion ghes or ghae %}"Ejecutores"{% endif %}, haz clic en **Agregar nuevo** y luego en **Grupo nuevo**.
|
||||
|
||||
|
||||
1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio.
|
||||
|
||||
Puedes configurar un grupo de ejecutores para que sea accesible a una lista específica de repositorios o a todos ellos en la organización.{% ifversion ghec or ghes %} Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo ejecutor. Pero esto se puede anular. Esta configuración no puede anularse si se configura un grupo ejecutor de la organización que haya compartido una empresa.{% endif %}
|
||||
|
||||
{%- ifversion ghes %}
|
||||
{% warning %}
|
||||
|
||||
**Advertencia**:
|
||||
|
||||
{% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
|
||||
|
||||
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
|
||||
|
||||
{% endwarning %}
|
||||
{%- endif %}
|
||||
|
||||
|
||||
1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política.
|
||||
{% endif %}
|
||||
{% data reusables.actions.creating-a-runner-group-for-an-organization %}
|
||||
|
||||
## Crear un grupo de ejecutores auto-hospedados para una empresa
|
||||
|
||||
Las empresas pueden agregar sus ejecutores auto-hospedados a grupos para su administración de accesos. Las empresas pueden crear grupos de ejecutores auto-hospedados que son accesibles para organizaciones específicas en la cuenta empresarial{% ifversion restrict-groups-to-workflows %} o para flujos de trabajo específicos{% endif %}. Los propietarios de organizaciones pueden entonces asignar políticas de acceso adicionales y granulares para los repositorios{% ifversion restrict-groups-to-workflows %} o flujos de trabajo{% endif %} a los grupos de ejecutores empresariales. Para obtener más información sobre cómo crear un grupo de ejecutores auto-hospedados con la API de REST, consulta las terminales empresariales en la [API de REST de {% data variables.product.prodname_actions %}](/rest/reference/actions#self-hosted-runner-groups).
|
||||
{%- ifversion ghec or ghes %}
|
||||
|
||||
Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser mimebros de un grupo a la vez. Puedes asignar el ejecutor a un grupo específico durante el proceso de registro o puedes moverlo después desde el grupo predeterminado a un grupo personalizado.
|
||||
{% data reusables.actions.self-hosted-runner-security-admonition %}
|
||||
|
||||
Cuando creas un grupo, debes elegir la política que defina qué organizaciones tienen acceso al grupo de ejecutores.
|
||||
{%- endif %}
|
||||
|
||||
{% data reusables.actions.self-hosted-runner-groups-add-to-enterprise-first-steps %}
|
||||
1. Para elegir una política para el acceso organizacional, selecciona el menú desplegable **Acceso organizacional** y haz clic en una política. Puedes configurar un grupo de ejecutores para que sea accesible a una lista de organizaciones específica o a todas las organizaciones en la empresa.{% ifversion ghes %} Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo, pero esto se puede anular.{% endif %}
|
||||
|
||||
{%- ifversion ghec or ghes %}
|
||||
{% warning %}
|
||||
|
||||
**Advertencia**:
|
||||
|
||||
{% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
|
||||
|
||||
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
|
||||
|
||||
{% endwarning %}
|
||||
{%- endif %}
|
||||
{%- ifversion ghec or ghes %}
|
||||
|
||||
|
||||
{%- elsif ghae %}
|
||||
|
||||
|
||||
{%- endif %}
|
||||
{% data reusables.actions.runner-group-assign-policy-workflow %}
|
||||
1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política.
|
||||
{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Cambiar la política de acceso de un grupo de ejecutores auto-hospedados
|
||||
|
||||
En el caso de los grupos de ejecutores en una empresa, puedes cambiar qué organizaciones dentro de ella pueden acceder a un grupo de ejecutores{% ifversion restrict-groups-to-workflows %} o restringir qué flujos de trabajo puede ejecutar un grupo de ejecutores{% endif %}. En el caso de los grupos de ejecutores en una organización, puedes cambiar qué repositorios en ella pueden acceder a un grupo de ejecutores{% ifversion restrict-groups-to-workflows %} o restringir qué flujos de trabajo puede ejecutar un grupo de ejecutores{% endif %}.
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
|
||||
### Cambiar qué organizaciones o repositorios pueden acceder a un grupo de ejecutores
|
||||
{% data reusables.actions.self-hosted-runner-security-admonition %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
|
||||
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
|
||||
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
|
||||
1. En el caso de los grupos de ejecutores en una empresa, debajo de **Acceso organizacional**, modifica qué organizaciones pueden acceder al grupo de ejecutores. En el caso de los grupos de ejecutores en una organización, debajo de **Acceso al repositorio**, modifica aquellos a los que puede acceder este grupo.
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes %}
|
||||
{% warning %}
|
||||
|
||||
**Advertencia**:
|
||||
|
||||
{% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
|
||||
|
||||
Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
|
||||
|
||||
{% endwarning %}
|
||||
{%- endif %}
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
{% data reusables.actions.self-hosted-runner-configure-runner-group-access %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion restrict-groups-to-workflows %}
|
||||
### Cambiar los flujos de trabajo a los cuales puede acceder un grupo de ejecutores
|
||||
Puedes configurar un grupo de ejecutores auto-hospedado para que ejecute ya sea flujos selectos o todos ellos. Por ejemplo, podrías utilizar este ajuste para proteger secretos almacenados en los ejecutores auto-hospedados o estandarizar los flujos de trabajo de despliegue restringiendo un grupo de ellos para que ejecute solo un flujo de trabajo reutilizable específico. Este ajuste no se puede anular si estás configurando un grupo de ejecutores de una organización que haya compartido una empresa.
|
||||
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
|
||||
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
|
||||
1. Debajo de **Acceso al flujo de trabajo**, selecciona el menú desplegable y haz clic en **Flujos de trabajo selectos**.
|
||||
1. Da clic en {% octicon "gear" aria-label="the gear icon" %}.
|
||||
1. Ingresa una lista separada por comas de los flujos de trabajo que pueden acceder al grupo de ejecutores. Utiliza la ruta completa, incluyendo el nombre y propietario del repositorio. Fija el flujo de trabajo a una rama, etiqueta o SHA completo. Por ejemplo: `octo-org/octo-repo/.github/workflows/build.yml@v2, octo-org/octo-repo/.github/workflows/deploy.yml@d6dc6c96df4f32fa27b039f2084f576ed2c5c2a5, monalisa/octo-test/.github/workflows/test.yml@main`.
|
||||
|
||||
Solo los jobs que se definan directamente dentro de los flujos de trabajo seleccionados tendrán acceso al grupo de ejecutores.
|
||||
|
||||
Los grupos de ejecutores que pertenecen a la organización no pueden acceder a los flujos de trabajo de otra organización de la empresa; en vez de esto, debes crear un grupo de ejecutores que pertenezca a la empresa.
|
||||
|
||||
1. Haz clic en **Save ** (guardar).
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
|
||||
|
||||
## Cambiar el nombre de un grupo de ejectuores
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
|
||||
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
|
||||
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
|
||||
1. Cambia el nombre del grupo de ejecutores.
|
||||
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
{% data reusables.actions.self-hosted-runner-configure-runner-group %}
|
||||
1. Cambia el nombre del grupo de ejecutores.
|
||||
{% endif %}
|
||||
{% data reusables.actions.changing-the-name-of-a-runner-group %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
## Agregar ejecutores auto-hospedados a un grupo automáticamente
|
||||
|
||||
Puedes utilizar el script de configuración para agregar automáticamente un ejecutor auto-hospedado nuevo a un grupo. Por ejemplo, este comando registra un ejecutor auto-hospedado nuevo y utiliza el parámetro `--runnergroup` para agregarlo a un grupo llamado `rg-runnergroup`.
|
||||
|
||||
```sh
|
||||
./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup
|
||||
```
|
||||
|
||||
El comando fallará si el grupo de ejecutores no existe:
|
||||
|
||||
```
|
||||
Could not find any self-hosted runner group named "rg-runnergroup".
|
||||
```
|
||||
{% data reusables.actions.automatically-adding-a-runner-to-a-group %}
|
||||
|
||||
## Mover un ejecutor auto-hospedado a un grupo
|
||||
|
||||
Si no especificas un grupo de ejecutores durante el proceso de registro, tus ejecutores auto-hospedados nuevos se asignarán automáticamente al grupo predeterminado y después se moverán a otro grupo.
|
||||
|
||||
{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
|
||||
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
|
||||
1. En la lista de "Ejecutores", haz clic en aquél que quieras configurar.
|
||||
2. Selecciona el menú desplegable de **Grupo de ejecutores**.
|
||||
3. En "Mover el ejecutor al grupo", elige un grupo destino para el ejecutor.
|
||||
{% elsif ghae or ghes < 3.4 %}
|
||||
1. En la sección {% ifversion ghes or ghae %}"Grupos de ejecutores"{% endif %} de la página de ajustes, ubica el grupo actual del ejecutor que quieras mover y expande la lista de miembros del grupo. 
|
||||
2. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. 
|
||||
3. Para mover el ejecutor, da clic en el grupo de destino. 
|
||||
{% endif %}
|
||||
{% data reusables.actions.moving-a-runner-to-a-group %}
|
||||
|
||||
## Eliminar un grupo de ejecutores auto-hospedados
|
||||
|
||||
Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina.
|
||||
|
||||
{% ifversion ghes or ghae or ghec %}
|
||||
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
|
||||
1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
|
||||
2. Para eliminar el grupo, da clic en **Eliminar grupo**.
|
||||
3. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
|
||||
{% data reusables.actions.removing-a-runner-group %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Entender las GitHub Actions
|
||||
shortTitle: Entendiendo las GitHub Actions
|
||||
intro: 'Aprende lo básico de las {% data variables.product.prodname_actions %}, incluyendo los conceptos nucleares y la terminología esencial.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
|
||||
- /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
|
||||
@@ -82,7 +83,7 @@ Para obtener más información, consulta la sección "[Crear acciones](/actions/
|
||||
|
||||
### Ejecutores
|
||||
|
||||
{% data reusables.actions.about-runners %} Cada ejecutor puede ejecutar un job individual a la vez. {% ifversion ghes or ghae %} Debes hospedar tus propios ejecutores para {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} proporciona ejecutores de Ubuntu Linux, Microsoft Windows y macOS para ejecutar tus flujos de trabajo; cada flujo de trabajo se ejecuta en una máquina virtual nueva y recién aprovisionada. Si necesitas un sistema operativo diferente o si requieres una configuración de hardware específica, puedes hospedar tus propios ejecutores.{% endif %} Para obtener más información{% ifversion fpt or ghec %} sobre los ejecutores auto-hospedados{% endif %}, consulta la sección "[Hospedar tus propios ejecutores](/actions/hosting-your-own-runners)".
|
||||
{% data reusables.actions.about-runners %} Cada ejecutor puede ejecutar un job individual a la vez. {% ifversion ghes or ghae %} Debes hospedar tus propios ejecutores para {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} proporciona ejecutores de Ubuntu Linux, Microsoft Windows y macOS para ejecutar tus flujos de trabajo; cada flujo de trabajo se ejecuta en una máquina virtual nueva y recién aprovisionada. {% ifversion actions-hosted-runners %} {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)." {% endif %}If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
|
||||
|
||||
{% data reusables.actions.workflow-basic-example-and-explanation %}
|
||||
|
||||
|
||||
@@ -86,6 +86,15 @@ While the job runs, the logs and output can be viewed in the {% data variables.p
|
||||
|
||||
## Supported runners and hardware resources
|
||||
|
||||
{% ifversion actions-hosted-runners %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
Hardware specification for Windows and Linux virtual machines:
|
||||
- 2-core CPU (x86_64)
|
||||
- 7 GB of RAM
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Controlling access to larger runners
|
||||
intro: 'Puedes utilizar políticas para limitar el acceso a los {% data variables.actions.hosted_runner %} que se hayan agregado a una organización o empresa.'
|
||||
product: '{% data reusables.gated-features.hosted-runners %}'
|
||||
versions:
|
||||
feature: actions-hosted-runners
|
||||
type: tutorial
|
||||
shortTitle: 'Controlling access to {% data variables.actions.hosted_runner %}s'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About runner groups
|
||||
|
||||
{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
|
||||
## Creating a runner group for an organization
|
||||
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.creating-a-runner-group-for-an-organization %}
|
||||
|
||||
## Creating a runner group for an enterprise
|
||||
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Changing the access policy of a runner group
|
||||
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
|
||||
|
||||
## Cambiar el nombre de un grupo de ejectuores
|
||||
|
||||
{% data reusables.actions.changing-the-name-of-a-runner-group %}
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
## Moving a runner to a group
|
||||
|
||||
{% data reusables.actions.moving-a-runner-to-a-group %}
|
||||
|
||||
## Removing a runner group
|
||||
|
||||
{% data reusables.actions.removing-a-runner-group %}
|
||||
|
||||
{% endif %}
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
ghes: '*'
|
||||
children:
|
||||
- /about-github-hosted-runners
|
||||
- /using-larger-runners
|
||||
- /controlling-access-to-larger-runners
|
||||
- /monitoring-your-current-jobs
|
||||
- /customizing-github-hosted-runners
|
||||
- /connecting-to-a-private-network
|
||||
|
||||
@@ -0,0 +1,135 @@
|
||||
---
|
||||
title: Using larger runners
|
||||
intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
product: '{% data reusables.gated-features.hosted-runners %}'
|
||||
versions:
|
||||
feature: 'actions-hosted-runners'
|
||||
shortTitle: Using {% data variables.actions.hosted_runner %}s
|
||||
---
|
||||
|
||||
## Overview of {% data variables.actions.hosted_runner %}s
|
||||
|
||||
In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources), {% data variables.product.prodname_dotcom %} also offers customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} plans a range of {% data variables.actions.hosted_runner %}s with more RAM and CPU. These runners are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.
|
||||
|
||||
When you add a {% data variables.actions.hosted_runner %} to an organization, you are defining a type of machine from a selection of available hardware specifications and operating system images. {% data variables.product.prodname_dotcom %} will then create multiple instances of this runner that scale up and down to match the job demands of your organization, based on the autoscaling limits you define.
|
||||
|
||||
## Architectural overview of {% data variables.actions.hosted_runner %}s
|
||||
|
||||
The {% data variables.actions.hosted_runner %}s are managed at the organization level, where they are arranged into groups that can contain multiple instances of the runner. They can also be created at the enterprise level and shared with organizations in the hierarchy. Once you've created a group, you can then add a runner to the group and update your workflows to target the label assigned to the {% data variables.actions.hosted_runner %}. You can also control which repositories are permitted to send jobs to the group for processing. For more information about groups, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
|
||||
|
||||
In the following diagram, a class of hosted runner named `ubuntu-20.04-16core` has been defined with customized hardware and operating system configuration.
|
||||
|
||||
|
||||
|
||||
1. Instances of this runner are automatically created and added to a group called `ubuntu-20.04-16core`.
|
||||
2. The runners have been assigned the label `ubuntu-20.04-16core`.
|
||||
3. Workflow jobs use the `ubuntu-20.04-16core` label in their `runs-on` key to indicate the type of runner they need to execute the job.
|
||||
4. {% data variables.product.prodname_actions %} checks the runner group to see if your repository is authorized to send jobs to the runner.
|
||||
5. The job runs on the next available instance of the `ubuntu-20.04-16core` runner.
|
||||
|
||||
## Autoscaling {% data variables.actions.hosted_runner %}s
|
||||
|
||||
Your {% data variables.actions.hosted_runner %}s can be configured to automatically scale to suit your needs. When jobs are submitted for processing, more machines can be automatically provisioned to run the jobs, until reaching a pre-defined maximum limit. Each machine only handles one job at a time, so these settings effectively determine the number of jobs that can be run concurrently.
|
||||
|
||||
During the runner deployment process, you can configure the _Max_ option, which allows you to control your costs by setting the maximum parallel number of machines that are created in this set. A higher value here can help avoid workflows being blocked due to parallelism.
|
||||
|
||||
## Networking for {% data variables.actions.hosted_runner %}s
|
||||
|
||||
By default, {% data variables.actions.hosted_runner %}s receive a dynamic IP address that changes for each job run. Optionally, {% data variables.product.prodname_ghe_cloud %} customers can configure their {% data variables.actions.hosted_runner %}s to receive a static IP address from {% data variables.product.prodname_dotcom %}'s IP address pool. When enabled, instances of the {% data variables.actions.hosted_runner %} will receive an address from a range that is unique to the runner, allowing you to use this range to configure a firewall allowlist. You can use up to 10 static IP address ranges in total across all your {% data variables.actions.hosted_runner %}s.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If runners are unused for more than 30 days, their IP address ranges are automatically removed and cannot be recovered.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Planning for {% data variables.actions.hosted_runner %}s
|
||||
|
||||
### Create a runner group
|
||||
|
||||
Runner groups are used to collect sets of virtual machines and create a security boundary around them. You can then decide which organizations or repositories are permitted to run jobs on those sets of machines. During the {% data variables.actions.hosted_runner %} deployment process, the runner can be added to an existing group, or otherwise it will join a default group. You can create a group by following the steps in "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
|
||||
|
||||
### Understanding billing
|
||||
|
||||
Compared to standard {% data variables.product.prodname_dotcom %}-hosted runners, {% data variables.actions.hosted_runner %}s are billed differently. For more information, see "[Per-minute rates](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)".
|
||||
|
||||
## Adding a {% data variables.actions.hosted_runner %} to an enterprise
|
||||
|
||||
You can add {% data variables.actions.hosted_runner %}s to an enterprise, where they can be assigned to multiple organizations. The organization admins can then control which repositories can use the runners. To add a {% data variables.actions.hosted_runner %} to an enterprise, you must be an enterprise owner.
|
||||
|
||||
{% data reusables.actions.add-hosted-runner-overview %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-runners-tab %}
|
||||
{% data reusables.actions.add-hosted-runner %}
|
||||
1. To allow organizations to access your {% data variables.actions.hosted_runner %}s, you specify the list of organizations that can use it. For more information, see "[Managing access to your runners](#managing-access-to-your-runners)."
|
||||
|
||||
## Adding a {% data variables.actions.hosted_runner %} to an organization
|
||||
|
||||
You can add a {% data variables.actions.hosted_runner %} to an organization, where the organization admins can control which repositories can use it.
|
||||
|
||||
{% data reusables.actions.add-hosted-runner-overview %}
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runners %}
|
||||
{% data reusables.actions.add-hosted-runner %}
|
||||
1. To allow repositories to access your {% data variables.actions.hosted_runner %}s, add them to the list of repositories that can use it. For more information, see "[Managing access to your runners](#managing-access-to-your-runners)."
|
||||
|
||||
## Running jobs on your runner
|
||||
|
||||
Once your runner type has been been defined, you can update your workflows to send jobs to the runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
|
||||
```yaml
|
||||
name: learn-github-actions
|
||||
on: [push]
|
||||
jobs:
|
||||
check-bats-version:
|
||||
runs-on: ubuntu-20.04-16core
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses:{% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: '14'
|
||||
- run: npm install -g bats
|
||||
- run: bats -v
|
||||
```
|
||||
|
||||
## Managing access to your runners
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Before your workflows can send jobs to {% data variables.actions.hosted_runner %}s, you must first configure permissions for the runner group. See the following sections for more information.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Runner groups are used to control which repositories can run jobs on your {% data variables.actions.hosted_runner %}s. You must grant access to the group from each level of the management hierarchy, depending on where you've defined the {% data variables.actions.hosted_runner %}:
|
||||
|
||||
- **Runners at the enterprise level**: Configure the runner group to grant access to all the required organizations. In addition, for each organization, you must configure the group to specify which repositories are allowed access.
|
||||
- **Runners at the organization level**: Configure the runner group by specifying which repositories are allowed access.
|
||||
|
||||
For example, the following diagram has a runner group named `grp-ubuntu-20.04-16core` at the enterprise level. Before the repository named `octo-repo` can use the runners in the group, you must first configure the group at the enterprise level to allow access from the `octo-org` organization; you must then configure the group at the organization level to allow access from `octo-repo`:
|
||||
|
||||
|
||||
|
||||
### Allowing repositories to access a runner group
|
||||
|
||||
This procedure demonstrates how to configure group permissions at the enterprise and organization levels:
|
||||
|
||||
{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
|
||||
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
|
||||
- For runner groups in an enterprise: under **Organization access**, modify which organizations can access the runner group.
|
||||
- For runner groups in an organization: under **Repository access**, modify which repositories can access the runner group.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**:
|
||||
|
||||
{% data reusables.actions.hosted-runner-security %}
|
||||
|
||||
For more information, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
|
||||
|
||||
{% endwarning %}
|
||||
@@ -23,7 +23,7 @@ topics:
|
||||
|
||||
En vez de copiar y pegar desde un flujo de trabajo hacia otro, puedes hacer flujos de trabajo reutilizables. Tú y cualquiera que tenga acceso a un flujo de trabajo reutilizable pueden entonces llamarlo desde otro flujo.
|
||||
|
||||
El reutilizar flujos de trabajo evita la duplicación. Esto hace que los flujos de trabajo se puedan mantener más fácilmente y te permite crear flujos de trabajo nuevos más fácilmente compilando sobre el trabajo de los demás, tal como lo haces con las acciones. La reutilización de flujos de trabajo también promueve las mejores prácticas al ayudarte a utilizar los flujos de trabajo que están bien diseñados, que ya se han probado y cuya efectividad ya se comprobó. Tu organización puede crear una librería de flujos de trabajo reutilizables que puede mantenerse centralmente.
|
||||
El reutilizar flujos de trabajo evita la duplicación. Esto hace que los flujos de trabajo se puedan mantener más fácilmente y te permite crear flujos de trabajo nuevos más fácilmente compilando sobre el trabajo de los demás, tal como lo haces con las acciones. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proven to be effective. Tu organización puede crear una librería de flujos de trabajo reutilizables que puede mantenerse centralmente.
|
||||
|
||||
El siguiente diagrama muestra tres jobs de compilación en la parte izquierda del mismo. Después de que cada uno de estos jobs se complete con éxito, se ejecutará un job dependiente llamado "Deploy". Este job crea un flujo de trabajo reutilizable que contiene tres jobs: "Staging", "Review" y "Production". El job de despliegue "Production" solo se ejecuta después de que el job "Staging" se haya completado con éxito. El utilizar un flujo de trabajo reutilizable para ejecutar jobs de despliegue te permite ejecutarlos para cada compilación sin duplicar el código en los flujos de trabajo.
|
||||
|
||||
@@ -127,7 +127,7 @@ Puedes definir entradas y secretos, las cuales pueden pasarse desde el flujo de
|
||||
runs-on: ubuntu-latest
|
||||
environment: production
|
||||
steps:
|
||||
- uses: ./.github/workflows/my-action
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.envPAT }}
|
||||
@@ -168,12 +168,13 @@ jobs:
|
||||
name: Pass input and secrets to my-action
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: ./.github/workflows/my-action
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.token }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% ifversion actions-reusable-workflow-matrix %}
|
||||
## Utilizar una estrategia de matriz con un flujo de trabajo reutilizable
|
||||
|
||||
|
||||
@@ -19,6 +19,8 @@ Si configuras un nombre del host en lugar de una dirección IP codificada de for
|
||||
|
||||
La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. Por ejemplo, tu ajuste de nombre de host podría ser `github.companyname.com.` Las solicitudes web y de la API se redireccionarán automáticamente al nombre de host que se configuró en la {% data variables.enterprise.management_console %}. Toma en cuenta que `localhost` no es un ajuste válido de nombre de host.
|
||||
|
||||
Hostnames must be less than 63 characters in length per [Section 2.3.4 of the Domain Names Specification RFC](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.4).
|
||||
|
||||
Después de que configuras un nombre de host, puedes habilitar el aislamiento de subdominios para incrementar la seguridad de {% data variables.product.product_location %} aún más. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)."
|
||||
|
||||
Para obtener más información sobre los tipos de nombres de host compatibles, consulta la [Sección 2.1 del RFC de HTTP](https://tools.ietf.org/html/rfc1123#section-2).
|
||||
|
||||
@@ -78,6 +78,14 @@ Los propietarios de las empresas pueden configurar los correos electrónicos par
|
||||
|
||||
Puedes requerir el cifrado de TLS para todas las conexiones entrantes de SMTP, lo cual puede ayudar a satisfacer un requisito de certificación ISO-27017.
|
||||
|
||||
{%- ifversion ghes = 3.6 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: Enforcement of TLS for SMTP connections is unavailable in {% data variables.product.product_name %} 3.6.0. The feature will be available in an upcoming release.
|
||||
|
||||
{% endnote %}
|
||||
{%- endif %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.email-settings %}
|
||||
1. Debajo de "Autenticación", selecciona **requerir la autenticación con TLS (recomendado)**.
|
||||
|
||||
|
||||
@@ -131,46 +131,49 @@ Key | Description
|
||||
{% ifversion ghes %}
|
||||
## Indexing
|
||||
|
||||
GitHub's [code search][] features are powered by [ElasticSearch][]. This section of the site admin dashboard shows you the current status of your ElasticSearch cluster and provides you with several tools to control the behavior of searching and indexing. These tools are split into the following three categories.
|
||||
GitHub's search features are powered by Elasticsearch. This section of the site admin dashboard shows you the current status of your Elasticsearch cluster and provides you with several tools to control search and index behavior.
|
||||
|
||||
[Code Search]: https://github.com/blog/1381-a-whole-new-code-search
|
||||
[ElasticSearch]: http://www.elasticsearch.org/
|
||||
For more information about code search, see "[Searching for information on {% data variables.product.prodname_dotcom %}](/search-github)." For more information about Elasticsearch, see the [Elasticsearch website](https://elastic.co).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: In normal use, site administrators do not need to create new indices or schedule repair jobs. For troubleshooting or other support purposes, {% data variables.contact.github_support %} may instruct you to run a repair job.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Index management
|
||||
|
||||
{% data variables.product.product_name %} reconciles the state of the search index with data on the instance automatically and regularly.
|
||||
|
||||
- Issues, pull requests, repositories, and users in the database
|
||||
- Git repositories (source code) on disk
|
||||
|
||||
Your instance uses repair jobs to reconcile the data, and schedules a repair job in the background when the following events occur.
|
||||
|
||||
- A new search index is created.
|
||||
- Missing data needs to be backfilled.
|
||||
- Old search data needs to be updated.
|
||||
|
||||
You can create a new index, or you can click on an existing index in the list to manage the index. You can perform the following operations on an index.
|
||||
|
||||
- Make the index searchable.
|
||||
- Make the index writable.
|
||||
- Update the index.
|
||||
- Delete the index
|
||||
- Reset the index repair state.
|
||||
- Start a new index repair job.
|
||||
- Enable or disable index repair jobs.
|
||||
|
||||
A progress bar shows the current status of a repair job across background workers. The bar is the percentage difference of the repair offset with the highest record ID in the database. You can ignore the value shown in the progress bar after a repair job has completed. The progress bar shows the difference between the repair offset and the highest record ID in the database, and will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed.
|
||||
|
||||
To minimize the effects on I/O performance and reduce the chances of operations timing out, run the repair job during off-peak hours. As the job reconciles the search index with database and Git repository data, one CPU will be used. Monitor your system's load averages and CPU usage with a utility like `top`. If you don't notice any significant increase in resource consumption, it should also be safe to run an index repair job during peak hours.
|
||||
|
||||
Repair jobs use a "repair offset" for parallelization. This is an offset into the database table for the record being reconciled. Multiple background jobs can synchronize work based on this offset.
|
||||
|
||||
### Code search
|
||||
|
||||
This allows you to enable or disable both search and index operations on source code.
|
||||
|
||||
### Code search index repair
|
||||
|
||||
This controls how the code search index is repaired. You can
|
||||
|
||||
- enable or disable index repair jobs
|
||||
- start a new index repair job
|
||||
- reset all index repair state
|
||||
|
||||
{% data variables.product.prodname_enterprise %} uses repair jobs to reconcile the state of the search index with data stored in a database (issues, pull requests, repositories, and users) and data stored in Git repositories (source code). This happens when
|
||||
|
||||
- a new search index is created;
|
||||
- missing data needs to be backfilled; or
|
||||
- old search data needs to be updated.
|
||||
|
||||
In other words, repair jobs are started as needed and run in the background—they are not scheduled by site admins in any way.
|
||||
|
||||
Furthermore, repair jobs use a "repair offset" for parallelization. This is an offset into the database table for the record being reconciled. Multiple background jobs can synchronize work based on this offset.
|
||||
|
||||
A progress bar shows the current status of a repair job across all of its background workers. It is the percentage difference of the repair offset with the highest record ID in the database. Don't worry about the value shown in the progress bar after a repair job has completed: because it shows the difference between the repair offset and the highest record ID in the database, it will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed.
|
||||
|
||||
You can start a new code-search index repair job at any time. It will use a single CPU as it reconciles the search index with database and Git repository data. To minimize the effects this will have on I/O performance and reduce the chances of operations timing out, try to run a repair job during off-peak hours first. Monitor your system's load averages and CPU usage with a utility like `top`; if you don't notice any significant changes, it should be safe to run an index repair job during peak hours, as well.
|
||||
|
||||
### Issues index repair
|
||||
|
||||
This controls how the [Issues][] index is repaired. You can
|
||||
|
||||
[Issues]: https://github.com/blog/831-issues-2-0-the-next-generation
|
||||
|
||||
- enable or disable index repair jobs
|
||||
- start a new index repair job
|
||||
- reset all index repair state
|
||||
{% endif %}
|
||||
## Reserved logins
|
||||
|
||||
|
||||
@@ -83,7 +83,7 @@ Puedes crear un grupo de ejecutores para administrar el acceso al ejecutor que a
|
||||
|
||||
{% data variables.product.product_name %} agrega a todos los ejecutores nuevos a un grupo. Los ejecutores pueden estar en solo un grupo a la vez. Predeterminadamente, {% data variables.product.product_name %} agrega ejecutores nuevos al grupo "Predeterminado".
|
||||
|
||||
{% data reusables.actions.self-hosted-runner-groups-add-to-enterprise-first-steps %}
|
||||
{% data reusables.actions.runner-groups-add-to-enterprise-first-steps %}
|
||||
1. Para elegir una política para el acceso de la organización, debajo de "Acceso de la organización", selecciona el menú desplegable **Acceso de la organización** y haz clic en **Organizaciones selectas**.
|
||||
1. A la derecha del menú desplegable con la política de acceso de la organización, haz clic en {% octicon "gear" aria-label="The Gear icon" %}.
|
||||
1. Selecciona las organizaciones a las cuales te gustaría otorgar acceso al grupo de ejecutores.
|
||||
@@ -100,7 +100,7 @@ Puedes crear un grupo de ejecutores para administrar el acceso al ejecutor que a
|
||||
|
||||
{% endwarning %}
|
||||
{%- endif %}
|
||||
{% data reusables.actions.self-hosted-runner-create-group %}
|
||||
{% data reusables.actions.create-runner-group %}
|
||||
{%- ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
|
||||
1. Haz clic en la pestaña de "Ejecutores".
|
||||
1. En la lista de ejecutores, haz clic en aquél que hayas desplegado en la sección previa.
|
||||
|
||||
@@ -121,7 +121,7 @@ Para obtener más información sobre la API de REST de la bitácora de auditorí
|
||||
La siguiente consulta busca los eventos de la bitácora de auditoría que se crearon el 1 de enero de 2022 en la empresa `avocado-corp` y devolvió la primera página con un máximo de 100 elementos por página utilizando la [Paginación de la API de REST](/rest/overview/resources-in-the-rest-api#pagination):
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: token <em>TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer <em>TOKEN</em>" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
|
||||
```
|
||||
@@ -133,7 +133,7 @@ Puedes especificar frases de búsqueda múltiples, tales como `created` y `actor
|
||||
La siguiente consulta busca los eventos de bitácora de auditoría para las solicitudes de cambios, en donde el evento ocurrió en o después del 1 de enero de 2022 en la empresa `avocado-corp` y el usuario `octocat` realizó la acción:
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: token <em>TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer <em>TOKEN</em>" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
|
||||
```
|
||||
|
||||
@@ -44,7 +44,7 @@ The Migrations API is currently in a preview period, which means that the endpoi
|
||||
* Your access token for authentication.
|
||||
* A [list of the repositories](/free-pro-team@latest/rest/repos#list-organization-repositories) you want to migrate:
|
||||
```shell
|
||||
curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
-X POST \
|
||||
-H "Accept: application/vnd.github+json" \
|
||||
-d'{"lock_repositories":true,"repositories":["<em>orgname</em>/<em>reponame</em>", "<em>orgname</em>/<em>reponame</em>"]}' \
|
||||
@@ -59,7 +59,7 @@ The Migrations API is currently in a preview period, which means that the endpoi
|
||||
* Your access token for authentication.
|
||||
* The unique `id` of the migration:
|
||||
```shell
|
||||
curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
-H "Accept: application/vnd.github+json" \
|
||||
https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>
|
||||
```
|
||||
@@ -74,7 +74,7 @@ The Migrations API is currently in a preview period, which means that the endpoi
|
||||
* Your access token for authentication.
|
||||
* The unique `id` of the migration:
|
||||
```shell
|
||||
curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
-H "Accept: application/vnd.github+json" \
|
||||
-L -o migration_archive.tar.gz \
|
||||
https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/archive
|
||||
@@ -84,7 +84,7 @@ The Migrations API is currently in a preview period, which means that the endpoi
|
||||
* Your access token for authentication.
|
||||
* The unique `id` of the migration:
|
||||
```shell
|
||||
curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
|
||||
-X DELETE \
|
||||
-H "Accept: application/vnd.github+json" \
|
||||
https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/archive
|
||||
|
||||
@@ -134,7 +134,7 @@ Para desbloquear los repositorios en una organización{% data variables.product.
|
||||
* El `id` único de la migración
|
||||
* El nombre del repositorio a desbloquear
|
||||
```shell
|
||||
curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
|
||||
curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
|
||||
-H "Accept: application/vnd.github.wyandotte-preview+json" \
|
||||
https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/repos/<em>repo_name</em>/lock
|
||||
```
|
||||
@@ -143,7 +143,7 @@ curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
|
||||
|
||||
Después de desbloquear los repositorios de organización de {% data variables.product.prodname_dotcom_the_website %} deberás borrar todos los repositorios que migraste previamente utilizando [la terminal de borrado de repositorios](/rest/repos/#delete-a-repository). Necesitarás tu token de acceso para la autenticación:
|
||||
```shell
|
||||
curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
|
||||
curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
|
||||
https://api.github.com/repos/<em>orgname</em>/<em>repo_name</em>
|
||||
```
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Acerca de la facturación para GitHub Actions
|
||||
intro: 'Si quieres utilizar {% data variables.product.prodname_actions %} con más almacenamiento o minutos de los que se incluyen en tu cuenta, se te cobrará por estos recursos adicionales.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
|
||||
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/about-billing-for-github-actions
|
||||
@@ -28,6 +29,13 @@ Los minutos se restablecen cada mes, pero no es el caso para el uso de almacenam
|
||||
|
||||
### Minutos y almacenamiento incluídos
|
||||
|
||||
{% ifversion actions-hosted-runners %}
|
||||
{% note %}
|
||||
|
||||
**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
| Producto | Almacenamiento | Minutos (por mes) |
|
||||
| --------------------------------------------------------------------- | -------------- | ----------------- |
|
||||
| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
|
||||
@@ -58,15 +66,15 @@ El almacenamiento que utilza un repositorio es el total del almacenamiento utili
|
||||
|
||||
### Tasas por minuto
|
||||
|
||||
| Sistema operativo | Tasa por minuto (USD) |
|
||||
| ----------------- | --------------------- |
|
||||
| Linux | $0.008 |
|
||||
| macOS | $0.08 |
|
||||
| Windows | $0.016 |
|
||||
{% data reusables.billing.billing-standard-runners %}
|
||||
{% ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{% endif %}
|
||||
|
||||
La cantidad de jobs que puedes ejecutar simultáneamente a través de todos los repositorios que pertenezcan a tu cuenta de usuario u organización dependerá de tu plan de GitHub. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados.
|
||||
|
||||
{% data reusables.user-settings.context_switcher %}
|
||||
- La cantidad de jobs que puedes ejecutar simultáneamente a través de todos los repositorios que pertenezcan a tu cuenta de usuario u organización dependerá de tu plan de GitHub. Para obtener más información, consulta la sección "[Facturación y límites de uso](/actions/reference/usage-limits-billing-and-administration)" para los ejecutores hospedados en {% data variables.product.prodname_dotcom %} y la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para los límites de uso de los ejecutores auto-hospedados.
|
||||
- {% data reusables.user-settings.context_switcher %}
|
||||
{% ifversion actions-hosted-runners %}
|
||||
- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
|
||||
- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
|
||||
{% endif %}
|
||||
|
||||
## Calcular los gastos por minuto y por almacenamiento
|
||||
|
||||
|
||||
@@ -359,7 +359,7 @@ In the following example, the `+` symbol ensures that the specified additional {
|
||||
|
||||
## Using a custom configuration file
|
||||
|
||||
A custom configuration file is an alternative way to specify additional {% ifversion codeql-packs %}packs and {% endif %}queries to run. You can also use the file to disable the default queries and to specify which directories to scan during analysis.
|
||||
A custom configuration file is an alternative way to specify additional {% ifversion codeql-packs %}packs and {% endif %}queries to run. You can also use the file to disable the default queries{% ifversion code-scanning-exclude-queries-from-analysis %}, exclude or include specific queries,{% endif %} and to specify which directories to scan during analysis.
|
||||
|
||||
In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
|
||||
|
||||
@@ -442,6 +442,41 @@ Optionally, you can give each array element a name, as shown in the example conf
|
||||
|
||||
If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
|
||||
|
||||
{% ifversion code-scanning-exclude-queries-from-analysis %}
|
||||
### Excluding specific queries from analysis
|
||||
|
||||
You can add `exclude` and `include` filters to your custom configuration file, to specify the queries you want to exclude or include in the analysis.
|
||||
|
||||
This is useful if you want to exclude, for example:
|
||||
- Specific queries from the default suites (`security`, `security-extended` and `security-and-quality`).
|
||||
- Specific queries whose results do not interest you.
|
||||
- All the queries that generate warnings and recommendations.
|
||||
|
||||
You can use `exclude` filters similar to those in the configuration file below to exclude queries that you want to remove from the default analysis. In the example of configuration file below, both the `js/redundant-assignment` and the `js/useless-assignment-to-local` queries are excluded from analysis.
|
||||
|
||||
```yaml
|
||||
query-filters:
|
||||
- exclude:
|
||||
id: js/redundant-assignment
|
||||
- exclude:
|
||||
id: js/useless-assignment-to-local
|
||||
```
|
||||
To find the id of a query, you can click the alert in the list of alerts in the Security tab. This opens the alert details page. The `Rule ID` field contains the query id. For more information about the alert details page, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tips:**
|
||||
- The order of the filters is important. The first filter instruction that appears after the instructions about the queries and query packs determines whether the queries are included or excluded by default.
|
||||
- Subsequent instructions are executed in order and the instructions that appear later in the file take precedence over the earlier instructions.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
You can find another example illustrating the use of these filters in the "[Example configuration files](#example-configuration-files)" section.
|
||||
|
||||
For more information about using `exclude` and `include` filters in your custom configuration file, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/#filtering-the-queries-in-a-query-suite)." For information on the query metadata you can filter on, see "[Metadata for CodeQL queries](https://codeql.github.com/docs/writing-codeql-queries/metadata-for-codeql-queries/)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Specifying directories to scan
|
||||
|
||||
For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %}, Ruby{% endif %} and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user