From fead78930ffa7896582e4f00186e4e464e7ec3ec Mon Sep 17 00:00:00 2001
From: github-openapi-bot
 <69533958+github-openapi-bot@users.noreply.github.com>
Date: Fri, 11 Dec 2020 12:10:45 -0500
Subject: [PATCH] Updating OpenAPI descriptions (#16778)

Co-authored-by: Sarah Edwards <skedwards88@github.com>
---
 lib/rest/static/decorated/api.github.com.json        | 12 ++++++------
 lib/rest/static/decorated/ghes-2.18.json             |  8 ++++----
 lib/rest/static/decorated/ghes-2.19.json             |  8 ++++----
 lib/rest/static/decorated/ghes-2.20.json             |  8 ++++----
 lib/rest/static/decorated/ghes-2.21.json             |  8 ++++----
 lib/rest/static/decorated/ghes-2.22.json             |  8 ++++----
 lib/rest/static/decorated/github.ae.json             |  8 ++++----
 .../static/dereferenced/api.github.com.deref.json    |  4 +++-
 lib/rest/static/dereferenced/ghes-2.18.deref.json    |  2 +-
 lib/rest/static/dereferenced/ghes-2.19.deref.json    |  2 +-
 lib/rest/static/dereferenced/ghes-2.20.deref.json    |  2 +-
 lib/rest/static/dereferenced/ghes-2.21.deref.json    |  2 +-
 lib/rest/static/dereferenced/ghes-2.22.deref.json    |  2 +-
 lib/rest/static/dereferenced/github.ae.deref.json    |  2 +-
 14 files changed, 39 insertions(+), 37 deletions(-)

diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json
index f5234c81cc..dc05a83d45 100644
--- a/lib/rest/static/decorated/api.github.com.json
+++ b/lib/rest/static/decorated/api.github.com.json
@@ -49098,11 +49098,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -49302,11 +49302,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
@@ -80855,7 +80855,7 @@
         "httpStatusCode": "200",
         "httpStatusMessage": "OK",
         "description": "Default response",
-        "payload": "<pre><code class=\"hljs language-json\">[\n  {\n    <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n    <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n    <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n    <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n    <span class=\"hljs-attr\">\"account\"</span>: {\n      <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n      <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n      <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n    },\n    <span class=\"hljs-attr\">\"plan\"</span>: {\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n      <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n      <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n      <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n      <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n      <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n      <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n      <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n      <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n      <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n      <span class=\"hljs-attr\">\"bullets\"</span>: [\n        <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n        <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n      ]\n    }\n  }\n]\n</code></pre>"
+        "payload": "<pre><code class=\"hljs language-json\">[\n  {\n    <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n    <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n    <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n    <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n    <span class=\"hljs-attr\">\"account\"</span>: {\n      <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n      <span class=\"hljs-attr\">\"node_id\"</span>: <span class=\"hljs-string\">\"MDEyOk9yZ2FuaXphdGlvbjE=\"</span>,\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n      <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n      <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n    },\n    <span class=\"hljs-attr\">\"plan\"</span>: {\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n      <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n      <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n      <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n      <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n      <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n      <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n      <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n      <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n      <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n      <span class=\"hljs-attr\">\"bullets\"</span>: [\n        <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n        <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n      ]\n    }\n  }\n]\n</code></pre>"
       },
       {
         "httpStatusCode": "304",
@@ -80942,7 +80942,7 @@
         "httpStatusCode": "200",
         "httpStatusMessage": "OK",
         "description": "Default response",
-        "payload": "<pre><code class=\"hljs language-json\">[\n  {\n    <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n    <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n    <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n    <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n    <span class=\"hljs-attr\">\"account\"</span>: {\n      <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n      <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n      <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n    },\n    <span class=\"hljs-attr\">\"plan\"</span>: {\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n      <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n      <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n      <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n      <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n      <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n      <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n      <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n      <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n      <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n      <span class=\"hljs-attr\">\"bullets\"</span>: [\n        <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n        <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n      ]\n    }\n  }\n]\n</code></pre>"
+        "payload": "<pre><code class=\"hljs language-json\">[\n  {\n    <span class=\"hljs-attr\">\"billing_cycle\"</span>: <span class=\"hljs-string\">\"monthly\"</span>,\n    <span class=\"hljs-attr\">\"next_billing_date\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"unit_count\"</span>: <span class=\"hljs-literal\">null</span>,\n    <span class=\"hljs-attr\">\"on_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n    <span class=\"hljs-attr\">\"free_trial_ends_on\"</span>: <span class=\"hljs-string\">\"2017-11-11T00:00:00Z\"</span>,\n    <span class=\"hljs-attr\">\"updated_at\"</span>: <span class=\"hljs-string\">\"2017-11-02T01:12:12Z\"</span>,\n    <span class=\"hljs-attr\">\"account\"</span>: {\n      <span class=\"hljs-attr\">\"login\"</span>: <span class=\"hljs-string\">\"github\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">4</span>,\n      <span class=\"hljs-attr\">\"node_id\"</span>: <span class=\"hljs-string\">\"MDEyOk9yZ2FuaXphdGlvbjE=\"</span>,\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/orgs/github\"</span>,\n      <span class=\"hljs-attr\">\"email\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"organization_billing_email\"</span>: <span class=\"hljs-string\">\"billing@github.com\"</span>,\n      <span class=\"hljs-attr\">\"type\"</span>: <span class=\"hljs-string\">\"Organization\"</span>\n    },\n    <span class=\"hljs-attr\">\"plan\"</span>: {\n      <span class=\"hljs-attr\">\"url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313\"</span>,\n      <span class=\"hljs-attr\">\"accounts_url\"</span>: <span class=\"hljs-string\">\"https://api.github.com/marketplace_listing/plans/1313/accounts\"</span>,\n      <span class=\"hljs-attr\">\"id\"</span>: <span class=\"hljs-number\">1313</span>,\n      <span class=\"hljs-attr\">\"number\"</span>: <span class=\"hljs-number\">3</span>,\n      <span class=\"hljs-attr\">\"name\"</span>: <span class=\"hljs-string\">\"Pro\"</span>,\n      <span class=\"hljs-attr\">\"description\"</span>: <span class=\"hljs-string\">\"A professional-grade CI solution\"</span>,\n      <span class=\"hljs-attr\">\"monthly_price_in_cents\"</span>: <span class=\"hljs-number\">1099</span>,\n      <span class=\"hljs-attr\">\"yearly_price_in_cents\"</span>: <span class=\"hljs-number\">11870</span>,\n      <span class=\"hljs-attr\">\"price_model\"</span>: <span class=\"hljs-string\">\"flat-rate\"</span>,\n      <span class=\"hljs-attr\">\"has_free_trial\"</span>: <span class=\"hljs-literal\">true</span>,\n      <span class=\"hljs-attr\">\"unit_name\"</span>: <span class=\"hljs-literal\">null</span>,\n      <span class=\"hljs-attr\">\"state\"</span>: <span class=\"hljs-string\">\"published\"</span>,\n      <span class=\"hljs-attr\">\"bullets\"</span>: [\n        <span class=\"hljs-string\">\"Up to 25 private repositories\"</span>,\n        <span class=\"hljs-string\">\"11 concurrent builds\"</span>\n      ]\n    }\n  }\n]\n</code></pre>"
       },
       {
         "httpStatusCode": "304",
diff --git a/lib/rest/static/decorated/ghes-2.18.json b/lib/rest/static/decorated/ghes-2.18.json
index d10bcdb33c..8cd77fe5b1 100644
--- a/lib/rest/static/decorated/ghes-2.18.json
+++ b/lib/rest/static/decorated/ghes-2.18.json
@@ -34324,11 +34324,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -34528,11 +34528,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
diff --git a/lib/rest/static/decorated/ghes-2.19.json b/lib/rest/static/decorated/ghes-2.19.json
index e254f94730..953c6ba88a 100644
--- a/lib/rest/static/decorated/ghes-2.19.json
+++ b/lib/rest/static/decorated/ghes-2.19.json
@@ -34983,11 +34983,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -35187,11 +35187,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
diff --git a/lib/rest/static/decorated/ghes-2.20.json b/lib/rest/static/decorated/ghes-2.20.json
index b5889ea988..7212ad4f3f 100644
--- a/lib/rest/static/decorated/ghes-2.20.json
+++ b/lib/rest/static/decorated/ghes-2.20.json
@@ -35450,11 +35450,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -35654,11 +35654,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
diff --git a/lib/rest/static/decorated/ghes-2.21.json b/lib/rest/static/decorated/ghes-2.21.json
index 6af3cf0431..c305a65fd1 100644
--- a/lib/rest/static/decorated/ghes-2.21.json
+++ b/lib/rest/static/decorated/ghes-2.21.json
@@ -39099,11 +39099,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -39303,11 +39303,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
diff --git a/lib/rest/static/decorated/ghes-2.22.json b/lib/rest/static/decorated/ghes-2.22.json
index 2a22ddf102..5b4f9ed054 100644
--- a/lib/rest/static/decorated/ghes-2.22.json
+++ b/lib/rest/static/decorated/ghes-2.22.json
@@ -46564,11 +46564,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -46768,11 +46768,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index b57c96c290..09c762b704 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -36969,11 +36969,11 @@
               },
               "base_tree": {
                 "type": "string",
-                "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+                "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
                 "name": "base_tree",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+                "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
                 "childParamsGroups": []
               }
             },
@@ -37173,11 +37173,11 @@
       },
       {
         "type": "string",
-        "description": "<p>The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.</p>",
+        "description": "<p>The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by <code>base_tree</code> and entries defined in the <code>tree</code> parameter. Entries defined in the <code>tree</code> parameter will overwrite items from <code>base_tree</code> with the same <code>path</code>. If you're creating new changes on a branch, then normally you'd set <code>base_tree</code> to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the <code>tree</code> parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the <code>tree</code> parameter will be listed as deleted by the new commit.</p>",
         "name": "base_tree",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted.",
+        "rawDescription": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n",
         "childParamsGroups": []
       }
     ]
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index 7dbc79d269..82f8b97418 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -155506,7 +155506,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [
@@ -270539,6 +270539,7 @@
                         "account": {
                           "login": "github",
                           "id": 4,
+                          "node_id": "MDEyOk9yZ2FuaXphdGlvbjE=",
                           "url": "https://api.github.com/orgs/github",
                           "email": null,
                           "organization_billing_email": "billing@github.com",
@@ -270852,6 +270853,7 @@
                         "account": {
                           "login": "github",
                           "id": 4,
+                          "node_id": "MDEyOk9yZ2FuaXphdGlvbjE=",
                           "url": "https://api.github.com/orgs/github",
                           "email": null,
                           "organization_billing_email": "billing@github.com",
diff --git a/lib/rest/static/dereferenced/ghes-2.18.deref.json b/lib/rest/static/dereferenced/ghes-2.18.deref.json
index 476aa57a33..f4adb36abf 100644
--- a/lib/rest/static/dereferenced/ghes-2.18.deref.json
+++ b/lib/rest/static/dereferenced/ghes-2.18.deref.json
@@ -110376,7 +110376,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [
diff --git a/lib/rest/static/dereferenced/ghes-2.19.deref.json b/lib/rest/static/dereferenced/ghes-2.19.deref.json
index 24c6a057fb..2a8e02c5c3 100644
--- a/lib/rest/static/dereferenced/ghes-2.19.deref.json
+++ b/lib/rest/static/dereferenced/ghes-2.19.deref.json
@@ -113552,7 +113552,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [
diff --git a/lib/rest/static/dereferenced/ghes-2.20.deref.json b/lib/rest/static/dereferenced/ghes-2.20.deref.json
index 7e7bac75ea..17dc4216de 100644
--- a/lib/rest/static/dereferenced/ghes-2.20.deref.json
+++ b/lib/rest/static/dereferenced/ghes-2.20.deref.json
@@ -114769,7 +114769,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [
diff --git a/lib/rest/static/dereferenced/ghes-2.21.deref.json b/lib/rest/static/dereferenced/ghes-2.21.deref.json
index 1c3be8a440..e3fb6ebdd8 100644
--- a/lib/rest/static/dereferenced/ghes-2.21.deref.json
+++ b/lib/rest/static/dereferenced/ghes-2.21.deref.json
@@ -124029,7 +124029,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [
diff --git a/lib/rest/static/dereferenced/ghes-2.22.deref.json b/lib/rest/static/dereferenced/ghes-2.22.deref.json
index b89d584129..1f96fa42c2 100644
--- a/lib/rest/static/dereferenced/ghes-2.22.deref.json
+++ b/lib/rest/static/dereferenced/ghes-2.22.deref.json
@@ -145204,7 +145204,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index f72cf1c7b8..0c149da495 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -118183,7 +118183,7 @@
                   },
                   "base_tree": {
                     "type": "string",
-                    "description": "The SHA1 of the tree you want to update with new data. If you don't set this, the commit will be created on top of everything; however, it will only contain your change, the rest of your files will show up as deleted."
+                    "description": "The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on.\nIf not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit.\n"
                   }
                 },
                 "required": [