Updating OpenAPI descriptions

descriptions/ghes-2.18/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": [

descriptions/ghes-2.18/dereferenced/ghes-2.18.deref.yaml

@@ -84685,10 +84685,9 @@ paths:
                           Using both `tree.sha` and `content` will return an error."
                 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.
+                    If 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.
               required:
               - tree
             example:

descriptions/ghes-2.18/ghes-2.18.json

@@ -18634,7 +18634,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": [

descriptions/ghes-2.18/ghes-2.18.yaml

@@ -13787,10 +13787,9 @@ paths:
                           Using both `tree.sha` and `content` will return an error."
                 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.
+                    If 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.
               required:
               - tree
             example:

descriptions/ghes-2.19/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": [

descriptions/ghes-2.19/dereferenced/ghes-2.19.deref.yaml

@@ -87058,10 +87058,9 @@ paths:
                           Using both `tree.sha` and `content` will return an error."
                 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.
+                    If 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.
               required:
               - tree
             example: