Skip to content

Commit c6ac7ff

Browse files
WyriHaximusgithub-actions[bot]
WyriHaximus
authored and
github-actions[bot]
committed
[GitHubEnterpriseCloud] Update to 1.1.4-1af67ef4f45d37f00bce6c1060039205 from 1.1.4-16de2a81f1c35833bd49594dda36d269
Detected Schema changes: 2025-02-26 20:29:30 ERROR unable to open the rolodex file, check specification references and base path ├ file: /__w/github-root/github-root/server-statistics-actions.yaml └ error: open /__w/github-root/github-root/server-statistics-actions.yaml: no such file or directory 2025-02-26 20:29:30 ERROR unable to open the rolodex file, check specification references and base path ├ error: open /__w/github-root/github-root/server-statistics-packages.yaml: no such file or directory └ file: /__w/github-root/github-root/server-statistics-packages.yaml 2025-02-26 20:29:30 ERROR unable to open the rolodex file, check specification references and base path ├ file: /__w/github-root/github-root/server-statistics-advisory-db.yaml └ error: open /__w/github-root/github-root/server-statistics-advisory-db.yaml: no such file or directory 2025-02-26 20:29:31 ERROR unable to open the rolodex file, check specification references and base path ├ file: /__w/github-root/github-root/server-statistics-actions.yaml └ error: open /__w/github-root/github-root/server-statistics-actions.yaml: no such file or directory 2025-02-26 20:29:31 ERROR unable to open the rolodex file, check specification references and base path ├ file: /__w/github-root/github-root/server-statistics-packages.yaml └ error: open /__w/github-root/github-root/server-statistics-packages.yaml: no such file or directory 2025-02-26 20:29:31 ERROR unable to open the rolodex file, check specification references and base path ├ file: /__w/github-root/github-root/server-statistics-advisory-db.yaml └ error: open /__w/github-root/github-root/server-statistics-advisory-db.yaml: no such file or directory ERROR: component `server-statistics-actions.yaml` does not exist in the specification ERROR: component `server-statistics-packages.yaml` does not exist in the specification ERROR: component `server-statistics-advisory-db.yaml` does not exist in the specification ERROR: cannot resolve reference `server-statistics-actions.yaml`, it's missing: $.['server-statistics-actions.yaml'] [215960:11] ERROR: cannot resolve reference `server-statistics-packages.yaml`, it's missing: $.['server-statistics-packages.yaml'] [215962:11] ERROR: cannot resolve reference `server-statistics-advisory-db.yaml`, it's missing: $.['server-statistics-advisory-db.yaml'] [215964:11] ERROR: component `server-statistics-actions.yaml` does not exist in the specification ERROR: component `server-statistics-packages.yaml` does not exist in the specification ERROR: component `server-statistics-advisory-db.yaml` does not exist in the specification ERROR: cannot resolve reference `server-statistics-actions.yaml`, it's missing: $.['server-statistics-actions.yaml'] [215510:11] ERROR: cannot resolve reference `server-statistics-packages.yaml`, it's missing: $.['server-statistics-packages.yaml'] [215512:11] ERROR: cannot resolve reference `server-statistics-advisory-db.yaml`, it's missing: $.['server-statistics-advisory-db.yaml'] [215514:11]
1 parent fef4e95 commit c6ac7ff

File tree

85 files changed

+7345
-193
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

85 files changed

+7345
-193
lines changed

‎clients/GitHubEnterpriseCloud/README.md‎

Lines changed: 232 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2920,6 +2920,30 @@ $client->operations()->enterpriseAdmin()->createOrUpdateEnterpriseCustomProperti
29202920
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/enterprise-admin/custom-properties#create-or-update-custom-properties-for-an-enterprise).
29212921

29222922

2923+
### enterprise-admin/promote-custom-property-to-enterprise
2924+
2925+
Promote a custom property to an enterprise
2926+
2927+
Using the `call` method:
2928+
```php
2929+
$client->call('PUT /enterprises/{enterprise}/properties/schema/organizations/{org}/{custom_property_name}/promote', [
2930+
'enterprise' => 'generated',
2931+
'org' => 'generated',
2932+
'custom_property_name' => 'generated',
2933+
]);
2934+
```
2935+
2936+
Operations method:
2937+
```php
2938+
$client->operations()->enterpriseAdmin()->promoteCustomPropertyToEnterprise( enterprise: 'generated',
2939+
org: 'generated',
2940+
custom_property_name: 'generated',
2941+
);
2942+
```
2943+
2944+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/enterprise-admin/custom-properties#promote-a-custom-property-to-an-enterprise).
2945+
2946+
29232947
### enterprise-admin/get-enterprise-custom-property
29242948

29252949
Get a custom property for an enterprise
@@ -6852,6 +6876,74 @@ $client->operations()->orgs()->listPushBypassRequestsListing( org: 'gener
68526876
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/orgs/bypass-requests#list-push-rule-bypass-requests-within-an-organization).
68536877

68546878

6879+
### secret-scanning/list-org-bypass-requests
6880+
6881+
List bypass requests for secret scanning for an org
6882+
6883+
Using the `call` method:
6884+
```php
6885+
$client->call('GET /orgs/{org}/bypass-requests/secret-scanning', [
6886+
'org' => 'generated',
6887+
'repository_name' => 'generated',
6888+
'reviewer' => 'generated',
6889+
'requester' => 'generated',
6890+
'time_period' => 'generated',
6891+
'request_status' => 'generated',
6892+
'per_page' => 8,
6893+
'page' => 1,
6894+
]);
6895+
```
6896+
6897+
Operations method:
6898+
```php
6899+
$client->operations()->secretScanning()->listOrgBypassRequests( org: 'generated',
6900+
repository_name: 'generated',
6901+
reviewer: 'generated',
6902+
requester: 'generated',
6903+
time_period: 'generated',
6904+
request_status: 'generated',
6905+
per_page: 8,
6906+
page: 1,
6907+
);
6908+
```
6909+
6910+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#list-bypass-requests-for-secret-scanning-for-an-org).
6911+
6912+
6913+
### secret-scanning/list-org-bypass-requests
6914+
6915+
List bypass requests for secret scanning for an org
6916+
6917+
Using the `call` method:
6918+
```php
6919+
$client->call('LIST /orgs/{org}/bypass-requests/secret-scanning', [
6920+
'org' => 'generated',
6921+
'repository_name' => 'generated',
6922+
'reviewer' => 'generated',
6923+
'requester' => 'generated',
6924+
'time_period' => 'generated',
6925+
'request_status' => 'generated',
6926+
'per_page' => 8,
6927+
'page' => 1,
6928+
]);
6929+
```
6930+
6931+
Operations method:
6932+
```php
6933+
$client->operations()->secretScanning()->listOrgBypassRequestsListing( org: 'generated',
6934+
repository_name: 'generated',
6935+
reviewer: 'generated',
6936+
requester: 'generated',
6937+
time_period: 'generated',
6938+
request_status: 'generated',
6939+
per_page: 8,
6940+
page: 1,
6941+
);
6942+
```
6943+
6944+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#list-bypass-requests-for-secret-scanning-for-an-org).
6945+
6946+
68556947
### code-scanning/list-alerts-for-org
68566948

68576949
List code scanning alerts for an organization
@@ -17451,6 +17543,146 @@ $client->operations()->repos()->getRepoPushBypassRequest( owner: 'generat
1745117543
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/repos/bypass-requests#get-a-repository-push-bypass-request).
1745217544

1745317545

17546+
### secret-scanning/list-repo-bypass-requests
17547+
17548+
List bypass requests for secret scanning for a repository
17549+
17550+
Using the `call` method:
17551+
```php
17552+
$client->call('GET /repos/{owner}/{repo}/bypass-requests/secret-scanning', [
17553+
'owner' => 'generated',
17554+
'repo' => 'generated',
17555+
'reviewer' => 'generated',
17556+
'requester' => 'generated',
17557+
'time_period' => 'generated',
17558+
'request_status' => 'generated',
17559+
'per_page' => 8,
17560+
'page' => 1,
17561+
]);
17562+
```
17563+
17564+
Operations method:
17565+
```php
17566+
$client->operations()->secretScanning()->listRepoBypassRequests( owner: 'generated',
17567+
repo: 'generated',
17568+
reviewer: 'generated',
17569+
requester: 'generated',
17570+
time_period: 'generated',
17571+
request_status: 'generated',
17572+
per_page: 8,
17573+
page: 1,
17574+
);
17575+
```
17576+
17577+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#list-bypass-requests-for-secret-scanning-for-a-repository).
17578+
17579+
17580+
### secret-scanning/list-repo-bypass-requests
17581+
17582+
List bypass requests for secret scanning for a repository
17583+
17584+
Using the `call` method:
17585+
```php
17586+
$client->call('LIST /repos/{owner}/{repo}/bypass-requests/secret-scanning', [
17587+
'owner' => 'generated',
17588+
'repo' => 'generated',
17589+
'reviewer' => 'generated',
17590+
'requester' => 'generated',
17591+
'time_period' => 'generated',
17592+
'request_status' => 'generated',
17593+
'per_page' => 8,
17594+
'page' => 1,
17595+
]);
17596+
```
17597+
17598+
Operations method:
17599+
```php
17600+
$client->operations()->secretScanning()->listRepoBypassRequestsListing( owner: 'generated',
17601+
repo: 'generated',
17602+
reviewer: 'generated',
17603+
requester: 'generated',
17604+
time_period: 'generated',
17605+
request_status: 'generated',
17606+
per_page: 8,
17607+
page: 1,
17608+
);
17609+
```
17610+
17611+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#list-bypass-requests-for-secret-scanning-for-a-repository).
17612+
17613+
17614+
### secret-scanning/get-bypass-request
17615+
17616+
Get a bypass request for secret scanning
17617+
17618+
Using the `call` method:
17619+
```php
17620+
$client->call('GET /repos/{owner}/{repo}/bypass-requests/secret-scanning/{bypass_request_number}', [
17621+
'owner' => 'generated',
17622+
'repo' => 'generated',
17623+
'bypass_request_number' => 21,
17624+
]);
17625+
```
17626+
17627+
Operations method:
17628+
```php
17629+
$client->operations()->secretScanning()->getBypassRequest( owner: 'generated',
17630+
repo: 'generated',
17631+
bypass_request_number: 21,
17632+
);
17633+
```
17634+
17635+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#get-a-bypass-request-for-secret-scanning).
17636+
17637+
17638+
### secret-scanning/review-bypass-request
17639+
17640+
Review a bypass request for secret scanning
17641+
17642+
Using the `call` method:
17643+
```php
17644+
$client->call('PATCH /repos/{owner}/{repo}/bypass-requests/secret-scanning/{bypass_request_number}', [
17645+
'owner' => 'generated',
17646+
'repo' => 'generated',
17647+
'bypass_request_number' => 21,
17648+
]);
17649+
```
17650+
17651+
Operations method:
17652+
```php
17653+
$client->operations()->secretScanning()->reviewBypassRequest( owner: 'generated',
17654+
repo: 'generated',
17655+
bypass_request_number: 21,
17656+
);
17657+
```
17658+
17659+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#review-a-bypass-request-for-secret-scanning).
17660+
17661+
17662+
### secret-scanning/dismiss-bypass-response
17663+
17664+
Dismiss a response on a bypass request for secret scanning
17665+
17666+
Using the `call` method:
17667+
```php
17668+
$client->call('DELETE /repos/{owner}/{repo}/bypass-responses/secret-scanning/{bypass_response_id}', [
17669+
'owner' => 'generated',
17670+
'repo' => 'generated',
17671+
'bypass_response_id' => 18,
17672+
]);
17673+
```
17674+
17675+
Operations method:
17676+
```php
17677+
$client->operations()->secretScanning()->dismissBypassResponse( owner: 'generated',
17678+
repo: 'generated',
17679+
bypass_response_id: 18,
17680+
);
17681+
```
17682+
17683+
You can find more about this operation over at the [API method documentation](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning/delegated-bypass#dismiss-a-response-on-a-bypass-request-for-secret-scanning).
17684+
17685+
1745417686
### checks/create
1745517687

1745617688
Create a check run

0 commit comments

Comments
 (0)