Octomerger Bot
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1b29be1bd50eddd63822bfcca4938452284ce9e45bd15d3d65c9972435e334ca
|
||||
size 655344
|
||||
oid sha256:9bbb0ac433deb50b795354539e5e448c4c5504bd35f543ee42296257edfa80bb
|
||||
size 654731
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e3c39f497d3ed56e96958b1c1e0afbd4c9801dc99a56e185f56f555ac975973b
|
||||
size 1358464
|
||||
oid sha256:5321245ba5033d2f5861c65ab9d91a578ea9b0df0fad8cf20e0bc129ec7dab22
|
||||
size 1359014
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e84f3f7e9806d0111af73c2a470f3c0ffb7d2a0e8a4b15878a087bde19eb988b
|
||||
size 979208
|
||||
oid sha256:1863b9f050a8fc2caa5a019838722b5a00489f4e451a130ebc35bfd7674c0684
|
||||
size 982701
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:760bbaebb58a16f15514f1426e68e9af537375e018c86aba39501cf95106d57c
|
||||
size 3988431
|
||||
oid sha256:b129640b808da254ef4b98c6d40259dbd2614edd57e6cba662aa2c825caf0585
|
||||
size 3990279
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cd7fccd27f3284924ea2578413f08d906af1f3054ec29a39331afc34a2408e14
|
||||
size 610484
|
||||
oid sha256:f1ebd8022524a35feb5465c9ce64e1484648157d1fda1225a5978b3b8b4c45f5
|
||||
size 610263
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ad33f0389b850885de6931ce5ffac9ceacd3a350b96af2099df61f75019f6216
|
||||
size 2547783
|
||||
oid sha256:3a1860118dd027aabf37d77a9c80fb2ec1c7eeb8c1e08ba0e281d798dccd67aa
|
||||
size 2545928
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2d284162c7a78b8de244617bd20c72301cf114d14fcfb126b71088c58edf68b8
|
||||
size 673926
|
||||
oid sha256:a9ea9563e608c1f18e1ce19364d5fb52315c6c73cf2fc2a1771ceda19c3b8a18
|
||||
size 675200
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:36deee9be411ea9430927f57831f98fe4e0fd673abec9109c69dead8b81666b9
|
||||
size 3554180
|
||||
oid sha256:befc916561f6d7a1049f370066e461c9f207ee409e20564cf9f51fcb463f6006
|
||||
size 3554532
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ef9dc613595760b1f041e68862c7ef3b20de843c45e5d7c69995ef71128e0bfd
|
||||
size 605486
|
||||
oid sha256:9e74e925904f7a56802de9bbfb59b0f058daf9077a2d69982f7d2bc1bbc055e4
|
||||
size 605762
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:69195a0b242a976a128cb3465f1278fb53bc806180aa8ad5375e52f7937028c4
|
||||
size 2469148
|
||||
oid sha256:13c38e059e191078c4f00160943195f458259145a1a6d71acd45265e4793df2a
|
||||
size 2471337
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0c7af246daa79605ff9494e2050238d811b6d541a4bf23075e9764449e23ffda
|
||||
size 668817
|
||||
oid sha256:fbf53d792d1982b88a495f8edc7192aeb77d66aa34ebcbdda0e8855c93be035c
|
||||
size 668897
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e80ac5211536ab98514aa686f6e875113a4d9d50083cd1fe28dbeaf1787ec179
|
||||
size 1395128
|
||||
oid sha256:e954d69d5d5c94de272f7214397f0e597c429e0ea5585e9763e9236f599bcc3e
|
||||
size 1395256
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3a93317b9656234c93087564c20f738d0729b95138f2d1d78950da89373126b5
|
||||
size 1009009
|
||||
oid sha256:b6124920e4c87ac8b0250c820bd9b385ae44080e2e37951f4574377a9101a1a1
|
||||
size 1005223
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6ed496e92c24469cc25692f754152b5a635de36128c106b02dcc263e69245de7
|
||||
size 4076917
|
||||
oid sha256:72d5a04ae54b1627a3e5e00b584d022dee6269aaa802cf0bf089eb39fdabf6f9
|
||||
size 4078287
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b15d208341a9b79bf83c03f4743dc0fd465a787590dc953c230c8bdf6ebf5ece
|
||||
size 622115
|
||||
oid sha256:87e601eeb3b1576a1e2b8d59a141458477c35d9163e3ed0f0519d128c98f5d00
|
||||
size 622570
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1e1b81493face8c47e5fe27ca4bfb7783bf83cc62a4eb6d8e49d5a135b1649ba
|
||||
size 2605199
|
||||
oid sha256:ab438e50e3ee170a5a1590587255feb5b514da4d43dae892ab37e7c72ea0b039
|
||||
size 2604055
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:105e7e086cce103f9a17c3eadc805a97ee2633a68dc8e16d6d3a87c073f92814
|
||||
size 688204
|
||||
oid sha256:bede55a70607167afa3fc022c68435e6ea3aa223aebb70adbe36a95b21fb00b8
|
||||
size 687829
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9addedb5ca05dfaf03fa72b509288acc82171fff62d51df9a8ac770150bfe996
|
||||
size 3636207
|
||||
oid sha256:29f178a458f2b0a402988e7c4e5b2435241b22ef080e56b29873c9f40f83c3f8
|
||||
size 3634098
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b554a8189185f064bbae4b08b6450ad04b200d80007cea5830edd1fe309f05d1
|
||||
size 617737
|
||||
oid sha256:d5ee1baeba1af9dc7826d8456f04434570fd5c2c4d94e47cc13d59aa4689ccef
|
||||
size 617451
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5489b4ebcd6318d4134e41527994bed7f80485b1e7a0d140c565e0ab37494b6f
|
||||
size 2523242
|
||||
oid sha256:da02bf9f9019a1668769f36d70631744ee0676ca5ebb60d7b9864469640b68ef
|
||||
size 2524768
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4e839ae5a6d83934cb2ca1dd8107e9f23b95e9951e2c72da0d7729e1f4170b25
|
||||
size 683820
|
||||
oid sha256:7848cdd505817b1f236e3257bba8e068216f82bd2e546fcf48463dfe5d9bac9a
|
||||
size 684020
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4a1f34fd22076f8f54085583e8ee2dddf06ea84315334e229c8847f687343413
|
||||
size 1426908
|
||||
oid sha256:447f2c925a8085ea6e20f774fb4aa6217e772f69d8f38599b5e74324f6fde0dc
|
||||
size 1427040
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:985c14572767722d82aabb28a08ff5c6d59e58a13a3fdbd9468372913c726c70
|
||||
size 1039387
|
||||
oid sha256:85082c40aeaa8eb7bb9685dd78d9d3822a1e23626d826429fe520728c736c1c1
|
||||
size 1038488
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ee406e7fc6f1376ed4ab1248f34d8dc35c524e37a97cea4f446c1b5643d59bfe
|
||||
size 4214819
|
||||
oid sha256:0c1cc795afda1ecd5f876f1c4e8537e440fbceece438642591aa3f3d4d278501
|
||||
size 4213013
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:47aa551b0cd0f7f47190152177c90e35e510c4720b1851bb8dff79ec18edf17e
|
||||
size 636593
|
||||
oid sha256:a83d26ccb97c55f9f3c6d87be86069feeeea7f83dedab797f81bb857b90ebfc5
|
||||
size 635568
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7e6f9ae59d441910b483e4960d98445c9d437777ef983a978b87d285c87c4882
|
||||
size 2667617
|
||||
oid sha256:8c9bfb6f994a7aabb777ec834076c86b40950dd2e8c100cc7722598cffb697c3
|
||||
size 2664430
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a4c31f2d2ef7a8e04bd7d80f70da0a062461ed7771a9888c53d6ee0e37918efd
|
||||
size 700978
|
||||
oid sha256:0edd922ba541ad4af3412f6091234547db12241c71c0783365b6cd7a4cc5d81d
|
||||
size 700773
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e7da621f8ed4f13859e5d1aeede447eba612ed3adf4dfbcf01e5d96a48d19f1a
|
||||
size 3713042
|
||||
oid sha256:c97ab9be359c29451a9e1958bf6508cdc862bc10a430173d641882b36e3966fb
|
||||
size 3711979
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:60dbee21d7e98bc099c8e2709b1e5606ba957ef76d0cd059e9b5d324cbb1f3c4
|
||||
size 632452
|
||||
oid sha256:1006d3bff566874b66d896e7c1b8764e4c99b379d7669e655a6bbf196a12b31a
|
||||
size 632545
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b7d6bd400e720c9f6db037cfe24bd11e1547d0202e26bc3207f8e464e0c36bc9
|
||||
size 2579984
|
||||
oid sha256:d2e9369120f14ea64d7d80f0edbda66ecb2dd9bcd4087a455485f94568bd67d8
|
||||
size 2580380
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cf67d463a6253311727d5284985099cc73911e7444b352eec16d6881fe77187f
|
||||
size 706081
|
||||
oid sha256:c9ed95040c13e66c7f2347c8f0d9767ecebb0b1ba179bca4ba4f17fc36fa8fc4
|
||||
size 705843
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4bfa7557f0f60af12e95f37211a8b9b6b93f984c1c25005d2de33287ff0833de
|
||||
size 1485559
|
||||
oid sha256:009b0a9487999c1fa9f418af4bc607e6b9d08f343b62aaf0fb7325770e59cd35
|
||||
size 1485670
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4ae10c2325bbf9e25d0dc3104849787c0bcde8033747758a37c9f812c7fb827c
|
||||
size 1072085
|
||||
oid sha256:80d74f640a51cf890cf776fe3148d31359ba80af91bc0c41f05bbfc105259801
|
||||
size 1073488
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4450ae7a6b3d1684dc88fab4d685dc0098e4598f821ace9878285a8e630b66a4
|
||||
size 4315929
|
||||
oid sha256:1ea9096a5451e38fd98d5d1b1017afc6bc0b8a579ab7be7461aa3993ab0ef5c1
|
||||
size 4315436
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cb3859eebd737c78040db848097c2562b79ec74cada912006eb8459e6ecfb91b
|
||||
size 656002
|
||||
oid sha256:78d6c220bfa84f849da251e0cf4ea5bfa25b5bb1f2484366821b40b336c9d283
|
||||
size 656174
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d0b4aa7b2d0d9ba72955da7057013a9b63427aaded11f2248e3449529c3b16c2
|
||||
size 2766183
|
||||
oid sha256:d18f16c7be3ea04d2ecb99de285bb54507dafc3c643f8dc77f32819405fff1f7
|
||||
size 2765693
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f30154e87955380b5fb534bc497a4ec8eb82cee70987883521eb9935ca37d6c4
|
||||
size 723705
|
||||
oid sha256:ee474cbfed74151ce05188d0e83d7b4792e5cde59163e9090ed2fa3366be8a28
|
||||
size 723543
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:48f76185f8d6df977e2855aa5b785626d90d46750dd4158e403a0ab5727e5fd5
|
||||
size 3836052
|
||||
oid sha256:183b304672790c0c00dd047a300d309a4f91fb8a1d9409e92e0f48856254016b
|
||||
size 3835679
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:65407b28154f48ee1a9ed701bd46b42daf752e6363ce28420ed29180edc6598d
|
||||
size 650862
|
||||
oid sha256:38798b498430305b342c770e1748105f5d50e65688395ca8feee7b2f6e58146f
|
||||
size 650295
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7a1d6134e43ab8cdbfc092742240ee7df29e74503e5d8b880a88ad6bfe5df144
|
||||
size 2664841
|
||||
oid sha256:307e57e4d687bf8d7c4ae567a1817a1c0e381cc9ac2e17b5c47f275f0f8bcb9a
|
||||
size 2663716
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:73df7da3e9062713b7ba1896621a5bb076377fdaed4fe8c91291b17285e44bed
|
||||
size 900773
|
||||
oid sha256:001ba07772b5f3a3414752b61d54fccc5e70cc1a7b79aca4b59e7d14b468fa9c
|
||||
size 900572
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f8eb9fb6e9e3cc03a8bf30806a2042aea07151cda9b25462d21f622e8f1ccbdc
|
||||
size 1635466
|
||||
oid sha256:8b7232af13fb45e630b435232104042053892c35a490d76547bde83635b9470c
|
||||
size 1635192
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:898891be945380e85381415fb6fdb93bf5ef5c6f552c991d9cb20273b589b1d1
|
||||
size 1364173
|
||||
oid sha256:aefa1eece941f47e2470c216087e7a1013aa350f5ab075e1c38824962f64470f
|
||||
size 1363162
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:280178d8f84c0f9d338e65bac88bc61f70807e235e6f510faccec5ce8d7ca93f
|
||||
size 5191156
|
||||
oid sha256:90212aaebc76fbf808c99e38667d2a0d75de1e4df82ab51b805140f707cec592
|
||||
size 5192521
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:484d228700c0698fc3c0b5212d44bd0e6579563db16b60b15ced569fedcf4072
|
||||
size 820486
|
||||
oid sha256:dbcf6165fedcbaac28a642488f70864063dffc371273716c20b291872ea3c5e5
|
||||
size 820187
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9219ba70a66c0a01af2d58706e6b0e40e59bfa8be27c9062ae2f81c14b82ab7a
|
||||
size 3288070
|
||||
oid sha256:edc1d2fbd081728a1151b0ee83b2e31379170c315d1dba1b4a250677086c869a
|
||||
size 3288040
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:179956d00298df81aae4523653735ebe559d91edf471149700ea5492cf7818eb
|
||||
size 917973
|
||||
oid sha256:a75f324b00356b9a2c87f3b42178de225b5727e7f4093b35a9b7b76e3d02d8f1
|
||||
size 918163
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:205abcc67377d96acfe48f25389c2f4fa0d5fe544597179dd7d955dddfbcd69e
|
||||
size 4648302
|
||||
oid sha256:b22e551b36a7d964a56b3b59530198c4660dbd3057ddcb3dc34f60e1c9f3776c
|
||||
size 4648021
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:927d3bd7f293e1cc34fc4cf2700da146768f7d8c07886b3f106aa4b9cc210d56
|
||||
size 819340
|
||||
oid sha256:6fa7eb4aef76671b8c7c8d8fbade643d0e5034a10ab48aa7baffde560422faa5
|
||||
size 819738
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e5f58b3d0c1a66c56d3d32c807af3aade4a9aee6bdc8ba25808acc7eef12978b
|
||||
size 3191369
|
||||
oid sha256:69306c6110402db9b688d8316dbe1b089695ff4e55cf8b38a29e04aebe8f65b2
|
||||
size 3193735
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:89fd57befa695817dae74d74c75d2afe16c81d61f2ebe6299f7e6793dd860f25
|
||||
size 551866
|
||||
oid sha256:971556b8649d279719e9b533c3c40e7838dfc746cdce5a44e2b69a0efa917642
|
||||
size 552383
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:60e019e3b2f7ff23f990fa84db54cb723bf825ec887b342c35a2070d45a75075
|
||||
size 1104976
|
||||
oid sha256:bc3a572b8137482a9a37ac8255543c57db5422065b5e200faa9a990d7cbf0743
|
||||
size 1105858
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5c1bc366a1b91a80dccbb89b0b5ad0522330242f445e9cf1476efb842964f08d
|
||||
size 856673
|
||||
oid sha256:b56b4a7d0c5f58612d9e7fad74d185caf37bb2e12cf21b9de7e712a44d723200
|
||||
size 857516
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9958e2e7f3874f4c74255a6796aa7bce75e4ff60667bb1ec467e053610ed6f80
|
||||
size 3435163
|
||||
oid sha256:af58d60e748ce00c7cb091b1e07c7c7e019065b9afaed106e1a5475f9aa09cb3
|
||||
size 3434133
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4df9fbd069f3eea22c81a07508845ccaa83a7c2027e3caf81f03f860cf59af7c
|
||||
size 515125
|
||||
oid sha256:b6652827e4b31943cfbfe90a0c72d3d4c6b5fafdd81373efd43a2ff6b9d06535
|
||||
size 515108
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cb2ba87f4e5a292b6ccc6aee2f1b4b2d6d089a605c925f7be3763cf14b006621
|
||||
size 2084148
|
||||
oid sha256:e75049b61efe7cecf3f6b954dd76408a2078382e8b6d981432acc088f4a204f2
|
||||
size 2085345
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2b889e10773dba824682ac0bbee600f5e5636ac08728a43adc1f96d46c82f7d6
|
||||
size 564872
|
||||
oid sha256:dbc10898c0e8d3cdc0b3729e32dc79e24e22f9c867874ebb8a1310612deb21f7
|
||||
size 565493
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f0f44663c2b292c4cfd5503e122519d961179a9d4254c98e215e313fbde01893
|
||||
size 2881075
|
||||
oid sha256:9c3fdabf6b4ae220e4263a6b67319e3f302b38c897e81a39e9ca311b146d0a54
|
||||
size 2882367
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:804b8bd0879a46cefb418adc8773b68ddd73ff826eb26fc6b55acf56760a06a1
|
||||
size 512830
|
||||
oid sha256:36594e6e19ee79efd428269864d1d546112f1371cf167ceedfb9e0caaafd8598
|
||||
size 513634
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c2c8ceae398b9f887e314b221993a587474665da537b0f7c72890d297488b923
|
||||
size 2010207
|
||||
oid sha256:977c8c29bd3c86de68ff8b0b9a1c8a64055932004a642150ee20770bee8330ef
|
||||
size 2011494
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:346e5306537925b396541cd0a3633c8257cb69dea3ac067eb695ddc1c705ed5d
|
||||
size 823770
|
||||
oid sha256:c824eed9b6444580b44289cfcffab552946c6d765fddcd85f2df4cf23a079947
|
||||
size 823021
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c065835b1a2f13f6a44f871885442052636fe2212273cc877797e6de342766ff
|
||||
size 1693018
|
||||
oid sha256:b48b8ba31a1a9cc4eaf6c2262c60ed0271b0011f3d32d3526148259829133b70
|
||||
size 1693542
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:727dc19d33dece3ba87d88dca39d32098453cbea3ebb10ce140cbcf6ca629798
|
||||
size 1239313
|
||||
oid sha256:081d15003c08caea2a9f97c6d31881d392185bf23dccd16833815c2436e87648
|
||||
size 1237371
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5b283cd1a4a9c18262483efe2eec29c128bbf1551f6930da46268f31f1465ee9
|
||||
size 4973495
|
||||
oid sha256:fd58a54139eba68f1e3ef946307c7d2d3905c46bab903c112b3727b57ccb084a
|
||||
size 4970360
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:27fd50aaa197b3f1bdb2d8888d52e0225679d51b7cdef89e10a03a08309c16a5
|
||||
size 777402
|
||||
oid sha256:d6571a256ef21b96935e22f1a89c2f7de8367681fabbcd222a9200e5062f3094
|
||||
size 776590
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:892bc8e6256a85035dee8cf6377ec5608c7c72190a26ee172ddc7baa82a52468
|
||||
size 3266499
|
||||
oid sha256:fcb15de5b8cd43ff322e08e929bd611dcef31cddb8b295889f3740cb49a93cc9
|
||||
size 3264567
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f5f674692a81bca1b6ba76c57a6e03ff6f5619f4c923d171948680461e1e1ff6
|
||||
size 846556
|
||||
oid sha256:df0dba5318339fdde890278d9d11936e1198e5cebc305808fdeddba57bf7c127
|
||||
size 847542
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:15df1fd28dbb74bbf7290409ce0df9036280323cc4ed9fd684747d07b41ac831
|
||||
size 4503277
|
||||
oid sha256:910fd6f3ff5de177d16d785bec6a9fd5bc8199ba8678c57a3d1fbcec6e402de1
|
||||
size 4501145
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3186da214214fae7cc3aa122b7f3c1ae01d495e1b8771fc91f8e9aceb27b0640
|
||||
size 777108
|
||||
oid sha256:b9d9c2470c258f1116ebc895ee6c80643a009d2a47f97ff31a91ea870394f309
|
||||
size 777112
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d23a038da455cb1d56c19555573a3a880a0920a945178fc0365c374a7411be53
|
||||
size 3167790
|
||||
oid sha256:8ccb35b258643b959939c84aedc7431f9c1121b89e0f42236a4ab44399a40abd
|
||||
size 3169057
|
||||
|
||||
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 4
|
||||
|
||||
## Acerca de la nueva sintaxis YAML para {% data variables.product.prodname_actions %}
|
||||
|
||||
Las acciones Docker y JavaScript requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos del archivo de metadatos definen las entradas, las salidas y el punto de entrada principal para tu acción.
|
||||
All actions require a metadata file. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
|
||||
|
||||
Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
|
||||
|
||||
|
||||
@@ -218,6 +218,10 @@ For example:
|
||||
curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
|
||||
```
|
||||
|
||||
### Adding permissions settings
|
||||
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
## Updating your workflows for OIDC
|
||||
|
||||
You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
|
||||
|
||||
@@ -56,14 +56,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
|
||||
|
||||
### Adding permissions settings
|
||||
|
||||
The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
|
||||
|
||||
```yaml{:copy}
|
||||
permissions:
|
||||
id-token: write
|
||||
```
|
||||
|
||||
You may need to specify additional permissions here, depending on your workflow's requirements.
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
### Requesting the access token
|
||||
|
||||
|
||||
@@ -50,14 +50,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
|
||||
|
||||
### Adding permissions settings
|
||||
|
||||
The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
|
||||
|
||||
```yaml{:copy}
|
||||
permissions:
|
||||
id-token: write
|
||||
```
|
||||
|
||||
You may need to specify additional permissions here, depending on your workflow's requirements.
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
### Requesting the access token
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Configuring OpenID Connect in cloud providers
|
||||
title: Configurar OpenID Connect en los proveedores de servicios en la nube
|
||||
shortTitle: Configurar OpenID Connect en los proveedores de servicios en la nube
|
||||
intro: Use OpenID Connect within your workflows to authenticate with cloud providers.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -30,21 +30,14 @@ To use OIDC, you will first need to configure your cloud provider to trust {% da
|
||||
## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
|
||||
|
||||
To update your workflows for OIDC, you will need to make two changes to your YAML:
|
||||
1. Add permissions settings for the token.
|
||||
1. Agregar ajustes de permisos para el token.
|
||||
2. Use the official action from your cloud provider to exchange the OIDC token (JWT) for a cloud access token.
|
||||
|
||||
If your cloud provider doesn't yet offer an official action, you can update your workflows to perform these steps manually.
|
||||
|
||||
### Adding permissions settings
|
||||
### Agregar ajustes de permisos
|
||||
|
||||
El flujo de trabajo requerirá una configuración de `permissions` con un valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. Si solo necesitas recuperar un token de OIDC para un solo job, entonces este permiso puede configurarse dentro de dicho job. Por ejemplo:
|
||||
|
||||
```yaml{:copy}
|
||||
permissions:
|
||||
id-token: write
|
||||
```
|
||||
|
||||
Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
### Using official actions
|
||||
|
||||
@@ -64,7 +57,7 @@ To update your workflows using this approach, you will need to make three change
|
||||
|
||||
### Requesting the JWT using the Actions core toolkit
|
||||
|
||||
The following example demonstrates how to use `actions/github-script` with the `core` toolkit to request the JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. For more information, see "[Adding actions toolkit packages](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)."
|
||||
The following example demonstrates how to use `actions/github-script` with the `core` toolkit to request the JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. Para obtener más información, consulta la sección "[Agregar paquetes de kit de herramientas de acciones](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)".
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Configuring OpenID Connect in Google Cloud Platform
|
||||
title: Configurar OpenID Connect en Google Cloud Platform
|
||||
shortTitle: Configurar OpenID Connect en Google Cloud Platform
|
||||
intro: Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -49,14 +49,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
|
||||
|
||||
### Agregar ajustes de permisos
|
||||
|
||||
El flujo de trabajo requerirá una configuración de `permissions` con un valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. Si solo necesitas recuperar un token de OIDC para un solo job, entonces este permiso puede configurarse dentro de dicho job. Por ejemplo:
|
||||
|
||||
```yaml{:copy}
|
||||
permissions:
|
||||
id-token: write
|
||||
```
|
||||
|
||||
Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
### Requesting the access token
|
||||
|
||||
|
||||
@@ -54,14 +54,7 @@ This example demonstrates how to use OIDC with the official action to request a
|
||||
|
||||
### Agregar ajustes de permisos
|
||||
|
||||
El flujo de trabajo requerirá una configuración de `permissions` con un valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. Si solo necesitas recuperar un token de OIDC para un solo job, entonces este permiso puede configurarse dentro de dicho job. Por ejemplo:
|
||||
|
||||
```yaml{:copy}
|
||||
permissions:
|
||||
id-token: write
|
||||
```
|
||||
|
||||
Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
|
||||
{% data reusables.actions.oidc-permissions-token %}
|
||||
|
||||
### Requesting the access token
|
||||
|
||||
|
||||
@@ -32,7 +32,6 @@ featuredLinks:
|
||||
- title: "GitHub Actions in action – Karan MV"
|
||||
href: 'https://www.youtube-nocookie.com/embed/4SWO0Pc76CU'
|
||||
videosHeading: GitHub Universe 2021 videos
|
||||
examples_source: data/product-examples/actions/code-examples.yml
|
||||
product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
|
||||
redirect_from:
|
||||
- /articles/automating-your-workflow-with-github-actions
|
||||
|
||||
@@ -18,16 +18,23 @@ shortTitle: Límites & facturación de los flujos de trabajo
|
||||
|
||||
## Acerca de la facturación para {% data variables.product.prodname_actions %}
|
||||
|
||||
{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
|
||||
{% else %}
|
||||
El uso de GitHub Actions es gratuito para los {% data variables.product.prodname_ghe_server %} que utilicen ejecutores auto-hospedados.
|
||||
GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## Disponibilidad
|
||||
|
||||
{% data variables.product.prodname_actions %} está disponible en todos los productos de {% data variables.product.prodname_dotcom %}, pero {% data variables.product.prodname_actions %} no está disponible para los repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% data reusables.gated-features.more-info %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Límites de uso
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
@@ -90,6 +90,9 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
|
||||
| issues | read/write | none | read |
|
||||
| metadata | read | read | read |
|
||||
| packages | read/write | none | read |
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6187 %}
|
||||
| pages | read/write | none | read |
|
||||
{%- endif %}
|
||||
| pull-requests | read/write | none | read |
|
||||
| repository-projects | read/write | none | read |
|
||||
| security-events | read/write | none | read |
|
||||
|
||||
@@ -354,3 +354,50 @@ Los secretos tienen un tamaño máximo de 64 KB. Para usar secretos de un tamañ
|
||||
run: cat $HOME/secrets/my_secret.json
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
## Storing Base64 binary blobs as secrets
|
||||
|
||||
You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Use `base64` to encode your file into a Base64 string. Por ejemplo:
|
||||
|
||||
```
|
||||
$ base64 -i cert.der -o cert.base64
|
||||
```
|
||||
|
||||
1. Create a secret that contains the Base64 string. Por ejemplo:
|
||||
|
||||
```
|
||||
$ gh secret set CERTIFICATE_BASE64 < cert.base64
|
||||
✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
|
||||
```
|
||||
|
||||
1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`. Por ejemplo:
|
||||
|
||||
```yaml
|
||||
name: Retrieve Base64 secret
|
||||
on:
|
||||
push:
|
||||
branches: [ octo-branch ]
|
||||
jobs:
|
||||
decode-secret:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Retrieve the secret and decode it to a file
|
||||
env:
|
||||
{% raw %}CERTIFICATE_BASE64: ${{ secrets.CERTIFICATE_BASE64 }}{% endraw %}
|
||||
run: |
|
||||
echo $CERTIFICATE_BASE64 | base64 --decode > cert.der
|
||||
- name: Show certificate information
|
||||
run: |
|
||||
openssl x509 -in cert.der -inform DER -text -noout
|
||||
```
|
||||
|
||||
|
||||
@@ -52,9 +52,11 @@ If you use Docker container actions or service containers in your workflows, you
|
||||
|
||||
If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://<IP_ADDRESS>` when setting or changing your {% data variables.product.prodname_actions %} configuration.
|
||||
|
||||
## Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname
|
||||
## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
|
||||
|
||||
If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
|
||||
{% data reusables.enterprise_installation.changing-hostname-not-supported %}
|
||||
|
||||
If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
|
||||
|
||||
You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures:
|
||||
|
||||
|
||||
@@ -97,12 +97,14 @@ featuredLinks:
|
||||
- '{% ifversion ghes %}/admin/installation{% endif %}'
|
||||
- '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
|
||||
- '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
|
||||
- '{% ifversion ghae %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae{% endif %}'
|
||||
- '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
|
||||
- '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
|
||||
- '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
|
||||
- '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}'
|
||||
- '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}'
|
||||
- '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}'
|
||||
- /admin/configuration/configuring-github-connect/managing-github-connect
|
||||
- /admin/enterprise-support/about-github-enterprise-support
|
||||
videos:
|
||||
- title: GitHub in the Enterprise – Maya Ross
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: Accessing compliance reports for your enterprise
|
||||
intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Accounts
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
permissions: Enterprise owners can access compliance reports for the enterprise.
|
||||
shortTitle: Access compliance reports
|
||||
---
|
||||
|
||||
## About {% data variables.product.company_short %}'s compliance reports
|
||||
|
||||
You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
|
||||
|
||||
{% data reusables.security.compliance-report-list %}
|
||||
|
||||
## Accessing compliance reports for your enterprise
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
|
||||
1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
|
||||
|
||||
{% data reusables.security.compliance-report-screenshot %}
|
||||
|
||||
## Leer más
|
||||
|
||||
- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
|
||||
@@ -15,5 +15,6 @@ children:
|
||||
- /system-overview
|
||||
- /about-the-github-enterprise-api
|
||||
- /creating-an-enterprise-account
|
||||
- /accessing-compliance-reports-for-your-enterprise
|
||||
---
|
||||
For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
|
||||
|
||||
@@ -149,9 +149,8 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
|
||||
{% data reusables.organizations.delete-ssh-ca %}
|
||||
|
||||
{% ifversion ghec or ghae %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
|
||||
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
|
||||
- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -9,6 +9,7 @@ redirect_from:
|
||||
intro: 'Una vez que se ha creado un equipo, los administradores de la organización pueden agregar usuarios desde {% data variables.product.product_location %} al equipo y determinar a qué repositorios tienen acceso.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Access management
|
||||
@@ -30,8 +31,12 @@ Cada equipo tiene sus propios premisos de acceso definidos de manera individual
|
||||
{% data reusables.organizations.invite_to_team %}
|
||||
{% data reusables.organizations.review-team-repository-access %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Asignar equipos a los grupos LDAP (para instancias que usan la sincronización LDAP para la autenticación de usuario)
|
||||
|
||||
{% data reusables.enterprise_management_console.badge_indicator %}
|
||||
|
||||
Para agregar un nuevo miembro a un equipo sincronizado con un grupo LDAP, agrega el usuario como un miembro del grupo LDAP o comunícate con el administrador LDAP.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -7,6 +7,7 @@ redirect_from:
|
||||
- /admin/user-management/continuous-integration-using-jenkins
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- CI
|
||||
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /admin/user-management/creating-teams
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Access management
|
||||
@@ -32,6 +33,8 @@ A prudent combination of teams is a powerful way to control repository access. F
|
||||
{% data reusables.organizations.create-team-choose-parent %}
|
||||
{% data reusables.organizations.create_team %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Creating teams with LDAP Sync enabled
|
||||
|
||||
Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.product.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
|
||||
@@ -60,3 +63,5 @@ You must be a site admin and an organization owner to create a team with LDAP sy
|
||||
{% data reusables.organizations.team_visibility %}
|
||||
{% data reusables.organizations.create-team-choose-parent %}
|
||||
{% data reusables.organizations.create_team %}
|
||||
|
||||
{% endif %}
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Administrar proyectos utilizando Jira
|
||||
intro: 'Puedes integrar Jura con {% data variables.product.prodname_enterprise %} para la administración de proyectos.'
|
||||
intro: 'Puedes integrar Jura con {% data variables.product.product_name %} para la administración de proyectos.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/guides/installation/project-management-using-jira
|
||||
- /enterprise/admin/articles/project-management-using-jira
|
||||
@@ -10,6 +10,7 @@ redirect_from:
|
||||
- /admin/user-management/managing-projects-using-jira
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /admin/user-management/removing-users-from-teams-and-organizations
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Access management
|
||||
@@ -25,6 +26,8 @@ Solo los propietarios o los administradores del equipo pueden eliminar miembros
|
||||
|
||||
## Eliminar un miembro del equipo
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Nota:** {% data reusables.enterprise_management_console.badge_indicator %}
|
||||
@@ -33,6 +36,8 @@ Para eliminar un miembro existente de un equipo sincronizado a un grupo LDAP, co
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user_settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
|
||||
@@ -8,6 +8,7 @@ redirect_from:
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
|
||||
- /github/extending-github/git-automation-with-oauth-tokens
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -0,0 +1,119 @@
|
||||
---
|
||||
title: About code scanning alerts
|
||||
intro: 'Learn about the different types of code scanning alerts and the information that helps you understand the problem each alert highlights.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Advanced Security
|
||||
- Code scanning
|
||||
- CodeQL
|
||||
---
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
## About alerts from {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
|
||||
## About alert 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 alert 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.
|
||||
|
||||
|
||||
|
||||
If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
|
||||
|
||||
When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
|
||||
|
||||
### About severity levels
|
||||
|
||||
Alert severity levels may be `Error`, `Warning`, or `Note`.
|
||||
|
||||
If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify which severity level of code scanning alerts causes a 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 %}
|
||||
|
||||
{% 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`.
|
||||
|
||||
To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
|
||||
|
||||
By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
|
||||
|
||||
### About labels for alerts that are not found in application code
|
||||
|
||||
{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
|
||||
|
||||
- **Generated**: Code generated by the build process
|
||||
- **Test**: Test code
|
||||
- **Library**: Library or third-party code
|
||||
- **Documentation**: Documentation
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
|
||||
|
||||
Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occurring in library code.
|
||||
|
||||
|
||||
|
||||
On the alert page, you can see that the filepath is marked as library code (`Library` label).
|
||||
|
||||
|
||||
|
||||
{% if codeql-ml-queries %}
|
||||
|
||||
## About experimental alerts
|
||||
|
||||
{% data reusables.code-scanning.beta-codeql-ml-queries %}
|
||||
|
||||
In repositories that run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql %} action, you may see some alerts that are marked as experimental. These are alerts that were found using a machine learning model to extend the capabilities of an existing {% data variables.product.prodname_codeql %} query.
|
||||
|
||||
|
||||
|
||||
### Benefits of using machine learning models to extend queries
|
||||
|
||||
Queries that use machine learning models are capable of finding vulnerabilities in code that was written using frameworks and libraries that the original query writer did not include.
|
||||
|
||||
Each of the security queries for {% data variables.product.prodname_codeql %} identifies code that's vulnerable to a specific type of attack. Security researchers write the queries and include the most common frameworks and libraries. So each existing query finds vulnerable uses of common frameworks and libraries. However, developers use many different frameworks and libraries, and a manually maintained query cannot include them all. Consequently, manually maintained queries do not provide coverage for all frameworks and libraries.
|
||||
|
||||
{% data variables.product.prodname_codeql %} uses a machine learning model to extend an existing security query to cover a wider range of frameworks and libraries. The machine learning model is trained to detect problems in code it's never seen before. Queries that use the model will find results for frameworks and libraries that are not described in the original query.
|
||||
|
||||
### Alerts identified using machine learning
|
||||
|
||||
Alerts found using a machine learning model are tagged as "Experimental alerts" to show that the technology is under active development. These alerts have a higher rate of false positive results than the queries they are based on. The machine learning model will improve based on user actions such as marking a poor result as a false positive or fixing a good result.
|
||||
|
||||
|
||||
|
||||
## Enabling experimental alerts
|
||||
|
||||
The default {% data variables.product.prodname_codeql %} query suites do not include any queries that use machine learning to generate experimental alerts. To run machine learning queries during {% data variables.product.prodname_code_scanning %} you need to run the additional queries contained in one of the following query suites.
|
||||
|
||||
{% data reusables.code-scanning.codeql-query-suites %}
|
||||
|
||||
When you update your workflow to run an additional query suite this will increase the analysis time.
|
||||
|
||||
``` yaml
|
||||
- uses: github/codeql-action/init@v1
|
||||
with:
|
||||
# Run extended queries including queries using machine learning
|
||||
queries: security-extended
|
||||
```
|
||||
|
||||
For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
|
||||
|
||||
## Disabling experimental alerts
|
||||
|
||||
The simplest way to disable queries that use machine learning to generate experimental alerts is to stop running the `security-extended` or `security-and-quality` query suite. In the example above, you would comment out the `queries` line. If you need to continue to run the `security-extended` or `security-and-quality` suite and the machine learning queries are causing problems, then you can open a ticket with [{% data variables.product.company_short %} support](https://support.github.com/contact) with the following details.
|
||||
|
||||
- Ticket title: "{% data variables.product.prodname_code_scanning %}: removal from experimental alerts beta"
|
||||
- Specify details of the repositories or organizations that are affected
|
||||
- Request an escalation to engineering
|
||||
|
||||
{% endif %}
|
||||
@@ -43,7 +43,7 @@ There are two main ways to use {% data variables.product.prodname_codeql %} anal
|
||||
|
||||
## About {% data variables.product.prodname_codeql %} queries
|
||||
|
||||
{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
|
||||
{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://codeql.github.com/) on the {% data variables.product.prodname_codeql %} website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
|
||||
|
||||
You can run additional queries as part of your code scanning analysis.
|
||||
|
||||
|
||||
@@ -18,7 +18,6 @@ topics:
|
||||
- Code scanning
|
||||
---
|
||||
|
||||
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
@@ -24,7 +24,7 @@ topics:
|
||||
- Python
|
||||
shortTitle: Configure code scanning
|
||||
---
|
||||
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
|
||||
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
@@ -89,7 +89,7 @@ If you scan pull requests, then the results appear as alerts in a pull request c
|
||||
{% 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 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)."
|
||||
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 "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
@@ -351,7 +351,7 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
|
||||
|
||||
You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
|
||||
|
||||
{% data reusables.code-scanning.codeql-query-suites %}
|
||||
{% data reusables.code-scanning.codeql-query-suites-explanation %}
|
||||
|
||||
{% if codeql-packs %}
|
||||
### Working with custom configuration files
|
||||
|
||||
@@ -26,7 +26,7 @@ topics:
|
||||
- C#
|
||||
- Java
|
||||
---
|
||||
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
|
||||
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
|
||||
@@ -16,6 +16,7 @@ topics:
|
||||
- Code scanning
|
||||
children:
|
||||
- /about-code-scanning
|
||||
- /about-code-scanning-alerts
|
||||
- /triaging-code-scanning-alerts-in-pull-requests
|
||||
- /setting-up-code-scanning-for-a-repository
|
||||
- /managing-code-scanning-alerts-for-your-repository
|
||||
@@ -28,4 +29,4 @@ children:
|
||||
- /running-codeql-code-scanning-in-a-container
|
||||
- /viewing-code-scanning-logs
|
||||
---
|
||||
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
|
||||
|
||||
|
||||
@@ -23,62 +23,9 @@ topics:
|
||||
- Alerts
|
||||
- Repositories
|
||||
---
|
||||
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
|
||||
## About alerts from {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
|
||||
{% data reusables.code-scanning.upload-sarif-alert-limit %}
|
||||
|
||||
## 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 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.
|
||||
|
||||
|
||||
|
||||
If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
|
||||
|
||||
When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
|
||||
|
||||
### About severity levels
|
||||
|
||||
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 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 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`.
|
||||
|
||||
To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
|
||||
|
||||
By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
|
||||
|
||||
### About labels for alerts that are not found in application code
|
||||
|
||||
{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
|
||||
|
||||
- **Generated**: Code generated by the build process
|
||||
- **Test**: Test code
|
||||
- **Library**: Library or third-party code
|
||||
- **Documentation**: Documentation
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
|
||||
|
||||
Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code.
|
||||
|
||||
|
||||
|
||||
On the alert page, you can see that the filepath is marked as library code (`Library` label).
|
||||
|
||||
|
||||
|
||||
## Viewing the alerts for a repository
|
||||
|
||||
Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
@@ -104,6 +51,8 @@ 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.
|
||||
|
||||
|
||||
For more information, 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)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
{% note %}
|
||||
|
||||
@@ -133,7 +82,7 @@ If you enter multiple filters, the view will show alerts matching _all_ these fi
|
||||
|
||||
{% ifversion fpt or ghes > 3.3 or ghec %}
|
||||
|
||||
You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag.
|
||||
You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% if codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, 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-experimental-alerts)."{% else %}.{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -23,7 +23,6 @@ topics:
|
||||
- Java
|
||||
---
|
||||
|
||||
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %}
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user