Merge pull request #1179 from php-api-clients/GitHub/from-1.1.4-eb75ba12b8f78ce6cf7e307635ad5f13-from-1.1.4-eb75ba12b8f78ce6cf7e307635ad5f13

Author: WyriHaximus

clients/GitHub/etc/openapi-client-generator.state

@@ -1,5 +1,5 @@
 {
-    "specHash": "6427e6326d9646fc1b49f1e1dcf2d9db",
+    "specHash": "eb75ba12b8f78ce6cf7e307635ad5f13",
     "generatedFiles": {
         "files": [
             {
@@ -5648,7 +5648,7 @@
             },
             {
                 "name": ".\/clients\/GitHub\/etc\/..\/\/src\/\/Operation\/Pulls.php",
-                "hash": "60138d3a0e61f4cd49819b25927d75b3"
+                "hash": "d922518f8c93d21148f0207ad009c14a"
             },
             {
                 "name": ".\/clients\/GitHub\/etc\/..\/\/src\/\/Operation\/SecurityAdvisories.php",

etc/specs/GitHub/current.spec.yaml

@@ -24761,7 +24761,7 @@ paths:
 
         To process a response with a large number of commits, use a query parameter (`per_page` or `page`) to paginate the results. When using pagination:
 
-        - The list of changed files is only shown on the first page of results, but it includes all changed files for the entire comparison.
+        - The list of changed files is only shown on the first page of results, and it includes up to 300 changed files for the entire comparison.
         - The results are returned in chronological order, but the last commit in the returned list may not be the most recent one in the entire set if there are more pages of results.
 
         For more information on working with pagination, see "[Using pagination in the REST API](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api)."