@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4d1e501e0348c6d7454fb2b4d9ff6457de1b19669537024ed70cb5af452cd151
|
||||
size 610675
|
||||
oid sha256:1a5d3a3ccc2216c070370ab7604ba06ef342157cabac87dc9b2979495bdc5601
|
||||
size 610870
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:de26a4c641a99cd9d8bac96d70623cd721c1178712037d6da7b848ed1eed87a7
|
||||
size 1658604
|
||||
oid sha256:36acbb974eb02ed43af68b64649df4ed634afdcb53320b1eb55b9f56d8d8b8e9
|
||||
size 1658799
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:19e9bf047eacd39ba76a589dde52a39d7635091816d21bfa5dd5ec0455b97d79
|
||||
size 952777
|
||||
oid sha256:68a8dde1afcddca73d7b55ef4b0161f7eb6c818c769df808bbac2261f01ef616
|
||||
size 952248
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e8c739e4c5a3c3284de9f4728ebae5831b517469e710fda18fc6f3b6690a07c4
|
||||
size 3903375
|
||||
oid sha256:dbaff4b180f1cdcb1a5613ee7f02fe363c8d9c43007434e6c35e8310c9f055c4
|
||||
size 3902631
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e8cf2e1914f290a6854367da381d4ed431a144cc63b9d8e2186054a5e248de7c
|
||||
size 584431
|
||||
oid sha256:8c94138496497ecbf8ede9be3885fb56d71ff05fbe5a94a52e0b9a3e4adfedd8
|
||||
size 584328
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a79ed22abe1734fb5ef312f3aaecca6b3209397d38dbe2af2a1111b0b5bcb699
|
||||
size 2703444
|
||||
oid sha256:c3d305f16be274040a2f85b2800f7320f95d378c3aa97b955addfb8f154e7a65
|
||||
size 2703886
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7707fe34b12bbfcdf7f45d774076a93089d343100ff942f62ed2c56fc7178543
|
||||
size 616771
|
||||
oid sha256:efdffa7bf12763da18f7c8cfb6f7943712eeccdf6cf2cb1d22461a0eda95a670
|
||||
size 616670
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b47ba8a38823bf30130015894b076e4fced460e987b002b3e820dc76503efdb4
|
||||
size 3419013
|
||||
oid sha256:854a680d1906124a8229717da9d45e6877143fb59cbad9626fc40a2b5de23aa7
|
||||
size 3419203
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:57bd4b1c2f5962413427e091b518d0df3762dfdaa7cb8e714dd987ceb5054ffb
|
||||
size 596255
|
||||
oid sha256:efabd15a7be2726fabda9893077625d004ac1c8a8af6fedc9d440c388ec9b5b2
|
||||
size 596335
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:18eb04a78a9c0ac9ddc7b0c4b8b60101f2e291a102abeddc3d8741c1af7b68f8
|
||||
size 2807440
|
||||
oid sha256:538ca77d3d24f7b6860fa21f130c72c604e3e6ef4d99137f8bcff76a553cf4b5
|
||||
size 2807923
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1e5cb92860261eeef9f7c772e0a7c129631db313e8c4a36b558bfb206220dfd4
|
||||
size 624363
|
||||
oid sha256:96c30a1e7a7eef4844dad35a6af25d379e22c6feab3920d6f205597ed9116eff
|
||||
size 624214
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0b5a96c694daaddf417899f232db2cf5428b3a97751960cca44cbcb634b72ba5
|
||||
size 1700922
|
||||
oid sha256:2ea318c405e971b66ea13afa588603a52b219fb8e340406bde1c5e582c2b0c48
|
||||
size 1699851
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6f49641d10d05a261da6b8889fb5c874a5e000f1be0c611e7fa594f3aaa3fb13
|
||||
size 977421
|
||||
oid sha256:c6966b41e6e697828cb83f68d6e3934e48c1dcd9c99e18fb8aeadbf12dd851e3
|
||||
size 977386
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a50bc0d1c1d68b46afccdff317bbfeca0e47493cdac70c1cff369255a1eaf64a
|
||||
size 3996100
|
||||
oid sha256:92d1059b4fba1bfceedd31ac77865b9653ff0d64f25c8b2ddd1108cae1bd92de
|
||||
size 3995150
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:886daea21c1092bd6cf48b25cdb58860a5625b0aa0886c72788109858fbafc5f
|
||||
size 596543
|
||||
oid sha256:d7e70bd1256b07ced5dda153e0ff418e8d1aa92dddd1565fea6f2c6e5c013a50
|
||||
size 596636
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cd71bdb4499fd85624115815b64b2cc145f26d686addc25031101efc615ea966
|
||||
size 2766239
|
||||
oid sha256:ea4d5f1c25db5f72820acdc2a3291101fb073a674f3f8d0aca531108eeacb1d0
|
||||
size 2766871
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6d117122c7be4f8c576705368f458d35639224006bfa82a908fcaf0a63719fda
|
||||
size 630151
|
||||
oid sha256:c8af6debc99c329a91a267e2f246b06173b58a0fe54ea255060c9b30a9bfd5da
|
||||
size 629982
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cdeee32bb55707536ad34a37c5771187f0b51620397d1694063926ddb1dea8b0
|
||||
size 3496433
|
||||
oid sha256:5d996de5d4d0c9bfdea0575f187be87b4ed28e3b1c485c1a34d2e7e3358ed6b3
|
||||
size 3496918
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:53653a82aa915196e959d831b9f7e34a5033e18e97db31990a581b7d10ec7a12
|
||||
size 608654
|
||||
oid sha256:893bb389935826265d16ce7b18f40f9d46697aae171f1b5f08fa6f73bde3f6a3
|
||||
size 608573
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:68543177a76f896746e9167f50c8e28811273d49593cedb4d2df7978631c3604
|
||||
size 2870290
|
||||
oid sha256:2a542126dc6a85f0c79119063171c2691416ae0b7de50653b5873816592eb2ca
|
||||
size 2870122
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:834963cc3927f24d4c901655e65425808c83fd6ce3ee135f0d4c7aeaf1b2de71
|
||||
size 635690
|
||||
oid sha256:3e96b667916711a4d1cd5a2c8fbe437db57d40787b638747d8da6a4b0ab43ef0
|
||||
size 635762
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1d574a3d0d0270feac2a83578ad82329c44d187f56ab585e1d0aefa800a236a7
|
||||
size 1726666
|
||||
oid sha256:179ffa0d449fd0224aefcc29c965a92dfb06c9de6f6bd3d3f558a008eac18d87
|
||||
size 1726549
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ece9dc9722b618850bc529b34fcf6c227b685d9440dded2339361052d97493e2
|
||||
size 1008468
|
||||
oid sha256:be5a21ac63689f5994523954df5729dea57332ea60a272e11c79b0522a6d1e02
|
||||
size 1012199
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e67d86dcf96178384dae255df19a0ffc521d968aa8de5a9dca7d26571b6b7946
|
||||
size 4116943
|
||||
oid sha256:762d47fcb78f9002872745972e996e14280920367aa84d1512a3680fa6a057fb
|
||||
size 4116785
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:aae756e02564d6bf070cada81f1ef94400c227c258a3e1fbac1e17ae4bd43e7b
|
||||
size 606987
|
||||
oid sha256:0f6fbb4fc4c485e674b045cd2681909ac785fe8cac429fed72aeb7616327cc8b
|
||||
size 606991
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ca762eec26edccd7845e8495121680658a500e656401ed597a09eac87f88f741
|
||||
size 2821100
|
||||
oid sha256:676e9843a9607eeb13ae1da4fe199d778bbd08a8a66332fcfa0f0a5518b2c62b
|
||||
size 2820863
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:aad4b77d9156b05049760e7c4ca479abac140dfc9db9fe597fad69d1c483df61
|
||||
size 641573
|
||||
oid sha256:2db4205fb2f7897cbecb32b7c07c5086be50a219f82404019ac57c63e5a40e17
|
||||
size 641640
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cc49a4bbb03709a6bba0bc9e02aafc4eee6e7c730290ebd077a1df809222e5b2
|
||||
size 3562799
|
||||
oid sha256:ef94698e6083d2bf614ae39c0a91fa02dba350d5b08421d2f368cbccf22d9fc1
|
||||
size 3564138
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2d30b5eb1175c450058af9cb4a33585cd0015a6a20990cdff54263a56038ef7a
|
||||
size 619978
|
||||
oid sha256:b13e2a8e6095cfc48182652bcbc7c27c7152b5531abc00bffba70ed1416d7796
|
||||
size 620030
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4b3ab52190ed72dbe2a3f4cd4e831bb4bb4ffe5b41f1a82afb5e8a684d368ffa
|
||||
size 2919687
|
||||
oid sha256:a0261828d9927193d4c658a11aa1fd3631bbd14bf62ba74add5ac974e0499e17
|
||||
size 2920327
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:557b5bb980d3d8cc18a69b1bca54612787ba41ad8347e02e7ad156eb895c067c
|
||||
size 656269
|
||||
oid sha256:5fe6101a26baa845a3f307183e8541da44b11b391a9d37bd2f67ff5a9860e649
|
||||
size 655883
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:86e41961bae2de3f8d770bcbde1dd5b6d0714f87d8d11758ecd55add0d832e8e
|
||||
size 1784419
|
||||
oid sha256:7b7d270dfd6ed73c8c0487818e159d28fa04962031297928bbcdb8dc37e9edca
|
||||
size 1784609
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fd55ef90a8895960f805d66b5734d481c46e4ba8d44b74b5b913805923a76992
|
||||
size 1042489
|
||||
oid sha256:bad14d5dea157f0ca43d3202df038cb320cd4c7042d99fff9c38d0018c9cd6b8
|
||||
size 1042029
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:55b47b6e8a29710b6b57f27f02650b482bc0fcd4c17836ee84359d6f4be1b429
|
||||
size 4217061
|
||||
oid sha256:0a3bd4c8e22dc62c65a9fc9a62ccc16816a87c33f47944a2a8839c7f26330094
|
||||
size 4216610
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a86df7ffb3f8e8b4ff129e61112336e6ae1c7dfbef4e7293900097ce6c7157e5
|
||||
size 625243
|
||||
oid sha256:07102915ea10a4cfe3139b58252c281f4d3d10a7cc509a429a00bda3ab23a198
|
||||
size 625081
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3f804c3ca90d52541cd1fa7a07bbb42bb56ed529aa5772ee8daa86694de1f8ba
|
||||
size 2918857
|
||||
oid sha256:7ae6611ac2e1203c0de2537eb55fd83ef6d82404d3abd4fdabc241096523943b
|
||||
size 2919857
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d70826e54408b2dabd02c5614407ec5eae1d958c68e843b10b8fff96eb48a7cc
|
||||
size 663272
|
||||
oid sha256:40c32b2ab6912b90f65b305e229c4cf28ce93a49e6ab7d3b96d8501b82790033
|
||||
size 663177
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:62348c413618e243a7d4a62b395078d0a41c6dbd2c21efc86b902a4ccb91d20c
|
||||
size 3682705
|
||||
oid sha256:7f2278696a418b65381861a0559769ae3ce9b13e41de168f1ab9972f0304fc5a
|
||||
size 3682810
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e236bb3e1d6406ee0f4a242fa25823e46479601d5018e25d7d74757c1fede5fc
|
||||
size 639005
|
||||
oid sha256:8ada660b18081cfca90a9f3122f0c9a0d01df3e7746f632fe53f79ef37656c27
|
||||
size 638952
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:aa11b795e3b468f91b55b23dd18dcaa972b57ef45490b6cf05d02b0e954c2e3f
|
||||
size 3006823
|
||||
oid sha256:8b9a94f6bc23cee4f5480c88e72ed05b2ac732c2c1585d7a5ee4cca938a39144
|
||||
size 3006541
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:62a7f2e4f66df357c261e85c156c01f3df8ee0a049c917f425655f717d7330f7
|
||||
size 846358
|
||||
oid sha256:dc298a2023686b9d84da8651238ca899cfeaadfe44ef562f43b246d1f80db2e5
|
||||
size 846485
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bff1c921b710f2e7ac1074af931f4f45bde90e5ddf10c0296b90c5b21add0bd6
|
||||
size 1971460
|
||||
oid sha256:49f6fa7a872e9a59b8abeb69f7076073e6eaa181eae2bef5157f0ed44683c631
|
||||
size 1972475
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:482fbbeb4be48ac7d3686babba7b9361f514a43aba3b16176dc91e67267201a1
|
||||
size 1318344
|
||||
oid sha256:608791d15597850ab5f99799656a3eec3759ed20366d082401039bde47ebfa30
|
||||
size 1325110
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:307252ac9c404aa14830d908ea3b2cf033320b079b06922db18a1b5145468bf2
|
||||
size 5061680
|
||||
oid sha256:1c8a04a47ebde877bc242a185bfeaf748fd85b02ea5e278581b86b132ae7b5c9
|
||||
size 5062996
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d71b9489dff2523ba510387d24d8f4147e56752286aacb00b32167ac33a76b31
|
||||
size 795919
|
||||
oid sha256:76cb6a4cc7b9db561bf25653ac64e21700c7cf936c83ab82c37753202224632a
|
||||
size 796100
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4ec201ed0b1cfea9baed94c0ab0639a0da39cc08a5098bc8f5c479da8aea826e
|
||||
size 3505760
|
||||
oid sha256:aa758352dc58204d8429573b43a7cca571f5612c9fb05656e69060cec6407013
|
||||
size 3504286
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2350992d5e90e09ee37d187a0c17d53ce3d38559e5411b56679dcf07ce831d5c
|
||||
size 858691
|
||||
oid sha256:df9cad269c9dcb283fb408b83ccac978a735c07effce04f0143ff7c7f204bb49
|
||||
size 858827
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:04d4e93c1ba7d318e70e971bfc58c5df40f021efe87183c1c96594a15a93763b
|
||||
size 4501066
|
||||
oid sha256:5ce2a91b742770566b572f79d65963cfe74ee978f33eb87db5da2093f79c512f
|
||||
size 4501058
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a702f3af4db73a54e2905786e9baf156488f5be4764913b8566765af4ffae621
|
||||
size 810483
|
||||
oid sha256:4bb761cfc58e0fa0b01bf5dba72ee77ab3c142f49e4b3dd5f12efebd9edfc3e3
|
||||
size 810174
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bfba688a45fb872ab6a5a240718e7207688e5d2a1c7424e42b765631faf5b85f
|
||||
size 3594461
|
||||
oid sha256:ab14a6f241e74b6071925f90ef62432a0fcffe35d6a86665ae3d34b1d29a8835
|
||||
size 3593914
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a4da7dfd5f79d15c4faa70deb05a3d8240df00bde941c584800cae7416a38c21
|
||||
size 509983
|
||||
oid sha256:61819e4d386853aa9cd47953d7abf7f21dbf6a814ee2bf80bd7307bfd17a367b
|
||||
size 510081
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9ebd2296c564d0c13d52e1500520cf9950cbcc49aa9a414d677f694562afc494
|
||||
size 1330088
|
||||
oid sha256:b95cb9b8820ce80a802aeadfd27a00152b959da81e8436ef04b8abaadca2c161
|
||||
size 1330024
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:aad570cba2ba8f28e68ae96f6a2f21d8eabb3864abdd165b5dc45db512e52a06
|
||||
size 831221
|
||||
oid sha256:f82dd88890220541328a396fd72eeb4de1895d0dd03eb56bc194a51ae206362d
|
||||
size 831173
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2a8049cb57d006c72a0794ac7ac0ff90f7c704485c57519f35f6c93bd5e11d38
|
||||
size 3335205
|
||||
oid sha256:3de6a6e352bd272beaec58e992aa43587ad491c8b507ecc91fb29b6deb643ff8
|
||||
size 3336379
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:81ea2dba5a9349ebfa438f0ef39b769a5a03a1834360cbb4b830a92bd79c9ce1
|
||||
size 487929
|
||||
oid sha256:f4c43a06b159c4f946592f2424b16a13b32e40c16e1918abfadd3c23c325770f
|
||||
size 487901
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ad392eeff32c4c39fa9dc37b51f34b1e80a54eb26865ee1c5f74f57421a69468
|
||||
size 2196113
|
||||
oid sha256:ef2e44666e77306dc20d1e8a921ee304959002d54abff4da29a88e82b8a9bec6
|
||||
size 2194954
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2da24e4730b6eecfd20aef7e757f897e3d9711b6bc43bee0dc84f0befd53e505
|
||||
size 515521
|
||||
oid sha256:174894b6448326477d3d74d7c7ed6a122a865d203935310dfad4ed29bbda29f2
|
||||
size 515509
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9a42e755b42a05fa5abaac64f9c4864febfb62a6204bb3b8619f83b6ef77ff9d
|
||||
size 2746039
|
||||
oid sha256:0af59e207df49a1c6221ad403f131de27aef2eb768123fc53a69b5a878c4f9de
|
||||
size 2746351
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e7fedc7858d305e7a091dad9fb66c9be8adfba8a1c1ed0f75bbfc99e7a0bc150
|
||||
size 500218
|
||||
oid sha256:35d18144ef396d2c0032b46be5eb90c020088722422c924d656c85a0621dfb3e
|
||||
size 500275
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:355368427f64fcd392c6241091d229e61c740284c11c1bb2c059daab22b6a0b2
|
||||
size 2277398
|
||||
oid sha256:7c0fa6bae59c4d0fe9beeda4e438f57e592d1d137ffe2ee48888e77c41fbdfd8
|
||||
size 2276409
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:741c0f7d0de230bc3c422f4043805368dd0c1b5a2a1549e13289ce333350f4e2
|
||||
size 770648
|
||||
oid sha256:1cb45a624a1155e0d23faaab5bf4f8a05664a1b30e1d222402299731c5bc0253
|
||||
size 770555
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d64c5fb18764e04c1e8f51a87d4d77269c4cf2bfb632fce7e6b6c4123a58e1b4
|
||||
size 1988547
|
||||
oid sha256:f9c1a21f0ba76b7541c95573813286a45a29abb880d9fa086facf73921ba2c23
|
||||
size 1988193
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f639c6b3a5ce25ec4bdaba4e2c7ec329001991f5a3f961a7024368ef960bd42d
|
||||
size 1186157
|
||||
oid sha256:d761e20d94679f26f47a73b7827e8bbe548fa618052890cd0ab624f0f526e198
|
||||
size 1186527
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:77ce50a4077a8d3d73f66fb9a2e25eb8304b5bdc486748f56c236ecab7895bf0
|
||||
size 4790370
|
||||
oid sha256:6e55b6874002c21a9428adab9685d2b2a82cc1adfb4d9c83c5055fa177fcbc0c
|
||||
size 4791571
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f272dce0200833fcea3d1f8da0bfde6b3040a04b40b1ef18e3807e5ed49c2ed5
|
||||
size 740692
|
||||
oid sha256:42ba7457c895fb62434af9eaf0de4c73bea943667b8449de903c99b8c87ca85f
|
||||
size 740566
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ef53e25967fa8e83712df72372a7e3edb60c30d868636e1010871b52d0ef8276
|
||||
size 3447782
|
||||
oid sha256:774a199c6192647d60a4076e18fc273740b264b1f439353b699704ba97520855
|
||||
size 3447924
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:236ff7d5384695110a860973ff6e53bef7447f4bb854e8fbcecb523a1343e533
|
||||
size 785390
|
||||
oid sha256:7da3a8b7a68d2e100110fcef073863d273b9e52d5e4cfa1df48d03b1049b6772
|
||||
size 785207
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:92ec3b77488b5cd1f2dd9934b4de562609381474c08868e9e249c069ee7b682f
|
||||
size 4340916
|
||||
oid sha256:48f9d6df0a3d38a95c249b1394fed5da3aaff9d8f1350f0324f7e14e0440fff1
|
||||
size 4340716
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:80a6b35e31d3657d6d0d43ffa7c26ce4639f4e868970575a2a6c6ab4c9902d55
|
||||
size 754701
|
||||
oid sha256:44854c698277c32aa45dc1ba634704e20ee83526cc32f90fa44370b14ac2605d
|
||||
size 754632
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:62a5f1fc498b61c46cf48211703a3b1f6151d0f85cdc2cfda6c6ce2fc91b969a
|
||||
size 3529592
|
||||
oid sha256:d2bf21eb03a97eca3f4896507821a6e5de81022e988b0833b604281527ca70c2
|
||||
size 3529627
|
||||
|
||||
@@ -60,7 +60,15 @@ translations/zh-CN/content/actions/deployment/about-deployments/about-continuous
|
||||
translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/about-deployments/index.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error
|
||||
@@ -262,6 +270,7 @@ translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-ser
|
||||
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-github-ae.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md,rendering error
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
|
||||
@@ -420,6 +429,7 @@ translations/zh-CN/content/code-security/supply-chain-security/keeping-your-depe
|
||||
translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,parsing error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,rendering error
|
||||
@@ -460,9 +470,19 @@ translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/set
|
||||
translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md,rendering error
|
||||
translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/index.md,rendering error
|
||||
translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,rendering error
|
||||
translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error
|
||||
translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error
|
||||
translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md,rendering error
|
||||
translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md,rendering error
|
||||
translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/index.md,rendering error
|
||||
translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
|
||||
translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md,rendering error
|
||||
translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md,rendering error
|
||||
translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md,rendering error
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md,rendering error
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,rendering error
|
||||
@@ -471,24 +491,64 @@ translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/ins
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md,rendering error
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,rendering error
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/index.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-oauth-apps/index.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/guides/using-content-attachments.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/index.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-github-apps/index.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-oauth-apps/index.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/index.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/index.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error
|
||||
translations/zh-CN/content/developers/overview/managing-deploy-keys.md,rendering error
|
||||
translations/zh-CN/content/developers/overview/replacing-github-services.md,rendering error
|
||||
translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,rendering error
|
||||
translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md,rendering error
|
||||
translations/zh-CN/content/developers/webhooks-and-events/webhooks/about-webhooks.md,rendering error
|
||||
translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
|
||||
translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,rendering error
|
||||
@@ -522,11 +582,16 @@ translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
|
||||
translations/zh-CN/content/get-started/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/githubs-products.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/be-social.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/communicating-on-github.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/create-a-repo.md,rendering error
|
||||
@@ -600,9 +665,20 @@ translations/zh-CN/content/graphql/guides/migrating-graphql-global-node-ids.md,r
|
||||
translations/zh-CN/content/graphql/index.md,rendering error
|
||||
translations/zh-CN/content/graphql/reference/mutations.md,rendering error
|
||||
translations/zh-CN/content/issues/guides.md,rendering error
|
||||
translations/zh-CN/content/issues/index.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md,rendering error
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,rendering error
|
||||
translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,rendering error
|
||||
translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,rendering error
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,rendering error
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
|
||||
@@ -688,20 +764,41 @@ translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pag
|
||||
translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/index.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md,rendering error
|
||||
translations/zh-CN/content/pages/index.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,rendering error
|
||||
@@ -760,14 +857,19 @@ translations/zh-CN/content/repositories/working-with-files/using-files/navigatin
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/basics-of-authentication.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/rest/guides/basics-of-authentication.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/best-practices-for-integrators.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/building-a-ci-server.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/delivering-deployments.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/index.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/traversing-with-pagination.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/working-with-comments.md,rendering error
|
||||
translations/zh-CN/content/rest/index.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/api-previews.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/libraries.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/rest/overview/other-authentication-methods.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,Listed in localization-support#489
|
||||
@@ -794,6 +896,8 @@ translations/zh-CN/content/rest/reference/teams.md,rendering error
|
||||
translations/zh-CN/content/rest/reference/webhooks.md,rendering error
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error
|
||||
translations/zh-CN/content/search-github/index.md,rendering error
|
||||
translations/zh-CN/content/search-github/searching-on-github/searching-commits.md,rendering error
|
||||
translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md,rendering error
|
||||
translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
|
||||
|
||||
|
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /github/automating-your-workflow-with-github-actions/building-actions
|
||||
- /actions/automating-your-workflow-with-github-actions/building-actions
|
||||
- /actions/building-actions
|
||||
- /articles/creating-a-github-action/
|
||||
- /articles/creating-a-github-action
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -0,0 +1,153 @@
|
||||
---
|
||||
title: Deploying Docker to Azure App Service
|
||||
intro: You can deploy a Docker container to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Containers
|
||||
- Docker
|
||||
- Azure App Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
{% data reusables.actions.create-azure-app-plan %}
|
||||
|
||||
1. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--deployment-container-image-name nginx:latest
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
{% data reusables.actions.create-azure-publish-profile %}
|
||||
|
||||
1. Set registry credentials for your web app.
|
||||
|
||||
Create a personal access token with the `repo` and `read:packages` scopes. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
|
||||
Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command:
|
||||
|
||||
```shell
|
||||
az webapp config appsettings set \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--settings DOCKER_REGISTRY_SERVER_URL=https://ghcr.io DOCKER_REGISTRY_SERVER_USERNAME=MY_REPOSITORY_OWNER DOCKER_REGISTRY_SERVER_PASSWORD=MY_PERSONAL_ACCESS_TOKEN
|
||||
```
|
||||
|
||||
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
|
||||
5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
|
||||
{% endif %}
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created.
|
||||
|
||||
{% data reusables.actions.delete-env-key %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Build and deploy a container to an Azure Web App
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
permissions:
|
||||
contents: 'read'
|
||||
packages: 'write'
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Set up Docker Buildx
|
||||
uses: docker/setup-buildx-action@v1
|
||||
|
||||
- name: Log in to GitHub container registry
|
||||
uses: docker/login-action@v1.10.0
|
||||
with:
|
||||
registry: ghcr.io
|
||||
username: {% raw %}${{ github.actor }}{% endraw %}
|
||||
password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
|
||||
|
||||
- name: Lowercase the repo name
|
||||
run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
|
||||
|
||||
- name: Build and push container image to registry
|
||||
uses: docker/build-push-action@v2
|
||||
with:
|
||||
push: true
|
||||
tags: ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
|
||||
file: ./Dockerfile
|
||||
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
needs: build
|
||||
environment:
|
||||
name: 'production'
|
||||
url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
|
||||
|
||||
steps:
|
||||
- name: Lowercase the repo name
|
||||
run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
|
||||
|
||||
- name: Deploy to Azure Web App
|
||||
id: deploy-to-webapp
|
||||
uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
|
||||
with:
|
||||
app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
|
||||
publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
|
||||
images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}'
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,134 @@
|
||||
---
|
||||
title: Deploying Java to Azure App Service
|
||||
intro: You can deploy your Java project to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Java
|
||||
- Azure App Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
{% data reusables.actions.create-azure-app-plan %}
|
||||
|
||||
1. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--runtime "JAVA|11-java11"
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
{% data reusables.actions.create-azure-publish-profile %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
|
||||
1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
|
||||
{% endif %}
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you want to use a Java version other than `11`, change `JAVA_VERSION`.
|
||||
|
||||
{% data reusables.actions.delete-env-key %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Build and deploy JAR app to Azure Web App
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
JAVA_VERSION: '11' # set this to the Java version to use
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Set up Java version
|
||||
uses: actions/setup-java@v2.3.1
|
||||
with:
|
||||
java-version: {% raw %}${{ env.JAVA_VERSION }}{% endraw %}
|
||||
cache: 'maven'
|
||||
|
||||
- name: Build with Maven
|
||||
run: mvn clean install
|
||||
|
||||
- name: Upload artifact for deployment job
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: java-app
|
||||
path: '{% raw %}${{ github.workspace }}{% endraw %}/target/*.jar'
|
||||
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
needs: build
|
||||
environment:
|
||||
name: 'production'
|
||||
url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
|
||||
|
||||
steps:
|
||||
- name: Download artifact from build job
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: java-app
|
||||
|
||||
- name: Deploy to Azure Web App
|
||||
id: deploy-to-webapp
|
||||
uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
|
||||
with:
|
||||
app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
|
||||
publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
|
||||
package: '*.jar'
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,144 @@
|
||||
---
|
||||
title: Deploying .NET to Azure App Service
|
||||
intro: You can deploy your .NET project to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Azure App Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
{% data reusables.actions.create-azure-app-plan %}
|
||||
|
||||
2. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--runtime "DOTNET|5.0"
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
{% data reusables.actions.create-azure-publish-profile %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
|
||||
5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
|
||||
{% endif %}
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`. If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
|
||||
|
||||
{% data reusables.actions.delete-env-key %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Build and deploy ASP.Net Core app to an Azure Web App
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
|
||||
DOTNET_VERSION: '5' # set this to the .NET Core version to use
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Set up .NET Core
|
||||
uses: actions/setup-dotnet@v1
|
||||
with:
|
||||
dotnet-version: {% raw %}${{ env.DOTNET_VERSION }}{% endraw %}
|
||||
|
||||
- name: Set up dependency caching for faster builds
|
||||
uses: actions/cache@v2
|
||||
with:
|
||||
path: ~/.nuget/packages
|
||||
key: {% raw %}${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}{% endraw %}
|
||||
restore-keys: |
|
||||
{% raw %}${{ runner.os }}-nuget-{% endraw %}
|
||||
|
||||
- name: Build with dotnet
|
||||
run: dotnet build --configuration Release
|
||||
|
||||
- name: dotnet publish
|
||||
run: dotnet publish -c Release -o {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp
|
||||
|
||||
- name: Upload artifact for deployment job
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: .net-app
|
||||
path: {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp
|
||||
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
needs: build
|
||||
environment:
|
||||
name: 'production'
|
||||
url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
|
||||
|
||||
steps:
|
||||
- name: Download artifact from build job
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: .net-app
|
||||
|
||||
- name: Deploy to Azure Web App
|
||||
id: deploy-to-webapp
|
||||
uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
|
||||
with:
|
||||
app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
|
||||
publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
|
||||
package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,141 @@
|
||||
---
|
||||
title: Deploying Node.js to Azure App Service
|
||||
intro: You can deploy your Node.js project to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
redirect_from:
|
||||
- /actions/guides/deploying-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Node
|
||||
- JavaScript
|
||||
- Azure App Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
{% data reusables.actions.create-azure-app-plan %}
|
||||
|
||||
2. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--runtime "NODE|14-lts"
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
{% data reusables.actions.create-azure-publish-profile %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
|
||||
5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
|
||||
{% endif %}
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
|
||||
|
||||
{% data reusables.actions.delete-env-key %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
|
||||
NODE_VERSION: '14.x' # set this to the node version to use
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Set up Node.js
|
||||
uses: actions/setup-node@v2
|
||||
with:
|
||||
node-version: {% raw %}${{ env.NODE_VERSION }}{% endraw %}
|
||||
cache: 'npm'
|
||||
|
||||
- name: npm install, build, and test
|
||||
run: |
|
||||
npm install
|
||||
npm run build --if-present
|
||||
npm run test --if-present
|
||||
- name: Upload artifact for deployment job
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: node-app
|
||||
path: .
|
||||
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
needs: build
|
||||
environment:
|
||||
name: 'production'
|
||||
url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
|
||||
|
||||
steps:
|
||||
- name: Download artifact from build job
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: node-app
|
||||
|
||||
- name: 'Deploy to Azure WebApp'
|
||||
id: deploy-to-webapp
|
||||
uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
|
||||
with:
|
||||
app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
|
||||
publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
|
||||
package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the
|
||||
[actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
|
||||
@@ -0,0 +1,155 @@
|
||||
---
|
||||
title: Deploying PHP to Azure App Service
|
||||
intro: You can deploy your PHP project to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Azure App Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
{% data reusables.actions.create-azure-app-plan %}
|
||||
|
||||
2. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--runtime "php|7.4"
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
{% data reusables.actions.create-azure-publish-profile %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
|
||||
5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
|
||||
{% endif %}
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
|
||||
|
||||
{% data reusables.actions.delete-env-key %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Build and deploy PHP app to Azure Web App
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
|
||||
PHP_VERSION: '8.x' # set this to the PHP version to use
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Setup PHP
|
||||
uses: shivammathur/setup-php@v2
|
||||
with:
|
||||
php-version: {% raw %}${{ env.PHP_VERSION }}{% endraw %}
|
||||
|
||||
- name: Check if composer.json exists
|
||||
id: check_files
|
||||
uses: andstor/file-existence-action@v1
|
||||
with:
|
||||
files: 'composer.json'
|
||||
|
||||
- name: Get Composer Cache Directory
|
||||
id: composer-cache
|
||||
if: steps.check_files.outputs.files_exists == 'true'
|
||||
run: |
|
||||
echo "::set-output name=dir::$(composer config cache-files-dir)"
|
||||
|
||||
- name: Set up dependency caching for faster installs
|
||||
uses: actions/cache@v2
|
||||
if: steps.check_files.outputs.files_exists == 'true'
|
||||
with:
|
||||
path: {% raw %}${{ steps.composer-cache.outputs.dir }}{% endraw %}
|
||||
key: {% raw %}${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}{% endraw %}
|
||||
restore-keys: |
|
||||
{% raw %}${{ runner.os }}-composer-{% endraw %}
|
||||
|
||||
- name: Run composer install if composer.json exists
|
||||
if: steps.check_files.outputs.files_exists == 'true'
|
||||
run: composer validate --no-check-publish && composer install --prefer-dist --no-progress
|
||||
|
||||
- name: Upload artifact for deployment job
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: php-app
|
||||
path: .
|
||||
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
needs: build
|
||||
environment:
|
||||
name: 'production'
|
||||
url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
|
||||
|
||||
steps:
|
||||
- name: Download artifact from build job
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: php-app
|
||||
|
||||
- name: 'Deploy to Azure Web App'
|
||||
id: deploy-to-webapp
|
||||
uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
|
||||
with:
|
||||
app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
|
||||
publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
|
||||
package: .
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,151 @@
|
||||
---
|
||||
title: Deploying Python to Azure App Service
|
||||
intro: You can deploy your Python project to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Python
|
||||
- Azure App Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
{% data reusables.actions.create-azure-app-plan %}
|
||||
|
||||
1. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--runtime "python|3.8"
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
{% data reusables.actions.create-azure-publish-profile %}
|
||||
|
||||
1. Add an app setting called `SCM_DO_BUILD_DURING_DEPLOYMENT` and set the value to `1`.
|
||||
|
||||
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
|
||||
5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
|
||||
{% endif %}
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
|
||||
|
||||
{% data reusables.actions.delete-env-key %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Build and deploy Python app to Azure Web App
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
PYTHON_VERSION: '3.8' # set this to the Python version to use
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Set up Python version
|
||||
uses: actions/setup-python@v2.2.2
|
||||
with:
|
||||
python-version: {% raw %}${{ env.PYTHON_VERSION }}{% endraw %}
|
||||
|
||||
- name: Create and start virtual environment
|
||||
run: |
|
||||
python -m venv venv
|
||||
source venv/bin/activate
|
||||
|
||||
- name: Set up dependency caching for faster installs
|
||||
uses: actions/cache@v2
|
||||
with:
|
||||
path: ~/.cache/pip
|
||||
key: {% raw %}${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}{% endraw %}
|
||||
restore-keys: |
|
||||
{% raw %}${{ runner.os }}-pip-{% endraw %}
|
||||
|
||||
- name: Install dependencies
|
||||
run: pip install -r requirements.txt
|
||||
|
||||
# Optional: Add a step to run tests here (PyTest, Django test suites, etc.)
|
||||
|
||||
- name: Upload artifact for deployment jobs
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: python-app
|
||||
path: |
|
||||
.
|
||||
!venv/
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
needs: build
|
||||
environment:
|
||||
name: 'production'
|
||||
url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
|
||||
|
||||
steps:
|
||||
- name: Download artifact from build job
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: python-app
|
||||
path: .
|
||||
|
||||
- name: 'Deploy to Azure Web App'
|
||||
id: deploy-to-webapp
|
||||
uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
|
||||
with:
|
||||
app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
|
||||
publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,126 @@
|
||||
---
|
||||
title: Deploying to Azure Kubernetes Service
|
||||
intro: You can deploy your project to Azure Kubernetes Service (AKS) as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Azure Kubernetes Service
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
1. Create a target AKS cluster and an Azure Container Registry (ACR). For more information, see "[Quickstart: Deploy an AKS cluster by using the Azure portal - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" and "[Quickstart - Create registry in portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" in the Azure documentation.
|
||||
|
||||
1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository.
|
||||
|
||||
Under the workflow `env` key, change the the following values:
|
||||
- `AZURE_CONTAINER_REGISTRY` to the name of your container registry
|
||||
- `PROJECT_NAME` to the name of your project
|
||||
- `RESOURCE_GROUP` to the resource group containing your AKS cluster
|
||||
- `CLUSTER_NAME` to the name of your AKS cluster
|
||||
|
||||
This workflow uses the `helm` render engine for the [`azure/k8s-bake` action](https://github.com/Azure/k8s-bake). If you will use the `helm` render engine, change the value of `CHART_PATH` to the path to your helm file. Change `CHART_OVERRIDE_PATH` to an array of override file paths. If you use a different render engine, update the input parameters sent to the `azure/k8s-bake` action.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Build and deploy to Azure Kubernetes Service
|
||||
|
||||
env:
|
||||
AZURE_CONTAINER_REGISTRY: MY_REGISTRY_NAME # set this to the name of your container registry
|
||||
PROJECT_NAME: MY_PROJECT_NAME # set this to your project's name
|
||||
RESOURCE_GROUP: MY_RESOURCE_GROUP # set this to the resource group containing your AKS cluster
|
||||
CLUSTER_NAME: MY_CLUSTER_NAME # set this to the name of your AKS cluster
|
||||
REGISTRY_URL: MY_REGISTRY_URL # set this to the URL of your registry
|
||||
# If you bake using helm:
|
||||
CHART_PATH: MY_HELM_FILE # set this to the path to your helm file
|
||||
CHART_OVERRIDE_PATH: MY_OVERRIDE_FILES # set this to an array of override file paths
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@master
|
||||
|
||||
- name: Azure Login
|
||||
uses: azure/login@89d153571fe9a34ed70fcf9f1d95ab8debea7a73
|
||||
with:
|
||||
creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %}
|
||||
|
||||
- name: Build image on ACR
|
||||
uses: azure/CLI@7378ce2ca3c38b4b063feb7a4cbe384fef978055
|
||||
with:
|
||||
azcliversion: 2.29.1
|
||||
inlineScript: |
|
||||
az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}
|
||||
az acr build -t -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
|
||||
|
||||
- name: Gets K8s context
|
||||
uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa
|
||||
with:
|
||||
creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %}
|
||||
resource-group: {% raw %}${{ env.RESOURCE_GROUP }}{% endraw %}
|
||||
cluster-name: {% raw %}${{ env.CLUSTER_NAME }}{% endraw %}
|
||||
id: login
|
||||
|
||||
- name: Configure deployment
|
||||
uses: azure/k8s-bake@773b6144a3732e3bf4c78b146a0bb9617b2e016b
|
||||
with:
|
||||
renderEngine: 'helm'
|
||||
helmChart: {% raw %}${{ env.CHART_PATH }}{% endraw %}
|
||||
overrideFiles: {% raw %}${{ env.CHART_OVERRIDE_PATH }}{% endraw %}
|
||||
overrides: |
|
||||
replicas:2
|
||||
helm-version: 'latest'
|
||||
id: bake
|
||||
|
||||
- name: Deploys application
|
||||
- uses: Azure/k8s-deploy@c8fbd76ededaad2799c054a9fd5d0fa5d4e9aee4
|
||||
with:
|
||||
manifests: {% raw %}${{ steps.bake.outputs.manifestsBundle }}{% endraw %}
|
||||
images: |
|
||||
{% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}.azurecr.io/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
|
||||
imagepullsecrets: |
|
||||
{% raw %}${{ env.PROJECT_NAME }}{% endraw %}
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,113 @@
|
||||
---
|
||||
title: Deploying to Azure Static Web App
|
||||
intro: You can deploy your web app to Azure Static Web App as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CD
|
||||
- Azure Static Web Apps
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
|
||||
|
||||
{% ifversion fpt or ghec or ghae-issue-4856 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation.
|
||||
|
||||
2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation.
|
||||
|
||||
## Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed.
|
||||
|
||||
Under the workflow `env` key, change the following values:
|
||||
- `APP_LOCATION` to the location of your client code
|
||||
- `API_LOCATION` to the location of your API source code. If `API_LOCATION` is not relevant, you can delete the variable and the lines where it is used.
|
||||
- `APP_ARTIFACT_LOCATION` to the location of your client code build output
|
||||
|
||||
For more information about these values, see "[Build configuration for Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions)" in the Azure documentation.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
name: Deploy web app to Azure Static Web Apps
|
||||
|
||||
env:
|
||||
APP_LOCATION: "/" # location of your client code
|
||||
API_LOCATION: "api" # location of your api source code - optional
|
||||
APP_ARTIFACT_LOCATION: "build" # location of client code build output
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
pull_request:
|
||||
types: [opened, synchronize, reopened, closed]
|
||||
branches:
|
||||
- main
|
||||
|
||||
permissions:
|
||||
issues: write
|
||||
|
||||
jobs:
|
||||
build_and_deploy:
|
||||
if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed')
|
||||
runs-on: ubuntu-latest
|
||||
name: Build and Deploy
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
with:
|
||||
submodules: true
|
||||
- name: Build And Deploy
|
||||
uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
|
||||
with:
|
||||
azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %}
|
||||
repo_token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
|
||||
action: "upload"
|
||||
app_location: {% raw %}${{ env.APP_LOCATION }}{% endraw %}
|
||||
api_location: {% raw %}${{ env.API_LOCATION }}{% endraw %}
|
||||
app_artifact_location: {% raw %}${{ env.APP_ARTIFACT_LOCATION }}{% endraw %}
|
||||
|
||||
close:
|
||||
if: github.event_name == 'pull_request' && github.event.action == 'closed'
|
||||
runs-on: ubuntu-latest
|
||||
name: Close
|
||||
steps:
|
||||
- name: Close
|
||||
uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
|
||||
with:
|
||||
azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %}
|
||||
action: "close"
|
||||
```
|
||||
|
||||
## Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
@@ -0,0 +1,19 @@
|
||||
---
|
||||
title: Deploying to Azure
|
||||
shortTitle: Deploy to Azure
|
||||
intro: Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
children:
|
||||
- /deploying-nodejs-to-azure-app-service
|
||||
- /deploying-python-to-azure-app-service
|
||||
- /deploying-java-to-azure-app-service
|
||||
- /deploying-net-to-azure-app-service
|
||||
- /deploying-php-to-azure-app-service
|
||||
- /deploying-docker-to-azure-app-service
|
||||
- /deploying-to-azure-static-web-app
|
||||
- /deploying-to-azure-kubernetes-service
|
||||
---
|
||||
@@ -4,10 +4,11 @@ shortTitle: Deploying to your cloud provider
|
||||
intro: 'You can deploy to various cloud providers, such as AWS, Azure, and GKE.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: 'issue-4856'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
children:
|
||||
- /deploying-to-amazon-elastic-container-service
|
||||
- /deploying-to-azure-app-service
|
||||
- /deploying-to-azure
|
||||
- /deploying-to-google-kubernetes-engine
|
||||
---
|
||||
|
||||
@@ -43,7 +43,6 @@ includeGuides:
|
||||
- /actions/using-containerized-services/creating-redis-service-containers
|
||||
- /actions/using-containerized-services/creating-postgresql-service-containers
|
||||
- /actions/deployment/deploying-to-amazon-elastic-container-service
|
||||
- /actions/deployment/deploying-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-google-kubernetes-engine
|
||||
- /actions/learn-github-actions/essential-features-of-github-actions
|
||||
- /actions/security-guides/security-hardening-for-github-actions
|
||||
@@ -64,5 +63,13 @@ includeGuides:
|
||||
- /actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column
|
||||
- /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions
|
||||
- /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app
|
||||
- /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service
|
||||
---
|
||||
|
||||
|
||||
@@ -30,10 +30,10 @@ changelog:
|
||||
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/
|
||||
- /articles/customizing-your-project-with-github-actions/
|
||||
- /articles/automating-your-workflow-with-github-actions
|
||||
- /articles/customizing-your-project-with-github-actions
|
||||
- /github/automating-your-workflow-with-github-actions
|
||||
- /actions/automating-your-workflow-with-github-actions/
|
||||
- /actions/automating-your-workflow-with-github-actions
|
||||
- /categories/automating-your-workflow-with-github-actions
|
||||
- /marketplace/actions
|
||||
- /actions/reference
|
||||
|
||||
@@ -221,7 +221,7 @@ The following table indicates where each context and special function can be use
|
||||
|
||||
| Path | Context | Special functions |
|
||||
| ---- | ------- | ----------------- |
|
||||
| <code>concurrency</code> | <code>github</code> | |
|
||||
| <code>concurrency</code> | <code>github, inputs</code> | |
|
||||
| <code>env</code> | <code>github, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
|
||||
| <code>jobs.<job_id>.container</code> | <code>github, needs, strategy, matrix, inputs</code> | |
|
||||
|
||||
@@ -11,7 +11,7 @@ redirect_from:
|
||||
- /actions/getting-started-with-github-actions/overview
|
||||
- /actions/getting-started-with-github-actions/getting-started-with-github-actions
|
||||
- /actions/configuring-and-managing-workflows/configuring-a-workflow
|
||||
- /articles/creating-a-workflow-with-github-actions/
|
||||
- /articles/creating-a-workflow-with-github-actions
|
||||
- /articles/configuring-a-workflow
|
||||
- /github/automating-your-workflow-with-github-actions/configuring-a-workflow
|
||||
- /actions/automating-your-workflow-with-github-actions/configuring-a-workflow
|
||||
|
||||
@@ -18,9 +18,9 @@ topics:
|
||||
|
||||
## Overview
|
||||
|
||||
Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
|
||||
Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
|
||||
|
||||
Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained.
|
||||
Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained.
|
||||
|
||||
The diagram below shows three build jobs on the left of the diagram. After each of these jobs completes successfully a dependent job called "Deploy" runs. This job calls a reusable workflow that contains three jobs: "Staging", "Review", and "Production." The "Production" deployment job only runs after the "Staging" job has completed successfully. Using a reusable workflow to run deployment jobs allows you to run those jobs for each build without duplicating code in workflows.
|
||||
|
||||
@@ -67,7 +67,6 @@ Called workflows can access self-hosted runners from caller's context. This mean
|
||||
* Reusable workflows can't call other reusable workflows.
|
||||
* Reusable workflows stored within a private repository can only be used by workflows within the same repository.
|
||||
* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)."
|
||||
* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs.<job_id>.concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)."
|
||||
* The `strategy` property is not supported in any job that calls a reusable workflow.
|
||||
|
||||
## Creating a reusable workflow
|
||||
@@ -77,13 +76,13 @@ Reusable workflows are YAML-formatted files, very similar to any other workflow
|
||||
For a workflow to be reusable, the values for `on` must include `workflow_call`:
|
||||
|
||||
```yaml
|
||||
on:
|
||||
on:
|
||||
workflow_call:
|
||||
```
|
||||
|
||||
### Using inputs and secrets in a reusable workflow
|
||||
|
||||
You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow.
|
||||
You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow.
|
||||
|
||||
1. In the reusable workflow, use the `inputs` and `secrets` keywords to define inputs or secrets that will be passed from a caller workflow.
|
||||
{% raw %}
|
||||
@@ -112,10 +111,10 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
- uses: ./.github/actions/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.envPAT }}
|
||||
token: ${{ secrets.envPAT }}
|
||||
```
|
||||
{% endraw %}
|
||||
In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
|
||||
In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -153,7 +152,7 @@ jobs:
|
||||
- uses: ./.github/actions/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.token }}
|
||||
token: ${{ secrets.token }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -163,7 +162,7 @@ You call a reusable workflow by using the `uses` keyword. Unlike when you are us
|
||||
|
||||
[`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
|
||||
|
||||
You reference reusable workflow files using the syntax:
|
||||
You reference reusable workflow files using the syntax:
|
||||
|
||||
`{owner}/{repo}/{path}/{filename}@{ref}`
|
||||
|
||||
@@ -191,7 +190,7 @@ When you call a reusable workflow, you can only use the following keywords in th
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:**
|
||||
**Note:**
|
||||
|
||||
* If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
|
||||
* The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow.
|
||||
@@ -226,7 +225,7 @@ jobs:
|
||||
|
||||
## Using outputs from a reusable workflow
|
||||
|
||||
A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.
|
||||
A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.
|
||||
|
||||
The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`.
|
||||
|
||||
@@ -243,12 +242,12 @@ on:
|
||||
value: ${{ jobs.example_job.outputs.output1 }}
|
||||
secondword:
|
||||
description: "The second output string"
|
||||
value: ${{ jobs.example_job.outputs.output2 }}
|
||||
|
||||
value: ${{ jobs.example_job.outputs.output2 }}
|
||||
|
||||
jobs:
|
||||
example_job:
|
||||
name: Generate output
|
||||
runs-on: ubuntu-latest
|
||||
runs-on: ubuntu-latest
|
||||
# Map the job outputs to step outputs
|
||||
outputs:
|
||||
output1: ${{ steps.step1.outputs.firstword }}
|
||||
|
||||
@@ -25,9 +25,9 @@ topics:
|
||||
|
||||
## About workflow templates
|
||||
|
||||
{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests.
|
||||
{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant workflow templates.{% endif %}
|
||||
|
||||
You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
|
||||
You can also create your own workflow templates to share with your organization. These templates will appear alongside the {% data variables.product.product_name %} workflow templates. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
|
||||
|
||||
## Using workflow templates
|
||||
|
||||
@@ -36,8 +36,8 @@ Anyone with write permission to a repository can set up {% data variables.produc
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. If you already have a workflow in your repository, click **New workflow**.
|
||||
1. Find the template that you want to use, then click **Set up this workflow**.
|
||||
1. If the workflow template contains comments detailing additional setup steps, follow these steps.
|
||||
1. Find the template that you want to use, then click **Set up this workflow**.{% if actions-starter-template-ui %} To help you find the template that you want, you can search for keywords or filter by category.{% endif %}
|
||||
1. If the workflow template contains comments detailing additional setup steps, follow these steps. Many of the templates have corresponding guides. For more information, see [the {% data variables.product.prodname_actions %} guides](/actions/guides)."
|
||||
1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
|
||||
1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs.
|
||||
1. Click **Start commit**.
|
||||
|
||||
@@ -9,7 +9,7 @@ versions:
|
||||
ghec: '*'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions
|
||||
- /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax/
|
||||
- /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax
|
||||
children:
|
||||
- /migrating-from-azure-pipelines-to-github-actions
|
||||
- /migrating-from-circleci-to-github-actions
|
||||
|
||||
@@ -71,6 +71,15 @@ These attributes are available. You can change the attribute names in the [manag
|
||||
| `public_keys` | Optional | The public SSH keys for the user. More than one can be specified. |
|
||||
| `gpg_keys` | Optional | The GPG keys for the user. More than one can be specified. |
|
||||
|
||||
To specify more than one value for an attribute, use multiple `<saml2:AttributeValue>` elements.
|
||||
|
||||
```
|
||||
<saml2:Attribute FriendlyName="public_keys" Name="urn:oid:1.2.840.113549.1.1.1" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
|
||||
<saml2:AttributeValue>ssh-rsa LONG KEY</saml2:AttributeValue>
|
||||
<saml2:AttributeValue>ssh-rsa LONG KEY 2</saml2:AttributeValue>
|
||||
</saml2:Attribute>
|
||||
```
|
||||
|
||||
## Configuring SAML settings
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
|
||||
@@ -31,6 +31,8 @@ Because client connections to {% data variables.product.prodname_ghe_server %} c
|
||||
|
||||
{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
|
||||
|
||||
{% data reusables.enterprise_installation.terminating-tls %}
|
||||
|
||||
### Enabling PROXY protocol support on {% data variables.product.product_location %}
|
||||
|
||||
We strongly recommend enabling PROXY protocol support for both your appliance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
|
||||
@@ -50,8 +52,6 @@ We strongly recommend enabling PROXY protocol support for both your appliance an
|
||||
|
||||
{% data reusables.enterprise_clustering.x-forwarded-for %}
|
||||
|
||||
{% data reusables.enterprise_installation.terminating-tls %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.privacy %}
|
||||
|
||||
@@ -56,8 +56,8 @@ If you need to get information on the users, organizations, and repositories in
|
||||
Specifically, you can download CSV reports that list
|
||||
|
||||
- all users
|
||||
- all users who have been active within the last month
|
||||
- all users who have been inactive for one month or more
|
||||
- all active users
|
||||
- all [dormant users](/admin/user-management/managing-dormant-users)
|
||||
- all users who have been suspended
|
||||
- all organizations
|
||||
- all repositories
|
||||
|
||||
@@ -10,7 +10,6 @@ redirect_from:
|
||||
- /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
|
||||
- /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
|
||||
- /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud
|
||||
permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
@@ -60,6 +59,12 @@ Enabling {% data variables.product.prodname_github_connect %} will not allow {%
|
||||
For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
|
||||
## Enabling {% data variables.product.prodname_github_connect %}
|
||||
|
||||
Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}.
|
||||
|
||||
If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_dotcom_the_website %} that is not owned by an enterprise account, you must enable {% data variables.product.prodname_github_connect %} with a personal account on {% data variables.product.prodname_dotcom_the_website %} that is an owner of the organization.
|
||||
|
||||
If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_dotcom_the_website %} that is owned by an enterprise account or to an enterprise account itself, you must enable {% data variables.product.prodname_github_connect %} with a personal account on {% data variables.product.prodname_dotcom_the_website %} that is an owner of the enterprise account.
|
||||
|
||||
{% ifversion ghes %}
|
||||
1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
|
||||
@@ -73,7 +78,9 @@ For more information about managing enterprise accounts using the GraphQL API, s
|
||||
1. Next to the enterprise account or organization you'd like to connect, click **Connect**.
|
||||

|
||||
|
||||
## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account
|
||||
## Disabling {% data variables.product.prodname_github_connect %}
|
||||
|
||||
Enterprise owners can disable {% data variables.product.prodname_github_connect %}.
|
||||
|
||||
When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.product.product_location %} are deleted.
|
||||
|
||||
|
||||
@@ -37,6 +37,8 @@ For more information about these features, see "[About the dependency graph](/gi
|
||||
|
||||
You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
|
||||
|
||||
### About generation of {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
@@ -21,9 +21,35 @@ This is an overview of the steps required to restore {% data variables.product.p
|
||||
|
||||
1. Confirm that the original appliance is offline.
|
||||
1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`.
|
||||
1. Configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance.
|
||||
1. To configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance, from the new appliance, set the required parameters with `ghe-config` command.
|
||||
|
||||
- Azure Blob Storage
|
||||
```shell
|
||||
ghe-config secrets.actions.storage.blob-provider "azure"
|
||||
ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_"
|
||||
```
|
||||
- Amazon S3
|
||||
```shell
|
||||
ghe-config secrets.actions.storage.blob-provider "s3"
|
||||
ghe-config secrets.actions.storage.s3.bucket-name "_S3_Bucket_Name"
|
||||
ghe-config secrets.actions.storage.s3.service-url "_S3_Service_URL_"
|
||||
ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_"
|
||||
ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_"
|
||||
```
|
||||
- Optionally, to enable S3 force path style, enter the following command:
|
||||
```shell
|
||||
ghe-config secrets.actions.storage.s3.force-path-style true
|
||||
```
|
||||
|
||||
|
||||
1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}.
|
||||
1. After {% data variables.product.prodname_actions %} is configured with the external storage provider, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
|
||||
```shell
|
||||
ghe-config app.actions.enabled true
|
||||
ghe-config-apply
|
||||
```
|
||||
|
||||
1. After {% data variables.product.prodname_actions %} is configured and enabled, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners).
|
||||
|
||||
For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)."
|
||||
|
||||
@@ -62,7 +62,7 @@ Before launching {% data variables.product.product_location %} on Azure, you'll
|
||||
|
||||
{% data reusables.enterprise_installation.necessary_ports %}
|
||||
|
||||
4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
|
||||
4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
|
||||
|
||||
Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 关于 GitHub AE
|
||||
intro: '{% data variables.product.prodname_ghe_managed %} 是一种在云端使用 {% data variables.product.prodname_dotcom %} 的安全性更强的标准方法。'
|
||||
title: About GitHub AE
|
||||
intro: '{% data variables.product.prodname_ghe_managed %} is a security-enhanced and compliant way to use {% data variables.product.prodname_dotcom %} in the cloud.'
|
||||
versions:
|
||||
ghae: '*'
|
||||
type: overview
|
||||
@@ -9,32 +9,33 @@ topics:
|
||||
- Fundamentals
|
||||
---
|
||||
|
||||
## 关于 {% data variables.product.prodname_ghe_managed %}
|
||||
## About {% data variables.product.prodname_ghe_managed %}
|
||||
|
||||
{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} 受到完全管理、可靠和且可扩展的,允许您在不牺牲风险管理的情况下加速交付。
|
||||
{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} is fully managed, reliable, and scalable, allowing you to accelerate delivery without sacrificing risk management.
|
||||
|
||||
{% data variables.product.prodname_ghe_managed %} 提供一个从想法到生产的开发者平台。 您可以使用团队了解和喜爱的工具提高开发速度,同时通过独特的安全和访问控制、工作流自动化及政策执行来维护行业和监管合规性。
|
||||
{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase development velocity with the tools that teams know and love, while you maintain industry and regulatory compliance with unique security and access controls, workflow automation, and policy enforcement.
|
||||
|
||||
## 高度可用的行星级云
|
||||
## A highly available and planet-scale cloud
|
||||
|
||||
{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务,托管在高可用性架构中。 {% data variables.product.prodname_ghe_managed %} 全球托管于云中,可以不受限制地扩展以支持您的完整开发生命周期。 {% data variables.product.prodname_dotcom %} 完全管理备份、故障转移和灾难恢复,因此您无需担心您的服务或数据。
|
||||
{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data.
|
||||
|
||||
## 数据存储
|
||||
## Data residency
|
||||
|
||||
您的所有数据都存储在您选择的地理区域内。 您可以遵守 GDRPR 和全球数据保护标准,将您的所有数据保存在您选定的区域。
|
||||
All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region.
|
||||
|
||||
## 隔离的帐户
|
||||
## Isolated accounts
|
||||
|
||||
所有开发者帐户在 {% data variables.product.prodname_ghe_managed %} 中完全隔离。 您可以通过身份提供商完全控制帐户,以 SAML 单点登录作为强制性要求。 SCIM 可让您确保员工只能访问他们应该访问的资源,如您的中央身份管理系统中所定义。 更多信息请参阅“[管理企业的身份和访问](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。
|
||||
All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)."
|
||||
|
||||
## 受限制的网络访问
|
||||
## Restricted network access
|
||||
|
||||
以受限的网络访问权限保护对您在 {% data variables.product.prodname_ghe_managed %} 上的企业的访问,以便只能从您的网络内访问您的数据。 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”。
|
||||
Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."
|
||||
|
||||
## 商业和政府环境
|
||||
## Commercial and government environments
|
||||
|
||||
{% data variables.product.prodname_ghe_managed %} 可用于 Azure Government 云(是美国政府机构及其伙伴信任的云)。 {% data variables.product.prodname_ghe_managed %} 也可在商业云中使用,因此您可以选择适合您组织的托管环境。
|
||||
{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[从 {% data variables.product.company_short %} 支持获得帮助](/admin/enterprise-support/receiving-help-from-github-support)"
|
||||
- "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
|
||||
- "[Receiving help from {% data variables.product.company_short %} Support](/admin/enterprise-support/receiving-help-from-github-support)"
|
||||
|
||||
@@ -35,8 +35,13 @@ When your code depends on a package that has a security vulnerability, this vuln
|
||||
{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %}
|
||||
- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %}
|
||||
- New advisory data is synchronized to {% data variables.product.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
{% note %}
|
||||
|
||||
**Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
{% endnote %}
|
||||
- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)."
|
||||
|
||||
{% data reusables.repositories.dependency-review %}
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Browsing security vulnerabilities in the GitHub Advisory Database
|
||||
intro: 'The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects on {% data variables.product.company_short %}.'
|
||||
shortTitle: Browse Advisory Database
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
- /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
@@ -22,13 +23,29 @@ topics:
|
||||
|
||||
{% data reusables.repositories.a-vulnerability-is %}
|
||||
|
||||
{% data variables.product.product_name %} will send you {% data variables.product.prodname_dependabot_alerts %} if we detect that any of the vulnerabilities from the {% data variables.product.prodname_advisory_database %} affect the packages that your repository depends on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
## About the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that have been mapped to packages tracked by the {% data variables.product.company_short %} dependency graph. {% data reusables.repositories.tracks-vulnerabilities %}
|
||||
The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
|
||||
|
||||
Each security advisory contains information about the vulnerability, including the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
|
||||
{% data reusables.repositories.tracks-vulnerabilities %}
|
||||
|
||||
### About {% data variables.product.company_short %}-reviewed advisories
|
||||
|
||||
{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities that have been mapped to packages tracked by the {% data variables.product.company_short %} dependency graph.
|
||||
|
||||
We carefully review each advisory for validity. Each {% data variables.product.company_short %}-reviewed advisory has a full description, and contains both ecosystem and package information.
|
||||
|
||||
If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
### About unreviewed advisories
|
||||
|
||||
Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed.
|
||||
|
||||
{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
|
||||
|
||||
## About security advisories
|
||||
|
||||
Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
|
||||
|
||||
The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
|
||||
- Low
|
||||
@@ -45,6 +62,11 @@ The {% data variables.product.prodname_advisory_database %} uses the CVSS levels
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Optionally, to filter the list, use any of the drop-down menus.
|
||||

|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
|
||||
|
||||
{% endtip %}
|
||||
3. Click on any advisory to view details.
|
||||
|
||||
{% note %}
|
||||
@@ -63,6 +85,8 @@ You can search the database, and use qualifiers to narrow your search. For examp
|
||||
|
||||
| Qualifier | Example |
|
||||
| ------------- | ------------- |
|
||||
| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories. |
|
||||
| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
|
||||
| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
|
||||
| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
|
||||
| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
|
||||
@@ -80,7 +104,7 @@ You can search the database, and use qualifiers to narrow your search. For examp
|
||||
|
||||
## Viewing your vulnerable repositories
|
||||
|
||||
For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
|
||||
For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
|
||||
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Click an advisory.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: About wikis
|
||||
intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.'
|
||||
redirect_from:
|
||||
- /articles/about-github-wikis/
|
||||
- /articles/about-github-wikis
|
||||
- /articles/about-wikis
|
||||
- /github/building-a-strong-community/about-wikis
|
||||
product: '{% data reusables.gated-features.wikis %}'
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user